[council] FW: New Liaison Statement, "Liaison Statement from the IAB to the ICANN Board on Technical Use of Domain Names"
Jonathan Robinson
jrobinson at afilias.info
Sun Oct 12 21:34:00 UTC 2014
All,
Sincere apologies, it looks like I missed this when it was sent to me.
Jonathan
-----Original Message-----
From: Jonne Soininen [mailto:jonne.soininen at icann.org]
Sent: 15 September 2014 12:59
To: ICANN Board of Directors ICANN; jonathan.robinson at ipracon.com
Cc: Russ Housley
Subject: Fwd: New Liaison Statement, "Liaison Statement from the IAB to the
ICANN Board on Technical Use of Domain Names"
Dear Board and the chair of the GNSO council,
please, see enclosed a liaison statement the IETF/IAB has sent to the ICANN
Board. Though, the main recipient is the ICANN board, I believe it is useful
for the GNSO council to see this as well.
Best Regards,
Jonne.
Begin forwarded message:
> From: Liaison Statement Management Tool <lsmt at ietf.org>
> Subject: New Liaison Statement, "Liaison Statement from the IAB to the
ICANN Board on Technical Use of Domain Names"
> Date: 15 Sep 2014 18:10:25 GMT+3
> To: <jonne.soininen at icann.org>
> Cc: Jonne Soininen <jonne.soininen at nsn.com>, The IAB Chair
> <iab-chair at iab.org>, The IAB <iab at iab.org>, The IAB Executive Director
> <execd at iab.org>
>
> Title: Liaison Statement from the IAB to the ICANN Board on Technical
> Use of Domain Names Submission Date: 2014-09-15 URL of the IETF Web
> page: http://datatracker.ietf.org/liaison/1351/
>
> From: The IAB (Russ Housley <housley at vigilsec.com>)
> To: ICANN Board of Directors (jonne.soininen at icann.org)
> Cc: Jonne Soininen <jonne.soininen at nsn.com>,The IAB Chair
> <iab-chair at iab.org>,The IAB <iab at iab.org>,The IAB Executive Director
<execd at iab.org> Response Contact:
> Technical Contact:
> Purpose: For information
>
> Body: Dear colleagues,
>
> We are writing this note in order to share with you some work in the
> IETF regarding domain names for "technical use," as described in RFC
> 2860.
>
> In RFC 2860 ("Memorandum of Understanding Concerning the Technical
> Work of the Internet Assigned Numbers Authority," June 2000), the IAB
> acknowledged the authority of ICANN for policies relating to the
> assignment of domain names, but retained authority over "assignments
> of domain names for technical use" (Section 4.3, pg 2):
>
>
>> 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.
>
> In order to support appropriate technical use of domain names in the
> context of its protocol development work, the IETF approved RFC 6761
> ("Special-Use Domain Names," February 2013). As directed, IANA
> established and populated a registry for such special-use names
>
(http://www.iana.org/assignments/special-use-domain-names/special-use-domain
-names.xhtml).
>
> Recently, several requests have come to the IETF for names to be added
> to the special-use domain names registry
> (See:
> http://www.ietf.org/archive/id/draft-chapin-additional-reserved-tlds-0
> 1.txt
> and
>
http://www.ietf.org/archive/id/draft-grothoff-iesg-special-use-p2p-names-02.
txt).
>
> Discussion of these requests under the process established in RFC 6761
> has revealed difficulties in applying its guidelines in practice.
> Under its current charter, the DNSOP working group in the IETF is
> responsible to review and clarify the overlap between (among other
> things) the special names registry from RFC 6761 and the public DNS
> root. This could include consideration of the problem of existing name
> collisions, provision of additional guidelines, or further
> modification to the process in RFC 6761 to reduce the potential for
> collisions in the future. Any changes are to be kept within the
> constraints of RFC 2860 (or any future modification to RFC 2860).
>
> All such discussion and any modification will be open and transparent
> to participation by interested parties, in accordance with established
> IETF processes. We invite participation of interested parties,
> including members of the ICANN community, in this work.
>
> On behalf of the IAB,
> Russ Housley
> IAB Chair
> Attachments:
>
> No document has been attached
>
--
Jonne Soininen
Tel: +358 40 527 4634
E-mail: jonne.soininen at icann.org
More information about the council
mailing list