MIME-Version: 1.0 Date: Mon, 12 Dec 2022 11:02:00 -0600 Reply-To: sarikaya@ieee.org Message-ID: Subject: IoT Draft Review Comments From: Behcet Sarikaya To: iot-dir@ietf.org, draft-ietf-lpwan-schc-over-sigfox@ietf.org, "Eric Vyncke (evyncke)" , lp-wan , lpwan-chairs@ietf.org Content-Type: multipart/alternative; boundary="0000000000007c69df05efa47694" --0000000000007c69df05efa47694 Content-Type: text/plain; charset="UTF-8" I am the assigned IoT Directorate reviewer for this draft. The Directorate aims to review IETF documents related with IoT (Internet of Things). Please treat these comments just like any other last call comments. For more information, please see https://trac.ietf.org/trac/int/wiki/IOTDirWiki. https://datatracker.ietf.org/group/iotdir/about/ Document:draft-ietf-lpwan-schc-over-sigfox-16.txt Reviewer:Behcet Sarikaya Review Date:2022-12-12 IETF Review End Date:2022-12-1-20 IESG Telechat date: (if known) Summary: Major issues:None Minor issues:Yes Nits/editorial comments:Yes In Introduction Base Stations then forward messages to the Sigfox Cloud infrastructure for further processing and final delivery to the customer What about receiving from cloud? (technical coverage of the cloud could be improved) In 3.6.1.3.1 Section Section 3.7.1 Section Section 4.1 Many places afterwards same repeated Section references In Section 3.1 Figure 1 NGW is referenced as Network Gateway, Sigfox Network, cloud-based Sigfox Core Network suggest Network Gateway (NGW) Section 8.1 RFC 3967 says IETF procedures generally require that a standards track RFC may not have a normative reference to another standards track document at a lower maturity level or to a non standards track specification refers to SCHC Compound Ack reference? --0000000000007c69df05efa47694 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I am the assigned IoT Directorate reviewer for this draft. The Direct= orate aims to review IETF documents related with IoT (Internet of Things). = Please treat these comments just like any other last call comments.

For more inform= ation, please see

https://tra= c.ietf.org/trac/int/wiki/IOTDirWiki.=C2=A0https://datatracker.ietf.org/group/iotdir/about/

Document:draft-ietf-lpwan-s= chc-over-sigfox-16.txt

Reviewer:Behcet Sarikaya

Review Date:2022-12-12

IETF Review End Date:2022-12= -1-20

IE= SG Telechat date: (if known)

Summary:

Major issues:None

Minor issues:Yes

Nits/editorial comments:Yes

<= p style=3D"box-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rg= b(36,41,47);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI&quo= t;,"Noto Sans",Helvetica,Arial,sans-serif,"Apple Color Emoji= ","Segoe UI Emoji"">In Introduction

Base Stations then forward messages to the Sigfox=C2=A0Cloud infrastructure for further processing and final deli= very to the=C2=A0customer


What about=C2=A0receiving=C2=A0from cloud? (technical= coverage of the cloud could be improved)

In 3.6.1.3.1=C2=A0

<= span style=3D"font-family:"Courier New";color:black">Section Sect= ion 3.7.1

Section Sec= tion 4.1=C2=A0

Many places afterwards same repeated Section reference= s

In Section 3.1

Figure= 1 NGW is referenced as Network Gateway, Sigfox Network, cloud-based Sigfox= Core Network

suggest Network Gateway (NGW)

= Section 8.1=C2=A0=

RFC 3967 says=C2=A0IETF procedures generally require that = a standards track RFC may not

   =
have a normative reference to another standards track document at a
   lower maturity level or to a non standards track specification
refers to SCHC Compound Ack reference?

=


--0000000000007c69df05efa47694--