Skip to main content

Last Call Review of draft-ietf-lpwan-schc-over-sigfox-17
review-ietf-lpwan-schc-over-sigfox-17-tsvart-lc-perkins-2022-12-20-00

Request Review of draft-ietf-lpwan-schc-over-sigfox
Requested revision No specific revision (document currently at 23)
Type Last Call Review
Team Transport Area Review Team (tsvart)
Deadline 2022-12-20
Requested 2022-12-06
Authors Juan-Carlos Zúñiga , Carles Gomez , Sergio Aguilar , Laurent Toutain , Sandra Cespedes , Diego S. Wistuba La Torre , Julien Boite
I-D last updated 2022-12-20
Completed reviews Intdir Last Call review of -17 by Jean-Michel Combes (diff)
Iotdir Last Call review of -16 by Behcet Sarikaya (diff)
Genart Last Call review of -20 by Elwyn B. Davies (diff)
Tsvart Last Call review of -17 by Colin Perkins (diff)
Opsdir Last Call review of -18 by Bo Wu (diff)
Assignment Reviewer Colin Perkins
State Completed
Request Last Call review on draft-ietf-lpwan-schc-over-sigfox by Transport Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/tsv-art/H_s7FLTCTliLFxBIpl39KOrOLD8
Reviewed revision 17 (document currently at 23)
Result Ready
Completed 2022-12-20
review-ietf-lpwan-schc-over-sigfox-17-tsvart-lc-perkins-2022-12-20-00
This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

This document describes a profile of Static Context Header Compression and
fragmentation (SCHC) [RFC 8724] to adapt it to with the Sigfox low-power
WAN protocol. 

The document appears clearly and precisely written, and gives a detailed
description of how the mapping of SCHC to Sigfox should operate. It makes
use of header compression and fragmentation/reassembly, which are frequent
areas of concern for the transport area, but appears to do so in a manner
that is consistent with RFC 8724 and draft-ietf-lpwan-schc-compound-ack,
and so doesn't raise any new transport issues.