Re: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]

"Susan Hares" <> Mon, 14 October 2019 18:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6DF3312004A; Mon, 14 Oct 2019 11:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 1.349
X-Spam-Level: *
X-Spam-Status: No, score=1.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.4, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id t60V3ButAWqg; Mon, 14 Oct 2019 11:12:38 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1B58D12000F; Mon, 14 Oct 2019 11:12:37 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: Susan Hares <>
To: 'idr wg' <>, 'SPRING WG List' <>
Date: Mon, 14 Oct 2019 14:12:34 -0400
Message-ID: <00f901d582ba$f474a230$dd5de690$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00FA_01D58299.6D630230"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdWCuk3YU0jOn/ygQ1+t1TuQqTQ3YA==
Content-Language: en-us
X-Antivirus: AVG (VPS 191012-6, 10/12/2019), Outbound message
X-Antivirus-Status: Not-Tested
Archived-At: <>
Subject: Re: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 14 Oct 2019 18:12:39 -0000

Greetings IDR and Spring WG


The WG Adoption for the two IDR drafts related to IDR received a level
support below the threshold to accept this draft into the IDR WG.  There
were no objection, but there was simply a low level of response. 


This 1 week extension to the Adoption call is to let the members of both the
IDR and SPRING WG comment on whether these drafts have matured enough to be
IDR WG drafts.  On 10/21/2019, the IDR chairs will make a determination of
whether either of these two drafts have enough support to be accepted. 


Thank you,  Susan  Hares

IDR co-chair 


From: Idr [] On Behalf Of Susan Hares
Sent: Tuesday, September 17, 2019 12:35 PM
To: 'idr wg'
Subject: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt
and draft-li-sr-policy-path-segment-01.txt [9/17 to 10/1/2019]


This begins a 2 week WG Adoption call two related drafts [9/17 to 10/1/2019]

.         draft-li-bgp-ls-sr-policy-path-segment-03.txt and 

.         draft-li-idr-sr-policy-path-segment-01.txt. 


You can access these two drafts at the following location:


The authors have pointed out that the adoption of this 

draft since the following  SR-MPLS Path Segment draft has been adopted:


Please consider the following questions in your responses? 


1)      Should this SR Policy technology be included in BGP for SR-MPLS 


Spring has adopted the draft, but IDR can provide feedback 

to spring about putting this technology in BGP.


2)      Is this technology a good way to implement the required 

Features in BGP? 


3)      Is this technology ready for adoption? 


4)      Do you have any concerns about adopting this technology? 



Cheers, Susan Hares