[rfc-i] draft-iab-streams-headers-boilerplates-06 : overlooked details?

Alfred =?hp-roman8?B?SM5uZXM=?= ah at tr-sys.de
Mon Jan 26 04:29:53 PST 2009


On Mon, 26 Jan 2009 10:52:20 +0100, Olaf Kolkman <olaf at NLnetLabs.nl> wrote:

> On Jan 23, 2009, at 5:13 PM, Alfred HÎnes wrote:
>
> CONTEXT:
> 3.4.  Other structural information in RFCs
>
>     RFCs contain other structural informational elements.  The RFC Editor
>     is responsible for the positioning and layout of these structural
>     element.  Note also that new elements may be introduced or obsoleted
>     using a process consistent with [RFC4844].  These additions may or
>     may not require documentation in an RFC.
>
>     Currently the following structural information is available or is
>     being considered for inclusion in RFCs:
>
>    [...]
> OLD:
>    Updates to the RFC  A reference identifying where more information
>        about the document can be found.  This may include information
>        whether the RFC has been updated or obsoleted, the RFC's
>        originating stream, a listing of possible errata, and information
>        on how to submit errata as described in
>        [I-D.rfc-editor-errata-process].
>
> NEW:
>    Updates to the RFC  A reference identifying where more information
>        about the document can be found.  This may include information
>        whether the RFC has been updated or obsoleted, the RFC's
>        originating stream, 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].
>
>
>  By moving out of the boilerplate to this section there is a bit more
>! leverage to, in the reference add stream specific information (you
>! could think of a pointer to which WG developed the protocol) and keep
>  it up to date (i.e. when the WG is not there and the comments should
>  go to the area) without having to redefine headers in this document.

This point, 'add stream specific information' could perhaps easily be
better reflected by simply shortening "originating stream" to "origin"
in the paragraph quoted above, leading to the following text variant:

|  NEW:
|     Updates to the RFC  A reference identifying where more information
|         about the document can be found.  This may include 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].


>> ...
>
> ...
>
> I'll be submitting version 07 shortly.
>
>
> --Olaf


Kind regards,
  Alfred HÎnes.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah at TR-Sys.de                     |
+------------------------+--------------------------------------------+



More information about the rfc-interest mailing list