idnits 2.17.1 draft-ietf-proto-proto-adviser-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.a on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 200. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 177. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 184. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 190. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 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 (March 15, 2005) is 6981 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) ** Downref: Normative reference to an Informational draft: draft-ietf-proto-wgchair-doc-shepherding (ref. 'PROTO') Summary: 6 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Proto Team D. Meyer 3 Internet-Draft Cisco/University of Oregon 4 Expires: September 16, 2005 March 15, 2005 6 The PROTO Adviser 7 draft-ietf-proto-proto-adviser-00 9 Status of this Memo 11 This document is an Internet-Draft and is subject to all provisions 12 of Section 3 of RFC 3667. By submitting this Internet-Draft, each 13 author represents that any applicable patent or other IPR claims of 14 which he or she is aware have been or will be disclosed, and any of 15 which he or she become aware will be disclosed, in accordance with 16 RFC 3668. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as 21 Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on September 16, 2005. 36 Copyright Notice 38 Copyright (C) The Internet Society (2005). 40 Abstract 42 The PROTO Adviser is a designated IETF community member who will 43 provide support to PROTO document shepherds during the first year or 44 so after the IETF working groups begin using PROTO. He or she 45 primarily serves as a source of institutional knowledge for the 46 shepherds and Chairs (and any community member with an interest in 47 PROTO). This document describes roles of the PROTO Adviser. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 2. PROTO Adviser Roles and Responsibilities . . . . . . . . . . . 3 53 3. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 55 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 56 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 57 7. Normative References . . . . . . . . . . . . . . . . . . . . . 4 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 5 59 Intellectual Property and Copyright Statements . . . . . . . . 6 61 1. Introduction 63 Early in 2004 the IESG undertook several experiments aimed at 64 evaluating whether any of the several candidate changes to the IETF 65 document approval process could yield qualitative improvements in 66 document throughput and quality. One such experiment, referred to as 67 PROTO [PROTO] (PROcess and TOols), is a set of methodologies designed 68 to involve the Working Group chairs more directly in their documents' 69 approval life cycle. In particular, the PROTO team focused on that 70 part of the document's life cycle which occurs after the document 71 editor and working group typically view the document as "tossed over 72 the wall" to the IESG for publication. In the PROTO methodology, 73 instead of tossing the document over the wall, the WG Chair takes 74 over the Area Director's shepherding tasks (as detailed in [PROTO]). 75 There are no changes in the document approval requirements, the IESG 76 still must carry out its approval steps, but the Working Group Chair 77 document shepherd is able to team with use his or her energy to 78 greatly enhance the work done during the approval process for the 79 document. 81 The PROTO process represents a shift in responsibilities from AD to 82 working group chair. This is a significant change which should 83 improve the timeliness and quality of IETF documents. Since this 84 change is being applied to working groups and important IETF 85 documents, the PROTO team felt that it would helpful to have a member 86 of the group which devised this new process available to the folks 87 using it to ensure that transition went smoothly. Note that the 88 Proto Adviser's responsibilities are generally to answer questions 89 about the process and remind folks to use it. Finally, the Proto 90 Adviser isn't intended to be directly involved in document 91 shepherding other than as an adviser on the PROTO process. 93 2. PROTO Adviser Roles and Responsibilities 95 The PROTO Adviser (PA) will provide support to the Working Group 96 document shepherds using PROTO in the first year or so after working 97 groups begin to use the PROTO approach to document publication. The 98 includes serving as a source of institutional knowledge available to 99 the Working Group Chairs during the PROTO process, both through 100 involvement in the PROTO team and through continuing manager 101 experience, and the following specific responsibilities: 103 1. Maintaining a list or website for the community of PROTO working 104 groups. See [PROTO] for the set of cases which are excluded. 105 The PA also reminds the ADs and Working Group Chairs that PROTO 106 write ups are required (thus starting the PROTO process) when 107 working group documents transition into AD Evaluation state. 108 Note that this requires that the PA receive notifications of the 109 state transitions for the PROTO documents. This reminder should 110 point the shepherds to [PROTO] to ensure that the structure and 111 content of the write up is full and complete. 113 2. Keeping track of WG progress status and activity level to ensure 114 that the methodology is being used (and works smoothly), 116 3. Acting as a general resource for WGCs involved in PROTO. In 117 particular, the PA serves as a resource for the WGC who can 118 triage PROTO related issues and vector them appropriate 119 resolution point, 121 4. The PA will periodically report to the community on the progress 122 of PROTO, including successes and problems encountered, and 123 incremental changes to the methodology. 125 3. Conclusions 127 This document introduces the roles and responsibilities of the PROTO 128 manager. It is important to note that the PROTO manager is an 129 informal position and is not intended to be institutionalized. 130 Rather, it is envisioned that the PROTO manager position will be 131 retained as long as it proves useful, i.e., until the PROTO ways of 132 working become very familiar, probably for a year or so. 134 4. Security Considerations 136 This document specifies a change to IETF document flow procedures. 137 As such, it neither raises nor considers protocol-specific security 138 issues. 140 5. Acknowledgments 142 Allison Mankin, Bill Fenner, Barbara Fuller, Margaret Wasserman, 143 Aaron Falk and Henrik Levkowetz all made important contributions to 144 this document. 146 6. IANA Considerations 148 This document creates no new requirements on IANA namespaces or other 149 IANA requirements. 151 7. Normative References 153 [PROTO] Falk, A., Levkowetz, H. and D. Meyer, "The PROTO Process: 154 Working Group Chair Document Shepherding", 155 Internet-Draft draft-ietf-proto-wgchair-doc-shepherding, 156 March 2005. 158 Author's Address 160 David Meyer 161 1225 Kincaid St 162 Eugene, OR 97403 163 USA 165 Phone: +1.541.346.1747 166 Email: dmm@1-4-5.net 168 Intellectual Property Statement 170 The IETF takes no position regarding the validity or scope of any 171 Intellectual Property Rights or other rights that might be claimed to 172 pertain to the implementation or use of the technology described in 173 this document or the extent to which any license under such rights 174 might or might not be available; nor does it represent that it has 175 made any independent effort to identify any such rights. Information 176 on the procedures with respect to rights in RFC documents can be 177 found in BCP 78 and BCP 79. 179 Copies of IPR disclosures made to the IETF Secretariat and any 180 assurances of licenses to be made available, or the result of an 181 attempt made to obtain a general license or permission for the use of 182 such proprietary rights by implementers or users of this 183 specification can be obtained from the IETF on-line IPR repository at 184 http://www.ietf.org/ipr. 186 The IETF invites any interested party to bring to its attention any 187 copyrights, patents or patent applications, or other proprietary 188 rights that may cover technology that may be required to implement 189 this standard. Please address the information to the IETF at 190 ietf-ipr@ietf.org. 192 Disclaimer of Validity 194 This document and the information contained herein are provided on an 195 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 196 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 197 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 198 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 199 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 200 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 202 Copyright Statement 204 Copyright (C) The Internet Society (2005). This document is subject 205 to the rights, licenses and restrictions contained in BCP 78, and 206 except as set forth therein, the authors retain all their rights. 208 Acknowledgment 210 Funding for the RFC Editor function is currently provided by the 211 Internet Society.