On 5/9/19 18:31, Robert Raszuk wrote: > Fernando, > > I am taking you extremely seriously ! In fact some of your emails make > me even worried. > > You say in one email that encapsulation is allowed and that the event of > encapsulation is the same as sourcing. > > So please notice text in network programming draft which says: > > This document defines the SRv6 Network Programming concept and aims > at standardizing the main segment routing functions to enable the > creation of interoperable *overlays* > * > * > I am not sure what is your definition of an overlay is but to me the > most common way to create an overlay of any sort is via encapsulation. > > I would not mix the use cases of net programming which apparently > happened and generated so much confusion around. Sure it could be used > also without encapsulation, but does it make it immediately illegal ?
I'm lost here. Again: * draft-ietf-spring-srv6-network-programming has a normative reference to draft-voyer-6man-extension-header-insertion * draft-voyer-6man-extension-header-insertion is about EH insertion * EH insertion is forbidden by RFC8200 We have wasted way too much time and energy with all the methafores and curious interpretations of standards by folks pushing and/or supporting EH insertion, really. -- Fernando Gont SI6 Networks e-mail: fg...@si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492 _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
