IETF Logo Mail Archive

Re: [urn] // in gnunet://, and other P2P URN's

Larry Masinter <masinter@adobe.com> Wed, 24 October 2012 21:22 UTC

Return-Path: <masinter@adobe.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BDC021F88D4 for <urn@ietfa.amsl.com>; Wed, 24 Oct 2012 14:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.599
X-Spam-Level:
X-Spam-Status: No, score=-107.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13waF5pQOvK6 for <urn@ietfa.amsl.com>; Wed, 24 Oct 2012 14:22:28 -0700 (PDT)
Received: from exprod6og106.obsmtp.com (exprod6og106.obsmtp.com [64.18.1.191]) by ietfa.amsl.com (Postfix) with ESMTP id 21DC421F8869 for <urn@ietf.org>; Wed, 24 Oct 2012 14:22:28 -0700 (PDT)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob106.postini.com ([64.18.5.12]) with SMTP ID DSNKUIhcEjQzyoU9reJkLLb8K/twOuK7Rzcx@postini.com; Wed, 24 Oct 2012 14:22:28 PDT
Received: from inner-relay-4.eur.adobe.com (inner-relay-4b [10.128.4.237]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id q9OLMQHP026175; Wed, 24 Oct 2012 14:22:26 -0700 (PDT)
Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98]) by inner-relay-4.eur.adobe.com (8.12.10/8.12.9) with ESMTP id q9OLKtXO012157; Wed, 24 Oct 2012 14:22:24 -0700 (PDT)
Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by nahub02.corp.adobe.com ([10.8.189.98]) with mapi; Wed, 24 Oct 2012 14:20:59 -0700
From: Larry Masinter <masinter@adobe.com>
To: Ivan Shmakov <oneingray@gmail.com>, "urn@ietf.org" <urn@ietf.org>
Date: Wed, 24 Oct 2012 14:20:57 -0700
Thread-Topic: [urn] // in gnunet://, and other P2P URN's
Thread-Index: Ac2ulW0Jsg6roougQBCt5GvY6E19SADl7eRg
Message-ID: <C68CB012D9182D408CED7B884F441D4D1E36C36954@nambxv01a.corp.adobe.com>
References: <86ehkwcr3v.fsf@gray.siamics.net> <50804510.7080900@grothoff.org> <8662679iun.fsf@gray.siamics.net> <20121019122226.GB21513@laperouse.bortzmeyer.org> <86mwzi8rfn.fsf_-_@gray.siamics.net> <86sj997gd7.fsf_-_@gray.siamics.net>
In-Reply-To: <86sj997gd7.fsf_-_@gray.siamics.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [urn] // in gnunet://, and other P2P URN's
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 21:22:32 -0000

(don't think this is a 'urn' issue, but):


http://tools.ietf.org/html/draft-ietf-iri-4395bis-irireg

3.2.  Syntactic Compatibility
   Avoid improper use of "//".  The use of double slashes in the first
   part of a URI/IRI is not an artistic indicator that what follows is a
   URI/IRI: Double slashes are used ONLY when the syntax of the <scheme-
   specific-part> contains a hierarchical structure.  In URIs and IRIs
   from such schemes, the use of double slashes indicates that what
   follows is the top hierarchical element for a naming authority.
   (Section 3.2 of RFC 3986 has more details.)  Schemes that do not
   contain a conformant hierarchical structure in their <scheme-
   specific-part> SHOULD NOT use double slashes following the
   "<scheme>:" string.

That is, the only effect of //  / delimited authority is on the resolution of relative references in contexts that do not otherwise have a "base".

> -----Original Message-----
> From: urn-bounces@ietf.org [mailto:urn-bounces@ietf.org] On Behalf Of Ivan
> Shmakov
> Sent: Saturday, October 20, 2012 12:28 AM
> To: urn@ietf.org
> Subject: [urn] // in gnunet://, and other P2P URN's
> 
> 	Well, we've discussed [1] this a bit in p2p-hackers@, and it
> 	seems that I've ran out of arguments by now.
> 
> 	The current GNUnet implementation [2] employs URI's like the
> 	following one for identifying content:
> 
> gnunet://fs/chk/17GU5A2CIAQMP0K0UIGI0F3SVVB1M5HCVQC74U6KQQV9LUV
> JHG78ID6DLNS3EKFKT6EH24QINVVFP5CEB9455I57KAE9AT1CSM98HA0.7MPI2R9L
> PGVIVPADTVKJBIRKQRQVVVQ5Q0N8HU8DDRHTK56P73SUPB82V356SFJQSL0H2
> RNHL2MLI8AM7BA3TAOS2D97K0RQ86VDVG0.14
> 
> 	where 17G…HA0 is (AIUI) the Base32-encoded hash of the content.
> 
> 	My point was that // in gnunet:// implies some sort of naming
> 	authority, which ‘fs’ (which names the “filesharing” component
> 	of GNUnet) is not.  So, presuming that the GNUnet URI scheme
> 	will (eventually) be submitted for registration with IANA, I've
> 	suggested to switch to the gnunet:fs: prefix instead.
> 	Unfortunately, as it now appears, I cannot clearly explain why
> 	exactly such a change should be made.
> 
> 	Could this issue be clarified, please?
> 
> 	TIA.
> 
> [1] http://comments.gmane.org/gmane.network.peer-to-peer.p2p-
> hackers/3569
> [2] http://gnunet.org/
> 
> --
> FSF associate member #7257
> 
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn

v2.23.0 | Report a Bug | By Email