< draft-ietf-lpwan-coap-static-context-hc-17.txt		draft-ietf-lpwan-coap-static-context-hc-18.txt >
	lpwan Working Group A. Minaburo		lpwan Working Group A. Minaburo
	Internet-Draft Acklio		Internet-Draft Acklio
	Intended status: Standards Track L. Toutain		Intended status: Standards Track L. Toutain
	Expires: July 25, 2021 Institut MINES TELECOM; IMT Atlantique		Expires: July 25, 2021 Institut MINES TELECOM; IMT Atlantique
	R. Andreasen		R. Andreasen
	Universidad de Buenos Aires		Universidad de Buenos Aires
	January 21, 2021		January 21, 2021
	LPWAN Static Context Header Compression (SCHC) for CoAP		LPWAN Static Context Header Compression (SCHC) for CoAP
	draft-ietf-lpwan-coap-static-context-hc-17		draft-ietf-lpwan-coap-static-context-hc-18
	Abstract		Abstract
	This draft defines how to compress the Constrained Application		This draft defines how to compress the Constrained Application
	Protocol (CoAP) using the Static Context Header Compression (SCHC).		Protocol (CoAP) using the Static Context Header Compression (SCHC).
	SCHC is a header compression mechanism adapted for Constrained		SCHC is a header compression mechanism adapted for Constrained
	Devices. SCHC uses a static description of the header to reduce the		Devices. SCHC uses a static description of the header to reduce the
	header's redundancy and size. While RFC 8724 describes the SCHC		header's redundancy and size. While RFC 8724 describes the SCHC
	compression and fragmentation framework, and its application for		compression and fragmentation framework, and its application for
	IPv6/UDP headers, this document applies SCHC for CoAP headers. The		IPv6/UDP headers, this document applies SCHC for CoAP headers. The
	skipping to change at page 5, line 4 ¶		skipping to change at page 5, line 4 ¶
	2. SCHC Applicability to CoAP		2. SCHC Applicability to CoAP
	SCHC Compression for CoAP header MAY be done in conjunction with the		SCHC Compression for CoAP header MAY be done in conjunction with the
	lower layers (IPv6/UDP) or independently. The SCHC adaptation		lower layers (IPv6/UDP) or independently. The SCHC adaptation
	layers, described in Section 5 of [RFC8724], may be used as shown in		layers, described in Section 5 of [RFC8724], may be used as shown in
	Figure 1, Figure 2, and Figure 3.		Figure 1, Figure 2, and Figure 3.
	In the first example, Figure 1, a Rule compresses the complete header		In the first example, Figure 1, a Rule compresses the complete header
	stack from IPv6 to CoAP. In this case, the Device and the NGW		stack from IPv6 to CoAP. In this case, the Device and the NGW
	perform SCHC C/D (Static Context Header Compression Compressor/		perform SCHC C/D (Static Context Header Compression Compressor/
	Decompressor). The host communicating with the Device does not		Decompressor). The Application communicating with the Device does
	implement SCHC C/D.		not implement SCHC C/D.
	(Device) (NGW) (App)		(Device) (NGW) (App)
	+--------+ +--------+		+--------+ +--------+
	| CoAP | | CoAP |		| CoAP | | CoAP |
	+--------+ +--------+		+--------+ +--------+
	| UDP | | UDP |		| UDP | | UDP |
	+--------+ +----------------+ +--------+		+--------+ +----------------+ +--------+
	| IPv6 | | IPv6 | | IPv6 |		| IPv6 | | IPv6 | | IPv6 |
	+--------+ +--------+-------+ +--------+		+--------+ +--------+-------+ +--------+
End of changes. 2 change blocks.
	3 lines changed or deleted		3 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/