A Framework for Ethernet Tree (E-Tree) Service over a Multiprotocol Label Switching (MPLS) Network
RFC 7387

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

(Adrian Farrel) Yes

(Jari Arkko) No Objection

Alissa Cooper No Objection

(Spencer Dawkins) No Objection

(Stephen Farrell) No Objection

Comment (2014-08-07 for -07)
No email
send info
I believe that its about time that text like sections 5 and 6
identified the lack of confidentiality mechanisms as a gap that
needs to be filled. Which could done be via MACsec or
(self-promotion alert!) MPLS with opportunistic security, or
something else. Can you justify (given BCP188) why this is not
a gap that's worth a look? This isn't a discuss since I'd be
happy to raise such on a protocol spec if warranted, but also
because it'd be wrong to expect you to re-do all L2VPN (by
adding a "real" P:-) in this draft.

(Joel Jaeggli) No Objection

(Kathleen Moriarty) No Objection

Comment (2014-08-07 for -07)
No email
send info
Could figure 1 be placed after the first paragraph of Section 3?  This would make it easier to look at the figure while reading the description that comes before and after the figure.

(Pete Resnick) No Objection

(Martin Stiemerling) No Objection