Re: [spring] Question about SRv6 Insert function

Fernando Gont <fgont@si6networks.com> Thu, 05 September 2019 20:02 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 17643120B2F; Thu, 5 Sep 2019 13:02:10 -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=unavailable 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 mp2XP3oxH_Wt; Thu, 5 Sep 2019 13:02:07 -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 0E490120B1F; Thu, 5 Sep 2019 13:02:07 -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 70FD086268; Thu, 5 Sep 2019 22:02:02 +0200 (CEST)
To: "Darren Dukes (ddukes)" <ddukes@cisco.com>
Cc: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, Fernando Gont <fernando@gont.com.ar>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>, Suresh Krishnan <suresh.krishnan@gmail.com>, draft-voyer-6man-extension-header-insertion <draft-voyer-6man-extension-header-insertion@ietf.org>, li zhenqiang <li_zhenqiang@hotmail.com>, draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
References: <HK0PR03MB3970C6DCC635E7CD802D65FDFCBD0@HK0PR03MB3970.apcprd03.prod.outlook.com> <BYAPR05MB54636A2332FED916A26A6F14AEBD0@BYAPR05MB5463.namprd05.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> <b83a7060-0517-c6ad-f6b0-bc9e61e4667f@si6networks.com> <01D79129-8CAC-49C3-A7EC-C37F935B11B1@cisco.com>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <eb05ad28-4fb1-c438-4655-6c5a0455b029@si6networks.com>
Date: Thu, 5 Sep 2019 23:01:42 +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: <01D79129-8CAC-49C3-A7EC-C37F935B11B1@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/Qf43PDoSd3ZTz4uV1GEdRHvugdQ>
X-Mailman-Approved-At: Thu, 05 Sep 2019 19:06:41 -0700
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, 05 Sep 2019 20:02:10 -0000

On 5/9/19 22:52, Darren Dukes (ddukes) wrote:
> Hey Fernando, since you’re lost, here are some more waypoints to help
> you find your way ;)
> 
> - draft-ietf-spring-srv6-network-programming mentions SRH insertion in
> only 2 of 39 SID behaviors - i.e. it’s a small part of the draft, and
> all insert variants have an encapsulation variant defined.

I don't see how this changes the discussion here. Are you suggesting
that EH insertion can be removed from the document and there would still
be value in pursuing the document?


> - At IETF 101, the 6man WG confirmed that SRH insertion must be worked
> on before draft-ietf-spring-srv6-network-programming can progress to RFC
> - i.e. there are not surprises anywhere.
> 
> - draft-ietf-spring-srv6-network-programming added a normative reference
> to draft-voyer-6man-extension-header-insertion to document that fact.

Among the possible options is that EH-insertion is never worked out. In
which case, what's the point of basing something on EH insertion when
the status quo is that EH insertion is not allowed, and there does not
seem to be any indication that that will change anytime soon?

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