Definitions of Managed Objects for Mapping of Address and Port with Encapsulation (MAP-E)
RFC 8389
Yes
No Objection
Note: This ballot was opened for revision 12 and is now closed.
Alvaro Retana No Objection
Warren Kumari No Objection
The obvious next comment is "Where is the YANG module?!" :-)
(Terry Manderson; former steering group member) Yes
(Adam Roach; former steering group member) No Objection
Thank you for a clearly written document. I have some very editorial corrections
to suggest.
---------------------------------------------------------------------------
§4.1.2:
> invalid packets that have been identified. There are two kind of
"...two kinds..."
> - The Border Relay (BR) will validates the received packet's source
"...will validate..."
---------------------------------------------------------------------------
§5:
> DESCRIPTION
> "Indicates that the PSID is represented as hexidecimal for
> clarity."
"...hexadecimal..."
^
(Alexey Melnikov; former steering group member) No Objection
(Alissa Cooper; former steering group member) No Objection
(Ben Campbell; former steering group member) No Objection
Please consider using the boilerplate from RFC 8174 rather than 2119. There are some lower case instances of normative keywords.
(Benjamin Kaduk; former steering group member) No Objection
Please expand "Customer Edge (CE)" on first use.
(Deborah Brungard; former steering group member) No Objection
(Eric Rescorla; former steering group member) No Objection
(Ignas Bagdonas; former steering group member) No Objection
A nit - maybe adding a paragraph mentioning that from manageability perspective this document specifies only a subset of what corresponding YANG module defined in I-D softwire-yang provides would be suitable.
(Martin Vigoureux; former steering group member) No Objection
(Mirja Kühlewind; former steering group member) No Objection
(Spencer Dawkins; former steering group member) No Objection
(Suresh Krishnan; former steering group member) No Objection