Re: [Modern] Fwd: [new-work] WG Review: Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers (modern)

Richard Shockey <richard@shockey.us> Thu, 25 June 2015 19:30 UTC

Return-Path: <richard@shockey.us>
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 7DAD81ACD25 for <modern@ietfa.amsl.com>; Thu, 25 Jun 2015 12:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.026
X-Spam-Level:
X-Spam-Status: No, score=-2.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 Wk-vv__WcIQ0 for <modern@ietfa.amsl.com>; Thu, 25 Jun 2015 12:30:22 -0700 (PDT)
Received: from qproxy1-pub.mail.unifiedlayer.com (qproxy1-pub.mail.unifiedlayer.com [173.254.64.10]) by ietfa.amsl.com (Postfix) with SMTP id 235741ACD0D for <modern@ietf.org>; Thu, 25 Jun 2015 12:30:22 -0700 (PDT)
Received: (qmail 11639 invoked by uid 0); 25 Jun 2015 19:30:16 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by qproxy1.mail.unifiedlayer.com with SMTP; 25 Jun 2015 19:30:16 -0000
Received: from box462.bluehost.com ([74.220.219.62]) by cmgw3 with id kp3M1q00d1MNPNq01p3QTC; Thu, 25 Jun 2015 19:03:24 -0600
X-Authority-Analysis: v=2.1 cv=LLP1Hvm9 c=1 sm=1 tr=0 a=jTEj1adHphCQ5SwrTAOQMg==:117 a=jTEj1adHphCQ5SwrTAOQMg==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=BsZzRlnUWeQA:10 a=MKtGQD3n3ToA:10 a=1oJP67jkp3AA:10 a=ZZnuYtJkoWoA:10 a=8WrITzYgnNwA:10 a=DZsV_1M2FacA:10 a=XAFQembCKUMA:10 a=PeFO9FbFhS32YxYntvkA:9 a=dci_DRCyiIAA:10 a=CiRkrLRW1GAA:10 a=iycWLhIX580A:10 a=ll-iCDY8AAAA:8 a=M0OflfRGAAAA:8 a=48vgC7mUAAAA:8 a=hZG83p_yAAAA:8 a=UqAplN6HAAAA:8 a=hGBaWAWWAAAA:8 a=yakATiurAAAA:8 a=hSQZmzSFDNvRm4y_zwIA:9 a=2WHKfzyYmgxZGtQ3:21 a=mwleYATuf5rYQG_P:21 a=wPNLvfGTeEIA:10 a=ivbTfD_dPm4A:10 a=6fpOX-4qs7AA:10 a=BQYh4w-RC7EA:10 a=kkUMZHjH4KkA:10 a=rcOQXM4wMrtryUgj6vwA:9 a=oMBZ581hdb51I-_P:21 a=tfcVN7WM68xQEHDK:21 a=1l57yv1GinqjKury:21 a=_W_S_7VecoQA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-type:Mime-version:In-Reply-To:References:Message-ID:To:From:Subject:Date; bh=1RZbt4rtctbeAZl4oWS1rglqJM4qIax+z9GSeOeLEJM=; b=VPcSHFD0KjehejLBR92m/iPCrnr42sThMuWmjhnX20VwLCBWcTK7kAYy1Segr31fp2qyy+ey1ZdwTKXgInvbO0/09kZUrg6VNUopc5c4qKPApDxkyV0rnJ4HWmWANzFP;
Received: from [64.134.43.227] (port=60975 helo=[192.168.20.103]) by box462.bluehost.com with esmtpa (Exim 4.84) (envelope-from <richard@shockey.us>) id 1Z8CXN-00065y-Av; Thu, 25 Jun 2015 13:10:13 -0600
User-Agent: Microsoft-MacOutlook/14.5.2.150604
Date: Thu, 25 Jun 2015 15:10:08 -0400
From: Richard Shockey <richard@shockey.us>
To: Alissa Cooper <alissa@cooperw.in>, modern@ietf.org
Message-ID: <D1B1CA46.27FAC%richard@shockey.us>
Thread-Topic: [Modern] Fwd: [new-work] WG Review: Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers (modern)
References: <9bdeb496cc524575a4ece857fa54e56f@TUCM03.TUECSP.UNICC.ORG> <10E9C750-6B20-4258-B538-F64AB40269B2@cooperw.in>
In-Reply-To: <10E9C750-6B20-4258-B538-F64AB40269B2@cooperw.in>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3518089813_798977"
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 64.134.43.227 authed with richard+shockey.us}
Archived-At: <http://mailarchive.ietf.org/arch/msg/modern/UIkkM5VessROYzMjhejcUMAPouY>
Subject: Re: [Modern] Fwd: [new-work] WG Review: Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers (modern)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 25 Jun 2015 19:30:27 -0000

DEL *.* ?


‹ 
Richard Shockey
Shockey Consulting LLC
Chairman of the Board SIP Forum
www.shockey.us
www.sipforum.org
richard<at>shockey.us
Skype-Linkedin-Facebook rshockey101
PSTN +1 703-593-2683


From:  Modern <modern-bounces@ietf.org> on behalf of Alissa Cooper
<alissa@cooperw.in>
Date:  Thursday, June 25, 2015 at 7:44 AM
To:  <modern@ietf.org>
Subject:  [Modern] Fwd: [new-work] WG Review: Managing, Ordering,
Distributing, Exposing, & Registering telephone Numbers (modern)

Would appreciate people¹s thoughts on whether any charter edits may be
warranted in response to these comments, and/or whether a separate response
may be useful for addressing some of the questions below.

Alissa

Begin forwarded message:

> From: "Zhang, Jie" <jie.zhang@itu.int>
> Subject: RE: [new-work] WG Review: Managing, Ordering, Distributing, Exposing,
> & Registering telephone Numbers (modern)
> Date: June 23, 2015 at 1:56:42 PM GMT-3
> To: "iesg@ietf.org" <iesg@ietf.org>
> Cc: "Jamoussi, Bilel" <bilel.jamoussi@itu.int>
> 
> Dear Sir/Madam,
> 
> Below please find comments from the ITU Telecommunication Standardization
> Bureau on the proposed IETF working group MODERN.
> 
> 1. Potential impacts on Recommendation ITU-T E.164 and E.164.1
> It is stated at the beginning of the Charter that 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. And it is
> mentioned that TNs are defined in RFC 3966 "The tel URI for Telephone
> Numbers". Does that mean the mechanism being referred to here only deals with
> Tel URI? Would there be any impact on Recommendation ITU-E E.164 and E.164.1
> which are core recommendations on Telephone Numbers?
> 2. Entities participating in the defined mechanisms
> The Charter states that the protocol mechanism for resolving TNs will allow
> entities such as service providers, devices, and applications to access data
> related to TNs. But it is not clear what kind of entities can participate in
> the mechanisms defined by this MODERN working group. Would it be restricted to
> the entities who have been assigned a TN or a block of TNS?
> 3. Status of Telephone numbers in the defined mechanisms
> Several operations related to TNs are mentioned in the Charter, including
> requesting, acquiring, resolving and associating. It is also stated that the
> protocol mechanism for acquiring TNs will provide an enrollment process for
> the entities that use and manage TNs. Does that mean Telephone numbers with
> various status, such as assigned, spare and reclaimed numbers will all be
> managed in the mechanisms defined by the MODERN working group?
> 4. Regulatory issues
> The Charter states that 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. We would like to bring your attention to the fact that the E.164
> international public telecommunication numbering plan is a politically
> significant numbering resource with direct implications on national
> sovereignty. ITU Plenipotentiary Conference Resolution 133 (Rev. BUSAN, 2014)
> recognized "the existing role and sovereignty of ITU Member States with
> respect to allocation and management of their country code numbering resources
> as enshrined in Recommendation ITU-T E.164", and further instructed the ITU
> Secretary-General and the Directors of three Bureaux (Telecommunication
> Standardization, Development, and Radiocommunication) to "take any necessary
> action to ensure the sovereignty of ITU Member States with regard to
> Recommendation ITU-T E.164 numbering plans whatever the application in which
> they are used".
> 5. Relationship with .Tel
> DNS-based use of international numbering resources has been discussed in ITU-T
> Study Group 2 (SG2) since its meeting of 17-26 September 2013. TSB Director
> has also exchanged letters with ICANN on issues related to registering digit
> strings in the .TEL domain. A representative from ICANN participated in the
> ITU-T SG2 meeting (28 May - June 2014) and provided some background on the
> TELNIC application. A correspondence group under ITU-T SG2 was also set up in
> this regard. We would like to know how the work of this new WG would relate to
> issues related to registering digit strings in the .TEL domain and other
> DNS-based use of telephone numbers.
> 6. Relationship with related existing or concluded WGs
> It is stated in the Charter that the working group will take into
> consideration existing IETF work including STIR, ENUM, SPEERMINT, DRINKS and
> SCIM. Detailed description of the relationship between this new WG and the
> above mentioned other existing or concluded WGs would be appreciated.
> 7. The name of this new WG
> The name of this new WG is "Managing, Ordering, Distributing, Exposing, &
> Registering telephone Numbers (modern)". But in the Charter, ordering,
> exposing and registering TNs are not mentioned, which seems to be a little bit
> inconsistent.
> 
> Best regards,
> 
> Jie Zhang
> Advisor, ITU-T SG2
> International Telecommunication Union
> Place des Nations
> CH-1211 Geneva , Switzerland
> Tel :+41 22 730 5855
> jie.zhang@itu.int
> www.itu.int
> www.itu150.org
> 
> 
> -----Original Message-----
> From: new-work [mailto:new-work-bounces@ietf.org] On Behalf Of The IESG
> Sent: Friday, June 12, 2015 8:47 PM
> To: new-work@ietf.org
> Subject: [new-work] WG Review: Managing, Ordering, Distributing, Exposing, &
> Registering telephone Numbers (modern)
> 
> 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
> 
> _______________________________________________
> new-work mailing list
> new-work@ietf.org
> https://www.ietf.org/mailman/listinfo/new-work
> 

_______________________________________________ Modern mailing list
Modern@ietf.org https://www.ietf.org/mailman/listinfo/modern