Fw: Boilerplate changes Required for TLP 4.0

Hi -

Forwarded for your information.

Randy

----- Original Message ----- 
> From: "Marshall Eubanks" <tme <at> americafree.tv>
> To: <tlp-interest <at> ietf.org>
> Cc: "Trustees" <trustees <at> ietf.org>; "Working Group Chairs" <wgchairs <at> ietf.org>; "Internet
Research Steering Group" <irsg <at> isi.edu>;
"RFC Interest" <rfc-interest <at> rfc-editor.org>
> Sent: Wednesday, January 13, 2010 3:47 AM
> Subject: Boilerplate changes Required for TLP 4.0
>
> Colleagues,
>
> Some concerns have been raised about tooling issues and boilerplate
> changes. At present, for example, xml2rfc is not supported, and
> because of this it is not clear when it will be possible to update it
> to support the new boilerplate.  However, Alternate Stream documents
> have been blocked for some time waiting for the new Trust Legal
> Provisions (TLP), and it was decided to unblock these documents with
> TLP 4.0 even in the absence of xml2rfc support. (There is an open call
> for volunteers to support xml2rfc, and I would encourage interested
> parties to contact Russ Housley.)
>
>      The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
>      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
>      "OPTIONAL" in this document are to be interpreted as described in