Re: [spring] Spirit and Letter of the Law (was: Question about SRv6 Insert function)

Fernando Gont <fgont@si6networks.com> Thu, 05 September 2019 19:00 UTC

Return-Path: <fgont@si6networks.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 30284120C89; Thu, 5 Sep 2019 12:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 jKJz2xztfpRt; Thu, 5 Sep 2019 12:00:48 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AD0D120C4B; Thu, 5 Sep 2019 12:00:48 -0700 (PDT)
Received: from [192.168.1.12] (ppp-94-69-228-80.home.otenet.gr [94.69.228.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 0B4648627C; Thu, 5 Sep 2019 21:00:43 +0200 (CEST)
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Cc: "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>, Ole Troan <otroan@employees.org>, Suresh Krishnan <suresh.krishnan@gmail.com>, Robert Raszuk <rraszuk@gmail.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, Robert Raszuk <robert@raszuk.net>
References: <BYAPR05MB54637FEAE1518F83977D274FAEB80@BYAPR05MB5463.namprd05.prod.outlook.com> <538732E2-915B-4952-A439-F4678FCC21B2@employees.org> <4c6b2456-db05-0771-5b98-bfd9f07b220b@si6networks.com> <34AB9F0F-614B-45C2-BD84-7DD53A1D5188@employees.org> <ea9557e5-9025-db78-8862-18454dd549c3@joelhalpern.com> <5200FFA0-E2F1-4491-8D06-0DC6BF87F77A@employees.org> <cdc190f4-315f-f716-951c-6d4ba1f4888d@si6networks.com> <CA+b+ERn6KMGCboERKOMeKAwM3y=1p=sc8j2LnEGYa7h5mz_xxw@mail.gmail.com> <a9a0c0a1-a7fa-835c-1347-95a9f5ca6d1f@si6networks.com> <CAOj+MMFmMGGTmtgf+n3cdHeh4+oDR=z6++YmAEjb_=jtOtCvbw@mail.gmail.com> <d6a55d41-a37f-1c32-20c6-bcbc2a9226b6@si6networks.com> <AM0PR03MB3828B2F0E9A5095A34808AE39DBB0@AM0PR03MB3828.eurprd03.prod.outlook.com>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <73a40138-33f4-73e3-40b8-2578ab7744e2@si6networks.com>
Date: Thu, 05 Sep 2019 19:06:44 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <AM0PR03MB3828B2F0E9A5095A34808AE39DBB0@AM0PR03MB3828.eurprd03.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/UtIzles4GrlPE5g8veUxMNGMvVs>
Subject: Re: [spring] Spirit and Letter of the Law (was: 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, 05 Sep 2019 19:00:58 -0000

On 5/9/19 18:42, Alexander Vainshtein wrote:
> Fernando,
> 
> With regard to the last statement in your email "If you create a new
> packet, and you put your own address in the SA of the packet, and
> encapsulate what you received in the IPv6 payload, you're free to
> generate as many EHs as you wish", do you see the need to comply with
> the 8200 recommendation that says
> 
>  
> 
> <quote>
> 
>    Each extension header should occur at most once, except for the
> 
>    Destination Options header, which should occur at most twice (once
> 
>    before a Routing header and once before the upper-layer header).
> 
> <end quote>

Of course. I was mostly meaning that if you encapsulate, then the
resulting packet can contain an EH, because you'd not be *inserting* and
EH in an existing packet, but rather creating a brand new one.

Of course, the rest of RFC8200 still applies.

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492