Re: [Enum] ENUM Query

Wayne Cutler <wcutler@gsma.com> Wed, 04 March 2020 12:45 UTC

Return-Path: <wcutler@gsma.com>
X-Original-To: enum@ietfa.amsl.com
Delivered-To: enum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A320E3A0E23 for <enum@ietfa.amsl.com>; Wed, 4 Mar 2020 04:45:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gsmasso.onmicrosoft.com
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 vb_b94BIQvgh for <enum@ietfa.amsl.com>; Wed, 4 Mar 2020 04:45:15 -0800 (PST)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2070.outbound.protection.outlook.com [40.107.20.70]) (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 4B6383A0DF7 for <enum@ietf.org>; Wed, 4 Mar 2020 04:45:15 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; =?utf-8?q?b=3DnnlPpmymZg3uqTSsf7qV1Yd3vSUPA1NqA7Cht8seIsH1WUH957xKaiBXL+7Rs?= =?utf-8?q?pDHNZJhF6dNEHAgW/cq+1QKKPArvwPpanod12+Sw0/6jE86/6WcLSLTN5TXv5KgwX?= =?utf-8?q?YFzYqIce3Jixfd89Y9+vejvWRNKBgyRWwOzrzbblls9zIKQyBYBoWj72LLpFj2RfH?= =?utf-8?q?ZZCaiY+0VjK6N0WuFYvGcejfMSSpnf1B4j6IVkHWc/8fz4fcMeMvG+r53J89Y83de?= =?utf-8?q?jvbYeXdF7+qcrWIz8F/65/G5s9Inknd2D/z36sNB5w3tqDRAHbRI7+/Qz9PvkBZSJ?= =?utf-8?q?B+aEJbK9OOG9U0L88Hfsw=3D=3D?=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; =?utf-8?q?h=3DFrom=3ADate=3ASubject=3AMessage-ID=3ACont?= =?utf-8?q?ent-Type=3AMIME-Version=3AX-MS-Exchange-SenderADCheck=3B?= =?utf-8?q?bh=3DsGllwAZrYl0k1R7AS2KV0qF8GdDXfuXLya3PnTkSlDs=3D=3B_b=3DZU7UOu?= =?utf-8?q?6nqtklATEM7xVTR0xCqJwGw7a1h2EPHftFVxbA9GtmYt4PhuVJ6k5mnF/zsOinX+r?= =?utf-8?q?hIw3HHmqcCoYjzs3+HyZsx6V1Ro4CGodl7QIACJBNiOzlzP4DcNlr9biPhdVukHNa?= =?utf-8?q?2EWbhG585d2M14wy7Z9iL3b2ode2I29Bgs/G6ki6QZFif863GgekzMhNg3P9WY3Qj?= =?utf-8?q?yk9VCqYRUA0T7tB1Q9v+lxJvWd42+MG4ldHq4Vbk5ywfms0XM3/warDiTVVTN5/2z?= =?utf-8?q?NmSHCYTdIPNPubGY33jC6G1R99B/vRbf+E+CcjppRUrxaI9rmr4zW3Q15Uy9G8sZY?= =?utf-8?q?UGLJk5a1dsg=3D=3D?=
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=gsma.com; dmarc=pass action=none header.from=gsma.com; dkim=pass header.d=gsma.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=GSMASSO.onmicrosoft.com; s=selector2-GSMASSO-onmicrosoft-com; =?utf-8?q?h?= =?utf-8?q?=3DFrom=3ADate=3ASubject=3AMessage-ID=3AContent-Type=3AMIME-Versi?= =?utf-8?q?on=3AX-MS-Exchange-SenderADCheck=3B?= =?utf-8?q?bh=3DsGllwAZrYl0k1R7AS2KV0qF8GdDXfuXLya3PnTkSlDs=3D=3B_b=3DH75UkJ?= =?utf-8?q?4p9ah3To9awFRTIBPiAKSZvMNrTGB5iMTwqPxtgU7kwZRYvad1ttSC+bQ1UIVYCOW?= =?utf-8?q?ZWYVMNOOH6IhJ/VHigXu7XwUFcpE/wxLNcoWqb8sJ1fVKXhMIx8h66veDF4TxVAPi?= =?utf-8?q?f/Y3xKs4iDv9yV/hpseEtQ2bkBaHCA+sL1s=3D?=
Received: from DB7PR04MB5418.eurprd04.prod.outlook.com (20.178.104.203) by DB7PR04MB5161.eurprd04.prod.outlook.com (20.176.235.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.15; Wed, 4 Mar 2020 12:45:09 +0000
Received: from DB7PR04MB5418.eurprd04.prod.outlook.com ([fe80::79e8:a6ac:7df9:c295]) by DB7PR04MB5418.eurprd04.prod.outlook.com ([fe80::79e8:a6ac:7df9:c295%4]) with mapi id 15.20.2772.019; Wed, 4 Mar 2020 12:45:09 +0000
From: Wayne Cutler <wcutler@gsma.com>
To: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
CC: Brian Rosen <br@brianrosen.net>, "enum@ietf.org" <enum@ietf.org>
Thread-Topic: [Enum] ENUM Query
Thread-Index: AdXxSRFnBGvgUDfqQUGG0eLpOyEqRQAO0jiAAB7UIfAABIubgAACUg1Q
Date: Wed, 4 Mar 2020 12:45:09 +0000
Message-ID: =?utf-8?q?=3CDB7PR04MB54186234B94264FEA913888EC3E50=40DB7PR04MB5?= =?utf-8?q?418=2Eeurprd04=2Eprod=2Eoutlook=2Ecom=3E?=
References: =?utf-8?q?=3CDB7PR04MB54183341C4145762B969A0B1C3E40=40DB7PR04MB5?= =?utf-8?q?418=2Eeurprd04=2Eprod=2Eoutlook=2Ecom=3E?= =?utf-8?q?=3CADFB7C13-0783-46A8-B9C9-86D503FF87B9=40brianrosen=2Enet=3E_=3C?= =?utf-8?q?DB7PR04MB5418DCD96342D69A51AFDF3AC3E50=40DB7PR04MB5418=2Eeurprd04?= =?utf-8?q?=2Eprod=2Eoutlook=2Ecom=3E?= <alpine.DEB.2.20.2003041130480.19506@softronics.hoeneisen.ch>
In-Reply-To: <alpine.DEB.2.20.2003041130480.19506@softronics.hoeneisen.ch>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=wcutler@gsma.com;
x-originating-ip: [86.167.201.200]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2057a2e9-e1e2-416e-f4e8-08d7c039dfe9
x-ms-traffictypediagnostic: DB7PR04MB5161:
x-microsoft-antispam-prvs: =?utf-8?q?=3CDB7PR04MB5161A275FA0EC8E7FF5D2E81C3E?= =?utf-8?q?50=40DB7PR04MB5161=2Eeurprd04=2Eprod=2Eoutlook=2Ecom=3E?=
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0332AACBC3
x-forefront-antispam-report: SFV:NSPM; =?utf-8?q?SFS=3A=2810001=29=281000902?= =?utf-8?b?MCkoNDYzNjAwOSkoMzk4NTA0MDAwMDQpKDM5NjAwMykoMTM2MDAzKSgzNDYwMDIp?= =?utf-8?b?KDM2NjAwNCkoMzc2MDAyKSgxOTkwMDQpKDE4OTAwMykoNjY5NDYwMDcpKDk2NjAw?= =?utf-8?q?5=29=2845080400002=29=28478600001=29=2855016002=29=2876116006=29?= =?utf-8?b?KDY0NzU2MDA4KSgyNjAwNSkoODYzNjIwMDEpKDUyNTM2MDE0KSg2NjQ3NjAwNyko?= =?utf-8?q?66446008=29=2871200400001=29=289686003=29=2833656002=29=286655600?= =?utf-8?b?OCkoMTg2MDAzKSg0MzI2MDA4KSg4MTE2NjAwNikoODkzNjAwMikoNjUwNjAwNyko?= =?utf-8?q?7696005=29=288676002=29=2881156014=29=2866574012=29=28316002=29?= =?utf-8?q?=282906002=29=2854906003=29=286916009=29=285660300002=29=28535460?= =?utf-8?q?11=29=3B?= DIR:OUT; SFP:1101; SCL:1; SRVR:DB7PR04MB5161; H:DB7PR04MB5418.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: gsma.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: =?utf-8?q?DqQxYDzlUCHn1ukclSH5tYKVGicpzp4?= =?utf-8?q?HjeTcA83YRVCEPlRNVU5+gZZca3o+FmgOb5fmE6OzYNa2ZW8HYfXc5rbCYPfPkwwS?= =?utf-8?q?OGY5kLft+GCPozH7cMvDIwWWzYwVK4hwvmdOxuHXdIZZjKGnqw3TgMx0MOa7+Z2Cq?= =?utf-8?q?pYb39Mr10jcLcV3Vj//wCjuVl8CdkU2mjGT9F3+gd893J7P34FASBFbJ0k0PGJ3tE?= =?utf-8?q?rHoSpav7dAYkaB2cXqxGDnCj7xs199ZsFymTkAQ5h682Hu/GsBPIBx5m27Co0gglS?= =?utf-8?q?dpQF1PBiJXWi/92y/ODA6xbyRd4cU80yemeikAEZ9UwR0XWMrribQBkWk6AGW+8jN?= =?utf-8?q?iZMz0elQHxXLN4T+PGGZO/Mmr2ZvHvi0vzXyt90dRPlyJtSI/wdk4I7siiVW5Mue4?= =?utf-8?q?rA36xx+l8K0qi+LcJu8h9wsJimCDTjSWUebYr+LtbFuQ9xi3wARCYJNFGJdDqeotJ?= =?utf-8?q?s8+/CuWzyJjwRISUiFQQkZUFPTcfR8b9o7EG+AzeY9ojcXGKLYeOTIzGnCfCxhXTU?= =?utf-8?q?7GheRR3avyP6N43CXhc2h1De1+008pPnmf7AH9Qq/CS4mfhBaavUS3JmAjGinXjP6?= =?utf-8?q?lE3m8cCzPDWKl7Ztou8wvuin?=
x-ms-exchange-antispam-messagedata: =?utf-8?q?MpaJi1Q6Xt93IAMtkQOt3i/SHHbMq2?= =?utf-8?q?lu+WnZGGCixeV3hcry0NnZpRHRm/b+jI/ezMMA9lzsynHKJi//ieomTyZK+161nlg?= =?utf-8?q?NmtknVEIpxZJ++1sHqarFwQMwSv+/YSkqjM3dshudY5dEl3bocQ4E+A=3D=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: gsma.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2057a2e9-e1e2-416e-f4e8-08d7c039dfe9
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2020 12:45:09.7135 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72a4ff82-fec3-469d-aafb-ac8276216699
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: =?utf-8?q?/g5PoWhyy3ipBnV8SKEI2?= =?utf-8?q?1r0S/qfqji+HbOS7gs6ebOTQ53pzpb98Weah1asEz+UMRshNyE1EPpvhvFy7PqZCQ?= =?utf-8?q?=3D=3D?=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR04MB5161
X-MS-Exchange-CrossPremises-AuthAs: Internal
X-MS-Exchange-CrossPremises-AuthMechanism: 04
X-MS-Exchange-CrossPremises-AuthSource: DB7PR04MB5418.eurprd04.prod.outlook.com
X-MS-Exchange-CrossPremises-TransportTrafficType: Email
X-MS-Exchange-CrossPremises-TransportTrafficSubType:
X-MS-Exchange-CrossPremises-SCL: 1
X-MS-Exchange-CrossPremises-messagesource: StoreDriver
X-MS-Exchange-CrossPremises-BCC:
X-MS-Exchange-CrossPremises-originalclientipaddress: 86.167.201.200
X-MS-Exchange-CrossPremises-transporttraffictype: Email
X-MS-Exchange-CrossPremises-transporttrafficsubtype:
X-MS-Exchange-CrossPremises-disclaimer-hash: aec8266e882fb4f8d424fb644b62ffb96bb5589a477100b41df8a31983dca2b9
X-MS-Exchange-CrossPremises-antispam-scancontext: DIR:Originating; SFV:NSPM; SKIP:0;
X-MS-Exchange-CrossPremises-processed-by-journaling: Journal Agent
X-OrganizationHeadersPreserved: DB7PR04MB5161.eurprd04.prod.outlook.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/enum/JCSABg6WysvqprEU3NyWbRJy7Ws>
Subject: Re: [Enum] ENUM Query
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/enum/>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2020 12:45:22 -0000

Hi Bernie,
See below..

Best Regards,
Wayne Cutler

-----Original Message-----
From: Bernie Hoeneisen [mailto:bernie@ietf.hoeneisen.ch]
Sent: 04 March 2020 10:44
To: Wayne Cutler <wcutler@gsma.com>
Cc: Brian Rosen <br@brianrosen.net>et>; enum@ietf.org
Subject: Re: [Enum] ENUM Query

“This email has been received from an external source – please review before actioning, clicking on links, or opening attachments”


Hi Wayne

To better assess the scope, I also have some questions:

1) What URI Schemes are currently specified to be used in the NAPTR RRs of the ENUM response (for each of the services RCS and MMTEL)?

WC - At the current time, the SIP URI scheme (RFC 3764) is specified in GSMA document NG.105 (" ENUM Guidelines for Service Providers and IPX Providers") for addressing a target IMS network. This is fine for MMTEL-only and MMTEL/RCS via single registration. It is intended to enhance NG.105 to account for the dual registration case - hence this thread. The document NG.105 describes "Carrier ENUM" - a private ENUM infrastructure for the telecommunications industry.

2) How likely do you think is it that further URI Schemes will be added in future (for each of the services RCS and MMTEL)?

WC - Highly unlikely. This is about routing SIP requests to the correct IMS network.

3) How do you think that further services (in addition to RCS and MMTEL) will be added in future?

WC - Difficult one to answer without a crystal ball. I would say that there may be future MNO-provided services may be non-SIP/IMS based and such services may be able to use other existing ENUM responses or not. In this case, we are focussed on SIP/IMS based MNO-provided services and the need to address the dual registration deployment option. It is likely that further services will be added to the RCS suite of services - but all RCS related service requests would be routed identically to the appropriate IMS core network.

4) What is your prediction on SMS to be moved to RCS in future?

WC - I would say that SMS will never be moved to RCS.

All the Best,
  Bernie Hoeneisen, IESG Appointed Designated Expert for ENUM

--

https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fucom.ch%2F&amp;data=02%7C01%7Cwcutler%40gsma.com%7C5ea0021bf0614dd5441108d7c028fde4%7C72a4ff82fec3469daafbac8276216699%7C0%7C0%7C637189155206270379&amp;sdata=Gm1avA8WQRFrNffpPZ1Km7xlJD%2BywiWTv%2BtAdKQn%2Fvg%3D&amp;reserved=0
Modern Telephony Solutions and Tech Consulting for Internet Technology


On Wed, 4 Mar 2020, Wayne Cutler wrote:

>
> Hi Brian,
>
> Thanks for your questions. Please see below in line..
>
>
>
> Regards,
>
> Wayne
>
>
>
> From: Brian Rosen [mailto:br@brianrosen.net]
> Sent: 03 March 2020 17:51
> To: Wayne Cutler <wcutler@gsma.com>
> Cc: enum@ietf.org
> Subject: Re: [Enum] ENUM Query
>
>
>
> “This email has been received from an external source – please review before actioning, clicking on links, or opening attachments”
>
>
>
> One question: are the services that are provided on these two networks distinct?
>
> WC - Yes.  The service-sets offered on the two networks do not intersect.
>
>
>
> Do one or both of them supply messaging service?  Calling Service?
>
> WC - Yes.  RCS offers a number of messaging services.  MMTEL offers
> voice and video calling.  For historic reasons,  SMS (which is
> technically a messaging service) is part of the service-set associated with MMTEL. So, in the dual-IMS core scenario, one IMS core provides voice/video/SMS and the second IMS Core provides RCS Messaging.
>
>
>
> If both, then how is a message/call to the TN routed?
>
> WC - GSMA defines two disjoint sets of services, which we refer to as
> RCS and MMTEL.  The desire is that the ENUM response provide 2 URIs,
> one for each service-set, each of which resolve to an entry point to the network providing that service-set.  These URIs can be the same or different (i.e. covering the single/dual IMS core(s) use cases).
>
>
>
> I think we would want to have some service differentiation as the discriminator if its one network that supplies each service.
>
> WC - Agreed.  GSMA is responsible for the mapping of service requests
> to a service-set.  We intend that the ENUM response provide a URI for each service-set.  What seems to be lacking is an ENUM service for the RCS Messaging service-set.
>
>
>
> Brian
>
>
>
>       On Mar 3, 2020, at 6:00 AM, Wayne Cutler <wcutler@gsma.com> wrote:
>
>
>
> Dear ENUM List,
>
> I have an ENUM Registry query that I’d like to run past you to solicit expert feedback/recommendations on the best way forward.
>
>
>
> The scenario that is applicable concerns the deployment of MMTEL
> (Multi-Media Telephony) & Advanced RCS Messaging by MNOs (Mobile
> Network Operators). For historic reasons, there are two different ways
> that MNOs have deployed MMTEL & RCS Messaging services :-
>
> i)                    Both MMTEL & RCS Messaging services are provided by a single IMS Core Network and the UE registers to this
> single IMS core to receive all of its services. All terminating
> service requests are required to be routed to the single IMS network.
> Therefore, the existing ENUM infrastructure is fine for this scenario as the telephone number of a given user resolves to a SIP URI that identifies the target IMS core network.
>
> ii)                   The MMTEL and RCS services are provided by 2 separate IMS Core Networks - one for MMTEL and one for RCS
> Messaging. In this scenario, the UE registers to both IMS core
> networks (so-called "dual registration") and gets its full suite of
> services via a combination of the 2 IMS cores.  The same IMPU (IMS
> Public User Id) is used for both IMS registrations and the same phone
> number is used to route terminating service requests for both MMTEL &
> RCS Messaging related requests. Therefore, in this case, an ENUM request for a given telephone number needs to be able to identify 2 different target IMS cores. The related service request can then be passed onto the correct IMS core based on the its context (i.e. does the request relate to a MMTEL or RCS Messaging service). This is the scenario that doesn't seem to be covered in the existing ENUM Registry.
>
>
>
> So, the problem we have is how to resolve a single telephone number to
> 2 different SIP URIs. Looking at the existing ENUM registry, there
> seems to be 3 options :-
>
> ·       Enhance the current ProtocolBasedClass of SIP as defined in RFC 3764 to add a sub-type - e.g. "SIP/MMTEL" & "SIP/RCS" -
> with the absence of a sub-type meaning "all services".
>
> ·       Re-use (or perhaps re-interpret?) an existing result (e.g. ApplicationBasedClass of IM or unifmsg) to mean RCS Messaging -
> but this feels like a kludge,
>
> ·       Define a new ENUM registry entry to identify RCS Messaging.
>
>
>
> I would be grateful of any advice / recommendation that you have and am happy to answer any further questions for clarification.
>
>
>
> Best Regards,
>
> Wayne Cutler
>
>
>
>
>
> .
>
> _______________________________________________
> enum mailing list
> enum@ietf.org
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> ietf.org%2Fmailman%2Flistinfo%2Fenum&amp;data=02%7C01%7Cwcutler%40gsma
> .com%7C5ea0021bf0614dd5441108d7c028fde4%7C72a4ff82fec3469daafbac827621
> 6699%7C0%7C0%7C637189155206270379&amp;sdata=9KAN9TKpLdPVv%2Fwxbyy5Cgmz
> uQrAjMHzjs8k0VkZiA8%3D&amp;reserved=0
>
>
>
> .
>
>
>
.