[rfc-i] Wrapup of Fwd: Comment on headers-and-boilerplates

Joe Touch touch at ISI.EDU
Tue Jan 13 18:10:19 PST 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Olaf Kolkman wrote:
> 
> Joe,
> 
> I read your other suggestions, but would like to stick to where we
> converged too...  a fragile balance.
> 
> However, you observed:
>>
>> ++ note that the IETF documents are missing a phrase that refers to
>> section 2 of RFCXXXX.
>>
> 
> I can sympathize to the argument for symmetry... and I can come up with
> wording.
> 
> So to the current paragraph:
>      For non-IETF stream documents a reference to <xref
>      target="standards"/> of this RFC is added with the following
>      sentence: "Documents approved for publication by the [stream
>      approver -- currently, one of: "IAB", "IRSG", or "RFC
>      Editor"] are not a candidate for any level of Internet
>      Standard; see <xref target="standards"/> of RFCXXXX."
> I propose to add:
>      For IETF stream documents a reference is added:
>      Not all documents approved for publication by the IETF are
>      candidate for any level of Internet Standards see
>      <xref target="standards"/> of RFCXXXX."
> 

I think you need a corresponding statement for the standards too, i.e.,
it is a standards-track doc, as explained in ...

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkltSYsACgkQE5f5cImnZrsTfgCeNcywv/VpRXHQtKqL57a7skE0
A1IAnRslEECkI0shwdzq1BEO7mISKCe3
=nkOg
-----END PGP SIGNATURE-----


More information about the rfc-interest mailing list