< draft-ietf-6lo-dispatch-iana-registry-02.txt		draft-ietf-6lo-dispatch-iana-registry-03.txt >
	6lo S. Chakrabarti		6lo S. Chakrabarti
	Internet-Draft Ericsson		Internet-Draft Ericsson
	Updates: 4944, 6282 (if approved) G. Montenegro		Updates: 4944, 6282 (if approved) G. Montenegro
	Intended status: Standards Track Microsoft		Intended status: Standards Track Microsoft
	Expires: September 22, 2016 R. Droms		Expires: October 9, 2016 R. Droms
	Cisco		Cisco
	J. Woodyatt		J. Woodyatt
	Nest		Nest
	March 21, 2016		April 7, 2016
	IANA Registry for 6lowpan ESC Dispatch Code points		IANA Registry for 6lowpan ESC Dispatch Code points
	draft-ietf-6lo-dispatch-iana-registry-02		draft-ietf-6lo-dispatch-iana-registry-03
	Abstract		Abstract
	RFC4944 defines ESC dispatch type for additional dispatch bytes in		RFC4944 defines ESC dispatch type for additional dispatch bytes in
	the 6lowpan header. The value of ESC byte has been updated by		the 6lowpan header. The value of ESC byte has been updated by
	RFC6282. However, the usage of ESC extension byte has not been		RFC6282. However, the usage of ESC extension byte has not been
	defined in RFC6282 and RFC4944. The purpose of this document is to		defined in RFC6282 and RFC4944. The purpose of this document is to
	define the ESC extension byte code points and to request		define the ESC extension byte code points and to request
	corresponding IANA actions.		corresponding IANA actions.
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	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 September 22, 2016.		This Internet-Draft will expire on October 9, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 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
	skipping to change at page 4, line 9 ¶		skipping to change at page 4, line 9 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 1: Frame Format with ESC Byte		Figure 1: Frame Format with ESC Byte
	ESC: The left-most byte is the ESC dispatch type containing '0100000'		ESC: The left-most byte is the ESC dispatch type containing '0100000'
	ESC Extension Type (EET): It is the first byte following the ESC		ESC Extension Type (EET): It is the first byte following the ESC
	byte. Extension type defines the payload for the additional dispatch		byte. Extension type defines the payload for the additional dispatch
	bytes. The values are from 0 to 255. Value 0 and 255 are reserved		bytes. The values are from 0 to 255. Value 0 and 255 are reserved
	for future use. These values are assigned by IANA. The EET values		for future use. These values are assigned by IANA. The EET values
	are similar to dispatch values in the 6lowpan header except they are		are similar to dispatch values in the 6lowpan header except they are
	preceeded by the ESC byte. Thus, ESC extension types and dispatch		preceded by the ESC byte. Thus, ESC extension types and dispatch
	values are using orthogonal code spaces. Though not desirable,		values are using orthogonal code spaces. Though not desirable,
	multiple ESC bytes MAY appear in a 6lowpan header. Section 3.1		multiple ESC bytes MAY appear in a 6lowpan header. Section 3.1
	describes how to handle unknown ESC dispatch type.		describes how to handle unknown ESC dispatch type.
	Extended Dispatch Payload(EDP): This part of frame format must be		Extended Dispatch Payload(EDP): This part of frame format must be
	defined by the corresponding extension type. A specification is		defined by the corresponding extension type. A specification is
	required to define each usage of extension type and its corresponding		required to define each usage of extension type and its corresponding
	Extension Payload. For the sake of interoperability, specifications		Extension Payload. For the sake of interoperability, specifications
	of extension bytes MUST NOT redefine the existing ESC Extension Type		of extension bytes MUST NOT redefine the existing ESC Extension Type
	codes.		codes.
	skipping to change at page 4, line 31 ¶		skipping to change at page 4, line 31 ¶
	Section 5.1 in RFC4944 indicates that the Extension Type field may		Section 5.1 in RFC4944 indicates that the Extension Type field may
	contain additional dispatch values larger than 63, as corrected by		contain additional dispatch values larger than 63, as corrected by
	[4944-ERRATA]. For the sake of interoperability, the new dispatch		[4944-ERRATA]. For the sake of interoperability, the new dispatch
	type (EET) MUST NOT modify the behavior of existing dispatch types		type (EET) MUST NOT modify the behavior of existing dispatch types
	[RFC4944].		[RFC4944].
	3.1. Interaction with other RFC4944 implementations		3.1. Interaction with other RFC4944 implementations
	It is expected that RFC4944 existing implementations are not capable		It is expected that RFC4944 existing implementations are not capable
	of processing ESC extension data bytes as defined in this document.		of processing ESC extension data bytes as defined in this document.
	However, implementors have to assume that existing implementation		However, implementers have to assume that existing implementation
	that attempt to process an EET unknown to them will simply drop the		that attempt to process an EET unknown to them will simply drop the
	packet or ignore the ESC dispatch bytes.		packet or ignore the ESC dispatch bytes.
	If an implementation following this document, during processing of		If an implementation following this document, during processing of
	the received packet reaches the ESC byte for which it does not		the received packet reaches the ESC byte for which it does not
	understand the extension bytes (EET), it MUST drop that packet.		understand the extension bytes (EET), it MUST drop that packet.
	However, it is important to clarify that a router node SHOULD forward		However, it is important to clarify that a router node SHOULD forward
	a 6lowpan packet with the EET bytes as long as it does not attempt to		a 6lowpan packet with the EET bytes as long as it does not attempt to
	process any unknown ESC extension bytes.		process any unknown ESC extension bytes.
	skipping to change at page 5, line 11 ¶		skipping to change at page 5, line 11 ¶
	higher chance there is that a legacy node will recognize and		higher chance there is that a legacy node will recognize and
	successfully process some dispatch type [RFC4944] before the EET and		successfully process some dispatch type [RFC4944] before the EET and
	then ignore the EET instead of dropping the entire packet.		then ignore the EET instead of dropping the entire packet.
	3.2. ESC Extension Bytes Typical Sequence		3.2. ESC Extension Bytes Typical Sequence
	ESC Extension bytes sequence and order with respect to 6LoWPAN Mesh		ESC Extension bytes sequence and order with respect to 6LoWPAN Mesh
	header and LoWPAN_IPHC header are described below. When LOWPAN_IPHC		header and LoWPAN_IPHC header are described below. When LOWPAN_IPHC
	dispatch type is present, ESC bytes MUST appear before the		dispatch type is present, ESC bytes MUST appear before the
	LOWPAN_IPHC dispatch type in order to maintain backward compatibility		LOWPAN_IPHC dispatch type in order to maintain backward compatibility
	with RFC 8262 section 3.2. The following diagrams provide examples		with RFC6282 section 3.2. The following diagrams provide examples of
	of ESC extension byte usages:		ESC extension byte usages:
	A LoWPAN encapsulated IPv6 Header compressed packet:		A LoWPAN encapsulated IPv6 Header compressed packet:
	+-------+------+--------+--------+-----------------+--------+		+-------+------+--------+--------+-----------------+--------+
	| ESC | EET | EDP |Dispatch| LOWPAN_IPHC hdr | Payld |		| ESC | EET | EDP |Dispatch| LOWPAN_IPHC hdr | Payld |
	+-------+------+--------+--------+-----------------+--------+		+-------+------+--------+--------+-----------------+--------+
	A LoWPAN_IPHC Header, Mesh header and an ESC extenstion byte:		A LoWPAN_IPHC Header, Mesh header and an ESC extension byte:
	+-----+-----+-----+----+------+-------+---------------+------+		+-----+-----+-----+----+------+-------+---------------+------+
	|M typ| Mhdr| ESC | EET|EDP |Disptch|LOWPAN_IPHC hdr| Payld|		|M typ| Mhdr| ESC | EET|EDP |Disptch|LOWPAN_IPHC hdr| Payld|
	+-----+-----+-----+----+------+-------+---------------+------+		+-----+-----+-----+----+------+-------+---------------+------+
	A Mesh header with ESC bytes		A Mesh header with ESC bytes
	+-------+-------+-----+-----+-------+		+-------+-------+-----+-----+-------+
	| M Typ | M Hdr | ESC | EET |EDP |		| M Typ | M Hdr | ESC | EET |EDP |
	+-------+-------+-----+-----+-------+		+-------+-------+-----+-----+-------+
	skipping to change at page 5, line 48 ¶		skipping to change at page 5, line 48 ¶
	+--------+--------+--------+		+--------+--------+--------+
	| ESC | EET | EDP |		| ESC | EET | EDP |
	+--------+--------+--------+		+--------+--------+--------+
	Figure 2: A 6lowpan packet with ESC Bytes		Figure 2: A 6lowpan packet with ESC Bytes
	3.3. ITU-T G.9903 ESC type usage		3.3. ITU-T G.9903 ESC type usage
	The ESC dispatch type is used in [G3-PLC] to provide native mesh		The ESC dispatch type is used in [G3-PLC] to provide native mesh
	header and bootstrapping functionalities. The ITU-T recommendation		routing and bootstrapping functionalities. The ITU-T recommendation
	defines command IDs in the [G3-PLC] section 9.4.2.3 which operates		defines command IDs in the [G3-PLC] section 9.4.2.3 which operates
	like ESC Extension type field. The command ID values are 0x01 to		like ESC Extension type field. The command ID values are 0x01 to
	0x1F.		0x1F.
	The frame format is defined as follows:		The frame format is defined as follows:
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|0 1| ESC | Command ID | Command Payload		|0 1| ESC | Command ID | Command Payload
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
End of changes. 9 change blocks.
	10 lines changed or deleted		10 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/