[rfc-dist] RFC 9177 on Constrained Application Protocol (CoAP) Block-Wise Transfer Options Supporting Robust Transmission
rfc-editor@rfc-editor.org Wed, 23 March 2022 00:36 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A85C3A1927; Tue, 22 Mar 2022 17:36:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1647995788; bh=IoGkpq5HsFuNUvJxCXlrbHRgX17JiWKno9EP7c+kLfI=; h=To:From:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Cc; b=sSwEYtDWxYx8tLlCZAdR8sr8f/pdyxJ3/pNUOJvY2cKoyBcYuwWM6I4WxuQcQ3kuW R9W8oa+xAT3HLitkPOrJgUkOA1xLFj/iHHRmYqJp9Qf9uTm3HPTNhR3XFdZny+zpew 8sDkeoC82An/uNxNPvD76ziStWTomQOOgqVn0LrU=
X-Mailbox-Line: From rfc-dist-bounces@rfc-editor.org Tue Mar 22 17:36:20 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 88C003A1550; Tue, 22 Mar 2022 17:34:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1647995643; bh=IoGkpq5HsFuNUvJxCXlrbHRgX17JiWKno9EP7c+kLfI=; h=To:From:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Cc; b=B8yjL5DqAvoZhnvXtVJJRbSebhRrWgacsk+OIK2EORO0PjQRH9o+tG6W/tJmFg6Wz gAe89LssoO+tRh/nFx7IWNq32743qLw5RGxuDPPgC4pwgiDcYwTt0eOXChzQnsYCoL QQ6bySkpewhU/HN+ICQpCQWAzSa4WCZvAtRLYzsI=
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0853A154D for <rfc-dist@ietfa.amsl.com>; Tue, 22 Mar 2022 17:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 KkIZNyWC-af5 for <rfc-dist@ietfa.amsl.com>; Tue, 22 Mar 2022 17:33:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E51E3A153B for <rfc-dist@ietfa.amsl.com>; Tue, 22 Mar 2022 17:33:44 -0700 (PDT)
Received: by rfc-editor.org (Postfix) id 9355110D78; Tue, 22 Mar 2022 17:33:43 -0700 (PDT)
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 499) id 91C083BA9D; Tue, 22 Mar 2022 17:33:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20220323003343.91C083BA9D@rfc-editor.org>
Date: Tue, 22 Mar 2022 17:33:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/P9ueJw_LXfQDu44B1ndmKASyfWU>
Subject: [rfc-dist] RFC 9177 on Constrained Application Protocol (CoAP) Block-Wise Transfer Options Supporting Robust Transmission
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, core@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries. RFC 9177 Title: Constrained Application Protocol (CoAP) Block-Wise Transfer Options Supporting Robust Transmission Author: M. Boucadair, J. Shallow Status: Standards Track Stream: IETF Date: March 2022 Mailbox: mohamed.boucadair@orange.com, supjps-ietf@jpshallow.com Pages: 41 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-core-new-block-14.txt URL: https://www.rfc-editor.org/info/rfc9177 DOI: 10.17487/RFC9177 This document specifies alternative Constrained Application Protocol (CoAP) block-wise transfer options: Q-Block1 and Q-Block2. These options are similar to, but distinct from, the CoAP Block1 and Block2 options defined in RFC 7959. The Q-Block1 and Q-Block2 options are not intended to replace the Block1 and Block2 options but rather have the goal of supporting Non-confirmable (NON) messages for large amounts of data with fewer packet interchanges. Also, the Q-Block1 and Q-Block2 options support faster recovery should any of the blocks get lost in transmission. 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 _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org