<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="paws.xsl"?>
<?xml-model href="paws.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="paws">
  <title>Protocol to Access White-Space (PAWS)</title>
  <created>2014-11-13</created>
  <updated>2015-05-22</updated>
  
  
  
  <registry id="ruleset-id">
    <title>PAWS Ruleset ID Registry</title>
    <xref type="rfc" data="rfc7545"/>
    <registration_rule>Specification Required</registration_rule>
    <expert>Unassigned</expert>
    <record date="2014-11-13">
      <value>FccTvBandWhiteSpace-2010</value>
      <spec><xref type="uri" data="http://www.ecfr.gov/cgi-bin/text-idx?rgn=div6&amp;view=text&amp;node=47:1.0.1.1.16.8">FCC-CFR47-15H</xref></spec>
      <template><xref type="rfc" data="rfc7545"/> Section 9.1.2.1</template>
    </record>
    <record date="2014-11-13">
      <value>ETSI-EN-301-598-1.1.1</value>
      <spec><xref type="uri" data="http://www.etsi.org/deliver/etsi_en/301500_301599/301598/01.01.01_60/en_301598v010101p.pdf">ETSI-EN-301-598</xref></spec>
      <template><xref type="rfc" data="rfc7545"/> Section 9.1.2.2</template>
    </record>
  </registry>

  <registry id="parameters">
    <title>PAWS Parameters Registry</title>
    <xref type="rfc" data="rfc7545"/>
    <registration_rule>Specification Required</registration_rule>
    <expert>Unassigned</expert>
    <record date="2014-11-13">
      <name>fccId</name>
      <location>DeviceDescriptor (Section 5.2 of <xref type="rfc" data="rfc7545"/>)</location>
      <spec><xref type="rfc" data="rfc7545"/> Specifies the
      device's FCC certification identifier.  A valid FCC ID is limited
      to 19 characters in the ASCII value range, as proposed in FCC
      Administration Topics Review <xref type="uri" data="http://transition.fcc.gov/bureaus/oet/ea/presentations/files/oct12/2b-TCB-Admin-Issues-Oct-2012-GT.pdf">FCC-Review-2012-10</xref>.  For the
      purposes of the PAWS protocol, the maximum length of the fccId
      value is 32 octets.</spec>
    </record>
    <record date="2014-11-13">
      <name>fccTvbdDeviceType</name>
      <location>DeviceDescriptor (Section 5.2 of <xref type="rfc" data="rfc7545"/>)</location>
      <spec>Specifies the White Space Device type, as
      defined by the ETSI Harmonised Standard <xref type="uri" data="http://www.etsi.org/deliver/etsi_en/301500_301599/301598/01.01.01_60/en_301598v010101p.pdf">ETSI-EN-301-598</xref>.  Valid
      values are single-letter strings, such as "A", "B", etc.  Consult
      the documentation for details about the device types.</spec>
    </record>
    <record date="2014-11-13">
      <name>etsiEnDeviceType</name>
      <location>DeviceDescriptor (Section 5.2 of <xref type="rfc" data="rfc7545"/>)</location>
      <spec><xref type="rfc" data="rfc7545"/> Specifies the TV Band
      White Space device type, as defined by the FCC.  Valid values are
      "FIXED", "MODE_1", "MODE_2".</spec>
    </record>
    <record date="2014-11-13">
      <name>etsiEnTechnologyId</name>
      <location>DeviceDescriptor (Section 5.2 of <xref type="rfc" data="rfc7545"/>)</location>
      <spec>Specifies the White Space Device
      technology identifier, as defined by the ETSI Harmonised Standard
      <xref type="uri" data="http://www.etsi.org/deliver/etsi_en/301500_301599/301598/01.01.01_60/en_301598v010101p.pdf">ETSI-EN-301-598</xref>.  The maximum length of the string value is 64
      octets.  Consult the documentation for valid values.</spec>
    </record>
    <record date="2014-11-13">
      <name>etsiEnDeviceCategory</name>
      <location>DeviceDescriptor (Section 5.2 of <xref type="rfc" data="rfc7545"/>)</location>
      <spec>Specifies the White Space Device
      category, as defined by the ETSI Harmonised Standard
      <xref type="uri" data="http://www.etsi.org/deliver/etsi_en/301500_301599/301598/01.01.01_60/en_301598v010101p.pdf">ETSI-EN-301-598</xref>.  Valid values are the strings, "master" and
      "slave".  It is case insensitive.</spec>
    </record>
    <record date="2014-11-13">
      <name>etsiEnSimultaneousChannelOperationRestriction</name>
      <location>SpectrumSpec (Section 5.9 of <xref type="rfc" data="rfc7545"/>)</location>
      <spec>Specifies the constraint on the device
      maximum total EIRP, as defined by the ETSI Harmonised Standard
      <xref type="uri" data="http://www.etsi.org/deliver/etsi_en/301500_301599/301598/01.01.01_60/en_301598v010101p.pdf">ETSI-EN-301-598</xref>.  The values are represented by numeric strings,
      such as "0", "1", etc.  Consult the documentation for the
      specification of the power constraint corresponding to each
      parameter value.</spec>
    </record>
    <record date="2015-05-04">
      <name>etsiEnDeviceEmissionsClass</name>
      <location>DeviceDescriptor (Section 5.2 of <xref type="rfc" data="rfc7545"/>)</location>
      <spec>Specifies the white-space device
      emissions class, as defined by the ETSI Harmonised Standard
      <xref type="uri" data="http://www.etsi.org/deliver/etsi_en/301500_301599/301598/01.01.01_60/en_301598v010101p.pdf">ETSI-EN-301-598</xref>, that characterizes the out-of-block emissions
      of the device. The values are represented by numeric strings,
      such as "1", "2", "3", etc. Consult the documentation for details
      about emissions classes.</spec>
    </record>
  </registry>

  <registry id="error-codes">
    <title>PAWS Error Code Registry</title>
    <xref type="rfc" data="rfc7545"/>
    <registration_rule>Specification Required</registration_rule>
    <expert>Unassigned</expert>
    <note>Error code values range from -32768 to 32767, inclusive. See Section 5.17 
of <xref type="rfc" data="rfc7545"/>.
    </note>
    
    <record>
      <code>32767 to 1</code>
      <name>Unassigned</name>
      <description/>
    </record>
    <record date="2014-11-13">
      <code>0</code>
      <name>Reserved</name>
      <description/>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record>
      <code>-1 to -99</code>
      <name>Unassigned</name>
      <description/>
    </record>
    <record date="2014-11-13">
      <code>-100</code>
      <name>Reserved</name>
      <description/>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record date="2014-11-13">
      <code>-101</code>
      <name>VERSION</name>
      <description>The Database does not support the specified
version of the message. This error does not
use any additional data.</description>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record date="2014-11-13">
      <code>-102</code>
      <name>UNSUPPORTED</name>
      <description>The Database does not support the device. For                            example, it supports none of the ruleset
specified in the request or does not support
the device, based on its device type, model,
etc. This error does not use any additional
data.</description>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record date="2014-11-13">
      <code>-103</code>
      <name>UNIMPLEMENTED</name>
      <description>The Database does not implement the optional
request or optional feature. This error does
not use any additional data.</description>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record date="2014-11-13">
      <code>-104</code>
      <name>OUTSIDE_COVERAGE</name>
      <description>The specified geolocation is outside the
coverage area of the Database. The Database
MAY include a DbUpdateSpec (Section 5.7 of <xref type="rfc" data="rfc7545"/>) to
provide a list of alternate databases that
might be appropriate for the requested
location. See OUTSIDE_COVERAGE Error (Section
5.17.1 of <xref type="rfc" data="rfc7545"/>) for more details.</description>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record date="2014-11-13">
      <code>-105</code>
      <name>DATABASE_CHANGE</name>
      <description>The Database has changed its URI. The
Database MAY include a DbUpdateSpec (Section
5.7 of <xref type="rfc" data="rfc7545"/>) in the error response to provide devices
with one or more alternate database URIs. The
device needs to update its preconfigured
entry for the responding database with the
alternate databases listed in the
DbUpdateSpec. See DATABASE_CHANGE Error
(Section 5.17.2 of <xref type="rfc" data="rfc7545"/>) for more details.</description>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record>
      <code>-106 to -199</code>
      <name>Unassigned</name>
      <description/>
    </record>
    <record date="2014-11-13">
      <code>-200</code>
      <name>Reserved</name>
      <description/>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record date="2014-11-13">
      <code>-201</code>
      <name>MISSING</name>
      <description>A required parameter is missing. The Database
MUST include a list of the required parameter
names. The Database MAY include only names of
parameters that are missing, but MAY include
a full list.  Including the full list of
missing parameters may reduce the number of
re-queries from the device. See MISSING Error
(Section 5.17.3 of <xref type="rfc" data="rfc7545"/>) for more details.</description>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record date="2014-11-13">
      <code>-202</code>
      <name>INVALID_VALUE</name>
      <description>A parameter value is invalid in some way. The
Database SHOULD include a message indicating
which parameter and why its value is invalid.
This error does not use any additional data.</description>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record>
      <code>-203 to -299</code>
      <name>Unassigned</name>
      <description/>
    </record>
    <record date="2014-11-13">
      <code>-300</code>
      <name>Reserved</name>
      <description/>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record date="2014-11-13">
      <code>-301</code>
      <name>UNAUTHORIZED</name>
      <description>The device is not authorized to used the
Database. Authorization may be determined by
the ruleset or be dependent on prior
arrangement between the device and Database.
This error does not use any additional data.</description>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record date="2014-11-13">
      <code>-302</code>
      <name>NOT_REGISTERED</name>
      <description>Device registration required, but the device
is not registered.  This error does not use
any additional data.</description>
      <xref type="rfc" data="rfc7545"/>
    </record>
    <record>
      <code>-303 to -31999</code>
      <name>Unassigned</name>
      <description/>
    </record>
    <record date="2014-11-13">
      <code>-32000 to -32768</code>
      <name>Reserved</name>
      <description>Reserved for JSON-RPC error codes.</description>
      <xref type="rfc" data="rfc7545"/>
    </record>
  </registry>


  <people/>
</registry>
