Mirja Kühlewind has entered the following ballot position for draft-ietf-nvo3-arch-07: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-nvo3-arch/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Two tiny comments: - Call section 4.5 "Virtual Access Point (VAP)" instead of only "VAP" - I don't really understand this: "As is the case for L2VPN, there is a client/server relationship between the overlay and underlay networks..." How do the terms client and server help me here? More general: I was hoping to find a discussion on how existing protocols would be applicable to the three needed control protocols. Also do these three protocols need to be three different protocols or could all three cases potentially be covered by the same protocol (because the protocol mechanisms are the same and maybe even sometimes the same information needs to be exchanged)? _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
