[Idr] Weekly status 5/2/2019

"Susan Hares" <shares@ndzh.com> Thu, 02 May 2019 13:28 UTC

Return-Path: <shares@ndzh.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 6C7EC120135 for <idr@ietfa.amsl.com>; Thu, 2 May 2019 06:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.947
X-Spam-Level:
X-Spam-Status: No, score=0.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=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 N80V-e4BGgbF for <idr@ietfa.amsl.com>; Thu, 2 May 2019 06:28:23 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (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 45B9A120020 for <idr@ietf.org>; Thu, 2 May 2019 06:28:23 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=166.176.248.72;
From: "Susan Hares" <shares@ndzh.com>
To: <idr@ietf.org>
Date: Thu, 2 May 2019 09:28:19 -0400
Message-ID: <00fd01d500ea$e8709fe0$b951dfa0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00FE_01D500C9.616149D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdUA5TbE8WM5MwuRRe2vYSq7mwOEQQ==
Content-Language: en-us
X-Antivirus: AVG (VPS 190502-0, 05/02/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-seAwQklOAqVkUUVG0ocLhBKjlA>
Subject: [Idr] Weekly status 5/2/2019
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, 02 May 2019 13:28:26 -0000

Greetings idr - 

 

To make sure IDR stays on track until IETF 105, I will be sending out weekly
status updates.   Please let me know if these status updates are helpful. 

 

Cheerily, Sue Hares 

 

Status as of 5/2/2019 

-------------

Drafts in adoption process: 

   The following 3 drafts have no objections and solid reasons behind
adoption.  

    The chairs will be reviewing these drafts and send out comments on
5/3/2019. 

 

1.       draft-ketant-idr-bgp-ls-app-specific-attrib [4/16-4/30] -   

2.       draft-li-idr-bgpls-ls-sbfd-extensions -  [4/18 - 5/2]

3.       draft-ketant-idr-bgp-ls-flex-algo -  [4/16 - 4/30]

4.       draft-wu-idr-bgp-segment-allocation-ext - [4/18 - 5/2]  - extended
to 5/9 

5.       draft-dawra-idr-bgpls-srv6-ext - [5/2 to 5/16] 

 

The authors of wu-idr-bgp-segment-allocation should start 

a discussion to determine all issues have been cleared. 

 

Flow Specification drafts

--------------------------

1)      Flow-specification base draft:  RFC5575bis 

   Please review John Scudder's call for input on the mail list 

   regarding the 4 implementation lack of support for:  

a)      packet rate in bytes, and 

b)      error handling and future NLRI 

 

Flow-specification draft authors should update their documents to include
RFC5575bis.  

These drafts include: 

1.       draft-ietf-idr-bgp-flowspec-oid.txt

2.       draft-ietf-idr-flowspec-l2vpn-09.txt

3.       draft-ietf-idr-flowspec-nvo3-04.txt 

4.       draft-ietf-idr-flowspec-path-redirect

5.       draft-ietf-idr-flowspec-interfaceset 

6.       draft-ietf-idr-bgp-flowspec-label

7.       draft-ietf-bess-nsh-bgp-control-plane-10

 

I may have missed another flowpec draft.  If so, would the authors please
send me a note. 

I would like to start WG LC for flow specification drafts on May 5th. 

 

WG LC

1.       RFC8203bis - [5/6 to 5/20]  

Status: Awaiting IPR statement (from John Scudder) 

   

Early allocations calls 

------------------------------

no objection noted in the emails, these will be forward to Alvaro and IANA
for early allocation: 

1.       draft-ietf-idr-nvo3-flowspec-04  -
<https://datatracker.ietf.org/doc/draft-ietf-idr-flowspec-nvo3/> 

2.       draft-ietf-idr-l2vpn-09.txt   -   

3.       draft draft-ietf-idr-te-lsp-distribution  

 

Early allocation call in progress, but some questions in email. 

4.       draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019]

 <https://datatracker.ietf.org/doc/draft-ietf-idr-te-lsp-distribution/> 

 

Chairs/Shepherds 

Shepherd write-ups pending (watch for email on 5/3) 

1.       draft-ietf-idr-bgp-extended-messages-30 [Sue Hares shepherd]

2.       draft-ietf-idr-bgp-bestpath-selection-criteria [Sue Hares shepherd]

 

If you have any final comments, please send implementation reports and
comments to the shepherd. 

 

The following drafts are undergoing active shepherd engagement

1.	draft-ietf-idr-tunnel-encaps-11  [John Scudder]
2.	draft-idr-bgp-optimal-route-reflection [John Scudder]