< draft-ietf-6lo-paging-dispatch-02.txt		draft-ietf-6lo-paging-dispatch-03.txt >
	6lo P. Thubert, Ed.		6lo P. Thubert, Ed.
	Internet-Draft Cisco		Internet-Draft Cisco
	Updates: 4944 (if approved) R. Cragie		Updates: 4944 (if approved) R. Cragie
	Intended status: Standards Track ARM		Intended status: Standards Track ARM
	Expires: January 19, 2017 July 18, 2016		Expires: January 21, 2017 July 20, 2016
	6LoWPAN Paging Dispatch		6LoWPAN Paging Dispatch
	draft-ietf-6lo-paging-dispatch-02		draft-ietf-6lo-paging-dispatch-03
	Abstract		Abstract
	This specification introduces a new context switch mechanism for		This specification updates RFC 4944 to introduce a new context switch
	6LoWPAN compression, expressed in terms of Pages and signaled by a		mechanism for 6LoWPAN compression, expressed in terms of Pages and
	new Paging Dispatch.		signaled by a new Paging Dispatch.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	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 January 19, 2017.		This Internet-Draft will expire on January 21, 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 5, line 18 ¶		skipping to change at page 5, line 18 ¶
	from 11 110000 through 11 111111 and represent Page Numbers 0 through		from 11 110000 through 11 111111 and represent Page Numbers 0 through
	15 as discussed in this document.		15 as discussed in this document.
	6.2. New Per-Page Dispatch Type registries		6.2. New Per-Page Dispatch Type registries
	This document creates 15 new IANA registries for the Per-Page		This document creates 15 new IANA registries for the Per-Page
	Dispatch type fields, indexed by Page Number, 1 to 15. Each Registry		Dispatch type fields, indexed by Page Number, 1 to 15. Each Registry
	corresponds to a bit-field of one octet.		corresponds to a bit-field of one octet.
	Future assignments in these registries are to be coordinated via IANA		Future assignments in these registries are to be coordinated via IANA
	under the policy of "Specification Required" [RFC2434]. It is		under the policy of "Specification Required" [RFC5226]. It is
	expected that this policy will allow for other (non-IETF)		expected that this policy will allow for other (non-IETF)
	organizations to more easily obtain assignments.		organizations to more easily obtain assignments.
	These registries extend the Dispatch type field registry that was		These registries extend the Dispatch type field registry that was
	created for [RFC4944], which is considered as the registry for Page		created for [RFC4944], which is considered as the registry for Page
	0.		0.
	As described above, this document allocates in the registry		As described above, this document allocates in the registry
	associated to Page 1 the Per-Page Dispatch type field values that are		associated to Page 1 the Per-Page Dispatch type field values that are
	allocated in the Dispatch type field for LOWPAN_IPHC by [RFC6282].		allocated in the Dispatch type field for LOWPAN_IPHC by [RFC6282].
	skipping to change at page 5, line 48 ¶		skipping to change at page 5, line 48 ¶
	the design in the 6lo Working Group.		the design in the 6lo Working Group.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[IEEE802154]		[IEEE802154]
	IEEE standard for Information Technology, "IEEE std.		IEEE standard for Information Technology, "IEEE std.
	802.15.4, Part. 15.4: Wireless Medium Access Control (MAC)		802.15.4, Part. 15.4: Wireless Medium Access Control (MAC)
	and Physical Layer (PHY) Specifications for Low-Rate		and Physical Layer (PHY) Specifications for Low-Rate
	Wireless Personal Area Networks", 2015.		Wireless Personal Area Networks".
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://www.rfc-editor.org/info/rfc2119>.
	[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", RFC 2434,
	DOI 10.17487/RFC2434, October 1998,
	<http://www.rfc-editor.org/info/rfc2434>.
	[RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,		[RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,
	"Transmission of IPv6 Packets over IEEE 802.15.4		"Transmission of IPv6 Packets over IEEE 802.15.4
	Networks", RFC 4944, DOI 10.17487/RFC4944, September 2007,		Networks", RFC 4944, DOI 10.17487/RFC4944, September 2007,
	<http://www.rfc-editor.org/info/rfc4944>.		<http://www.rfc-editor.org/info/rfc4944>.
			[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
			IANA Considerations Section in RFCs", BCP 26, RFC 5226,
			DOI 10.17487/RFC5226, May 2008,
			<http://www.rfc-editor.org/info/rfc5226>.
	[RFC6282] Hui, J., Ed. and P. Thubert, "Compression Format for IPv6		[RFC6282] Hui, J., Ed. and P. Thubert, "Compression Format for IPv6
	Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,		Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,
	DOI 10.17487/RFC6282, September 2011,		DOI 10.17487/RFC6282, September 2011,
	<http://www.rfc-editor.org/info/rfc6282>.		<http://www.rfc-editor.org/info/rfc6282>.
	8.2. Informative References		8.2. Informative References
	[RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and		[RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and
	Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January		Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January
	2014, <http://www.rfc-editor.org/info/rfc7102>.		2014, <http://www.rfc-editor.org/info/rfc7102>.
End of changes. 8 change blocks.
	13 lines changed or deleted		13 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/