Re: Last Call: <draft-ietf-genarea-datatracker-community-06.txt> (Requirements for Internet-Draft Tracking by the IETF Community in the Datatracker) to Informational RFC

Paul -

1) If we publish this as an RFC, note that imgur.com will only keep an image if it's viewed at least once every three months.

2) In the list of things constituting an "update to an RFC", could you call out marking an RFC as Historic, and changing the
maturity level of an RFC in place (such as was done for 5652)

3) 2.1.2 talks of the ease of use to create a datatracker account. I think we have that already through the tools system.
Are you thinking this will require the creation of a different system?

RjS

On Mar 4, 2011, at 4:46 PM, The IESG wrote:

> 
> The IESG has received a request from the General Area Open Meeting WG
> (genarea) to consider the following document:
> - 'Requirements for Internet-Draft Tracking by the IETF Community in the
>   Datatracker'
>  <draft-ietf-genarea-datatracker-community-06.txt> as an Informational
> RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-03-18. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-genarea-datatracker-community/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-genarea-datatracker-community/
> 
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce