draft-ietf-6lo-paging-dispatch-03.txt   draft-ietf-6lo-paging-dispatch-04.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 21, 2017 July 20, 2016 Expires: March 13, 2017 September 9, 2016
6LoWPAN Paging Dispatch 6LoWPAN Paging Dispatch
draft-ietf-6lo-paging-dispatch-03 draft-ietf-6lo-paging-dispatch-04
Abstract Abstract
This specification updates RFC 4944 to introduce a new context switch This specification updates RFC 4944 to introduce a new context switch
mechanism for 6LoWPAN compression, expressed in terms of Pages and mechanism for 6LoWPAN compression, expressed in terms of Pages and
signaled by a 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
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 January 21, 2017. This Internet-Draft will expire on March 13, 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 14 skipping to change at page 2, line 14
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
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 Column in Dispatch Type Registry . . . . . . . . . . 5
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 5 8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 6 8.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
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 4, line 8 skipping to change at page 4, line 8
Note: This specification does not use the Escape Dispatch, which Note: This specification does not use the Escape Dispatch, which
extends Page 0 to more values, but rather allocates another Dispatch extends Page 0 to more values, but rather allocates another Dispatch
Bit Pattern (1111xxxx) for a new Paging Dispatch, that is present in Bit Pattern (1111xxxx) for a new Paging Dispatch, that is present in
all Pages, including Page 0 and Pages defined in future all Pages, including Page 0 and Pages defined in future
specifications, to indicate the next parsing context represented by specifications, to indicate the next parsing context represented by
its Page Number. The rationale for avoiding that approach is that its Page Number. The rationale for avoiding that approach is that
there can be multiple occurrences of a new header indexed by this there can be multiple occurrences of a new header indexed by this
specification in a single frame and the overhead on an octet each specification in a single frame and the overhead on an octet each
time for the Escape Dispatch would be prohibitive. time for the Escape Dispatch would be prohibitive.
A Page (say Page N) is is said to be active once the Page N Paging A Page (say Page N) is said to be active once the Page N Paging
Dispatch is parsed, and as long as no other Paging Dispatch is Dispatch is parsed, and as long as no other Paging Dispatch is
parsed. parsed.
4. Page 1 Paging Dispatch 4. Page 1 Paging Dispatch
This specification defines some special properties for Page 1, This specification defines some special properties for Page 1,
detailed below: detailed below:
The Dispatch bits defined for LOWPAN_IPHC by the Compression The Dispatch bits defined for LOWPAN_IPHC by the Compression
Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks
skipping to change at page 5, line 11 skipping to change at page 5, line 11
The security considerations of [RFC4944] and [RFC6282] apply. The security considerations of [RFC4944] and [RFC6282] apply.
6. IANA Considerations 6. IANA Considerations
6.1. Consuming Dispatch Types 6.1. Consuming Dispatch Types
This document allocates 16 values from the Dispatch type field This document allocates 16 values from the Dispatch type field
registry that was created for [RFC4944]. The allocated values are registry that was created for [RFC4944]. The allocated values are
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 Column in Dispatch Type Registry
This document creates 15 new IANA registries for the Per-Page This document extends the Dispatch type field registry that was
Dispatch type fields, indexed by Page Number, 1 to 15. Each Registry created for [RFC4944] and updated by the [RFC6282], by adding a new
corresponds to a bit-field of one octet. column called "Page".
This document defines 16 Pages, "Page 0" to "Page 15".
The content of the incumbent registry is assigned to "Page 0".
This document also places in the registry associated to Page 1 the
Dispatch type field values that are allocated for LOWPAN_IPHC by
[RFC6282]. These values range from 01 100000 through 01 111111 and
have the same definition in Page 1 as they do in Page 0; as a result,
the registry entries for Page 0 and Page 1 are an exact overlap in
this range.
The resulting registry may be represented as a table as follow
(partial):
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Pattern | Page | Header Type | defining document |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 0 | NALP | RFC 4944 |
+ 00xxxxxx +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 1..15 | free | N/A |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 0 | ESC | RFC 6282 |
+ 01000000 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 1..15 | free | N/A |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
... ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 0..1 | LOWPAN_IPHC | RFC 6282 |
+ 011xxxxx +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 2..15 | free | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
... ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1111xxxx | 0..15 | Page switch | This |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Integrating the new Page column
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" [RFC5226]. 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
created for [RFC4944], which is considered as the registry for Page
0.
As described above, this document allocates in the registry
associated to Page 1 the Per-Page Dispatch type field values that are
allocated in the Dispatch type field for LOWPAN_IPHC by [RFC6282].
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
registries for Page 0 and Page 1 are an exact overlap in this range.
7. Acknowledgments 7. Acknowledgments
The authors wish to thank Tom Phinney, Thomas Watteyne, Tengfei The authors wish to thank Tom Phinney, Thomas Watteyne, Tengfei
Chang, Martin Turon, James Woodyatt, Samita Chakrabarti, Jonathan Chang, Martin Turon, James Woodyatt, Samita Chakrabarti, Jonathan
Hui, Gabriel Montenegro and Ralph Droms for constructive reviews to Hui, Gabriel Montenegro and Ralph Droms for constructive reviews to
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
 End of changes. 8 change blocks. 
25 lines changed or deleted 52 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/