RE: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Fri, 22 May 2020 15:21 UTC

Return-Path: <pengshuping@huawei.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 AE3513A0AD3; Fri, 22 May 2020 08:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 bfVMYytyG_k1; Fri, 22 May 2020 08:21:11 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 63CDE3A0AF7; Fri, 22 May 2020 08:21:11 -0700 (PDT)
Received: from lhreml718-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 94AC88578CF16CE00C62; Fri, 22 May 2020 16:21:08 +0100 (IST)
Received: from lhreml718-chm.china.huawei.com (10.201.108.69) by lhreml718-chm.china.huawei.com (10.201.108.69) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Fri, 22 May 2020 16:21:08 +0100
Received: from DGGEML406-HUB.china.huawei.com (10.3.17.50) by lhreml718-chm.china.huawei.com (10.201.108.69) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Fri, 22 May 2020 16:21:07 +0100
Received: from DGGEML532-MBX.china.huawei.com ([169.254.8.202]) by dggeml406-hub.china.huawei.com ([10.3.17.50]) with mapi id 14.03.0487.000; Fri, 22 May 2020 23:21:05 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>, "Bob Hinden" <bob.hinden@gmail.com>
CC: "spring@ietf.org" <spring@ietf.org>, 6man <6man@ietf.org>, Robert Raszuk <robert@raszuk.net>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>
Subject: RE: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH
Thread-Topic: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH
Thread-Index: AQHWL+b7sBPKmNB+RkCfzSC75r1PAaiy7ZiAgAAFfICAAUQToA==
Date: Fri, 22 May 2020 15:21:05 +0000
Message-ID: <4278D47A901B3041A737953BAA078ADE18F3D9C5@DGGEML532-MBX.china.huawei.com>
References: <9CF68CCE-B584-4648-84DA-F2DBEA94622D@cisco.com> <C7C2E1C43D652C4E9E49FE7517C236CB02A2C1AE@dggeml529-mbx.china.huawei.com> <DM6PR05MB6348A22A123AFA7E7345087BAEB70@DM6PR05MB6348.namprd05.prod.outlook.com> <MW3PR11MB457041A967A6BBDA1C7EF0FDC1B70@MW3PR11MB4570.namprd11.prod.outlook.com> <93a31c7f-a102-da59-d9a8-2585cd8e3c65@gmail.com> <MW3PR11MB4570B197EE00C5385DAEE138C1B40@MW3PR11MB4570.namprd11.prod.outlook.com> <5F062FA6-9E2D-46BB-A3D6-257D374D8F92@gmail.com> <MW3PR11MB4570485EEDBADEF3B193BB82C1B40@MW3PR11MB4570.namprd11.prod.outlook.com>
In-Reply-To: <MW3PR11MB4570485EEDBADEF3B193BB82C1B40@MW3PR11MB4570.namprd11.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.218.16]
Content-Type: multipart/alternative; boundary="_000_4278D47A901B3041A737953BAA078ADE18F3D9C5DGGEML532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/93M8nH2gr4uQLtXXZP1smXvYDA4>
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: Fri, 22 May 2020 15:21:15 -0000

The “mapping ID” indeed needs to be carefully explored, which may cause serious operational issue considering such a large number of local FIB entries imposed by CRH.

Shuping


From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Ketan Talaulikar (ketant)
Sent: Friday, May 22, 2020 11:53 AM
To: Bob Hinden <bob.hinden@gmail.com>
Cc: spring@ietf.org; 6man <6man@ietf.org>rg>; Robert Raszuk <robert@raszuk.net>et>; rtg-ads@ietf.org
Subject: RE: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH


Hi Bob,



Perhaps I will try to make my case to you (and everyone else here) … one last time.



This is how I've seen RH work being done in 6man until now (in a matter that fits its charter).



1) There is a WG (not 6man) that defines the problem statement, use-cases and architecture that requires RH

2) The 6man being the experts on IPv6 design, either take up the document that specifies that RH (or even if it is done in another WG, reviews it).



So 6man has always had work done in (1) to reference and lean upon when doing (2).



My argument of the shortcut in the case of this specific adoption is that we don't have (1).



It is not in 6man charter nor expertise to take up (1) because CRH is not purely IPv6 work. It is not meant for "Internet" but a specific "limited domain". The SIDs that it introduces is a new "mapping ID" concept. It is not an IPv6 address and neither it is MPLS. This is a Routing Header and part of a new Source Routing solution.



Therefore, without (1) being made available to 6man, I believe that working on (2) in 6man is to me a shortcutting of the IETF technical review process (specifically of the Routing area in this case) for a solution and does not provide the necessary reference for 6man to work on.



Why the rush?



I close my arguments.



Thanks,

Ketan



-----Original Message-----
From: Bob Hinden <bob.hinden@gmail.com<mailto:bob.hinden@gmail.com>>
Sent: 22 May 2020 09:03
To: Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>
Cc: Bob Hinden <bob.hinden@gmail.com<mailto:bob.hinden@gmail.com>>; Brian Carpenter <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>>; Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>; Chengli (Cheng Li) <c.l@huawei.com<mailto:c.l@huawei.com>>; Zafar Ali (zali) <zali@cisco.com<mailto:zali@cisco.com>>; Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>>; spring@ietf.org<mailto:spring@ietf.org>; 6man <6man@ietf.org<mailto:6man@ietf.org>>
Subject: Re: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH



Ketan,



> On May 21, 2020, at 8:12 PM, Ketan Talaulikar (ketant) <ketant=40cisco.com@dmarc.ietf.org<mailto:ketant=40cisco.com@dmarc.ietf.org>> wrote:

>

> Hi Brian,

>

> Please see my previous response to your comments.

>

> My argument is not legalistic. I am not as experience in IETF work as you and Bob are. But what I understand is that the reason why we have these "legal" process of charters and BoF is to enable a proper technical discussion with the right context and details of the proposal presented for review of the community.

>

> I do not see how shortcutting them helps anyone and I wonder why it is being done in this case?



There is no short cutting here.  The adoption call is to determine if there is interest in the w.g. to take this work into 6man.   If it becomes a w.g. draft, then the w.g. is responsible to decide what happens next.



It’s a first step, it is not a decision to publish it.



Bob (w/ w.g. chair hat on)









>

> Thanks,

> Ketan

>

> -----Original Message-----

> From: Brian E Carpenter <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>>

> Sent: 22 May 2020 04:18

> To: Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>; Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>; Chengli (Cheng Li) <c.l@huawei.com<mailto:c.l@huawei.com>>; Zafar Ali (zali) <zali@cisco.com<mailto:zali@cisco.com>>; Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>>

> Cc: spring@ietf.org<mailto:spring@ietf.org>; 6man <6man@ietf.org<mailto:6man@ietf.org>>

> Subject: Re: CRH is back to the SPRING Use-Case - Re: Size of CR in CRH

>

> On 22-May-20 05:26, Ketan Talaulikar (ketant) wrote:

> ...> It is the 6man charter that precludes it from defining a new Source Routing solution..

>> “It is not chartered to develop major changes or additions to the IPv6 specifications.”

>

> If this addition was major, that would be true. But adding a new RH type is well within the scope of maintenance, IMHO. We have already done it quite recently.

>

> In any case, legalistic arguments about WG charters are really not how we should take technical decisions.

>

> Regards

>    Brian

>

>

> _______________________________________________

> spring mailing list

> spring@ietf.org<mailto:spring@ietf.org>

> https://www.ietf.org/mailman/listinfo/spring