80 likes | 244 Views
What Does This Mean? What Should We Do?. IANAPLAN at IETF90. Stuff requested. Policy RFC 5226, RFC 6220 (?) Implementation RFC 2850, RFC 5226, RFC 6220, current registries, MoU & adjustments Oversight By IAB, per RFC 2850, RFC 2860, RFC RFC 6220, and the MoUs. Stuff requested (2).
E N D
What Does This Mean?What Should We Do? IANAPLAN at IETF90 IETF 90
Stuff requested • Policy • RFC 5226, RFC 6220 (?) • Implementation • RFC 2850, RFC 5226, RFC 6220, current registries, MoU & adjustments • Oversight • By IAB, per RFC 2850, RFC 2860, RFC RFC 6220, and the MoUs IETF 90
Stuff requested (2) • Accountability • Implementation failures: mechanisms specified in MoUs (includes, in worst case, replace operator) • Policy failures: RFC 3777 and updates IETF 90
A suggestion • Stability says to change as little as possible at one time • The contractual structure is changing • Nothing about the arrangement between IANA operator and us needs to change • Therefore, document current state and do nothing else IETF 90
Have we done everything? Is there actually anything else we need to add? IETF 90
IANAPLAN at IETF90 Proposed Charter IETF 90
Content of charter • Are there things that are missing? • Are there things that should be removed? • Do we need a WG? IETF 90
WG? • Do you think there is a real problem here? • If yes, do you understand the problem? • Do you think we can do this work? • Are you personally willing to do work? IETF 90