Re: [Enum] ENUM Next Generation

Bernie Hoeneisen <bhoeneis@switch.ch> Sun, 09 July 2006 14:53 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FzafS-0001oH-9R; Sun, 09 Jul 2006 10:53:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FzafR-0001oC-Hv for enum@ietf.org; Sun, 09 Jul 2006 10:53:53 -0400
Received: from central.switch.ch ([130.59.11.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FzafQ-0008Eh-7J for enum@ietf.org; Sun, 09 Jul 2006 10:53:53 -0400
Received: from machb.switch.ch ([130.59.6.129]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1FzafO-0005v8-00; Sun, 09 Jul 2006 16:53:50 +0200
Date: Sun, 09 Jul 2006 16:53:43 +0200
From: Bernie Hoeneisen <bhoeneis@switch.ch>
X-X-Sender: bhoeneis@machb
To: Patrik Fältström <paf@cisco.com>
Subject: Re: [Enum] ENUM Next Generation
In-Reply-To: <187818D2-7193-4B9F-963A-4E87D10F5A58@cisco.com>
Message-ID: <Pine.LNX.4.64.0607091551160.18928@machb>
References: <187818D2-7193-4B9F-963A-4E87D10F5A58@cisco.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="98048-1941616486-1152456823=:18928"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: IETF ENUM WG <enum@ietf.org>
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
Errors-To: enum-bounces@ietf.org

Hi Patrik

Interesting ideas...
Comments inline.

On Sun, 9 Jul 2006, Patrik Fältström wrote:

> Then we issue a 2nd query depending on what we are looking for either of 
> these two:
>
> _sip._enum.4.3.2.1.8.6.4.e164.arpa. IN URI "sip:081234@sipprovider.net"
>
> _smtp._enum.4.3.2.1.8.6.4.emailprovider.net. IN URI "mailto:081234@sipprovider.net"

could it be that this example (smtp) contains a typo?
I would rather expect:

_smtp._enum.4.3.2.1.8.6.4.e164.arpa. IN URI "mailto:081234@emailprovider.net"

Or did I miss anything?

> and (a good thing for infrastructure ENUM I think) it is possible to 
> do delegations from the zone that is today User ENUM to the service 
> providers. I.e. if the zone for the E.164 is held by a neutral party (just 
> like the parent zone(s)), the delegation for the tel service field can be 
> made to the carrier of record for the E.164 number.

Hmmm, this would involve, that the Tier-1 Registry (or some other 
trusted party) needs to maintain the U-ENUM Zones, to ensure correct 
delegations to the I-ENUM entries.
Carriers put stronger requirements to (DNS) answering times and timeouts, 
as the call-setup time is crucial. Therefore no way, that a user can 
operate his own nameservers.
You could also not leave the U-ENUM zone maintainance to the carrier, as 
this might be misused to hinder or control (in a negative sense) the 
U-ENUM deployment.
Anyways, IMHO this is not backward compatible to nowadays ENUM deployment.

Furthermore this would also kind of mandate RFC 4114, Dynamic DNS updates 
or some other (possibly new) interface to change the content of the U-ENUM Zones.

> Now, what do you say?

I like the idea to keep the zones small (packet size/EDNS0 discussions), 
but I am not sure, whether this is a good way to combine U-ENUM and 
I-ENUM.

BTW: Could your idea have impact on block delegations or open numbering 
plans? I haven't studied that through yet.

cheers,
  Bernie
_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum