Definitions of Managed Objects for Mapping of Address and Port with Encapsulation (MAP-E)
RFC 8389

Note: This ballot was opened for revision 12 and is now closed.

(Terry Manderson) Yes

Ignas Bagdonas No Objection

Comment (2018-05-24 for -12)
No email
send info
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.

Deborah Brungard No Objection

(Ben Campbell) No Objection

Comment (2018-05-23 for -12)
No email
send info
Please consider using the boilerplate from RFC 8174 rather than 2119. There are some lower case instances of normative keywords.

Alissa Cooper No Objection

(Spencer Dawkins) No Objection

Benjamin Kaduk No Objection

Comment (2018-05-18 for -12)
No email
send info
Please expand "Customer Edge (CE)" on first use.

Suresh Krishnan No Objection

Warren Kumari No Objection

Comment (2018-05-22 for -12)
No email
send info
The obvious next comment is "Where is the YANG module?!" :-)

Mirja Kühlewind No Objection

Alexey Melnikov No Objection

(Eric Rescorla) No Objection

Alvaro Retana No Objection

Adam Roach No Objection

Comment (2018-05-21 for -12)
No email
send info
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..."
       ^

Martin Vigoureux No Objection