Re: [Idr] draft-ietf-idr-ext-opt-param-06.txt - 2 Week WG LC (7/30 to 8/13/2019)

[John Scudder <[e-mail]>]

(As a co-author of course.)

Since it seemed helpful last time, here's the elevator pitch for ext-opt-param: We are currently limited to 255 bytes of BGP capabilities. Since many/most BGP extensions want to use a capability, it’s not hard to imagine overrunning the 255 bytes. It would be in everyone’s interest to fix the limitation before we ever bump into it. This draft is a spec for a fix.

Thanks,

—John

On Jul 30, 2019, at 12:06 PM, Susan Hares <[e-mail]<mailto:[e-mail]>> wrote:

This begins a 2 week working group last call on draft-ietf-idr-ext-opt-param-06.txt from 7/30 to 8/13/2019.

You can access the draft at:

https://datatracker.ietf.org/doc/draft-ietf-idr-ext-opt-param/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Didr-2Dext-2Dopt-2Dparam_&d=DwMFAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=hLt5iDJpw7ukqICc0hoT7A&m=7yslJny2ZMcwH_kCk9UyVzGfQaVlMu7BoMyOtSDbMnk&s=p2572N3TH8pEFI-9eitSzTedYkto_TMR805OddPtQHU&e=>

John and Enke – I am counting on you gather information on the 2 implementations and post this on the IDR Wiki during these 2 weeks.

For the WG, consider if:

1)      The technology is ready for publication or if there are flaws that prevent its publication,
2)      Is this technology useful to BGP deployments?
3)      Are there any minor editorial errors the authors should address before publication.


Cheerily, Sue Hares