Thanks for addressing my comments Jorge. Paul
Sent using a virtual keyboard on a phone > On Apr 28, 2023, at 10:28, Jorge Rabadan (Nokia) <[email protected]> > wrote: > > > Hi Paul, > > Thanks you very much for reviewing. > Version 06 addresses your comments. > > Please see in-line. > > Thx > Jorge > > From: Paul Wouters via Datatracker <[email protected]> > Date: Thursday, April 27, 2023 at 11:44 AM > To: The IESG <[email protected]> > Cc: [email protected] > <[email protected]>, [email protected] > <[email protected]>, [email protected] <[email protected]>, Sam Aldrin > <[email protected]>, [email protected] <[email protected]> > Subject: Paul Wouters' No Objection on draft-ietf-nvo3-evpn-applicability-05: > (with COMMENT) > > > CAUTION: This is an external email. Please be very careful when clicking > links or opening attachments. See the URL nok.it/ext for additional > information. > > > > Paul Wouters has entered the following ballot position for > draft-ietf-nvo3-evpn-applicability-05: 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/about/groups/iesg/statements/handling-ballot-positions/ > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-nvo3-evpn-applicability/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Abstract: > > I find the "Conclusion" section (with the word 'justifies' replaced > with 'documents') a clearer Abstract of the document than the > current Abstract. Maybe move the Conclusion as Abstract, and move > some technical details of the current Abstract to the Introduction? > > [jorge] That makes sense. I removed the conclusions section and changed the > abstract to: > > Ethernet Virtual Private Network (EVPN) provides a unified control-plane that > solves the Network Virtualization Edge (NVE) auto-discovery, tenant MAC/IP > dissemination and advanced features required by Network Virtualization Over > Layer-3 (NVO3) networks. EVPN is a scalable solution for NVO3 networks and > keeps the independence of the underlay IP Fabric, i.e. there is no need to > enable PIM in the underlay network and maintain multicast states for tenant > Broadcast Domains. This document describes the use of EVPN for NVO3 networks, > discusses its applicability to basic Layer-2 and Layer-3 connectivity > requirements, as well as advanced features such as MAC-mobility, MAC > Protection and Loop Protection, multi-homing, Data Center Interconnect (DCI) > and much more. No new EVPN procedures are introduced. > > Section 1: > > TOR/Leaf switches > > I had to follow the link a few sentences down to RFC 7365 to realize > TOR here does not mean Tor Onion Routing but Top of Rack switch. > > RFC 7365 uses "ToR" and not "TOR" as well. So maybe expand and fix > the capitalization. > > [jorge] fixed > > > > Section 2: > > The terminology is listed alphabetically, but some items are referred > in items before they are explained. It might be better to re-order > them. But perhaps not - me as a newbie in this space didn't know any, > but perhaps people familiar with terms find this sorting method easier > to use when reading the document. > > [jorge] The section in version 06 is ordered alphabetically (it’s done > properly this time), as discussed with John during his review. > > > > > NVO3 tunnels or simply Overlay tunnels will be used interchangeably > > Why not stick to one term for simplicity ? > > [jorge] good point. I changed it to just use NVO3 tunnels all the time. > > > >
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
