Hi Jingrong. The processing of protocol type 59 “no next header” is intentionally defined to drop in section 4.3.1.2 of draft-ietf-6man-segment-routing-header-18.
4.3.1 says: This document, and section, defines a single SRv6 SID called END. Future documents may define additional SRv6 SIDs. In which case, the entire content of this section will be defined in that document. The SRv6 network programming draft does define other SIDs that would replace the text in 4.3.1 and its subsections. This is accomplished for L2VPN with the END.DT2*/END.DX2* SID types. Darren On Apr 15, 2019, at 4:09 AM, Xiejingrong <[email protected]<mailto:[email protected]>> wrote: Hello authors, Section 4.3.1.2. Upper-layer Header or No Next Header of <draft-ietf-6man-segment-routing-header-18> doesn’t include the No Next Header case ? The SRv6-Network-programming relies heavily on the No-next-header in SRv6-L2VPN cases. Thanks Jingrong -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected]<mailto:[email protected]> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
