Re: [spring] Question about SRv6 Insert function

Fernando Gont <fgont@si6networks.com> Sat, 07 September 2019 22:40 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 A119112018D; Sat, 7 Sep 2019 15:40:52 -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 7m48nWw-O2iS; Sat, 7 Sep 2019 15:40:51 -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 2E713120145; Sat, 7 Sep 2019 15:40:51 -0700 (PDT)
Received: from [192.168.1.14] (ppp-94-69-228-20.home.otenet.gr [94.69.228.20]) (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 4B5C386355; Sun, 8 Sep 2019 00:40:49 +0200 (CEST)
To: Robert Raszuk <robert@raszuk.net>
Cc: Ole Troan <otroan@employees.org>, "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@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> <b83a7060-0517-c6ad-f6b0-bc9e61e4667f@si6networks.com> <01D79129-8CAC-49C3-A7EC-C37F935B11B1@cisco.com> <eb05ad28-4fb1-c438-4655-6c5a0455b029@si6networks.com> <BB439981-F078-4833-98BF-7779E1D03930@cisco.com> <f27d975b-b48d-377b-9a7d-aba63b5c77e7@si6networks.com> <DM6PR11MB260302DC79D7E7BF6367B74AC8BA0@DM6PR11MB2603.namprd11.prod.outlook.com> <1f697fd6-dc77-b8dd-15fb-be23b3c296a4@si6networks.com> <2C6D1E3F-5271-4516-94E6-F08974501DD0@employees.org> <0ac79226-906b-6c11-5c6b-7cb7b8bcc336@si6networks.com> <CAOj+MMGjP9+OoarT12G4X_qhB3dmOa76mxTj7dOcQxEAVQdQzA@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <98ffe27a-37de-cf41-156b-5b0fc2214675@si6networks.com>
Date: Sun, 8 Sep 2019 01:40:43 +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: <CAOj+MMGjP9+OoarT12G4X_qhB3dmOa76mxTj7dOcQxEAVQdQzA@mail.gmail.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/yeGhdCb-WqcWtChtDrjfBRNfRk8>
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: Sat, 07 Sep 2019 22:40:53 -0000

On 8/9/19 01:23, Robert Raszuk wrote:
[...]
> 
>     4) I expect that, as co-chair, you'd agree with me that allowing EH
>     insertion in IPv6 is a major modification/addition. According to our
>     charter, we don't seem allowed to do that:
> 
> 
> Do you need a new charter to be allowed to standardize extensions to
> IPv6 header and their operations like SRH ? That is not what AD and
> chairs said and one would assume they know better how to guide the work
> in the group. 

WGs do have a charter, which specifies what the WG does. That's why, in
the extreme case, 6man doesn't do TCP stuff. Charters are not casted
into stone, though.



> Because if this is really the case - we should indeed stop any efforts
> in this regard and perhaps seriously start considering a new WG
> formation to work on new IP header design perhaps even backwards
> compatible with current IPv6 "legacy". 

Besides having my own personal opinion, I'd say that no matter the path
you want to follow (or need to follow) to pursue this, you really should
have a much stronger and complete document than the current proposal.



> In the meantime - if what you communicate is true WG consensus -

I'm not entitled to communicate things for the wg. I made a comment
about the charter -- a side comment that came up while noting that
EH-insertion does *not* seem to be a minor addition/modification to IPv6.


> proposals for addition of EH to IPv4 become not only nice to have, but
> in fact very useful to have. 

I'm not sure I follow...

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