Re: [Enum] non-E.164 Numbers in ENUM

Jim Reid <jim@rfc1035.com> Wed, 15 September 2004 19:09 UTC

From: Jim Reid <jim@rfc1035.com>
Date: Wed, 15 Sep 2004 15:09:04 -0400
To: "Yu, James" <"james.yu at neustar.biz">
Subject: Re: [Enum] non-E.164 Numbers in ENUM
In-Reply-To: <941284C9668BFD4FB342F1FF01ECA8240314A0@stntexch02.cis.neustar.com>
Message-ID: <17634.1095274706@gromit.rfc1035.com>
MIME-Version: 1.0
Content-Type: text/plain
Status: R

>>>>> "James" == Yu, James <james.yu at neustar.biz> writes:

    James> ENUM resolver (one that generates the ENUM query for a
    James> phone number) can only check if the phone number has more
    James> than 15 digits (a valid E.164# is up to 15 digits long)
    James> because it is not likely to understand the numbering plan
    James> in every country.  It won't be able to know if
    James> 1-571-434-1234-5 is a valid E.164# if it does not
    James> understand the numbering plan for country code 1.

Indeed. In fact it would be very foolish for anyone to put a priori
knowledge of a numbering plan into an ENUM resolver. Especially on an
embedded device like a handset. Numbering plans change. Pretty much
all an ENUM resolver could/should do is check that the input string
conforms to the length and legal character set defined in E.164.

_______________________________________________
enum mailing list
enum at ietf.org
https://www1.ietf.org/mailman/listinfo/enum