[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New ID-Checklist to replace ID-nits (fwd)
Hi Elizabeth,
Sunday 23 May 2004, elizabeth.rodriguez at dothill.com wrote:
> I am trying to check a document for my WG, and have a couple of
> questions/comments.
>
> 1) Internet Draft boilerplate
>
> Section 2.2, 1: It MUST contain boilerplate that permits publication as an
> RFC, see [RFC3667]Bradner, S., IETF Rights in Contributions, February 2004.,
> Section 5.2.
>
> Section 5.2 of 3667 does not seem to have a standard boilerplate, only the
> two boilerplates that restrict IETF derivative works. So, are we supposed
> to use the 2026 boilerplate and replace 2026 with 3667? The statement " Do
> not add a numbered reference in the I-D boilerplate to RFC 3667 or RFC 3668
> (or to RFC 2026 for older documents)." Section 2.1, 7 implies that the
> boilerplate has been updated and references 3667.
FWIW, I enclose the boilerplate I've had some of the MIP4 authors use;
this also matches what the latest version of the xml2rfc produces. As
far as I can see this complies fully with 3667 and 3668.
> 2) The script refers to sections in 2026, but the ID-checklist indicates
> using text verbatim from 3667 and 3668.
Not sure which script you're referring to, but if it is the 'idnits'
script, it looks at the draft and tries to determine whether the draft
is based on 2026 or 3667 boilerplate, and judges it accordingly. A
future version will be strict in permitting 3667 only, but currently
there are a lot of drafts in flight based on 2026, so I going by the
'conform to either 2026 or 3667' approach for now. Mmm, maybe I'll add
a switch which makes it 3667-strict now; with the updated ID-checklist
that seems reasonable.
Henrik
> Thanks,
>
> Elizabeth Rodriguez
> -----Original Message-----
> From: Harald Tveit Alvestrand [mailto:harald at alvestrand.no]
> Sent: Friday, May 21, 2004 7:54 AM
> To: wgchairs at ietf.org
> Subject: New ID-Checklist to replace ID-nits (fwd)
>
> I assume most of you saw this message on ietf-announce.
> But since it's especially important to the WG chairs, I'm forwarding it to
> you directly.
>
> Take care!
>
> ---------- Forwarded Message ----------
> Date: 20. mai 2004 09:34 -0400
> From: The IESG <iesg at ietf.org>
> To: IETF-Announce
> Subject: New ID-Checklist to replace ID-nits
>
> As you probably all know, we have used the ID-nits for a few
> years to help you all to prepare your Internet-Drafts such that
> they will process faster through the AD-review, IETF Last Call
> and IESG approval process.
>
> The name was somewhat wrong in that it is more a serious checklist
> than merely "nits" (however, there are some nits too).
> The IESG, RFC-Editor and IANA have evaluated the checklist, and
> a new (improved) ID-Checklist is now available at
>
> http://www.ietf.org/ID-Checklist.html
>
> Please help us all by actually CHECKING your Internet-Draft BEFORE
> you pass it on to your AD and the IESG via a "request to publish".
> It will help to make the process go faster and reduce the workload
> on all of us if your document has been checked and complies with
> the guidance/rules in the ID-Checklist.
>
> Thanks, the IESG
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce at ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
>
>
>
> ---------- End Forwarded Message ----------
>
>
>
>
Draft Boilerplate conformant with RFC 3667 and 3668
===================================================
DRAFT INTRO:
------------------------------------------------------------------------
Status of this Memo
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt .
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html .
This Internet-Draft will expire on ....................
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
------------------------------------------------------------------------
DRAFT ENDING:
------------------------------------------------------------------------
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr at ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
------------------------------------------------------------------------