[core] RFC 9039 on Uniform Resource Names for Device Identifiers

rfc-editor@rfc-editor.org Wed, 30 June 2021 20:45 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D228A3A29ED; Wed, 30 Jun 2021 13:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 74ZMnzxQZixB; Wed, 30 Jun 2021 13:45:21 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1631E3A29E9; Wed, 30 Jun 2021 13:45:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 552A9F40727; Wed, 30 Jun 2021 13:45:02 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, core@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210630204502.552A9F40727@rfc-editor.org>
Date: Wed, 30 Jun 2021 13:45:02 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/LNvPP9F_l7K1x08lbTtdE1zYeWs>
Subject: [core] =?utf-8?q?RFC_9039_on_Uniform_Resource_Names_for_Device_I?= =?utf-8?q?dentifiers?=
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jun 2021 20:45:26 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9039

        Title:      Uniform Resource Names for Device 
                    Identifiers 
        Author:     J. Arkko,
                    C. Jennings,
                    Z. Shelby
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2021
        Mailbox:    jari.arkko@piuha.net,
                    fluffy@iii.ca,
                    zach@edgeimpulse.com
        Pages:      15
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-core-dev-urn-11.txt

        URL:        https://www.rfc-editor.org/info/rfc9039

        DOI:        10.17487/RFC9039

This document describes a new Uniform Resource Name (URN) namespace
for hardware device identifiers. A general representation of device
identity can be useful in many applications, such as in sensor data
streams and storage or in equipment inventories. A URN-based
representation can be passed along in applications that need the
information.

This document is a product of the Constrained RESTful Environments Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: 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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC