<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="_6tisch.xsl"?>
<?xml-model href="_6tisch.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="_6tisch">
  <title>IPv6 Over the TSCH Mode of IEEE 802.15.4 (6TiSCH)</title>
  <created>2018-08-20</created>
  <updated>2021-06-21</updated>

  <registry id="_6tisch-6p-version-numbers">
    <title>6P Version Numbers</title>
    <xref type="rfc" data="rfc8480"/>
    <registration_rule>IETF Review or IESG Approval</registration_rule>
    <note>In the 6top Protocol (6P) <xref type="rfc" data="rfc8480"/>, there is a 
field to identify the version of the protocol.  
This field is 4 bits in size.
    </note>
    <record date="2018-08-20">
      <value>0</value>
      <xref type="rfc" data="rfc8480"/>
    </record>
  </registry>
  
  <registry id="_6tisch-6p-message-types">
    <title>6P Message Types</title>
    <xref type="rfc" data="rfc8480"/>
    <registration_rule>IETF Review or IESG Approval</registration_rule>
    <note>In the 6top Protocol (6P) version 0 <xref type="rfc" data="rfc8480"/>, there 
is a field to identify the type of message.  This 
field is 2 bits in size.
    </note>
    <record date="2018-08-20">
      <value>b00</value>
      <description>REQUEST</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>b01</value>
      <description>RESPONSE</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>b10</value>
      <description>CONFIRMATION</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record>
      <value>b11</value>
      <description>Unassigned</description>
    </record>
  </registry>
  
  <registry id="_6tisch-6p-command-identifiers">
    <title>6P Command Identifiers</title>
    <xref type="rfc" data="rfc8480"/>
    <registration_rule>IETF Review or IESG Approval</registration_rule>
    <note>In the 6top Protocol (6P) version 0 <xref type="rfc" data="rfc8480"/>, there 
is a Code field which is 8 bits in size.  In a 6P 
Request, the value of this Code field is used to 
identify the command.
    </note>
    <record date="2018-08-20">
      <value>0</value>
      <description>Reserved</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>1</value>
      <description>ADD</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>2</value>
      <description>DELETE</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>3</value>
      <description>RELOCATE</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>4</value>
      <description>COUNT</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>5</value>
      <description>LIST</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>6</value>
      <description>SIGNAL</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>7</value>
      <description>CLEAR</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record>
      <value>8-254</value>
      <description>Unassigned</description>
    </record>
    <record date="2018-08-20">
      <value>255</value>
      <description>Reserved</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
  </registry>
  
  <registry id="_6tisch-6p-return-codes">
    <title>6P Return Codes</title>
    <xref type="rfc" data="rfc8480"/>
    <registration_rule>IETF Review or IESG Approval</registration_rule>
    <note>In the 6top Protocol (6P) version 0 <xref type="rfc" data="rfc8480"/>, there 
is a Code field which is 8 bits in size.  In a 6P 
Response or 6P Confirmation, the value of this Code 
field is used to identify the return code.
    </note>
    <record date="2018-08-20">
      <value>0</value>
      <name>RC_SUCCESS</name>
      <description>operation succeeded</description>
      <error>No</error>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>1</value>
      <name>RC_EOL</name>
      <description>end of list</description>
      <error>No</error>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>2</value>
      <name>RC_ERR</name>
      <description>generic error</description>
      <error>Yes</error>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>3</value>
      <name>RC_RESET</name>
      <description>critical error, reset</description>
      <error>Yes</error>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>4</value>
      <name>RC_ERR_VERSION</name>
      <description>unsupported 6P version</description>
      <error>Yes</error>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>5</value>
      <name>RC_ERR_SFID</name>
      <description>unsupported SFID</description>
      <error>Yes</error>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>6</value>
      <name>RC_ERR_SEQNUM</name>
      <description>schedule inconsistency</description>
      <error>Yes</error>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>7</value>
      <name>RC_ERR_CELLLIST</name>
      <description>cellList error</description>
      <error>Yes</error>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>8</value>
      <name>RC_ERR_BUSY</name>
      <description>busy</description>
      <error>Yes</error>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>9</value>
      <name>RC_ERR_LOCKED</name>
      <description>cells are locked</description>
      <error>Yes</error>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record>
      <value>10-255</value>
      <name>Unassigned</name>
      <description/>
      <error/>
    </record>
  </registry>
  
  <registry id="_6tisch-6p-scheduling-function-identifiers">
    <title>6P Scheduling Function Identifiers</title>
    <xref type="rfc" data="rfc8480"/>
    <range>
      <value>0-127</value>
      <registration_rule>IETF Review or IESG Approval</registration_rule>
    </range>
    <range>
      <value>128-255</value>
      <registration_rule>Expert Review</registration_rule>
    </range>
    <expert>Xavi Vilajosana Guillen, Thomas Watteyne</expert>
    <note>In the 6top Protocol (6P) version 0 <xref type="rfc" data="rfc8480"/>, there 
is a field to identify the scheduling function to 
handle the message.  This field is 8 bits in size.
    </note>
    <record date="2020-09-15">
      <value>0</value>
      <description>Minimal Scheduling Function (MSF)</description>
      <xref type="rfc" data="rfc9033"/>
    </record>
    <record>
      <value>1-255</value>
      <description>Unassigned</description>
    </record>
  </registry>
  
  <registry id="_6tisch-6p-celloptions-bitmap">
    <title>6P CellOptions Bitmap</title>
    <xref type="rfc" data="rfc8480"/>
    <registration_rule>IETF Review or IESG Approval</registration_rule>
    <note>In the 6top Protocol (6P) version 0 <xref type="rfc" data="rfc8480"/>, there 
is an optional CellOptions field which is 8 bits in 
size.
    </note>
    <record date="2018-08-20">
      <value>0</value>
      <description>TX (Transmit)</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>1</value>
      <description>RX (Receive)</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record date="2018-08-20">
      <value>2</value>
      <description>SHARED</description>
      <xref type="rfc" data="rfc8480"/>
    </record>
    <record>
      <value>3-7</value>
      <description>Unassigned</description>
    </record>
  </registry>
  
  <registry id="_6tisch-cojp-parameters">
    <title>Constrained Join Protocol (CoJP) Parameters</title>
    <xref type="rfc" data="rfc9031"/>
    <range>
      <value>Integer values less than -65536</value>
      <registration_rule>Private Use</registration_rule>
    </range>
    <range>
      <value>Integer values from -65536 to -257</value>
      <registration_rule>Specification Required</registration_rule>
    </range>
    <range>
      <value>Integer values from -256 to 255</value>
      <registration_rule>Standards Action</registration_rule>
    </range>
    <range>
      <value>Integer values from 256 to 65535</value>
      <registration_rule>Specification Required</registration_rule>
    </range>
    <range>
      <value>Integer values greater than 65535</value>
      <registration_rule>Expert Review</registration_rule>
    </range>
    <expert>Mališa Vučinić, Michael Richardson</expert>
    <record date="2019-12-23">
      <name>Reserved for Private Use</name>
      <value>less than -65536</value>
      <cbor/>
      <description/>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record>
      <name>Unassigned</name>
      <value>-65536 to 0</value>
      <cbor/>
      <description/>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>role</name>
      <value>1</value>
      <cbor>unsigned integer</cbor>
      <description>Identifies the role parameter</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>link-layer key set</name>
      <value>2</value>
      <cbor>array</cbor>
      <description>Identifies the array carrying one or more link-level 
      cryptographic keys</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>short identifier</name>
      <value>3</value>
      <cbor>array</cbor>
      <description>Identifies the assigned short identifier</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>JRC address</name>
      <value>4</value>
      <cbor>byte string</cbor>
      <description>Identifies the IPv6 address of of the JRC</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>network identifier</name>
      <value>5</value>
      <cbor>byte string</cbor>
      <description>Identifies the network identifier parameter</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>blacklist</name>
      <value>6</value>
      <cbor>array</cbor>
      <description>Identifies the blacklist parameter</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>join rate</name>
      <value>7</value>
      <cbor>unsigned integer</cbor>
      <description>Identifies the join rate parameter</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>unsupported configuration</name>
      <value>8</value>
      <cbor>array</cbor>
      <description>Identifies the unsupported configuration parameter</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
  </registry>
  
  <registry id="_6tisch-cojp-key-usage">
    <title>Constrained Join Protocol (CoJP) Key Usage</title>
    <xref type="rfc" data="rfc9031"/>
    <range>
      <value>Integer values less than -65536</value>
      <registration_rule>Private Use</registration_rule>
    </range>
    <range>
      <value>Integer values from -65536 to -257</value>
      <registration_rule>Specification Required</registration_rule>
    </range>
    <range>
      <value>Integer values from -256 to 255</value>
      <registration_rule>Standards Action</registration_rule>
    </range>
    <range>
      <value>Integer values from 256 to 65535</value>
      <registration_rule>Specification Required</registration_rule>
    </range>
    <range>
      <value>Integer values greater than 65535</value>
      <registration_rule>Expert Review</registration_rule>
    </range>
    <expert>Mališa Vučinić, Michael Richardson</expert>
    <record date="2019-12-23">
      <name>Reserved for Private Use</name>
      <value>less than -65536</value>
      <alg/>
      <description/>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record>
      <name>Unassigned</name>
      <value>-65536 to -1</value>
      <alg/>
      <description/>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K1K2-ENC-MIC32</name>
      <value>0</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use MIC-32 for EBs, ENC-MIC-32 for DATA and ACKNOWLEDGMENT.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K1K2-ENC-MIC64</name>
      <value>1</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use MIC-64 for EBs, ENC-MIC-64 for DATA and ACKNOWLEDGMENT.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K1K2-ENC-MIC128</name>
      <value>2</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use MIC-128 for EBs, ENC-MIC-128 for DATA and ACKNOWLEDGMENT.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K1K2-MIC32</name>
      <value>3</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use MIC-32 for EBs, DATA and ACKNOWLEDGMENT.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K1K2-MIC64</name>
      <value>4</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use MIC-64 for EBs, DATA and ACKNOWLEDGMENT.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K1K2-MIC128</name>
      <value>5</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use MIC-128 for EBs, DATA and ACKNOWLEDGMENT.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K1-MIC32</name>
      <value>6</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use MIC-32 for EBs.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K1-MIC64</name>
      <value>7</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use MIC-64 for EBs.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K1-MIC128</name>
      <value>8</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use MIC-128 for EBs.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K2-MIC32</name>
      <value>9</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use MIC-32 for DATA and ACKNOWLEDGMENT.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K2-MIC64</name>
      <value>10</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use MIC-64 for DATA and ACKNOWLEDGMENT.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K2-MIC128</name>
      <value>11</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use MIC-128 for DATA and ACKNOWLEDGMENT.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K2-ENC-MIC32</name>
      <value>12</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use ENC-MIC-32 for DATA and ACKNOWLEDGMENT.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K2-ENC-MIC64</name>
      <value>13</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use ENC-MIC-64 for DATA and ACKNOWLEDGMENT.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>6TiSCH-K2-ENC-MIC128</name>
      <value>14</value>
      <alg>IEEE802154-AES-CCM-128</alg>
      <description>Use ENC-MIC-128 for DATA and ACKNOWLEDGMENT.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
  </registry>
  
  <registry id="_6tisch-cojp-unsupported-configuration-codes">
    <title>Constrained Join Protocol (CoJP) Unsupported Configuration Codes</title>
    <xref type="rfc" data="rfc9031"/>
    <range>
      <value>Integer values less than -65536</value>
      <registration_rule>Private Use</registration_rule>
    </range>
    <range>
      <value>Integer values from -65536 to -257</value>
      <registration_rule>Specification Required</registration_rule>
    </range>
    <range>
      <value>Integer values from -256 to 255</value>
      <registration_rule>Standards Action</registration_rule>
    </range>
    <range>
      <value>Integer values from 256 to 65535</value>
      <registration_rule>Specification Required</registration_rule>
    </range>
    <range>
      <value>Integer values greater than 65535</value>
      <registration_rule>Expert Review</registration_rule>
    </range>
    <expert>Mališa Vučinić, Michael Richardson</expert>
    <record date="2019-12-23">
      <name>Reserved for Private Use</name>
      <value>less than -65536</value>
      <description/>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record>
      <name>Unassigned</name>
      <value>-65536 to -1</value>
      <description/>
      <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>Unsupported</name>
      <value>0</value>
      <description>The indicated setting is not supported by the networking 
        stack implementation.</description>
        <xref type="rfc" data="rfc9031"/>
    </record>
    <record date="2019-12-23">
      <name>Malformed</name>
      <value>1</value>
      <description>The indicated parameter value is malformed.</description>
      <xref type="rfc" data="rfc9031"/>
    </record>
  </registry>
  
  <people/>
</registry>
