Skip to main content

IANA Stewardship Transition Coordination Group Responds to Submitted Proposals

As part of its assessment of the proposals received concerning protocol parameters and numbers, the ICG has sent the following question to the IETF IANAPLAN working group and CRISP team:

"The IETF consensus as reflected in draft-ietf-ianaplan-icg-response [1] did not include a formal request to change the arrangements regarding the IANA trademark and the iana.org domain as a requirement of its transition proposal. But Section III.A.2 of the RIR proposal [2] says: "With regards to the IANA trademark and the IANA.ORG domain, it is the expectation of the Internet Number Community that both are associated with the IANA Numbering Services and not with a particular IANA Numbering Services Operator. Identifying an organization that is not the IANA Numbering Services Operator and which will permanently hold these assets will facilitate a smooth transition should another operator (or operators) be selected in the future. It is the preference of the Internet Number Community that the IANA trademark and the IANA.ORG domain name be transferred to an entity independent of the IANA Numbering Services Operator, in order to ensure that these assets are used in a non-discriminatory manner for the benefit of the entire community. From the Internet Number Community's perspective, the IETF Trust would be an acceptable candidate for this role."

The numbers proposal sees these changes as a requirement of the transition and the protocols parameters proposal does not. If these aspects of the proposals are perceived as incompatible would the numbers and protocol parameters communities be willing to modify their proposals to reconcile them?

Please either send us your response or let us know that you'll need more time by February 21, 2015.

Thanks,
Alissa Cooper on behalf of the ICG


[1] https://www.dropbox.com/s/txu310uikebwfbj/draft-ietf-ianaplan-icg-response-09.pdf?dl=0 [PDF, 100 KB]
[2] https://www.dropbox.com/s/j9xzphbzczl2372/ICG%20RFP%20Number%20Resource%20Proposal.pdf?dl=0" [PDF, 266 KB]


More Announcements
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."