Re: [Enum] ENUM Query

Brian Rosen <> Mon, 09 March 2020 15:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B5C903A1289 for <>; Mon, 9 Mar 2020 08:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 66-Cxz5wSjOP for <>; Mon, 9 Mar 2020 08:50:19 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::c42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A2CB13A12A6 for <>; Mon, 9 Mar 2020 08:50:19 -0700 (PDT)
Received: by with SMTP id i1so6327079ywf.4 for <>; Mon, 09 Mar 2020 08:50:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UhI2B4pjVXnfIMryT11je5/F+8py4dbFAi6AsoNU/x8=; b=2UAKhWcfeV96GzbNvld4+LGESsIekm0sZ6KNsbxNQqzTALON3a+sYntnqtYBgEAJ/v 3B0b6wcwEgQQZw6vYu2fsyD1FiDxSZzxfX36VK0LwnIma/Py38qMh1YTtw1WITXQukoH JbAXJEjbQ+KQHxfYwj0Mg2cB5JU5yRd3QXP9tO3kN7x6EQG9tvuFeqfTNE/vsl5ACzvL KUWShHN8je5rh51DVUbVmYBTDM8irGL79nsudD5L0/FP9HYf/Wa9K9m6JGE0HhxkifQP IQUOHT7T/jHUQI3Wg7/VLCK5ExLK06lrH/oN+gwVGFlUkLpM94h2MAbnAwjNUnDQbt4P XZqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UhI2B4pjVXnfIMryT11je5/F+8py4dbFAi6AsoNU/x8=; b=egqbbR0r7yRNUqWzrEzIaMcMD4qRjh8D8BSjKTTMp/1KDOgTBnlVIJ1LDDAygvDAXF tA5ZjKulEXtMHNQor2fVx9ppMwMhA4NYFgvRU7AaKOu8kgxawiXTcB/T9W8r+z81LKGl VxLZ7dlL4ttSn4EKgnQEen3UUTbbfvzIwGgLiCM/1MXdm9lqoRwwm9sPlKYfWg8kxFzy pgccGWfBBJIDYGzKaUy0fNcUktfHKbhAo/uZjoHVuY+Kjvz4uW2IP9QcgLW5fbZNB2vt 0OinmFud3DlVRNGu1mNtCcrQmwR6qvZHkQGC+Z/3QWXyJHnDabewzDBtmIBJ9fV9EUqO Dt+w==
X-Gm-Message-State: ANhLgQ0nhhZ2txVjeItpcKptxIqdGhyjshYrw+az9jBecMdHD8qOuNYb TeYNplFIx9Bc8XAlJfQa/ZueudEKjwDQcw==
X-Google-Smtp-Source: =?utf-8?q?ADFU+vtkwyTcGeh7eWB6Y3oqkVZuC2UKdD/VquI9JrAI?= =?utf-8?q?7ymvPgxEScsrOvd0IMz6AJkHpIOTbdjDGQ=3D=3D?=
X-Received: by 2002:a0d:e583:: with SMTP id o125mr18518729ywe.303.1583769017488; Mon, 09 Mar 2020 08:50:17 -0700 (PDT)
Received: from brians-mbp-2871.lan ([]) by with ESMTPSA id z126sm7694191ywb.49.2020. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Mar 2020 08:50:16 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.\))
From: Brian Rosen <>
In-Reply-To: <>
Date: Mon, 9 Mar 2020 11:50:15 -0400
Cc: Wayne Cutler <>, "" <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
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?= =?utf-8?q?=3Calpine=2EDEB=2E2=2E20=2E2003041130480=2E19506=40softronics=2Eh?= =?utf-8?q?oeneisen=2Ech=3E_=3CDB7PR04MB54186234B94264FEA913888EC3E50=40DB7P?= =?utf-8?q?R04MB5418=2Eeurprd04=2Eprod=2Eoutlook=2Ecom=3E?= =?utf-8?q?=3Calpine=2EDEB=2E2=2E20=2E2003071103230=2E19506=40softronics=2Eh?= =?utf-8?q?oeneisen=2Ech=3E_=3CDB7PR04MB5418E392AD73AF330044E0F2C3FE0=40DB7P?= =?utf-8?q?R04MB5418=2Eeurprd04=2Eprod=2Eoutlook=2Ecom=3E?= <>
To: Bernie Hoeneisen <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [Enum] ENUM Query
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Enum Discussion List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 09 Mar 2020 15:50:22 -0000

I think adding new enumservices for both rcs and mmtel is a good way forward.

While we could eventually not see anyone using the sip enumservice for messaging, it is, and will be widely used for voice calls.  


> On Mar 9, 2020, at 10:49 AM, Bernie Hoeneisen <> wrote:
> Hi Wayne
> My comments inline.
> On Mon, 9 Mar 2020, Wayne Cutler wrote:
>> So, we are after a mechanism to get a SIP URI for the RCS Messaging Services, and these services comprise things like 1:1 Chat, File Transfer, Geolocation Push etc.
>> Regarding the differences between RCS Messaging and im/unifmsg, I would say that :-
>> 1) im allows users to send and receive typically short, often textual messages in near real-time - which sounds a lot like RCS Chat - and returns an IM URI. So, I think that RCS is more general than im and also the need to translate from the im URI to a SIP URI is an additional minor nuisance.
>> 2) unifmsg is about having a unified (voice/video) mailbox capability in the event of a user being unreachable. The RCS services aren't really about the user being unreachable and so this is not really a good fit IMO.
> Thanks for clarification.
>> So, I think the proposal to have a new Application-Based Enumservice seems reasonable to me. What would be the next steps? Writing an Internet Draft presumably?
> RFC 6117 defines the process in details
> cf.
>> Regarding the suggestion to also take a similar approach for MMTEL, I think there are backwards compatibility issues as there are implementations already out there that use the Protocol-Based Enumservice "sip" for MMTEL. Therefore, this is something we wouldn't want to do.
> Not sure this creates a new backward compatibility issue. AFAICT, using two new Enumservices, new systems would be more efficient and less prone to ambiguities. And in the long run you'd get a clean system.
> - for old systems you probably need to maintain "sip" (only)
>  (provision and lookup). You may add a recommendation to at
>  least provision also the new Enumservices "mmtel:sip" and "rcs:sip"
>  (pointing to the same as "sip"), which is easy to implement.
> - for new systems you could specify:
>  - Lookup: use "rcs:sip" or "mmtel:sip" (with priority);
>    use "sip", only if no hit with rcs or mmtel (fallback)
>  - Provision: "rcs:sip" and "mmtel:sip" would point to the respecive
>    services,
>    while "sip" could be provisioned to help old systems to find the
>    correct service, e.g. a redirection service (or alike) or a system
>    that can deal with requests for the "wrong" (mmtel vs. rcs) service.
> You could deprecate "sip" Enumservice and after a long enough transition period, you may get rid of the "sip" Enumservice altogether.
> Does this make sense for your environment?
> cheers
> Bernie
> _______________________________________________
> enum mailing list