From owner-urn-ietf@LISTS.NETSOL.COM Mon Jul 2 10:04:02 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA14518 for ; Mon, 2 Jul 2001 10:04:01 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id JAA12857; Mon, 2 Jul 2001 09:56:07 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 6575 for URN-IETF@LISTS.NETSOL.COM; Mon, 2 Jul 2001 09:53:35 -0400 Received: from urz07.urz.uni-bamberg.de (urz07.urz.uni-bamberg.de [141.13.240.7]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id JAA12845 for ; Mon, 2 Jul 2001 09:53:33 -0400 (EDT) Received: from urz01.urz.uni-bamberg.de (urz01.urz.uni-bamberg.de [141.13.240.3]) by urz07.urz.uni-bamberg.de (2.5 Build 2639 (Berkeley 8.8.6)/8.8.4) with ESMTP id PAA00817 for ; Mon, 02 Jul 2001 15:47:44 +0200 Received: from URZ01/SpoolDir by urz01.urz.uni-bamberg.de (Mercury 1.47); 2 Jul 01 15:47:45 GMT+0200 Received: from SpoolDir by URZ01 (Mercury 1.47); 2 Jul 01 15:47:27 GMT+0200 Received: from ppp.uni-bamberg.de (213.7.41.212) by urz01.urz.uni-bamberg.de (Mercury 1.47) with ESMTP; 2 Jul 01 15:47:24 GMT+0200 X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: de,en MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------DE1706BF8BDC607CBA2D5CF4" Approved-By: Dieter =?iso-8859-1?Q?K=F6hler?= Message-ID: <3B407B10.E66D2829@ppp.uni-bamberg.de> Date: Mon, 2 Jul 2001 15:45:52 +0200 Reply-To: Dieter =?iso-8859-1?Q?K=F6hler?= From: Dieter =?iso-8859-1?Q?K=F6hler?= Subject: URN Namespace for Structured Object Designators To: URN-IETF@LISTS.NETSOL.COM This is a multi-part message in MIME format. --------------DE1706BF8BDC607CBA2D5CF4 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I developed and attached to this posting a proposal of a formal URN names= pace for what I call "Structured Object Designators". Because of its global = scope I wonder, (i) whether it is a candidate for the standards track and (ii) wh= ether it is an appropriate candidate for an URN namespace at all or should inst= ead be specified as a new type of an URI. Any advice and comments on this proposal are welcome! Dieter K=F6hler, M.A. Philosophy Chair II Staff University of Bamberg (Germany) --------------DE1706BF8BDC607CBA2D5CF4 Content-Type: text/plain; charset=us-ascii; name="sod.txt" Content-Disposition: inline; filename="sod.txt" Content-Transfer-Encoding: 7bit XXXXXXXXXXXXX Dieter Koehler Request for Comments: YYYY University of Bamberg Category: Standards Track July 2001 URN Namespace for Structured Object Designators (SOD) 1.0 Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This document describes an URN (Uniform Resource Name) namespace for structured object designators. A structured object designator is ... 1. Introduction Structured object designators are designed for dynamic linking of metadata about structured objects in an open hypertext system. These objects may or may not be identifiable by a network URL. Examples for objects which are not identifiable by a network URL are physical or abstract objects such as "London" or "The works of Plato". However, such objects can be addressed in electronic hypertext systems by a digital alias. This document defines the framework for hierarchical structured reference systems for such objects, their parts, and different versions thereof. For example: "London in the year 1776", "London - East End", "The beginning of Plato's Symposion", "The additions of hand two to manuscript W of Plato's Symposion". If a reference system is defined according to this framework, the syntactical form of a reference allows an user agent to search for related metadata not only based on the exact reference provided, but also on proximity with regard to the reference system. For example: A search for metadata about "London in the year 1776" might also reveal proximity metadata about "England in the year 1776" or "London in the 1770s", or by using a widened scope: "Europe in the 18th century". XXX Question: Is a SOD an appropriate candidate for an URN namespace at all, or should it better be specified as a new type of an URI? XXX 2. Namespace ID "sod" requested. 3. Registration Information Registration Version Number: 1.0 Registration Date: yyyy-mm-dd 4. Declared registrant of the namespace: Dieter Koehler service@philo.de Mittlerer Kaulberg 22 D-96049 Bamberg Germany 5. Syntax The following syntax definitions are given in Augmented Backus-Naur Form (ABNF) according to [RFC2234]. The URN syntax as described in [RFC2141] defines an URN as URN = "urn:" NID ":" NSS where is the Namespace Identifier, and is the Namespace Specific String. URNs in the SOD namespace can be identified by the following Namespace Identifier: NID = "sod" All Namespace Specific Strings in the SOD namespace have the following syntax: NSS = versionNum ":" OSS versionNum = 1*( ALPHA / DIGIT / "_" / "." / "-" ) OSS = authorityId ":" dateId ":" reference authorityId = 1*( ALPHA / DIGIT / "." / "-" ) dateId = 8 ( DIGIT ) reference = div *( ":" div) div = divName *1( "*" *1(divVersion) ) ; divName = 1*divChars ; XXX limit the number of divChars ? XXX divVersion = 1*divChars ; XXX limit the number of divChars ? XXX divChars = ALPHA / DIGIT / escape / other escape = "%" HEXDIG HEXDIG other = "(" / ")" / "+" / "," / "-" / "." / "=" / "@" / ";" / "$" / "_" / "!" / "'" The indicates conformance of the Object Specific String () to the labeled SOD namespace specification version. The version number "1.0" should be used to indicate conformance to this version of this SOD namespace specification; the value "1.0" must not be used if the URN does not conform to this version of this specification. It is intended to give later versions of this specification numbers other than "1.0", but this intent does not indicate a commitment to produce any future versions of SOD, nor if any are produced, to use any particular numbering scheme. Since future versions are not ruled out, this construct is provided as a means to allow the possibility of automatic version recognition, should it become necessary. Processors may signal an error if they receive URNs labeled with versions they do not support. The must be an Internet domain name, and must be owned by the organization creating the SOD reference system and allocating the URN to it, at the date identified by the DateId. is a date in [ISO8601] Basic Format (CCYYMMDD), and must correspond to a date at which the organization allocating the URN owned the domain name specified in the . The "00000000" indicates an experimental SOD URN. No provision is made for avoiding collision of experimental SOD URNs; they are intended for use within internal or limited experimental contexts. signifies a certain reference according to a reference system defined by the authority with owned the domain name specified in the . The used reference system is uniquely identified by the combination of and . 6. Basic Reference System Structure A reference consists of a sequence of division statements separated by colons (":"). The allowed values for these divisions form a reference system. These divisions represent nested structure levels beginning with the most general and leading to the most specific. In other words: The possible divisions of a reference system form one or more nested trees. Each division consists of a mandatory division name and an optional division version indicator separated by asterisk ("*"). If no division version indicator is given, the division name together with its parent divisions specify a certain object. If a division version indicator is given, it indicates a certain version of the object specified by the division name and its parent divisions. If only the asterisk, but no division version indicator is given, it refers to each of the individual versions of the object specified by the division name and its parent divisions, but not to the object as a whole. Division versions are local. Literal equivalence between division versions indicates equivalent versions of an object only under the same parent division. Equivalent division versions occurring on different division levels do not indicate the same global version. Resource system specifications may introduce additional rules to define equivalence between literally different references. The literal values of references indicate no specific order. Resource system specifications may introduce additional rules for ordering references. More than one reference system for the same objects may be defined. However, it is out of the scope of this documentation to define a mechanism to identify references based on different reference systems designating them same designat. 7. Examples For the following examples it is assumed that a fictitious authority owns the domain at <20010101> and is declaring under this authorityId and dateId a simple sod namespace for bibliographic reference of the form "author:book:chapter:paragraph". (i) Thus urn:sod:1.0:x-test.org:20010101:Adams:My%20Life:42:11 is to be read as pointing to chapter 42, paragraph 11 of the book entitled "My Life" from an author named "Adams". If there exist two editions of this book, both could for example be distinguished by different division versions "A" and "B": urn:sod:1.0:x-test.org:20010101:Adams:My%20Life*A:42:11 urn:sod:1.0:x-test.org:20010101:Adams:My%20Life*B:42:11 (ii) Note that these URNs do not necessarily mean the same as: urn:sod:1.0:x-test.org:20010101:Adams:My%20Life:42:11*A urn:sod:1.0:x-test.org:20010101:Adams:My%20Life:42:11*B This document makes no assumptions about the identity of literally identical division versions appearing on different division levels. However, authorities specifying a reference system are free to do so. (iii) Varying the above example the URN urn:sod:1.0:x-test.org:20010101:Adams:My%20Life is referring to all editions of Adams' book "My Life", while urn:sod:1.0:x-test.org:20010101:Adams:My%20Life*A is only referring to edition "A". (iv) The sod namespace also provides means to distinguish between e.g. a reference to the author "Adams" from a reference to all of his works. To refer to the author "Adams" the URN urn:sod:1.0:x-test.org:20010101:Adams can be used, while urn:sod:1.0:x-test.org:20010101:Adams: refers to all of his books (individually). However, it is up to the authority specifying a reference system to exactly define the meaning of the first of these two references, and so she might choose to treat it as a shortcut for the second. 8. Identifier uniqueness considerations The combination of AuthorityId and DateId serves to uniquely identify the organization that is allocating the URN. That organization is responsible for ensuring the uniqueness of the designator. 9. Identifier persistence considerations A SOD URN may only be allocated by an organization that owns an Internet domain name. The URN identifies a date on which the organization owned that domain name. The combination of date and domain name will serve to uniquely identify that organization for all time. 10. Process of identifier assignment The organization identified by the AuthorityId/DateId combination is responsible for allocating a designator that is unique among all those that it allocates with that DateId. 11. Process of identifier resolution SOD providers are responsible for clearly specifying the designat of the designators, they define. Since SOD URNs are primarily designed to identify abstract or physical objects SOD providers are responsible for the provision of a URN resolution service, if any, only if there exists a canonical network resource of the designat they have assigned with a SOD URN. 12. Rules for Lexical Equivalence Two SOD URNs are lexically equivalent if they are octet-by-octet equal after the following preprocessing: 1. normalize the case of the leading "urn:sod:" token 2. normalize the case of the versionNum 3. normalize the case of the AuthorityId 4. normalizing the case of any %-escaping Note that %-escaping MUST NOT be removed. Some SOD providers may define additional lexical equivalencies, such as case-insensitivity of the (or parts thereof). Additional lexical equivalencies MUST be clearly documented, MUST always have the effect of eliminating some of the false negatives obtained by the procedure above, and MUST NEVER say that two URNs are not equivalent if the procedure above says they are equivalent. 13. Dynamic linking of documents containing SOD URNs Defining rules for dynamic linking of documents containing SOD URNs is out of the scope of this document. 14. Conformance with URN Syntax No special considerations beyond the syntax herein described. 15. Validation mechanism Organizations that allocate SOD URNs are responsible for the provision of a URN validation service, if any, for URNs they have assigned with a valid AuthorityId/DateId combination. 16. Scope Global 17. Security considerations This document proposes means of encoding structured object designators within the URN framework. This document does not discuss resolution; thus questions of secure or authenticated resolution mechanisms are out of scope. It does not address means of validating the integrity or authenticating the source or provenance of URNs that contain structured object designators. 18. Acknowledgments ... 19. References [ISO8601] XXX [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. [RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997. --------------DE1706BF8BDC607CBA2D5CF4-- From owner-urn-ietf@LISTS.NETSOL.COM Mon Jul 2 12:37:14 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA19371 for ; Mon, 2 Jul 2001 12:37:11 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id MAA13724; Mon, 2 Jul 2001 12:31:32 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 6678 for URN-IETF@LISTS.NETSOL.COM; Mon, 2 Jul 2001 12:29:16 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id MAA13678 for ; Mon, 2 Jul 2001 12:15:08 -0400 (EDT) Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id MAA26081; Mon, 2 Jul 2001 12:05:23 -0400 (EDT) References: <3B407B10.E66D2829@ppp.uni-bamberg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 User-Agent: Mutt/1.1.2i Message-ID: <20010702120522.R13798@bailey.dscga.com> Date: Mon, 2 Jul 2001 12:05:22 -0400 Reply-To: Michael Mealling From: Michael Mealling Subject: Re: URN Namespace for Structured Object Designators To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <3B407B10.E66D2829@ppp.uni-bamberg.de>; from dieter.koehler@PPP.UNI-BAMBERG.DE on Mon, Jul 02, 2001 at 03:45:52PM +0200 X-MIME-Autoconverted: from 8bit to quoted-printable by lists.netsol.com id MAA13724 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA19371 On Mon, Jul 02, 2001 at 03:45:52PM +0200, Dieter Köhler wrote: > I developed and attached to this posting a proposal of a formal URN namespace > for what I call "Structured Object Designators". Because of its global scope I > wonder, (i) whether it is a candidate for the standards track It looks general enough to be applicable to the standards track.... > and (ii) whether it is an appropriate candidate for an URN namespace at all > or should instead be specified as a new type of an URI. At first glance it looks to be very much appropriate as a URN. It has many of the features that several example URN namespaces had. The timestamped domain-name is a recurring theme and the psuedo hierarchy. The only real question is do you want the namespace subject to the non-reassignability requirements of URNs? -MM -- -------------------------------------------------------------------------------- Michael Mealling | mailto:michael@research.netsol.com Advanced Naming Research Manager | go:Michael Mealling Verisign Applied Research | urn:pin:1 From owner-urn-ietf@LISTS.NETSOL.COM Mon Jul 2 13:57:52 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11213 for ; Mon, 2 Jul 2001 13:57:51 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id NAA14323; Mon, 2 Jul 2001 13:52:50 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 6775 for URN-IETF@LISTS.NETSOL.COM; Mon, 2 Jul 2001 13:50:02 -0400 Received: from deimos.hpl.hp.com (deimos.hpl.hp.com [192.6.19.190]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id NAA14312 for ; Mon, 2 Jul 2001 13:50:00 -0400 (EDT) Received: from hplns3.hpl.hp.com (hplns3.hpl.hp.com [15.0.48.4]) by deimos.hpl.hp.com (8.9.3 (PHNE_18546)/HPL-PA Relay) with ESMTP id KAA09811; Mon, 2 Jul 2001 10:43:46 -0700 (PDT) Received: from timpc.hpl.hp.com (timpc.hpl.hp.com [15.4.92.160]) by hplns3.hpl.hp.com (8.10.2/8.10.2 HPL-PA Hub) with ESMTP id f62Hi1x24099; Mon, 2 Jul 2001 10:44:01 -0700 (PDT) X-Sender: timothy@hplex1.hpl.hp.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 References: <3B407B10.E66D2829@ppp.uni-bamberg.de> <3B407B10.E66D2829@ppp.uni-bamberg.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed X-MIME-Autoconverted: from quoted-printable to 8bit by lists.netsol.com id NAA14313 Approved-By: Tim Kindberg Message-ID: <5.0.2.1.1.20010702103514.03360a98@hplex1.hpl.hp.com> Date: Mon, 2 Jul 2001 10:44:01 -0700 Reply-To: Tim Kindberg From: Tim Kindberg Subject: Re: URN Namespace for Structured Object Designators To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <20010702120522.R13798@bailey.dscga.com> X-MIME-Autoconverted: from 8bit to quoted-printable by lists.netsol.com id NAA14323 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA11213 Dieter, At 12:05 PM 7/2/2001 -0400, Michael Mealling wrote: >On Mon, Jul 02, 2001 at 03:45:52PM +0200, Dieter Köhler wrote: > > I developed and attached to this posting a proposal of a formal URN > namespace > > for what I call "Structured Object Designators". Because of its > global scope I > > wonder, (i) whether it is a candidate for the standards track > >.....The >timestamped domain-name is a recurring theme ....... You may not be aware of the tag URI scheme (see taguri.org), which your proposal bears some similarity to (at least at first glance). We also date-stamp an authority name to gain uniqueness over time, although we allow email addresses as well as domain names as the authority names. The essential difference seems to be that you mandate the syntax of what appears after the dated authority, whereas we specifically avoid doing so. We think that that is the business of the authority that mints the tag identifier, and no-one else. We went through some discussions with members of this list on the question of whether tags are URNs. You may want to look at the archives on that subject. Cheers, Tim. Tim Kindberg internet & mobile systems lab hewlett-packard laboratories 1501 page mill road, ms 1u-17 palo alto ca 94304-1126 usa www.champignon.net/TimKindberg/ timothy@hpl.hp.com voice +1 650 857 5609 fax +1 650 857 2358 From owner-urn-ietf@LISTS.NETSOL.COM Fri Jul 6 09:49:59 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA02394 for ; Fri, 6 Jul 2001 09:49:59 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id JAA01331; Fri, 6 Jul 2001 09:40:18 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 7512 for URN-IETF@LISTS.NETSOL.COM; Fri, 6 Jul 2001 09:37:49 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from mobile.webweaving.org (w149.z064000151.sjc-ca.dsl.cnc.net [64.0.151.149]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id CAA00226 for ; Fri, 6 Jul 2001 02:45:52 -0400 (EDT) Received: from localhost (dirkx@localhost) by mobile.webweaving.org (8.11.2/8.11.1) with ESMTP id f666dhc02381 for ; Thu, 5 Jul 2001 23:39:43 -0700 (PDT) X-Passed: MX on Titatovenaar at WebWeaving.org on Thu, 5 Jul 2001 23:39:43 -0700 (PDT) and masked X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. X-Curiousity: Killed the Cat X-Huis-aan-Huis-Sticker: Nee-Nee X-Authentication-Warning: titatovenaar.sfo.covalent.net: dirkx owned process doing -bs X-X-Sender: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-ID: Date: Thu, 5 Jul 2001 23:39:43 -0700 Reply-To: Dirk-Willem van Gulik From: Dirk-Willem van Gulik Subject: Java implementation. To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <3A0C97DC.546CC338@thinkingcat.com> Just realized how stale my bookmark list has become... ftp://research.netsol.com ,issn.org, vlc.com.au ... what happend to my world; are URL's perhaps not long term stable enough ? Any pointers to a recent and updated resolution library written in Java - I am getting a little annoyed by my SOAP implementation not quite getting the resolution of the urn's quite right - whilst throwing them around in just about every id reference. Txs, Dw From owner-urn-ietf@LISTS.NETSOL.COM Fri Jul 6 10:37:51 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA04513 for ; Fri, 6 Jul 2001 10:37:51 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id KAA01832; Fri, 6 Jul 2001 10:33:04 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 7604 for URN-IETF@LISTS.NETSOL.COM; Fri, 6 Jul 2001 10:31:01 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id KAA01762 for ; Fri, 6 Jul 2001 10:19:33 -0400 (EDT) Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id KAA06086; Fri, 6 Jul 2001 10:09:09 -0400 (EDT) References: <3A0C97DC.546CC338@thinkingcat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.2i Message-ID: <20010706100909.H4202@bailey.dscga.com> Date: Fri, 6 Jul 2001 10:09:09 -0400 Reply-To: Michael Mealling From: Michael Mealling Subject: Re: Java implementation. To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: ; from dirkx@COVALENT.NET on Thu, Jul 05, 2001 at 11:39:43PM -0700 On Thu, Jul 05, 2001 at 11:39:43PM -0700, Dirk-Willem van Gulik wrote: > Just realized how stale my bookmark list has become... > ftp://research.netsol.com ,issn.org, vlc.com.au ... what happend to my > world; are URL's perhaps not long term stable enough ? > > Any pointers to a recent and updated resolution library written in Java - > I am getting a little annoyed by my SOAP implementation not quite getting > the resolution of the urn's quite right - whilst throwing them around in > just about every id reference. I have the beginnings of one at http://www.usrlocalsrc.org/URN/download.html but it needs some serious help. One of the other problems is that people are using NIDs that aren't registered. While this isn't a huge issue right now, the only way they will resolve via the urn.arpa domain when its setup is to be real registered namespaces. Is there a particular API you'd like the resolver to work with? -MM -- -------------------------------------------------------------------------------- Michael Mealling | mailto:michael@research.netsol.com Advanced Naming Research Manager | go:Michael Mealling Verisign Applied Research | urn:pin:1 From owner-urn-ietf@LISTS.NETSOL.COM Fri Jul 6 18:45:25 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA22535 for ; Fri, 6 Jul 2001 18:45:24 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id SAA03499; Fri, 6 Jul 2001 18:37:29 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 7709 for URN-IETF@LISTS.NETSOL.COM; Fri, 6 Jul 2001 18:35:06 -0400 Received: from mail001.syd.optusnet.com.au (mail001.syd.optusnet.com.au [203.2.75.244]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id SAA03486 for ; Fri, 6 Jul 2001 18:35:03 -0400 (EDT) Received: from vlc.com.au (camax2-137.dialup.optusnet.com.au [198.142.117.137]) by mail001.syd.optusnet.com.au (8.11.1/8.11.1) with ESMTP id f66MShG01156; Sat, 7 Jul 2001 08:28:44 +1000 X-Mailer: Mozilla 4.76 [en]C-{C-UDP; OWL-18191} (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Approved-By: Justin Couch Message-ID: <3B463C20.291A734A@vlc.com.au> Date: Sat, 7 Jul 2001 08:30:56 +1000 Reply-To: Justin Couch From: Justin Couch Organization: The Virtual Light Company Subject: Re: Java implementation. To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit Dirk-Willem van Gulik wrote: > > Just realized how stale my bookmark list has become... > ftp://research.netsol.com ,issn.org, vlc.com.au ... what happend to my > world; are URL's perhaps not long term stable enough ? > > Any pointers to a recent and updated resolution library written in Java - Mine is still very active. The page hasn't changed in a long time, but the CVS repository has :) Right now, I'm using the lib in the Xj3D browser for VRML97/X3D content. I'm very happy with the basic library capabilities so the structure hasn't changed much at all. I'm spending more time just developing basic capabilities, such as a better set of content handlers. The only issue I can see on the near term cards is to add support for the JDK 1.4 URI class. -- Justin Couch http://www.vlc.com.au/~justin/ Freelance Java Consultant http://www.yumetech.com/ Author, Java 3D FAQ Maintainer http://www.j3d.org/ ------------------------------------------------------------------- "Humanism is dead. Animals think, feel; so do machines now. Neither man nor woman is the measure of all things. Every organism processes data according to its domain, its environment; you, with all your brains, would be useless in a mouse's universe..." - Greg Bear, Slant ------------------------------------------------------------------- From owner-urn-ietf@LISTS.NETSOL.COM Tue Jul 10 20:02:53 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA00588 for ; Tue, 10 Jul 2001 20:02:53 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id TAA18654; Tue, 10 Jul 2001 19:57:13 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 8314 for URN-IETF@LISTS.NETSOL.COM; Tue, 10 Jul 2001 19:54:45 -0400 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id TAA18635; Tue, 10 Jul 2001 19:54:44 -0400 (EDT) Message-ID: <200107102354.TAA18635@lists.netsol.com> Date: Tue, 10 Jul 2001 19:54:44 -0400 Reply-To: Constance Parker From: Constance Parker Subject: .ws extension To: URN-IETF@LISTS.NETSOL.COM Could someone please tell me what .ws extension stands for. I have looked through out NETWORK SOLUTIONS and can not find it. I know it is there somewhere along with .com, .edu etc. Thanks in advance Constance From owner-urn-ietf@LISTS.NETSOL.COM Tue Jul 10 22:48:45 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA06244 for ; Tue, 10 Jul 2001 22:48:45 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id WAA19450; Tue, 10 Jul 2001 22:44:01 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 8408 for URN-IETF@LISTS.NETSOL.COM; Tue, 10 Jul 2001 22:41:48 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from sh.w3.mag.keio.ac.jp (sh.w3.mag.keio.ac.jp [133.27.194.41]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id VAA19172 for ; Tue, 10 Jul 2001 21:19:47 -0400 (EDT) Received: from enoshima (g055115.ppp.asahi-net.or.jp [211.132.55.115]) by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id KAA14371; Wed, 11 Jul 2001 10:14:09 +0900 (JST) X-Sender: duerst@sh.w3.mag.keio.ac.jp X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Message-ID: <4.2.0.58.J.20010711101318.05e30860@sh.w3.mag.keio.ac.jp> Date: Wed, 11 Jul 2001 10:13:38 +0900 Reply-To: Martin Duerst From: Martin Duerst Subject: Re: .ws extension To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <200107102354.TAA18635@lists.netsol.com> I guess it's Western Samoa. Regards, Martin. At 19:54 01/07/10 -0400, Constance Parker wrote: >Could someone please tell me what .ws extension stands for. > >I have looked through out NETWORK SOLUTIONS and can not find it. > >I know it is there somewhere along with .com, .edu etc. > >Thanks in advance > >Constance From owner-urn-ietf@LISTS.NETSOL.COM Tue Jul 10 23:24:38 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA07045 for ; Tue, 10 Jul 2001 23:24:37 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id XAA19848; Tue, 10 Jul 2001 23:20:06 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 8491 for URN-IETF@LISTS.NETSOL.COM; Tue, 10 Jul 2001 23:18:01 -0400 Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by lists.netsol.com (8.9.3/8.9.3) with SMTP id XAA19833 for ; Tue, 10 Jul 2001 23:17:56 -0400 (EDT) Received: (qmail 79557 invoked from network); 11 Jul 2001 03:12:09 -0000 Received: from unknown (HELO Magnus) ([64.81.85.4]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 11 Jul 2001 03:12:09 -0000 References: <4.2.0.58.J.20010711101318.05e30860@sh.w3.mag.keio.ac.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Approved-By: Tim Langdell Message-ID: <02a801c109b6$e986ada0$0200a8c0@Magnus> Date: Tue, 10 Jul 2001 20:09:30 -0700 Reply-To: Tim Langdell From: Tim Langdell Subject: Re: .ws extension To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit Technically, yes, Samoa. But some while ago an entity took it over to turn it from a ccTLD to a gTLD, and they now market it as "WebSite" (rather like .tv has been marketed by dotTV). see: www.website.ws ----- Original Message ----- From: "Martin Duerst" To: Sent: Tuesday, July 10, 2001 6:13 PM Subject: Re: .ws extension > I guess it's Western Samoa. Regards, Martin. > > At 19:54 01/07/10 -0400, Constance Parker wrote: > >Could someone please tell me what .ws extension stands for. > > > >I have looked through out NETWORK SOLUTIONS and can not find it. > > > >I know it is there somewhere along with .com, .edu etc. > > > >Thanks in advance > > > >Constance > From owner-urn-ietf@LISTS.NETSOL.COM Tue Jul 10 23:49:05 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA07880 for ; Tue, 10 Jul 2001 23:49:05 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id XAA20162; Tue, 10 Jul 2001 23:44:09 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 8565 for URN-IETF@LISTS.NETSOL.COM; Tue, 10 Jul 2001 23:42:02 -0400 Received: from femail22.sdc1.sfba.home.com (femail22.sdc1.sfba.home.com [24.0.95.147]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id XAA20148 for ; Tue, 10 Jul 2001 23:42:01 -0400 (EDT) Received: from c261218a ([24.19.76.143]) by femail22.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010711033205.XNOB59.femail22.sdc1.sfba.home.com@c261218a> for ; Tue, 10 Jul 2001 20:32:05 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 5 (Lowest) X-MSMail-Priority: Low X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Low X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Approved-By: Webmaster Message-ID: <017001c109b9$d42be210$8f4c1318@c261218a> Date: Tue, 10 Jul 2001 22:30:27 -0500 Reply-To: Webmaster From: Webmaster Subject: Re: .ws extension To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <02a801c109b6$e986ada0$0200a8c0@Magnus> X-MIME-Autoconverted: from 8bit to quoted-printable by lists.netsol.com id XAA20162 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id XAA07880 I found this with Jim Fleming's help. Domain Names have a variety of basic rules: ---------------------------------------------------------------------------- ---- .WS Domain Names .WS - WebSite, to be used for commercial and personal sites Use only letters, numbers, or hyphen ("-") Cannot begin or end with a hyphen .WS domains registered through register.com™ must have between 4 and 59 characters, not including the .WS extension Thanks for all of you who helped me out. I was doing this to help a club and thank God it worked out for the best. Constance Parker -----Original Message----- From: Tim Langdell [mailto:langdell@technologist.com] Sent: Tuesday, July 10, 2001 10:10 PM To: Martin Duerst; URN-IETF@LISTS.NETSOL.COM Cc: Constance Parker Subject: Re: Re: .ws extension Technically, yes, Samoa. But some while ago an entity took it over to turn it from a ccTLD to a gTLD, and they now market it as "WebSite" (rather like .tv has been marketed by dotTV). see: www.website.ws ----- Original Message ----- From: "Martin Duerst" To: Sent: Tuesday, July 10, 2001 6:13 PM Subject: Re: .ws extension > I guess it's Western Samoa. Regards, Martin. > > At 19:54 01/07/10 -0400, Constance Parker wrote: > >Could someone please tell me what .ws extension stands for. > > > >I have looked through out NETWORK SOLUTIONS and can not find it. > > > >I know it is there somewhere along with .com, .edu etc. > > > >Thanks in advance > > > >Constance > From owner-urn-ietf@LISTS.NETSOL.COM Wed Jul 11 00:20:09 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA08629 for ; Wed, 11 Jul 2001 00:20:09 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id AAA20683; Wed, 11 Jul 2001 00:15:25 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 8668 for URN-IETF@LISTS.NETSOL.COM; Wed, 11 Jul 2001 00:13:22 -0400 Received: from pimout1-int.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id AAA20664 for ; Wed, 11 Jul 2001 00:13:20 -0400 (EDT) Received: from pc (nas-147-242.chicago-n.navipath.net [64.20.147.242]) by pimout1-int.prodigy.net (8.11.0/8.11.0) with SMTP id f6B47EK17056; Wed, 11 Jul 2001 00:07:14 -0400 References: <017001c109b9$d42be210$8f4c1318@c261218a> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Approved-By: Jim Fleming Message-ID: <00a401c109bf$2b6000c0$f2931440@pc> Date: Tue, 10 Jul 2001 23:08:39 -0500 Reply-To: Jim Fleming From: Jim Fleming Subject: Re: .ws extension To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit One note on .WS, it may be the only TLD that has a "Default A-Record Response". Most TLD servers when presented with a non-existent SLD name return a response that does not resolve. The .WS servers return an A-Record. I am not sure this is a good thing and have been surprised that the .COM folks have not done it. To test it....click here.... http://www.ThisIsLikelyANameThatIsNotRegistered.WS ...as for other TLD topics... http://www.ietf.org/mail-archive/ietf/Current/msg12574.html RFC-2001-07-01-000 IPv8 Expansion of Proof of Concept TLD Development Jim Fleming http://www.DOT-Arizona.com http://www.DOT.Arizona ----- Original Message ----- From: "Webmaster" To: Sent: Tuesday, July 10, 2001 10:30 PM Subject: Re: .ws extension I found this with Jim Fleming's help. Domain Names have a variety of basic rules: ---------------------------------------------------------------------------- ---- .WS Domain Names .WS - WebSite, to be used for commercial and personal sites Use only letters, numbers, or hyphen ("-") Cannot begin or end with a hyphen .WS domains registered through register.comT must have between 4 and 59 characters, not including the .WS extension Thanks for all of you who helped me out. I was doing this to help a club and thank God it worked out for the best. Constance Parker -----Original Message----- From: Tim Langdell [mailto:langdell@technologist.com] Sent: Tuesday, July 10, 2001 10:10 PM To: Martin Duerst; URN-IETF@LISTS.NETSOL.COM Cc: Constance Parker Subject: Re: Re: .ws extension Technically, yes, Samoa. But some while ago an entity took it over to turn it from a ccTLD to a gTLD, and they now market it as "WebSite" (rather like .tv has been marketed by dotTV). see: www.website.ws ----- Original Message ----- From: "Martin Duerst" To: Sent: Tuesday, July 10, 2001 6:13 PM Subject: Re: .ws extension > I guess it's Western Samoa. Regards, Martin. > > At 19:54 01/07/10 -0400, Constance Parker wrote: > >Could someone please tell me what .ws extension stands for. > > > >I have looked through out NETWORK SOLUTIONS and can not find it. > > > >I know it is there somewhere along with .com, .edu etc. > > > >Thanks in advance > > > >Constance > From owner-urn-ietf@LISTS.NETSOL.COM Wed Jul 11 09:15:14 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA02453 for ; Wed, 11 Jul 2001 09:15:13 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id JAA22520; Wed, 11 Jul 2001 09:07:03 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 8845 for URN-IETF@LISTS.NETSOL.COM; Wed, 11 Jul 2001 09:04:41 -0400 Received: from tomts5-srv.bellnexxia.net (tomts5.bellnexxia.net [209.226.175.25]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id JAA22501 for ; Wed, 11 Jul 2001 09:04:40 -0400 (EDT) Received: from thinkingcat.com ([64.229.193.32]) by tomts5-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010711125823.XIXP17517.tomts5-srv.bellnexxia.net@thinkingcat.com>; Wed, 11 Jul 2001 08:58:23 -0400 X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 References: <017001c109b9$d42be210$8f4c1318@c261218a> <00a401c109bf$2b6000c0$f2931440@pc> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Approved-By: Leslie Daigle Message-ID: <3B4C4CD2.400921B6@thinkingcat.com> Date: Wed, 11 Jul 2001 08:55:46 -0400 Reply-To: Leslie Daigle From: Leslie Daigle Organization: Thinking Cat Enterprises Subject: Stop it [was Re: .ws extension] To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit This discussion has nothing to do with the work of the URN WG. Please take it elsewhere. Thanks, Leslie. Jim Fleming wrote: > > One note on .WS, it may be the only TLD that has a "Default A-Record > Response". > > Most TLD servers when presented with a non-existent SLD name return > a response that does not resolve. The .WS servers return an A-Record. > I am not sure this is a good thing and have been surprised that the .COM > folks have not done it. > > To test it....click here.... > > http://www.ThisIsLikelyANameThatIsNotRegistered.WS > > ...as for other TLD topics... > > http://www.ietf.org/mail-archive/ietf/Current/msg12574.html > RFC-2001-07-01-000 IPv8 Expansion of Proof of Concept TLD Development > > Jim Fleming > http://www.DOT-Arizona.com > http://www.DOT.Arizona > > ----- Original Message ----- > From: "Webmaster" > To: > Sent: Tuesday, July 10, 2001 10:30 PM > Subject: Re: .ws extension > > I found this with Jim Fleming's help. > > Domain Names have a variety of basic rules: > > ---------------------------------------------------------------------------- > ---- > .WS Domain Names > .WS - WebSite, to be used for commercial and personal sites > Use only letters, numbers, or hyphen ("-") > Cannot begin or end with a hyphen > .WS domains registered through register.comT must have between 4 and 59 > characters, not including the .WS extension > > Thanks for all of you who helped me out. I was doing this to help a club > and thank God it worked out for the best. > > Constance Parker > > -----Original Message----- > From: Tim Langdell [mailto:langdell@technologist.com] > Sent: Tuesday, July 10, 2001 10:10 PM > To: Martin Duerst; URN-IETF@LISTS.NETSOL.COM > Cc: Constance Parker > Subject: Re: Re: .ws extension > > Technically, yes, Samoa. But some while ago an entity took it over to turn > it from a ccTLD to a gTLD, and they now market it as "WebSite" (rather like > .tv has been marketed by dotTV). > > see: www.website.ws > > ----- Original Message ----- > From: "Martin Duerst" > To: > Sent: Tuesday, July 10, 2001 6:13 PM > Subject: Re: .ws extension > > > I guess it's Western Samoa. Regards, Martin. > > > > At 19:54 01/07/10 -0400, Constance Parker wrote: > > >Could someone please tell me what .ws extension stands for. > > > > > >I have looked through out NETWORK SOLUTIONS and can not find it. > > > > > >I know it is there somewhere along with .com, .edu etc. > > > > > >Thanks in advance > > > > > >Constance > > -- ------------------------------------------------------------------- "The best laid plans are written in pencil." -- ThinkingCat Leslie Daigle leslie@thinkingcat.com ------------------------------------------------------------------- From owner-urn-ietf@LISTS.NETSOL.COM Wed Jul 11 10:43:33 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA05810 for ; Wed, 11 Jul 2001 10:43:33 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id KAA23104; Wed, 11 Jul 2001 10:37:16 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 8950 for URN-IETF@LISTS.NETSOL.COM; Wed, 11 Jul 2001 10:35:12 -0400 Received: from femail21.sdc1.sfba.home.com (femail21.sdc1.sfba.home.com [24.0.95.146]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id KAA23084 for ; Wed, 11 Jul 2001 10:35:10 -0400 (EDT) Received: from c261218a ([24.19.76.143]) by femail21.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010711142918.GPLP6500.femail21.sdc1.sfba.home.com@c261218a> for ; Wed, 11 Jul 2001 07:29:18 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 5 (Lowest) X-MSMail-Priority: Low X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Low Approved-By: Webmaster Message-ID: <001101c10a15$a8293b70$8f4c1318@c261218a> Date: Wed, 11 Jul 2001 09:27:47 -0500 Reply-To: Webmaster From: Webmaster Subject: Re: Stop it [was Re: .ws extension] To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <3B4C4CD2.400921B6@thinkingcat.com> Content-Transfer-Encoding: 7bit I am sorry and thanks for those who helped.' I will remove myself from the list as I did not come here to cause a problem. Sorry Leslie if this upset you. Constance Parker -----Original Message----- From: Leslie Daigle [mailto:leslie@thinkingcat.com] Sent: Wednesday, July 11, 2001 7:56 AM To: URN-IETF@LISTS.NETSOL.COM Subject: Stop it [was Re: .ws extension] This discussion has nothing to do with the work of the URN WG. Please take it elsewhere. Thanks, Leslie. Jim Fleming wrote: > > One note on .WS, it may be the only TLD that has a "Default A-Record > Response". > > Most TLD servers when presented with a non-existent SLD name return > a response that does not resolve. The .WS servers return an A-Record. > I am not sure this is a good thing and have been surprised that the .COM > folks have not done it. > > To test it....click here.... > > http://www.ThisIsLikelyANameThatIsNotRegistered.WS > > ...as for other TLD topics... > > http://www.ietf.org/mail-archive/ietf/Current/msg12574.html > RFC-2001-07-01-000 IPv8 Expansion of Proof of Concept TLD Development > > Jim Fleming > http://www.DOT-Arizona.com > http://www.DOT.Arizona > > ----- Original Message ----- > From: "Webmaster" > To: > Sent: Tuesday, July 10, 2001 10:30 PM > Subject: Re: .ws extension > > I found this with Jim Fleming's help. > > Domain Names have a variety of basic rules: > > -------------------------------------------------------------------------- -- > ---- > .WS Domain Names > .WS - WebSite, to be used for commercial and personal sites > Use only letters, numbers, or hyphen ("-") > Cannot begin or end with a hyphen > .WS domains registered through register.comT must have between 4 and 59 > characters, not including the .WS extension > > Thanks for all of you who helped me out. I was doing this to help a club > and thank God it worked out for the best. > > Constance Parker > > -----Original Message----- > From: Tim Langdell [mailto:langdell@technologist.com] > Sent: Tuesday, July 10, 2001 10:10 PM > To: Martin Duerst; URN-IETF@LISTS.NETSOL.COM > Cc: Constance Parker > Subject: Re: Re: .ws extension > > Technically, yes, Samoa. But some while ago an entity took it over to turn > it from a ccTLD to a gTLD, and they now market it as "WebSite" (rather like > .tv has been marketed by dotTV). > > see: www.website.ws > > ----- Original Message ----- > From: "Martin Duerst" > To: > Sent: Tuesday, July 10, 2001 6:13 PM > Subject: Re: .ws extension > > > I guess it's Western Samoa. Regards, Martin. > > > > At 19:54 01/07/10 -0400, Constance Parker wrote: > > >Could someone please tell me what .ws extension stands for. > > > > > >I have looked through out NETWORK SOLUTIONS and can not find it. > > > > > >I know it is there somewhere along with .com, .edu etc. > > > > > >Thanks in advance > > > > > >Constance > > -- ------------------------------------------------------------------- "The best laid plans are written in pencil." -- ThinkingCat Leslie Daigle leslie@thinkingcat.com ------------------------------------------------------------------- From owner-urn-ietf@LISTS.NETSOL.COM Thu Jul 12 04:31:04 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA15194 for ; Thu, 12 Jul 2001 04:31:04 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id LAA23493; Wed, 11 Jul 2001 11:11:23 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 9029 for URN-IETF@LISTS.NETSOL.COM; Wed, 11 Jul 2001 11:09:16 -0400 Received: from pimout1-int.prodigy.net ([207.115.63.77]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id LAA23459 for ; Wed, 11 Jul 2001 11:09:14 -0400 (EDT) Received: from pc (nas-147-235.chicago-n.navipath.net [64.20.147.235]) by pimout1-int.prodigy.net (8.11.0/8.11.0) with SMTP id f6BF26K47070; Wed, 11 Jul 2001 11:02:06 -0400 References: <001101c10a15$a8293b70$8f4c1318@c261218a> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400 Approved-By: Jim Fleming Message-ID: <013101c10a1a$a12d1bc0$51931440@pc> Date: Wed, 11 Jul 2001 10:03:21 -0500 Reply-To: Jim Fleming From: Jim Fleming Subject: Re: Stop it [was Re: .ws extension] To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit Constance, Your questions and comments are always welcome. http://www1.ietf.org/mail-archive/ietf/Current/msg12713.html RFC-2001-07-11-000 IPv4+ and Testing of TOS Routing on New.Net Transport Jim Fleming http://www.Unir.com ----- Original Message ----- From: "Webmaster" To: Sent: Wednesday, July 11, 2001 9:27 AM Subject: Re: Stop it [was Re: .ws extension] > I am sorry and thanks for those who helped.' > > I will remove myself from the list as I did not come here to cause a > problem. > > Sorry Leslie if this upset you. > > Constance Parker > > -----Original Message----- > From: Leslie Daigle [mailto:leslie@thinkingcat.com] > Sent: Wednesday, July 11, 2001 7:56 AM > To: URN-IETF@LISTS.NETSOL.COM > Subject: Stop it [was Re: .ws extension] > > > This discussion has nothing to do with the work of the URN WG. Please > take it elsewhere. > > Thanks, > Leslie. > > Jim Fleming wrote: > > > > One note on .WS, it may be the only TLD that has a "Default A-Record > > Response". > > > > Most TLD servers when presented with a non-existent SLD name return > > a response that does not resolve. The .WS servers return an A-Record. > > I am not sure this is a good thing and have been surprised that the .COM > > folks have not done it. > > > > To test it....click here.... > > > > http://www.ThisIsLikelyANameThatIsNotRegistered.WS > > > > ...as for other TLD topics... > > > > http://www.ietf.org/mail-archive/ietf/Current/msg12574.html > > RFC-2001-07-01-000 IPv8 Expansion of Proof of Concept TLD Development > > > > Jim Fleming > > http://www.DOT-Arizona.com > > http://www.DOT.Arizona > > > > ----- Original Message ----- > > From: "Webmaster" > > To: > > Sent: Tuesday, July 10, 2001 10:30 PM > > Subject: Re: .ws extension > > > > I found this with Jim Fleming's help. > > > > Domain Names have a variety of basic rules: > > > > -------------------------------------------------------------------------- > -- > > ---- > > .WS Domain Names > > .WS - WebSite, to be used for commercial and personal sites > > Use only letters, numbers, or hyphen ("-") > > Cannot begin or end with a hyphen > > .WS domains registered through register.comT must have between 4 and 59 > > characters, not including the .WS extension > > > > Thanks for all of you who helped me out. I was doing this to help a club > > and thank God it worked out for the best. > > > > Constance Parker > > > > -----Original Message----- > > From: Tim Langdell [mailto:langdell@technologist.com] > > Sent: Tuesday, July 10, 2001 10:10 PM > > To: Martin Duerst; URN-IETF@LISTS.NETSOL.COM > > Cc: Constance Parker > > Subject: Re: Re: .ws extension > > > > Technically, yes, Samoa. But some while ago an entity took it over to turn > > it from a ccTLD to a gTLD, and they now market it as "WebSite" (rather > like > > .tv has been marketed by dotTV). > > > > see: www.website.ws > > > > ----- Original Message ----- > > From: "Martin Duerst" > > To: > > Sent: Tuesday, July 10, 2001 6:13 PM > > Subject: Re: .ws extension > > > > > I guess it's Western Samoa. Regards, Martin. > > > > > > At 19:54 01/07/10 -0400, Constance Parker wrote: > > > >Could someone please tell me what .ws extension stands for. > > > > > > > >I have looked through out NETWORK SOLUTIONS and can not find it. > > > > > > > >I know it is there somewhere along with .com, .edu etc. > > > > > > > >Thanks in advance > > > > > > > >Constance > > > > > -- > > ------------------------------------------------------------------- > "The best laid plans > are written in pencil." > -- ThinkingCat > > Leslie Daigle > leslie@thinkingcat.com > ------------------------------------------------------------------- From owner-urn-ietf@LISTS.NETSOL.COM Mon Jul 16 16:23:27 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA02918 for ; Mon, 16 Jul 2001 16:23:27 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id QAA15457; Mon, 16 Jul 2001 16:17:55 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 5224 for URN-IETF@LISTS.NETSOL.COM; Mon, 16 Jul 2001 16:15:29 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from ietf.org (odin.ietf.org [132.151.1.176]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id PAA15383 for ; Mon, 16 Jul 2001 15:59:44 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27610; Mon, 16 Jul 2001 15:53:02 -0400 (EDT) Message-ID: <200107161953.PAA27610@ietf.org> Date: Mon, 16 Jul 2001 15:53:02 -0400 Reply-To: iesg@ietf.org Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: The IESG Subject: Last Call: URN Namespace Definition Mechanisms to BCP To: URN-IETF@LISTS.NETSOL.COM The IESG has received a request from the Uniform Resource Names Working Group to consider URN Namespace Definition Mechanisms 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 July 30, 2001. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-urn-rfc2611bis-03.txt From owner-urn-ietf@LISTS.NETSOL.COM Tue Jul 17 13:53:54 2001 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA02848 for ; Tue, 17 Jul 2001 13:53:53 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id NAA19093; Tue, 17 Jul 2001 13:54:52 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 5429 for URN-IETF@LISTS.NETSOL.COM; Tue, 17 Jul 2001 13:52:17 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from roam.psg.com (H-135-207-10-122.research.att.com [135.207.10.122]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id NAA18954; Tue, 17 Jul 2001 13:33:32 -0400 (EDT) Received: from randy by roam.psg.com with local (Exim 3.30 #1) id 15MYb7-0000LK-00; Tue, 17 Jul 2001 13:25:25 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Rsent-To: eos@ops.ietf.org Approved: snmp Message-ID: Date: Tue, 17 Jul 2001 13:25:25 -0400 Reply-To: The IESG From: The IESG Subject: Note Well To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit Greetings, This is the revised text of the NOTE WELL statement. ------------------------------------------------------ NOTE WELL All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to: - the IETF plenary session, - any IETF working group or portion thereof, - the IESG, or any member thereof on behalf of the IESG, - the IAB or any member thereof on behalf of the IAB, - any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, - the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions.