Hi, Darren:
RFC8754 should defines the general processing rule for the SRH, not defining any kind of SID. Different kinds of SID behavior should be defined in other documents, for example, the network programming draft etc. I think https://tools.ietf.org/html/rfc8754#section-4.3.1.1( for SRH) covers all the processing rules that defined in https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-14.. The description in https://tools.ietf.org/html/rfc8754#section-4.3.1.2 (for Upper Layer)should also cover all the situations that defined in https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-14, and the situations defined in any other related drafts. And, if your statement is true, what kind of SID behavior is defined in this section then? What is its relationship with the different SID behaviors described in the network program draft? Best Regards Aijun Wang China Telecom 发件人: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] 代表 Darren Dukes (ddukes) 发送时间: 2020年6月16日 10:17 收件人: Ron Bonica <rbonica=40juniper....@dmarc.ietf.org>; Aijun Wang <wang...@chinatelecom.cn>; i...@ietf.org; spring@ietf.org 主题: Re: About the upper layer header processing in RFC8754(SRH) Hi Ron. The SID described in RFC8754 is fully described there. The SIDs in draft-ietf-spring-SRv6-network-programming are fully defined in that document. Darren _____ From: Ron Bonica <rbonica=40juniper....@dmarc.ietf.org <mailto:rbonica=40juniper....@dmarc.ietf.org> > Sent: Monday, June 15, 2020 3:08:12 PM To: Darren Dukes (ddukes) <ddu...@cisco.com <mailto:ddu...@cisco.com> >; Aijun Wang <wang...@chinatelecom.cn <mailto:wang...@chinatelecom.cn> >; i...@ietf.org <mailto:i...@ietf.org> <i...@ietf.org <mailto:i...@ietf.org> >; spring@ietf.org <mailto:spring@ietf.org> <spring@ietf.org <mailto:spring@ietf.org> > Subject: RE: About the upper layer header processing in RFC8754(SRH) Darren, Does the SID described in RFC 8754 represent any of the SIDs in the Network Programming Draft? In any other document? Ron Juniper Business Use Only From: ipv6 <ipv6-boun...@ietf.org <mailto:ipv6-boun...@ietf.org> > On Behalf Of Darren Dukes (ddukes) Sent: Monday, June 15, 2020 12:21 PM To: Aijun Wang <wang...@chinatelecom.cn <mailto:wang...@chinatelecom.cn> >; i...@ietf.org <mailto:i...@ietf.org> ; spring@ietf.org <mailto:spring@ietf.org> Subject: Re: About the upper layer header processing in RFC8754(SRH) [External Email. Be cautious of content] 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 <mailto:ipv6-boun...@ietf.org> > on behalf of Aijun Wang <wang...@chinatelecom.cn <mailto:wang...@chinatelecom.cn> > Sent: Sunday, June 14, 2020 10:15 PM To: i...@ietf.org <mailto:i...@ietf.org> ; spring@ietf.org <mailto: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://urldefense.com/v3/__https:/tools.ietf.org/html/rfc8754*section-4..3. 1.2__;Iw!!NEt6yMaO-gk!W4_ZbJ6IaphycWPj08UYd8k9IPlcBP_h6HEasypDyifP-5j3jjAVQJ YjvxKIgrBz$> ) 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-pro gramming-15#section-9.1 <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-ietf -spring-srv6-network-programming-15*section-9.1__;Iw!!NEt6yMaO-gk!W4_ZbJ6Iap hycWPj08UYd8k9IPlcBP_h6HEasypDyifP-5j3jjAVQJYjv0iiulaO$> ), 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
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
