< draft-ietf-6lo-paging-dispatch-01.txt		draft-ietf-6lo-paging-dispatch-02.txt >
	6lo P. Thubert, Ed.		6lo P. Thubert, Ed.
	Internet-Draft Cisco		Internet-Draft Cisco
	Updates: 4944 (if approved) January 15, 2016		Updates: 4944 (if approved) R. Cragie
	Intended status: Standards Track		Intended status: Standards Track ARM
	Expires: July 18, 2016		Expires: January 19, 2017 July 18, 2016
	6LoWPAN Paging Dispatch		6LoWPAN Paging Dispatch
	draft-ietf-6lo-paging-dispatch-01		draft-ietf-6lo-paging-dispatch-02
	Abstract		Abstract
	This specification introduces a new context switch mechanism for		This specification introduces a new context switch mechanism for
	6LoWPAN compression, expressed in terms of Pages and signaled by a		6LoWPAN compression, expressed in terms of Pages and signaled by a
	new Paging Dispatch.		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
	skipping to change at page 1, line -137 ¶		skipping to change at page 1, line -137 ¶
	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 July 18, 2016.		This Internet-Draft will expire on January 19, 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 2, line 19 ¶		skipping to change at page 2, line 19 ¶
	3. Updating RFC 4944 . . . . . . . . . . . . . . . . . . . . . . 3		3. Updating RFC 4944 . . . . . . . . . . . . . . . . . . . . . . 3
	4. Page 1 Paging Dispatch . . . . . . . . . . . . . . . . . . . 4		4. Page 1 Paging Dispatch . . . . . . . . . . . . . . . . . . . 4
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 4		5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
	6.1. Consuming Dispatch Types . . . . . . . . . . . . . . . . 5		6.1. Consuming Dispatch Types . . . . . . . . . . . . . . . . 5
	6.2. New Per-Page Dispatch Type registries . . . . . . . . . . 5		6.2. New Per-Page Dispatch Type registries . . . . . . . . . . 5
	7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5		7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
	8.1. Normative References . . . . . . . . . . . . . . . . . . 5		8.1. Normative References . . . . . . . . . . . . . . . . . . 5
	8.2. Informative References . . . . . . . . . . . . . . . . . 6		8.2. Informative References . . . . . . . . . . . . . . . . . 6
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
	1. Introduction		1. Introduction
	The design of Low Power and Lossy Networks (LLNs) is generally		The design of Low Power and Lossy Networks (LLNs) is generally
	focused on saving energy, which often is a very constrained resource.		focused on saving energy, which often is a very constrained resource.
	Other constraints, such as memory capacity and duty cycle		Other constraints, such as memory capacity and duty cycle
	restrictions on LLN devices, usually derive from that primary		restrictions on LLN devices, usually derive from that primary
	concern. Energy is often available only from primary batteries that		concern. Energy is often available only from primary batteries that
	are expected to last for years, or is scavenged from the environment		are expected to last for years, or is scavenged from the environment
	in very limited amounts. Any protocol that is intended for use in		in very limited amounts. Any protocol that is intended for use in
	skipping to change at page 5, line 35 ¶		skipping to change at page 5, line 35 ¶
	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].
	Those values are from 01 100000 through 01 111111 and they have the		Those values are from 01 100000 through 01 111111 and they have the
	same definition in Page 1 as they do in Page 0, meaning that the		same definition in Page 1 as they do in Page 0, meaning that the
	registries for Page 0 and Page 1 are an exact overlap in this range.		registries for Page 0 and Page 1 are an exact overlap in this range.
	7. Acknowledgments		7. Acknowledgments
	The authors wish to thank Thomas Watteyne, Tengfei Chang, Martin		The authors wish to thank Tom Phinney, Thomas Watteyne, Tengfei
	Turon, James Woodyatt, Samita Chakrabarti, Jonathan Hui, Gabriel		Chang, Martin Turon, James Woodyatt, Samita Chakrabarti, Jonathan
	Montenegro and Ralph Droms for constructive reviews to the design in		Hui, Gabriel Montenegro and Ralph Droms for constructive reviews to
	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", 2015.
	skipping to change at page 6, line 36 ¶		skipping to change at page 6, line 36 ¶
	[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>.
	[RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for		[RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for
	Constrained-Node Networks", RFC 7228,		Constrained-Node Networks", RFC 7228,
	DOI 10.17487/RFC7228, May 2014,		DOI 10.17487/RFC7228, May 2014,
	<http://www.rfc-editor.org/info/rfc7228>.		<http://www.rfc-editor.org/info/rfc7228>.
	Author's Address		Authors' Addresses
	Pascal Thubert (editor)		Pascal Thubert (editor)
	Cisco Systems		Cisco Systems
	Building D - Regus		Building D - Regus
	45 Allee des Ormes		45 Allee des Ormes
	BP1200		BP1200
	MOUGINS - Sophia Antipolis 06254		MOUGINS - Sophia Antipolis 06254
	FRANCE		FRANCE
	Phone: +33 4 97 23 26 34		Phone: +33 4 97 23 26 34
	Email: pthubert@cisco.com		Email: pthubert@cisco.com
			Robert Cragie
			ARM Ltd.
			110 Fulbourn Road
			Cambridge CB1 9NJ
			UK
			Email: robert.cragie@gridmerge.com
End of changes. 7 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/