We pulled this together, hope this helps: https://docs.google.com/document/d/1vF657f48o3n-zosS8PNyMAesgol-NdPH2Bg85Wkp... A legally distinct IANA affiliate, consisting of ICANN's current IANA department operations, with one or more members including ICANN, the RIRs (their preferred legal entity), and IETF (their preferred legal entity), and governed by a community selected board: - maintains operational security, stability, resiliency of the DNS and other IANA functions; - clearly separates the implementation of the IANA functions from names (ICANN), numbers (RIRs) and protocols (IETF) policy making; - creates IANA operational oversight, with service level agreements continuing or being developed in conjunction with and monitored by a direct customer committee(s) and comparable bodies within the policy organizations; - creates IANA organizational accountability, with its board 1) being directly selected through multistakeholder community selection mechanisms within the policy making organizations, and 2) decisions subject to an independent appeals mechanism; - addresses IANA legal and financial risk, by limiting the scope of IANA’s operations and activities; - addresses geopolitical concerns potentially through the geographic diversity of IANA’s members; - reduces Internet governance and business risk, by maintaining the coherency of the IANA functions while, should it be necessary, allowing for the portability of IETF, RIR, and ICANN registries; - creates consistency between and strengthens the proposed contractual transition approaches of the IETF, RIRs, and ICANN; - adheres to and satisfies the NTIA’s four principles, and achieves the USG’s stated "intent to transition key Internet domain name functions to the global multistakeholder community". --------------------------------------- Brenden Kuerbis Post Doctoral Researcher, iSchool, Syracuse University || http://internetgovernance.org <http://internetgovernance.org>