[core] RFC 9423 on Constrained RESTful Environments (CoRE) Target Attributes Registry

rfc-editor@rfc-editor.org Thu, 11 April 2024 21:21 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
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 E5B5CC15154E; Thu, 11 Apr 2024 14:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.65
X-Spam-Level:
X-Spam-Status: No, score=-6.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CUccVGnbEajU; Thu, 11 Apr 2024 14:21:19 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28017C14F739; Thu, 11 Apr 2024 14:21:19 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id E393CCE3BD; Thu, 11 Apr 2024 14:21:18 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20240411212118.E393CCE3BD@rfcpa.amsl.com>
Date: Thu, 11 Apr 2024 14:21:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/DDel18asHhPDzAdzTenAHAqsYdc>
Subject: [core] RFC 9423 on Constrained RESTful Environments (CoRE) Target Attributes Registry
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 11 Apr 2024 21:21:24 -0000

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

        
        RFC 9423

        Title:      Constrained RESTful Environments (CoRE) Target 
                    Attributes Registry 
        Author:     C. Bormann
        Status:     Informational
        Stream:     IETF
        Date:       April 2024
        Mailbox:    cabo@tzi.org
        Pages:      8
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-core-target-attr-06.txt

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

        DOI:        10.17487/RFC9423

The Constrained RESTful Environments (CoRE) specifications apply web
technologies to constrained environments. One such important
technology is Web Linking (RFC 8288), which CoRE specifications use
as the basis for a number of discovery protocols, such as the Link
Format (RFC 6690) in the Constrained Application Protocol's (CoAP's)
resource discovery process (Section 7.2 of RFC 7252) and the Resource
Directory (RD) (RFC 9176). 

Web Links can have target attributes, the names of which are not
generally coordinated by the Web Linking specification (Section 2.2
of RFC 8288). This document introduces an IANA registry for
coordinating names of target attributes when used in CoRE. It updates
the "RD Parameters" IANA registry created by RFC 9176 to coordinate
with this registry.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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