IETF Logo Mail Archive

RE: [Enum] DDDS, DNS clarification needed?

Patrik Fältström <paf@cisco.com> Thu, 21 February 2002 06:47 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 BAA01913 for <enum-archive@odin.ietf.org>; Thu, 21 Feb 2002 01:47:46 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id BAA28207 for enum-archive@odin.ietf.org; Thu, 21 Feb 2002 01:47:46 -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 BAA27912; Thu, 21 Feb 2002 01:38:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA27880 for <enum@optimus.ietf.org>; Thu, 21 Feb 2002 01:38:39 -0500 (EST)
Received: from cisco.com (nordic.cisco.com [64.103.48.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01780 for <enum@ietf.org>; Thu, 21 Feb 2002 01:38:33 -0500 (EST)
Received: from [0.0.0.0] (ssh-ams-1.cisco.com [144.254.74.55]) by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id HAA04094; Thu, 21 Feb 2002 07:37:52 +0100 (MET)
Date: Thu, 21 Feb 2002 07:19:14 +0100
From: Patrik Fältström <paf@cisco.com>
To: "Yu, James" <james.yu@neustar.biz>, 'Michael Mealling' <michael@neonym.net>, Lawrence Conroy <lwc@roke.co.uk>
cc: enum@ietf.org
Subject: RE: [Enum] DDDS, DNS clarification needed?
Message-ID: <4638544.1014275954@localhost>
In-Reply-To: <23309E398D84D5119D0F00306E075139ECEC5F@dc02.npac.com>
References: <23309E398D84D5119D0F00306E075139ECEC5F@dc02.npac.com>
X-Mailer: Mulberry/2.1.2 (Mac OS X)
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 2002-02-20 21.59 -0600 "Yu, James" <james.yu@neustar.biz> wrote:

> I believe
> that Patrik intentionally keep the "+" for the regular expression mapping
> use.

That was the intention, yes. If one reuse NAPTR for for example private
dialing plans, then one might want to have some way in the regexp to detect
a E.164 number and ENUM, and that was why I kept the '+'.

  paf


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

v2.46.0 | Report a Bug | By Email | System Status