[Modern] draft charter

"Peterson, Jon" <jon.peterson@neustar.biz> Wed, 11 February 2015 17:18 UTC

Return-Path: <jon.peterson@neustar.biz>
X-Original-To: modern@ietfa.amsl.com
Delivered-To: modern@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1382D1A894C for <modern@ietfa.amsl.com>; Wed, 11 Feb 2015 09:18:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.566
X-Spam-Level:
X-Spam-Status: No, score=-99.566 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, 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 tFwwqFNgx53n for <modern@ietfa.amsl.com>; Wed, 11 Feb 2015 09:18:39 -0800 (PST)
Received: from mx0b-0018ba01.pphosted.com (mx0b-0018ba01.pphosted.com [67.231.157.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0AF61A894E for <modern@ietf.org>; Wed, 11 Feb 2015 09:18:39 -0800 (PST)
Received: from pps.filterd (m0078668.ppops.net [127.0.0.1]) by mx0b-0018ba01.pphosted.com (8.14.7/8.14.7) with SMTP id t1BHDUGr016673 for <modern@ietf.org>; Wed, 11 Feb 2015 12:18:39 -0500
Received: from stntexhc12.cis.neustar.com ([156.154.17.216]) by mx0b-0018ba01.pphosted.com with ESMTP id 1sg3cv8ngr-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <modern@ietf.org>; Wed, 11 Feb 2015 12:18:38 -0500
Received: from STNTEXMB11.cis.neustar.com ([169.254.1.67]) by stntexhc12.cis.neustar.com ([::1]) with mapi id 14.03.0158.001; Wed, 11 Feb 2015 12:18:37 -0500
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "modern@ietf.org" <modern@ietf.org>
Thread-Topic: draft charter
Thread-Index: AQHQRh7FZCWKLIxx2EOzvUKYZFZGpg==
Date: Wed, 11 Feb 2015 17:18:37 +0000
Message-ID: <D100CEF2.1492B8%jon.peterson@neustar.biz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-originating-ip: [192.168.128.80]
Content-Type: multipart/alternative; boundary="_000_D100CEF21492B8jonpetersonneustarbiz_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=nai engine=5600 definitions=7708 signatures=670625
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1502110170
Archived-At: <http://mailarchive.ietf.org/arch/msg/modern/LdnS3u7Z6QlDvdiM-x3Qj0_q2R4>
Subject: [Modern] draft charter
X-BeenThere: modern@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers non-WG discussion list" <modern.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/modern>, <mailto:modern-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/modern/>
List-Post: <mailto:modern@ietf.org>
List-Help: <mailto:modern-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/modern>, <mailto:modern-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 17:18:51 -0000

At the Dallas IETF meeting in March, we'd like to get together and talk about what a working group for MODERN might look like. As an initial input to the discussion, a few of us have put together a proposed charter. While the TeRQ work was positively evaluated in the DISPATCH process, we feel this is broader enough in scope to warrant its own BoF.

Comments are welcome, this is just a starting point.

------

Modern charter text:

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.  Existing mechanisms for these purposes face obsolescence as the voice communications infrastructure evolves to IP technology and new applications for TNs become possible.  The traditional model of a TN having an association to a single service provider and a single application is breaking down.  Its use as a network locator is going away, but its use as an identifier for an individual or an organization will remain for some time. Devices, applications, and network tools increasingly need to manage TNs, including requesting and acquiring TN delegations from authorities.

The working group will define a framework for the roles and functions involved in managing and resolving TNs in an IP environment. This includes a protocol mechanism for acquiring TNs, which will provide an enrollment process for the individuals and entities that use and manage TNs. TNs may either be managed in a hierarchical tree, or in a distributed peer-to-peer architecture.  Privacy of the enrollment data and security of the resource will be primary considerations.

Additionally, the working group will deliver a protocol mechanism for resolving TNs which will allow entities such as service providers, devices, and applications to access data related to TNs, possibly including caller name data (CNAM).  Maintaining reliability, real time application performance, security and privacy are primary considerations.  The working group will take into consideration existing IETF work including ENUM, SPEERMINT, STIR, and DRINKS.

The work of this group is limited to specifying a solution for TNs and covers any service that can be addressed using a TN.  Expanding the work to other identifiers is out of scope.  Solutions and mechanisms created by the working group will be flexible enough to accommodate different policies, e.g., by different regulatory agencies.

The work group will deliver the following:


-       An architecture overview document that includes high level requirements and security/privacy considerations

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

-       A document describing protocol mechanisms for accessing contact information associated with enrollments

-       A document describing mechanisms for resolving information related to TNs