draft-ietf-iasa2-rfc7776bis-03.txt   rfc8716.txt 
IASA 2.0 P. Resnick Internet Engineering Task Force (IETF) P. Resnick
Internet-Draft Episteme Technology Consulting LLC Request for Comments: 8716 Episteme Technology Consulting LLC
BCP: 25 A. Farrel BCP: 25 A. Farrel
Updates: 7776 (if approved) Old Dog Consulting Updates: 7776 Old Dog Consulting
Intended status: Best Current Practice September 14, 2019 Category: Best Current Practice February 2020
Expires: March 17, 2020 ISSN: 2070-1721
Update to the IETF Anti-Harassment Procedures for the Replacement of the Update to the IETF Anti-Harassment Procedures for the Replacement of the
IAOC with the IETF Administration LLC IETF Administrative Oversight Committee (IAOC) with the IETF
draft-ietf-iasa2-rfc7776bis-03 Administration LLC
Abstract Abstract
The IETF Anti-Harassment Procedures are described in RFC 7776. The IETF Anti-Harassment Procedures are described in RFC 7776.
The IETF Administrative Oversight Committee (IAOC) has been replaced The IETF Administrative Oversight Committee (IAOC) has been replaced
by the IETF Administration LLC, and the IETF Administrative Director by the IETF Administration LLC, and the IETF Administrative Director
has been replaced by the IETF LLC Executive Director. This document has been replaced by the IETF LLC Executive Director. This document
updates RFC 7776 to amend these terms. updates RFC 7776 to amend these terms.
RFC 7776 contained updates to RFC 7437. draft-ietf-iasa2-rfc7437bis RFC 7776 contained updates to RFC 7437. RFC 8713 has incorporated
has incorporated those updates, so this document also updates RFC those updates, so this document also updates RFC 7776 to remove those
7776 to remove those updates. updates.
NOTE for RFC Editor and Readers of this Document
When published as an RFC
o All references to and mentions of draft-ietf-iasa2-rfc7437bis in
this document should be replaced by the RFC that results from
draft-ietf-iasa2-rfc7437bis.
o The string "XXXX" should be replaced with the RFC number assigned
to the RFC that results from draft-ietf-iasa2-rfc7437bis.
o This note should be removed.
*** END OF NOTE ***
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This memo documents an Internet Best Current Practice.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 7841.
This Internet-Draft will expire on March 17, 2020. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8716.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction
2. Changes to RFC 7776 . . . . . . . . . . . . . . . . . . . . . 3 2. Changes to RFC 7776
2.1. Changes to Section 3.4 . . . . . . . . . . . . . . . . . 3 2.1. Changes to Section 3.4
2.2. Changes to Section 5 . . . . . . . . . . . . . . . . . . 3 2.2. Changes to Section 5
2.3. Changes to References to RFC 7437 . . . . . . . . . . . . 4 2.3. Changes to References to RFC 7437
2.3.1. Changes to Metadata . . . . . . . . . . . . . . . . . 4 2.3.1. Changes to Metadata
2.3.2. Changes to the Abstract . . . . . . . . . . . . . . . 4 2.3.2. Changes to the Abstract
2.3.3. Changes to Section 5.1 . . . . . . . . . . . . . . . 5 2.3.3. Changes to Section 5.1
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 3. IANA Considerations
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. References
5.1. Normative References . . . . . . . . . . . . . . . . . . 5 5.1. Normative References
5.2. Informative References . . . . . . . . . . . . . . . . . 6 5.2. Informative References
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6 Acknowledgements
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses
1. Introduction 1. Introduction
The IETF Anti-Harassment Procedures are described in RFC 7776 The IETF Anti-Harassment Procedures are described in RFC 7776
[RFC7776]. Those procedures include direction for the IETF Chair and [RFC7776]. Those procedures include direction for the IETF Chair and
Ombudsteam to take advice from the IETF Administrative Oversight Ombudsteam to take advice from the IETF Administrative Oversight
Committee (IAOC) with respect to the budget available for training. Committee (IAOC) with respect to the budget available for training.
The IAOC has been replaced by the IETF Administration LLC, and the The IAOC has been replaced by the IETF Administration LLC, and the
IETF Administrative Director has been replaced by the IETF LLC IETF Administrative Director has been replaced by the IETF LLC
Executive Director. This document updates RFC 7776 to amend these Executive Director. This document updates RFC 7776 to amend these
term and to update a reference. terms and to update a reference.
RFC 7776 contained updates to [RFC7437]. [I-D.ietf-iasa2-rfc7437bis] RFC 7776 contained updates to [RFC7437]. [RFC8713] has incorporated
has incorporated those updates, so this document also updates RFC those updates, so this document also updates RFC 7776 to remove those
7776 to remove those updates. updates.
This document makes no other changes to the procedures described in This document makes no other changes to the procedures described in
RFC 7776. RFC 7776.
2. Changes to RFC 7776 2. Changes to RFC 7776
2.1. Changes to Section 3.4 2.1. Changes to Section 3.4
Section 3.4 of RFC 7776 [RFC7776] is about Qualifications and Section 3.4 of [RFC7776] is about the qualifications and training of
Training. The last paragraph of that section is replaced as follows: the Ombudsteam. The last paragraph of that section is replaced as
follows:
OLD OLD
In determining the appropriate training, the IETF Chair and | In determining the appropriate training, the IETF Chair and
Ombudsteam shall take professional advice and will consult with | Ombudsteam shall take professional advice and will consult with
the IETF Administrative Oversight Committee (IAOC) with respect to | the IETF Administrative Oversight Committee (IAOC) with respect to
the overall IETF budget. | the overall IETF budget.
NEW NEW
In determining the appropriate training, the IETF Chair and | In determining the appropriate training, the IETF Chair and
Ombudsteam shall take professional advice and will consult with | Ombudsteam shall take professional advice and will consult with
the IETF Administration LLC with respect to the overall IETF | the IETF Administration LLC with respect to the overall IETF
budget. | budget.
END END
2.2. Changes to Section 5 2.2. Changes to Section 5
Section 5 of RFC 7776 [RFC7776] is about Remedies (available to the Section 5 of [RFC7776] is about remedies available to the Ombudsteam.
Ombudsteam). The last paragraph of that section is replaced as The last paragraph of that section is replaced as follows:
follows:
OLD OLD
Where specific action is required to ensure that a remedy is | Where specific action is required to ensure that a remedy is
realized or enforced, the Ombudsteam will make a request in | realized or enforced, the Ombudsteam will make a request in
writing to the IETF Secretariat and/or IETF Administrative | writing to the IETF Secretariat and/or IETF Administrative
Director (IAD) to take action as appropriate. | Director (IAD) to take action as appropriate.
NEW NEW
Where specific action is required to ensure that a remedy is | Where specific action is required to ensure that a remedy is
realized or enforced, the Ombudsteam will make a request in | realized or enforced, the Ombudsteam will make a request in
writing to the IETF Secretariat and/or IETF LLC Executive Director | writing to the IETF Secretariat and/or IETF LLC Executive Director
to take action as appropriate. | to take action as appropriate.
END END
2.3. Changes to References to RFC 7437 2.3. Changes to References to RFC 7437
RFC 7776 updated RFC 7437 [RFC7437] by allowing the Obmudsteam to RFC 7776 updated RFC 7437 [RFC7437] by allowing the Ombudsteam to
form a recall petition. This document does not change any of the form a recall petition. This document does not change any of the
associated processes, however during the process of documenting the associated processes. However, during the process of documenting the
replacement of the IAOC by the IETF Administration LLC, RFC 7437 has replacement of the IAOC by the IETF Administration LLC, RFC 7437 has
been obsoleted by [I-D.ietf-iasa2-rfc7437bis], and as part of that been obsoleted by [RFC8713], and as part of that work, [RFC8713] has
work, [I-D.ietf-iasa2-rfc7437bis] has included the update from RFC included the update from RFC 7776.
7776.
This document updates RFC 7776 to remove the update of RFC 7437. This document updates RFC 7776 to remove the update of RFC 7437.
2.3.1. Changes to Metadata 2.3.1. Changes to Metadata
The following change is made to the metadata at the head of The following change is made to the metadata at the head of
[RFC7776]: [RFC7776]:
OLD OLD
Updates: 2418, 7437 | Updates: 2418, 7437
NEW NEW
Updates: 2418 | Updates: 2418
END END
2.3.2. Changes to the Abstract 2.3.2. Changes to the Abstract
The following change is made to text in the Abstract of [RFC7776]: The following change is made to text in the Abstract of [RFC7776]:
DELETE DELETE
This document updates RFC 7437 by allowing the Ombudsteam to form | This document updates RFC 7437 by allowing the Ombudsteam to form
a recall petition without further signatories. | a recall petition without further signatories.
END END
2.3.3. Changes to Section 5.1 2.3.3. Changes to Section 5.1
The following change is made to text in Section 5.1 of [RFC7776] The following change is made to text in Section 5.1 of [RFC7776]:
OLD OLD
o Many IETF management positions are appointed by the NomCom with | * Many IETF management positions are appointed by the NomCom with
confirmation from the IESG, IAB, or ISOC. [RFC7437] describes the | confirmation from the IESG, IAB, or ISOC. [RFC7437] describes
recall procedure for such appointments. This document updates | the recall procedure for such appointments. This document
[RFC7437] by allowing the Ombudsteam to form a recall petition on | updates [RFC7437] by allowing the Ombudsteam to form a recall
its own and without requiring 20 signatories from the community. | petition on its own and without requiring 20 signatories from
Such a petition shall be treated in all ways like any other recall | the community. Such a petition shall be treated in all ways
petition as described in [RFC7437]: that is, the fact of the | like any other recall petition as described in [RFC7437]: that
petition and its signatories (the Ombudsteam) shall be announced | is, the fact of the petition and its signatories (the
to the IETF community, and a Recall Committee Chair shall be | Ombudsteam) shall be announced to the IETF community, and a
appointed to complete the Recall Committee process. It is | Recall Committee Chair shall be appointed to complete the
expected that the Recall Committee will receive a briefing from | Recall Committee process. It is expected that the Recall
the Ombudsteam explaining why recall is considered an appropriate | Committee will receive a briefing from the Ombudsteam
remedy. | explaining why recall is considered an appropriate remedy.
NEW NEW
o The Ombudsteam may form a recall petition on its own without | * The Ombudsteam may form a recall petition on its own without
requiring signatures from the community as described in | requiring signatures from the community as described in
[I-D.ietf-iasa2-rfc7437bis]. | [RFC8713].
END END
3. IANA Considerations 3. IANA Considerations
This document makes no request for IANA action. This document has no IANA actions.
4. Security Considerations 4. Security Considerations
This document has no implications for Internet security. This document has no implications for Internet security.
5. References 5. References
5.1. Normative References 5.1. Normative References
[I-D.ietf-iasa2-rfc7437bis]
Kucherawy, M., Hinden, R., and J. Livingood, "IAB, IESG,
IETF Trust and IETF LLC Selection, Confirmation, and
Recall Process: Operation of the IETF Nominating and
Recall Committees", draft-ietf-iasa2-rfc7437bis-09 (work
in progress), July 2019.
[RFC7776] Resnick, P. and A. Farrel, "IETF Anti-Harassment [RFC7776] Resnick, P. and A. Farrel, "IETF Anti-Harassment
Procedures", BCP 25, RFC 7776, DOI 10.17487/RFC7776, March Procedures", BCP 25, RFC 7776, DOI 10.17487/RFC7776, March
2016, <https://www.rfc-editor.org/info/rfc7776>. 2016, <https://www.rfc-editor.org/info/rfc7776>.
[RFC8713] Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood,
Ed., "IAB, IESG, and IETF LLC Selection, Confirmation, and
Recall Process: Operation of the IETF Nominating and
Recall Committees", BCP 10, RFC 8713,
DOI 10.17487/RFC8713, February 2020,
<https://www.rfc-editor.org/info/rfc8713>.
5.2. Informative References 5.2. Informative References
[RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection,
Confirmation, and Recall Process: Operation of the Confirmation, and Recall Process: Operation of the
Nominating and Recall Committees", BCP 10, RFC 7437, Nominating and Recall Committees", BCP 10, RFC 7437,
DOI 10.17487/RFC7437, January 2015, DOI 10.17487/RFC7437, January 2015,
<https://www.rfc-editor.org/info/rfc7437>. <https://www.rfc-editor.org/info/rfc7437>.
Appendix A. Acknowledgements Acknowledgements
Thanks to Jason Livingwood for suggesting the need for this document. Thanks to Jason Livingood for suggesting the need for this document.
Subramanian Moonesamy, Sean Turner, Jon Peterson, Roman Danyliw, and Subramanian Moonesamy, Sean Turner, Jon Peterson, Roman Danyliw, and
Barry Leiba raised useful points during their reviews of this work. Barry Leiba raised useful points during their reviews of this work.
Authors' Addresses Authors' Addresses
Pete Resnick Pete Resnick
Episteme Technology Consulting LLC Episteme Technology Consulting LLC
503 West Indiana Avenue 503 West Indiana Avenue
Urbana, Illinois 61801-4941 Urbana, Illinois 61801-4941
United States United States of America
Phone: +1 217 337 1905 Phone: +1 217 337 1905
Email: resnick@episteme.net Email: resnick@episteme.net
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
 End of changes. 32 change blocks. 
116 lines changed or deleted 97 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/