RE: [Enum] Potential Agenda for ENUM Adelide
Patrik Fältström <paf@swip.net> Wed, 22 March 2000 04:23 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 XAA13296 for <enum-archive@ietf.org>; Tue, 21 Mar 2000 23:23: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 XAA10024; Tue, 21 Mar 2000 23:20:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA09994 for <enum@ns.ietf.org>; Tue, 21 Mar 2000 23:20:48 -0500 (EST)
Received: from nic.cafax.se (IDENT:root@nic.cafax.se [192.71.228.17]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13181 for <enum@ietf.org>; Tue, 21 Mar 2000 23:22:55 -0500 (EST)
Received: from 192.168.110.8 (workstation1.swip.net [130.244.254.1]) by nic.cafax.se (8.9.1a/8.9.1) with ESMTP id FAA23303; Wed, 22 Mar 2000 05:22:44 +0100 (MET)
Date: Tue, 21 Mar 2000 20:13:21 -0800
From: Patrik Fältström <paf@swip.net>
To: "Rosen, Brian" <brosen@fore.com>, 'Richard Shockey' <rshockey@ix.netcom.com>, enum@ietf.org
Subject: RE: [Enum] Potential Agenda for ENUM Adelide
Message-ID: <2292963.3162658401@localhost>
In-Reply-To: <4FBEA8857476D311A03300204840E1CF208B3E@whq-msgusr-02.fore.com>
X-Mailer: Mulberry/2.0.0b12 (MacOS)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
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: 7bit
--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 (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. Patrik _______________________________________________ enum mailing list enum@ietf.org http://www.ietf.org/mailman/listinfo/enum
- [Enum] Potential Agenda for ENUM Adelide Richard Shockey
- RE: [Enum] Potential Agenda for ENUM Adelide Rosen, Brian
- RE: [Enum] Potential Agenda for ENUM Adelide Patrik Fältström
- RE: [Enum] Potential Agenda for ENUM Adelide Richard Shockey
- RE: [Enum] Potential Agenda for ENUM Adelide Patrik Fältström
- RE: [Enum] Potential Agenda for ENUM Adelide Richard Shockey