[urn] Draft URN namespace assignment request
Alexander Martin <alexbuzzbee@gmail.com> Thu, 06 June 2019 00:17 UTC
Return-Path: <alexbuzzbee@gmail.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 BC954120142 for <urn@ietfa.amsl.com>; Wed, 5 Jun 2019 17:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2NRLWv8JtUK0 for <urn@ietfa.amsl.com>; Wed, 5 Jun 2019 17:17:48 -0700 (PDT)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0B0D120045 for <urn@ietf.org>; Wed, 5 Jun 2019 17:17:48 -0700 (PDT)
Received: by mail-qk1-x72b.google.com with SMTP id l128so435126qke.2 for <urn@ietf.org>; Wed, 05 Jun 2019 17:17:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:message-id:date:user-agent:mime-version :content-language; bh=2u8Jf53Ge+dhO//y0TweUMwbGpRuux5XLg2g5B9Q24g=; b=FpGxTk4BXMSdF+MrXk2GBJpZyCdhxGbOcS02x9XRac4kBpAQcDJeK5zmNIWzvO5q4p X8HTnE6UiHKDsrRp/CKU8Bg6Ozb965yaJDPLUitMqNhI9IceUPVVvU2GscZKyLNnxCvh y5JF239CoSFbFcLONYF1e7UbKXQc6RSfYoEZRYjLyAqUT9hvcEDZa6RUcqxbDRYT0lt1 VtLTHLtPjA9/lK2hJsTz7awSNOXhdDr+C6cgHQhE5u2XCmFIpHyEHX51K8K++a8frYsg zYkzq27zeQ4s4WG7XwR5gOnzq+PTZ06T7LQJ9DlnS+rEgSUBMRaz3w/XrnbCNAt7+04w jaWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-language; bh=2u8Jf53Ge+dhO//y0TweUMwbGpRuux5XLg2g5B9Q24g=; b=hhKXr5rZK322P+iN1VHNlj5+au3v1YaEqpZHSc/ZmjXv5K1wrUu9+WvZ1WjR86sMLb WnoBmo8HJ9DM2L7PytDyqgCjPEabg+AiTJwtkhcthZ2W/RwsF84rCPk293ctYQd6bHzW wHJkTqwUoIWgz/VOYD738eIzVAI5A+4SvWy1EtlfNRrFHjX8MloE6pF0WzNFNv1cuNDM 1Mbo6r2sl1xsyUbfT1DEQchn4fMU/KCo9PoYE1SuaMkF6QCDSYjcIC1QJ2a0eAcZ31W0 vRpOd0Ry4opZBfq7vijkr1LLj8BFThQZOB/KZjyS8G+5rYV0L6bDr5WzRXjWphpTYVA+ Rv9w==
X-Gm-Message-State: APjAAAVi7fazTLK7JK1w/ESzK+nph/xJlCmQo+TF45Gajw9nAkLsyBYT Z4RudfWgF52h1/aXeUX1k7QPED+G
X-Google-Smtp-Source: APXvYqz4VS7cT1yRwCLHyXPvrBlSn3ghc1Skn4GzzPMah4AODnxYy185tf0Awokg6kgF5n+N24hqFg==
X-Received: by 2002:a05:620a:533:: with SMTP id h19mr35844853qkh.325.1559780267498; Wed, 05 Jun 2019 17:17:47 -0700 (PDT)
Received: from alm-void-02.local (d-24-233-209-94.md.cpe.atlanticbb.net. [24.233.209.94]) by smtp.gmail.com with ESMTPSA id d17sm151307qtp.84.2019.06.05.17.17.46 for <urn@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Wed, 05 Jun 2019 17:17:46 -0700 (PDT)
From: Alexander Martin <alexbuzzbee@gmail.com>
To: urn@ietf.org
Message-ID: <6c9a05a7-bae3-0dc8-47d0-5ebd3f778e69@gmail.com>
Date: Wed, 05 Jun 2019 20:17:45 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------F2DD79BE6D0C0CA67BC69889"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/QIhouQ_IMtS-Lem-GCsaHl1ZHl8>
X-Mailman-Approved-At: Wed, 05 Jun 2019 18:33:59 -0700
Subject: [urn] Draft URN namespace assignment request
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 06 Jun 2019 01:13:31 -0000
Namespace Identifier: Assigned by IANA Version: 1 Date: 2019-06-05 Registrant: Alexander L. Martin alexbuzzbee@gmail.com Purpose: Identifies a resource with a name assigned by an arbitrary, non-centrally-registered authority, allowing the generation of URNs by applications and entities that do not have or do not wish to use a domain name, email address, or other registered identifier, but that still wish to use a human-readable name. Syntax: The syntactical structure of this namespace's NSS is identical to that of the 'uuid' namespace, with the addition of a human-readable name following a colon, like so: urn:urn-N:0fce65b6-bf2d-4dde-8e78-ef50d9d67a1e:foobar-xml-namespace The UUID serves as an "authority identifier" that prevents collisions between names assigned by different authorities. Each authority generates its own authority identifier, and can then assign an unlimited number of names using that authority identifier. URN-equivalence is as described in section 3 of RFC 4122 (under the heading "Rules for Lexical Equivalence") for UUIDs, and in section 3.1 of RFC 8141 for all other components. The structure and meaning of q-components, r-components, and f-components are not defined here, but may be defined by later specifications that make use of the namespace. Assignment: Each authority wishing to assign names generates a UUID. It then includes that UUID as the authority identifier in each name it assigns. The nature of UUIDs ensures that authority identifiers will not conflict unless the UUIDs are generated improperly. Security and Privacy: The UUID could serve to identify a particular entity if used many times, but the assigning authority could simply generate a new UUID to change its identity. Additionally, the UUID would not reveal information other than by correlating names assigned by the same authority, unless that UUID is somehow known to associate with a specific entity. Interoperability: There are no known interoperability concerns. Resolution: Because of the decentralized nature of UUIDs, a single resolution method is impossible. It may be possible for later specifications using the namespace to specify a resolution method. Documentation: This document. Additional Information: While both this namespace and 'uuid' make use of UUIDs, 'uuid' contains only a UUID, while this namespace also contains a human-readable name. Due to this, this namespace may, and likely will, use the same UUID for multiple names. An alternate possibility for fulfilment of the same need would be to update RFC 4122 in order to allow the use of a q-component or f-component to give a human-readable name. However, this would necessarily result in a violation of section 3.1 of RFC 8141, to wit: If an r-component, q-component, or f-component (or any combination thereof) is included in a URN, it MUST be ignored for purposes of determining URN-equivalence.
- [urn] Draft URN namespace assignment request Alexander Martin