[CWG-RFP3] Policy authority

[David Conrad]

Malcolm,

On Nov 18, 2014, at 3:35 PM, Malcolm Hutty <malcolm at linx.net> wrote:
> I have to disagree with the assertion above. IANA is not changing (not
> unless we change it, anyway); NTIA is.

Just a minor point unrelated to the main thrust of your note: the above is not precisely accurate.

With the transition of the stewardship of the IANA functions contract, the IANA root zone management function _must_ change.

As I believe has been discussed before, NTIA currently has an operational role in that function: the administrator role that authorizes root zone modifications (both to the registration database and the root zone database itself).

The community has three options:
- remove the authorization requirement;
- replace NTIA with a single authorizer; or
- replace NTIA with multiple authorizers.

The IANA root zone management function may also need to change depending on what the community decides with respect to the Root Zone Maintainer function currently performed by Verisign under a separate cooperative agreement with NTIA.

I'll not comment on the more substantive part of your message.

Regards,
-drc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mm.icann.org/pipermail/cwg-rfp3/attachments/20141119/95c8bc34/signature.asc>