draft-ietf-6lo-ethertype-request-00.txt   draft-ietf-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: October 20, 2016 April 18, 2016 Expires: December 8, 2016 June 6, 2016
Assignment of an Ethertype for IPv6 with LoWPAN Encapsulation Assignment of an Ethertype for IPv6 with LoWPAN Encapsulation
draft-ietf-6lo-ethertype-request-00 draft-ietf-6lo-ethertype-request-01
Abstract Abstract
When carried over layer 2 technologies such as Ethernet, IPv6 When carried over layer 2 technologies such as Ethernet, IPv6
datagrams using LoWPAN encapsulation as defined in RFC 4944 must be datagrams using LoWPAN encapsulation as defined in RFC 4944 must be
identified so the receiver can correctly interpret the encoded IPv6 identified so the receiver can correctly interpret the encoded IPv6
datagram. This document requests the assignment of an Ethertype for datagram. This document requests the assignment of an Ethertype for
that purpose. that purpose.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 October 20, 2016. This Internet-Draft will expire on December 8, 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
skipping to change at page 2, line 17 skipping to change at page 2, line 17
The IETF has defined a format for IPv6 [RFC2460] datagram The IETF has defined a format for IPv6 [RFC2460] datagram
encapsulation [RFC4944] ("LoWPAN encapsulation"). This document encapsulation [RFC4944] ("LoWPAN encapsulation"). This document
regards any IPv6 datagram using the Dispatch octet as defined in regards any IPv6 datagram using the Dispatch octet as defined in
section 5.1 of RFC 4944 to be using LoWPAN encapsulation. LoWPAN section 5.1 of RFC 4944 to be using LoWPAN encapsulation. LoWPAN
encapsulation as defined in RFC 4944 has been updated by [RFC6282], encapsulation as defined in RFC 4944 has been updated by [RFC6282],
and may be extended and modified by future IETF standards document. and may be extended and modified by future IETF standards document.
The intended layer 2 technology for IPv6 datagrams using LoWPAN The intended layer 2 technology for IPv6 datagrams using LoWPAN
encapsulation as originally defined is [IEEE.802.15.4_2011], which encapsulation as originally defined is [IEEE.802.15.4_2011], which
does not provide for a protocol switch in its layer 2 headers. 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 supporting Ethertype based protocol dispatch for
technologies that do include a protocol switch field: LoWPAN encapsulated IPv6 datagrams:
o Usage of LoWPAN encapsulation in conjunction with IEEE 802.15.9 o Usage of LoWPAN encapsulation in conjunction with IEEE 802.15.9
Multiplexed Data Service [IEEE802159], which provides the ability Multiplexed Data Service [IEEE802159], which provides the ability
to perform upper layer protocol dispatch for IEEE 802.15.4 to perform upper layer protocol dispatch for IEEE 802.15.4
networks. Wi-SUN Alliance intends to use the 15.9 Multiplexed networks. Wi-SUN Alliance intends to use the 15.9 Multiplexed
Data Information Element to dispatch LoWPAN encapsulation frames Data Information Element to dispatch LoWPAN encapsulation frames
to upper stack layers. As specified in IEEE 802.15.9, dispatch of to upper stack layers. As specified in IEEE 802.15.9, dispatch of
LoWPAN encapsulation frames will require an Ethertype be assigned LoWPAN encapsulation frames will require an Ethertype be assigned
for LoWPAN encapsulation. for LoWPAN encapsulation.
o LoWPAN encapsulation will likely be needed for WiFi Alliance's o LoWPAN encapsulation will likely be needed for WiFi Alliance's
HaLoW [HALOW] 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 LoWPAN such as Wireshark require a unique protocol type field for LoWPAN
encapsulation to properly interpret IPv6 datagrams that use LoWPAN encapsulation to properly interpret IPv6 datagrams that use LoWPAN
encapsulation. encapsulation.
o Any existing or future Layer 2 technology, incorporating Ethertype
based upper layer dispatch, can use the Ethertype proposed in this
document to dispatch LoWPAN encapsulated IPv6 datagrams.
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 LoWPAN encapsulation. using LoWPAN encapsulation.
3. IANA Considerations 3. IANA Considerations
This memo includes no request to IANA. This memo includes no request to IANA.
 End of changes. 5 change blocks. 
5 lines changed or deleted 9 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/