draft-ietf-6lo-dispatch-iana-registry-03.txt   draft-ietf-6lo-dispatch-iana-registry-04.txt 
6lo S. Chakrabarti 6lo S. Chakrabarti
Internet-Draft Ericsson Internet-Draft Ericsson
Updates: 4944, 6282 (if approved) G. Montenegro Updates: 4944, 6282 (if approved) G. Montenegro
Intended status: Standards Track Microsoft Intended status: Standards Track Microsoft
Expires: October 9, 2016 R. Droms Expires: February 9, 2017 R. Droms
Cisco Cisco
J. Woodyatt J. Woodyatt
Nest Nest
April 7, 2016 August 8, 2016
IANA Registry for 6lowpan ESC Dispatch Code points 6lowpan ESC Dispatch Code Points and Guidelines
draft-ietf-6lo-dispatch-iana-registry-03 draft-ietf-6lo-dispatch-iana-registry-04
Abstract Abstract
RFC4944 defines ESC dispatch type for additional dispatch bytes in RFC4944 defines ESC dispatch type for additional dispatch bytes in
the 6lowpan header. The value of ESC byte has been updated by the 6lowpan header. The value of ESC byte has been updated by
RFC6282. However, the usage of ESC extension byte has not been RFC6282. However, the usage of ESC extension byte has not been
defined in RFC6282 and RFC4944. The purpose of this document is to defined in RFC6282 and RFC4944. This document updates RFC4944 and
define the ESC extension byte code points and to request RFC6282 by defining the ESC extension byte code points including
corresponding IANA actions. registration of entries for known use-cases at the time of writing of
this document.
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 October 9, 2016. This Internet-Draft will expire on February 9, 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 23 skipping to change at page 2, line 24
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Usage of ESC dispatch bytes . . . . . . . . . . . . . . . . . . 3 3. Usage of ESC dispatch bytes . . . . . . . . . . . . . . . . . . 3
3.1. Interaction with other RFC4944 implementations . . . . . . 4 3.1. Interaction with other RFC4944 implementations . . . . . . 4
3.2. ESC Extension Bytes Typical Sequence . . . . . . . . . . . 5 3.2. ESC Extension Bytes Typical Sequence . . . . . . . . . . . 5
3.3. ITU-T G.9903 ESC type usage . . . . . . . . . . . . . . . 5 3.3. ITU-T G.9903 ESC type usage . . . . . . . . . . . . . . . 5
3.4. NALP and ESC bytes . . . . . . . . . . . . . . . . . . . . 6 3.4. NALP and ESC bytes . . . . . . . . . . . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Normative References . . . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . . 8
7.2. Informative References . . . . . . . . . . . . . . . . . . 8 7.2. Informative References . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
[RFC4944] section 5.1 defines the dispatch header and types. The ESC [RFC4944] section 5.1 defines the dispatch header and types. The ESC
type is defined for using additional dispatch bytes in the 6lowpan type is defined for using additional dispatch bytes in the 6lowpan
header. RFC 6282 modifies the value of the ESC dispatch type and it header. RFC 6282 modifies the value of the ESC dispatch type and it
is recorded in IANA registry [6LOWPAN-IANA]. However, the bytes and is recorded in IANA registry [6LOWPAN-IANA]. However, the bytes and
usage following the ESC byte are not defined in either [RFC4944] and usage following the ESC byte are not defined in either [RFC4944] and
skipping to change at page 6, line 39 skipping to change at page 6, line 39
4. IANA Considerations 4. IANA Considerations
This document requests IANA to register the 'ESC Extension Type' This document requests IANA to register the 'ESC Extension Type'
values as per the policy 'Specification Required'[RFC5226] as values as per the policy 'Specification Required'[RFC5226] as
specified in this document which follows the same policy as in the specified in this document which follows the same policy as in the
IANA section of [RFC4944]. For each Extension Type (except the IANA section of [RFC4944]. For each Extension Type (except the
Reserved values) the specification MUST define corresponding Extended Reserved values) the specification MUST define corresponding Extended
Dispatch Payload frame bytes for the receiver implementation to read Dispatch Payload frame bytes for the receiver implementation to read
the ESC bytes with interoperability. the ESC bytes with interoperability.
[RFC5226] section 4.1 also indicates that "Specification Srequired"
implies a Designated expert review of the public specification which
is requesting registry for the ESC Extenstion Type values.
The allocation of code-points should follow the guidelines on "Usage
Of ESC Dispatch Bytes" and the typical example sections. ESC
Extension type code points MUST be used in conjunction with 6lo
protocols following [RFC4944] or its derivatives. The requesting
document MUST specify how the ESC dispatch bytes will be used along
with 6LOWPAN headers in their use-cases.
The initial values for the 'ESC Extension Type' fields are: The initial values for the 'ESC Extension Type' fields are:
+-------+---------------------------------+---------------+ +-------+---------------------------------+---------------+
| Value | Description | Reference | | Value | Description | Reference |
+-------+---------------------------------+---------------+ +-------+---------------------------------+---------------+
| 0 | Reserved for future use | This document | | 0 | Reserved for future use | This document |
| | | | | | | |
| 1-31 | Used by ITU-T G.9903 and G.9905 | ITU-T G.9903 &| | 1-31 | Used by ITU-T G.9903 and G.9905 | ITU-T G.9903 &|
| | Command IDs | ITU-T G.9905 | | | Command IDs | ITU-T G.9905 |
| | | | | | | |
skipping to change at page 7, line 39 skipping to change at page 7, line 42
6. Acknowledgements 6. Acknowledgements
The authors would like to thank the members of the 6lo WG members for The authors would like to thank the members of the 6lo WG members for
the comments in the mailing list. Many thanks to Carsten Bormann, the comments in the mailing list. Many thanks to Carsten Bormann,
Ralph Droms, Thierry Lys, Cedric Lavenu, Pascal Thubert for their Ralph Droms, Thierry Lys, Cedric Lavenu, Pascal Thubert for their
discussions regarding resolving the bits allocation issues which led discussions regarding resolving the bits allocation issues which led
to this document. Jonathan Hui and Robert Cregie provided extensive to this document. Jonathan Hui and Robert Cregie provided extensive
reviews and guidance for interoperability. The authors acknowledges reviews and guidance for interoperability. The authors acknowledges
the comments from the following people for shaping this document: the comments from the following people for shaping this document:
Paul Duffy, Don Sturek, Michael Richardson, Xavier Vilajosana and Paul Duffy, Don Sturek, Michael Richardson, Xavier Vilajosana and
Scott Mansfield. Scott Mansfield. Brian Haberman, our document shepherd helped us
modify the IANA section for guideline.
7. References 7. References
7.1. Normative References 7.1. Normative References
[4944-ERRATA] [4944-ERRATA]
"https://www.rfc-editor.org/errata_search.php?rfc=4944". "https://www.rfc-editor.org/errata_search.php?rfc=4944".
[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, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 8, line 24 skipping to change at page 8, line 30
Datagrams over IEEE 802.15.4-Based Networks", RFC 6282, Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,
DOI 10.17487/RFC6282, September 2011, DOI 10.17487/RFC6282, September 2011,
<http://www.rfc-editor.org/info/rfc6282>. <http://www.rfc-editor.org/info/rfc6282>.
7.2. Informative References 7.2. Informative References
[6LOWPAN-IANA] [6LOWPAN-IANA]
"https://www.iana.org/assignments/_6lowpan-parameters/ "https://www.iana.org/assignments/_6lowpan-parameters/
_6lowpan-parameters.xhtml". _6lowpan-parameters.xhtml".
[6loCHART]
"https://datatracker.ietf.org/wg/6lo/charter".
[G3-PLC] "http://www.itu.int/rec/T-REC-G.9903-201402-I". [G3-PLC] "http://www.itu.int/rec/T-REC-G.9903-201402-I".
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
Authors' Addresses Authors' Addresses
Samita Chakrabarti Samita Chakrabarti
 End of changes. 10 change blocks. 
12 lines changed or deleted 27 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/