Internet Architecture Board statement on the registration of special use names in the ARPA domain
IAB Chair <iab-chair@ietf.org> Thu, 30 March 2017 19:05 UTC
Return-Path: <iab-chair@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A9490129A20; Thu, 30 Mar 2017 12:05:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IAB Chair <iab-chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: iab@iab.org
Subject: Internet Architecture Board statement on the registration of special use names in the ARPA domain
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <149090074668.15567.4906905482600521711.idtracker@ietfa.amsl.com>
Date: Thu, 30 Mar 2017 12:05:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/mHm5G0cF-QXJX8_75rJZ8DEopkE>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Mar 2017 19:05:47 -0000
The IAB has noted some controversy in respect of possible registrations of names using the mechanisms defined in RFC 6761. The IAB observes that there is a distinction to be made between creating an entry in the Special-Use Domain Names registry where that entry prevents the name from being registered in the DNS and creating an entry in the Special-Use Domain Names registry where that name is intended to be resolved using the DNS protocol. Through the IAB, the IETF is in a position to specify names beneath the top-level domain ARPA, which is designated as the Address and Routing Parameter Area domain. This is not a general purpose registry, but it is set aside for technical infrastructure established by IETF standards. All names registered in the Special-Use Domain Names registry that are intended for use via the DNS protocol are found beneath the ARPA top- level domain. Other names in the Special-Use Domain Names registry are intended for exclusion from DNS resolution. An entry in the Special-Use Domain Names Registry that does not require DNS resolution does not require the registrant to control the relevant name in the DNS. In the view of the IAB, when placing any name in the Special-Use Domain Names registry with the intention that it be used with the DNS protocol, such an entry must be within a domain under the control of the body making the registration. For the IETF, an appropriate domain for such names would be ARPA, as long as those names meet the conditions in RFC 3172. For the IAB, Ted Hardie IAB Chair