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

["Richard Hill" <[e-mail]>]

Not creating the group would resolve the ITU-T concerns, so it would be a
"del *.*".

 

Ignoring the ITU-T concerns would, in my opinion, lead to even more concerns
being expressed subsequently.


Best,

Richard

 

From: Modern [mailto:[e-mail]] On Behalf Of Gorman, Pierce A
[CTO]
Sent: Thursday, June 25, 2015 21:32
To: Richard Shockey; Alissa Cooper; [e-mail]
Subject: Re: [Modern] Fwd: [new-work] WG Review: Managing, Ordering,
Distributing, Exposing, & Registering telephone Numbers (modern)

 

Which part Richard?  The charter, or the ITU-T concerns?  J

 

Best regards,

 

 

Pierce Gorman

Core Network Planning

O: 913-439-4368

[e-mail]

cid:408000_086801428601145001@pvmxe13g01

 

From: Modern [mailto:[e-mail]] On Behalf Of Richard Shockey
Sent: June 25, 2015 2:10 PM
To: Alissa Cooper; [e-mail]
Subject: Re: [Modern] Fwd: [new-work] WG Review: Managing, Ordering,
Distributing, Exposing, & Registering telephone Numbers (modern)

 

 

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 [phone]

 

 

From: Modern <[e-mail]> on behalf of Alissa Cooper
<[e-mail]>
Date: Thursday, June 25, 2015 at 7:44 AM
To: <[e-mail]>
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" <[e-mail]>

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: "[e-mail]" <[e-mail]>

Cc: "Jamoussi, Bilel" <[e-mail]>

 

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 :[phone]
[e-mail]
www.itu.int
www.itu150.org


-----Original Message-----
From: new-work [mailto:[e-mail]] On Behalf Of The IESG
Sent: Friday, June 12, 2015 8:47 PM
To: [e-mail]
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 <[e-mail]>
 Steve Donovan <[e-mail]>

Assigned Area Director:
 Alissa Cooper <[e-mail]>

Mailing list
 Address: [e-mail]
 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
[e-mail]
https://www.ietf.org/mailman/listinfo/new-work

 

_______________________________________________ Modern mailing list
[e-mail] https://www.ietf.org/mailman/listinfo/modern 

 

  _____  


This e-mail may contain Sprint proprietary information intended for the sole
use of the recipient(s). Any use by others is prohibited. If you are not the
intended recipient, please contact the sender and delete all copies of the
message.