(as WG chair)

A warning that the standard boilerplate will change on internet drafts
shortly. See attached message.

Those of you that use xml2rfc from the server pages to create your
documents should have no problem (although you will be making a slightly
different legal commitment). Those of you (JAMES!) who insist on using
more diverse means of creating your internet-drafts will have to take
more trouble.

regards

Keith
--- Begin Message ---
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 BCP0078.  RFC5378 is an update to RFC2026, and
RFC5378 obsoletes both 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 at
http://trustee.ietf.org/license-info/
 
Taken as a set, the documents listed above specify changes that are now
required in all new submissions into the IETF.

Henrik Levkowetz has updated the idnit tool and AMS have updated the
Internet-Draft submission tool to reflect the new requirements.  An
update to the xml2rfc has been requested. 
 
Please review the "Legal Provisions Relating to IETF Documents" and
RFC5378 to discover the new boilerplate text that is now required.
Please also take action to update the tools you use for creating your
documents.

New submissions using either the old or the new boilerplate text will be
accepted starting today, until 01h00 UTC on December 16th, 2008.  After
this cutoff date, all new submissions will be required to use ONLY the
new boilerplate text.  All submissions using old boilerplate text after
the cutoff date will be rejected.

Regards and FYI.

 
Ed Juskevicius
IETF Trust Chair
[EMAIL PROTECTED]


p.s. - Don't be surprised if you see periodic reminders about this as we
approach December 16th. 

--- End Message ---
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip

Reply via email to