Hi, Greg, I was not in London, but if you do not mind, I will piggy back on this email to ask a couple of key questions that I still cannot figure out:
1. What is the objective of an OOAM, or what is purpose for adding an indirection, a shim, a nested header and additional lookup, to a bunch of encapsulations? The Abstract in draft-ooamdt-rtgwg-ooam-header says “to ensure that OOAM control packets are in-band with user traffic and de-multiplex OOAM protocols.” But frankly I cannot make sense of that sentence. The same holds equally true without OOAM and this will not change the behavior of active OAM methods. Imagine the performance of BFD buried under redundant fields to parse. 2. Could you add an Implementation Status section [RFC 7942] to this document? Thanks, Carlos. On Mar 29, 2018, at 1:32 AM, Greg Mirsky <[email protected]<mailto:[email protected]>> wrote: Hi Ignas, another well-captured discussion, thank you. Few notes: * I believe that in discussion of OOAM Header "?/Cisco" should be Frank Brockners * would you consider splitting comments and responses with <CR><LF> to ease readability? Kind regards, Greg On Thu, Mar 29, 2018 at 4:38 AM, Ignas Bagdonas <[email protected]<mailto:[email protected]>> wrote: Working group, Draft minutes for IETF101 NVO3 WG meeting have been posted at the meeting materials page. https://datatracker.ietf.org/doc/minutes-101-nvo3/ Please take a look and provide any corrections if needed. Thank you. Ignas _______________________________________________ nvo3 mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
