[rfc-i] RFC Metadata Pages

[Dave Thaler]

Yes, these are very nice, thanks!

Currently:
        IAB is a link to http://www.iab.org/
        IETF is not a link (why?)
        Independent is a link to http://www.rfc-editor.org/indsubs.html
        IRTF is a link to http://www.irtf.org/

An alternative would be to having the stream value (e.g., "IETF") be
a link to the relevant stream definition document:
        RFC 4845 for IAB
        RFC 2026 for IETF
        RFC 4846 for independent
        The I-D in progress for IRTF? Or perhaps
                http://trac.tools.ietf.org/group/irtf/trac/wiki/IRTF-RFCs

I also observe that April 1st RFCs currently say stream=Independent
and link to a page stating:
"Every document to be published as an RFC must first be posted online
as an Internet-Draft".
Is there any page that tells how someone can submit a document for
April 1st RFC consideration?

-Dave

> -----Original Message-----
> From: rfc-interest-bounces at rfc-editor.org [mailto:rfc-interest-
> bounces at rfc-editor.org] On Behalf Of Leslie Daigle
> Sent: Friday, August 07, 2009 11:17 AM
> To: RFC Editor
> Cc: rfc-interest at rfc-editor.org
> Subject: Re: [rfc-i] RFC Metadata Pages
>
>
> Nice!
>
> Leslie.
>
> RFC Editor wrote:
> > Greetings,
> >
> > We have created RFC metadata pages to meet the requirements described
> > in Section 3.2.3 of draft-iab-streams-headers-boilerplates-08, for
> > example:
> >
> >    http://www.rfc-editor.org/info/rfc2026
> >    http://www.rfc-editor.org/info/rfc5246
> >    http://www.rfc-editor.org/info/rfc5507
> >
> > These pages include:
> > - links to the RFC (in the formats available from rfc-editor.org)
> > - Status (as defined in RFC 2026)
> > - Obsoletes / Updates / Obsoleted by / Updated by information (if
> applicable)
> > - Author(s)
> > - Stream (as defined in RFC 4844 or Legacy*)
> > - Source (Working Group and Area, if applicable)
> > - links to any errata
> > - Abstract
> >
> > * For Stream, "Legacy" indicates that source information was not
> > recorded for this RFC; we are working on updating this information
> for
> > RFCs for which it exists.
> >
> > Please note that we do not plan to include the URLs in RFCs as
> > described in draft-iab-streams-headers-boilerplates-08 until the
> > document is ready to be published.
> >
> > We welcome your feedback.
> >
> > Thank you.
> >
> > RFC Editor
> >
> > Section 3.2.3 of draft-iab-streams-headers-boilerplates-08:
> >
> >    The boilerplate ends with a reference to where further relevant
> >    information can be found.  This information may include, subject
> to
> >    the RFC Editor's discretion, information whether the RFC has been
> >    updated or obsoleted, the RFC's origin, a listing of possible
> errata,
> >    information about how to provide feedback and suggestion, and
> >    information on how to submit errata as described in
> >    [I-D.rfc-editor-errata-process].  The exact wording and URL is
> >    subject to change (at the RFC Editor's discretion), but current
> text
> >    is:
> >
> >    "Information about the current status of this document, any
> errata,
> >    and how to provide feedback on it may be obtained at
> >    http://www.rfc-editor.org/<static-path>/rfc<rfc-no>.html"
> >
> > _______________________________________________
> > rfc-interest mailing list
> > rfc-interest at rfc-editor.org
> > http://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
>
> --
>
> -------------------------------------------------------------------
> "Reality:
>       Yours to discover."
>                                  -- ThinkingCat
> Leslie Daigle
> leslie at thinkingcat.com
> -------------------------------------------------------------------
> _______________________________________________
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
> http://mailman.rfc-editor.org/mailman/listinfo/rfc-interest