Re: rfc2821bis-04

[Tony Hansen <[e-mail]>]

rfc2821bis-04 is out. To see diffs from -03, I suggest going to
tools.ietf.org/html/draft-klensin-rfc2821bis and clicking on either
Diff1 or Diff2 at the top.

As John's issues list indicates, text has been added to deal with issues
2, 10, 23, 25, 32b and 35. Please review those areas. If there are no
problems, those issues will be considered closed.

John's issues list shows issue 5 (Sect 4.4. Syntax of ID in trace) as
still open. However, a change was put in for that one back in -02. There
was sufficient consensus to change it to "atom", but no one took up the
suggestion to change to "dot-string". Since there's been no further
discussion, I'll declare that one as closed as well.

I'll address the still open issues in another email message.

	Tony Hansen
	[e-mail]

John C Klensin wrote:
> Hi.
> 
> rfc2821bis-04 is in the posting queue.  I assume that it will
> show up in the directories sometime today or tomorrow and that
> Tony will post an issues status list and further instructions
> shortly thereafter. 
> 
> This is beginning to feel to me as if we are getting into the
> home stretch, aka the point of diminishing returns, but
> decisions about that are up to Tony.
> 
> I have just added Issue 36 to reflect the general topic of
> revising the IANA Considerations Section to include pointers to
> sundry registry-creation documents.  Note that, if we do this,
> we are likely to need downrefs to some existing documents (per
> draft-klensin-norm-ref-04, to be RFC 4897 sometime soon) and/or
> to move them to Draft along with this one and, if we need a
> reference to draft-hansen-4468upd-mailesc-registry, to move that
> along and into Last Call and the RFC Editor queue really soon
> now so it can _even_ be a downref.
> 
> Current issues list attached.
> 
>      john