Re: [Idr] status - incremental 4/8/2020 -

[Susan Hares <[e-mail]>]

Acee:

 

My understanding is that the authors need to address the issues that Alvaro raised.     See email on the subject on 2/21/2019. 

 

Keyur said he would get on it on 2/21.  Life may be challenged.    The other option is to Ping Gunter or Sri.   I’ll ping them again today.   

 

Maybe it will raise the urgency and they can deal with it while we are offline 

 

Sue 

 

From: Idr [mailto:[e-mail]] On Behalf Of Acee Lindem (acee)
Sent: Wednesday, April 8, 2020 9:00 AM
To: Susan Hares; [e-mail]
Subject: Re: [Idr] status - incremental 4/8/2020 -

 

Hi Sue, 

One clarification… 

 

From: Idr <[e-mail]> on behalf of Susan Hares <[e-mail]>
Date: Wednesday, April 8, 2020 at 8:40 AM
To: IDR List <[e-mail]>
Subject: [Idr] status - incremental 4/8/2020 -

 

IDR WG:

 

A little status to read with your coffee this morning.   We have an interim at 13:00 UTC (9:00 EDT,  6:00 PDT, 21:00 Bejing time) 

 

Please let me know if I’ve missed any updates. 

 

Cheers, Sue 

 

---------

At IESG in IETF LC 

1) draft-ietf-idr-rfc5575bis-19.txt – 

    Shepherd: John Scudder 

    Status:  IETF LC ended, IESG telechat: 4/15 

    IESG Publication request: 7/9/2019 

   2  AD Reviews [8/2-9/10/2019, [1/17-1/23/2020]

   

2) draft-ietf-idr-bgp-ls-segment-routing-msd-08.txt

     [Shepherd: Susan Hares]

     Status:  3rd round of AD revisions  

     IESG Publication requested:  10/15/2019

     IETF WG LC:  6 days  

 

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

AD review – authors need to respond 

1)  <https://datatracker.ietf.org/doc/draft-ietf-idr-tunnel-encaps/> draft-ietf-idr-tunnel-encaps-14 - sent to IESG 

[Waiting 47 days] 

 

So, this draft requires a response from the authors to Alvaro? It hasn’t gone to full IESG yet – right? We have a couple LSR drafts with a normative reference. 

 

Thanks,

Acee

 

2) draft-ietf-idr-capabilities-registry-change-05.txt 

[Waiting 57 days] 

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

WG past WG LC – stuck  waiting for implementation reports on wiki

[reported to have 2 implementations, but no details on wiki] 

 

1) draft-ietf-idr-ext-opt-param

2) draft-idr-eag-distribution-09.txt 

---------

Drafts stuck post WG LC – waiting for minor edits 

1) draft-ietf-idr-rfc8203bis.05.txt  - 

----

Flow specification drafts in WG LC 

 

1) Draft-ietf-idr-flow-spec-v6-10.txt

   Status: restarted [4/8 to 4/22]

   Status: IESG desires, but is it ready? 

   Needed:  implementation reports 

 

2)  <https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-flowspec-oid/> draft-ietf-idr-bgp-flowspec-oid-11

    Status:  3/13/ to 4/13 

    Status: light response, please comment 

    Authors:  Please fill out implementation report 

 

-----------

WG Adoption calls: 

 

   1) Draft-hujun-idr-bgp-ipsec

       WG adoption:  3/30-4/13

        Shepherd: Susan Hares 

        Comment: only 1 response, heading toward “no consensus”

 

2) draft-hujun-idr-bgp-ipsec-transport-mode

     WG Adoption: 3/30 – 4/13

      Shepherd: Susan Hares 

     Comment: only 1 response, heading toward “no consensus”

 

3) draft-li-idr-sr-policy-path-mtu-03.txt 

    WG adoption: 3/30 – 4/13 

     Shepherd: Susan Hares 

    Comment: Positive response: Heading toward WG Adoption 

 

Request for input:

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

draft-scharf-tcpm-yang-tcp-04

 

Proposed WG LC drafts for flow-specification that were on hold: 

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

[Authors should contact chairs] 

 

1)  draft-ietf-idr-flowspec-interfaceset-05 – 

WG notes indicated this might go ahead without flow-specification v2 

 

2) draft-ietf-idr-flowspec-path-redirect-10 – 

WG discussion needs to occur on whether flowspecification 

 

 

Proposed WG LCs (3/30 and 4/8) 

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

1) draft-ietf-idr-bgp-open-policy-08 – on hold pending  revision -09

2)  draft-ietf-idr-flowspec-l2vpn-13 – in slides for 4/8

 

 

Proposed Adoption calls  

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

draft-cl-idr-bgp-ext-com-registry-udpate-00.txt