< draft-ietf-lpwan-schc-over-nbiot-01.txt		draft-ietf-lpwan-schc-over-nbiot-02.txt >
	lpwan Working Group E. Ramos		lpwan Working Group E. Ramos
	Internet-Draft Ericsson		Internet-Draft Ericsson
	Intended status: Informational A. Minaburo		Intended status: Informational A. Minaburo
	Expires: May 19, 2020 Acklio		Expires: November 18, 2020 Acklio
	November 16, 2019		May 17, 2020
	SCHC over NB-IoT		SCHC over NB-IoT
	draft-ietf-lpwan-schc-over-nbiot-01		draft-ietf-lpwan-schc-over-nbiot-02
	Abstract		Abstract
	The Static Context Header Compression (SCHC) specification describes		The Static Context Header Compression (SCHC) specification describes
	a header compression and fragmentation functionalities for LPWAN (Low		a header compression and fragmentation functionalities for LPWAN (Low
	Power Wide Area Networks) technologies. SCHC was designed to be		Power Wide Area Networks) technologies. SCHC was designed to be
	adapted over any of the LPWAN technologies.		adapted over any of the LPWAN technologies.
	This document describes the use of SCHC over the NB-IoT wireless		This document describes the use of SCHC over the NB-IoT wireless
	access, and provides elements for an efficient parameterization.		access, and provides elements for an efficient parameterization.
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 May 19, 2020.		This Internet-Draft will expire on November 18, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 2, line 35 ¶		skipping to change at page 2, line 35 ¶
	6. Non-IP based Data Transmission . . . . . . . . . . . . . . . 12		6. Non-IP based Data Transmission . . . . . . . . . . . . . . . 12
	6.1. SCHC Entities Placing . . . . . . . . . . . . . . . . . . 12		6.1. SCHC Entities Placing . . . . . . . . . . . . . . . . . . 12
	6.2. Parameters for Static Context Header Compression . . . . 13		6.2. Parameters for Static Context Header Compression . . . . 13
	6.2.1. SCHC Context initialization . . . . . . . . . . . . . 13		6.2.1. SCHC Context initialization . . . . . . . . . . . . . 13
	6.2.2. SCHC Rules . . . . . . . . . . . . . . . . . . . . . 13		6.2.2. SCHC Rules . . . . . . . . . . . . . . . . . . . . . 13
	6.2.3. Rule ID . . . . . . . . . . . . . . . . . . . . . . . 14		6.2.3. Rule ID . . . . . . . . . . . . . . . . . . . . . . . 14
	6.2.4. SCHC MAX_PACKET_SIZE . . . . . . . . . . . . . . . . 14		6.2.4. SCHC MAX_PACKET_SIZE . . . . . . . . . . . . . . . . 14
	6.3. Fragmentation . . . . . . . . . . . . . . . . . . . . . . 14		6.3. Fragmentation . . . . . . . . . . . . . . . . . . . . . . 14
	6.3.1. Fragmentation modes . . . . . . . . . . . . . . . . . 14		6.3.1. Fragmentation modes . . . . . . . . . . . . . . . . . 14
	6.3.2. Fragmentation Parameters(TBD) . . . . . . . . . . . . 14		6.3.2. Fragmentation Parameters(TBD) . . . . . . . . . . . . 14
	7. Padding . . . . . . . . . . . . . . . . . . . . . . . . . . . 15		7. Padding . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
	8. Security considerations . . . . . . . . . . . . . . . . . . . 15		8. Security considerations . . . . . . . . . . . . . . . . . . . 16
	9. 3GPP References . . . . . . . . . . . . . . . . . . . . . . . 15		9. 3GPP References . . . . . . . . . . . . . . . . . . . . . . . 16
	10. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . 16		10. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . 17
	10.1. NB-IoT User Plane protocol architecture . . . . . . . . 16		10.1. NB-IoT User Plane protocol architecture . . . . . . . . 17
	10.1.1. Packet Data Convergence Protocol (PDCP) . . . . . . 16		10.1.1. Packet Data Convergence Protocol (PDCP) . . . . . . 17
	10.1.2. Radio Link Protocol (RLC) . . . . . . . . . . . . . 16		10.1.2. Radio Link Protocol (RLC) . . . . . . . . . . . . . 17
	10.1.3. Medium Access Control (MAC) . . . . . . . . . . . . 17		10.1.3. Medium Access Control (MAC) . . . . . . . . . . . . 18
	10.2. NB-IoT Data over NAS (DoNAS) . . . . . . . . . . . . . . 18		10.2. NB-IoT Data over NAS (DoNAS) . . . . . . . . . . . . . . 19
	11. Informative References . . . . . . . . . . . . . . . . . . . 21		11. Informative References . . . . . . . . . . . . . . . . . . . 22
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
	1. Introduction		1. Introduction
	The Static Context Header Compression (SCHC)		The Static Context Header Compression (SCHC)
	[I-D.ietf-lpwan-ipv6-static-context-hc] defines a header compression		[RFC8724] defines a header compression
	scheme and fragmentation functionality, both specially tailored for		scheme and fragmentation functionality, both specially tailored for
	Low Power Wide Area Networks (LPWAN) networks defined in [RFC8376].		Low Power Wide Area Networks (LPWAN) networks defined in [RFC8376].
	Header compression is needed to efficiently bring Internet		Header compression is needed to efficiently bring Internet
	connectivity to the node within an NB-IoT network. SCHC uses a		connectivity to the node within an NB-IoT network. SCHC uses a
	static context to performs header compression with specific		static context to performs header compression with specific
	parameters that need to be adapted into the NB-IoT wireless access.		parameters that need to be adapted into the NB-IoT wireless access.
	This document assumes functionality for NB-IoT of 3GPP release 15		This document assumes functionality for NB-IoT of 3GPP release 15
	otherwise other versions functionality is explicitly mentioned in the		otherwise other versions functionality is explicitly mentioned in the
	text.		text.
	This document describes the use of SCHC and its parameterizing over		This document describes the use of SCHC and its parameterizing over
	the NB-IoT wireless access.		the NB-IoT wireless access.
	2. Terminology		2. Terminology
	This document will follow the terms defined in		This document will follow the terms defined in
	[I-D.ietf-lpwan-ipv6-static-context-hc], in [RFC8376], and the		[RFC8724], in [RFC8376], and the
	[TGPP23720].		[TGPP23720].
	o CIoT. Cellular IoT		o CIoT. Cellular IoT
	o C-SGN. CIoT Serving Gateway Node		o C-SGN. CIoT Serving Gateway Node
	o UE. User Equipment		o UE. User Equipment
	o eNB. Node B. Base Station that controls the UE		o eNB. Node B. Base Station that controls the UE
	skipping to change at page 14, line 50 ¶		skipping to change at page 14, line 50 ¶
	end-to-end if no transport protocol takes care of retransmission. To		end-to-end if no transport protocol takes care of retransmission. To
	achieve this, the packets fragmentation is activated with the ACK-on-		achieve this, the packets fragmentation is activated with the ACK-on-
	Error mode enabled. In some cases, it is even desirable to keep		Error mode enabled. In some cases, it is even desirable to keep
	track of all the SCHC packets delivered, in that case, the		track of all the SCHC packets delivered, in that case, the
	fragmentation function could be active for all packets transmitted by		fragmentation function could be active for all packets transmitted by
	the applications (SCHC MAX_PACKET_SIZE == 1 Byte) and the ACK-on-		the applications (SCHC MAX_PACKET_SIZE == 1 Byte) and the ACK-on-
	Error mode.		Error mode.
	6.3.2. Fragmentation Parameters(TBD)		6.3.2. Fragmentation Parameters(TBD)
	o Rule ID		o Rule ID. The Fragmentation Rule ID is given when choosing the
			profile according to the fragmentation mode require. 1 bit can be
			used to recognize each mode.
	o DTag		o DTag.
	o FCN
	o W (number of bits)		No_ACK. May take 1 bit.
			ACK_on_Error. May take 1 bit.
			o FCN (N value).
			No_ACK. The value of N is 1.
			ACK_on_Error. The value of N depends on the
			o W (M value)
			No_ACK. This field is not used in this mode
			ACK_on_Error.
	o WINDOW_SIZE		o WINDOW_SIZE
			No_ACK. This mode does not use windows
			ACK_on_Error.
	o Retransmission Timer		o Retransmission Timer
			No_ACK. This timmer is not used in this mode
			ACK_on_Error. This timer needs to be set to 1h or 10h
	o Inactivity Timer		o Inactivity Timer
	o MAX_ACK_Retries		No_ACK. Must be maintained and needs to be bigger than 1h or 10h
	o MAX_ATTEMPS		ACK_on_Error. Must be bigger than 1h or 10h
			o MAX_ACK_REQUESTS
			No_ACK. Not used in this mode.
			ACK_on_Error.
	o MIC (size and algorithm)		o MIC (size and algorithm)
			No_ACK.
			ACK_on_Error.
			o RCS
			No_ACK
			ACK_on_Error.
			o Tiles size
			No_ACK. Not used in this mode.
			ACK_on_Error. (also mention if the last tile is carried in a
			regular fragment or in All-1 fragment)
	7. Padding		7. Padding
	NB-IoT and 3GPP wireless access, in general, assumes byte aligned		NB-IoT and 3GPP wireless access, in general, assumes byte aligned
	payload. Therefore the L2 word for NB-IoT MUST be considered 8 bits		payload. Therefore the L2 word for NB-IoT MUST be considered 8 bits
	and the treatment of padding should use this value accordingly.		and the treatment of padding should use this value accordingly.
	8. Security considerations		8. Security considerations
	3GPP access security is specified in (TGPP33203).		3GPP access security is specified in (TGPP33203).
	skipping to change at page 21, line 37 ¶		skipping to change at page 22, line 37 ¶
	MAC |MAC |RLC | RLC ||MAC |RLC | RLC ||MAC | RLC |Pad|		MAC |MAC |RLC | RLC ||MAC |RLC | RLC ||MAC | RLC |Pad|
	|Head|Head| PAYLOAD ||Head |Head| PAYLOAD ||Head| PDU | |		|Head|Head| PAYLOAD ||Head |Head| PAYLOAD ||Head| PDU | |
	+----+----+----------++-----+----+---------++----+---------+---+		+----+----+----------++-----+----+---------++----+---------+---+
	TB1 TB2 TB3		TB1 TB2 TB3
	Figure 8: Example of User Plane packet encapsulation for Data over		Figure 8: Example of User Plane packet encapsulation for Data over
	NAS		NAS
	11. Informative References		11. Informative References
	[I-D.ietf-lpwan-ipv6-static-context-hc]		[RFC8724] Minaburo, A., Toutain, L., Gomez, C., Barthel, D., and J.
	Minaburo, A., Toutain, L., Gomez, C., Barthel, D., and J.		Zuniga, "SCHC: Generic Framework for Static Context Header
	Zuniga, "Static Context Header Compression (SCHC) and		Compression and Fragmentation", April 2020,
	fragmentation for LPWAN, application to UDP/IPv6", draft-		<https://www.rfc-editor.org/infor/rfc8724>.
	ietf-lpwan-ipv6-static-context-hc-22 (work in progress),
	October 2019.
	[RFC5795] Sandlund, K., Pelletier, G., and L-E. Jonsson, "The RObust		[RFC5795] Sandlund, K., Pelletier, G., and L-E. Jonsson, "The RObust
	Header Compression (ROHC) Framework", RFC 5795,		Header Compression (ROHC) Framework", RFC 5795,
	DOI 10.17487/RFC5795, March 2010, <https://www.rfc-		DOI 10.17487/RFC5795, March 2010, <https://www.rfc-
	editor.org/info/rfc5795>.		editor.org/info/rfc5795>.
	[RFC8376] Farrell, S., Ed., "Low-Power Wide Area Network (LPWAN)		[RFC8376] Farrell, S., Ed., "Low-Power Wide Area Network (LPWAN)
	Overview", RFC 8376, DOI 10.17487/RFC8376, May 2018,		Overview", RFC 8376, DOI 10.17487/RFC8376, May 2018,
	<https://www.rfc-editor.org/info/rfc8376>.		<https://www.rfc-editor.org/info/rfc8376>.
End of changes. 16 change blocks.
	30 lines changed or deleted		74 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/