Hi Jingrong and Arjun I believe what Daren is pointing out is that section 4.3.1 is referencing RFC 8200 for next header processing. Since that is stated in the beginning of section 4 and pertains to all sub sections I believe that would suffice. For SRv6 PGM draft I agree section 4 needs updating. I think that got clipped in Darens post.
4.3.1 <https://tools.ietf.org/html/rfc8754#section-4.3.1>. FIB Entry Is a Locally Instantiated SRv6 SID This document and section define a single SRv6 SID. Future documents may define additional SRv6 SIDs. In such a case, the entire content of this section will be defined in that document. If the FIB entry represents a locally instantiated SRv6 SID, process the next header chain of the IPv6 header as defined in Section 4 of [RFC8200] <https://tools.ietf.org/html/rfc8200#section-4>. Section 4.3.1.1 <https://tools.ietf.org/html/rfc8754#section-4.3.1.1> describes how to process an SRH; Section 4.3.1.2 <https://tools.ietf.org/html/rfc8754#section-4.3.1.2> describes how to process an upper-layer header or the absence of a Next Header. Kind Regards Gyan On Mon, Jun 15, 2020 at 12:21 PM Darren Dukes (ddukes) <ddukes= 40cisco....@dmarc.ietf.org> wrote: > Hello Aijun. > > No update to rfc8754 is necessary. Rfc8754 was written so new sids can be > defined in other documents independently. > > section 4.3.1 says: > > This document and section define a single SRv6 SID. Future documents > may define additional SRv6 SIDs. In such a case, the entire content > of this section will be defined in that document. > > > > Thanks > Darren > (Written on mobile) > > ------------------------------ > *From:* ipv6 <ipv6-boun...@ietf.org> on behalf of Aijun Wang < > wang...@chinatelecom.cn> > *Sent:* Sunday, June 14, 2020 10:15 PM > *To:* i...@ietf.org; spring@ietf.org > *Subject:* About the upper layer header processing in RFC8754(SRH) > > > Hi, Folks: > > RFC8754(SRH) section 4.3.1.2( > https://tools..ietf.org/html/rfc8754#section-4.3.1.2 > <https://tools.ietf.org/html/rfc8754#section-4.3.1.2>) describes the > process of upper layer header as the followings: > > IF (Upper-layer Header is IPv4 or IPv6) and > > local configuration permits { > > Perform IPv6 decapsulation > > Resubmit the decapsulated packet to the IPv4 or IPv6 module > > } > > ELSE { > > …… > > } > > And in network programming draft section 9.1( > https://datatracker.ietf.org/doc/html/draft-ietf-spring-srv6-network-programming-15#section-9.1), > one new Ethernet Next Header Type(143) is proposed. > > > > Although the detail process of this new next header are described in the > network program draft, does it need to update the section 4.3.1.2 of > RFC8754 to reflect the process of new header type(143)? > > > > Best Regards > > > > Aijun Wang > > China Telecom > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > i...@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
