RE: [ITU+IETF] RE: [Enum] Re: Structure of DNS entry for ENUM

"Lind, Steven D, ALARC" <sdlind@att.com> Mon, 07 February 2000 20:20 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20792 for <itu+ietf-archive@ietf.org>; Mon, 7 Feb 2000 15:20:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02953 for <itu+ietf-web-archive@optimus.ietf.org>; Mon, 7 Feb 2000 15:18:50 -0500 (EST)
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20787; Mon, 7 Feb 2000 15:20:16 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02864; Mon, 7 Feb 2000 15:18:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02816 for <itu+ietf@optimus.ietf.org>; Mon, 7 Feb 2000 15:18:35 -0500 (EST)
Received: from ckmso1.proxy.att.com (ckmso1.att.com [12.20.58.69]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20778; Mon, 7 Feb 2000 15:19:47 -0500 (EST)
Received: from njb140r1.ems.att.com ([135.65.202.58]) by ckmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id PAA22227; Mon, 7 Feb 2000 15:19:13 -0500 (EST)
Received: from njb140bh2.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id PAA22001; Mon, 7 Feb 2000 15:18:36 -0500 (EST)
Received: by njb140bh2.ems.att.com with Internet Mail Service (5.5.2448.0) id <1H1F0VWH>; Mon, 7 Feb 2000 15:19:10 -0500
Message-ID: <B13F591F20ACD311BE4300902761550F12660A@njb140po06.ems.att.com>
From: "Lind, Steven D, ALARC" <sdlind@att.com>
To: 'David Oran' <oran@cisco.com>, Keith Moore <moore@cs.utk.edu>, Randy Bush <randy@psg.com>
Cc: Bill Manning <bmanning@isi.edu>, Richard Shockey <rshockey@ix.netcom.com>, enum@ietf.org, itu+ietf@ietf.org
Subject: RE: [ITU+IETF] RE: [Enum] Re: Structure of DNS entry for ENUM
Date: Mon, 07 Feb 2000 15:19:07 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Sender: itu+ietf-admin@ietf.org
Errors-To: itu+ietf-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Joint ITU+IETF Discussion List <itu+ietf.ietf.org>
X-BeenThere: itu+ietf@ietf.org

	Perhaps because some people want to use enum for resolving telephone
numbers
	other than e.164 globally-unique numbers, such as:
		800 numbers (really names)
		700 numbers (really names)
		private numbering plans

800 and 700 numbers are E.164 numbers. Fully qualified, they would be +1 800
xxx xxxx or +1 700 xxx xxxx. Other countries have similar free phone
services with their own set of E.164 numbers.

Steve Lind
---------------------------------------------------------------
Steven D. Lind                   Tel: (973) 236-6787
AT&T                             Fax: (973) 236-6452  
180 Park Ave., Bldg. 2            e-mail: sdlind@att.com
Florham Park, NJ 07932                 
---------------------------------------------------------------


> -----Original Message-----
> From:	David Oran [SMTP:oran@cisco.com]
> Sent:	Monday, February 07, 2000 2:28 PM
> To:	Keith Moore; Randy Bush
> Cc:	Bill Manning; Richard Shockey; enum@ietf.org; itu+ietf@ietf.org
> Subject:	RE: [ITU+IETF] RE: [Enum] Re: Structure of DNS entry for
> ENUM 
> 
> Perhaps because some people want to use enum for resolving telephone
> numbers
> other than e.164 globally-unique numbers, such as:
> 	800 numbers (really names)
> 	700 numbers (really names)
> 	private numbering plans
> 
> I agree that if something is really truly a globally unique E.164 number
> there should be ony and only one root for resolving them. Unfortunately,
> you
> can't look at a string of digits and know that, unlike an IP address.
> 
> > -----Original Message-----
> > From: itu+ietf-admin@ietf.org [mailto:itu+ietf-admin@ietf.org]On Behalf
> > Of Keith Moore
> > Sent: Monday, February 07, 2000 12:43 PM
> > To: Randy Bush
> > Cc: Bill Manning; Richard Shockey; enum@ietf.org; itu+ietf@ietf.org
> > Subject: Re: [ITU+IETF] RE: [Enum] Re: Structure of DNS entry for ENUM
> >
> >
> > > > I find this hard to fathom.
> > >
> > > i am not surprised
> >
> > well, it would seem odd for IETF to insist on consistency of
> > meaning for IP numbers (modulo private address space) but not
> > care about consistency of meaning for E.164 numbers.
> >
> > seems like users' interests are best served by having a consistent
> > meaning, everywhere, for both kinds of address.
> >
> > Keith
> >
> > _______________________________________________
> > ITU+IETF mailing list
> > ITU+IETF@ietf.org
> > http://www.ietf.org/mailman/listinfo/itu+ietf
> >
> >
> 
> 
> _______________________________________________
> enum mailing list
> enum@ietf.org
> http://www.ietf.org/mailman/listinfo/enum

_______________________________________________
ITU+IETF mailing list
ITU+IETF@ietf.org
http://www.ietf.org/mailman/listinfo/itu+ietf