[GROW] draft-ietf-grow-bgp-gshut

[<[e-mail]>]

Hi all,

 > From: Job Snijders [mailto:[e-mail]]
 > Sent: Friday, May 26, 2017 4:05 PM
> 
 > Hi GROW,
 > 
 > I've compiled a todo list to outline the next steps for the
 > draft-ietf-grow-bgp-session-culling document.
 > 

[...]
 
 > BGP g-shut (possible action for Bruno et al)
 > --------------------------------------------
 > 
 > Bruno promised a new, fresh version of draft-ietf-grow-bgp-gshut which
 > would focus on the rfc1997 well-known community 65535:0 - I would
 > appreciate if this is posted at some point so we can make an Informative
 > reference to a non-zombie draft.  NTT (as2914) & Coloclue (as8283)
 > implemented experimental rfc1997 gshut support for customers and it
 > appears to work as advertise (no pun intended ;-).
 
https://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-07 has just been posted and addresses the above point.

As previously discussed on the list, the main technical change is the focus, for the eBGP signaling, on the use of a well-known BGP community.
In other word, the alternative option to use a non-transitive community has been removed, following latest IDR discussion on community and the lack of implementation (hence IDR WG progress) of draft-ietf-idr-reserved-extended-communities / draft.ietf-idr-as4octet-extcomm-generic-subtype.
As a benefit, this draft is now aligned with:
- the BGP gshut/planned maintenance implementations disclosed on this list https://mailarchive.ietf.org/arch/msg/grow/ReJtavkJDlyrDo5qoD7u9iJDLXs
- the deployed usage

Thanks to Job for the in-depth review, comments, and reminders to update the draft.

--Bruno




_________________________________________________________________________________________________________________________

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.