[URN] urn-nid evaluation list
Leslie Daigle <leslie@Bunyip.Com> Tue, 24 November 1998 19:59 UTC
Received: from services.bunyip.com (services.Bunyip.Com [192.77.55.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id OAA04706 for <urn-archive@ietf.org>; Tue, 24 Nov 1998 14:59:17 -0500 (EST)
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id OAA01073 for urn-ietf-out; Tue, 24 Nov 1998 14:07:21 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA01068 for <urn-ietf@services.bunyip.com>; Tue, 24 Nov 1998 14:07:19 -0500 (EST)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id OAA04084 for urn-ietf@services; Tue, 24 Nov 1998 14:07:19 -0500 (EST)
Received: from localhost (leslie@localhost) by mocha.bunyip.com (8.8.5/8.8.5) with SMTP id OAA04081 for <urn-ietf@bunyip.com>; Tue, 24 Nov 1998 14:07:17 -0500 (EST)
Date: Tue, 24 Nov 1998 14:07:16 -0500
From: Leslie Daigle <leslie@Bunyip.Com>
To: urn-ietf@Bunyip.Com
Subject: [URN] urn-nid evaluation list
Message-ID: <Pine.SUN.3.95.981124135610.2419G-100000@mocha.bunyip.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Leslie Daigle <leslie@Bunyip.Com>
Errors-To: owner-urn-ietf@Bunyip.Com
Howdy, The URN Namespace Definition Mechanisms document outlines the role of the urn-nid@apps.ietf.org as being the forum for "clarifying the expression of the registration information and suggestions for improvements to the namespace proposal." If you'd like to participate in that review process, you can subscribe via: urn-nid-request@apps.ietf.org Thanks, Leslie. ---------------------------------------------------------------------------- If cats had bumper stickers: Leslie Daigle "I wake for food." Bunyip Information Systems -- ThinkingCat (514) 875-8611 leslie@bunyip.com ---------------------------------------------------------------------------- Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id OAA01073 for urn-ietf-out; Tue, 24 Nov 1998 14:07:21 -0500 (EST) Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA01068 for <urn-ietf@services.bunyip.com>; Tue, 24 Nov 1998 14:07:19 -0500 (EST) Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id OAA04084 for urn-ietf@services; Tue, 24 Nov 1998 14:07:19 -0500 (EST) Received: from localhost (leslie@localhost) by mocha.bunyip.com (8.8.5/8.8.5) with SMTP id OAA04081 for <urn-ietf@bunyip.com>; Tue, 24 Nov 1998 14:07:17 -0500 (EST) Date: Tue, 24 Nov 1998 14:07:16 -0500 (EST) From: Leslie Daigle <leslie@Bunyip.Com> To: urn-ietf@bunyip.com Subject: [URN] urn-nid evaluation list Message-ID: <Pine.SUN.3.95.981124135610.2419G-100000@mocha.bunyip.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-urn-ietf@Bunyip.Com Precedence: bulk Reply-To: Leslie Daigle <leslie@Bunyip.Com> Errors-To: owner-urn-ietf@Bunyip.Com Howdy, The URN Namespace Definition Mechanisms document outlines the role of the urn-nid@apps.ietf.org as being the forum for "clarifying the expression of the registration information and suggestions for improvements to the namespace proposal." If you'd like to participate in that review process, you can subscribe via: urn-nid-request@apps.ietf.org Thanks, Leslie. ---------------------------------------------------------------------------- If cats had bumper stickers: Leslie Daigle "I wake for food." Bunyip Information Systems -- ThinkingCat (514) 875-8611 leslie@bunyip.com ---------------------------------------------------------------------------- Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id KAA27390 for urn-ietf-out; Tue, 24 Nov 1998 10:49:52 -0500 (EST) Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id KAA27385 for <urn-ietf@services.bunyip.com>; Tue, 24 Nov 1998 10:49:49 -0500 (EST) Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id KAA03056 for urn-ietf@services; Tue, 24 Nov 1998 10:49:49 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id KAA03053 for <urn-ietf@bunyip.com>; Tue, 24 Nov 1998 10:49:46 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA24926; Tue, 24 Nov 1998 10:49:43 -0500 (EST) Message-Id: <199811241549.KAA24926@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: urn-ietf@bunyip.com From: Internet-Drafts@ietf.org Subject: [URN] I-D ACTION:draft-ietf-urn-net-procedures-01.txt Date: Tue, 24 Nov 1998 10:49:42 -0500 Sender: owner-urn-ietf@Bunyip.Com Precedence: bulk Reply-To: Internet-Drafts@ietf.org Errors-To: owner-urn-ietf@Bunyip.Com --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Uniform Resource Names Working Group of the IETF. Title : Assignment Procedures for the URI Resolution using DNS (RFC2168) Author(s) : M. Mealling Filename : draft-ietf-urn-net-procedures-01.txt Pages : 5 Date : 23-Nov-98 RFC2168 defines a DNS resource record and an algorithm for using DNS as a registry for retrieving URI delegation rules (sometimes called resolution hints). That document specifies that the first step in that algorithm is to append 'uri.net' to the URI scheme and retrieve the NAPTR record for that domain-name. I.e., the first step in resolving 'http://foo.com/' would be to look up a NAPTR record for the domain 'http.uri.net'. URN resolution also follows a similar procedure but uses the 'urn.net' zone as its root. This document describes the procedures for inserting a new rule into the 'uri.net' and 'urn.net' zones. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-urn-net-procedures-01.txt". A URL for the Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-urn-net-procedures-01.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nic.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-urn-net-procedures-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19981123083833.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-urn-net-procedures-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-urn-net-procedures-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19981123083833.I-D@ietf.org> --OtherAccess-- --NextPart-- Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id HAA06185 for urn-ietf-out; Mon, 23 Nov 1998 07:04:05 -0500 (EST) Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id HAA06180 for <urn-ietf@services.bunyip.com>; Mon, 23 Nov 1998 07:04:02 -0500 (EST) Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id HAA11203 for urn-ietf@services; Mon, 23 Nov 1998 07:04:03 -0500 (EST) Received: from nix.swip.net (nix.swip.net [192.71.220.2]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id HAA11200 for <urn-ietf@Bunyip.Com>; Mon, 23 Nov 1998 07:04:00 -0500 (EST) Received: from [192.168.124.31] (workstation1.swip.net [130.244.254.1]) by nix.swip.net (8.8.8/8.8.8) with ESMTP id NAA22387; Mon, 23 Nov 1998 13:03:45 +0100 (MET) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Sender: paf@nix.swip.net Message-Id: <v04102706b27ef5eac515@[192.168.124.31]> In-Reply-To: <199811230416.UAA06434@smtp2.jps.net> Date: Mon, 23 Nov 1998 13:03:53 +0100 To: "Yves Arrouye" <yves@centraal.com>, Justin Couch <couch@ccis.adisys.com.au> From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net> Subject: Re: [URN] Looking for latest BIND with NAPTR implementation Cc: urn-ietf@bunyip.com Sender: owner-urn-ietf@Bunyip.Com Precedence: bulk Reply-To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net> Errors-To: owner-urn-ietf@Bunyip.Com At 20.13 -0800 98-11-22, Yves Arrouye wrote: >They also do handle SRV RRs by the way, which >can be used in the process of discovering a resolver for URNs. You can also check the "getservicebyhostname" function which I have written. You can find it on ftp://ftp.cafax.se/pub/paf/srvlookup.tar It handles the parsing of srv records in DNS. paf Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id AAA02716 for urn-ietf-out; Mon, 23 Nov 1998 00:32:54 -0500 (EST) Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id AAA02711 for <urn-ietf@services.bunyip.com>; Mon, 23 Nov 1998 00:32:51 -0500 (EST) Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id AAA10537 for urn-ietf@services; Mon, 23 Nov 1998 00:32:51 -0500 (EST) Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id AAA10534 for <urn-ietf@Bunyip.Com>; Mon, 23 Nov 1998 00:32:48 -0500 (EST) Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id XAA12515; Sun, 22 Nov 1998 23:47:54 -0500 (EST) From: Michael Mealling <michael@bailey.dscga.com> Message-Id: <199811230447.XAA12515@bailey.dscga.com> Subject: Re: [URN] Looking for latest BIND with NAPTR implementation In-Reply-To: <199811230416.UAA06434@smtp2.jps.net> from Yves Arrouye at "Nov 22, 98 08:13:40 pm" To: yves@centraal.com Date: Sun, 22 Nov 1998 23:47:53 -0500 (EST) Cc: couch@ccis.adisys.com.au, urn-ietf@bunyip.com X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-urn-ietf@Bunyip.Com Precedence: bulk Reply-To: Michael Mealling <michael@bailey.dscga.com> Errors-To: owner-urn-ietf@Bunyip.Com Yves Arrouye said this: > Justin, > > I've developed my C URN resolution library (soon to be freely available from > Centraal Corporation) using BIND 4.9.7. I think that BIND 4.9.6 and up > handle NAPTR RRs correctly. They also do handle SRV RRs by the way, which > can be used in the process of discovering a resolver for URNs. > Beware that bind 8.1.2 (current production version) has a bug in named-xfer that causes NAPTR records to not be transfered correctly during a zone transfer. If you don't have a secondary (bad thing) or are running 4.9.6 or higher this bug does not affect you. Contact me directly if you need the patch. You can also find it in the list archives... -MM -- -------------------------------------------------------------------------------- Michael Mealling | Vote Libertarian! | www.rwhois.net/michael Sr. Research Engineer | www.ga.lp.org/gwinnett | ICQ#: 14198821 Network Solutions | www.lp.org | michaelm@netsol.com Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id XAA01651 for urn-ietf-out; Sun, 22 Nov 1998 23:13:54 -0500 (EST) Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id XAA01643 for <urn-ietf@services.bunyip.com>; Sun, 22 Nov 1998 23:13:51 -0500 (EST) Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id XAA10399 for urn-ietf@services; Sun, 22 Nov 1998 23:13:52 -0500 (EST) Received: from smtp2.jps.net (smtp2.jps.net [209.63.224.235]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id XAA10396 for <urn-ietf@bunyip.com>; Sun, 22 Nov 1998 23:13:49 -0500 (EST) Received: from [209.239.196.129] (209-239-196-129.oak.jps.net [209.239.196.129]) by smtp2.jps.net (8.9.0/8.8.5) with ESMTP id UAA06434; Sun, 22 Nov 1998 20:16:28 -0800 (PST) Message-Id: <199811230416.UAA06434@smtp2.jps.net> X-Mailer: Microsoft Outlook Express for Macintosh - 4.01 (295) Date: Sun, 22 Nov 1998 20:13:40 -0800 Subject: Re: [URN] Looking for latest BIND with NAPTR implementation From: "Yves Arrouye" <yves@centraal.com> To: Justin Couch <couch@ccis.adisys.com.au> CC: urn-ietf@bunyip.com Mime-version: 1.0 X-Priority: 3 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-urn-ietf@Bunyip.Com Precedence: bulk Reply-To: "Yves Arrouye" <yves@centraal.com> Errors-To: owner-urn-ietf@Bunyip.Com Justin, I've developed my C URN resolution library (soon to be freely available from Centraal Corporation) using BIND 4.9.7. I think that BIND 4.9.6 and up handle NAPTR RRs correctly. They also do handle SRV RRs by the way, which can be used in the process of discovering a resolver for URNs. Yves. Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id WAA01222 for urn-ietf-out; Sun, 22 Nov 1998 22:55:52 -0500 (EST) Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id WAA01217 for <urn-ietf@services.bunyip.com>; Sun, 22 Nov 1998 22:55:49 -0500 (EST) Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id WAA10358 for urn-ietf@services; Sun, 22 Nov 1998 22:55:50 -0500 (EST) Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id WAA10355 for <urn-ietf@Bunyip.Com>; Sun, 22 Nov 1998 22:55:46 -0500 (EST) Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id WAA12337; Sun, 22 Nov 1998 22:48:47 -0500 (EST) From: Michael Mealling <michael@bailey.dscga.com> Message-Id: <199811230348.WAA12337@bailey.dscga.com> Subject: Re: [URN] Looking for latest BIND with NAPTR implementation In-Reply-To: <3658BDA8.4BC4F2A0@ccis.adisys.com.au> from Justin Couch at "Nov 23, 98 09:43:04 am" To: couch@ccis.adisys.com.au Date: Sun, 22 Nov 1998 22:48:46 -0500 (EST) Cc: urn-ietf@bunyip.com X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-urn-ietf@Bunyip.Com Precedence: bulk Reply-To: Michael Mealling <michael@bailey.dscga.com> Errors-To: owner-urn-ietf@Bunyip.Com Justin Couch said this: > Excuse the newbie status to this WG, We're all newbies to implementations! ;-) > I'm starting to work on some java based URN implementations for client > side resolver work. I'm trying to determine/locate what is the > recommended version of BIND with the latest implementation of the > NAPTR/SRV schemes. It is prefered that it be capable of generating the > additional info fields for testing purposes (preferably running on Linux > as I can't get access to our production machines). Also, compliance with > the two drafts issued last Friday would be great. All versions of BIND since 4.9.6 support NAPTR on the client and server side. The earlier versions of BIND 8 had a problem with zone transfers that was caused by a bug in named-xfer. The current version of BIND 8 has fixed that problem. The two knew drafts don't really change anything with respect to NAPTR and URN resolution. The only minor change is the step for doing general URI resolution. I.e. unless I screwed something up, the new papers are backward compatible. > I've searched through all this year's archives but cannot find any > reference to publically available implementations (although plenty of > discussions about NAPTRs themselves!). I have released a toolkit (apache style license) that contains an attempt at an Internet Explorer plugin and the client side libraries that were put together by Ron Daniel at LANL. We will be following these up with a Java client library. We are also working on NAPTR/SRV support in Mozilla (the ngLayout switch is making that one take longer). > I'm doing this work as part of the VRML efforts (you've probably seen > the the posts from Aaron Walsh) and also for larger issues. I've already > implemented a simple file based URN resolver but would like to start > work on the DNS based solution. As part of this work, there will be a > generic DNS resolver classes and the URN implementation making use of > it. Any pointers to starter code (searched all the usual places like > Gamelan, JARS etc) that would save me coding (and can be freely > redistributed) would also be greatfully accepted. Another really useful > item would be an implementation of the regexp rewriting rules in pure > java (no outsourcing to PERL!). There are several Java regexp implmementations out there. I can dig them up if needed. The toolkit above uses an Apache style license so any changes to that can be incorporated into anything you need. We are desperately looking for help in implementations (I'm _not_ a win32 programmer by any stretch of the imagination). > In some private conversations with Aaron and some list members, there is > quite some interest in a pure DNS resolver class independent of the URN > handling. Expected delivery would be within 2-3 weeks assuming > everything goes smoothly on the server end for the resolver and the URN > stuff sometime just after Christmas. Ah. You need a Java class for NAPTR and SRV? We have both of those. I'll find the code and put that into the toolkit as well. If you don't hear from me by Monday afternoon be sure and bug me about the Java classes. The location of the current toolkit is: ftp://research.netsol.com/pub/urn/plugin/ -MM -- -------------------------------------------------------------------------------- Michael Mealling | Vote Libertarian! | www.rwhois.net/michael Sr. Research Engineer | www.ga.lp.org/gwinnett | ICQ#: 14198821 Network Solutions | www.lp.org | michaelm@netsol.com Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id VAA00546 for urn-ietf-out; Sun, 22 Nov 1998 21:40:23 -0500 (EST) Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id VAA00541 for <urn-ietf@services.bunyip.com>; Sun, 22 Nov 1998 21:40:21 -0500 (EST) Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id VAA10207 for urn-ietf@services; Sun, 22 Nov 1998 21:40:21 -0500 (EST) Received: from fire.adisys.com.au ([203.20.100.67]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id VAA10204 for <urn-ietf@bunyip.com>; Sun, 22 Nov 1998 21:40:16 -0500 (EST) Received: (from nobody@localhost) by fire.adisys.com.au (8.8.8/8.7.3) id KAA05731 for <urn-ietf@bunyip.com>; Mon, 23 Nov 1998 10:39:30 +0800 (WST) X-Authentication-Warning: fire.adisys.com.au: nobody set sender to <couch@ccis.adisys.com.au> using -f Received: from hawk(193.10.80.9) by fire via smap (V2.0) id xma005719; Mon, 23 Nov 98 10:39:16 +0800 Received: from ccis.adisys.com.au (beardie [193.10.80.73]) by ccis.adisys.com.au (8.8.8/8.8.8) with ESMTP id KAA05717 for <urn-ietf@bunyip.com>; Mon, 23 Nov 1998 10:41:21 +0800 (WST) Message-ID: <3658BDA8.4BC4F2A0@ccis.adisys.com.au> Date: Mon, 23 Nov 1998 09:43:04 +0800 From: Justin Couch <couch@ccis.adisys.com.au> Organization: ADI Ltd Systems Group X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: IETF URN WG <urn-ietf@bunyip.com> Subject: [URN] Looking for latest BIND with NAPTR implementation Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-urn-ietf@Bunyip.Com Precedence: bulk Reply-To: Justin Couch <couch@ccis.adisys.com.au> Errors-To: owner-urn-ietf@Bunyip.Com Excuse the newbie status to this WG, I'm starting to work on some java based URN implementations for client side resolver work. I'm trying to determine/locate what is the recommended version of BIND with the latest implementation of the NAPTR/SRV schemes. It is prefered that it be capable of generating the additional info fields for testing purposes (preferably running on Linux as I can't get access to our production machines). Also, compliance with the two drafts issued last Friday would be great. I've searched through all this year's archives but cannot find any reference to publically available implementations (although plenty of discussions about NAPTRs themselves!). I'm doing this work as part of the VRML efforts (you've probably seen the the posts from Aaron Walsh) and also for larger issues. I've already implemented a simple file based URN resolver but would like to start work on the DNS based solution. As part of this work, there will be a generic DNS resolver classes and the URN implementation making use of it. Any pointers to starter code (searched all the usual places like Gamelan, JARS etc) that would save me coding (and can be freely redistributed) would also be greatfully accepted. Another really useful item would be an implementation of the regexp rewriting rules in pure java (no outsourcing to PERL!). In some private conversations with Aaron and some list members, there is quite some interest in a pure DNS resolver class independent of the URN handling. Expected delivery would be within 2-3 weeks assuming everything goes smoothly on the server end for the resolver and the URN stuff sometime just after Christmas. -- Justin Couch Senior Software Engineer VRML-Java Author ADI Ltd, Systems Group. justin@vlc.com.au http://www.vlc.com.au/~justin/ ------------------------------------------------------------------- "Look through the lens, and the light breaks down into many lights. Turn it or move it, and a new set of arrangements appears... is it a single light or many lights, lights that one must know how to distinguish, recognise and appreciate? Is it one light with many frames or one frame for many lights?" -Subcomandante Marcos ------------------------------------------------------------------- Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id LAA28115 for urn-ietf-out; Thu, 19 Nov 1998 11:34:19 -0500 (EST) Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA28110 for <urn-ietf@services.bunyip.com>; Thu, 19 Nov 1998 11:34:11 -0500 (EST) Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id LAA22311 for urn-ietf@services; Thu, 19 Nov 1998 11:34:09 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA22308 for <urn-ietf@bunyip.com>; Thu, 19 Nov 1998 11:34:05 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA13275; Thu, 19 Nov 1998 11:34:01 -0500 (EST) Message-Id: <199811191634.LAA13275@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: urn-ietf@bunyip.com From: Internet-Drafts@ietf.org Subject: [URN] I-D ACTION:draft-ietf-urn-dns-rds-00.txt Date: Thu, 19 Nov 1998 11:34:00 -0500 Sender: owner-urn-ietf@Bunyip.Com Precedence: bulk Reply-To: Internet-Drafts@ietf.org Errors-To: owner-urn-ietf@Bunyip.Com --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Uniform Resource Names Working Group of the IETF. Title : Resolution of Uniform Resource Identifiers using the Domain Name System Author(s) : M. Mealling, R. Daniel Filename : draft-ietf-urn-dns-rds-00.txt Pages : 15 Date : 18-Nov-98 The architectural principles laid out in RFC2276 [15] defines the concept of a 'resolver discovery service'. This document describes an immediately-deployable RDS. It is implemented by a new DNS Resource Record, NAPTR (Naming Authority PoinTeR) [16], that provides a method for encoding incrementally discovered rules within DNS. By using these incrementally discovered rules to re-map parts of a URI, we can change the host that is contacted to resolve a URI. This will allow a more graceful handling of URLs over long time periods, and forms the foundation for a new proposal for Uniform Resource Names. In addition to locating resolvers, the NAPTR provides for other naming systems to be grandfathered into the URN world, provides independence between the name assignment system and the resolution protocol system, and allows multiple services (Identifier to Location, Identifier to Description, Identifier to Resource, ...) to be offered. In conjunction with the SRV RR, the NAPTR record allows those services to be replicated for the purposes of fault tolerance and load balancing. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-urn-dns-rds-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-urn-dns-rds-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nic.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-urn-dns-rds-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19981118110228.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-urn-dns-rds-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-urn-dns-rds-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19981118110228.I-D@ietf.org> --OtherAccess-- --NextPart-- Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id LAA27953 for urn-ietf-out; Thu, 19 Nov 1998 11:17:37 -0500 (EST) Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA27948 for <urn-ietf@services.bunyip.com>; Thu, 19 Nov 1998 11:17:33 -0500 (EST) Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id LAA22266 for urn-ietf@services; Thu, 19 Nov 1998 11:17:33 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id LAA22263 for <urn-ietf@bunyip.com>; Thu, 19 Nov 1998 11:17:30 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA12262; Thu, 19 Nov 1998 11:17:27 -0500 (EST) Message-Id: <199811191617.LAA12262@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: urn-ietf@bunyip.com From: Internet-Drafts@ietf.org Subject: [URN] I-D ACTION:draft-ietf-urn-naptr-rr-00.txt Date: Thu, 19 Nov 1998 11:17:26 -0500 Sender: owner-urn-ietf@Bunyip.Com Precedence: bulk Reply-To: Internet-Drafts@ietf.org Errors-To: owner-urn-ietf@Bunyip.Com --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Uniform Resource Names Working Group of the IETF. Title : The Naming Authority Pointer (NAPTR) DNS Resource Record Author(s) : M. Mealling, R. Daniel Filename : draft-ietf-urn-naptr-rr-00.txt Pages : 12 Date : 18-Nov-98 This document describes a DNS Resource Record which specifies a rewrite rule that, when applied to an existing string will produce a new domain. Reasons for rewriting a domain vary from URN Resource Discovery Systems to moving out of date services to new domains. This document updates the portions of RFC2168 specifically dealing with the definition of the NAPTR record. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-urn-naptr-rr-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-urn-naptr-rr-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nic.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-urn-naptr-rr-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19981118111108.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-urn-naptr-rr-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-urn-naptr-rr-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19981118111108.I-D@ietf.org> --OtherAccess-- --NextPart-- Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id IAA14989 for urn-ietf-out; Wed, 11 Nov 1998 08:54:46 -0500 (EST) Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id IAA14979 for <urn-ietf@services.bunyip.com>; Wed, 11 Nov 1998 08:54:41 -0500 (EST) Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id IAA11613 for urn-ietf@services; Wed, 11 Nov 1998 08:54:54 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id IAA11610 for <urn-ietf@bunyip.com>; Wed, 11 Nov 1998 08:54:52 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id IAA28767; Wed, 11 Nov 1998 08:54:15 -0500 (EST) Message-Id: <199811111354.IAA28767@ietf.org> To: IETF-Announce: ; Cc: RFC Editor <rfc-editor@isi.edu> Cc: Internet Architecture Board <iab@isi.edu> Cc: urn-ietf@bunyip.com From: The IESG <iesg-secretary@ietf.org> Subject: [URN] Document Action: URI Resolution Services Necessary for URN Resolution to Experimental Date: Wed, 11 Nov 1998 08:54:14 -0500 Sender: owner-urn-ietf@Bunyip.Com Precedence: bulk Reply-To: The IESG <iesg-secretary@ietf.org> Errors-To: owner-urn-ietf@Bunyip.Com The IESG has approved the Internet-Draft URI Resolution Services Necessary for URN Resolution <draft-ietf-urn-resolution-services-07.txt> as a Experimental Protocol. This document is the product of the Uniform Resource Names Working Group. The IESG contact persons are Keith Moore and Patrik Faltstrom. Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id HAA18874 for urn-ietf-out; Tue, 10 Nov 1998 07:45:15 -0500 (EST) Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id HAA18866 for <urn-ietf@services.bunyip.com>; Tue, 10 Nov 1998 07:45:12 -0500 (EST) Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id HAA06722 for urn-ietf@services; Tue, 10 Nov 1998 07:45:25 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id HAA06719 for <urn-ietf@bunyip.com>; Tue, 10 Nov 1998 07:45:23 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA22185; Tue, 10 Nov 1998 07:45:18 -0500 (EST) Message-Id: <199811101245.HAA22185@ietf.org> To: IETF-Announce: ; Cc: urn-ietf@bunyip.com From: The IESG <iesg-secretary@ietf.org> Subject: [URN] Last Call: URN Namespace Definition Mechanisms to BCP Date: Tue, 10 Nov 1998 07:45:18 -0500 Sender: owner-urn-ietf@Bunyip.Com Precedence: bulk Reply-To: The IESG <iesg-secretary@ietf.org> Errors-To: owner-urn-ietf@Bunyip.Com The IESG has received a request from the Uniform Resource Names Working Group to consider URN Namespace Definition Mechanisms <draft-ietf-urn-nid-req-07.txt> as a BCP. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by November 24, 1998. Files can be obtained via ftp://ftp.ietf.org/internet-drafts/draft-ietf-urn-nid-req-07.txt Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id JAA23385 for urn-ietf-out; Sat, 7 Nov 1998 09:31:14 -0500 (EST) Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id JAA23380 for <urn-ietf@services.bunyip.com>; Sat, 7 Nov 1998 09:31:06 -0500 (EST) Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id JAA14190 for urn-ietf@services; Sat, 7 Nov 1998 09:31:16 -0500 (EST) Received: from itek.norut.no (emma.itek.norut.no [193.156.106.30]) by mocha.bunyip.com (8.8.5/8.8.5) with SMTP id JAA14185 for <urn-ietf@bunyip.com>; Sat, 7 Nov 1998 09:31:12 -0500 (EST) From: viagra2000@usa.net Received: from itek.norut.no (embert) by itek.norut.no with SMTP id AA14725 (5.65c8+/IDA-1.4.4 for <urn-ietf@bunyip.com>); Sat, 7 Nov 1998 15:31:06 +0100 Received: from 193.174.4.1 by itek.norut.no (8.8.8) id PAA38144; Sat, 7 Nov 1998 15:29:27 +0100 (MET) Date: Sat, 7 Nov 1998 15:29:27 +0100 (MET) Message-Id: <199811071429.PAA38144@itek.norut.no> To: <urn-ietf@bunyip.com> Subject: [URN] Free Shipping included Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-Charset: LATIN1 X-Char-Esc: 29 Sender: owner-urn-ietf@Bunyip.Com Precedence: bulk Reply-To: viagra2000@usa.net Errors-To: owner-urn-ietf@Bunyip.Com Sender: Viagra.4.you Email: viagra2000@usa.net Visit http://surf.to/forsale for full details. This message is sent in compliance of the new e-mail bill: SECTION 301, Paragraph (a)(2)(C) of s. 1618 To be removed from our mailing list, simply reply with "REMOVE" in the subject.
- [URN] urn-nid evaluation list Leslie Daigle