idnits 2.17.00 (12 Aug 2021) /tmp/idnits52024/draft-thubert-lpwan-command-reg-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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC6550, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC8138, but the abstract doesn't seem to mention this, which it should. 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 (25 March 2020) is 787 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) == Outdated reference: draft-ietf-lpwan-ipv6-static-context-hc has been published as RFC 8724 == Outdated reference: A later version (-09) exists of draft-ietf-lpwan-schc-over-sigfox-01 == Outdated reference: A later version (-08) exists of draft-ietf-lpwan-schc-over-nbiot-01 == Outdated reference: draft-ietf-lpwan-schc-over-lorawan has been published as RFC 9011 Summary: 0 errors (**), 0 flaws (~~), 6 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 LPWAN P. Thubert, Ed. 3 Internet-Draft Cisco Systems 4 Updates: 6550, 8138 (if approved) 25 March 2020 5 Intended status: Standards Track 6 Expires: 26 September 2020 8 Configuration option for RFC 8138 9 draft-thubert-lpwan-command-reg-00 11 Abstract 13 This document creates a registry for command and control rule values 14 across technologies 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on 26 September 2020. 33 Copyright Notice 35 Copyright (c) 2020 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 40 license-info) in effect on the date of publication of this document. 41 Please review these documents carefully, as they describe your rights 42 and restrictions with respect to this document. Code Components 43 extracted from this document must include Simplified BSD License text 44 as described in Section 4.e of the Trust Legal Provisions and are 45 provided without warranty as described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2.1. References . . . . . . . . . . . . . . . . . . . . . . . 2 52 2.2. BCP 14 . . . . . . . . . . . . . . . . . . . . . . . . . 2 53 3. Purpose of this document . . . . . . . . . . . . . . . . . . 2 54 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 55 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 56 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 3 57 7. Normative References . . . . . . . . . . . . . . . . . . . . 3 58 8. Informative References . . . . . . . . . . . . . . . . . . . 4 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 61 1. Introduction 63 2. Terminology 65 2.1. References 67 2.2. BCP 14 69 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 70 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 71 "OPTIONAL" in this document are to be interpreted as described in BCP 72 14 [RFC2119][RFC8174] when, and only when, they appear in all 73 capitals, as shown here. 75 3. Purpose of this document 77 "Static Context Header Compression (SCHC) and fragmentation for 78 LPWAN, application to UDP/IPv6" [SCHC] defines a generic compression 79 and fragmentation protocol that is optimized for LPWAN networks. 81 SCHC needs to be instanciated to be applied to a particular 82 networking technology. This is being done at the LPWAN WG for 83 [LoRaWAN], [Sigfox], and [NB-IOT]. 85 SCHC does not have to be limited to compression and fragmentation; it 86 can be extended for other purposes, e.g., to transport commands and 87 responses. The necessary commands appear to be very similar across 88 technologies and it makes sense to create a share IANA registry that 89 is valid across technologies. It does not mean that all technologies 90 need to implement all the command and controls defined in the IANA 91 registry that this document creates, either. 93 4. Security Considerations 95 This specification creates a registry. There is no security 96 consideration about the registry itself. 98 5. IANA Considerations 100 This specification creates a new Subregistry for the LPWAN command 101 and control values for use within the [SCHC] protocol. 103 * Possible values are 8-bit unsigned integers (0..255). 105 * Registration procedure is "Standards Action" [RFC8126]. 107 * Initial allocation is as indicated in Table 1: 109 +-------+---------+-----------+ 110 | Value | Meaning | Reference | 111 +=======+=========+===========+ 112 | 0 | Reset | RFC THIS | 113 +-------+---------+-----------+ 114 | 1 | Ack | RFC THIS | 115 +-------+---------+-----------+ 116 | 2 | Rekey | RFC THIS | 117 +-------+---------+-----------+ 119 Table 1: Acceptance values 120 of the RPL Status 122 6. Acknowledgments 124 TBD 126 7. Normative References 128 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 129 Requirement Levels", BCP 14, RFC 2119, 130 DOI 10.17487/RFC2119, March 1997, 131 . 133 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 134 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 135 May 2017, . 137 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 138 Writing an IANA Considerations Section in RFCs", BCP 26, 139 RFC 8126, DOI 10.17487/RFC8126, June 2017, 140 . 142 [SCHC] Minaburo, A., Toutain, L., Gomez, C., Barthel, D., and J. 143 Zuniga, "Static Context Header Compression (SCHC) and 144 fragmentation for LPWAN, application to UDP/IPv6", Work in 145 Progress, Internet-Draft, draft-ietf-lpwan-ipv6-static- 146 context-hc-24, 5 December 2019, 147 . 150 8. Informative References 152 [Sigfox] Zuniga, J., Gomez, C., and L. Toutain, "SCHC over Sigfox 153 LPWAN", Work in Progress, Internet-Draft, draft-ietf- 154 lpwan-schc-over-sigfox-01, 4 November 2019, 155 . 158 [NB-IOT] Ramos, E. and A. Minaburo, "SCHC over NB-IoT", Work in 159 Progress, Internet-Draft, draft-ietf-lpwan-schc-over- 160 nbiot-01, 16 November 2019, . 163 [LoRaWAN] Gimenez, O. and I. Petrov, "Static Context Header 164 Compression (SCHC) over LoRaWAN", Work in Progress, 165 Internet-Draft, draft-ietf-lpwan-schc-over-lorawan-05, 20 166 December 2019, . 169 Author's Address 171 Pascal Thubert (editor) 172 Cisco Systems, Inc 173 Building D 174 45 Allee des Ormes - BP1200 175 06254 MOUGINS - Sophia Antipolis 176 France 178 Phone: +33 497 23 26 34 179 Email: pthubert@cisco.com