Hi Ron,

Your guess is wrong. Please read the sentence right after the one you quote.

   "The effective next-header (ENH) is the next-header field of the IP
   header when no SRH is present, or is the next-header field of the
   last SRH.

   In this version of the document, we assume that there are no other
   extension headers than the SRH.  These will be lifted in future
   versions of the document."

As said in the note, as part of the work on this draft we will update the 
pseudocodes to get better alignment with SRH draft, removing the stated 
limitations. For simplicity we did not add them in previous revisions of the 
draft.

Thanks,
Pablo.

-----Original Message-----
From: ipv6 <[email protected]> on behalf of Ron Bonica 
<[email protected]>
Date: Monday, 6 May 2019 at 03:05
To: SPRING WG <[email protected]>, 6man WG <[email protected]>
Subject: SRv6 Network Programming: More Headers

    Folks,
    
    In draft-ietf-spring-srv6-network-programming, can a packet that is 
destined for an End.DX4 SID contain a Fragment header? An Authentication 
header? An Encapsulating Security Payload header? A Destination Options header?
    
    My initial guess is that it cannot. According to the draft:
    
    "The effective next-header (ENH) is the next-header field of the IP header 
when no SRH is present, or is the next-header field of the last SRH"
    
    Also, according to Section 4.9 of the draft, the packet will be dropped if 
the Effective Next Header is not equal to 4 (IPv4).
    
    Do I have this right?
    
                                                           Ron
    
    Juniper Internal
    
    --------------------------------------------------------------------
    IETF IPv6 working group mailing list
    [email protected]
    Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
    --------------------------------------------------------------------
    


_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring

Reply via email to