[yam] Referencing 1652bis and update to RFC 5321/5322

[Alexey Melnikov <[e-mail]>]

[Moving this discussion to YAM and changing the subject.]

SM wrote:

> At 16:17 26-06-10, John C Klensin wrote:

 [...]

>> For these and others, let's make sure we remember (the Nits
>> checker will presumably do that for us, but not actually make
>> changes until it is absolutely, 100%, clear that 1652bis will be
>> published.  In particular note that, while it is in the RFC
>> Editor queue, it is stuck in MISSREF waiting on 5321bis and
>> 5322bis, for neither of which there is even an active I-D yet (I
>> expect that will be cured for one or both before IETF 78, but
>> one should not count on that until it happens).  Also note that
>> if the IESG, in its wisdom, approves
>> draft-housley-two-maturity-levels in the next month or two, the
>> YAM WG enters the "overtaken by events" stage and 5321bis and
>> 5322bis (and probably even the supposedly-approved 1652bis)
>> become more effort than they are worth to finish.  Having the
>> distinction of being the last full standards approved by the
>> IETF under a set of rules that are being phased out does not
>> seem to me to be likely to be treated by the responsible editors
>> as worth the trouble.  That is, of course, just my opinion.
>
> I don't know what will happen to the maturity levels.  The MISSREF 
> could be cleared.

Yes, this particular MISREF can be cleared at any time by asking the RFC 
Editor to use published RFCs.

I have a more fundamental question for this WG: are people still going 
to be interested in updating various email specs if 3 muturity levels 
are replaced with 1 or 2?
(I understand that that would mean rechartering, but that is a 
relatively minor point.)