idnits 2.17.1 draft-thubert-lpwan-command-reg-01.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 (25 March 2020) is 1483 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: A later version (-23) exists of draft-ietf-lpwan-schc-over-sigfox-01 == Outdated reference: A later version (-15) exists of draft-ietf-lpwan-schc-over-nbiot-01 == Outdated reference: A later version (-14) exists of draft-ietf-lpwan-schc-over-lorawan-05 Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). 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 Intended status: Standards Track 25 March 2020 5 Expires: 26 September 2020 7 Command and Control Registry for SCHC 8 draft-thubert-lpwan-command-reg-01 10 Abstract 12 This document creates a registry for command and control rule values 13 across technologies 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at https://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on 26 September 2020. 32 Copyright Notice 34 Copyright (c) 2020 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 39 license-info) in effect on the date of publication of this document. 40 Please review these documents carefully, as they describe your rights 41 and restrictions with respect to this document. Code Components 42 extracted from this document must include Simplified BSD License text 43 as described in Section 4.e of the Trust Legal Provisions and are 44 provided without warranty as described in the Simplified BSD License. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 49 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2.1. References . . . . . . . . . . . . . . . . . . . . . . . 2 51 2.2. BCP 14 . . . . . . . . . . . . . . . . . . . . . . . . . 2 52 3. Purpose of this document . . . . . . . . . . . . . . . . . . 2 53 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 54 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 55 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 3 56 7. Normative References . . . . . . . . . . . . . . . . . . . . 3 57 8. Informative References . . . . . . . . . . . . . . . . . . . 4 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 60 1. Introduction 62 "Static Context Header Compression (SCHC) and fragmentation for 63 LPWAN, application to UDP/IPv6" [SCHC] defines a generic compression 64 and fragmentation protocol that is optimized for LPWAN networks. 66 SCHC needs to be instanciated to be applied to a particular 67 networking technology. This is being done at the LPWAN WG for 68 [LoRaWAN], [Sigfox], and [NB-IOT]. 70 SCHC does not have to be limited to compression and fragmentation; it 71 can be extended for other purposes, e.g., to transport commands and 72 responses. The necessary commands appear to be very similar across 73 technologies and it makes sense to create a shared IANA registry that 74 is valid across technologies. 76 2. Terminology 78 2.1. References 80 2.2. BCP 14 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 84 "OPTIONAL" in this document are to be interpreted as described in BCP 85 14 [RFC2119][RFC8174] when, and only when, they appear in all 86 capitals, as shown here. 88 3. Purpose of this document 90 This document creates a registry for command and control rule values 91 across technologies. This does not mean that all technologies need 92 to implement all the command and controls defined in the IANA 93 registry that this document creates, either. 95 4. Security Considerations 97 This specification only creates a registry. There is no security 98 consideration about the registry itself. 100 5. IANA Considerations 102 This specification creates a new Subregistry for the LPWAN command 103 and control values for use within the [SCHC] protocol. 105 * Possible values are 8-bit unsigned integers (0..255). 107 * Registration procedure is "Standards Action" [RFC8126]. 109 * Initial allocation is as indicated in Table 1: 111 +-------+---------+-----------+ 112 | Value | Meaning | Reference | 113 +=======+=========+===========+ 114 | 0 | Reset | RFC THIS | 115 +-------+---------+-----------+ 116 | 1 | Ack | RFC THIS | 117 +-------+---------+-----------+ 118 | 2 | Rekey | RFC THIS | 119 +-------+---------+-----------+ 121 Table 1: Acceptance values 122 of the RPL Status 124 6. Acknowledgments 126 TBD 128 7. Normative References 130 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 131 Requirement Levels", BCP 14, RFC 2119, 132 DOI 10.17487/RFC2119, March 1997, 133 . 135 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 136 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 137 May 2017, . 139 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 140 Writing an IANA Considerations Section in RFCs", BCP 26, 141 RFC 8126, DOI 10.17487/RFC8126, June 2017, 142 . 144 [SCHC] Minaburo, A., Toutain, L., Gomez, C., Barthel, D., and J. 145 Zuniga, "Static Context Header Compression (SCHC) and 146 fragmentation for LPWAN, application to UDP/IPv6", Work in 147 Progress, Internet-Draft, draft-ietf-lpwan-ipv6-static- 148 context-hc-24, 5 December 2019, 149 . 152 8. Informative References 154 [Sigfox] Zuniga, J., Gomez, C., and L. Toutain, "SCHC over Sigfox 155 LPWAN", Work in Progress, Internet-Draft, draft-ietf- 156 lpwan-schc-over-sigfox-01, 4 November 2019, 157 . 160 [NB-IOT] Ramos, E. and A. Minaburo, "SCHC over NB-IoT", Work in 161 Progress, Internet-Draft, draft-ietf-lpwan-schc-over- 162 nbiot-01, 16 November 2019, . 165 [LoRaWAN] Gimenez, O. and I. Petrov, "Static Context Header 166 Compression (SCHC) over LoRaWAN", Work in Progress, 167 Internet-Draft, draft-ietf-lpwan-schc-over-lorawan-05, 20 168 December 2019, . 171 Author's Address 173 Pascal Thubert (editor) 174 Cisco Systems, Inc 175 Building D 176 45 Allee des Ormes - BP1200 177 06254 MOUGINS - Sophia Antipolis 178 France 180 Phone: +33 497 23 26 34 181 Email: pthubert@cisco.com