.nz Memorandum of Understanding with NZ Government Jay Daley, - - PowerPoint PPT Presentation

nz memorandum of understanding with nz government
SMART_READER_LITE
LIVE PREVIEW

.nz Memorandum of Understanding with NZ Government Jay Daley, - - PowerPoint PPT Presentation

.nz Memorandum of Understanding with NZ Government Jay Daley, ICANN Helsinki 2016 Structure of .nz ccTLD Jay Jordan Debbie Sets .nz policy .nz registry .nz Designated manager Authorises


slide-1
SLIDE 1

.nz Memorandum of Understanding with NZ Government

Jay Daley, ICANN Helsinki 2016

slide-2
SLIDE 2
  • .nz registry
  • .nz marketing

and channel management

  • Broad

technical research

  • Business

development

Structure of .nz ccTLD

June 2016 ICANN 56 Helsinki 2

Jay Jordan Debbie

  • .nz Designated

manager

  • Voice for the

Internet and all users

  • Internet policy
  • Community

funding

  • Events
  • Sets .nz policy
  • Authorises

registrars

  • Regulates

market

  • Handles

complaints

  • Manages

disputes

slide-3
SLIDE 3

MEMORANDUM OF UNDERSTANDING Management of the .nz Country Code Top Level Domain

  • Between InternetNZ and gov’t department
  • Entered into voluntarily
  • 18 months of discussions/negotiations
  • Three CEs for .nz ~ GAC rep for NZ gov’t
  • Signed in May 2016

New MoU

June 2016 ICANN 56 Helsinki 3

slide-4
SLIDE 4
  • Impact of disagreeing with Gov’t on

Internet policy

Regulated pricing for monopoly infrastructure Surveillance/interception laws

  • Claims that .nz profits are a “public tax”

Calls for gov’t to redistribute .nz profits ”Why does InternetNZ get to decide?”

  • No authoritative document to point to

Assumptions that something this important must be government controlled Regular threat from newcomers misunderstanding

Tackles 3 important risks

June 2016 ICANN 56 Helsinki 4

slide-5
SLIDE 5
  • Role of government defined

And thereby limited

  • Recognition/definition of InternetNZ role

Difficult for third parties to challenge

  • Public obligations for InternetNZ

Keeping us honest ~ in community interests

  • Defined process for resolving concerns

Follows RFC1591 principles

  • Pinned to external documents

RFC1591, Framework of Interpretations, GAC principles, our own TLD principles

  • Excludes funding and intellectual property

MoU tackles this

June 2016 ICANN 56 Helsinki 5

slide-6
SLIDE 6

Responsible for ensuring

  • Stability of Internet
  • .nz is reliable and responsive
  • .nz is run consistent with RFC1591
  • .nz supports interests of users
  • So yes – Government is now committed to

ensuring that we follow RFC1591 !

Role of NZ Government

June 2016 ICANN 56 Helsinki 6

slide-7
SLIDE 7
  • Designated manager
  • Appointed by local Internet community

through a proper process

  • Will make a surplus from .nz and will use it

to further its objects

Which may include disagreeing with government

  • Decides and implements the .nz market

structure and regulates the market

  • Develops and sets all .nz policy ~ benefit

and meet needs of local community

Recognition of InternetNZ role

June 2016 ICANN 56 Helsinki 7

slide-8
SLIDE 8

“… commits to high standards of public transparency and commits to continuing …”

  • Publish annual report in public and in timely

fashion

  • Hold governance meetings in public and

publish minutes in timely fashion

  • Provide public reports on how surplus from

.nz is spent

  • Engage in broad community consultation on

any changes to the “objects” or .nz policy

Existing practices become

  • bligations

June 2016 ICANN 56 Helsinki 8

slide-9
SLIDE 9

“… regularly testing views of the broad community ...”

  • To ensure InternetNZ is demonstrably in

touch with Internet users

  • To increase community understanding of

its own views

  • To identify their key issues of concern
  • Publicly report back on views expressed

One new obligation

June 2016 ICANN 56 Helsinki 9

slide-10
SLIDE 10

“... in principle available on an equal basis to any significantly interested party.”

  • Stage 1 – Open dialogue

“Please explain” Notify and give time to resolve

  • Stage 2 – Initiate community conversation

Must be multi-stakeholder, open and inclusive

  • Stage 3 – Is there community consensus?

Management of .nz inconsistent with RFC1591 Better, local, RFC1591 compliant manager exists

  • Stage 4 – Transfer of designated manager

Which InternetNZ would support and assist

Process for resolving concerns

June 2016 ICANN 56 Helsinki 10

slide-11
SLIDE 11

Thanks

Debbie Monahan <dnc@dnc.org.nz> Jordan Carter <jordan@internetnz.net.nz> Jay Daley <jay@nzrs.net.nz>