Re: [Idr] Are there IDR drafts the Grow WG needs completed quickly?

Hi Susan, all

> From Susan Hares
 > Sent: Thursday, July 20, 2017 10:53 AM

 > 
 > Job:
 > 
 > If this solution was good was the best solution,  there is no further work.

This is the case.

 > If this solution was due to the slow progress of IDR, I'd like to know.
 > We've been trying to fast track all operator needs.

As the author of the offending sentence/slide and co-author of the g-shut document, I can assure you that I had zero (b) intention to put the responsibility on IDR or on an IDR draft (a).
I'm sorry if it felt that way.

--Bruno

(a) Plus being an author of draft-ietf-idr-reserved-extended-communities, I would have been the one to blame.
(b) zero as per https://en.wikipedia.org/wiki/0 not as per https://en.wikipedia.org/wiki/Zero-point_energy

 > 
 > Sue
 > 
 > -----Original Message-----
 > From: Job Snijders [mailto:job@ntt.net]
 > Sent: Thursday, July 20, 2017 4:42 AM
 > To: Christopher Morrow
 > Cc: Susan Hares; idr@ietf.org List; grow@ietf.org grow@ietf.org
 > Subject: Re: [Idr] Are there IDR drafts the Grow WG needs completed quickly?
 > 
 > On Thu, Jul 20, 2017 at 10:33:04AM +0200, Christopher Morrow wrote:
 > > On Thu, Jul 20, 2017 at 9:57 AM, Susan Hares <shares@ndzh.com> wrote:
 > > > As the IDR co-chairs sat in the grow meeting, we heard of an IDR
 > > > draft that was so long in becoming an RFC that the Grow authors took
 > > > another approach (which was less desired).
 > >
 > > I'm unsure what draft this is? this might be the gshut draft?
 > 
 > GROW's draft-ietf-grow-bgp-gshut had a dependency on
 > draft-ietf-idr-reserved-extended-communities which related to
 > draft-ietf-idr-as4octet-extcomm-generic-subtype - eventually this was
 > resolved by just working with RFC 1997 well-known communities.
 > 
 > Kind regards,
 > 
 > Job
 > 
 > _______________________________________________
 > Idr mailing list
 > Idr@ietf.org
 > 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.