Data Model for Static Context Header Compression (SCHC)Acklio1137A avenue des Champs Blancs35510 Cesson-Sevigne CedexFranceana@ackl.ioInstitut MINES TELECOM; IMT Atlantique2 rue de la ChataigneraieCS 1760735576 Cesson-Sevigne CedexFranceLaurent.Toutain@imt-atlantique.frlpwan Working GroupThis document describes a YANG data model for the SCHC (Static Context Header Compression)
compression and fragmentation rules.SCHC is a compression and fragmentation mechanism for constrained networks defined in .
It is based on a static context shared by two entities at the boundary of the constrained network.
provides a non formal representation of the rules used either for compression/decompression (or C/D)
or fragmentation/reassembly (or F/R). The goal of this document is to formalize the description of the rules to offer:the same definition on both ends, even if the internal representation is different.an update of the other end to set up some specific values (e.g. IPv6 prefix, destination address,…)… illustrates the exchange of rules using the YANG data model.This document defines a YANG module to represent both compression and fragmentation rules, which leads to common representation for values for all the rules elements.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 when, and only when, they
appear in all capitals, as shown here.This document defines a YANG module to represent both compression and fragmentation rules, which leads to common representation for values for all the rules elements.SCHC compression is generic, the main mechanism does not refer
to a specific protocol. Any header field is abstracted through an ID, a position, a direction, and a value that can be a numerical
value or a string. and specify fields for IPv6 , UDP, CoAP including options definied for no serveur response and OSCORE . For the latter splits this field into sub-fields.SCHC fragmentation requires a set of common parameters that are included in a rule. These parameters are defined in .The YANG data model allows to select the compression or the fragmentation using the feature command. proposes a non formal representation of the compression rule.
A compression context for a device is composed of a set of rules. Each rule contains information to
describe a specific field in the header to be compressed.Identifier used in the SCHC YANG data model are from the identityref statement to ensure to be globally unique and be easily augmented if needed. The principle to define a new type based on a group of identityref is the following:define a main identity ending with the keyword base-type.derive all the identities used in the Data Model from this base type.create a typedef from this base type.The example () shows how an identityref is created for RCS (Reassembly Check Sequence) algorithms used during SCHC fragmentation.In the process of compression, the headers of the original packet are first parsed to create a list of fields. This list of fields is matched against the rules to find the appropriate rule and apply compression. does not state how the field ID value is constructed.
In examples, identification is done through a string indexed by the protocol name (e.g. IPv6.version, CoAP.version,…).The current YANG data model includes fields definitions found in , .Using the YANG data model, each field MUST be identified through a global YANG identityref.
A YANG field ID for the protocol is always derived from the fid-base-type. Then an identity
for each protocol is specified using the naming convention fid-<<protocol name»-base-type.
All possible fields for this protocol MUST derive from the protocol identity. The naming
convention is “fid” followed by the protocol name and the field name. If a field has
to be divided into sub-fields, the field identity serves as a base.The full field-id definition is found in . A type is defined for IPv6 protocol, and each
field is based on it. Note that the DiffServ bits derives from the Traffic Class identity.Field length is either an integer giving the size of a field in bits or a specific function. defines the
“var” function which allows variable length fields (whose length is expressed in bytes) and defines the “tkl” function for managing the CoAP
Token length field.The naming convention is “fl” followed by the function name.The field length function can be defined as an identityref as described in . Therefore, the type for field length is a union between an integer giving in bits the size of the length and the identityref.Field position is a positive integer which gives the position of a field, the default value is 1, and incremented at each repetition.
value 0 indicates that the position is not important and is not considered during the rule selection process.Field position is a positive integer. The type is an uint8.The Direction Indicator (di) is used to tell if a field appears in both direction (Bi) or only uplink (Up) or Downlink (Dw). The naming convention is “di” followed by the Direction Indicator name.The type is “di-type”.The Target Value is a list of binary sequences of any length, aligned to the left. In the rule, the structure will be used as a list, with index as a key. The highest index value is used to compute the size of the index sent in residue for the match-mapping CDA (Compression Decompression Action). The index allows to specify several values:For Equal and LSB, Target Value contains a single element. Therefore, the index is set to 0.For match-mapping, Target Value can contain several elements. Index values MUST start from 0 and MUST be contiguous.If the header field contains a text, the binary sequence uses the same enconding.Matching Operator (MO) is a function applied between a field value provided by the parsed header and the target value. defines 4 MO.The naming convention is “mo” followed by the MO name.The type is “mo-type”They are viewed as a list, built with a tv-struct (see chapter ).Compression Decompression Action (CDA) identifies the function to use for compression or decompression.
defines 6 CDA.The naming convention is “cda” followed by the CDA name.Currently no CDA requires arguments, but in the future some CDA may require one or several arguments.
They are viewed as a list, of target-value type.Fragmentation is optional in the data model and depends on the presence of the “fragmentation” feature.Most of the fragmentation parameters are listed in Annex D of .Since fragmentation rules work for a specific direction, they MUST contain a mandatory direction indicator.
The type is the same as the one used in compression entries, but bidirectional MUST NOT be used. defines 3 fragmentation modes:No Ack: this mode is unidirectionnal, no acknowledgment is sent back.Ack Always: each fragmentation window must be explicitly acknowledged before going to the next.Ack on Error: A window is acknowledged only when the receiver detects some missing fragments.The type is “fragmentation-mode-type”.
The naming convention is “fragmentation-mode” followed by the fragmentation mode name.A data fragment header, starting with the rule ID can be sent on the fragmentation direction.
indicates that the SCHC header may be composed of (cf. ):a Datagram Tag (Dtag) identifying the datagram being fragmented if the fragmentation applies concurrently on several datagrams. This field in optional and its length is defined by the rule.a Window (W) used in Ack-Always and Ack-on-Error modes. In Ack-Always, its size is 1. In Ack-on-Error, it depends on the rule. This field is not needed in No-Ack mode.a Fragment Compressed Number (FCN) indicating the fragment/tile position within the window. This field is mandatory on all modes defined in , its size is defined by the rule.The last fragment of a datagram is sent with an RCS (Reassembly Check Sequence) field to detect residual
transmission error and possible losses in the last window. defines a single algorithm based on Ethernet
CRC computation.The naming convention is “rcs” followed by the algorithm name.For Ack-on-Error mode, the All-1 fragment may just contain the RCS or can include a tile. The parameters defines the
behavior:all-1-data-no: the last fragment contains no data, just the RCSall-1-data-yes: the last fragment includes a single tile and the RCSall-1-data-sender-choice: the last fragment may or may not contain a single tile. The receiver can detect if a tile is present.The naming convention is “all-1-data” followed by the behavior identifier.The acknowledgment fragment header goes in the opposite direction of data. defines the header, composed of (see ):a Dtag (if present).a mandatory window as in the data fragment.a C bit giving the status of RCS validation. In case of failure, a bitmap follows, indicating the received tile.For Ack-on-Error, SCHC defines when an acknowledgment can be sent. This can be at any time defined by the layer 2, at the end of a window (FCN all-0)
or as a response to receiving the last fragment (FCN all-1). The naming convention is “ack-behavior” followed by the algorithm name.The state machine requires some common values to handle correctly fragmentation.retransmission-timer gives the duration before sending an ack request (cf. section 8.2.2.4. of ). If specified, value must be strictly positive.inactivity-timer gives the duration before aborting a fragmentation session (cf. section 8.2.2.4. of ). The value 0 explicitly indicates that this timer is disabled. do not specified any range for these timers. recommends a duration of 12 hours. In fact, the value range sould be between milliseconds for real time systems to several days. To allow a large range of applications, two parameters must be specified:the duration of a tick. It is computed by this formula 2^tick-duration/10^6. When tick-duration is set to 0, the unit is the microsecond. The default value of 20 leads to a unit of 1.048575 second. A value of 32 leads to a tick duration of about 1 hour 11 minutes.the number of ticks in the predefined unit. With the default tick-duration value of 20, the timers can cover a range between 1.0 sec and 19 hours covering recommandation.The SCHC fragmentation protocol specifies the the number of attempts before aborting through the parameter:max-ack-requests (cf. section 8.2.2.4. of ).The data model includes two parameters needed for fragmentation:l2-word-size: base fragmentation, in bits, on a layer 2 word which can be of any length. The default value is 8 and correspond
to the default value for byte aligned layer 2. A value of 1 will indicate that there is no alignment and no need for padding.maximum-packet-size: defines the maximum size of a uncompressed datagram. By default, the value is set to 1280 bytes.They are defined as unsigned integer, see .A rule is idenfied by a unique rule identifier (rule ID) comprising both a Rule ID value and a Rule ID length.
The YANG grouping rule-id-type defines the structure used to represent a rule ID. A length of 0 is allowed to represent an implicit rule.Three types of rules are defined in :Compression: a compression rule is associated with the rule ID.No compression: this identifies the default rule used to send a packet in extenso when no compression rule was found (see section 6).Fragmentation: fragmentation parameters are associated with the rule ID. Fragmentation is optional and feature “fragmentation” should be set.To access a specific rule, the rule ID length and value are used as a key. The rule is either
a compression or a fragmentation rule.A compression rule is composed of entries describing its processing. An entry contains all the information defined in with the types defined above.The compression rule described is defined by compression-content. It defines a list of
compression-rule-entry, indexed by their field id, position and direction. The compression-rule-entry
element represent a line of the table . Their type reflects the identifier types defined in
Some checks are performed on the values:target value must be present for MO different from ignore.when MSB MO is specified, the matching-operator-value must be presentA Fragmentation rule is composed of entries describing the protocol behavior. Some on them are numerical entries,
others are identifiers defined in .This section records the status of known implementations of the
protocol defined by this specification at the time of posting of
this Internet-Draft, and is based on a proposal described in
. The description of implementations in this section is
intended to assist the IETF in its decision processes in
progressing drafts to RFCs. Please note that the listing of any
individual implementation here does not imply endorsement by the
IETF. Furthermore, no effort has been spent to verify the
information presented here that was supplied by IETF contributors.
This is not intended as, and must not be construed to be, a
catalog of available implementations or their features. Readers
are advised to note that other implementations may exist.According to , “this will allow reviewers and working
groups to assign due consideration to documents that have the
benefit of running code, which may serve as evidence of valuable
experimentation and feedback that have made the implemented
protocols more mature. It is up to the individual working groups
to use this information as they see fit”.Openschc is implementing the conversion between the local rule
representation and the representation conform to the data model
in JSON and CBOR (following -08 draft).This document registers one URIs and one YANG modules.This document requests IANA to register the following four URIs in the “IETF XML Registry” :URI: urn:ietf:params:xml:ns:yang:ietf-schcRegistrant Contact: The IESG.XML: N/A; the requested URI is an XML namespace.This document registers the following four YANG modules in the “YANG Module Names” registry .name: ietf-schcnamespace: urn:ietf:params:xml:ns:yang:ietf-schcprefix: schcreference: RFC XXXX Data Model for Static Context Header Compression (SCHC)The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF or RESTCONF . The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS
.The Network Configuration Access Control Model (NACM) provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content.This data model formalizes the rules elements described in for compression and fragmentation. As explained in the architecture document , a rule can be read, created, updated or deleted in response to a management request. These actions can be done between two instances of SCHC or between a SCHC instance and a rule repository.The rule contains some sensible informations such as the application IPv6 address. An attacker by changing a rule content may block the communication or intercept the traffic. Therefore, the identity of the requester must be validated. This can be done through certificates or access lists.The full tree is sensitive, since it represents all the elements that can be managed. This module aims to be encapsulated into a YANG module including access right and identities.The authors would like to thank Dominique Barthel, Carsten Bormann, Ivan Martinez, Alexander Pelov for their careful reading and valuable inputs. A special thanks for
Carl Moberg, Tom Petch
and Eric Vyncke for their explanations and wise advices when building the model.User Datagram ProtocolKey words for use in RFCs to Indicate Requirement LevelsIn many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.The IETF XML RegistryThis document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]The Constrained Application Protocol (CoAP)The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation.CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments.Constrained Application Protocol (CoAP) Option for No Server ResponseThere can be machine-to-machine (M2M) scenarios where server responses to client requests are redundant. This kind of open-loop exchange (with no response path from the server to the client) may be desired to minimize resource consumption in constrained systems while updating many resources simultaneously or performing high-frequency updates. CoAP already provides Non-confirmable (NON) messages that are not acknowledged by the recipient. However, the request/response semantics still require the server to respond with a status code indicating "the result of the attempt to understand and satisfy the request", per RFC 7252.This specification introduces a CoAP option called 'No-Response'. Using this option, the client can explicitly express to the server its disinterest in all responses against the particular request. This option also provides granular control to enable expression of disinterest to a particular response class or a combination of response classes. The server MAY decide to suppress the response by not transmitting it back to the client according to the value of the No-Response option in the request. This option may be effective for both unicast and multicast requests. This document also discusses a few examples of applications that benefit from this option.Ambiguity of Uppercase vs Lowercase in RFC 2119 Key WordsRFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.Internet Protocol, Version 6 (IPv6) SpecificationThis document specifies version 6 of the Internet Protocol (IPv6). It obsoletes RFC 2460.Object Security for Constrained RESTful Environments (OSCORE)This document defines Object Security for Constrained RESTful Environments (OSCORE), a method for application-layer protection of the Constrained Application Protocol (CoAP), using CBOR Object Signing and Encryption (COSE). OSCORE provides end-to-end protection between endpoints communicating using CoAP or CoAP-mappable HTTP. OSCORE is designed for constrained nodes and networks supporting a range of proxy operations, including translation between different transport protocols.Although an optional functionality of CoAP, OSCORE alters CoAP options processing and IANA registration. Therefore, this document updates RFC 7252.SCHC: Generic Framework for Static Context Header Compression and FragmentationThis document defines the Static Context Header Compression and fragmentation (SCHC) framework, which provides both a header compression mechanism and an optional fragmentation mechanism. SCHC has been designed with Low-Power Wide Area Networks (LPWANs) in mind.SCHC compression is based on a common static context stored both in the LPWAN device and in the network infrastructure side. This document defines a generic header compression mechanism and its application to compress IPv6/UDP headers.This document also specifies an optional fragmentation and reassembly mechanism. It can be used to support the IPv6 MTU requirement over the LPWAN technologies. Fragmentation is needed for IPv6 datagrams that, after SCHC compression or when such compression was not possible, still exceed the Layer 2 maximum payload size.The SCHC header compression and fragmentation mechanisms are independent of the specific LPWAN technology over which they are used. This document defines generic functionalities and offers flexibility with regard to parameter settings and mechanism choices. This document standardizes the exchange over the LPWAN between two SCHC entities. Settings and choices specific to a technology or a product are expected to be grouped into profiles, which are specified in other documents. Data models for the context and profiles are out of scope.Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)This document defines how to compress Constrained Application Protocol (CoAP) headers using the Static Context Header Compression and fragmentation (SCHC) framework. SCHC defines a header compression mechanism adapted for Constrained Devices. SCHC uses a static description of the header to reduce the header's redundancy and size. While RFC 8724 describes the SCHC compression and fragmentation framework, and its application for IPv6/UDP headers, this document applies SCHC to CoAP headers. The CoAP header structure differs from IPv6 and UDP, since CoAP uses a flexible header with a variable number of options, themselves of variable length. The CoAP message format is asymmetric: the request messages have a header format different from the format in the response messages. This specification gives guidance on applying SCHC to flexible headers and how to leverage the asymmetry for more efficient compression Rules.Network Configuration Protocol (NETCONF)The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK]RESTCONF ProtocolThis document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).Using the NETCONF Protocol over Secure Shell (SSH)This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK]The Transport Layer Security (TLS) Protocol Version 1.3This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations.Network Configuration Access Control ModelThe standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.This document obsoletes RFC 6536.Improving Awareness of Running Code: The Implementation Status SectionThis document describes a simple process that allows authors of Internet-Drafts to record the status of known implementations by including an Implementation Status section. This will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature.This process is not mandatory. Authors of Internet-Drafts are encouraged to consider using the process for their documents, and working groups are invited to think about applying the process to all of their protocol specifications. This document obsoletes RFC 6982, advancing it to a Best Current Practice.The YANG 1.1 Data Modeling LanguageYANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF).Static Context Header Compression and Fragmentation (SCHC) over LoRaWANThe Static Context Header Compression and fragmentation (SCHC) specification (RFC 8724) describes generic header compression and fragmentation techniques for Low-Power Wide Area Network (LPWAN) technologies. SCHC is a generic mechanism designed for great flexibility so that it can be adapted for any of the LPWAN technologies.This document defines a profile of SCHC (RFC 8724) for use in LoRaWAN networks and provides elements such as efficient parameterization and modes of operation.LPWAN Static Context Header Compression (SCHC) ArchitectureAcklioCisco SystemsAcklio This document defines the LPWAN SCHC architecture.