< draft-droms-6lo-ethertype-request-00.txt   draft-droms-6lo-ethertype-request-01.txt >
6lo Working Group R. Droms 6lo Working Group R. Droms
Internet-Draft P. Duffy Internet-Draft P. Duffy
Intended status: Informational Cisco Intended status: Informational Cisco
Expires: August 20, 2016 February 17, 2016 Expires: October 6, 2016 April 4, 2016
Assignment of an Ethertype for IPv6 with RFC 4944, RFC 6282 Header Assignment of an Ethertype for IPv6 with LoWPAN Encapsulation
Encoding draft-droms-6lo-ethertype-request-01
draft-droms-6lo-ethertype-request-00
Abstract Abstract
When carried over layer 2 technologies such as Ethernet, IPv6 When carried over layer 2 technologies such as Ethernet, IPv6
datagrams using datagram encoding as defined in RFC 4944 and RFC 6282 datagrams using LoWPAN encapsulation as defined in RFC 4944 must be
must be identified so the receiver can correctly interpret the identified so the receiver can correctly interpret the encoded IPv6
encoded IPv6 datagram. This document requests the assignment of an datagram. This document requests the assignment of an Ethertype for
Ethertype for that purpose. that purpose.
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 August 20, 2016. This Internet-Draft will expire on October 6, 2016.
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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
1. Introduction 1. Introduction
The IETF has defined a format for IPv6 [RFC2460] datagram encoding in The IETF has defined a format for IPv6 [RFC2460] datagram
[RFC4944] and [RFC6282] (6loENC). 6loENC as defined in RFC 4944 and encapsulation [RFC4944] ("LoWPAN encapsulation"). This document
RFC 6282 may be extended and modified by future IETF standards regards any IPv6 datagram using the Dispatch octet as defined in
document. The intended layer 2 technology for IPv6 datagrams using section 5.1 of RFC 4944 to be using LoWPAN encapsulation. LoWPAN
6loENC as originally defined is [IEEE.802.15.4_2011], which does not encapsulation as defined in RFC 4944 has been updated by [RFC6282],
provide for a protocol switch in its layer 2 headers. and may be extended and modified by future IETF standards document.
The intended layer 2 technology for IPv6 datagrams using LoWPAN
encapsulation as originally defined is [IEEE.802.15.4_2011], which
does not provide for a protocol switch in its layer 2 headers.
There is interest in carrying IPv6 datatgrams over layer 2 There is interest in carrying IPv6 datatgrams over layer 2
technologies that do include a protocol switch field: technologies that do include a protocol switch field:
o Usage of 6loENC in conjunction with IEEE 802.15.9 Multiplexed Data o Usage of LoWPAN encapsulation in conjunction with IEEE 802.15.9
Service [IEEE802159], which provides the ability to perform upper Multiplexed Data Service [IEEE802159], which provides the ability
layer protocol dispatch for IEEE 802.15.4 networks. Wi-SUN to perform upper layer protocol dispatch for IEEE 802.15.4
Alliance intends to use the 15.9 Multiplexed Data Information networks. Wi-SUN Alliance intends to use the 15.9 Multiplexed
Element to dispatch 6loENC frames to upper stack layers. As Data Information Element to dispatch LoWPAN encapsulation frames
specified in IEEE 802.15.9, dispatch of 6loENC frames will require to upper stack layers. As specified in IEEE 802.15.9, dispatch of
an Ethertype be assigned for 6loENC. LoWPAN encapsulation frames will require an Ethertype be assigned
for LoWPAN encapsulation.
o 6loENC will likely be needed for WiFi Alliance's HaLoW [HALOW] o LoWPAN encapsulation will likely be needed for WiFi Alliance's
standard (low power operation in the 900 MHz band) HaLoW [HALOW] standard (low power operation in the 900 MHz band)
o Other layer 2 technologies such as Ethernet and debugging tools o Other layer 2 technologies such as Ethernet and debugging tools
such as Wireshark require a unique protocol type field for 6loENC such as Wireshark require a unique protocol type field for LoWPAN
to properly interpret IPv6 datagrams that use 6loENC. encapsulation to properly interpret IPv6 datagrams that use LoWPAN
encapsulation.
2. Request to IEEE for assignment of an Ethertype 2. Request to IEEE for assignment of an Ethertype
When this document is published, the IETF will formally submit a When this document is published, the IETF will formally submit a
request to IEEE for assignment of an Ethertype for IPv6 datagrams request to IEEE for assignment of an Ethertype for IPv6 datagrams
using 6loENC. using LoWPAN encapsulation.
3. IANA Considerations 3. IANA Considerations
This memo includes no request to IANA. This memo includes no request to IANA.
4. Security Considerations 4. Security Considerations
This document is intended only to request assignment of an Ethertype This document is intended only to request assignment of an Ethertype
for IPv6 datagrams using 6loENC. It has no incremental implications for IPv6 datagrams using LoWPAN encapsulation. It has no incremental
for security beyond those in the relevant protocols. implications for security beyond those in the relevant protocols.
5. Normative References 5. Normative References
[HALOW] Wi-Fi Alliance, "Wi-Fi HaLow", [HALOW] Wi-Fi Alliance, "Wi-Fi HaLow",
http://www.wi-fi.org/discover-wi-fi/wi-fi-halow . http://www.wi-fi.org/discover-wi-fi/wi-fi-halow .
[IEEE.802.15.4_2011] [IEEE.802.15.4_2011]
IEEE, "IEEE Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and metropolitan area
networks--Part 15.4: Low-Rate Wireless Personal Area networks--Part 15.4: Low-Rate Wireless Personal Area
Networks (LR-WPANs)", IEEE 802.15.4-2011, Networks (LR-WPANs)", IEEE 802.15.4-2011,
 End of changes. 10 change blocks. 
29 lines changed or deleted 33 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/