< draft-ietf-lpwan-schc-over-lorawan-11.txt		draft-ietf-lpwan-schc-over-lorawan-12.txt >
	lpwan Working Group O. Gimenez, Ed.		lpwan Working Group O. Gimenez, Ed.
	Internet-Draft Semtech		Internet-Draft Semtech
	Intended status: Standards Track I. Petrov, Ed.		Intended status: Standards Track I. Petrov, Ed.
	Expires: April 18, 2021 Acklio		Expires: April 27, 2021 Acklio
	October 15, 2020		October 24, 2020
	Static Context Header Compression (SCHC) over LoRaWAN		Static Context Header Compression (SCHC) over LoRaWAN
	draft-ietf-lpwan-schc-over-lorawan-11		draft-ietf-lpwan-schc-over-lorawan-12
	Abstract		Abstract
	The Static Context Header Compression (SCHC) specification describes		The Static Context Header Compression (SCHC) specification describes
	generic header compression and fragmentation techniques for Low Power		generic header compression and fragmentation techniques for Low Power
	Wide Area Networks (LPWAN) technologies. SCHC is a generic mechanism		Wide Area Networks (LPWAN) technologies. SCHC is a generic mechanism
	designed for great flexibility so that it can be adapted for any of		designed for great flexibility so that it can be adapted for any of
	the LPWAN technologies.		the LPWAN technologies.
	This document specifies a profile of RFC8724 to use SCHC in LoRaWAN		This document specifies a profile of RFC8724 to use SCHC in LoRaWAN
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on April 18, 2021.		This Internet-Draft will expire on April 27, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 19, line 10 ¶		skipping to change at page 19, line 10 ¶
	the corresponding SCHC ACK message might be lost; therefore the SCHC		the corresponding SCHC ACK message might be lost; therefore the SCHC
	gateway MUST request a retransmission of this ACK when the		gateway MUST request a retransmission of this ACK when the
	retransmission timer expires. To open a downlink opportunity the		retransmission timer expires. To open a downlink opportunity the
	device MUST transmit an uplink every		device MUST transmit an uplink every
	RETRANSMISSION_TIMER/(MAX_ACK_REQUESTS *		RETRANSMISSION_TIMER/(MAX_ACK_REQUESTS *
	SCHC_ACK_REQ_DN_OPPORTUNITY). The format of this uplink is		SCHC_ACK_REQ_DN_OPPORTUNITY). The format of this uplink is
	application specific. It is RECOMMENDED for a device to send an		application specific. It is RECOMMENDED for a device to send an
	empty frame (see Section 4.6) but it is application specific and will		empty frame (see Section 4.6) but it is application specific and will
	be used by the NGW to transmit a potential SCHC ACK REQ.		be used by the NGW to transmit a potential SCHC ACK REQ.
	SCHC_ACK_REQ_DN_OPPORTUNITY is application specific and its		SCHC_ACK_REQ_DN_OPPORTUNITY is application specific and its
	recommended value <<<<<<< HEAD is 2, it MUST be greater than 1. This		recommended value is 2. It MUST be greater than 1. This allows to
	allows for more downlink opportunities than required by SCHC control		open a downlink opportunity to any downlink with higher priority than
	traffic, leaving opportunity for any other downlink with higher		the SCHC ACK REQ message.
	priority than SCHC ACK REQ message. ======= is 2. It MUST be
	greater than 1. This allows to open a downlink opportunity to any
	downlink with higher priority than the SCHC ACK REQ message. >>>>>>>
	0b92a54cc8a5551fcf289f74e1ae3637a2f1c217
	_Note_: The device MUST keep this SCHC ACK message in memory until it		_Note_: The device MUST keep this SCHC ACK message in memory until it
	receives a downlink SCHC Fragmentation Message (with FPort ==		receives a downlink SCHC Fragmentation Message (with FPort ==
	FPortDown) that is not a SCHC ACK REQ: it indicates that the SCHC		FPortDown) that is not a SCHC ACK REQ: it indicates that the SCHC
	gateway has received the SCHC ACK message.		gateway has received the SCHC ACK message.
	5.6.3.6. Class B or Class C devices		5.6.3.6. Class B or Class C devices
	Class B devices can receive in scheduled RX slots or in RX slots		Class B devices can receive in scheduled RX slots or in RX slots
	following the transmission of an uplink. Class C devices are almost		following the transmission of an uplink. Class C devices are almost
End of changes. 4 change blocks.
	11 lines changed or deleted		7 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/