Re: [Idr] community of the day - common header

[<[e-mail]>]

> From: Martin Millnert  > Sent: Wednesday, September 14, 2016 1:33 PM
 > On Fri, 2016-09-09 at 20:48 +0200, Robert Raszuk wrote:
 > > > If 10+ years is the *norm* for geting something done, this is worse
 > > > than
 > > > I assumed.
 > >
 > > All I can say that regardless if this is 5 years or 10 years new
 > > functionality in BGP take that long when you add IETF process,
 > > vendor's priorities and deployment rollout all together.
 > 
 > Robert, I believe your explanation is correct.
 > 
 > It could probably be mentioned in the footprint somewhere that
 > interdependencies of protocol changes are often complex, and some times
 > the changes themselves become complex as a result.
 > 
 > To combat that, minimizing cognitive load and complexities helps. As a
 > guide line:
 >     "A designer knows he has achieved perfection not when there is
 >     nothing left to add, but when there is nothing left to take away."
 >       -- Antoine de Saint-Exupery

One could also read this as a call for a single BGP attribute, a single (common) header and a single/few type(s) of community (rather than a multiplication of community attributes: regular, extended, large, extra-large, wide/flexible...)

IOW, minimizing the complexity for a specific use case is different from minimizing the total complexity for all uses cases.

Bruno

PS: As French quotes gain popularity in IDR, I can also quote Antoine de Saint-Exupery: "Chacun est responsable de tous. Chacun est seul responsable. Chacun est seul responsable de tous."
Which, according to Lewis Galantière, translates as "Each is responsible for all. Each is by himself responsible. Each by himself is responsible for all."

https://books.google.fr/books?id=Ulh-yhlmN8cC&pg=PT141&lpg=PT141&dq=%E2%80%9CEach+by+himself+is+responsible+for+all%E2%80%9D&source=bl&ots=nOo0yvpOGe&sig=xRFvCCNE8cf9ZcY0cTDrjaA8VzA&hl=fr&sa=X&ved=0ahUKEwiZ77iv7o7PAhXGlxoKHcNvAS4Q6AEIJjAB#v=onepage&q=%E2%80%9CEach%20by%20himself%20is%20responsible%20for%20all%E2%80%9D&f=false


 > I believe the thinking such as behind this particular change in Large
 > [1] is a good example of this in action, and encouraging to see.
 > 
 > Best,
 > Martin
 > [1] https://tools.ietf.org/rfcdiff?url2=draft-heitz-idr-large-community-02.txt
 > 
 > _______________________________________________
 > Idr mailing list
 > [e-mail]
 > https://www.ietf.org/mailman/listinfo/idr

_________________________________________________________________________________________________________________________

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.