Robert, I fully agree with you that RFC 8200 does not prevent a node that owns the destination address of the IPv6 header to insert EH. However, RFCV 8200 recommends (?) not to have more than one EH header of any type (excluding the Destination Options header that can occur no more than twice – once before the Routing header and once again – before the upper layer header). I.e., two Routing Headers (of any type) in the same packet are, if not prohibited, then, at least, not recommended.
Do I miss something? Regards, Sasha Office: +972-39266302 Cell: +972-549266302 Email: alexander.vainsht...@ecitele.com From: spring <spring-boun...@ietf.org> On Behalf Of Robert Raszuk Sent: Thursday, September 5, 2019 11:29 AM To: Fernando Gont <fg...@si6networks.com> Cc: Ron Bonica <rbonica=40juniper....@dmarc.ietf.org>; spring@ietf.org; 6...@ietf.org; Ole Troan <otr...@employees.org>; Suresh Krishnan <suresh.krish...@gmail.com>; draft-voyer-6man-extension-header-insertion <draft-voyer-6man-extension-header-insert...@ietf.org>; draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programm...@ietf.org> Subject: Re: [spring] Question about SRv6 Insert function Hi Fernando, If folks want to do EH insertion, the #1 step is to publish a document that updates RFC8200 such that the "EHs must not be inserted..." is replaced with something else or eliminated. I have very basic question to close this debate. Is IP encapsulation of the packet allowed by IPv6 specs or not ? If it is I see no issue with any documents you quote since when I add a new IPv6 header I can add any field to it. Moreover when I see myself as destination address of the packet RFC8200 verbatim allows to add, delete or modify EHs. I hope you agree with it. If IP encapsulation is forbidden by IPv6 RFCs please provide a quote and ref. Many thx, R. ___________________________________________________________________________ This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof. ___________________________________________________________________________
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
