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

"Susan Hares" <shares@ndzh.com> Thu, 18 April 2019 14:04 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8302E120343 for <idr@ietfa.amsl.com>; Thu, 18 Apr 2019 07:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id aoO6gS_MacHX for <idr@ietfa.amsl.com>; Thu, 18 Apr 2019 07:04:56 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26D9812014A for <idr@ietf.org>; Thu, 18 Apr 2019 07:04:55 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
Date: Thu, 18 Apr 2019 10:04:51 -0400
Message-ID: <013301d4f5ef$b1b51310$151f3930$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0134_01D4F5CE.2AA37310"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdT17jAMyz+sjMM6SRqyoxzf6xKAMQ==
Content-Language: en-us
X-Antivirus: AVG (VPS 190418-0, 04/18/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/5TSSHTa0e3E-q4IrJs1oL7ZZ5zE>
Subject: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call
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: Thu, 18 Apr 2019 14:04:59 -0000

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




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

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


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