All,
My usual AD review of this document threw up a few small issues that don't need
to delay the start of IETF last call. Could you please treat them as last call
comments and address them with any other points that are raised.
Thanks,
Adrian
===
Hi authors,
Thanks for this document. Sorry I sat on it for a little while.
The document is very readable and doesn't waste words.
There are a few small nits that need to be sorted out. I think we can
handle these as part of the IETF last call, so I will start that process
and then send these comments as last call comments.
Thanks for the work,
Adrian
===
"MPL" is not a well-known abbreviation so we need to expand it:
- in the document title
OLD
MPL forwarder policy for multicast with admin-local scope
NEW
Forwarder policy for multicast with admin-local scope in the
Multicast Protocol for Low power and Lossy Networks (MPL)
- in the Abstract
OLD
The purpose of this document is to specify an automated policy for
the routing of MPL multicast messages with admin-local scope in a
border router.
NEW
The purpose of this document is to specify an automated policy for
the routing of Multicast Protocol for Low power and Lossy Networks
(MPL) multicast messages with admin-local scope in a border router.
- in the third paragraph of the Introduction
OLD
The admin-local scope must therefore be administratively configured.
This draft describes an automated policy for the MPL forwarding of
multicast messages with admin-local scope within a border router.
NEW
The admin-local scope must therefore be administratively configured.
This draft describes an automated policy for the Multicast Protocol
for Low power and Lossy Networks (MPL) [[I-D.ietf-roll-trickle-mcast]
forwarding of multicast messages with admin-local scope within a
border router.
---
I think it would be worth scoping the term "border router" in the
Introduction. Something like...
OLD
multicast messages with admin-local scope within a border router.
NEW
multicast messages with admin-local scope within a border router
that lies between a network running MPL and some other network.
---
The last paragraph of the Introduction reads...
It is expected that the network of an organization, building, or
home, is connected to the Internet via the edge routers provided by
an ISP. The intention is that within the network of an organization,
building, or home, MPL messages with multicast addresses of admin-
local scope are freely forwarded but are never forwarded to edge
routers which MUST NOT enable their interfaces for MPL messages.
This suggests that your vision is...
ISP network --- Access --- Border --- MPL network
Router Router
That is fine. But wouldn't it be possible to have an access router that
also served as a border router?
---------------------
| Access Router |
| |
| -----------| MPL i/f
|non-MPL | multicast +---------- MPL network
ISP network --- +---------| forwarder |
|traffic | | MPL i/f
| | +---------- MPL network
| -----------|
---------------------
What you wrote may be a reflection of the boxes on the market today, and
that is fine, but perhaps you are being too limiting of future
developments.
---
A few more abbreviations need to be expanded on first use.
Section 2.1 "PAN"
Section 2.2 "SSID"
---
In section 2.4 you note that Bluetooth does not have the concept of
associating more than one network with a channel. You say that the way
to handle this is to set the network identifier of a BTLE link is "any".
Add the head of section 2 you say
When no network identifier exists for a given link, the network
identifier has the value "undefined".
Are these two statements consistent?
---
Section 3
s/with an scope/with a scope/
---
Section 3
You have "MPL zone". Do you mean "MPL4 zone"?
---
Please add a note to Section 10 saying that the change log can be
removed before publication as an RFC.