Subject: [spring] H.Encaps pseudocode (was Re: Question about SRv6 Insert function)

From: "Pablo Camarillo (pcamaril)" <[email-masked]>
Date: Fri, 20 Dec 2019 17:36:36 +0000

I will update it to P1' and P2' as suggested. Thank you.

Happy Holidays,
Pablo.

-----Original Message-----
From: spring <[email-masked]> on behalf of Alexandre Petrescu <[email-masked]>
Date: Thursday, 19 December 2019 at 15:09
To: "[email-masked]" <[email-masked]>
Subject: Re: [spring] Question about SRv6 Insert function

    Le 19/12/2019 à 14:33, Alexandre Petrescu a écrit :
    > 
    > 
    > Le 19/12/2019 à 12:52, Pablo Camarillo (pcamaril) a écrit :
    [...]
    >>    S05.   Decrement inner Hop Limit or TTL
    >>    S06.   Submit the packet to the IPv6 module for transmission to S1
    >>
    >>    After the H.Encaps behavior, P1 and P2 respectively look like:
    
    P1 and P2 respectively dont look like that.  They are encapsulated.
    These are new packets that are created.
    
    >>    - (T, S1) (S3, S2, S1; SL=2) (A, B2)
    >>
    >>    - (T, S1) (S3, S2, S1; SL=2) (A, B2) (B3, B2, B1; SL=1)
    
    The P1 and P2 are indeed not modified, they are encapsulated.  But there 
    are new packets that are shown there: P1` and P2` if you wish.
    
    After encapsulation one couldnt say that a packet looks like before.
    
    An encapsulated packet does not know what's happening to itself, and has 
    no idea about its encapsulating header.
    
    Alex
    
    _______________________________________________
    spring mailing list
    [email-masked]
    https://www.ietf.org/mailman/listinfo/spring