Re: [core] I-D Action: draft-ietf-core-new-block-02.txt

Hi all, 

We published the -02 as per the plan presented in the interim. The main changes are to reflect the outcomes of the interim:
(1) Add a statement that either both or neither options can be supported.
(2) Add an implementation note about how tokens are handled. 
(3) Change the name of the options.
(4) Add a clarification about the behaviour when multiple instances of Q-Block2 are included. 
(5) Remove the "MUST NOT" restriction on 2.31 (Continue) as a provision to (9). 
(6) Clarify what is meant by "repeat request". Marco, please check if the NEW wording is better.  
(7) Overflow discussion. Michael, please check and let us know if we need to say more. 
(8) Update the CDDL and add an implementation note to suggest the use of indefinite-length arrays.
(9) Add a note about the ACK_TIMEOUT delay after MAX_PAYLOADS. 

We are waiting for the feedback from the WG whether (9) is worth to be solved at the CoAP level. This is the main pending issue that we would like to fix before asking for the WGLC (https://mailarchive.ietf.org/arch/msg/core/uoXMI8vcsGoto6fa1GpgftXS-cU/). 

Please review and share your comments.

Cheers,
Jon & Med

> -----Message d'origine-----
> De : core [mailto:core-bounces@ietf.org] De la part de internet-
> drafts@ietf.org
> Envoyé : jeudi 29 octobre 2020 10:01
> À : i-d-announce@ietf.org
> Cc : core@ietf.org
> Objet : [core] I-D Action: draft-ietf-core-new-block-02.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Constrained RESTful Environments WG
> of the IETF.
> 
>         Title           : Constrained Application Protocol (CoAP)
> Block-Wise Transfer Options for Faster Transmission
>         Authors         : Mohamed Boucadair
>                           Jon Shallow
> 	Filename        : draft-ietf-core-new-block-02.txt
> 	Pages           : 25
> 	Date            : 2020-10-29
> 
> Abstract:
>    This document specifies alternative Constrained Application
> Protocol
>    (CoAP) Block-Wise transfer options: Q-Block1 and Q-Block2
> Options.
> 
>    These options are similar to the CoAP Block1 and Block2 Options,
> not
>    a replacement for them, but do enable faster transmission rates
> for
>    large amounts of data with less packet interchanges as well as
>    supporting faster recovery should any of the blocks get lost in
>    transmission.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-core-new-block/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-core-new-block-02
> https://datatracker.ietf.org/doc/html/draft-ietf-core-new-block-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-core-new-block-02
> 
> 
> Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at
> tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> 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.