idnits 2.17.1 draft-ietf-iasa2-rfc7776bis-03.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 (September 14, 2019) is 1685 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) -- Obsolete informational reference (is this intentional?): RFC 7437 (Obsoleted by RFC 8713) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 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 September 14, 2019 7 Expires: March 17, 2020 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-03 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 Administrative 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 updates 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 *** END OF NOTE *** 41 Status of This Memo 43 This Internet-Draft is submitted in full conformance with the 44 provisions of BCP 78 and BCP 79. 46 Internet-Drafts are working documents of the Internet Engineering 47 Task Force (IETF). Note that other groups may also distribute 48 working documents as Internet-Drafts. The list of current Internet- 49 Drafts is at https://datatracker.ietf.org/drafts/current/. 51 Internet-Drafts are draft documents valid for a maximum of six months 52 and may be updated, replaced, or obsoleted by other documents at any 53 time. It is inappropriate to use Internet-Drafts as reference 54 material or to cite them other than as "work in progress." 56 This Internet-Draft will expire on March 17, 2020. 58 Copyright Notice 60 Copyright (c) 2019 IETF Trust and the persons identified as the 61 document authors. All rights reserved. 63 This document is subject to BCP 78 and the IETF Trust's Legal 64 Provisions Relating to IETF Documents 65 (https://trustee.ietf.org/license-info) in effect on the date of 66 publication of this document. Please review these documents 67 carefully, as they describe your rights and restrictions with respect 68 to this document. Code Components extracted from this document must 69 include Simplified BSD License text as described in Section 4.e of 70 the Trust Legal Provisions and are provided without warranty as 71 described in the Simplified BSD License. 73 Table of Contents 75 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 76 2. Changes to RFC 7776 . . . . . . . . . . . . . . . . . . . . . 3 77 2.1. Changes to Section 3.4 . . . . . . . . . . . . . . . . . 3 78 2.2. Changes to Section 5 . . . . . . . . . . . . . . . . . . 3 79 2.3. Changes to References to RFC 7437 . . . . . . . . . . . . 4 80 2.3.1. Changes to Metadata . . . . . . . . . . . . . . . . . 4 81 2.3.2. Changes to the Abstract . . . . . . . . . . . . . . . 4 82 2.3.3. Changes to Section 5.1 . . . . . . . . . . . . . . . 5 83 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 84 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 85 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 86 5.1. Normative References . . . . . . . . . . . . . . . . . . 5 87 5.2. Informative References . . . . . . . . . . . . . . . . . 6 88 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6 89 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 91 1. Introduction 93 The IETF Anti-Harassment Procedures are described in RFC 7776 94 [RFC7776]. Those procedures include direction for the IETF Chair and 95 Ombudsteam to take advice from the IETF Administrative Oversight 96 Committee (IAOC) with respect to the budget available for training. 98 The IAOC has been replaced by the IETF Administration LLC, and the 99 IETF Administrative Director has been replaced by the IETF LLC 100 Executive Director. This document updates RFC 7776 to amend these 101 term and to update a reference. 103 RFC 7776 contained updates to [RFC7437]. [I-D.ietf-iasa2-rfc7437bis] 104 has incorporated those updates, so this document also updates RFC 105 7776 to remove those updates. 107 This document makes no other changes to the procedures described in 108 RFC 7776. 110 2. Changes to RFC 7776 112 2.1. Changes to Section 3.4 114 Section 3.4 of RFC 7776 [RFC7776] is about Qualifications and 115 Training. The last paragraph of that section is replaced as follows: 117 OLD 119 In determining the appropriate training, the IETF Chair and 120 Ombudsteam shall take professional advice and will consult with 121 the IETF Administrative Oversight Committee (IAOC) with respect to 122 the overall IETF budget. 124 NEW 126 In determining the appropriate training, the IETF Chair and 127 Ombudsteam shall take professional advice and will consult with 128 the IETF Administration LLC with respect to the overall IETF 129 budget. 131 END 133 2.2. Changes to Section 5 135 Section 5 of RFC 7776 [RFC7776] is about Remedies (available to the 136 Ombudsteam). The last paragraph of that section is replaced as 137 follows: 139 OLD 141 Where specific action is required to ensure that a remedy is 142 realized or enforced, the Ombudsteam will make a request in 143 writing to the IETF Secretariat and/or IETF Administrative 144 Director (IAD) to take action as appropriate. 146 NEW 148 Where specific action is required to ensure that a remedy is 149 realized or enforced, the Ombudsteam will make a request in 150 writing to the IETF Secretariat and/or IETF LLC Executive Director 151 to take action as appropriate. 153 END 155 2.3. Changes to References to RFC 7437 157 RFC 7776 updated RFC 7437 [RFC7437] by allowing the Obmudsteam to 158 form a recall petition. This document does not change any of the 159 associated processes, however during the process of documenting the 160 replacement of the IAOC by the IETF Administration LLC, RFC 7437 has 161 been obsoleted by [I-D.ietf-iasa2-rfc7437bis], and as part of that 162 work, [I-D.ietf-iasa2-rfc7437bis] has included the update from RFC 163 7776. 165 This document updates RFC 7776 to remove the update of RFC 7437. 167 2.3.1. Changes to Metadata 169 The following change is made to the metadata at the head of 170 [RFC7776]: 172 OLD 174 Updates: 2418, 7437 176 NEW 178 Updates: 2418 180 END 182 2.3.2. Changes to the Abstract 184 The following change is made to text in the Abstract of [RFC7776]: 186 DELETE 188 This document updates RFC 7437 by allowing the Ombudsteam to form 189 a recall petition without further signatories. 191 END 193 2.3.3. Changes to Section 5.1 195 The following change is made to text in Section 5.1 of [RFC7776] 197 OLD 199 o Many IETF management positions are appointed by the NomCom with 200 confirmation from the IESG, IAB, or ISOC. [RFC7437] describes the 201 recall procedure for such appointments. This document updates 202 [RFC7437] by allowing the Ombudsteam to form a recall petition on 203 its own and without requiring 20 signatories from the community. 204 Such a petition shall be treated in all ways like any other recall 205 petition as described in [RFC7437]: that is, the fact of the 206 petition and its signatories (the Ombudsteam) shall be announced 207 to the IETF community, and a Recall Committee Chair shall be 208 appointed to complete the Recall Committee process. It is 209 expected that the Recall Committee will receive a briefing from 210 the Ombudsteam explaining why recall is considered an appropriate 211 remedy. 213 NEW 215 o The Ombudsteam may form a recall petition on its own without 216 requiring signatures from the community as described in 217 [I-D.ietf-iasa2-rfc7437bis]. 219 END 221 3. IANA Considerations 223 This document makes no request for IANA action. 225 4. Security Considerations 227 This document has no implications for Internet security. 229 5. References 231 5.1. Normative References 233 [I-D.ietf-iasa2-rfc7437bis] 234 Kucherawy, M., Hinden, R., and J. Livingood, "IAB, IESG, 235 IETF Trust and IETF LLC Selection, Confirmation, and 236 Recall Process: Operation of the IETF Nominating and 237 Recall Committees", draft-ietf-iasa2-rfc7437bis-09 (work 238 in progress), July 2019. 240 [RFC7776] Resnick, P. and A. Farrel, "IETF Anti-Harassment 241 Procedures", BCP 25, RFC 7776, DOI 10.17487/RFC7776, March 242 2016, . 244 5.2. Informative References 246 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 247 Confirmation, and Recall Process: Operation of the 248 Nominating and Recall Committees", BCP 10, RFC 7437, 249 DOI 10.17487/RFC7437, January 2015, 250 . 252 Appendix A. Acknowledgements 254 Thanks to Jason Livingwood for suggesting the need for this document. 256 Subramanian Moonesamy, Sean Turner, Jon Peterson, Roman Danyliw, and 257 Barry Leiba raised useful points during their reviews of this work. 259 Authors' Addresses 261 Pete Resnick 262 Episteme Technology Consulting LLC 263 503 West Indiana Avenue 264 Urbana, Illinois 61801-4941 265 United States 267 Phone: +1 217 337 1905 268 Email: resnick@episteme.net 270 Adrian Farrel 271 Old Dog Consulting 273 Email: adrian@olddog.co.uk