Re: [urn] Request for oneM2M URN Namespace registration

Peter Saint-Andre <stpeter@stpeter.im> Wed, 23 February 2022 17:19 UTC

Return-Path: <stpeter@stpeter.im>
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 A52773A115D for <urn@ietfa.amsl.com>; Wed, 23 Feb 2022 09:19:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.813
X-Spam-Level:
X-Spam-Status: No, score=-2.813 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=Ii1WlFcj; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Dfs7IDU2
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 gXTdCi7iDnJH for <urn@ietfa.amsl.com>; Wed, 23 Feb 2022 09:18:58 -0800 (PST)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 091A33A1150 for <urn@ietf.org>; Wed, 23 Feb 2022 09:18:57 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 9885632009E8; Wed, 23 Feb 2022 12:18:52 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 23 Feb 2022 12:18:52 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=cc :cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; bh=yZFULUT79Sn+o1 AycFrtL/jkUwHZjMjwrkyi/y6JU1k=; b=Ii1WlFcj/wGDbJWvswRumTrUK86s7v 2gTSzPsORE/pW8ncJmqyBpL22SVVsuORl277WSV1WxptEU7CNrIx5fOjLwGN/qn7 6x1chyITiunJMoA7mSqgbFs67wAu33mUcbDZolstGikGE+b5t4l/nCyYTDPNfTln RV6wGcqi2LLs/+LpcWjUu8cW6Ob//zflkOQudLfm+FvVnzvobDUy+cd1X1qA8nMt wJoyL5zBFKlcD8XDZCJqmoSX+4kWVcLuHE4envd8SXiyq9ecfmgclFBssh6paZ5p PnGdoWc3c/gFJ4VxLgCWwL78roqKnzBkO95mAOQ4uP5k8+XRIQpGyagw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=yZFULUT79Sn+o1AycFrtL/jkUwHZjMjwrkyi/y6JU 1k=; b=Dfs7IDU2sxRJS+l10hegqwB7yHBM2KbEDM92ISZVKuWhWKuwdaJwIv/TU E8iD/qTXK602MA98DbJr4Hzyrpsa6vMMn6xJMCepmnm+wbewLfPBikpggxEgjrGj +1HhsLv7m5sI7OECNmQyybQVhuXxiSLpsCdHkyx4pTnFnJiiVCPNK+OwGPZAWqyt /4zZoe0UGI443IV6HH2qaJ5dDIQy6r6Ojr0eVMGFvg/bfDcRaWOlwgcdxFRTvl34 Z3NGtUH/hp/UhNABgmOFae0XDE/zp4V1s4XWi7NK5tl+vyFiDBDSKJy8O+LJc49Z LwA47NJtYuVvO9lFOQzmoqDeIHJsg==
X-ME-Sender: <xms:e2wWYqiYYCpoNH1EH-7kuwKY2eITTXDkKKA1G3q2WUfRgkoZn2i5nA> <xme:e2wWYrALHofFN3xEVKdZQ8IbqRHUjG1wAO6hBbtG72GaexlzbFcPXvlpRbPY-9t4L CTtD5sdhEOYNqIvkA>
X-ME-Received: <xmr:e2wWYiFy6-Pl6PRvj5xsUE8SnzDtTRHMddmZA7QRyNwOMwQhQEU5b_D3LxCyDAEurjrRVfi4Y8P66BxDvKNLrycRrwFxuofrgmXtZu4>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrledtgdeljecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthejre dttdefjeenucfhrhhomheprfgvthgvrhcuufgrihhnthdqtehnughrvgcuoehsthhpvght vghrsehsthhpvghtvghrrdhimheqnecuggftrfgrthhtvghrnhepfefgueehteefkedvue egvdetheetieehtddtueejtedtueektdeihffgudekjefgnecuffhomhgrihhnpehivght fhdrohhrghdpihgrnhgrrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrg hmpehmrghilhhfrhhomhepshhtphgvthgvrhesshhtphgvthgvrhdrihhm
X-ME-Proxy: <xmx:e2wWYjSqGK3t2uKU-tjJbpo9gzan6OptcMEiza_Hamrv836Ii15q6g> <xmx:e2wWYnz0nhhn5w03Oq5_l54ZnRa-oAjKkSEGWDFwpFp8Z_W9vfUY9g> <xmx:e2wWYh4djLZLjx-oqipIF7o0A9-7JLp1UEZ9hPgJIv1xOoU3bNOOnA> <xmx:fGwWYgpIv6KoaUIr-HrOsxHGDAwfAdADPfEyjpet7wfyfiLW2Ruu3A>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 23 Feb 2022 12:18:51 -0500 (EST)
Message-ID: <05c07d2c-8f43-e8a9-fafd-15bee4dfe114@stpeter.im>
Date: Wed, 23 Feb 2022 10:18:50 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: Miguel Angel Reina Ortega <MiguelAngel.ReinaOrtega=40etsi.org@dmarc.ietf.org>
Cc: "urn@ietf.org" <urn@ietf.org>
References: <PR0P264MB1804CAE04B82C5D3D36EECAE8E3A9@PR0P264MB1804.FRAP264.PROD.OUTLOOK.COM> <87ee3ue2qz.fsf@hobgoblin.ariadne.com> <HE1PR07MB3196DEBC39E401BD187D3B99FA3C9@HE1PR07MB3196.eurprd07.prod.outlook.com> <PR0P264MB18044507FF06DE3F57B286F28E3C9@PR0P264MB1804.FRAP264.PROD.OUTLOOK.COM>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <PR0P264MB18044507FF06DE3F57B286F28E3C9@PR0P264MB1804.FRAP264.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/vLwVByp8oXyB8pi98IGhItob3WI>
Subject: Re: [urn] Request for oneM2M URN Namespace registration
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: Wed, 23 Feb 2022 17:19:04 -0000

On 2/23/22 2:09 AM, Miguel Angel Reina Ortega wrote:

> URN namespace registrations do not need to be RFCs. An RFC can be provided if the identifier system has not been specified elsewhere, and it is considered useful to create an RFC for this purpose (see e.g. RFC 8458; https://datatracker.ietf.org/doc/html/rfc8458). In your case, I do not think that RFC is required or even justified. It will be easier both for you and IETF if you send us just a template as specified in RFC 8141. All registrations published as such templates are listed at https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml.
> 
> ETSI has already made one namespace registration as a template, available at https://www.iana.org/assignments/urn-formal/etsi.
> 
> [MRO] ETSI URN namespace was registered by creating an RFC (https://tools.ietf.org/search/rfc8515), and because of the nature of oneM2M, I considered that the same approach was needed. In addition, we already did an attempt to register the oneM2M URN namespace in the past (some years ago) and we followed that approach (https://datatracker.ietf.org/doc/draft-fujimoto-urn-onem2m/history/).

Some registrants prefer to publish an RFC (e.g., for archival purposes), 
but I agree with Juha that this is not necessary. If nothing else, 
publishing an Internet-Draft can make it easier to track changes to the 
registration template, but this isn't necessary either.

Peter