| iana-program-old.txt | iana-program-new-alternative2b.txt | |||
|---|---|---|---|---|
| IANA Program | IETF-IANA Group | |||
| Purpose | Purpose | |||
| The IANA program’s primary focus is the stewardship over the IANA | The background for the IETF-IANA group are the IANA functions for the | |||
| functions for the Internet in General and the IETF in particular. | Internet and the IETF, as specified in the IANA MoU (RFC2860) and | |||
| related agreements between stakeholders. At the IETF, the formal | ||||
| Its main focus is on: | responsibility for the relationship lies in four entities: | |||
| * the IANA MoU (RFC2860) and related agreements between stakeholders; | ||||
| * maintaining a vision of the role of the IANA functions; and | ||||
| * implementation and interpretation of the above. | ||||
| The program acts also as a think-tank and advises the IAB on strategic | ||||
| and liaison issues. | ||||
| In some cases this group may provide guidance and insight on matters | * The IAB that is tasked with IANA oversight | |||
| relating ICANN in general. | * The LLC that is tasked with managing the contracts | |||
| * The IETF Trust that holds the rights for related domains and trademarks | ||||
| * The CCG, which provides advice and guidance to the IETF Trust | ||||
| The group is not responsible for daily operational guidance, and does | Today, the IANA functions are provided by Public Technical Identifiers | |||
| not have any formal role in contracts relating to the IANA functions. | (PTI), a purpose-built organization for providing the IANA functions | |||
| to the community. PTI is an affiliate of ICANN. | ||||
| Work Items | The IETF-IANA group organizes regular meetings to provide advice, | |||
| primarily to the IAB and PTI. The group has participants from both | ||||
| IETF and PTI sides. The group is expected to review the publicly | ||||
| available IANA performance statistics, discuss specific issues that | ||||
| have come up in the protocol parameter service, provide input on | ||||
| proposed yearly updates to the IANA Functions SLA, or any other | ||||
| similar topics. | ||||
| The group focuses on the following high-level work items and responsibilities: | However, the group is not responsible for daily operational | |||
| guidance, and does not have any formal role in contracts relating to | ||||
| the IANA functions. The advice that it provides is input to the | ||||
| relevant entities that perform IANA functions (PTI) or provide | ||||
| oversight (the IAB), but may indirectly be useful also for those in | ||||
| charge of contract management on either side. | ||||
| * Tracking the developments surrounding the IANA functions and their use in the Internet ecosystem | The group co-leads will review and update membership yearly | |||
| * Responding to specific developments and information requests on this topic | together with the IAB. | |||
| Results and References | Results and References | |||
| * IANA MoU | * RFC 2860: IANA MoU | |||
| * RFC 6220: Defining the Role and Function of IETF Protocol Parameter Registry Operator | ||||
| * RFC 7500: Principles for Operation of Internet Assigned Numbers Authority (IANA) Registries | ||||
| * RFC 8090: Appointment Procedures for the IETF Representatives to the Community Coordination Group (CCG) | ||||
| * IETF Trust agreement on IANA | * IETF Trust agreement on IANA | |||
| * Appointment Procedures for the IETF Representatives to the Community Coordination Group (CCG) | ||||
| * IAB response to the IANA NOI | ||||
| * Defining the Role and Function of IETF Protocol Parameter Registry Operator (RFC6220) | ||||
| * ICANN-IETF Service Level Agreements | * ICANN-IETF Service Level Agreements | |||
| * ICANN performance evaluation | ||||
| * Information on IANA performance | * Information on IANA performance | |||
| * IANA oversight statement by IETF Administrative Director | ||||
| * RFC 7500: Principles for Operation of Internet Assigned Numbers Authority (IANA) Registries | ||||
| * Comments on RDAP Operational Profile for gTLD Registries and Registrars | ||||
| * Comments on the CCWG-Accountability 3rd Draft Report | ||||
| * Comments on the CCWG-Accountability 2nd Draft Report | ||||
| * Comments on the ICG Proposal | ||||
| * Comments on the CCWG-Accountability 1st Draft Report | ||||
| * Statement on the NETmundial Initiative | ||||
| * Evolution on the IANA Protocol Parameter Registries | ||||
| Members | Members | |||
| IAB Members | * Michelle Cotton (Group co-Lead & PTI Protocol Parameters Engagement Sr. Manager) | |||
| * Russ Housley (Group co-Lead) | ||||
| * Jari Arkko (IAB Lead) | * Jari Arkko (IAB Lead) | |||
| * Alissa Cooper | * Mirja Kühlewind (IAB Chair) | |||
| * Ted Hardie | * Alissa Cooper (IETF Chair) | |||
| * Mirja Kühlewind | * Lars Eggert (Incoming IETF Chair) | |||
| * Jay Daley (LLC Executive Director) | ||||
| Non-IAB Members | * Kim Davies (PTI President) | |||
| * Harald Alvestrand (IETF-ICANN board liaison) | ||||
| * Marc Blanchet | (* Other members based on checking their availability) | |||
| * Russ Housley | ||||
| * Barry Leiba | ||||
| * Jonne Soininen | ||||
| * Suzanne Woolf | ||||
| End of changes. 13 change blocks. | ||||
| 36 lines changed or deleted | 33 lines changed or added | |||
This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||