< draft-gomez-6lo-schc-15dot4-00.txt		draft-gomez-6lo-schc-15dot4-01.txt >
	6lo Working Group C. Gomez		6lo Working Group C.G. Gomez
	Internet-Draft UPC		Internet-Draft UPC
	Intended status: Standards Track A. Minaburo		Intended status: Standards Track A.M. Minaburo
	Expires: January 11, 2022 Acklio		Expires: 26 April 2022 Acklio
	July 10, 2021		October 2021
	Transmission of SCHC-compressed packets over IEEE 802.15.4 networks		Transmission of SCHC-compressed packets over IEEE 802.15.4 networks
	draft-gomez-6lo-schc-15dot4-00		draft-gomez-6lo-schc-15dot4-01
	Abstract		Abstract
	A framework called Static Context Header Compression and		A framework called Static Context Header Compression and
	fragmentation (SCHC) has been designed with the primary goal of		fragmentation (SCHC) has been designed with the primary goal of
	supporting IPv6 over Low Power Wide Area Network (LPWAN) technologies		supporting IPv6 over Low Power Wide Area Network (LPWAN) technologies
	[RFC8724]. One of the SCHC components is a header compression		[RFC8724]. One of the SCHC components is a header compression
	mechanism. If used properly, SCHC header compression allows a		mechanism. If used properly, SCHC header compression allows a
	greater compression ratio than that achievable with traditional		greater compression ratio than that achievable with traditional
	6LoWPAN header compression [RFC6282]. For this reason, it may make		6LoWPAN header compression [RFC6282]. For this reason, it may make
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line -198 ¶
	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 January 11, 2022.		This Internet-Draft will expire on 4 April 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 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/
	(https://trustee.ietf.org/license-info) in effect on the date of		license-info) in effect on the date of publication of this document.
	publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		Please review these documents carefully, as they describe your rights
	to this document. Code Components extracted from this document must		and restrictions with respect to this document. Code Components
	include Simplified BSD License text as described in Section 4.e of		extracted from this document must include Simplified BSD License text
	the Trust Legal Provisions and are provided without warranty as		as described in Section 4.e of the Trust Legal Provisions and are
	described in the Simplified BSD License.		provided without warranty as described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2.1. Requirements language . . . . . . . . . . . . . . . . . . 3		2.1. Requirements language . . . . . . . . . . . . . . . . . . 4
	2.2. Background on SCHC . . . . . . . . . . . . . . . . . . . 4		2.2. Background on SCHC . . . . . . . . . . . . . . . . . . . 4
	3. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 4		3. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 4
	3.1. Network topologies . . . . . . . . . . . . . . . . . . . 4		3.1. Network topologies . . . . . . . . . . . . . . . . . . . 4
	3.2. Protocol stack . . . . . . . . . . . . . . . . . . . . . 4		3.2. Protocol stack . . . . . . . . . . . . . . . . . . . . . 4
	4. Frame Format . . . . . . . . . . . . . . . . . . . . . . . . 5		4. Frame Format . . . . . . . . . . . . . . . . . . . . . . . . 5
	4.1. SCHC Dispatch . . . . . . . . . . . . . . . . . . . . . . 6		4.1. SCHC Dispatch . . . . . . . . . . . . . . . . . . . . . . 6
	4.2. Padding . . . . . . . . . . . . . . . . . . . . . . . . . 6		4.2. SCHC Header . . . . . . . . . . . . . . . . . . . . . . . 6
			4.3. Padding . . . . . . . . . . . . . . . . . . . . . . . . . 6
	5. SCHC compression for IPv6, UDP, and CoAP headers . . . . . . 6		5. SCHC compression for IPv6, UDP, and CoAP headers . . . . . . 6
	6. Fragmentation and reassembly . . . . . . . . . . . . . . . . 7		5.1. SCHC compression for IPv6 and UDP headers . . . . . . . . 6
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		5.1.1. Compression of IPv6 addresses . . . . . . . . . . . . 7
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 7		5.1.2. Compression of UDP ports . . . . . . . . . . . . . . 7
	9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7		5.2. SCHC compression for CoAP headers . . . . . . . . . . . . 7
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		5.3. Header compression examples . . . . . . . . . . . . . . . 8
	10.1. Normative References . . . . . . . . . . . . . . . . . . 7		6. Fragmentation and reassembly . . . . . . . . . . . . . . . . 8
	10.2. Informative References . . . . . . . . . . . . . . . . . 8		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8		8. Security Considerations . . . . . . . . . . . . . . . . . . . 8
			9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
			10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
			10.1. Normative References . . . . . . . . . . . . . . . . . . 8
			10.2. Informative References . . . . . . . . . . . . . . . . . 10
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
	1. Introduction		1. Introduction
	RFC 6282 is the main specification for IPv6 over Low power Wireless		RFC 6282 is the main specification for IPv6 over Low power Wireless
	Personal Area Network (6LoWPAN) IPv6 header compression [RFC6282].		Personal Area Network (6LoWPAN) IPv6 header compression [RFC6282].
	This RFC was designed assuming IEEE 802.15.4 as the layer below the		This RFC was designed assuming IEEE 802.15.4 as the layer below the
	6LoWPAN adaptation layer, and it has also been reused (with proper		6LoWPAN adaptation layer, and it has also been reused (with proper
	adaptations) for IPv6 header compression over many other technologies		adaptations) for IPv6 header compression over many other technologies
	relatively similar to IEEE 802.15.4 in terms of characteristics such		relatively similar to IEEE 802.15.4 in terms of characteristics such
	as physical layer bit rate, layer 2 maximum payload size, etc.		as physical layer bit rate, layer 2 maximum payload size, etc.
	skipping to change at page 3, line 27 ¶		skipping to change at page 3, line 34 ¶
	Protocol (CoAP) headers as well [RFC7252][RFC8824], which further		Protocol (CoAP) headers as well [RFC7252][RFC8824], which further
	increases the achievable performance improvement of using SCHC header		increases the achievable performance improvement of using SCHC header
	compression, since there is no 6LoWPAN header compression defined for		compression, since there is no 6LoWPAN header compression defined for
	CoAP. Therefore, it may make sense to use SCHC header compression in		CoAP. Therefore, it may make sense to use SCHC header compression in
	some 6LoWPAN environments [I-D.toutain-6lo-6lo-and-schc], including		some 6LoWPAN environments [I-D.toutain-6lo-6lo-and-schc], including
	IEEE 802.15.4 networks, considering its greater efficiency.		IEEE 802.15.4 networks, considering its greater efficiency.
	If SCHC header compression is added to the panoply of header		If SCHC header compression is added to the panoply of header
	compression mechanisms used in 6LoWPAN environments, then there is a		compression mechanisms used in 6LoWPAN environments, then there is a
	need to signal when a packet header has been compressed by using		need to signal when a packet header has been compressed by using
	SCHC. To this end, in its current form, the present document		SCHC. To this end, the present document specifies a 6LoWPAN Dispatch
	specifies a 6LoWPAN Dispatch Type for SCHC header compression, based		Type for SCHC header compression [RFC4944].
	on exploiting RFC 8025 Dispatch type space [RFC8025].
	This document specifies how a SCHC-compressed packet can be carried		This document specifies how a SCHC-compressed packet can be carried
	over IEEE 802.15.4 networks. Note that, as per this document, and		over IEEE 802.15.4 networks. Note that, as per this document, and
	while SCHC defines fragmentation mechanisms as well, 6LoWPAN/6Lo		while SCHC defines fragmentation mechanisms as well, 6LoWPAN/6Lo
	fragmentation is used when necessary to transport SCHC-compressed		fragmentation is used when necessary to transport SCHC-compressed
	packets over IEEE 802.15.4 networks [RFC4944][RFC8931].		packets over IEEE 802.15.4 networks [RFC4944][RFC8930][RFC8931].
	TO-DO: indicate here any specific updates of RFC 8724 for IEEE		TO-DO: indicate here any specific updates of RFC 8724 for use over
	802.15.4.		IEEE 802.15.4.
	2. Terminology		2. Terminology
	2.1. Requirements language		2.1. Requirements language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in		"OPTIONAL" in this document are to be interpreted as described in
	BCP14 [RFC2119], [RFC8174], when, and only when, they appear in all		BCP14 [RFC2119], [RFC8174], when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
	2.2. Background on SCHC		2.2. Background on SCHC
	skipping to change at page 5, line 19 ¶		skipping to change at page 5, line 19 ¶
	+------------+ +------------+		+------------+ +------------+
	| IPv6 | | IPv6 |		| IPv6 | | IPv6 |
	+------------+ +------------+		+------------+ +------------+
	| 6LoWPAN HC | | SCHC HC | <-- NEW		| 6LoWPAN HC | | SCHC HC | <-- NEW
	+------------+ +------------+		+------------+ +------------+
	|6LoWPAN Frag| |6LoWPAN Frag|		|6LoWPAN Frag| |6LoWPAN Frag|
	+------------+ +------------+		+------------+ +------------+
	| 802.15.4 | | 802.15.4 |		| 802.15.4 | | 802.15.4 |
	+------------+ +------------+		+------------+ +------------+
	Figure 1: Traditional 6LoWPAN-based protocol stack over IEEE 802.15.4		Figure 1: Traditional 6LoWPAN-based protocol stack over IEEE
	(left) and alternative protocol stack using SCHC for header		802.15.4 (left) and alternative protocol stack using SCHC for
	compression (right). HC and Frag stand for Header Compression and		header compression (right). HC and Frag stand for Header
	Fragmentation, respectively.		Compression and Fragmentation, respectively.
	SCHC header compression may be applied to the headers of different		SCHC header compression may be applied to the headers of different
	protocols or sets of protocols. Some examples include: i) IPv6		protocols or sets of protocols. Some examples include: i) IPv6
	packet headers, ii) joint IPv6 and UDP packet headers, iii) joint		packet headers, ii) joint IPv6 and UDP packet headers, iii) joint
	IPv6, UDP and CoAP packet headers, etc.		IPv6, UDP and CoAP packet headers, etc.
	4. Frame Format		4. Frame Format
	This document defines the frame format to be used when a SCHC-		This document defines the frame format to be used when a SCHC-
	compressed packet is carried over IEEE 802.15.4. Such format is		compressed packet is carried over IEEE 802.15.4. Such format is
	skipping to change at page 5, line 46 ¶		skipping to change at page 5, line 46 ¶
	frame format.		frame format.
	<---------- IEEE 802.15.4 frame payload ---------->		<---------- IEEE 802.15.4 frame payload ---------->
	<----- SCHC Packet ----->		<----- SCHC Packet ----->
	+---------------+-------------+---------+ - - - - +		+---------------+-------------+---------+ - - - - +
	| SCHC Dispatch | SCHC Header | Payload | Padding |		| SCHC Dispatch | SCHC Header | Payload | Padding |
	+---------------+-------------+---------+ - - - - +		+---------------+-------------+---------+ - - - - +
	Figure 2: Encapsulated, SCHC-compressed packet. Padding bits are		Figure 2: Encapsulated, SCHC-compressed packet. Padding bits are
	added if needed.		added if needed.
	4.1. SCHC Dispatch		4.1. SCHC Dispatch
	Adding SCHC header compression to the panoply of header compression		Adding SCHC header compression to the panoply of header compression
	mechanisms used in 6LoWPAN/6Lo environments creates the need to		mechanisms used in 6LoWPAN/6Lo environments creates the need to
	signal when a packet header has been compressed by using SCHC. To		signal when a packet header has been compressed by using SCHC. To
	this end, the present document specifies the SCHC Dispatch. The SCHC		this end, the present document specifies the SCHC Dispatch. The SCHC
	Dispatch indicates that the next field in the frame format is a SCHC-		Dispatch indicates that the next field in the frame format is a SCHC-
	compressed header. The latter corresponds to a packet header that		compressed header (SCHC Header in Figure 2, see 4.2)).
	has been compressed by using SCHC. As defined in [RFC8724], the SCHC
	Header comprises a RuleID, and a compression residue.
	This document defines the SCHC Dispatch as a 6LoWPAN Dispatch Type		This document defines the SCHC Dispatch as a 6LoWPAN Dispatch Type
	for SCHC header compression, based on exploiting RFC 8025 Dispatch		for SCHC header compression [RFC4944]. With the aim to minimize
	type space and the concept of "pages" [RFC8025]. With the aim to		[RFC8025] for the SCHC Dispatch Type:
	minimize overhead, the present document allocates a whole page (Page
	2) for the SCHC Dispatch Type:
	SCHC Dispatch Type bit pattern: 11110010 (Page 2) (Note: to be		SCHC Dispatch Type bit pattern: 01000100 (Page 0) (Note: to be
	confirmed by IANA))		confirmed by IANA))
	TO-DO: RuleID discussion		4.2. SCHC Header
	4.2. Padding		SCHC Header (Figure 2) corresponds to a packet header that has been
			compressed by using SCHC. As defined in [RFC8724], the SCHC Header
			comprises a RuleID, and a compression residue. The present
			specification defines a RuleID size of 8 bits.
			4.3. Padding
	If SCHC header compression leads to a SCHC Packet size of a non-		If SCHC header compression leads to a SCHC Packet size of a non-
	integer number of bytes, padding bits of value equal to zero MUST be		integer number of bytes, padding bits of value equal to zero MUST be
	appended to the SCHC Packet as appropriate to align to an octet		appended to the SCHC Packet as appropriate to align to an octet
	boundary.		boundary.
	5. SCHC compression for IPv6, UDP, and CoAP headers		5. SCHC compression for IPv6, UDP, and CoAP headers
	SCHC header compression may be applied to the headers of different		SCHC header compression may be applied to the headers of different
	protocols or sets of protocols. Some examples include: i) IPv6		protocols or sets of protocols. Some examples include: i) IPv6
	packet headers, ii) joint IPv6 and UDP packet headers, iii) joint		packet headers, ii) joint IPv6 and UDP packet headers, iii) joint
	IPv6, UDP and CoAP packet headers, etc.		IPv6, UDP and CoAP packet headers, etc.
	IPv6 and UDP header fields MUST be compressed as per Section 10 of		5.1. SCHC compression for IPv6 and UDP headers
	RFC 8724.
	TO-DO: adaptation of DevIID and AppIID in 802.15.4 environments		With the exception of IPv6 addresses and UDP ports, IPv6 and UDP
			header fields MUST be compressed as per Section 10 of RFC 8724.
			IPv6 addresses are split into two 64-bit-long fields; one for the
			prefix and one for the Interface Identifier (IID).
			To allow for a single Rule being used for both directions, RFC 8724
			identifies IPv6 addresses and UDP ports by their role (Dev or App)
			and not by their position in the header (source or destination).
			However, such roles are not applicable in some types of 6LoWPAN
			environments (e.g., when a sender and its destination are both nodes
			in a mesh topology network). In such cases, the terms Uplink and
			Downlink as they have been defined in RFC 8724 are not applicable
			either.
			The present specification identifies IPv6 addresses and UDP ports by
			their position in the header (source or destination). Accordingly,
			the present specification defines two new values for the Direction
			Indicator: Transmit (Tx) and Receive (Rx).
			5.1.1. Compression of IPv6 addresses
			Compression of IPv6 source and destination prefixes MUST be performed
			as per Section 10.7.1 of RFC 8724.
			If the source or destination IID are based on an L2 address, then the
			IID can be reconstructed with information coming from the L2 header.
			In that case, the TV is not set, the MO is set to "ignore" and the
			CDA is set to compute-IID.
			As described in [RFC8065], it may be undesirable to build the source
			IPv6 IID of a device out of the device address. Another static value
			is used instead. In that case, the TV contains the static value, the
			MO operator is set to "equal" and the CDA is set to "not-sent".
			If several IIDs are possible, then the TV contains the list of
			possible IIDs, the MO is set to "match-mapping" and the CDA is set to
			"mapping-sent".
			It may also happen that the IID variability only expresses itself on
			a few bytes. In that case, the TV is set to the stable part of the
			IID, the MO is set to "MSB" and the CDA is set to "LSB".
			5.1.2. Compression of UDP ports
			TO-DO
			5.2. SCHC compression for CoAP headers
	CoAP header fields MUST be compressed as per Sections 4 to 6 of RFC		CoAP header fields MUST be compressed as per Sections 4 to 6 of RFC
	8824.		8824.
			5.3. Header compression examples
	TO-DO: provide examples for IPv6-only, IPv6/UDP and IPv6/UDP/CoAP.		TO-DO: provide examples for IPv6-only, IPv6/UDP and IPv6/UDP/CoAP.
	6. Fragmentation and reassembly		6. Fragmentation and reassembly
	After applying SCHC header compression to a packet intended for		After applying SCHC header compression to a packet intended for
	transmission, if the size of the resulting frame format (Section 4)		transmission, if the size of the resulting frame format (Section 4)
	exceeds the IEEE 802.15.4 frame payload space available, such frame		exceeds the IEEE 802.15.4 frame payload space available, such frame
	format MUST be fragmented, carried and reassembled by means of		format MUST be fragmented, carried and reassembled by means of
	6LoWPAN fragmentation and reassembly [RFC4944][RFC8931].		6LoWPAN fragmentation and reassembly [RFC4944][RFC8930][RFC8931].
	7. IANA Considerations		7. IANA Considerations
	This document requests the allocation of the Dispatch Type Field bit		This document requests the allocation of the Dispatch Type Field bit
	pattern 11110010 (Page 2) as SCHC Dispatch Type.		pattern 01000100 (Page 0) as SCHC Dispatch Type.
	8. Security Considerations		8. Security Considerations
	TBD		This document does not define SCHC header compression functionality
			beyond the one defined in RFC 8724. Therefore, the security
			considerations in section 12.1 of RFC 8724 apply.
			As a safety measure, a SCHC decompressor implementing the present
			specification MUST NOT reconstruct a packet larger than 1500 bytes
			[RFC8724].
	9. Acknowledgments		9. Acknowledgments
	Ana Minaburo and Laurent Toutain suggested for the first time the use		Ana Minaburo and Laurent Toutain suggested for the first time the use
	of SCHC in environments where 6LoWPAN has traditionally been used.		of SCHC in environments where 6LoWPAN has traditionally been used.
	Laurent Toutain made comments that helped shape this document.		Laurent Toutain, Pascal Thubert, Dominique Barthel, and Guangpeng Li
			made comments that helped shape this document.
	Carles Gomez has been funded in part by the Spanish Government		Carles Gomez has been funded in part by the Spanish Government
	through project PID2019-106808RA-I00, and by Secretaria		through project PID2019-106808RA-I00, and by Secretaria
	d'Universitats i Recerca del Departament d'Empresa i Coneixement de		d'Universitats i Recerca del Departament d'Empresa i Coneixement de
	la Generalitat de Catalunya 2017 through grant SGR 376.		la Generalitat de Catalunya 2017 through grant SGR 376.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	skipping to change at page 8, line 15 ¶		skipping to change at page 9, line 25 ¶
	[RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained		[RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
	Application Protocol (CoAP)", RFC 7252,		Application Protocol (CoAP)", RFC 7252,
	DOI 10.17487/RFC7252, June 2014,		DOI 10.17487/RFC7252, June 2014,
	<https://www.rfc-editor.org/info/rfc7252>.		<https://www.rfc-editor.org/info/rfc7252>.
	[RFC8025] Thubert, P., Ed. and R. Cragie, "IPv6 over Low-Power		[RFC8025] Thubert, P., Ed. and R. Cragie, "IPv6 over Low-Power
	Wireless Personal Area Network (6LoWPAN) Paging Dispatch",		Wireless Personal Area Network (6LoWPAN) Paging Dispatch",
	RFC 8025, DOI 10.17487/RFC8025, November 2016,		RFC 8025, DOI 10.17487/RFC8025, November 2016,
	<https://www.rfc-editor.org/info/rfc8025>.		<https://www.rfc-editor.org/info/rfc8025>.
			[RFC8065] Thaler, D., "Privacy Considerations for IPv6 Adaptation-
			Layer Mechanisms", RFC 8065, DOI 10.17487/RFC8065,
			February 2017, <https://www.rfc-editor.org/info/rfc8065>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[RFC8724] Minaburo, A., Toutain, L., Gomez, C., Barthel, D., and JC.		[RFC8724] Minaburo, A., Toutain, L., Gomez, C., Barthel, D., and JC.
	Zuniga, "SCHC: Generic Framework for Static Context Header		Zuniga, "SCHC: Generic Framework for Static Context Header
	Compression and Fragmentation", RFC 8724,		Compression and Fragmentation", RFC 8724,
	DOI 10.17487/RFC8724, April 2020,		DOI 10.17487/RFC8724, April 2020,
	<https://www.rfc-editor.org/info/rfc8724>.		<https://www.rfc-editor.org/info/rfc8724>.
	[RFC8824] Minaburo, A., Toutain, L., and R. Andreasen, "Static		[RFC8824] Minaburo, A., Toutain, L., and R. Andreasen, "Static
	Context Header Compression (SCHC) for the Constrained		Context Header Compression (SCHC) for the Constrained
	Application Protocol (CoAP)", RFC 8824,		Application Protocol (CoAP)", RFC 8824,
	DOI 10.17487/RFC8824, June 2021,		DOI 10.17487/RFC8824, June 2021,
	<https://www.rfc-editor.org/info/rfc8824>.		<https://www.rfc-editor.org/info/rfc8824>.
			[RFC8930] Watteyne, T., Ed., Thubert, P., Ed., and C. Bormann, "On
			Forwarding 6LoWPAN Fragments over a Multi-Hop IPv6
			Network", RFC 8930, DOI 10.17487/RFC8930, November 2020,
			<https://www.rfc-editor.org/info/rfc8930>.
	[RFC8931] Thubert, P., Ed., "IPv6 over Low-Power Wireless Personal		[RFC8931] Thubert, P., Ed., "IPv6 over Low-Power Wireless Personal
	Area Network (6LoWPAN) Selective Fragment Recovery",		Area Network (6LoWPAN) Selective Fragment Recovery",
	RFC 8931, DOI 10.17487/RFC8931, November 2020,		RFC 8931, DOI 10.17487/RFC8931, November 2020,
	<https://www.rfc-editor.org/info/rfc8931>.		<https://www.rfc-editor.org/info/rfc8931>.
	10.2. Informative References		10.2. Informative References
	[I-D.toutain-6lo-6lo-and-schc]		[I-D.toutain-6lo-6lo-and-schc]
	Minaburo, A. and L. Toutain, "Comparison of 6lo and SCHC",		Minaburo, A. and L. Toutain, "Comparison of 6lo and SCHC",
	draft-toutain-6lo-6lo-and-schc-00 (work in progress),		Work in Progress, Internet-Draft, draft-toutain-6lo-6lo-
	November 2019.		and-schc-00, 4 November 2019,
			<https://www.ietf.org/archive/id/draft-toutain-6lo-6lo-
			and-schc-00.txt>.
	[RFC9006] Gomez, C., Crowcroft, J., and M. Scharf, "TCP Usage		[RFC9006] Gomez, C., Crowcroft, J., and M. Scharf, "TCP Usage
	Guidance in the Internet of Things (IoT)", RFC 9006,		Guidance in the Internet of Things (IoT)", RFC 9006,
	DOI 10.17487/RFC9006, March 2021,		DOI 10.17487/RFC9006, March 2021,
	<https://www.rfc-editor.org/info/rfc9006>.		<https://www.rfc-editor.org/info/rfc9006>.
	Authors' Addresses		Authors' Addresses
	Carles Gomez		Carles Gomez
	UPC		UPC
	C/Esteve Terradas, 7		C/Esteve Terradas, 7
	Castelldefels 08860		08860 Castelldefels
	Spain		Spain
	Email: carlesgo@entel.upc.edu		Email: carlesgo@entel.upc.edu
	Ana Minaburo		Ana Minaburo
	Acklio		Acklio
	1137A avenue des Champs Blancs		1137A avenue des Champs Blancs
	Cesson-Sevigne Cedex 35510		35510 Cesson-Sevigne Cedex
	France		France
	Email: ana@ackl.io		Email: ana@ackl.io
End of changes. 32 change blocks.
	57 lines changed or deleted		129 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/