IETF Logo Mail Archive

Re: [spring] Question about SRv6 Insert function

Fernando Gont <fgont@si6networks.com> Sat, 07 September 2019 02:54 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC8B6120E25; Fri, 6 Sep 2019 19:54:47 -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, 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 xk-AJLJ6bUq2; Fri, 6 Sep 2019 19:54:45 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F206120815; Fri, 6 Sep 2019 19:54:44 -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 4B8ED82DAD; Sat, 7 Sep 2019 04:54:40 +0200 (CEST)
Subject: Re: [spring] Question about SRv6 Insert function
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> <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>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <1f697fd6-dc77-b8dd-15fb-be23b3c296a4@si6networks.com>
Date: Sat, 07 Sep 2019 05:18:29 +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: <DM6PR11MB260302DC79D7E7BF6367B74AC8BA0@DM6PR11MB2603.namprd11.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/ipv6/nX8wm3L5bR0u62cUoz_VMLmaFWI>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Sep 2019 02:54:48 -0000

On 6/9/19 03:56, Darren Dukes (ddukes) wrote:
> Hi Fernando. 
> 
> The takeaway I attempted to highlight is that there is in fact agreement
> between 6man and spring on how to proceed, and we are proceeding as
> agreed to work on the relevant documents.

I don't really know what the agreement is, other than the implicit
agreement that if you're considering violating an IPv6 standard, you
should come to 6man and do a Std Track document that updates the
relevant standard...

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

v2.23.0 | Report a Bug | By Email