IPv6 Scoped Address Architecture
RFC 4007
Yes
No Objection
Note: This ballot was opened for revision 02 and is now closed.
(Margaret Cullen; former steering group member) Yes
(Alex Zinin; former steering group member) No Objection
(Allison Mankin; former steering group member) No Objection
(Bert Wijnen; former steering group member) No Objection
This formulation (towards bottom of page 6) sounds/feels a bit strange: dedicated purpose. An entry of a Management Information Base (MIB) will be an example of the dedicated purpose. The actual Not sure what "An entry of a .. (MIB)" is. Maybe a better sentence might be Usage of the index to identify an entry in the Management Information Base (MIB) is an example of the dedicated purpose.
(Bill Fenner; former steering group member) No Objection
(David Kessens; former steering group member) No Objection
(Scott Hollenbeck; former steering group member) No Objection
A table of contents would be helpful. The I-D checklist says one is required for documents longer than 15 pages.
(Steven Bellovin; former steering group member) (was Discuss) No Objection
The discussion of convex routing in Section 5 should probably note that tunneled links are excluded from the prohibition.
(Ted Hardie; former steering group member) No Objection
In Section 6:
A tunnel interface (e.g., the abstract endpoint of an
IPv6-over-IPv6 tunnel [8], presumably established over either the
Ethernet or the point-to-point link.)
COMMENT: In general, this is a very helpful example. I would
suggest, though, that defining the tunnel interface as established
over the Ethernet might help illustrate the point that it gets
its own link-local zone, where two interfaces to the same Ethernet
link do not. Not strictly necessary, but it would be a good opportunity
to make the point.