Annex 8: Responsibilities for e164.arpa
(1)
What do IANA do,
excerpt from RFC 2860:
4.
Agreed technical work items. ICANN
agrees that during the term of this MOU it shall cause IANA to comply,
for protocols within IETF's scope, with the following requirements,
which ICANN and IETF acknowledge reflect the existing arrangements under
which the IANA is operated:
4.1.
The IANA will assign and register Internet protocol parameters only as
directed by the criteria and procedures specified in RFCs, including
Proposed, Draft and full Internet Standards and Best Current Practice
documents, and any other RFC that calls for IANA assignment. If they are
not so specified, or in case of ambiguity, IANA will continue to assign
and register Internet protocol parameters that have traditionally been
registered by IANA, following past and current practice for such
assignments, unless otherwise directed by the IESG.
If
in doubt or in case of a technical dispute, IANA will seek and follow
technical guidance exclusively from the IESG. Where appropriate the IESG
will appoint an expert to advise IANA.
The
IANA will work with the IETF to develop any missing criteria and
procedures over time, which the IANA will adopt when so instructed by the
IESG.
4.2.
In the event of technical dispute between the IANA and the IESG, both will
seek guidance from the IAB whose decision shall be final.
4.3.
Two particular assigned spaces present policy issues in addition to the
technical considerations specified by the IETF: the assignment of domain
names, and the assignment of IP address blocks. These policy issues are
outside the scope of this MOU.
Note
that (a) assignments of domain names for technical uses (such as domain
names for inverse DNS lookup), (b) assignments of specialised address
blocks (such as multicast or anycast blocks), and (c) experimental
assignments are not considered to be policy issues, and shall remain
subject to the provisions of this Section 4.
(For purposes of this MOU, the term "assignments"
includes allocations.) In the event ICANN adopts a policy that prevents it
from complying with the provisions of this Section 4 with respect to the
assignments described in (a) - (c) above, ICANN will notify the IETF,
which may then exercise its ability to cancel this MOU under Section 2
above.
4.4.
The IANA shall make available to the public, on-line and free of charge,
information about each current assignment, including contact details for
the assignee. Assignments
published in RFCs by the RFC Editor and available publicly will be deemed
to meet the requirements of this Section 4.4.
4.5.
The IANA shall provide on-line facilities for the public to request
Internet protocol parameter assignments and shall either execute such
assignments, or deny them for non- conformance with applicable technical
requirements, in a timely manner. There shall be no charge for assignments
without the consent of the IAB. Requests shall only be denied on
legitimate technical grounds. For protocols within the IETF scope (i.e.,
registries created by IETF action), appeals against such denials may be
made to the IESG and subsequently to the IAB as provided in 4.2 above.
4.6.
The IANA shall have non-voting liaison seats on appropriate IETF
committees as determined by the IETF, and may participate in all IETF
discussions concerning technical requirements for protocol parameter
assignment through such liaisons.
4.7.
The IANA shall review all documents in IETF Last Call to identify any
issues of concern to the IANA, and shall raise these issues with the IESG.
(2)
IAB requested on May
17 2000 that assignment of subdomains of
arpa should be a task of IANA according to the specification of
"technical uses" in bullet point 4.3 above. The "whois
record" of .arpa was
changed accordingly on request by Department of Commerce. This implies that registration of subdomains to .arpa is done
according to instructions in RFCs (see point (1) above).
This
was the request of change of the whois record:
Registrant:
ARPA
Domain
Internet Assigned Numbers Authority (IANA)
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
US
Administrative
Contact, Technical Contact, Zone Contact:
Internet Assigned Numbers Authority (IANA) iana@iana.org
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
US
310-823-9358
Fax - 310-823-8649
(3)
Instructions to IANA
to register e164.arpa, delegate e164.arpa according to instructions from
IAB, handling content of e164.arpa according to E.164 is specified in RFC
2916:
4.
IANA Considerations
This
memo requests that the IANA delegate the E164.ARPA domain following
instructions to be provided by the IAB.
Names within this zone are to be delegated to parties according to
the ITU recommendation E.164. The
names allocated should be hierarchic in accordance with ITU Recommendation
E.164, and the codes should assigned in accordance with that
Recommendation.
Delegations
in the zone e164.arpa (not delegations in delegated domains of e164.arpa)
should be done after Expert Review, and the IESG will appoint a designated
expert.
|