And it's headed north now (sorry for the delay) On Wed, Dec 19, 2018 at 11:25 AM Tim Evens (tievens) <[email protected]> wrote: > > Done... This should be good to go. > > On 12/18/18, 5:55 PM, "Job Snijders" <[email protected]> wrote: > > On Wed, Dec 19, 2018 at 01:44:21AM +0000, Tim Evens (tievens) wrote: > > Just to confirm... I need to update the draft with the allocations by > > incrementing the revision or is that done as a separate process? > > I am not sure there is rules or tradition in this regard, so feel free > to post a new version referencing these codepoints. It may help new > implementers. In the IANA Considerations you can describe that IANA made > early allocations, and which ones they are. > > Later on in the process (shepherd write-up, directorate review, IETF > last call, IESG review, RFC Editor are yet to come!) the language in > that section will be adjusted to reflect the correct tense and make the > early allocations permanent (if the document makes it to the finish line > of course). > > Kind regards, > > Job > > > _______________________________________________ > GROW mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/grow
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
