Re: [Idr] WG adoption call for draft-scudder-idr-entropy-label-01 (9/6/2022 to 9/20/2022)

[Susan Hares <[e-mail]>]

Aijun:

Thank you for your patience with my delay in responding.   I have been on travel.   This working group adoption call has closed and the chairs have decided to adopt draft-scudder-idr-entropy-label-01.txt.

The purpose of draft-scudder-idr-entropy-label-01.txt is to fix an existing problem with IDR specification.  It is possible that the sequence you listed in your emails could occur:

1) RFC6790
2) RFC 7447(deprecate RFC6790)
3) RFC****(deprecate RFC7447 again, based on the final document of draft-scudder-idr-entropy-label-01)
4) RFC####(depeciated RFC**** again, based on the final document of [I-D.ietf-idr-next-hop-capability]

I have received requests from the IDR mail list and from private email from implementers and operators.  As you know from our conversations, the IDR care deeply about standardizing BGP additions (fixes or enhancements) needed by network operators.

Whether this “fix” should be replaced by draft-ietf-idr-next-hop-capability or some combination of other drafts (draft-ietf-idr-attribute-announcement) is something the IDR chairs need feedback on.   We decided to hold an interim on 10/13 with 1 hour devoted to this topic.

Since you asked about my thought processes, I will post my write-up on this call on the IDR wiki by Monday.  I continued on with adoption calls on Tuesday to address your second concern – keeping the IDR Working Group working on other drafts.

If you would like to chat with me after you read my adoption call write-up, I would be happy to chat with you.

Cheerily,  Sue











One of the challenges of a WG chair is to make a call based on input from the working group.   This

From: Aijun Wang <[e-mail]>
Sent: Tuesday, September 27, 2022 8:24 PM
To: Susan Hares <[e-mail]>
Cc: [e-mail]
Subject: Re: [Idr] WG adoption call for draft-scudder-idr-entropy-label-01 (9/6/2022 to 9/20/2022)

Hi, Sue: Want to ask where are the consensus on the list for this draft? Given this draft has contradicted with the existing WG draft which has been pointed out by several several service providers? A
External ([e-mail]<mailto:[e-mail]>)
  Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnMTA1ODY5MTIvc2hhcmVzQG5kemguY29tL2E0ODEyZTY1MDkxZmYyNWUxMjk5OTg3NmJkMjM0YjZmLzE2NjQzMjQ2MzAuMDc=#key=6b2acfdfee8de47a3570ac1b99e16495>  FAQ<https://www.inky.com/banner-faq>  GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>

Hi, Sue:

Want to ask where are the consensus on the list for this draft? Given this draft has contradicted with the existing WG draft which has been pointed out by several several service providers?
As also mentioned in your list questions, there is necessary to discuss the short term and long term improvements of BGP next hop in the coming interim meeting, then what’s the reason to adopt this document in hurry?

Aijun Wang
China Telecom


On Sep 28, 2022, at 01:14, Susan Hares <[e-mail]<mailto:[e-mail]>> wrote:

The chairs have reviewed the IDR WG discussion and feedback from implementers on draft-ietf-idr-entropy-label-01.txt.

The consensus from this review is that we should:
1) adopt draft-scudder-idr-entropy-label-01 as
draft-ietf-idr-entropy-label-01


2) Hold a discussion of BGP Next-Hop technology to discuss
the needs for current and future standards on BGP Next Hop.

During this interim we will discuss the open proposals for
BGP Next HOPS to determine what technology goes forward
toward standardization.

IDR needs the feedback from implementers and operators
about the short term and long-term improvements to
BGP Next hop.

Cheerily, Sue
_______________________________________________
Idr mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/idr<https://shared.outlook.inky.com/link?domain=www.ietf.org&t=h.eJxdjkEOgyAUBa9iWDd8QERx5VVQQGj12wiGpE3v3rLt9mXeZN7kOjcyNiTk_EwjQCmFRpc9Pc4VdhO33SBsMeWI_oBoT3JryKM-0OUfw1k3KM0FpGBOlya0r0CXYwcjBy6c6pjm3ovOcaG1Hno1W9HKWXngSslWSNUyyvpqddVaDK4m3i-ccoq4hsvUErpgJWwl_vfPF80-PKw.MEUCIAsl5ny1fLlhHqaFZCdGKYnPBSkUzaNYE7Z5ZASJnP84AiEA8bkjgqiKtsEjcCXEeEeu7gCj1HOzgHHS_mql4ITDsT0>