draft-ietf-6lo-lowpanz-07.txt   draft-ietf-6lo-lowpanz-08.txt 
IPv6 over Networks of Resource-constrained Nodes (6lo) WG A. Brandt IPv6 over Networks of Resource-constrained Nodes (6lo) WG A. Brandt
Internet-Draft J. Buron Internet-Draft J. Buron
Intended status: Standards Track Sigma Designs Intended status: Standards Track Sigma Designs
Expires: March 26, 2015 September 22, 2014 Expires: May 3, 2015 October 30, 2014
Transmission of IPv6 packets over ITU-T G.9959 Networks Transmission of IPv6 packets over ITU-T G.9959 Networks
draft-ietf-6lo-lowpanz-07 draft-ietf-6lo-lowpanz-08
Abstract Abstract
This document describes the frame format for transmission of IPv6 This document describes the frame format for transmission of IPv6
packets and a method of forming IPv6 link-local addresses and packets and a method of forming IPv6 link-local addresses and
statelessly autoconfigured IPv6 addresses on ITU-T G.9959 networks. statelessly autoconfigured IPv6 addresses on ITU-T G.9959 networks.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 26, 2015. This Internet-Draft will expire on May 3, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 17 skipping to change at page 2, line 17
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terms used . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terms used . . . . . . . . . . . . . . . . . . . . . . . 3
2. G.9959 parameters to use for IPv6 transport . . . . . . . . . 5 2. G.9959 parameters to use for IPv6 transport . . . . . . . . . 5
2.1. Addressing mode . . . . . . . . . . . . . . . . . . . . . 5 2.1. Addressing mode . . . . . . . . . . . . . . . . . . . . . 5
2.2. IPv6 Multicast support . . . . . . . . . . . . . . . . . 6 2.2. IPv6 Multicast support . . . . . . . . . . . . . . . . . 6
2.3. G.9959 MAC PDU size and IPv6 MTU . . . . . . . . . . . . 6 2.3. G.9959 MAC PDU size and IPv6 MTU . . . . . . . . . . . . 6
2.4. Transmission status indications . . . . . . . . . . . . . 6 2.4. Transmission status indications . . . . . . . . . . . . . 7
2.5. Transmission security . . . . . . . . . . . . . . . . . . 7 2.5. Transmission security . . . . . . . . . . . . . . . . . . 7
3. 6LoWPAN Adaptation Layer and Frame Format . . . . . . . . . . 7 3. 6LoWPAN Adaptation Layer and Frame Format . . . . . . . . . . 7
3.1. Dispatch Header . . . . . . . . . . . . . . . . . . . . . 8 3.1. Dispatch Header . . . . . . . . . . . . . . . . . . . . . 8
4. 6LoWPAN addressing . . . . . . . . . . . . . . . . . . . . . 9 4. 6LoWPAN addressing . . . . . . . . . . . . . . . . . . . . . 9
4.1. Stateless Address Autoconfiguration of routable IPv6 4.1. Stateless Address Autoconfiguration of routable IPv6
addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
4.2. IPv6 Link Local Address . . . . . . . . . . . . . . . . . 9 4.2. IPv6 Link Local Address . . . . . . . . . . . . . . . . . 9
4.3. Unicast Address Mapping . . . . . . . . . . . . . . . . . 10 4.3. Unicast Address Mapping . . . . . . . . . . . . . . . . . 10
4.4. On the use of Neighbor Discovery technologies . . . . . . 10 4.4. On the use of Neighbor Discovery technologies . . . . . . 10
4.4.1. Prefix and CID management (Route-over) . . . . . . . 11 4.4.1. Prefix and CID management (Route-over) . . . . . . . 11
4.4.2. Prefix and CID management (Mesh-under) . . . . . . . 11 4.4.2. Prefix and CID management (Mesh-under) . . . . . . . 11
5. Header Compression . . . . . . . . . . . . . . . . . . . . . 12 5. Header Compression . . . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 13 8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 13
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
10.1. Normative References . . . . . . . . . . . . . . . . . . 14 10.1. Normative References . . . . . . . . . . . . . . . . . . 14
10.2. Informative References . . . . . . . . . . . . . . . . . 15 10.2. Informative References . . . . . . . . . . . . . . . . . 15
Appendix A. G.9959 6LoWPAN datagram example . . . . . . . . . . 16 Appendix A. G.9959 6LoWPAN datagram example . . . . . . . . . . 16
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 19 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 20
B.1. Changes since -00 . . . . . . . . . . . . . . . . . . . . 19 B.1. Changes since -00 . . . . . . . . . . . . . . . . . . . . 20
B.2. Changes since -01 . . . . . . . . . . . . . . . . . . . . 20 B.2. Changes since -01 . . . . . . . . . . . . . . . . . . . . 20
B.3. Changes since -02 . . . . . . . . . . . . . . . . . . . . 20 B.3. Changes since -02 . . . . . . . . . . . . . . . . . . . . 21
B.4. Changes since -03 . . . . . . . . . . . . . . . . . . . . 21 B.4. Changes since -03 . . . . . . . . . . . . . . . . . . . . 21
B.5. Changes since -04 . . . . . . . . . . . . . . . . . . . . 21 B.5. Changes since -04 . . . . . . . . . . . . . . . . . . . . 22
B.6. Changes since -05 . . . . . . . . . . . . . . . . . . . . 21 B.6. Changes since -05 . . . . . . . . . . . . . . . . . . . . 22
B.7. Changes since -06 . . . . . . . . . . . . . . . . . . . . 22 B.7. Changes since -06 . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 B.8. Changes since -07 . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
The ITU-T G.9959 recommendation [G.9959] targets low-power Personal The ITU-T G.9959 recommendation [G.9959] targets low-power Personal
Area Networks (PANs). This document defines the frame format for Area Networks (PANs). This document defines the frame format for
transmission of IPv6 [RFC2460] packets as well as the formation of transmission of IPv6 [RFC2460] packets as well as the formation of
IPv6 link-local addresses and statelessly autoconfigured IPv6 IPv6 link-local addresses and statelessly autoconfigured IPv6
addresses on G.9959 networks. addresses on G.9959 networks.
The general approach is to adapt elements of [RFC4944] to G.9959 The general approach is to adapt elements of [RFC4944] to G.9959
skipping to change at page 5, line 44 skipping to change at page 5, line 44
| +--------+---------------------------------------------+ | +--------+---------------------------------------------+
| | 1 | Node MUST use DHCPv6 based addressing and | | | 1 | Node MUST use DHCPv6 based addressing and |
| | | Node MUST comply fully with [RFC6775] | | | | Node MUST comply fully with [RFC6775] |
+--------+--------+---------------------------------------------+ +--------+--------+---------------------------------------------+
Figure 1: RA M flag support and interpretation Figure 1: RA M flag support and interpretation
A node that uses DHCPv6 based addressing MUST comply fully with the A node that uses DHCPv6 based addressing MUST comply fully with the
text of [RFC6775]. text of [RFC6775].
If DHCPv6 based addressing is used, the DHCPv6 client must use a DUID
of type DUID-UUID, as described in [RFC6355]. The UUID used in the
DUID-UUID must be generated as specified in [RFC4122], section 4.5,
starting at the second paragraph in that section (the 47-bit random
number-based UUID). The DUID must be stored persistently by the node
as specified in section 3 of [RFC6355].
A word of caution: since HomeIDs and NodeIDs are handed out by a A word of caution: since HomeIDs and NodeIDs are handed out by a
network controller function during inclusion, identifier validity and network controller function during inclusion, identifier validity and
uniqueness is limited by the lifetime of the network membership. uniqueness is limited by the lifetime of the network membership.
This can be cut short by a mishap occurring to the network This can be cut short by a mishap occurring to the network
controller. Having a single point of failure at the network controller. Having a single point of failure at the network
controller suggests that high-reliability network deployments may controller suggests that high-reliability network deployments may
benefit from a redundant network controller function. benefit from a redundant network controller function.
This warning applies to link-layer-derived addressing as well as to This warning applies to link-layer-derived addressing as well as to
non-link-layer-derived addressing deployments. non-link-layer-derived addressing deployments.
skipping to change at page 6, line 42 skipping to change at page 6, line 47
IPv6 packets MUST be transmitted using G.9959 transmission profile R3 IPv6 packets MUST be transmitted using G.9959 transmission profile R3
or higher. or higher.
[RFC2460] specifies that any link that cannot convey a 1280-octet [RFC2460] specifies that any link that cannot convey a 1280-octet
packet in one piece, must provide link-specific fragmentation and packet in one piece, must provide link-specific fragmentation and
reassembly at a layer below IPv6. reassembly at a layer below IPv6.
G.9959 provides Segmentation And Reassembly for payloads up to 1350 G.9959 provides Segmentation And Reassembly for payloads up to 1350
octets. IPv6 Header Compression [RFC6282] improves the chances that octets. IPv6 Header Compression [RFC6282] improves the chances that
a short IPv6 packet can fit into a single G.9959 frame. Therefore, a short IPv6 packet can fit into a single G.9959 frame. Therefore,
section Section 3 specifies that [RFC6282] MUST be supported. With Section 3 specifies that [RFC6282] MUST be supported. With the
the mandatory link-layer security enabled, a G.9959 R3 MAC PDU may mandatory link-layer security enabled, a G.9959 R3 MAC PDU may
accommodate 6LoWPAN datagrams of up to 130 octets without triggering accommodate 6LoWPAN datagrams of up to 130 octets without triggering
G.9959 Segmentation and Reassembly (SAR). Longer 6LoWPAN datagrams G.9959 Segmentation and Reassembly (SAR). Longer 6LoWPAN datagrams
will lead to the transmission of multiple G.9959 PDUs. will lead to the transmission of multiple G.9959 PDUs.
2.4. Transmission status indications 2.4. Transmission status indications
The G.9959 MAC layer provides native acknowledgement and The G.9959 MAC layer provides native acknowledgement and
retransmission of MAC PDUs. The G.9959 SAR layer does the same for retransmission of MAC PDUs. The G.9959 SAR layer does the same for
larger datagrams. A mesh routing layer may provide a similar feature larger datagrams. A mesh routing layer may provide a similar feature
for routed communication. An IPv6 routing stack communicating over for routed communication. An IPv6 routing stack communicating over
skipping to change at page 14, line 12 skipping to change at page 14, line 12
Some link layers use a 48-bit or a 64-bit link layer address which Some link layers use a 48-bit or a 64-bit link layer address which
uniquely identifies the node on a global scale regardless of global uniquely identifies the node on a global scale regardless of global
prefix changes. The risk of exposing a G.9959 device from its link- prefix changes. The risk of exposing a G.9959 device from its link-
layer-derived IID is limited because of the short 8-bit link layer layer-derived IID is limited because of the short 8-bit link layer
address. address.
While intended for central address management, DHCPv6 address While intended for central address management, DHCPv6 address
assignment also decouples the IPv6 address from the link layer assignment also decouples the IPv6 address from the link layer
address. Addresses may be made dynamic by the use of a short DHCP address. Addresses may be made dynamic by the use of a short DHCP
lease period and an assignment policy which makes the DHCP server lease period and an assignment policy which makes the DHCP server
hand out a fresh IP address every time. hand out a fresh IP address every time. For enhanced privacy, the
DHCP assigned addresses should be logged only for the duration of the
lease provided the implementation also allows logging for longer
durations as per the operational policies.
It should be noted that privacy and frequently changing address It should be noted that privacy and frequently changing address
assignment comes at a cost. Non-link-layer-derived IIDs require the assignment comes at a cost. Non-link-layer-derived IIDs require the
use of address registration and further, non-link-layer-derived IIDs use of address registration and further, non-link-layer-derived IIDs
cannot be compressed, which leads to longer datagrams and increased cannot be compressed, which leads to longer datagrams and increased
link layer segmentation. Finally, frequent prefix changes link layer segmentation. Finally, frequent prefix changes
necessitate more Context Identifier updates, which not only leads to necessitate more Context Identifier updates, which not only leads to
increased traffic but also may affect the battery lifetime of increased traffic but also may affect the battery lifetime of
sleeping nodes. sleeping nodes.
skipping to change at page 14, line 47 skipping to change at page 15, line 5
[G.9959] "G.9959 (02/12) + G.9959 Amendment 1 (10/13): Short range, [G.9959] "G.9959 (02/12) + G.9959 Amendment 1 (10/13): Short range,
narrow-band digital radiocommunication transceivers", narrow-band digital radiocommunication transceivers",
February 2012. February 2012.
[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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122, July
2005.
[RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
Addresses", RFC 4193, October 2005. Addresses", RFC 4193, October 2005.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
September 2007. September 2007.
[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, September 2007. Networks", RFC 4944, September 2007.
[RFC6282] Hui, J. and P. Thubert, "Compression Format for IPv6 [RFC6282] Hui, J. 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,
September 2011. September 2011.
[RFC6355] Narten, T. and J. Johnson, "Definition of the UUID-Based
DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355, August
2011.
[RFC6775] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann, [RFC6775] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann,
"Neighbor Discovery Optimization for IPv6 over Low-Power "Neighbor Discovery Optimization for IPv6 over Low-Power
Wireless Personal Area Networks (6LoWPANs)", RFC 6775, Wireless Personal Area Networks (6LoWPANs)", RFC 6775,
November 2012. November 2012.
[RFC_TBD_GHC] [RFC_TBD_GHC]
"draft-ietf-6lo-ghc: 6LoWPAN Generic Compression of "draft-ietf-6lo-ghc: 6LoWPAN Generic Compression of
Headers and Header-like Payloads", September 2014. Headers and Header-like Payloads", September 2014.
10.2. Informative References 10.2. Informative References
skipping to change at page 22, line 10 skipping to change at page 22, line 41
o Added reference to Privacy Considerations section from 6LoWPAN o Added reference to Privacy Considerations section from 6LoWPAN
Addressing section. Addressing section.
o Introducing optional GHC header compression. o Introducing optional GHC header compression.
B.7. Changes since -06 B.7. Changes since -06
o Added a note to section 5, that the mapping of 802.15.4 terms to o Added a note to section 5, that the mapping of 802.15.4 terms to
similar G.9959 terms applies not only to RFC6282 but also to GHC. similar G.9959 terms applies not only to RFC6282 but also to GHC.
B.8. Changes since -07
o Added a note to the Privacy considerations section on avoiding
DHCP logging.
o Added requirements for forming a UUID if DHCPv6 address assignment
is used.
Authors' Addresses Authors' Addresses
Anders Brandt Anders Brandt
Sigma Designs Sigma Designs
Emdrupvej 26A, 1. Emdrupvej 26A, 1.
Copenhagen O 2100 Copenhagen O 2100
Denmark Denmark
Email: anders_brandt@sigmadesigns.com Email: anders_brandt@sigmadesigns.com
 End of changes. 14 change blocks. 
13 lines changed or deleted 40 lines changed or added

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