IETF Logo Mail Archive

Re: [spring] Question about SRv6 Insert function

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 19 December 2019 14:07 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9094D120810 for <spring@ietfa.amsl.com>; Thu, 19 Dec 2019 06:07:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VsaF9MovZzYe for <spring@ietfa.amsl.com>; Thu, 19 Dec 2019 06:07:36 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C773120818 for <spring@ietf.org>; Thu, 19 Dec 2019 06:07:36 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id xBJE7XQA003613 for <spring@ietf.org>; Thu, 19 Dec 2019 15:07:33 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 20B942042CB for <spring@ietf.org>; Thu, 19 Dec 2019 15:07:33 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 16BFF2021E0 for <spring@ietf.org>; Thu, 19 Dec 2019 15:07:33 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id xBJE7X9u006438 for <spring@ietf.org>; Thu, 19 Dec 2019 15:07:33 +0100
To: spring@ietf.org
References: <HK0PR03MB3970C6DCC635E7CD802D65FDFCBD0@HK0PR03MB3970.apcprd03.prod.outlook.com> <3e31873a-278a-2154-0e71-4d820bba323d@gont.com.ar> <4012D854-2F10-4476-951D-FFFE73C5083C@gmail.com> <cb2f56f8-acdc-d68d-0878-9609cb3d7b1b@gont.com.ar> <28214_1567694772_5D711FB4_28214_238_1_53C29892C857584299CBF5D05346208A48BFA9F3@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <129bbb32-0f14-b799-430c-8f76fb6b1279@gont.com.ar> <1824_1575998223_5DEFD30F_1824_112_1_53C29892C857584299CBF5D05346208A48D24EBD@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <4384c08a-65f5-dbfb-85c7-8365feba9662@gmail.com> <11783_1576056453_5DF0B685_11783_221_1_53C29892C857584299CBF5D05346208A48D261E9@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <260f6f3c-e3cc-e174-1782-456df7cded86@gmail.com> <8683D672-1A59-4253-AC46-14DD2D8C8B14@cisco.com> <35c4119f-1d46-0220-d7e4-168b27beb782@gmail.com> <MWHPR11MB1374842A5AFCB0EFD5AECFA0C9530@MWHPR11MB1374.namprd11.prod.outlook.com> <3b78c6b0-1153-b8ad-6b97-84c91ee915c5@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <0c241920-36e7-2198-e956-f41f9251a7a4@gmail.com>
Date: Thu, 19 Dec 2019 15:07:32 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0
MIME-Version: 1.0
In-Reply-To: <3b78c6b0-1153-b8ad-6b97-84c91ee915c5@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/Ak1FWCGePWXPmnLwAHYuSXL70I4>
Subject: Re: [spring] Question about SRv6 Insert function
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Dec 2019 14:07:41 -0000


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

v2.2.0 | Report a Bug | By Email