[core] I-D Action: draft-ietf-core-responses-00.txt

internet-drafts@ietf.org Mon, 12 January 2026 10:39 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <176821438812.660281.5680701629247496131@dt-datatracker-5656579b89-r5kdq>
Date: Mon, 12 Jan 2026 02:39:48 -0800
Message-ID-Hash: G7GYVY5ML6V26O6YTQHZOA7A6BCWCVK4
CC: core@ietf.org
Reply-To: core@ietf.org
Subject: [core] I-D Action: draft-ietf-core-responses-00.txt
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/mp8d8V0xP10Auzkp4BEp_yuIRyk>

Internet-Draft draft-ietf-core-responses-00.txt is now available. It is a work
item of the Constrained RESTful Environments (CORE) WG of the IETF.

   Title:   CoAP: Non-traditional response forms
   Authors: Carsten Bormann
            Christian Amsüss
   Name:    draft-ietf-core-responses-00.txt
   Pages:   14
   Dates:   2026-01-12

Abstract:

   In CoAP as defined by RFC 7252, responses are always unicast back to
   a client that posed a request.  The present memo describes two forms
   of responses that go beyond that model.

   The design spaces for the new CoAP Options proposed to represent
   these responses are now sufficiently understood that they can be
   developed to standards-track specifications, either in this document
   or by transferring the specification for an Option to a document that
   that Option closely works with.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-core-responses/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-core-responses-00.html

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts

[core] I-D Action: draft-ietf-core-responses-00.t… internet-drafts