Re: [urn] Formal request for URN for ITU
Ted Hardie <ted.ietf@gmail.com> Mon, 02 July 2018 20:12 UTC
Return-Path: <ted.ietf@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 5268F1312E5 for <urn@ietfa.amsl.com>; Mon, 2 Jul 2018 13:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 lTdFlzKBkZ1B for <urn@ietfa.amsl.com>; Mon, 2 Jul 2018 13:12:22 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (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 C887A1312DA for <urn@ietf.org>; Mon, 2 Jul 2018 13:12:14 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id k12-v6so4988701oiw.8 for <urn@ietf.org>; Mon, 02 Jul 2018 13:12:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=z0vufNDybjobbXYiIDJqIOaerQxIWfKvEWnTsTmEEQw=; b=KQQWwqe88xgkeXLjXreSrSHfDyfhOwxKtSIhabLacWfAjNI8PXsdqPfEdc5gFG1TPw E+9OZ0DgcJKfxtVuSITh+ut8aDeypI6+sdERuFwa+tiKX6iKRH6FzddDYftdh85Aj11t 1uuBYkIEfoDnJKk4nT7QPwjn1q9SvkKu5uJq++uUMX8nU2O/6PYb0ZXjKdhp+rBfYmV/ 2SRZlz0TTSIA3fESNw6BT2PRNXuk+NAfqnSu1h5d0HQGokhbn/nZte3cdRnKG9IUFdGZ +BGaj9ZJI4G4N2RxuEd34SYLBDPiOhfds2RLO55iFHht/OeALHzAYypPXssUP2KtvQsV uvDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=z0vufNDybjobbXYiIDJqIOaerQxIWfKvEWnTsTmEEQw=; b=fR4rXauUky70C5uD0BOKADfF+j2JStzl7xN1I7+2TDE4XJa4jq0KpVs/uLGaYtXZQI HbYbuDgYpx0XJG5HdW7zaPnBYCrrlWVQPkI4I4AFdRlhnJdDltvLwgdy+FVLJZ6Opx7K 8FrRcnHEAAyRc6QIu/L/ZbS9pDSo8wIFDNCiJQ0Y8W/kvIfZCa///AVKw28HQdQ30BiV yv4wyj9qa6CCbOg7raPC/kbjC8C0JfxoVCdDqx44QZBsO3AStn5fP+dnLq8WnQZV7t6T ArTFeVIrqbb3S9YAk/fY5u5zYjU3DefqM8uYIju9X+/M9iCfadMxzfOu2x86vVvFRbpb jUUA==
X-Gm-Message-State: APt69E1kAR/t5AHf+aeG2IKhABq9iNyQa8Fl2cDoCl7ACJIlhaq3oopx GtKN8PsYHN4Hyyf7gh5j1o6ghvmacNcLGS1pQU8=
X-Google-Smtp-Source: AAOMgpf52mDrdEOEcqJyWq0/MXAEbkfK+e8N0LJ7/Oz+yDekuvxsI0BW9afw3qeBkVv9zTJG8nsbN0rA2Dx6msjbZUs=
X-Received: by 2002:aca:d015:: with SMTP id h21-v6mr17897390oig.142.1530562334011; Mon, 02 Jul 2018 13:12:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:66d9:0:0:0:0:0 with HTTP; Mon, 2 Jul 2018 13:11:43 -0700 (PDT)
In-Reply-To: <CY1PR15MB02352EACC39739486038AB008B430@CY1PR15MB0235.namprd15.prod.outlook.com>
References: <CY1PR15MB0235486A2436E18C8F5C92CB8B430@CY1PR15MB0235.namprd15.prod.outlook.com> <CA+9kkMAgy9WBO2gXfQDEoC0DOeUa1UeyJuAgpzMWo9_tbthGPA@mail.gmail.com> <CY1PR15MB02352EACC39739486038AB008B430@CY1PR15MB0235.namprd15.prod.outlook.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 02 Jul 2018 13:11:43 -0700
Message-ID: <CA+9kkMAoxs=XdMn7FtRJeVDK7ZPzRD_9UBHY77p8nGEQxJ89sw@mail.gmail.com>
To: Scott Mansfield <scott.mansfield@ericsson.com>
Cc: "urn@ietf.org" <urn@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000039b6d4057009d081"
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/GwQMnZ8qlqDbIEutmAqt9Rv_Bqs>
Subject: Re: [urn] Formal request for URN for ITU
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.26
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: Mon, 02 Jul 2018 20:12:32 -0000
Hi Scott, Thanks for the quick responses, I appreciate it. regards, Ted On Mon, Jul 2, 2018 at 12:21 PM, Scott Mansfield < scott.mansfield@ericsson.com> wrote: > For your first question about “a single document may have more than one > recommendation string defined’… > > <scott> > > If the namespace was used for their document repository, the ITU would > create a unique identifier for each document. So that if the documents > were identical (except for file name) then there would be multiple > identifiers. > > </scott> > > > > For your second question about “ITU-TSB”. > > <scott> > > Registering organization: > > Name: International Telecommunication Union (ITU) > > > > The address provided is the address of the group that is maintaining the > ITU namespace. So I would argue that ITU-TSB is not the registrant, but > ITU is. In the purpose section it talks about “Namespace needed for > identifier defined by ITU”. Also in section 2.6 it states that “ITU will > manage…”. Yes the example I give is for the ITU-T, but that is because the > T Sector will be the first to use the ITU namespace. > > > > The ITU General Secretariat has been contacted and has agreed with this > proposal. TSB will manage and coordinate with the ITU General Secretariat > and also the other ITU sectors. > > </scott> > > > > If I’m not being clear, or have misunderstood something, please let me > know. > > > > Regards, > > -scott. > > > > *From:* Ted Hardie <ted.ietf@gmail.com> > *Sent:* Monday, July 02, 2018 2:45 PM > *To:* Scott Mansfield <scott.mansfield@ericsson.com> > *Cc:* urn@ietf.org > *Subject:* Re: [urn] Formal request for URN for ITU > > > > Hi Scott, > > > > Thanks for providing this. Two questions to confirm my understanding of > how the namespace will be maintained. First, it's my understanding that in > the ITU system that a single document may have more than one recommendation > string defined. See: https://www.itu.int/rec/R-REC-BO.1774/en for an > example, of a pointer to identical documents within that system. It would > be useful for the ITU to communicate whether, as namespace manager, it will > mint multiple identifiers for identical documents (as I understand it, this > is permitted, but it is useful for others to understand when or if it will > be done). Second, the document lists a registrant in ITU-TSB and the > origin of the request is apparently in the needs of Study Group 15. Has > the registrant considered whether a namespace specific to ITU-TSB might > serve its needs as well, or confirmed that the other ITU Sectors have > confirmed this registration? > > > > Note that I do not believe that answering either of these is required by > the process; I put them forward solely to understand better how this will > be used. Thanks for any insight. > > > > regards, > > > > Ted > > > > On Mon, Jul 2, 2018 at 7:03 AM, Scott Mansfield < > scott.mansfield@ericsson.com> wrote: > > This is a request from International Telecommunication Union (ITU) for a > namespace. > > > > Please review and provide comments/revisions to ensure clarity and focus > of the request. The format of the request is in ID format capturing the > information requested from Appendix A of RFC 8141. > > > > Regards, > > -scott. > > > > Scott Mansfield > > Ericsson Inc. > > +1 724 931 9316 > > > > > _______________________________________________ > urn mailing list > urn@ietf.org > https://www.ietf.org/mailman/listinfo/urn > > >
- Re: [urn] Formal request for URN for ITU Scott Mansfield
- Re: [urn] Formal request for URN for ITU Peter Saint-Andre
- Re: [urn] Formal request for URN for ITU Scott Mansfield
- Re: [urn] Formal request for URN for ITU Scott Mansfield
- Re: [urn] Formal request for URN for ITU Dale R. Worley
- Re: [urn] Formal request for URN for ITU John R Levine
- Re: [urn] Formal request for URN for ITU Dale R. Worley
- [urn] Formal request for URN for ITU Scott Mansfield
- Re: [urn] Formal request for URN for ITU Ted Hardie
- Re: [urn] Formal request for URN for ITU Ted Hardie
- Re: [urn] Formal request for URN for ITU Scott Mansfield
- Re: [urn] Formal request for URN for ITU Dale R. Worley
- Re: [urn] Formal request for URN for ITU Scott Mansfield
- Re: [urn] Formal request for URN for ITU Dale R. Worley
- Re: [urn] Formal request for URN for ITU Hakala, Juha E
- Re: [urn] Formal request for URN for ITU John Levine
- Re: [urn] Formal request for URN for ITU Dale R. Worley
- Re: [urn] Formal request for URN for ITU Hakala, Juha E
- Re: [urn] Formal request for URN for ITU Scott Mansfield
- Re: [urn] Formal request for URN for ITU John R Levine
- Re: [urn] Formal request for URN for ITU John C Klensin
- Re: [urn] Formal request for URN for ITU Scott Mansfield
- Re: [urn] Formal request for URN for ITU John C Klensin
- Re: [urn] Formal request for URN for ITU Scott Mansfield
- Re: [urn] Formal request for URN for ITU Hakala, Juha E