idnits 2.17.1 draft-heard-rfc4181-update-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 13. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 125. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 101. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 108. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 114. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 140 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The abstract seems to indicate that this document updates RFC4181, but the header doesn't have an 'Updates:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (2 January 2007) is 6324 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3978 (Obsoleted by RFC 5378) ** Obsolete normative reference: RFC 4748 (Obsoleted by RFC 5378) Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT C. M. Heard, Editor 2 Will Update: RFC 4181 2 January 2007 3 (if approved) 5 RFC 4181 Update to Recognize the IETF Trust 6 8 Status of this Memo 10 By submitting this Internet-Draft, each author represents that any 11 applicable patent or other IPR claims of which he or she is aware 12 have been or will be disclosed, and any of which he or she becomes 13 aware will be disclosed, in accordance with Section 6 of BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on 6 July 2007. 33 Copyright Notice 35 Copyright (C) The IETF Trust (2007). 37 Abstract 39 This document updates RFC 4181, "Guidelines for Authors and Reviewers 40 of MIB Documents", to recognize the creation of the IETF Trust. 42 1. Introduction 44 In order to reflect the creation of the IETF Trust, certain updates 45 to the copyright notices required in IETF documents by RFC 3978 46 [RFC3978] have been published in RFC 4748 [RFC4748]. This document 47 updates RFC 4181 [RFC4181] to bring it into alignment with those 48 changes. 50 2. Updates to RFC 4181 52 The text of RFC 4181 is hereby updated as set forth below to reflect 53 the creation of the IETF Trust. 55 2.1. Updates to Section 3.7 57 In the copyright notice templates in Section 3.7, replace all 58 occurrences of "The Internet Society" with "The IETF Trust". 60 3. Security Considerations 62 The updates in this document have no impact in the security of the 63 Internet. 65 4. IANA Considerations 67 The updates in this document have no impact on the IANA. 69 5. References 71 5.1. Normative References 73 [RFC3978] Bradner, S., Ed., "IETF Rights in Contributions", 74 BCP 78, RFC 3978, March 2005. 76 [RFC4748] Bradner, S., Ed., " RFC 3978 Update to Recognize the 77 IETF Trust", BCP 78, RFC 4748, October 2006. 79 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers 80 of MIB Documents", BCP 111, RFC 4181, September 2005. 82 Editor's Address 84 C. M. Heard 85 158 South Madison Ave. #207 86 Pasadena, CA 91101-2569 87 USA 89 Phone: +1 626 795 5311 90 EMail: heard@pobox.com 92 Intellectual Property Statement 94 The IETF takes no position regarding the validity or scope of any 95 Intellectual Property Rights or other rights that might be claimed to 96 pertain to the implementation or use of the technology described in 97 this document or the extent to which any license under such rights 98 might or might not be available; nor does it represent that it has 99 made any independent effort to identify any such rights. Information 100 on the procedures with respect to rights in RFC documents can be 101 found in BCP 78 and BCP 79. 103 Copies of IPR disclosures made to the IETF Secretariat and any 104 assurances of licenses to be made available, or the result of an 105 attempt made to obtain a general license or permission for the use of 106 such proprietary rights by implementers or users of this 107 specification can be obtained from the IETF on-line IPR repository at 108 http://www.ietf.org/ipr. 110 The IETF invites any interested party to bring to its attention any 111 copyrights, patents or patent applications, or other proprietary 112 rights that may cover technology that may be required to implement 113 this standard. Please address the information to the IETF at 114 ietf-ipr@ietf.org. 116 Disclaimer of Validity 118 This document and the information contained herein are provided 119 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 120 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 121 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 122 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 123 WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE 124 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 125 FOR A PARTICULAR PURPOSE. 127 Copyright Statement 129 Copyright (C) The IETF Trust (2007). 131 This document is subject to the rights, licenses and restrictions 132 contained in BCP 78, and except as set forth therein, the authors 133 retain all their rights. 135 Acknowledgement 137 Funding for the RFC Editor function is provided by the IETF 138 Administrative Support Activity (IASA).