Re: [lp-wan] I-D Action: draft-ietf-lpwan-coap-static-context-hc-06.txt

[<[e-mail]>]

Dear authors,

I've read draft-ietf-lpwan-coap-static-context-hc-06 .
Here are a few comments so far. I haven't seriously read OSCORE and
examples yet.
Overall, you are not using MUST and SHOULD. Is this intended because of
the informational status?

Technical
- I did not understand the last paragraph of 4.5 CoAP Token fields.
- I did not understand the first sentence of 5.3.1, Variable length
Uri-Path and Uri-Query. Do you mean "not" known? Also, I think the
following sentence no longer applies "and the LSB CDA must not carry any
value."
- 6.3 No-Response: "If the value is not known, ...". I guess you mean the
opposite.
- 6.4 Time Scale: "If the value is not known, ...". I guess you mean the
opposite.



Editorial
- Section 1 Introduction: "The context is said static since the field
description composing the Rules and the context are not learned during the
packet exchanges but are previously defined." Context used twice, sentence
needs rewriting.
- many more English writing nits, I will do a Pull Request on GitHub.

Best regards
Dominique 

Le 05/02/19 15:00, « lp-wan on behalf of [e-mail] »
<[e-mail] on behalf of [e-mail]> a écrit :

>
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
>This draft is a work item of the IPv6 over Low Power Wide-Area Networks
>WG of the IETF.
>
>        Title           : LPWAN Static Context Header Compression (SCHC)
>for CoAP
>        Authors         : Ana Minaburo
>                          Laurent Toutain
>                          Ricardo Andreasen
>	Filename        : draft-ietf-lpwan-coap-static-context-hc-06.txt
>	Pages           : 29
>	Date            : 2019-02-05
>
>Abstract:
>   This draft defines the way SCHC header compression can be applied to
>   CoAP headers.  The CoAP header structure differs from IPv6 and UDP
>   protocols since CoAP
>   use a flexible header with a variable number of options themselves of
>   a variable length.  The CoAP protocol is asymmetric in its format
>   messages, the format of the header packet in the request messages is
>   different than in the response messages.  Most of the compression
>   mechanisms have been introduced in
>   [I-D.ietf-lpwan-ipv6-static-context-hc], this document explains how
>   to use the SCHC compression for CoAP.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-lpwan-coap-static-context-hc/
>
>There are also htmlized versions available at:
>https://tools.ietf.org/html/draft-ietf-lpwan-coap-static-context-hc-06
>https://datatracker.ietf.org/doc/html/draft-ietf-lpwan-coap-static-context
>-hc-06
>
>A diff from the previous version is available at:
>https://www.ietf.org/rfcdiff?url2=draft-ietf-lpwan-coap-static-context-hc-
>06
>
>
>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/
>
>_______________________________________________
>lp-wan mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/lp-wan


_________________________________________________________________________________________________________________________

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.