Re: Fwd: Protocol Action: 'Moving mailserver: URI scheme to historic' to Proposed Standard (draft-melnikov-mailserver-uri-to-historic-00.txt)

Per RFC 2026, Informational RFCs explicitly do not reflect consensus of
the Internet community:

   An "Informational" specification is published for the general
   information of the Internet community, and does not represent an
   Internet community consensus or recommendation.

However, moving the mailserver URI scheme to historic has consensus.
Therefore, publication of this document as an Informational RFC seems
incorrect, and publication on the standards track seems correct.

Peter

On 1/10/11 5:26 PM, "Martin J. Dürst" wrote:
> Now that I see it right in front of my eyes, I'm quite a bit surprised
> that this document is going to be a Proposed Standard. Was this
> discussed before? Is there a plan to advance it to Draft Standard and
> then Full Standard? Wouldn't Informational be good enough? Can this
> still be fixed?
> 
> [If this was already discussed, please ignore this message.]
> 
> Regards,   Martin.
> 
> -------- Original Message --------
> Subject: Protocol Action: 'Moving mailserver: URI scheme to historic'
> to    Proposed Standard (draft-melnikov-mailserver-uri-to-historic-00.txt)
> Date: Mon, 10 Jan 2011 11:49:48 -0800
> From: The IESG <iesg-secretary@ietf.org>
> To: IETF-Announce <ietf-announce@ietf.org>
> CC: Internet Architecture Board <iab@iab.org>,        RFC Editor
> <rfc-editor@rfc-editor.org>
> 
> The IESG has approved the following document:
> - 'Moving mailserver: URI scheme to historic'
>   (draft-melnikov-mailserver-uri-to-historic-00.txt) as a Proposed
> Standard
> 
> This document has been reviewed in the IETF but is not the product of an
> IETF Working Group.
> 
> The IESG contact person is Peter Saint-Andre.
> 
> A URL of this Internet Draft is:
> http://datatracker.ietf.org/doc/draft-melnikov-mailserver-uri-to-historic/
> 
> 
> 
> Technical Summary
> 
>    This document registers the mailserver: URI scheme as
>    historic in the IANA URI registry.
> 
> Working Group Summary
> 
>    This document is not the product of a working group.
> 
> Document Quality
> 
>    The document cleans out some cruft in the IANA registry
>    and clarifies possible confusion regarding the mailserver:
>    URI scheme, which was never put into use.  This topic was
>    discussed on the URI and Applications Area email lists, and
>    there was wide agreement that this document is helpful.
> 
> Personnel
> 
>    The Document Shepherd / Responsible Area Director is
>    Peter Saint-Andre.
> 
> RFC Editor Note
> 
>    Please add the following line to the document header:
> 
>       Updates: RFC 1738
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce