RFC 8090

📜 RFC 8090: Appointment Procedures for the IETF Representatives to the Community Coordination Group (CCG) 💖

okay bestie, let's get into this one 🫶 first, the title block, because it's the tea ☕

• Number and title: RFC 8090, Appointment Procedures for the IETF Representatives to the Community Coordination Group (CCG) 🎀
• Published by: the Internet Architecture Board (IAB) 👑
• Author: R. Housley of Vigil Security 🦋
• Category: Informational, so this is NOT a standards-track spec 💅
• Date: February 2017 🌸
• ISSN: 2070-1721 ✨
• Obsoletes and updates: the title block doesn't list anything here, so there's nothing it replaces or changes 🙈

the abstract is basically: this doc explains how the IETF picks people for the Community Coordination Group (CCG), which gives advice to the IETF Trust about the IANA trademarks and IANA domain names 🧚

---

Status of This Memo ✨

okay so this section is giving "this is informational, not a standard" energy 💅 it's an IAB document that's basically going on the permanent record, and it reflects what the IAB agreed on 🌈 IAB-approved docs can't become any level of Internet Standard, and you can read Section 2 of RFC 7841 for that 🦋

for the current status, errata, and feedback, go to http://www.rfc-editor.org/info/rfc8090 💖

Copyright Notice 🎀

copyright is 2017, IETF Trust and the authors, all rights reserved 🔒 this doc is under BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as of publication, so read those carefully because they spell out your rights and restrictions 🫶

Table of Contents 🌸

1. Introduction ................................................... 2
2. Desirable Qualifications for CCG Representatives ............... 3
3. CCG Representative Selection Procedures ........................ 3
   3.1. Duration of Appointment ................................... 3
   3.2. Nominations and Eligibility ............................... 3
   3.3. Selection ................................................. 4
4. CCG Representative Removal Procedures .......................... 4
5. CCG Representative Co-Chair Selection Procedures ............... 5
6. Initial Appointments ........................................... 5
7. Reporting by the CCG Representatives to the IAB ................ 5
8. IANA Considerations ............................................ 6
9. Security Considerations ........................................ 6
10. Informative References ........................................ 6
IAB Members at the Time of Approval ............................... 6
Acknowledgements .................................................. 7
Author's Address .................................................. 7

1. Introduction 🧚

okay so the "IANA IPR Community Agreement" [1] was one of the big docs in the IANA Stewardship Transition 💅 it's what created the Community Coordination Group (CCG), whose whole job is giving guidance and advice to the IETF Trust about stewarding the IANA Intellectual Property, which means the IANA trademarks and the IANA domain names ✨

the CCG has nine people called CCG Representatives 🎀 the three operational communities (the Names Community, the Numbers Community, and the Protocol Parameters Community) each pick three of them 👑 each community can change any of its reps whenever it wants, as long as it gives written notice to the other communities and the IETF Trust 🦋 a community can remove or replace its reps at any time, totally at its own discretion, and how it picks, appoints, and removes its reps is up to that community alone 💖

each community also appoints one rep as CCG co-chair 🌈 that co-chair can speak for their community about the IANA Intellectual Property 🫶 they can change the co-chair with written notice too, and again the community can remove or replace it at any time at its sole discretion 🌸

so this doc is about how the IETF picks, appoints, and removes the three CCG Reps for the Protocol Parameter Community 🔥 it also covers how the co-chair gets chosen from those three 💅

2. Desirable Qualifications for CCG Representatives 💜

candidates for the Protocol Parameters Community CCG Rep should have demonstrable involvement in the IETF and a solid understanding of the many ways the IETF uses protocol parameter registries 🦋 they should also know how the IETF community depends on the IANA trademarks and IANA domain names 🎀

candidates are expected to be able to call on others in the IETF community, as needed, so the IETF Trust gets the highest quality advice available ✨

candidates are also expected to have clearly demonstrated technical competence in managing IANA protocol parameter registries 🔥 and they should understand how the Names Community and the Numbers Community use IANA registries too 👑

3. CCG Representative Selection Procedures 🌈

the three CCG Reps for the Protocol Parameters Community serve at the pleasure of the IAB 🫶

3.1. Duration of Appointment 🌸

each CCG Rep is expected to serve for at least a year 🦋 appointments ought to be staggered so they don't all get replaced at the same time 💖 every year the IAB asks the IETF community for input on whether a personnel change makes sense 🧚

3.2. Nominations and Eligibility 🎀

when the IAB decides to appoint a new CCG Rep, it will make a public call for nominations on the ietf-announce@ietf.org mailing list ✨ the call will say how nominations are accepted and how the nominee list gets published for IETF community feedback 💅 self-nominations are permitted 👑

each nomination must include the name and contact information of each candidate 🔥 the candidate's background and qualifications for the job should be included with the nomination too 🌈 trustees of the IETF Trust are not eligible for nomination 🦋 everyone else in the IETF, including working group chairs, IETF NomCom members, IAB members, and IESG members, is eligible 💜

IAB members who accept a nomination shall recuse themselves from selection discussions 🙈

3.3. Selection 💖

the IAB will publish the list of people who accepted their nomination or nominated themselves 🌸 the IAB considers IETF community feedback when it makes a selection, and it keeps that feedback confidential 🔒

the IAB will also consider potential conflicts with a CCG Rep position and any other positions the nominated candidates hold 🦋

after weighing the community feedback, potential conflicts, and any other appropriate info that's available, the IAB shall vote to select the best qualified CCG Rep ✨

4. CCG Representative Removal Procedures 🔥

if there are concerns about how an IAB-appointed CCG Rep is performing, the IETF community can ask the IAB to consider removal 👑 that request must be sent by email to iab-chair@iab.org 💅

the request must include a statement justifying the removal, including all relevant and appropriate supporting documentation 🫶

the IAB shall respond to the request within six weeks ⭐ if an IAB member holds any CCG Rep position, no matter which operational community they represent, that IAB member shall be recused from any investigation, discussion, and vote about what to do 🙈

if the CCG Rep gets removed, the open spot gets filled according to Section 3 of this document 🌈

5. CCG Representative Co-Chair Selection Procedures 🦋

whenever the list of people serving as CCG Reps for the Protocol Parameters Community changes, the sitting reps shall use a procedure of their own choosing to pick the co-chair 💖 the co-chair selection shall be confirmed by the IAB, and then the IAB shall announce it to the IETF community, the IETF Trust, and the CCG Reps from the other operational communities 🧚

at any time, for any reason, the list of people serving as CCG Reps for the Protocol Parameters Community may revisit the co-chair selection 🎀 if they pick someone different, that new selection shall be confirmed by the IAB, and then the IAB shall announce it to the same groups 🌸

as part of confirmation, the IAB shall consider potential conflicts of interest for the co-chair candidate ✨

6. Initial Appointments 🌈

okay this part is a throwback 🥹 three CCG Reps had to be in place at midnight on 30 September 2016 when the IANA Stewardship Transition happened, so the IAB quickly appointed three people who were heavily involved in the transition 💅 those three agreed to serve until the appointment procedures could be adopted and used 👑

using the procedures in this doc, the IAB will appoint three CCG Reps before the second IETF meeting in 2017 🔥

to encourage staggered replacement, at least one of those appointed will be replaced before the second IETF meeting in 2018, which is one year after the first set of CCG Reps is appointed through this process 🫶

7. Reporting by the CCG Representatives to the IAB 💜

CCG Reps shall deliver reports to the IAB within a reasonable time frame, and whenever possible that should give the chance to get advice on open IANA Intellectual Property issues 🦋 no specific reporting time periods are mandated, but CCG Reps are expected to keep the IAB informed of CCG activities 💖

reports from the CCG Reps will be made publicly available, except for comments about individuals 🙈 they'll typically be part of the minutes of the IAB meeting where they're discussed 🧚

8. IANA Considerations 🎀

this document does not require any IANA actions ✨

9. Security Considerations 🔥

okay bestie, this section is short but it's giving "nothing to see here" 💅 this doc does not describe any technical protocols and has no implications for network security 👑

10. Informative References 🌈

[1] IETF Trust, "IANA IPR Community Agreement", 21 September 2016, https://trustee.ietf.org/documents/Community-Agreement-09-21-2016clean.pdf.

---

This is part 1 of 2. Part 2 picks up with the IAB Members at the Time of Approval, Acknowledgements, and Author's Address. Stay tuned, bestie 🫶✨

Acknowledgements 🙏✨

Okay bestie, huge thank-yous go to Ted Hardie, Alissa Cooper, Brian Carpenter, Andrew Sullivan, Dave Crocker, John Klensin, Dave Thaler, and Martin Thomson 🫶. They reviewed the document and left valuable comments, and the whole thing is so much better because of them 💜.

Author's Address 🎀

The author is Russ Housley, and you can reach him at the details below 💌.

Russ Housley
918 Spring Knoll Drive
Herndon, VA  20170
USA

Email: housley@vigilsec.com

That's the whole document, we made it! 🌈💖