< draft-ietf-6lo-dispatch-iana-registry-05.txt		draft-ietf-6lo-dispatch-iana-registry-06.txt >
	6lo S. Chakrabarti		6lo S. Chakrabarti
	Internet-Draft Ericsson		Internet-Draft
	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: March 20, 2017 R. Droms		Expires: May 20, 2017 R. Droms
	Cisco
	J. Woodyatt		J. Woodyatt
	Nest		Nest
	September 16, 2016		November 16, 2016
	6lowpan ESC Dispatch Code Points and Guidelines		6lowpan ESC Dispatch Code Points and Guidelines
	draft-ietf-6lo-dispatch-iana-registry-05		draft-ietf-6lo-dispatch-iana-registry-06
	Abstract		Abstract
	RFC4944 defines the ESC dispatch type to allow for additional		RFC4944 defines the ESC dispatch type to allow for additional
	dispatch bytes in the 6lowpan header. The value of the ESC byte was		dispatch bytes in the 6lowpan header. The value of the ESC byte was
	updated by RFC6282, however, its usage was not defined either in		updated by RFC6282, however, its usage was not defined either in
	RFC6282 or in RFC4944. This document updates RFC4944 and RFC6282 by		RFC6282 or in RFC4944. This document updates RFC4944 and RFC6282 by
	defining the ESC extension byte code points including registration of		defining the ESC extension byte code points including registration of
	entries for known use cases at the time of writing of this document.		entries for known use cases at the time of writing of this document.
	skipping to change at page 1, line 39 ¶		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 March 20, 2017.		This Internet-Draft will expire on May 20, 2017.
	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 3, line 47 ¶		skipping to change at page 3, line 47 ¶
	octets are left unstructured for the specific use of the extension		octets are left unstructured for the specific use of the extension
	type:		type:
	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 | ESC EXT Type | Extended Dispatch Payload		|0 1| ESC | ESC EXT Type | Extended Dispatch Payload
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	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
			'01000000'
	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. Values 0 and 255 are reserved		bytes. The values are from 0 to 255. Values 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
	preceded 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 an unknown ESC dispatch type.		describes how to handle an unknown ESC dispatch type.
	skipping to change at page 8, line 43 ¶		skipping to change at page 8, line 43 ¶
	[G3-PLC] "http://www.itu.int/rec/T-REC-G.9903-201402-I".		[G3-PLC] "http://www.itu.int/rec/T-REC-G.9903-201402-I".
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,		IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	DOI 10.17487/RFC5226, May 2008,		DOI 10.17487/RFC5226, May 2008,
	<http://www.rfc-editor.org/info/rfc5226>.		<http://www.rfc-editor.org/info/rfc5226>.
	Authors' Addresses		Authors' Addresses
	Samita Chakrabarti		Samita Chakrabarti
	Ericsson
	300 Holger Way
	San Jose, CA		San Jose, CA
	USA		USA
	Email: samitac.ietf@gmail.com		Email: samitac.ietf@gmail.com
	Gabriel Montenegro		Gabriel Montenegro
	Microsoft		Microsoft
	USA		USA
	Email: gabriel.montenegro@microsoft.com		Email: gabriel.montenegro@microsoft.com
	Ralph Droms		Ralph Droms
	Cisco
	USA		USA
	Email: rdroms.ietf@gmail.com		Email: rdroms@gmail.com
	James Woodyatt		James Woodyatt
	Nest		Nest
	Mountain View, CA		Mountain View, CA
	USA		USA
	Email: jhw@netstlabs.com		Email: jhw@netstlabs.com
End of changes. 10 change blocks.
	11 lines changed or deleted		11 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/