idnits 2.17.1 draft-ietf-iasa2-rfc7776bis-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 5, 2019) is 1847 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-09) exists of draft-ietf-iasa2-rfc7437bis-06 -- Obsolete informational reference (is this intentional?): RFC 7437 (Obsoleted by RFC 8713) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IASA 2.0 P. Resnick 3 Internet-Draft Episteme Technology Consulting LLC 4 BCP: 25 A. Farrel 5 Updates: 7776 (if approved) Old Dog Consulting 6 Intended status: Best Current Practice April 5, 2019 7 Expires: October 7, 2019 9 Update to the IETF Anti-Harassment Procedures for the Replacement of the 10 IAOC with the IETF Administration LLC 11 draft-ietf-iasa2-rfc7776bis-02 13 Abstract 15 The IETF Anti-Harassment Procedures are described in RFC 7776. 17 The IETF Administrative Oversight Committee (IAOC) has been replaced 18 by the IETF Administration LLC, and the IETF Adminstrative Director 19 has been replaced by the IETF LLC Executive Director. This document 20 updates RFC 7776 to amend these terms. 22 RFC 7776 contained updated to RFC 7437. draft-ietf-iasa2-rfc7437bis 23 has incorporated those updates, so this document also updates RFC 24 7776 to remove those updates. 26 NOTE for RFC Editor and Readers of this Document 28 When published as an RFC 30 o All references to and mentions of draft-ietf-iasa2-rfc7437bis in 31 this document should be replaced by the RFC that results from 32 draft-ietf-iasa2-rfc7437bis. 34 o The string "XXXX" should be replaced with the RFC number assigned 35 to the RFC that results from draft-ietf-iasa2-rfc7437bis. 37 o This note should be removed. 39 Status of This Memo 41 This Internet-Draft is submitted in full conformance with the 42 provisions of BCP 78 and BCP 79. 44 Internet-Drafts are working documents of the Internet Engineering 45 Task Force (IETF). Note that other groups may also distribute 46 working documents as Internet-Drafts. The list of current Internet- 47 Drafts is at https://datatracker.ietf.org/drafts/current/. 49 Internet-Drafts are draft documents valid for a maximum of six months 50 and may be updated, replaced, or obsoleted by other documents at any 51 time. It is inappropriate to use Internet-Drafts as reference 52 material or to cite them other than as "work in progress." 54 This Internet-Draft will expire on October 7, 2019. 56 Copyright Notice 58 Copyright (c) 2019 IETF Trust and the persons identified as the 59 document authors. All rights reserved. 61 This document is subject to BCP 78 and the IETF Trust's Legal 62 Provisions Relating to IETF Documents 63 (https://trustee.ietf.org/license-info) in effect on the date of 64 publication of this document. Please review these documents 65 carefully, as they describe your rights and restrictions with respect 66 to this document. Code Components extracted from this document must 67 include Simplified BSD License text as described in Section 4.e of 68 the Trust Legal Provisions and are provided without warranty as 69 described in the Simplified BSD License. 71 Table of Contents 73 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 74 2. Changes to RFC 7776 . . . . . . . . . . . . . . . . . . . . . 3 75 2.1. Changes to Section 3.4 . . . . . . . . . . . . . . . . . 3 76 2.2. Changes to Section 5 . . . . . . . . . . . . . . . . . . 3 77 2.3. Changes to References to RFC 7437 . . . . . . . . . . . . 4 78 2.3.1. Changes to Metadata . . . . . . . . . . . . . . . . . 4 79 2.3.2. Changes to the Abstract . . . . . . . . . . . . . . . 4 80 2.3.3. Changes to Section 5.1 . . . . . . . . . . . . . . . 4 81 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 82 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 83 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 84 5.1. Normative References . . . . . . . . . . . . . . . . . . 5 85 5.2. Informative References . . . . . . . . . . . . . . . . . 5 86 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6 87 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 89 1. Introduction 91 The IETF Anti-Harassment Procedures are described in RFC 7776 92 [RFC7776]. Those procedures include direction for the IETF Chair and 93 Ombudsteam to take advice from the IETF Administrative Oversight 94 Committee (IAOC) with respect to the budget available for training. 96 The IAOC has been replaced by the IETF Administration LLC, and the 97 IETF Adminstrative Director has been replaced by the IETF LLC 98 Executive Director. This document updates RFC 7776 to amend these 99 term and to update a reference. 101 RFC 7776 contained updated to [RFC7437]. [I-D.ietf-iasa2-rfc7437bis] 102 has incorporated those updates, so this document also updates RFC 103 7776 to remove those updates. 105 This document makes no other changes to the procedures described in 106 RFC 7776. 108 2. Changes to RFC 7776 110 2.1. Changes to Section 3.4 112 Section 3.4 of RFC 7776 [RFC7776] is about Qualifications and 113 Training. The last paragraph of that section is replaced as follows: 115 OLD 117 In determining the appropriate training, the IETF Chair and 118 Ombudsteam shall take professional advice and will consult with 119 the IETF Administrative Oversight Committee (IAOC) with respect to 120 the overall IETF budget. 122 NEW 124 In determining the appropriate training, the IETF Chair and 125 Ombudsteam shall take professional advice and will consult with 126 the IETF Administration LLC with respect to the overall IETF 127 budget. 129 2.2. Changes to Section 5 131 Section 5 of RFC 7776 [RFC7776] is about Remedies (available to the 132 Ombudsteam). The last paragraph of that section is replaced as 133 follows: 135 OLD 137 Where specific action is required to ensure that a remedy is 138 realized or enforced, the Ombudsteam will make a request in 139 writing to the IETF Secretariat and/or IETF Administrative 140 Director (IAD) to take action as appropriate. 142 NEW 143 Where specific action is required to ensure that a remedy is 144 realized or enforced, the Ombudsteam will make a request in 145 writing to the IETF Secretariat and/or IETF LLC Executive Director 146 to take action as appropriate. 148 2.3. Changes to References to RFC 7437 150 RFC 7776 updated RFC 7437 [RFC7437] by allowing the obmudsteam to 151 form a recall petition. This document does not change any of the 152 associated processes, however during the process of documenting the 153 replacement of the IAOC by the IETF Administration LLC, RFC 7437 has 154 been obsoleted by [I-D.ietf-iasa2-rfc7437bis], and as part of that 155 work, [I-D.ietf-iasa2-rfc7437bis] has included the update from RFC 156 7776. 158 This document updates RFC 7776 to remove the update of RFC 7437. 160 2.3.1. Changes to Metadata 162 The following change is made to the metadata at the head of 163 [RFC7776]: 165 OLD 167 Updates: 2418, 7437 169 NEW 171 Updates: 2418 173 2.3.2. Changes to the Abstract 175 The following change is made to text in the Abstract of [RFC7776]: 177 DELETE 179 This document updates RFC 7437 by allowing the Ombudsteam to form 180 a recall petition without further signatories. 182 END 184 2.3.3. Changes to Section 5.1 186 The following change is made to text in Section 5.1 of [RFC7776] 188 OLD 189 o Many IETF management positions are appointed by the NomCom with 190 confirmation from the IESG, IAB, or ISOC. [RFC7437] describes the 191 recall procedure for such appointments. This document updates 192 [RFC7437] by allowing the Ombudsteam to form a recall petition on 193 its own and without requiring 20 signatories from the community. 194 Such a petition shall be treated in all ways like any other recall 195 petition as described in [RFC7437]: that is, the fact of the 196 petition and its signatories (the Ombudsteam) shall be announced 197 to the IETF community, and a Recall Committee Chair shall be 198 appointed to complete the Recall Committee process. It is 199 expected that the Recall Committee will receive a briefing from 200 the Ombudsteam explaining why recall is considered an appropriate 201 remedy. 203 NEW 205 o The Ombudsteam may form a recall petition on its own without 206 requiring signatures from the community as described in 207 [I-D.ietf-iasa2-rfc7437bis]. 209 3. IANA Considerations 211 This document makes no request for IANA action. 213 4. Security Considerations 215 This document has no implications for Internet security. 217 5. References 219 5.1. Normative References 221 [I-D.ietf-iasa2-rfc7437bis] 222 Kucherawy, M., Hinden, R., and J. Livingood, "IAB, IESG, 223 IETF Trust and IETF LLC Selection, Confirmation, and 224 Recall Process: Operation of the IETF Nominating and 225 Recall Committees", draft-ietf-iasa2-rfc7437bis-06 (work 226 in progress), March 2019. 228 [RFC7776] Resnick, P. and A. Farrel, "IETF Anti-Harassment 229 Procedures", BCP 25, RFC 7776, DOI 10.17487/RFC7776, March 230 2016, . 232 5.2. Informative References 234 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 235 Confirmation, and Recall Process: Operation of the 236 Nominating and Recall Committees", BCP 10, RFC 7437, 237 DOI 10.17487/RFC7437, January 2015, 238 . 240 Appendix A. Acknowledgements 242 Thanks to Jason Livingwood for suggesting the need for this document. 244 Subramanian Moonesamy and Sean Turner raised useful points during 245 their reviews of this work. 247 Authors' Addresses 249 Pete Resnick 250 Episteme Technology Consulting LLC 251 503 West Indiana Avenue 252 Urbana, Illinois 61801-4941 253 United States 255 Phone: +1 217 337 1905 256 Email: resnick@episteme.net 258 Adrian Farrel 259 Old Dog Consulting 261 Email: adrian@olddog.co.uk