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

"Gorman, Pierce A [CTO]" <Pierce.Gorman@sprint.com> Thu, 25 June 2015 19:32 UTC

Return-Path: <Pierce.Gorman@sprint.com>
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 632491ACD55 for <modern@ietfa.amsl.com>; Thu, 25 Jun 2015 12:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.928
X-Spam-Level:
X-Spam-Status: No, score=-1.928 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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 axYUfqE1HBIO for <modern@ietfa.amsl.com>; Thu, 25 Jun 2015 12:32:14 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0121.outbound.protection.outlook.com [207.46.100.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F29B1ACD28 for <modern@ietf.org>; Thu, 25 Jun 2015 12:32:13 -0700 (PDT)
Received: from BY2FFO11FD002.protection.gbl (10.1.14.32) by BY2FFO11HUB011.protection.gbl (10.1.15.222) with Microsoft SMTP Server (TLS) id 15.1.201.10; Thu, 25 Jun 2015 19:32:07 +0000
Authentication-Results: spf=permerror (sender IP is 144.230.172.36) smtp.mailfrom=sprint.com; ietf.org; dkim=none (message not signed) header.d=none;
Received-SPF: PermError (protection.outlook.com: domain of sprint.com used an invalid SPF mechanism)
Received: from plsapdm1.corp.sprint.com (144.230.172.36) by BY2FFO11FD002.mail.protection.outlook.com (10.1.14.124) with Microsoft SMTP Server (TLS) id 15.1.201.10 via Frontend Transport; Thu, 25 Jun 2015 19:32:07 +0000
Received: from pps.filterd (plsapdm1.corp.sprint.com [127.0.0.1]) by plsapdm1.corp.sprint.com (8.15.0.59/8.15.0.59) with SMTP id t5PJVvka002255; Thu, 25 Jun 2015 14:32:06 -0500
Received: from plswe13m07.ad.sprint.com (plswe13m07.corp.sprint.com [144.229.214.26]) by plsapdm1.corp.sprint.com with ESMTP id 1v8n7e1apt-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 25 Jun 2015 14:32:06 -0500
Received: from PLSWE13M08.ad.sprint.com (2002:90e5:d61b::90e5:d61b) by PLSWE13M07.ad.sprint.com (2002:90e5:d61a::90e5:d61a) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Thu, 25 Jun 2015 14:32:05 -0500
Received: from PLSWE13M08.ad.sprint.com ([fe80::948e:8473:1735:b216]) by PLSWE13M08.ad.sprint.com ([fe80::948e:8473:1735:b216%15]) with mapi id 15.00.1044.021; Thu, 25 Jun 2015 14:32:05 -0500
From: "Gorman, Pierce A [CTO]" <Pierce.Gorman@sprint.com>
To: Richard Shockey <richard@shockey.us>, Alissa Cooper <alissa@cooperw.in>, "modern@ietf.org" <modern@ietf.org>
Thread-Topic: [Modern] Fwd: [new-work] WG Review: Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers (modern)
Thread-Index: AQHQr31oVhNQitnoIUyGmpgejVxL7J29nAuQ
Date: Thu, 25 Jun 2015 19:32:04 +0000
Message-ID: <963da9c467264967a5b96bc81a08bb44@PLSWE13M08.ad.sprint.com>
References: <9bdeb496cc524575a4ece857fa54e56f@TUCM03.TUECSP.UNICC.ORG> <10E9C750-6B20-4258-B538-F64AB40269B2@cooperw.in> <D1B1CA46.27FAC%richard@shockey.us>
In-Reply-To: <D1B1CA46.27FAC%richard@shockey.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.214.116.22]
Content-Type: multipart/related; boundary="_004_963da9c467264967a5b96bc81a08bb44PLSWE13M08adsprintcom_"; type="multipart/alternative"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Microsoft-Exchange-Diagnostics: 1; BY2FFO11FD002; 1:54MSe8MvTNyBQInNi0s8tirNZA4h9v3+B09jlPv3zmec7BqqAMsU7q7ttYX/V1j0XIUWO1k/usj7aqO0Vg5Vu8DmytwVqnh1Kqi7mtUm2DrsNpegUFj/EdjuFP+aPVya2KgqdMJ79i6rqFdCOsl7+U8nOsSkYm2NjZHOvFPPptsbB5AqiYKs2wBvFF21xFDU8t5S4yxllB+6UGWdrv/VQtv2O4T3/CivFX/SMyS5+PWI2NYO/LiRA7kUpTdYrRb/4ZlZemikPI0cdIe9ChXIyanUKPpRaj+RvlYJctKRM4V0UCl3ovcI98dz3xT5QJlX
X-Forefront-Antispam-Report: CIP:144.230.172.36; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(2980300002)(448002)(2473001)(45074003)(377454003)(13464003)(60444003)(189002)(199003)(19625215002)(108616004)(5003600100002)(77156002)(19580395003)(15975445007)(24736003)(102836002)(92566002)(18206015028)(62966003)(2656002)(5250100002)(87936001)(84326002)(2950100001)(85326001)(106466001)(76176999)(2900100001)(54356999)(2501003)(86362001)(575784001)(19580405001)(107886002)(5001960100002)(512954002)(189998001)(99936001)(46102003)(33646002)(19627595001)(19617315012)(5001770100001)(17760045003)(106116001)(66926002)(30436002)(67866002)(50986999)(16601075003)(6806004)(15974865002)(7099028); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2FFO11HUB011; H:plsapdm1.corp.sprint.com; FPR:; SPF:PermError; MLV:sfv; MX:1; A:1; LANG:en;
X-Microsoft-Exchange-Diagnostics: 1; BY2FFO11HUB011; 2:lSKFXe26aPzAjScI4ZxQnwD841e1ApEfAOJ6Gcs2a2qjxCuyGGdF/a6o1yI1CkBL; 3:nk/glaf/jQVGn1jDxefXSfzuCMeTyLKr/eYyZQczgllHkLL71udjEdPW+228aw8BRFm/2nqT/lwQX4ikGEKd8RoLTOi2HEv9TsX84bZ+3oWk+bD+NJIxzE2nR8UZHBWAGQ5YQQPX9j9BVk91SkweDE11VhShsiEkhY01xkDrWrx5Db+sUyYsA/CJ7EKA2jOS9c3mLg7OTVEf2fd1X2As1FKYiDbaq+yiunjSCGfnhyHNrVnjRrums8fxGvns6hrP; 20:eM9ZbfF7qqMiwrUdLgK9wM9u7XGh70VhuEjzgO3vDkFTpEQ7N2dExyZj9xCBaZyNwbrbj9LzS6Q8d4P/n7Q34UQPUyIOTdMLpwnJmiyzTNTME2rsjoqeJieOlyC6SudkuiUd9/kaldymoB0a4bAb2Xd4rQnQdkPX9REa/9mrfxSn8dUBVARfQX0x9s3awEa3/iHRPgzeyz7ffwrzrDo/EWz3+jOYFaEGizrJY0gidIGG10ALfX4WBpDFZ+/hM95Y; 4:bYkXipNdkj/Lisq++P1sbI+lFF2MydcbNhu/lB/fbPH3bIFQHXceQH0Y59fzf02Vi66F4PWZB/MuSRHvk4Im2k7QtYpD2yZJlnWyN6veglIZqXpq35cHj7mm9wM1958Dlz3D9Dc6mPRafPRHqOEMIt1PFP3GBrYdtfqtBIw6SzcpZcFm0G+OMx/JDdpDdLsqwQzwzwd4+HGBq/Xe3vGFM9J0U/6H1PwIaFG+4S51O5GkKS87FgCntfGeDORqCzI7leMEfiP2mF7ja19ZiWkipcimC06XXH0U039fYmKNP8M=
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2FFO11HUB011;
X-Microsoft-Antispam-PRVS: <BY2FFO11HUB011546A28CB3DE955A2CC4F89AE0@BY2FFO11HUB011.protection.gbl>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:BY2FFO11HUB011; BCL:0; PCL:0; RULEID:; SRVR:BY2FFO11HUB011;
X-Forefront-PRVS: 0618E4E7E1
X-Microsoft-Exchange-Diagnostics: 1; BY2FFO11HUB011; 23:nkkgJsbBFZwVbl8U6QP44lCI74giZh2rk3xVvRnEI5qpFnhO56vGSIwwfMQYIL4A/SWcA5dt0AJy5xM+l47sIm8GSQaQ03QPmDKSYwlCKGVkbmUSHxIhRdmRt5Bk6yz9fE9vpSVyd35cMl6K9kMHSh7BjRF397FBc/2dYGSI90/tpm6rKW0IE8U301Grb+GFflUuOxblvWzy9VAiYRirUgj3Qmak4HHEzAvCqhdX1qSiYerKiMiEltYkgufXpuj2fMaRae5OQSwxU3XUa3l/AfSmxmEQ7Kt/iX0YwRC46sdqcjKF6dDSqViWLOzdSqeHk/yB4j3D60HWR7nvGTWr2xSe9MhBq3eyJYI7A7C6tN2I1zLnb5342L0Vw7UyiFITI7n6yevBD77mV++rDZlBmA1HL8xdhnQUiO3Xafhq2jozUrwysuGpPz5BxbwoMRM+2+ar2pQf+19StyHPqYOxNIcLu4WqKkDh/9SfhOhq3TgtYyz4/MISqQR7SIydCYBHp13LoPs5tnattl3NBzY32J58dNPIZGPB3OrUeZ3cNTZGJRQ4ntSmjayb4NSAsoQsMRXK8+/ald39epjEQPEngIsV7WbN7G0irF5wS5oqQ3yc5bMSc3vnuqmHz335nu5ysH4aZXA0mHzM+KBUEOjFfAG/lIjFJ7BDGfl2MFq36wk2a8yZ4BT7xuJhF2lj4C/55qhrjv/GOQwPHs6uPpdcZDNpstUOcULhxAkuD4U6vUFr6evhpABlrsb7DE0bwMqM/0Kb5J5fShONj7PAfRM6xjz+We+Uf4O6ZDc5Yc96Du7/iJWBsduHpNPMcrGgENEKc2HQU3n9jA9Hdzx66LZ+6Nc8ee4EYeJcBiEJVZp1Tz94Umyi04saE4N96Ho4imXow8/PmEnWo/v8Oj891D3SppUYqYhZ+gncReKgI7Vu4T/4EHJaeY9ibievQ6L9gqCLp/Vj+NY6i04gZ2I1QetOpdNqucnPG7edAiEzeFXP2cThsI4OGWxUqg+e3jHOmCIrdgxyGYw/D2L5wkOEfjwtnIUqZnZpFTckATa7jiWoyf3rwlJjpp0VNlwZsJJudkCRdPJreE1BQOQastaDq9snoC9ypXTWc7UsEUzkT0NZkHuP2YpLdOgl+2QxYcg6Hvqbu5tgpn1Q4zMiizDUBHfz4uDOBhkA5EErIbmh8rLbrmgl+95oLOTc0Mc9SulUuzqvqSWOAvszrq3B4Na9wjEdooo3BB7xEpcYTy6LcpO3vsW/+I0RjC1OIoIxgvEszjFb2N0+ZGf2c8nqIMO8RrqnltCApb6LU98mymH0wnt8yEamNpnYIJL1FJqjj4AHfVP2V7FwsuF4BnIDQDtJoXOEJ6ZoRtVyAHojdZyvAVQYhlF6JRqkerRfUd1mD0flPQgp
X-Microsoft-Exchange-Diagnostics: 1; BY2FFO11HUB011; 5:OBH4FtR5effsHKRM8hkfblkO/PMWdVXEXYlvBSO0mULvFCynanjEpAbEiLeRlsTfhfT+hKOFY5qP1dW44ZCdy9Qw+KorlQyVw2UTEQ8UIlJWVagPBX/2erZDRJZu45wBbB6MNIH1WVQveC3e+o1Qjw==; 24:s4Gti/U6/D0DL6AYVpTi6LZ0Fs1Y4MIoXOapgTnwyaY4QnoDEFZZxGZly+rfjNhQp05zhCj0vsj3cHpRcfldHnID6B3XRn06vwLeHAfPH6c=
X-OriginatorOrg: sprint.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 25 Jun 2015 19:32:07.1299 (UTC)
X-MS-Exchange-CrossTenant-Id: 4f8bc0ac-bd78-4bf5-b55f-1b31301d9adf
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=4f8bc0ac-bd78-4bf5-b55f-1b31301d9adf; Ip=[144.230.172.36]; Helo=[plsapdm1.corp.sprint.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2FFO11HUB011
Archived-At: <http://mailarchive.ietf.org/arch/msg/modern/TNORhG2kSYpiS4AihZypJH18f1E>
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:32:21 -0000

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

Best regards,


Pierce Gorman
Core Network Planning
O: 913-439-4368
pierce.gorman@sprint.com
[cid:408000_086801428601145001@pvmxe13g01]

From: Modern [mailto:modern-bounces@ietf.org] On Behalf Of Richard Shockey
Sent: June 25, 2015 2:10 PM
To: Alissa Cooper; modern@ietf.org
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<http://www.shockey.us>
www.sipforum.org<http://www.sipforum.org>
richard<at>shockey.us
Skype-Linkedin-Facebook rshockey101
PSTN +1 703-593-2683


From: Modern <modern-bounces@ietf.org<mailto:modern-bounces@ietf.org>> on behalf of Alissa Cooper <alissa@cooperw.in<mailto:alissa@cooperw.in>>
Date: Thursday, June 25, 2015 at 7:44 AM
To: <modern@ietf.org<mailto: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<mailto: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<mailto:iesg@ietf.org>" <iesg@ietf.org<mailto:iesg@ietf.org>>
Cc: "Jamoussi, Bilel" <bilel.jamoussi@itu.int<mailto: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<mailto:jie.zhang@itu.int>
www.itu.int<http://www.itu.int>
www.itu150.org<http://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<mailto: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<mailto:tom.mcgarry@neustar.biz>>
 Steve Donovan <srdonovan@usdonovans.com<mailto:srdonovan@usdonovans.com>>

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

Mailing list
 Address: modern@ietf.org<mailto: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<mailto:new-work@ietf.org>
https://www.ietf.org/mailman/listinfo/new-work

_______________________________________________ Modern mailing list Modern@ietf.org<mailto:Modern@ietf.org> 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.