Re: [Idr] draft-ietf-idr-capabilities-registry-change-05.txt - WG LC []6/9/2019 to 6/16/2019] - extending this for a 3rd week (7/8 to 7/15)

[<[e-mail]>]

I support progressing this draft.


1)      As the introduction states it, the current situation is not satisfactory. We need to improve to it, so IMHO in this case, the bias should be toward progressing the document rather than not progressing it.

2)      That specific proposal is good and has been commented multiple times on the list. AFAIR, the author has updated the document to reflect WG comments.

On a side note, as this document is not proposing a new fancy feature, it feels like understandable that it does not generate much excitation on the list.



Ø  Is there any technical or operational issue in making this change?

Quite the opposite. There is operational issue in not making this change.
https://tools.ietf.org/html/rfc5226#section-4.1
      Private Use - For private or local use only, with the type and
            purpose defined by the local site.  No attempt is made to
            prevent multiple sites from using the same value in
            different (and incompatible) ways.  [...] It is the responsibility of the sites
            making use of the Private Use range to ensure that no
            conflicts occur (within the intended scope of use).

EBGP sessions are very likely to not be limited to a "local site", and rfc5492 did not made any provision to handle such "private" code points any differently over EBGP session. (such as restricting/filtering over EBGP (both when sending and receiving), or creating a local context/translation for this EBGP peer ). As a result, two implementations could advertise the same "Private" code point over an EBGP session, for a different meaning, thereby creating an interop issue that the network operator would likely can't protect from).

Thank you,
--Bruno

From: Idr [mailto:[e-mail]] On Behalf Of Susan Hares
Sent: Monday, July 8, 2019 7:00 PM
To: [e-mail]
Subject: Re: [Idr] draft-ietf-idr-capabilities-registry-change-05.txt - WG LC []6/9/2019 to 6/16/2019] - extending this for a 3rd week (7/8 to 7/15)

Greetings:

The email list support for this draft did not receive as many comments as I expected.   Perhaps, this lack of comments was due to vacations or due to this idea "just making sense".

Since one of the WG chairs is an author, I do need a strong sense of support.  Please send in comments or just a comment for "support" or "no support" for this draft.

Cheerily, Susan Hares


From: Idr [mailto:[e-mail]] On Behalf Of Susan Hares
Sent: Sunday, June 9, 2019 1:33 PM
To: [e-mail]
Subject: [Idr] draft-ietf-idr-capabilities-registry-change-05.txt - WG LC []6/9/2019 to 6/16/2019]

This begins a 2 week IDR  WG Last Call (LC) on ft-ietf-idr-capabilities-registry-change-05.txt.

The document is at:
https://datatracker.ietf.org/doc/draft-ietf-idr-capabilities-registry-change/

As registration document, there is no implementation report.

Please indicate in comments to the IDR "support" or "no support" for WG LC.
Consider:


1)      Does this change to registration procedures for BGP capability codes help speed up processing?

2)      Is there any technical or operational issue in making this change?

3)      Do we need to pass this to the IESG at the same time as any GROW document?

John Scudder is an author so I am the shepherd/chair on this draft.

Cheerily, Susan Hares

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.