idnits 2.17.00 (12 Aug 2021) /tmp/idnits13912/draft-bormann-6lo-coap-802-15-ie-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (April 03, 2016) is 2232 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'I-D.wang-6tisch-6top-coapie' is defined on line 174, but no explicit reference was found in the text == Outdated reference: draft-kivinen-802-15-ie has been published as RFC 8137 ** Downref: Normative reference to an Informational draft: draft-kivinen-802-15-ie (ref. 'I-D.kivinen-802-15-ie') Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 6Lo C. Bormann 3 Internet-Draft Universitaet Bremen TZI 4 Intended status: Standards Track April 03, 2016 5 Expires: October 5, 2016 7 Constrained Application Protocol (CoAP) over IEEE 802.15.4 Information 8 Element for IETF 9 draft-bormann-6lo-coap-802-15-ie-00.txt 11 Abstract 13 IEEE Std. 802.15.4-2015 defines Information Elements (IE), and draft- 14 kivinen-802-15-ie defines a framework for using these IEs in IETF 15 protocols. 17 The present specification defines a way to transport CoAP messages in 18 IEs. This can be used to perform CoAP exchanges with neighboring 19 IEEE 802.15.4 nodes before there is IP connectivity, e.g., to 20 configure that IP connectivity. 22 draft-wang-6tisch-6top-coapie demonstrates example applications of 23 this for 6TiSCH. Other areas of application are conceivable even in 24 classic 6LoWPAN networks. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on October 5, 2016. 43 Copyright Notice 45 Copyright (c) 2016 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 62 2. CoAP over IETF IE . . . . . . . . . . . . . . . . . . . . . . 2 63 3. Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 65 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 66 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 67 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 7.1. Normative References . . . . . . . . . . . . . . . . . . 4 69 7.2. Informative References . . . . . . . . . . . . . . . . . 4 70 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 72 1. Introduction 74 (See abstract for now.) 76 1.1. Terminology 78 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 79 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 80 "OPTIONAL" in this document are to be interpreted as described in RFC 81 2119 [RFC2119]. 83 In this specification, the term "byte" is used in its now customary 84 sense as a synonym for "octet". 86 2. CoAP over IETF IE 88 The format of the IETF IE is defined in [I-D.kivinen-802-15-ie] as 89 follows: 91 1 2 3 92 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 93 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 94 | Sub-Type ID | | 95 +-+-+-+-+-+-+-+-+ | 96 ~ Sub-Type Content ~ 97 | | 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 100 IETF IE Subtype Format 102 Here, Sub-Type ID is the IANA allocated number specifying the sub- 103 type of the IETF IE. The CoAP message is embedded in the IETF IE as 104 follows: 106 1 2 3 107 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 |Ver| T | TKL | Code | Message ID | 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 111 | Token (if any, TKL bytes) ... 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | Options (if any) ... 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 |1 1 1 1 1 1 1 1| Payload (if any) ... 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 118 IETF IE Subtype Format for CoAP 120 This means that the combinations of Ver, T, TKL used by CoAP need to 121 be allocated as Sub-Type IDs. Ver is always 1; T can be 0, 1, 2, 3, 122 and TKL can be between 0 and 8 for T in 0..2 and 0 only for T = 3. 123 This means that 3*9+1 = 28 Sub-Type IDs are needed. 125 3. Benefits 127 Allocating 11 % of the code points (28 out of the 256) available for 128 IETF IEs may seem like a large chunk. However, it enables the 129 embedding of CoAP messages into IEs in an efficient way; any smaller 130 allocation would need additional complexity for variable length 131 encoding or would even always need an additional byte of overhead. 133 4. IANA Considerations 135 This specification requests IANA to assign the following 28 code 136 points in the registry for IETF IE Sub-type IDs to this 137 specification: 139 +--------+-------------+ 140 | Value | Sub-type ID | 141 +--------+-------------+ 142 | 64-72 | CoAP | 143 | 80-88 | CoAP | 144 | 96-104 | CoAP | 145 | 112 | CoAP | 146 +--------+-------------+ 148 5. Security Considerations 150 The security considerations of [I-D.kivinen-802-15-ie] apply. 151 Specifically, this means that object security (intrinsic in the 152 resources accessed or explicit on the CoAP level) may be required. 154 6. Acknowledgments 156 Much of the text here is taken from [I-D.kivinen-802-15-ie]. 158 7. References 160 7.1. Normative References 162 [I-D.kivinen-802-15-ie] 163 Kivinen, T. and P. Kinney, "IEEE 802.15.4 Information 164 Element for IETF", draft-kivinen-802-15-ie-00 (work in 165 progress), March 2016. 167 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 168 Requirement Levels", BCP 14, RFC 2119, 169 DOI 10.17487/RFC2119, March 1997, 170 . 172 7.2. Informative References 174 [I-D.wang-6tisch-6top-coapie] 175 Wang, Q., Vilajosana, X., Watteyne, T., Sudhaakar, R., and 176 P. Zand, "Transporting CoAP Messages over IEEE802.15.4e 177 Information Elements", draft-wang-6tisch-6top-coapie-01 178 (work in progress), July 2015. 180 Author's Address 181 Carsten Bormann 182 Universitaet Bremen TZI 183 Postfach 330440 184 Bremen D-28359 185 Germany 187 Phone: +49-421-218-63921 188 Email: cabo@tzi.org