Re: [Enum] NAPTR Record Replacement Field
Richard Shockey <rshockey@ix.netcom.com> Fri, 09 June 2000 16:56 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 MAA15125 for <enum-archive@odin.ietf.org>; Fri, 9 Jun 2000 12:56:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11741; Fri, 9 Jun 2000 12:56:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11710 for <enum@ns.ietf.org>; Fri, 9 Jun 2000 12:55:59 -0400 (EDT)
Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15100 for <enum@ietf.org>; Fri, 9 Jun 2000 12:55:59 -0400 (EDT)
Received: from computer.ix.netcom.com ([209.138.179.12]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id MAA08084; Fri, 9 Jun 2000 12:55:46 -0400 (EDT)
Message-Id: <4.3.1.2.20000609115220.00c9a200@127.0.0.1>
X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 09 Jun 2000 11:56:50 -0500
To: Hong Liu <lhong@research.telcordia.com>, paf@swip.net, enum@ietf.org
From: Richard Shockey <rshockey@ix.netcom.com>
Subject: Re: [Enum] NAPTR Record Replacement Field
Cc: lhong@research.telcordia.com
In-Reply-To: <39411759.CB920970@research.telcordia.com>
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
At 12:12 PM 6/9/2000 -0400, Hong Liu wrote: >Hi, Patrik, > >I have two questions regarding your ENUM draft. > >In "draft-ietf-enum-e164-dns-00.txt", you use the replacement field of >the NAPTR RR to store the the URLs for the answer of an E.164 query, >such as a SIP URL "sip:paf@swip.net". When I looked through the NAPTR RR >documents, both RFC2168 and "draft-ietf-urn-naptr-rr-03.txt" say that >the replacement field MUST be a fully qualified domain name. Maybe I am >missing something. Could you explain the difference here? > >The second question is regarding the service field "N2R". According to >RFC2168, "N2R" is a service that maps an URN to an instance of resource. >Since an ENUM query returns a set of URLs, will that be "N2L" instead? Thanks for your message...one thing I think we should make clear is that ENUM is "application agnostic". Namely how various applications use ENUM is essentially up to them. We should not attempt to define how SIP or VPIM or other applications use ENUM. The examples in Patrik's document are _examples_. The use of NAPTR is certainly one method..but we should start to make clear that other work groups need to begin thinking about specific ID's of how to implement ENUM. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Please Note New Contact Information: Richard Shockey Shockey Consulting LLC 5237 Sutherland St. Louis, MO 63109 Voice 314.503.0640 eFAX Fax to EMail 815.333.1237 (Preferred for Fax) INTERNET Mail & IFAX : rshockey@ix.netcom.com <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org http://www1.ietf.org/mailman/listinfo/enum
- [Enum] NAPTR Record Replacement Field Hong Liu
- Re: [Enum] NAPTR Record Replacement Field Richard Shockey
- Re: [Enum] NAPTR Record Replacement Field Patrik Fältström
- [Enum] Re: NAPTR Record Replacement Field Patrik Fältström