[Internal-cg] ICG Call: NTIA Role

Kavouss Arasteh kavouss.arasteh at gmail.com
Sun Apr 26 09:46:07 UTC 2015


Dear Jonathan
Dear Martin,
To make the issue of repartition of the tasks between ICANN and future
oversighting entity of IANA functions ( replacing NTIA ) and the CSC in
performing some of the NTIA Functions  .
In order to clarify the matter it is good to refresh our mind of the
following
The curremt functions performed by IANA are

Since 2000, ICANN has performed the IANA functions, on behalf of the U.S.
government, through a contract with NTIA (read more on this background
<https://www.nro.net/nro-and-internet-governance/iana-oversight/background>).
This contract has been amended, extended and renewed over the years.
The current
version
<http://www.ntia.doc.gov/files/ntia/publications/sf_26_pg_1-2-final_award_and_sacs.pdf>
of the IANA contract, awarded by NTIA in July 2012, defines the following
functions:

   1. Coordination of the assignment of technical protocol parameters
   including the management of the address and routing parameter area (ARPA)
   TLD.
   2. The administration of certain responsibilities associated with the
   Internet DNS root zone management, namely:
      - Root Zone File Change Request Management
      - Root Zone *“*WHOIS*” *Change Request and Database Management
      - Delegation and Redelegation of a Country Code Top Level-Domain
      (ccTLD*)*
      - Delegation and Redelegation of a Generic Top Level Domain (gTLD)
      - Root Zone Automation
      - Root Domain Name System Security Extensions (DNSSEC) Key Management
      - Customer Service Complaint Resolution Process (CSCRP)
      - The allocation of Internet numbering resources:
         - To the Regional Internet Registries (RIRs)
      3. Other services related to the management of the ARPA and INT
   top-level domains (TLDs

The above functions could be summarized as follows
a. Domain Name System Root Zone Management$
b. Internet Number Registry Management
c Protocol pParameter Registry Managmenrt in cluding management of the
Addresse and Rooting Parameter AREA (ARPA ) TLD and
Management of the INTernational treat organization ( INT) to Level Domain
Pls kindly confirm if all these functions will be tasked to PTI  and which
one goes to CSC
On the other hand ,the oversight role played by the NTIA.includes:

   - Awarding and setting the terms of the IANA functions contract for a
   defined period, including specific options for extending that contract.
   - Ensuring that the contractor meets specific service and reporting
   requirements. This includes:
      - Working with defined “interested and affected parties” (including
      the RIRs) to develop:
         - User instructional documentation, including technical
         requirements
         - Documentation of the source of policies and procedures for
         specific IANA functions
         - Performance standards for operation of the IANA functions
         - Customer complaint process
      - Security plan (updated annually)
      - Monthly performance standards reports
      - Annual customer service survey
      - Annual external audit report
      - Annual Conflict of Interest Enforcement and Compliance report
      - Annually updated Contingency and Continuation of Operations Plan
      (CCOP)
      - Plan for Transition to Successor

Please kindly clarify which of these functions
A ,Continued to be performed by NTIA,if any
B) Will be performed by ICANN as replacement of NTIA
C) Will be performed by CSC
Regards


2015-04-25 22:35 GMT+02:00 Kavouss Arasteh <kavouss.arasteh at gmail.com>:

> Dear Martin
> I wish to receive your kind reply about the distribution / repartition of
> the Current NTIA to Future ICANN ( acting as NTIA 9 AND csc ( PERFPORMING
> OPERATION FUNCTIONS OF NTIA)
> Pls kindly advise which NTIA CURRENT FUNCTIONS will be performed by ICANN
> as per CWG output and which current NTIA function will be perfomned by CSC
> It is not clear
> Regards
> Kavouss
>
> 2015-04-24 21:40 GMT+02:00 Mary Uduma <mnuduma at yahoo.com>:
>
>> Thank you Milton for the clarifications.
>> I guess these are still some of the fine tuning and gaps to be filled by
>> the  CWG-IANA
>>
>>
>> Mary Uduma
>>
>>
>>
>>   On Friday, April 24, 2015 2:13 PM, Milton L Mueller <mueller at syr.edu>
>> wrote:
>>
>>
>>  Mary:
>> Your questions may have been answered by someone else during the call but
>> I didn’t see any responses so I will give it a go:
>>
>>   Is CWG proposing that ICANN can sack PTI?
>>
>> MM: Yes, but not unilaterally, there is a review process anchored in the
>> names community that it would have to do through. Some of the details of
>> the review and separation process are not specified yet.
>>
>>  Will ICANN sack the Board, Mangement or staff?
>>
>> MM: Here again we need to distinguish between “ICANN” (the corporation)
>> and ICANN community. The review process could lead to calls for changes in
>> the PTI board, and I think the CSC would also have an escalation process
>> that could lead to pressure on the PTI board.
>>
>> Would ICANN  register another Affiliate to carry on the IANA Functions
>> since PTI is  not  totally independent of ICANN?
>>
>> MM: Who got the new names-IANA contract would depend on the outcome of an
>> RFP I believe
>>
>>
>>
>>
>>
>>
>>
>>
>>    On Wednesday, April 22, 2015 6:02 PM, Martin Boyle <
>> Martin.Boyle at nominet.org.uk> wrote:
>>
>>    Hi Kavouss,
>>
>>  There seems to me that there was some confusion between us on the role
>> of the NTIA and how the names proposal would address this.
>>
>>  The NTIA has a number of roles – identified in the document which went
>> to consultation in December.  I’m sorry if I did not make clear that I was
>> looking at NTIA’s role in letting the contract and its ability to terminate
>> and re-tender.
>>
>>  One key part of the CWG’s discussion has been focussed on separability
>> – a role that NTIA currently has by virtue of its contract with ICANN for
>> the role of IANA functions operator.  The contract approach allows the role
>> to be reassigned in the case of the IANA functions operator failing to meet
>> obligations and failing to remedy the failings.
>>
>>  In the model in front of us today, at transition ICANN would take the
>> NTIA responsibility for a contract with its affiliate (subsidiary) the PTI
>> – where PTI is the contractor currently providing the IANA functions
>> operator, the IANA division in ICANN.
>>
>>  The role of the CSC is to carry out the operational responsibilities
>> associated with managing the contract.  Its role is quite limited in that
>> it monitors performance against the agreed service level targets and works
>> with PTI to ensure that concerns are addressed.  The CSC does not make the
>> decision on the future of the contract.
>>
>>  For other roles of the NTIA, we recommend:
>>  •             Discontinuing the third party authorisation of changes to
>> the registries;
>>  •             Further work on dealing with appeals on changes to the
>> registries;
>>  •             Using the CSC and PRF to process changes to service level
>> agreements and other operational conditions;  and
>>  •             Using the CSC (and/or the PRF) to initiate discussion on
>> structural or operational changes (the introduction of DNSSEC was the
>> example I used) but leave open for the moment who might authorise change.
>>  (I might have missed something, so do not treat this as a definitive
>> list.  There’s also a lot of detail I have not covered.)
>>  However, all of these would come back to ICANN to implement or cause to
>> be implemented.
>>
>>  Hope this helps
>>
>>  Martin
>>
>> _______________________________________________
>> Internal-cg mailing list
>> Internal-cg at mm.ianacg.org
>> http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org
>>
>>
>> _______________________________________________
>> Internal-cg mailing list
>> Internal-cg at mm.ianacg.org
>> http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/attachments/20150426/397f1488/attachment.html>


More information about the Internal-cg mailing list