Chris:
Yes – it is gshust. Please see slide 3 of the gshut presentation. Waiting for the dependency on a draft - Draft-ietf-idr-reserved-extended-communities - Draft-ietf-idr-as4octet-exztcomm-generic-subtype We will do early allocation of code points for any draft adopted by IDR. Either the authors or another WG can asked us to do these early code point allocation. See From: Idr [mailto:[email protected]] On Behalf Of Christopher Morrow Sent: Thursday, July 20, 2017 4:33 AM To: Susan Hares Cc: [email protected] List; [email protected] [email protected] Subject: Re: [Idr] Are there IDR drafts the Grow WG needs completed quickly? On Thu, Jul 20, 2017 at 9:57 AM, Susan Hares <[email protected]> wrote: Grow and IDR groups: 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? I don't believe we have other work waiting in a similar state, Peter, do any come to mind for you? We would like to know what IDR drafts need to be moved forward quickly. If you would send the name of these drafts to the chairs, it would help us push forward these critical drafts. You can send these names in response to this email or send a private note to the IDR chairs. Sue Hares
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
