| Internet-Draft | SCHC commands | March 2020 |
| Thubert | Expires 26 September 2020 | [Page] |
This document creates a registry for command and control rule values across technologies¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 26 September 2020.¶
Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
"Static Context Header Compression (SCHC) and fragmentation for LPWAN, application to UDP/IPv6" [SCHC] defines a generic compression and fragmentation protocol that is optimized for LPWAN networks.¶
SCHC needs to be instanciated to be applied to a particular networking technology. This is being done at the LPWAN WG for [LoRaWAN], [Sigfox], and [NB-IOT].¶
SCHC does not have to be limited to compression and fragmentation; it can be extended for other purposes, e.g., to transport commands and responses. The necessary commands appear to be very similar across technologies and it makes sense to create a shared IANA registry that is valid across technologies.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119][RFC8174] when, and only when, they appear in all capitals, as shown here.¶
This document creates a registry for command and control rule values across technologies. This does not mean that all technologies need to implement all the command and controls defined in the IANA registry that this document creates, either.¶
This specification only creates a registry. There is no security consideration about the registry itself.¶
This specification creates a new Subregistry for the LPWAN command and control values for use within the [SCHC] protocol.¶
| Value | Meaning | Reference |
| 0 | Reset | RFC THIS |
| 1 | Ack | RFC THIS |
| 2 | Rekey | RFC THIS |
TBD¶