idnits 2.17.1 draft-klensin-recall-rev-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 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 153. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 130. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 137. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 143. ** 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. 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 : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. 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 (November 11, 2005) is 6742 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 3777 (Obsoleted by RFC 7437) Summary: 5 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Klensin 3 Internet-Draft November 11, 2005 4 Expires: May 15, 2006 6 Revision of the Recall Initiation Model 7 draft-klensin-recall-rev-00.txt 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on May 15, 2006. 34 Copyright Notice 36 Copyright (C) The Internet Society (2005). 38 Abstract 40 The procedures for initiating a recall specified in RFC 3777 restrict 41 signatories to those who are "nomcom qualified". Perhaps 42 inadvertently, this prohibits members of the IESG and IAB from 43 initiating these procedures. This document suggests that limitation 44 was an unanticipated and undesirable side-effect and proposes to 45 remove it. 47 This document is intended to update RFC 3777. 49 Table of Contents 51 1. Introduction and Rationale . . . . . . . . . . . . . . . . . . 3 52 2. Modification of the Recall Process . . . . . . . . . . . . . . 3 53 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 54 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 55 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 57 Intellectual Property and Copyright Statements . . . . . . . . . . 6 59 1. Introduction and Rationale 61 The procedures for initiating a recall specified in [RFC3777] 62 restrict signatories to those who are "nomcom qualified". Perhaps 63 inadvertently, this prohibits members of the IESG and IAB from 64 initiating these procedures. This is probably not in the best 65 interests of the community: if there is a problem within the IESG or 66 IAB, other members of those bodies are likely to be aware of it 67 before the general community. The risks of permitting IESG or IAB 68 members abusing process or each other by initiating a recall seem 69 minimal: they remain ineligible to be members of the recall committee 70 itself and the community would presumably swiftly punish such abuse 71 through either the nomcom or the recall process. 73 This document suggests that making IAB and IESG members ineligible to 74 initiate recalls was an undesirable side-effect and proposes to 75 remove it. 77 2. Modification of the Recall Process 79 The first two paragraphs of Section 7.1 of [RFC3777] are replaced by 80 the following: 82 1. At any time, at least 20 members of the IETF community, who are, 83 with the exception below, qualified to be voting members of a 84 nominating committee, may request by signed petition (email is 85 acceptable) to the Internet Society President the recall of any 86 sitting IAB or IESG member. 88 For the purposes of this section, sitting members of the IESG, IAB, 89 or Internet Society Board of Trustees may sign recall petitions. In 90 other words, Section 4.15 of RFC 3777 is not applicable in 91 determining who is permitted to sign these petitions. 93 All individual and collective qualifications of nominating committee 94 eligibility, excepting the one described in the previous paragraph, 95 are applicable, including that no more than two signatories may have 96 the same primary affiliation. 98 3. IANA Considerations 100 This document does not require any IANA actions, 102 4. Security Considerations 103 This document discusses IETF procedures. It raises no security 104 issues for the Internet. 106 5. References 108 [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and 109 Recall Process: Operation of the Nominating and Recall 110 Committees", BCP 10, RFC 3777, June 2004. 112 Author's Address 114 John C. Klensin 115 1770 Massachusetts Ave, Suite 322 116 Cambridge, MA 02140 117 USA 119 Email: john-ietf@jck.com 121 Intellectual Property Statement 123 The IETF takes no position regarding the validity or scope of any 124 Intellectual Property Rights or other rights that might be claimed to 125 pertain to the implementation or use of the technology described in 126 this document or the extent to which any license under such rights 127 might or might not be available; nor does it represent that it has 128 made any independent effort to identify any such rights. Information 129 on the procedures with respect to rights in RFC documents can be 130 found in BCP 78 and BCP 79. 132 Copies of IPR disclosures made to the IETF Secretariat and any 133 assurances of licenses to be made available, or the result of an 134 attempt made to obtain a general license or permission for the use of 135 such proprietary rights by implementers or users of this 136 specification can be obtained from the IETF on-line IPR repository at 137 http://www.ietf.org/ipr. 139 The IETF invites any interested party to bring to its attention any 140 copyrights, patents or patent applications, or other proprietary 141 rights that may cover technology that may be required to implement 142 this standard. Please address the information to the IETF at 143 ietf-ipr@ietf.org. 145 Disclaimer of Validity 147 This document and the information contained herein are provided on an 148 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 149 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 150 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 151 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 152 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 153 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 155 Copyright Statement 157 Copyright (C) The Internet Society (2005). This document is subject 158 to the rights, licenses and restrictions contained in BCP 78, and 159 except as set forth therein, the authors retain all their rights. 161 Acknowledgment 163 Funding for the RFC Editor function is currently provided by the 164 Internet Society.