RFC 8974 on Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP)
rfc-editor@rfc-editor.org Fri, 08 January 2021 20:21 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9B723A1288; Fri, 8 Jan 2021 12:21:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 gE1lKa-85c7k; Fri, 8 Jan 2021 12:21:11 -0800 (PST)
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 A95483A1286; Fri, 8 Jan 2021 12:21:11 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 124FCF4071C; Fri, 8 Jan 2021 12:21:06 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8974 on Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP)
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: <20210108202106.124FCF4071C@rfc-editor.org>
Date: Fri, 08 Jan 2021 12:21:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/NoweHKY8G7xN-FtkdO0ZO6q06fM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 20:21:13 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8974 Title: Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP) Author: K. Hartke, M. Richardson Status: Standards Track Stream: IETF Date: January 2021 Mailbox: klaus.hartke@ericsson.com, mcr+ietf@sandelman.ca Pages: 20 Updates: RFC 7252, RFC 8323 I-D Tag: draft-ietf-core-stateless-08.txt URL: https://www.rfc-editor.org/info/rfc8974 DOI: 10.17487/RFC8974 This document provides considerations for alleviating Constrained Application Protocol (CoAP) clients and intermediaries of keeping per-request state. To facilitate this, this document additionally introduces a new, optional CoAP protocol extension for extended token lengths. This document updates RFCs 7252 and 8323 with an extended definition of the "TKL" field in the CoAP message header. 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