RE: Proposed text for IESG Handling of Historic Status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: ietf-bounces@xxxxxxxx [mailto:ietf-bounces@xxxxxxxx] On Behalf Of Alexey Melnikov
> Sent: Saturday, June 04, 2011 2:00 PM
> To: Mykyta Yevstifeyev
> Cc: ietf@xxxxxxxx; The IESG
> Subject: Re: Proposed text for IESG Handling of Historic Status
> 
> > First, for RFCs of what categories is it legitimate to move them to
> > Historic.  Whether Experimental or Informational RFCs could be
> > considered for such action?  As far as I understand RFC 2026, Historic
> > can be assigned to Standards Track documents; however it won't be
> > excessive to clarify this regulation in the IESG statement additionally.
> 
> My understanding is that any RFC can be moved to Historic. But if this
> is not clear from RFC 2026, maybe it is worth clarifying.

If 2026 doesn't limit what types of RFCs can become Historic, then I presume any of them can.  I'm not sure we need to make that explicit.

_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]