RFC 9423: Constrained RESTful Environments (CoRE) Target Attributes Registry
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9423
- Published
- April 2024
- Authors
- C. Bormann
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9176Constrained RESTful Environments (CoRE) Resource DirectoryCurrent
April 2022
- RFC 9290Concise Problem Details for Constrained Application Protocol (CoAP) APIsCurrent
October 2022
- RFC 9264Linkset: Media Types and a Link Relation Type for Link SetsCurrent
July 2022
- RFC 9876Updates to the IANA Registration Procedures for Constrained Application Protocol (CoAP) Content-FormatsCurrent
November 2025
- RFC 9952Application-Layer Protocol Negotiation (ALPN) ID for CoAP over DTLSCurrent
March 2026
- RFC 9953DNS over CoAP (DoC)Current
March 2026
- RFC 8790FETCH and PATCH with Sensor Measurement Lists (SenML)Current
June 2020
- RFC 8710Multipart Content-Format for the Constrained Application Protocol (CoAP)Current
February 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?