Re: [Idr] 5/29/2018 IDR status updates

"Susan Hares" <> Thu, 30 May 2019 13:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EEB5E12014F for <>; Thu, 30 May 2019 06:37:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.949
X-Spam-Status: No, score=0.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, 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 DLAU9v5Il-i0 for <>; Thu, 30 May 2019 06:37:19 -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 A8903120113 for <>; Thu, 30 May 2019 06:37:18 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: Susan Hares <>
To: 'Robert Raszuk' <>
Cc: "'idr@ietf. org'" <>
References: <00b101d51699$4526dd80$cf749880$> <>
In-Reply-To: <>
Date: Thu, 30 May 2019 09:37:13 -0400
Message-ID: <00af01d516ec$ca7d9b60$5f78d220$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B0_01D516CB.436BFB60"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLF6U0Jr5OVUubv3kne0tqP6v0wqAGJAbASpJW7q2A=
Content-Language: en-us
X-Antivirus: AVG (VPS 190530-0, 05/30/2019), Outbound message
X-Antivirus-Status: Not-Tested
Archived-At: <>
Subject: Re: [Idr] 5/29/2018 IDR status updates
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: Thu, 30 May 2019 13:37:21 -0000



Per requests of WG, the status is a change in status and NOT an indication of importance.   


I’m hoping we’ll forward several drafts to Alvaro next week (RFC5575bis,  extended messages, bgp best path selection, and bgp route optimization) next week.    I’ve got some time to work on the shepherd report this weekend.  


Would you watch for emails regarding the implementation report needs over the weekend?  


Cheers,  Sue 



From: Robert Raszuk [] 
Sent: Thursday, May 30, 2019 4:31 AM
To: Susan Hares
Cc: idr@ietf. org
Subject: Re: [Idr] 5/29/2018 IDR status updates


Hi Sue,


May I ask about the status of ? 


It passed WGLC, it has number of implementations, it did not change since 2016 and yet we see it stuck ... can we please push it a little forward ? 


Last year Nov 18th you indicated to take it over and complete review yet we luckily have may 2019 now and nothing moved :) And you do not even list it in your below great summary report.


Thx a lot,




On Thu, May 30, 2019 at 5:39 AM Susan Hares <> wrote:

Status updates (changes only) from 5/2 to 5/29: 


The following drafts were adopted:

·         draft-ketant-idr-bgp-ls-app-specific-attrib-01..txt, 

·         draft-li-idr-bgp-ls-sbfd-extensions-03.txt, 

·         draft-ketant-idr-bgp-ls-flex-algo-01.txt, 

·         draft-dawra-idr-bgpls-srv6-ext-06.txt 


The adoption call for draft-wu-idr-bgp-segment-allocation-ext-02 indicated interest in the work, but additional work was needed prior to adoption.  After the authors spin another revision of the draft (or drafts), a second WG.  


Drafts Past WG LC to IESG: 

·         John Scudder has determined that draft-ietf-idr-rfc5575bis-15.txt has enough implementation breath to pass to the IESG without all portions being implemented.   John has requested any comments regarding this point be sent to him by June 1st. 

·         draft-ietf-idr-tunnel-encaps has been revised (see -12.txt).  Since substantial text was edited after WG LC, a period of WG review will be held until June 7th.  At that time the document will be sent to the IESG for publication. 


WG LCs:  [6/1 to 6/14] 

IPR polls have been started for the following three drafts: 

·         draft-ietf-idr-bgp-flowspec-oid-08, 

·         draft-ietf-idr-rfc8203bis-04, and 

·         draft-ietf-idr-capabilities-registry-change-05..   

After all authors respond to the poll, these WG LC will begin.  


Early Allocations approved by WG: 

1)       draft-ietf-idr-nvo3-flowspec-04.txt, 

2)       draft-ietf-idr-flowspec-l2vpn-10.txt,

3)       draft-ietf-idr-segment-routing-te-policy-06  


Alvaro will review these early allocation requests. 


Sue Hares 



Idr mailing list