IETF Logo Mail Archive

Re: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call(Internet mail)

oliverxu(许锋) <oliverxu@tencent.com> Wed, 08 May 2019 00:59 UTC

Return-Path: <oliverxu@tencent.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46425120099 for <idr@ietfa.amsl.com>; Tue, 7 May 2019 17:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.92
X-Spam-Level:
X-Spam-Status: No, score=-0.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 5r_u1ZKMnYOr for <idr@ietfa.amsl.com>; Tue, 7 May 2019 17:59:42 -0700 (PDT)
Received: from mail2.tencent.com (mail2.tencent.com [163.177.67.195]) by ietfa.amsl.com (Postfix) with ESMTP id 00CE7120073 for <idr@ietf.org>; Tue, 7 May 2019 17:59:31 -0700 (PDT)
Received: from EXHUB-SZMail01.tencent.com (unknown [10.14.6.21]) by mail2.tencent.com (Postfix) with ESMTP id 628E08E877; Wed, 8 May 2019 08:59:30 +0800 (CST)
Received: from EX-SZ013.tencent.com (10.28.6.37) by EXHUB-SZMail01.tencent.com (10.14.6.21) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 8 May 2019 08:59:29 +0800
Received: from EX-SZ001.tencent.com (10.28.6.13) by EX-SZ013.tencent.com (10.28.6.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 8 May 2019 08:59:29 +0800
Received: from EX-SZ001.tencent.com ([fe80::5c7a:169a:d419:87ee]) by EX-SZ001.tencent.com ([fe80::5c7a:169a:d419:87ee%3]) with mapi id 15.01.1713.004; Wed, 8 May 2019 08:59:29 +0800
From: "oliverxu(许锋)" <oliverxu@tencent.com>
To: "idr@ietf.org" <idr@ietf.org>, "shares@ndzh.com" <shares@ndzh.com>
Thread-Topic: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call(Internet mail)
Thread-Index: AdT17jAMyz+sjMM6SRqyoxzf6xKAMQOlnl9wABRVvYAAGNI6AA==
Date: Wed, 08 May 2019 00:59:29 +0000
Message-ID: <81DF304E-1F1D-4E92-B62B-ACD7E8AC68F7@tencent.com>
References: <013301d4f5ef$b1b51310$151f3930$@ndzh.com> <19AB2A007F56DB4E8257F949A2FB9858E5B84285@NKGEML515-MBX.china.huawei.com> <C01B0098369B2D4391851938DA6700B7134E40E1@DGGEML532-MBX.china.huawei.com>
In-Reply-To: <C01B0098369B2D4391851938DA6700B7134E40E1@DGGEML532-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.14.87.228]
Content-Type: multipart/alternative; boundary="_000_81DF304E1F1D4E92B62BACD7E8AC68F7tencentcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/LofVntxcmXKOJu5e4Ay6f7n0Wd8>
Subject: Re: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call(Internet mail)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2019 00:59:49 -0000

Hi experts,

Support adoption. For yang/oc-yang, It’s too long time to wait the standardization process。


Oliver.


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Thursday, April 18, 2019 10:05 PM
To: idr@ietf.org<mailto:idr@ietf.org>
Subject: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call

This begins a 2 week WG Adoption call for draft-wu-idr-bgp-segment-allocation-ext-02.txt.  You can access the draft at:

https://datatracker.ietf.org/doc/draft-wu-idr-bgp-segment-allocation-ext/

In your comments, consider:


  1.  Does this draft mechanisms for  extending BGP-LS to provide IDs for allocation provide a beneficial addition to BGP mechanisms for segment routing?
  2.  Is the mechanism well-formed enough to adopted as a WG draft?
  3.  Do you see any problems with using these IDs for flow redirection?
  4.  Do you support extending BGP-LS?
  5.  Should we provide an early allocation for this technology?
  6.  Do you know of any early implementations?

By answering these questions during WG Adoption call, you will help John and I determine what issues need to be considered prior to finalizing this WG draft.    Your answer will help us increase the speed of processing BGP-LS drafts.

If enough people indicate that they wish an early allocation upon adoption, I will then send this early allocation to Alvaro.

Sue Hares

PS – I’m trying new methods of WG adoption calls to help speed up the process in IDR WG.   Please send any thoughts on these new methods to me or John.

v2.23.0 | Report a Bug | By Email