[Dots] TR: [core] RFC 9177 on Constrained Application Protocol (CoAP) Block-Wise Transfer Options Supporting Robust Transmission

[[e-mail]]

Hi all, 

FYI. This spec is cited as normative in draft-ietf-dots-robust-blocks.

Cheers,
Med

-----Message d'origine-----
De : core <[e-mail]> De la part de [e-mail]
Envoyé : mercredi 23 mars 2022 01:34
À : [e-mail]; [e-mail]
Cc : [e-mail]; [e-mail]; [e-mail]
Objet : [core] RFC 9177 on Constrained Application Protocol (CoAP) Block-Wise Transfer Options Supporting Robust Transmission

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:    [e-mail],
                    [e-mail]
        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 [e-mail].  Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
core mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/core

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.