Re: [Enum] draft-ietf-enum-e164-gstn-np-00.txt

"A.M.Rutkowski" <amr@netmagic.com> Sat, 25 November 2000 21:59 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 SMTP id QAA22899 for <enum-archive@odin.ietf.org>; Sat, 25 Nov 2000 16:59:13 -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 QAA18597; Sat, 25 Nov 2000 16:56:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA18562 for <enum@ns.ietf.org>; Sat, 25 Nov 2000 16:56:27 -0500 (EST)
Received: from exchange.chaos.com (exchange.chaos.com [206.5.17.8]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22191 for <enum@ietf.org>; Sat, 25 Nov 2000 16:56:22 -0500 (EST)
Received: from [206.5.17.17] by exchange.netmagic.com (NTMail 5.06.0016/NT2627.00.5ef58ba0) with ESMTP id pkcjaaaa for enum@ietf.org; Sat, 25 Nov 2000 16:56:24 -0500
Message-Id: <5.0.1.3.2.20001125162801.00ae3cd0@mail.netmagic.com>
X-Sender: amr@mail.netmagic.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1.3 (Beta)
Date: Sat, 25 Nov 2000 16:56:23 -0500
To: Richard Shockey <rshockey@ix.netcom.com>, Dave Crocker <dhc@dcrocker.net>
From: "A.M.Rutkowski" <amr@netmagic.com>
Subject: Re: [Enum] draft-ietf-enum-e164-gstn-np-00.txt
Cc: enum@ietf.org
In-Reply-To: <5.0.0.25.2.20001125160322.02cf79e0@127.0.0.1>
References: <5.0.1.3.2.20001125113856.00afff08@mail.netmagic.com> <5.0.1.4.2.20001125081342.032e5d20@joy.songbird.com> <5.0.1.3.2.20001125092648.00a764e0@mail.netmagic.com> <5.0.0.25.2.20001113203057.02868560@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: enum-admin@ietf.org
Errors-To: enum-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Enum Discussion List <enum.ietf.org>
X-BeenThere: enum@ietf.org

Hi Richard,

>The purpose of the e164.arpa namespace is to be "athoritive" as opposed to 
>any other domain. There is certainly nothing stopping anyone from putting 
>number strings in FOO.NET or whatever for the purpose of defining some 
>private service or services.  Consequently the administrative model for 
>determining correct holder of a E.164 number within e164.arpa must by 
>definition follow the appropriate national numbering plan. That is what 
>RFC2916 states and that is what the ITU has agreed to as well.

Thanks for the clarification.

Where in RFC2916 is there a specification that
"the e164.arpa namespace is to be 'authoritive'
as opposed to any other domain?"

What ITU-T Study Group 2 agreed was that this subject
was a national matter.  Is there anything to prevent
each of these national authorities from establishing
a neutral authentication interface and maintaining a
level playing field among competitive providers?

Do you expect the FCC to begin a proceeding concerning
their portion of 1.164.arpa.?   Could they decide they
don't want a regulated zone or that this is anticompetitive,
and leave it to e164.com and others via an authoritative
authentication mechanism?

--amr



_______________________________________________
enum mailing list
enum@ietf.org
http://www1.ietf.org/mailman/listinfo/enum