IETF Logo Mail Archive

RE: [Enum] Potential Agenda for ENUM Adelide

Richard Shockey <rshockey@ix.netcom.com> Wed, 22 March 2000 06:15 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 BAA01020 for <enum-archive@ietf.org>; Wed, 22 Mar 2000 01:15:37 -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 BAA15646; Wed, 22 Mar 2000 01:12:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA15616 for <enum@ns.ietf.org>; Wed, 22 Mar 2000 01:12:05 -0500 (EST)
Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00280 for <enum@ietf.org>; Wed, 22 Mar 2000 01:14:12 -0500 (EST)
Received: from laptop.ix.netcom.com ([209.138.6.165]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id BAA17838; Wed, 22 Mar 2000 01:14:03 -0500 (EST)
Message-Id: <4.3.2.20000321235323.00b79670@127.0.0.1>
X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Wed, 22 Mar 2000 00:04:00 -0600
To: Patrik Fältström <paf@swip.net>, "Rosen, Brian" <brosen@fore.com>, enum@ietf.org
From: Richard Shockey <rshockey@ix.netcom.com>
Subject: RE: [Enum] Potential Agenda for ENUM Adelide
In-Reply-To: <2292963.3162658401@localhost>
References: <4FBEA8857476D311A03300204840E1CF208B3E@whq-msgusr-02.fore.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id BAA15617
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
Content-Transfer-Encoding: 8bit

At 08:13 PM 3/21/2000 -0800, Patrik Fältström wrote:
>--On 2000-03-21 13.43 -0500, "Rosen, Brian" <brosen@fore.com> wrote:
>
> > I'm not sure we can get through draft-faltstrom-e164-05.txt in
> > 10 minutes.
>
>I am sorry if the text in the draft is confusing. The text talk about two
>things, and the latter probably should be deleted, as it is confusing
>people:
>
>(1) How to do a mechanical transformation of one E.164 number into a
>domainname which can be stored in DNS

Oh yes.. I get it now.  Patrik you are on to something fundamentally 
correct here.

There will have to be multiple RFC here but the core is TN  to >domain of 
authority as Greg outlines.

At least hint to references to service provisioning.

Second level is service provisioning which may or may not require 3rd level 
resolution to LDAP authority.

Am I making sense here?


>(2) Give examples of existing services defined for use given arbitrary DNS
>names (including the ones defined under (1) above)
>
>It is only (1) above which is important. The second thing is that when
>having E.164 numbers as DNS names, that they try to guess/experiment/try
>what things can be done given _existing_ operations and data that can be
>stored.
>
>It should not be in a draft only talking about the E.164<->DNS
>transformation though, and I am happy to remove that text. It is already
>described in other RFCs and doesn't have to / should not be repeated.


Examples in the primary ENUM resolution document may be useful but not 
binding on others wishing to demonstrate service provision.  Am I making 
sense here?


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey
Shockey Consulting LLC
8045 Big Bend Blvd. Suite 110
St. Louis, MO 63119
Voice 314.918.9020
eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
INTERNET Mail & IFAX : rshockey@ix.netcom.com
GSTN Fax 314.918.9015
MediaGate iPost VoiceMail and Fax 800.260.4464
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


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

v2.23.0 | Report a Bug | By Email