Re: [Trustees] DRAFT text for Announcement of Transition to new Boilerplate text

0 views
Skip to first unread message

Fred Baker

unread,
Nov 12, 2008, 7:59:13 AM11/12/08
to xml...@xml.resource.org, xml2rfc-...@googlegroups.com
Heads up from the IETF Trust; we are going to need RFC 5378 text sometime in the near future. 

On Nov 11, 2008, at 2:57 PM, Ed Juskevicius wrote:

Ray, Jorge, Russ, what do you think of the draft text below, for an announcement to the community?
 
Let's iterate on this text, and then decide who should send the approved text and also "to which lists?".
 
Thanks,
 
Ed
 
----------------
 
Greetings.  This message is to draw your attention to the significance of the publication of RFC5377 and RFC5378 earlier today.  
 
* RFC5377 is Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents
* RFC5378 is Rights Contributors Provide to the IETF Trust
 
Note that RFC5378 is also BCP 78.  Its publication is an update to RFC2026, and RFC5378 also obsoletes RFC3978 and RFC4748. 
 
Coincident with the above, the IETF Trustees have posted a new policy document with guidance to the community on:
* Legal Provisions Relating to IETF Documents
 
Taken as a set, the documents listed above specify changes that will be required for all new submissions to the IETF.
 
Please read both the "Legal Provisions Relating to IETF Documents" and RFC5378 for specific guidance new boilerplate text that are now required.  Please also take steps to update the tools you use in create your documents.  New submissions using either of the old or the new boilerplate text will be accepted until  01h00 UTC on December 16th, 2008.  After this cutoff date, all new submissions will be required to use the new boilerplate text.  All submissions still using old boilerplate text will be rejected after the cutoff date.
 
Regards,
 
Ed, Ray, Russ (or whoever)
 
-----------
_______________________________________________
Trustees mailing list
Trus...@ietf.org
https://www.ietf.org/mailman/listinfo/trustees

Reply all
Reply to author
Forward
0 new messages