Internet Engineering Task Force (IETF)                   P. Thubert, Ed.
Request for Comments: 8025                                         Cisco
Updates: 4944                                                  R. Cragie
Category: Standards Track                                            ARM
ISSN: 2070-1721                                            November 2016
        
Internet Engineering Task Force (IETF)                   P. Thubert, Ed.
Request for Comments: 8025                                         Cisco
Updates: 4944                                                  R. Cragie
Category: Standards Track                                            ARM
ISSN: 2070-1721                                            November 2016
        

IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Paging Dispatch

低功耗无线个人区域网(6LoWPAN)上的IPv6寻呼调度

Abstract

摘要

This specification updates RFC 4944 to introduce a new context switch mechanism for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) compression, expressed in terms of Pages and signaled by a new Paging Dispatch.

本规范更新了RFC 4944,为低功耗无线个人区域网(6LoWPAN)上的IPv6压缩引入了一种新的上下文切换机制,该机制以页面表示,并由新的寻呼调度发出信号。

Status of This Memo

关于下段备忘

This is an Internet Standards Track document.

这是一份互联网标准跟踪文件。

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.

本文件是互联网工程任务组(IETF)的产品。它代表了IETF社区的共识。它已经接受了公众审查,并已被互联网工程指导小组(IESG)批准出版。有关互联网标准的更多信息,请参见RFC 7841第2节。

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8025.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息,请访问http://www.rfc-editor.org/info/rfc8025.

Copyright Notice

版权公告

Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.

版权所有(c)2016 IETF信托基金和确定为文件作者的人员。版权所有。

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件,因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本,并提供简化BSD许可证中所述的无担保。

Table of Contents

目录

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Updating RFC 4944 . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Page 1 Paging Dispatch  . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Page Switch Dispatch Types  . . . . . . . . . . . . . . .   5
     6.2.  New Column in Dispatch Type Registry  . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8
        
   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Updating RFC 4944 . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Page 1 Paging Dispatch  . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Page Switch Dispatch Types  . . . . . . . . . . . . . . .   5
     6.2.  New Column in Dispatch Type Registry  . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8
        
1. Introduction
1. 介绍

The design of Low-Power and Lossy Networks (LLNs) is generally focused on saving energy, which is often a very constrained resource. Other constraints, such as memory capacity and duty cycle restrictions on LLN devices, usually derive from that primary concern. Energy is often available only from primary batteries that are expected to last for years or is scavenged from the environment in very limited amounts. Any protocol that is intended for use in LLNs must be designed with a primary focus on saving energy, which is a strict requirement.

低功耗和有损网络(LLN)的设计通常侧重于节能,而节能往往是一项非常有限的资源。其他限制,如LLN设备上的内存容量和占空比限制,通常源自该主要关注点。能量通常只能从原电池中获得,原电池预计可以使用数年,或者从环境中清除的能量非常有限。任何用于LLN的协议都必须以节能为主要目标进行设计,这是一项严格的要求。

Controlling the amount of data transmission is one possible means of saving energy. In a number of LLN standards, the frame size is limited to much smaller values than the IPv6 maximum transmission unit (MTU) of 1280 bytes. In particular, an LLN that relies on the classical Physical Layer (PHY) of IEEE 802.15.4 [IEEE.802.15.4] is limited to 127 bytes per frame. The need to compress IPv6 packets over IEEE 802.15.4 led to the 6LoWPAN Header Compression (6LoWPAN-HC) [RFC6282] work.

控制数据传输量是一种可能的节能方法。在许多LLN标准中,帧大小被限制为比1280字节的IPv6最大传输单元(MTU)小得多的值。具体而言,依赖IEEE 802.15.4[IEEE.802.15.4]的经典物理层(PHY)的LLN被限制为每帧127字节。需要通过IEEE 802.15.4压缩IPv6数据包导致6LoWPAN头压缩(6LoWPAN HC)[RFC6282]工作。

As more and more protocols need to be compressed, the encoding capabilities of the original dispatch defined in the 6LowPAN adaptation-layer framework ([RFC4944] and [RFC6282]) becomes saturated. This specification introduces a new context switch mechanism for 6LoWPAN compression, expressed in terms of Pages and signaled by a new Paging Dispatch mechanism.

随着越来越多的协议需要压缩,6LowPAN适配层框架([RFC4944]和[RFC6282])中定义的原始调度的编码能力变得饱和。本规范介绍了一种新的用于6LoWPAN压缩的上下文切换机制,该机制以页面表示,并由一种新的分页调度机制发出信号。

2. Terminology
2. 术语

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”应按照[RFC2119]中的说明进行解释。

The terminology used in this document is consistent with and incorporates that described in "Terms Used in Routing for Low-Power and Lossy Networks" [RFC7102] and "Terminology for Constrained-Node Networks" [RFC7228].

本文件中使用的术语与“低功耗和有损网络路由中使用的术语”[RFC7102]和“受限节点网络术语”[RFC7228]中所述的术语一致,并结合了这些术语。

3. Updating RFC 4944
3. 更新RFC4944

This document adapts 6LoWPAN while maintaining backward compatibility with IPv6 over IEEE 802.15.4 [RFC4944] by introducing the concept of a "parsing context" in the 6LoWPAN parser, a context being identified by a Page Number. This specification defines 16 Pages.

本文档通过在6LoWPAN解析器中引入“解析上下文”的概念,对6LoWPAN进行了修改,同时通过IEEE 802.15.4[RFC4944]与IPv6保持向后兼容性,该上下文由页码标识。本规范定义了16页。

Pages are delimited in a 6LoWPAN packet by a Paging Dispatch value that indicates the next current Page. The Page Number is encoded in a Paging Dispatch with the Value Bit Pattern of 11 11xxxx, where xxxx is the Page Number, 0 to 15, as described in Figure 1:

页面在6LoWPAN数据包中由指示下一个当前页面的分页分派值分隔。页码在分页调度中编码,其值位模式为11 11xxxx,其中xxxx是页码,0到15,如图1所示:

                            0
                            0 1 2 3 4 5 6 7
                           +-+-+-+-+-+-+-+-+
                           |1|1|1|1|Page Nb|
                           +-+-+-+-+-+-+-+-+
        
                            0
                            0 1 2 3 4 5 6 7
                           +-+-+-+-+-+-+-+-+
                           |1|1|1|1|Page Nb|
                           +-+-+-+-+-+-+-+-+
        

Figure 1: Paging Dispatch with Page Number Encoding

图1:使用页码编码的分页调度

Values of the Dispatch byte defined in [RFC4944] are considered as belonging to the Page 0 parsing context, which is the default and does not need to be signaled explicitly at the beginning of a 6LoWPAN packet. This ensures backward compatibility with existing implementations of 6LoWPAN.

[RFC4944]中定义的调度字节值被视为属于第0页解析上下文,这是默认值,不需要在6LoWPAN数据包的开头显式发出信号。这确保了与6LoWPAN现有实现的向后兼容性。

The Dispatch bits defined in [RFC4944] are used in Page 0 and are free to be reused in Pages 1 to 15. In Section 4, this specification allocates some values in Page 1 and leaves the rest open for future allocations.

[RFC4944]中定义的调度位用于第0页,可在第1页至第15页中自由重用。在第4节中,本规范在第1页中分配了一些值,并保留其余值供将来分配。

Values made available by this specification in Pages 1 to 14 are to be assigned for new protocols whereas Page 15 is reserved for Experimental Use [RFC5226].

本规范第1页至第14页中提供的值将分配给新协议,而第15页保留供实验使用[RFC5226]。

Note: This specification does not use the Escape Dispatch, which extends Page 0 to more values, but rather allocates another Dispatch Bit Pattern (11 11xxxx) for a new Paging Dispatch that is present in all Pages, including Page 0 and Pages defined in future specifications, to indicate the next parsing context represented by its Page Number. The rationale for avoiding that approach is that there can be multiple occurrences of a new header indexed by this specification in a single frame and the overhead on an octet each time for the Escape Dispatch would be prohibitive.

注意:本规范不使用转义分派(将第0页扩展到更多值),而是为所有页(包括第0页和未来规范中定义的页)中存在的新分页分派分配另一个分派位模式(11 11xxxx),以指示由其页码表示的下一个解析上下文。避免这种方法的基本原理是,在单个帧中可能会多次出现由本规范索引的新报头,并且每次转义调度的八位组开销将是禁止的。

A Page (say Page N) is said to be active once the Page N Paging Dispatch is parsed, and it remains active until another Paging Dispatch is parsed.

一个页面(比如第N页)在第N页分页分派被解析后被称为活动页面,并且在另一个分页分派被解析之前它一直保持活动状态。

4. Page 1 Paging Dispatch
4. 第1页寻呼调度

This specification defines some special properties for Page 1, detailed below:

本规范定义了第1页的一些特殊属性,详情如下:

The Dispatch bits defined for LOWPAN_IPHC by the "Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks" [RFC6282] are defined with the same values in Page 1, so there is no need to switch context from Page 1 to Page 0 to decode a packet that is encoded per [RFC6282].

“基于IEEE 802.15.4的网络上IPv6数据报的压缩格式”[RFC6282]为LOWPAN_IPHC定义的调度位在第1页中定义为相同的值,因此无需将上下文从第1页切换到第0页来解码根据[RFC6282]编码的数据包。

Mesh Headers represent Layer 2 information and are processed before any Layer 3 information that is encoded in Page 1. If a 6LoWPAN packet requires a Mesh Header, the Mesh Header MUST always be placed in the packet before the first Page 1 Paging Dispatch, if any.

网格标头表示第2层信息,并在第1页中编码的任何第3层信息之前进行处理。如果6LoWPAN数据包需要Mesh报头,则Mesh报头必须始终在第一页1分页调度(如果有)之前放置在数据包中。

For the same reason, Fragment Headers as defined in [RFC4944] MUST always be placed in the packet before the first Page 1 Paging Dispatch, if any.

出于同样的原因,[RFC4944]中定义的片段头必须始终放在第一页1分页调度(如果有)之前的数据包中。

The NALP Dispatch Bit Pattern as defined in [RFC4944] is only defined for the first octet in the packet. Switching back to Page 0 for NALP inside a 6LoWPAN packet does not make sense.

[RFC4944]中定义的NALP调度位模式仅为数据包中的第一个八位字节定义。对于6LoWPAN数据包内的NALP,切换回第0页没有意义。

As a result, there is no need to restore the Page 0 parsing context after a context was switched to Page 1, so the value for the Page 0 Paging Dispatch of 11 110000 may not actually occur in those packets that adhere to 6LoWPAN specifications available at the time of writing this specification.

因此,在将上下文切换到第1页后,不需要恢复第0页解析上下文,因此在编写本规范时遵守6LoWPAN规范的那些数据包中,第0页分页分派的值11 110000实际上可能不会出现。

5. Security Considerations
5. 安全考虑

The security considerations of [RFC4944] and [RFC6282] apply.

[RFC4944]和[RFC6282]的安全注意事项适用。

6. IANA Considerations
6. IANA考虑
6.1. Page Switch Dispatch Types
6.1. 页面交换调度类型

This document allocates 16 values for "Page switch" from the "Dispatch Type Field" registry that was created by [RFC4944]. The allocated values are from 11 110000 through 11 111111 and represent Page Numbers 0 through 15 as discussed in this document.

本文档从[RFC4944]创建的“分派类型字段”注册表中为“页面切换”分配16个值。分配的值从11 110000到11 111111,表示本文件中讨论的页码0到15。

6.2. New Column in Dispatch Type Registry
6.2. 调度类型注册表中的新列

This document extends the "Dispatch Type Field" registry, which was created by [RFC4944] and updated by [RFC6282], by adding a new column called "Page".

本文档通过添加一个名为“页面”的新列,扩展了由[RFC4944]创建并由[RFC6282]更新的“分派类型字段”注册表。

This document defines 16 Pages, "Page 0" to "Page 15".

本文件定义了16页,“第0页”至“第15页”。

The preexisting registry content is assigned to "Page 0".

先前存在的注册表内容已分配给“第0页”。

This document also associates the Dispatch type field values that are allocated for LOWPAN_IPHC by [RFC6282] to Page 1. 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, Page 0 and Page 1 are grouped together in the registry for this range.

本文件还将[RFC6282]为LOWPAN_IPHC分配的分派类型字段值与第1页相关联。这些值的范围为01 100000到01 111111,第1页中的定义与第0页中的定义相同;因此,第0页和第1页在该范围的注册表中分组在一起。

Values ranging from 00 000000 to 11 101111 in Page 15 (that is, all of Page 15 except the space used for Page switch) are reserved for Experimental Use [RFC5226] and shall not be assigned.

第15页中从00 000000到11 101111的值(即,除页面切换所用空间外的所有第15页)保留供实验使用[RFC5226],不得分配。

Figure 2 represents the updates to the registry as described above. Refer to <http://www.iana.org/assignments/_6lowpan-parameters> for the complete list of updates.

图2显示了如上所述的注册表更新。指<http://www.iana.org/assignments/_6lowpan-parameters>获取更新的完整列表。

 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  Bit Pattern  |    Page     | Header Type         |  Reference      |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |               |     0       |  NALP               |  RFC 4944,      |
 |               |             |                     |  this document  |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  00 xxxxxx    |    1-14     |  Unassigned         |                 |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
 |               |    15       |  Reserved for       |  this document  |
 |               |             |  Experimental Use   |                 |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |               |     0       |  ESC                |  RFC 6282,      |
 |               |             |                     |  this document  |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  01 000000    |    1-14     |  Unassigned         |                 |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
 |               |    15       |  Reserved for       |  this document  |
 |               |             |  Experimental Use   |                 |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                       ...                   ...
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |               |    0-1      |  LOWPAN_IPHC        |  RFC 6282,      |
 |               |             |                     |  this document  |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  01 1xxxxx    |    2-14     |  Unassigned         |                 |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
 |               |    15       |  Reserved for       |  this document  |
 |               |             |  Experimental Use   |                 |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                       ...                   ...
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  11 11xxxx    |    0-15     |  Page switch        |  this document  |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  Bit Pattern  |    Page     | Header Type         |  Reference      |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |               |     0       |  NALP               |  RFC 4944,      |
 |               |             |                     |  this document  |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  00 xxxxxx    |    1-14     |  Unassigned         |                 |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
 |               |    15       |  Reserved for       |  this document  |
 |               |             |  Experimental Use   |                 |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |               |     0       |  ESC                |  RFC 6282,      |
 |               |             |                     |  this document  |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  01 000000    |    1-14     |  Unassigned         |                 |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
 |               |    15       |  Reserved for       |  this document  |
 |               |             |  Experimental Use   |                 |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                       ...                   ...
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |               |    0-1      |  LOWPAN_IPHC        |  RFC 6282,      |
 |               |             |                     |  this document  |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  01 1xxxxx    |    2-14     |  Unassigned         |                 |
 +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
 |               |    15       |  Reserved for       |  this document  |
 |               |             |  Experimental Use   |                 |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                       ...                   ...
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  11 11xxxx    |    0-15     |  Page switch        |  this document  |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Figure 2: Integrating the New Page Column

图2:集成新页面列

Future assignments in these registries are to be coordinated via IANA under the policy of "Specification Required" [RFC5226]. It is expected that this policy will allow for other (non-IETF) organizations to more easily obtain assignments.

这些登记处的未来分配将根据“要求规范”政策通过IANA进行协调[RFC5226]。预计该政策将允许其他(非IETF)组织更容易获得任务。

7. References
7. 工具书类
7.1. Normative References
7.1. 规范性引用文件

[IEEE.802.15.4] IEEE, "IEEE Standard for Low-Rate Wireless Networks", IEEE 802.15.4-2015, DOI 10.1109/IEEESTD.2016.7460875, <http://ieeexplore.ieee.org/document/7460875/>.

[IEEE.802.15.4]IEEE,“低速无线网络的IEEE标准”,IEEE 802.15.4-2015,DOI 10.1109/IEEESTD.2016.7460875<http://ieeexplore.ieee.org/document/7460875/>.

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.

[RFC2119]Bradner,S.,“RFC中用于表示需求水平的关键词”,BCP 14,RFC 2119,DOI 10.17487/RFC2119,1997年3月<http://www.rfc-editor.org/info/rfc2119>.

[RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks", RFC 4944, DOI 10.17487/RFC4944, September 2007, <http://www.rfc-editor.org/info/rfc4944>.

[RFC4944]黑山,G.,Kushalnagar,N.,Hui,J.,和D.Culler,“通过IEEE 802.15.4网络传输IPv6数据包”,RFC 4944,DOI 10.17487/RFC4944,2007年9月<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>.

[RFC5226]Narten,T.和H.Alvestrand,“在RFCs中编写IANA注意事项部分的指南”,BCP 26,RFC 5226,DOI 10.17487/RFC5226,2008年5月<http://www.rfc-editor.org/info/rfc5226>.

[RFC6282] Hui, J., Ed. and P. Thubert, "Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks", RFC 6282, DOI 10.17487/RFC6282, September 2011, <http://www.rfc-editor.org/info/rfc6282>.

[RFC6282]Hui,J.,Ed.和P.Thubert,“基于IEEE 802.15.4的网络上IPv6数据报的压缩格式”,RFC 6282,DOI 10.17487/RFC6282,2011年9月<http://www.rfc-editor.org/info/rfc6282>.

7.2. Informative References
7.2. 资料性引用

[RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January 2014, <http://www.rfc-editor.org/info/rfc7102>.

[RFC7102]Vasseur,JP.,“低功率和有损网络路由中使用的术语”,RFC 7102,DOI 10.17487/RFC7102,2014年1月<http://www.rfc-editor.org/info/rfc7102>.

[RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for Constrained-Node Networks", RFC 7228, DOI 10.17487/RFC7228, May 2014, <http://www.rfc-editor.org/info/rfc7228>.

[RFC7228]Bormann,C.,Ersue,M.和A.Keranen,“受限节点网络的术语”,RFC 7228,DOI 10.17487/RFC7228,2014年5月<http://www.rfc-editor.org/info/rfc7228>.

Acknowledgments

致谢

The authors wish to thank Tom Phinney, Thomas Watteyne, Tengfei Chang, Martin Turon, James Woodyatt, Samita Chakrabarti, Jonathan Hui, Gabriel Montenegro, and Ralph Droms for constructive reviews of the design in the 6lo working group.

作者希望感谢Tom Phinney、Thomas Watteyne、Tengfei Chang、Martin Turon、James Woodyatt、Samita Chakrabarti、Jonathan Hui、Gabriel Montegon和Ralph Droms在6lo工作组中对设计进行的建设性审查。

Authors' Addresses

作者地址

Pascal Thubert (editor) Cisco Systems Building D - Regus 45 Allee des Ormes BP1200 Mougins - Sophia Antipolis 06254 France

Pascal Thubert(编辑)思科系统D大楼-雷格斯45 Allee des Ormes BP1200 Mougins-索菲亚安提波利斯06254法国

   Phone: +33 4 97 23 26 34
   Email: pthubert@cisco.com
        
   Phone: +33 4 97 23 26 34
   Email: pthubert@cisco.com
        

Robert Cragie ARM Ltd. 110 Fulbourn Road Cambridge CB1 9NJ United Kingdom

Robert Cragie ARM Ltd.英国剑桥CB1 9NJ富尔伯恩路110号

   Email: robert.cragie@gridmerge.com
        
   Email: robert.cragie@gridmerge.com