WG Review: Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers (modern)

The IESG <iesg-secretary@ietf.org> Fri, 12 June 2015 18:45 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8CE1ACEC1; Fri, 12 Jun 2015 11:45:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jaj-rS62-9SW; Fri, 12 Jun 2015 11:45:39 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C11C1ACEBE; Fri, 12 Jun 2015 11:45:39 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Review: Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers (modern)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150612184539.31257.17908.idtracker@ietfa.amsl.com>
Date: Fri, 12 Jun 2015 11:45:39 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/GvU4SAvXGFC6RnUEuSrtiprSU8k>
Cc: modern WG <modern@ietf.org>
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: <http://www.ietf.org/mail-archive/web/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: Fri, 12 Jun 2015 18:45:41 -0000

A new IETF working group has been proposed in the Applications and
Real-Time Area. The IESG has not made any determination yet. The
following draft charter was submitted, and is provided for informational
purposes only. Please send your comments to the IESG mailing list (iesg
at ietf.org) by 2015-06-22.

Managing, Ordering, Distributing, Exposing, & Registering telephone
Numbers (modern)
------------------------------------------------
Current Status: Proposed WG

Chairs:
  Tom McGarry <tom.mcgarry@neustar.biz>
  Steve Donovan <srdonovan@usdonovans.com>

Assigned Area Director:
  Alissa Cooper <alissa@cooperw.in>

Mailing list
  Address: modern@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/modern
  Archive: http://www.ietf.org/mail-archive/web/modern/

Charter:

The MODERN working group will define a set of Internet-based mechanisms
for the purposes of managing and resolving telephone numbers (TNs) in an
IP environment. Devices, applications, and network tools increasingly
need to manage TNs, including requesting and acquiring TN delegations
from authorities. The output of the working group should make
distribution, acquisition, and management of TNs simpler for all entities
involved.

The working group will define an information management framework for the
roles and functions involved in associating information with one or more
TNs in an IP environment.  The working group will also identify protocol
mechanisms to support the interactions between the functions defined by
the framework. This includes either recommending or defining protocol
mechanisms for acquiring, associating and resolving TNs, with a
preference for use of existing protocol mechanisms. TNs may either be
managed in a hierarchical tree, or in a distributed registry. The
protocol mechanism for acquiring TNs will provide an enrollment process
for the entities that use and manage TNs. 

The protocol mechanism for resolving TNs will allow entities such as
service providers, devices, and applications to access data related to
TNs. Maintaining reliability, real-time application performance, and
security and privacy for both the data and the protocol interactions are
primary considerations. The working group will take into consideration
existing IETF work including STIR, ENUM, SPEERMINT, DRINKS and SCIM.

The work of this group will focus on TNs, as defined in RFC3966, and
blocks of TNs, that are used to initiate communication with another user
of a service. There is an expectation that aspects of the architecture
and protocols defined by the working group will be reusable for other
user-focused identifiers. Any such extensions or reuse of MODERN
mechanisms are out of scope for the MODERN working group. Solutions and
mechanisms created by the working group will be flexible enough to
accommodate different policies for TN assignment and management, for
example those established by different regulatory agencies.

The working group will deliver the following:

- An architecture overview, including high level requirements and
security/privacy considerations

- A description of the enrollment processes for existing and new TNs
including any modifications to metadata related to those TNs

- A description of protocol mechanisms for accessing contact information
associated with enrollments

- A description of mechanisms for resolving information related to TNs

Milestones:

TBD