New Non-WG Mailing List: Arcing -- This list will discuss different architectural approaches to signalling alternative resolution contexts for Internet names

IETF Secretariat <ietf-secretariat@ietf.org> Thu, 21 January 2016 17:14 UTC

Return-Path: <ietf-secretariat@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 26B0C1A8F3B; Thu, 21 Jan 2016 09:14:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: New Non-WG Mailing List: Arcing -- This list will discuss different architectural approaches to signalling alternative resolution contexts for Internet names
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160121171414.30958.65902.idtracker@ietfa.amsl.com>
Date: Thu, 21 Jan 2016 09:14:14 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/onHwGwApoiJVpVPy0c-cefTdLWE>
Cc: ted.ietf@gmail.com
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
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, 21 Jan 2016 17:14:14 -0000

A new IETF non-working group email list has been created.

List address: arcing@ietf.org
Archive: https://mailarchive.ietf.org/arch/search/?email_list=arcing
To subscribe: https://www.ietf.org/mailman/listinfo/arcing

Purpose:

While the most common Internet names by far are those which are part of the domain name system, that set of names is not the whole. A number of independent naming and resolution contexts have emerged. In addition to those created for onion routing and multicast DNS, there are large sets associated with the Handle system, URNs, and Internet scale proprietary names (e.g. twitter handles). 

It is apparent that the desire to re-use Internet protocols that default to DNS-based resolution in other resolution contexts has created ambiguities in what resolution context should be used for individual names. Those ambiguities may be expressed in operational difficulties (queries in the wrong context) and in concerns about limitations implied for DNS-based names. This list will discuss the architectural issues and best practices for identifying alternative resolution contexts.

For additional information, please contact the list administrators.