draft-ietf-paws-protocol-09.txt   draft-ietf-paws-protocol-10.txt 
PAWS V. Chen, Ed. PAWS V. Chen, Ed.
Internet-Draft Google Internet-Draft Google
Intended status: Standards Track S. Das Intended status: Standards Track S. Das
Expires: August 3, 2014 Applied Communication Sciences Expires: August 7, 2014 Applied Communication Sciences
L. Zhu L. Zhu
Huawei Huawei
J. Malyar J. Malyar
iconectiv (formerly Telcordia iconectiv (formerly Telcordia
Interconnection Solutions) Interconnection Solutions)
P. McCann P. McCann
Huawei Huawei
January 30, 2014 February 3, 2014
Protocol to Access White-Space (PAWS) Databases Protocol to Access White-Space (PAWS) Databases
draft-ietf-paws-protocol-09 draft-ietf-paws-protocol-10
Abstract Abstract
Portions of the radio spectrum that are allocated to licensees are Portions of the radio spectrum that are allocated to licensees are
available for non-interfering use. This available spectrum is called available for non-interfering use. This available spectrum is called
"White Space." Allowing secondary users access to available spectrum "White Space." Allowing secondary users access to available spectrum
"unlocks" existing spectrum to maximize its utilization and to "unlocks" existing spectrum to maximize its utilization and to
provide opportunities for innovation, resulting in greater overall provide opportunities for innovation, resulting in greater overall
spectrum utilization. spectrum utilization.
skipping to change at page 1, line 49 skipping to change at page 1, line 49
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 3, 2014. This Internet-Draft will expire on August 7, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 18 skipping to change at page 3, line 18
5.9. SpectrumSpec . . . . . . . . . . . . . . . . . . . . . . 36 5.9. SpectrumSpec . . . . . . . . . . . . . . . . . . . . . . 36
5.10. SpectrumSchedule . . . . . . . . . . . . . . . . . . . . 38 5.10. SpectrumSchedule . . . . . . . . . . . . . . . . . . . . 38
5.11. Spectrum . . . . . . . . . . . . . . . . . . . . . . . . 38 5.11. Spectrum . . . . . . . . . . . . . . . . . . . . . . . . 38
5.12. SpectrumProfile . . . . . . . . . . . . . . . . . . . . . 41 5.12. SpectrumProfile . . . . . . . . . . . . . . . . . . . . . 41
5.13. FrequencyRange . . . . . . . . . . . . . . . . . . . . . 42 5.13. FrequencyRange . . . . . . . . . . . . . . . . . . . . . 42
5.14. EventTime . . . . . . . . . . . . . . . . . . . . . . . . 42 5.14. EventTime . . . . . . . . . . . . . . . . . . . . . . . . 42
5.15. GeoSpectrumSpec . . . . . . . . . . . . . . . . . . . . . 43 5.15. GeoSpectrumSpec . . . . . . . . . . . . . . . . . . . . . 43
5.16. DeviceValidity . . . . . . . . . . . . . . . . . . . . . 44 5.16. DeviceValidity . . . . . . . . . . . . . . . . . . . . . 44
5.17. Error Element . . . . . . . . . . . . . . . . . . . . . . 44 5.17. Error Element . . . . . . . . . . . . . . . . . . . . . . 44
5.17.1. OUTSIDE_COVERAGE Error . . . . . . . . . . . . . . . 46 5.17.1. OUTSIDE_COVERAGE Error . . . . . . . . . . . . . . . 46
5.17.2. DATABASE_CHANGE Error . . . . . . . . . . . . . . . . 46 5.17.2. DATABASE_CHANGE Error . . . . . . . . . . . . . . . . 47
5.17.3. REQUIRED Error . . . . . . . . . . . . . . . . . . . 47 5.17.3. REQUIRED Error . . . . . . . . . . . . . . . . . . . 47
6. Message Encoding . . . . . . . . . . . . . . . . . . . . . . 47 6. Message Encoding . . . . . . . . . . . . . . . . . . . . . . 48
6.1. JSON-RPC Binding . . . . . . . . . . . . . . . . . . . . 48 6.1. JSON-RPC Binding . . . . . . . . . . . . . . . . . . . . 48
6.2. init Method . . . . . . . . . . . . . . . . . . . . . . . 49 6.2. init Method . . . . . . . . . . . . . . . . . . . . . . . 49
6.2.1. INIT_REQ Parameters . . . . . . . . . . . . . . . . . 49 6.2.1. INIT_REQ Parameters . . . . . . . . . . . . . . . . . 50
6.2.2. INIT_RESP Parameters . . . . . . . . . . . . . . . . 51 6.2.2. INIT_RESP Parameters . . . . . . . . . . . . . . . . 51
6.3. register Method . . . . . . . . . . . . . . . . . . . . . 52 6.3. register Method . . . . . . . . . . . . . . . . . . . . . 53
6.3.1. REGISTRATION_REQ Parameters . . . . . . . . . . . . . 52 6.3.1. REGISTRATION_REQ Parameters . . . . . . . . . . . . . 53
6.3.2. REGISTRATION_RESP Parameters . . . . . . . . . . . . 53 6.3.2. REGISTRATION_RESP Parameters . . . . . . . . . . . . 54
6.4. getSpectrum Method . . . . . . . . . . . . . . . . . . . 54 6.4. getSpectrum Method . . . . . . . . . . . . . . . . . . . 55
6.4.1. AVAIL_SPECTRUM_REQ Parameters . . . . . . . . . . . . 55 6.4.1. AVAIL_SPECTRUM_REQ Parameters . . . . . . . . . . . . 56
6.4.2. AVAIL_SPECTRUM_RESP Parameters . . . . . . . . . . . 57 6.4.2. AVAIL_SPECTRUM_RESP Parameters . . . . . . . . . . . 58
6.5. getSpectrumBatch Method . . . . . . . . . . . . . . . . . 61 6.5. getSpectrumBatch Method . . . . . . . . . . . . . . . . . 62
6.5.1. AVAIL_SPECTRUM_BATCH_REQ Parameters . . . . . . . . . 62 6.5.1. AVAIL_SPECTRUM_BATCH_REQ Parameters . . . . . . . . . 63
6.5.2. AVAIL_SPECTRUM_BATCH_RESP Parameters . . . . . . . . 64 6.5.2. AVAIL_SPECTRUM_BATCH_RESP Parameters . . . . . . . . 65
6.6. notifySpectrumUse Method . . . . . . . . . . . . . . . . 67 6.6. notifySpectrumUse Method . . . . . . . . . . . . . . . . 68
6.6.1. SPECTRUM_USE_NOTIFY Parameters . . . . . . . . . . . 67 6.6.1. SPECTRUM_USE_NOTIFY Parameters . . . . . . . . . . . 68
6.6.2. SPECTRUM_USE_RESP Parameters . . . . . . . . . . . . 69 6.6.2. SPECTRUM_USE_RESP Parameters . . . . . . . . . . . . 70
6.7. verifyDevice Method . . . . . . . . . . . . . . . . . . . 70 6.7. verifyDevice Method . . . . . . . . . . . . . . . . . . . 71
6.7.1. DEV_VALID_REQ Parameters . . . . . . . . . . . . . . 70 6.7.1. DEV_VALID_REQ Parameters . . . . . . . . . . . . . . 71
6.7.2. DEV_VALID_RESP Parameters . . . . . . . . . . . . . . 71 6.7.2. DEV_VALID_RESP Parameters . . . . . . . . . . . . . . 72
6.8. Sub-message Schemas . . . . . . . . . . . . . . . . . . . 73 6.8. Sub-message Schemas . . . . . . . . . . . . . . . . . . . 74
6.8.1. GeoLocation . . . . . . . . . . . . . . . . . . . . . 73 6.8.1. GeoLocation . . . . . . . . . . . . . . . . . . . . . 74
6.8.2. DeviceDescriptor . . . . . . . . . . . . . . . . . . 75 6.8.2. DeviceDescriptor . . . . . . . . . . . . . . . . . . 76
6.8.3. AntennaCharacteristics . . . . . . . . . . . . . . . 76 6.8.3. AntennaCharacteristics . . . . . . . . . . . . . . . 77
6.8.4. DeviceCapabilities . . . . . . . . . . . . . . . . . 77 6.8.4. DeviceCapabilities . . . . . . . . . . . . . . . . . 78
6.8.5. DeviceOwner . . . . . . . . . . . . . . . . . . . . . 78 6.8.5. DeviceOwner . . . . . . . . . . . . . . . . . . . . . 79
6.8.6. RulesetInfo . . . . . . . . . . . . . . . . . . . . . 79 6.8.6. RulesetInfo . . . . . . . . . . . . . . . . . . . . . 80
6.8.7. DbUpdateSpec . . . . . . . . . . . . . . . . . . . . 80 6.8.7. DbUpdateSpec . . . . . . . . . . . . . . . . . . . . 81
6.8.8. DatabaseSpec . . . . . . . . . . . . . . . . . . . . 81 6.8.8. DatabaseSpec . . . . . . . . . . . . . . . . . . . . 82
6.8.9. Spectrum . . . . . . . . . . . . . . . . . . . . . . 81 6.8.9. Spectrum . . . . . . . . . . . . . . . . . . . . . . 82
6.8.10. FrequencyRange . . . . . . . . . . . . . . . . . . . 83 6.8.10. FrequencyRange . . . . . . . . . . . . . . . . . . . 84
6.8.11. EventTime . . . . . . . . . . . . . . . . . . . . . . 84 6.8.11. EventTime . . . . . . . . . . . . . . . . . . . . . . 85
6.8.12. SpectrumSchedule . . . . . . . . . . . . . . . . . . 84 6.8.12. SpectrumSchedule . . . . . . . . . . . . . . . . . . 85
6.8.13. SpectrumSpec . . . . . . . . . . . . . . . . . . . . 85 6.8.13. SpectrumSpec . . . . . . . . . . . . . . . . . . . . 86
6.8.14. GeoSpectrumSpec . . . . . . . . . . . . . . . . . . . 86 6.8.14. GeoSpectrumSpec . . . . . . . . . . . . . . . . . . . 87
6.8.15. DeviceValidity . . . . . . . . . . . . . . . . . . . 87 6.8.15. DeviceValidity . . . . . . . . . . . . . . . . . . . 88
6.8.16. Additional Properties . . . . . . . . . . . . . . . . 88 6.8.16. Additional Properties . . . . . . . . . . . . . . . . 89
7. HTTPS Binding . . . . . . . . . . . . . . . . . . . . . . . . 88 7. HTTPS Binding . . . . . . . . . . . . . . . . . . . . . . . . 89
8. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 90 8. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 91
8.1. Defining New Message Parameters . . . . . . . . . . . . . 90 8.1. Defining New Message Parameters . . . . . . . . . . . . . 91
8.2. Defining Ruleset Identifiers . . . . . . . . . . . . . . 90 8.2. Defining Ruleset Identifiers . . . . . . . . . . . . . . 91
8.3. Defining Additional Error Codes . . . . . . . . . . . . . 91 8.3. Defining Additional Error Codes . . . . . . . . . . . . . 92
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 91 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 92
9.1. PAWS Parameters Registry . . . . . . . . . . . . . . . . 91 9.1. PAWS Parameters Registry . . . . . . . . . . . . . . . . 92
9.1.1. Registration Template . . . . . . . . . . . . . . . . 91 9.1.1. Registration Template . . . . . . . . . . . . . . . . 92
9.1.2. Initial Registry Contents . . . . . . . . . . . . . . 92 9.1.2. Initial Registry Contents . . . . . . . . . . . . . . 93
9.2. PAWS Ruleset ID Registry . . . . . . . . . . . . . . . . 93 9.2. PAWS Ruleset ID Registry . . . . . . . . . . . . . . . . 94
9.2.1. Registration Template . . . . . . . . . . . . . . . . 94 9.2.1. Registration Template . . . . . . . . . . . . . . . . 95
9.2.2. Initial Registry Contents . . . . . . . . . . . . . . 94 9.2.2. Initial Registry Contents . . . . . . . . . . . . . . 95
9.3. PAWS Error Code Registry . . . . . . . . . . . . . . . . 96 9.3. PAWS Error Code Registry . . . . . . . . . . . . . . . . 97
9.3.1. Registration Template . . . . . . . . . . . . . . . . 96 9.3.1. Registration Template . . . . . . . . . . . . . . . . 98
9.3.2. Initial Registry Contents . . . . . . . . . . . . . . 97 9.3.2. Initial Registry Contents . . . . . . . . . . . . . . 98
10. Security Considerations . . . . . . . . . . . . . . . . . . . 97 10. Security Considerations . . . . . . . . . . . . . . . . . . . 98
10.1. Assurance of Proper Database . . . . . . . . . . . . . . 98 10.1. Assurance of Proper Database . . . . . . . . . . . . . . 99
10.2. Protection Against Modification . . . . . . . . . . . . . 98 10.2. Protection Against Modification . . . . . . . . . . . . . 100
10.3. Protection Against Eavesdropping . . . . . . . . . . . . 98 10.3. Protection Against Eavesdropping . . . . . . . . . . . . 100
10.4. Client Authentication Considerations . . . . . . . . . . 99 10.4. Client Authentication Considerations . . . . . . . . . . 100
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 99 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 100
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 100 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 101
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 100 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 101
13.1. Normative References . . . . . . . . . . . . . . . . . . 100 13.1. Normative References . . . . . . . . . . . . . . . . . . 101
13.2. Informative References . . . . . . . . . . . . . . . . . 101 13.2. Informative References . . . . . . . . . . . . . . . . . 102
Appendix A. Changes / Author Notes. . . . . . . . . . . . . . . 102 Appendix A. Changes / Author Notes. . . . . . . . . . . . . . . 103
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 105 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 107
1. Introduction 1. Introduction
This section provides some high level introductory material. Readers This section provides some high level introductory material. Readers
are strongly encouraged to read Protocol to Access White-Space (PAWS) are strongly encouraged to read Protocol to Access White-Space (PAWS)
Databases: Use Cases and Requirements [RFC6953] for use cases, Databases: Use Cases and Requirements [RFC6953] for use cases,
requirements, and additional background. requirements, and additional background.
A geospatial database can track available spectrum (in accordance A geospatial database can track available spectrum (in accordance
with the rules of one or more regulatory domains) and make this with the rules of one or more regulatory domains) and make this
skipping to change at page 28, line 32 skipping to change at page 28, line 32
masterDeviceDesc: Depending on regulatory rules, when the request is masterDeviceDesc: Depending on regulatory rules, when the request is
made by the Master Device on behalf of a Slave Device, the Master made by the Master Device on behalf of a Slave Device, the Master
Device MAY be required to provide its own descriptor. Device MAY be required to provide its own descriptor.
4.5.2. DEV_VALID_RESP 4.5.2. DEV_VALID_RESP
+---------------------------------------+ +---------------------------------------+
|DEV_VALID_RESP | |DEV_VALID_RESP |
+----------------------------+----------+ +----------------------------+----------+
|deviceValidities:list | required |---- |deviceValidities:list | required |----
|databaseChange:DbUpdateSpac | optional | | |databaseChange:DbUpdateSpec | optional | |
+----------------------------+----------+ | +----------------------------+----------+ |
V 1..* V 1..*
+---------------------------------------+ +---------------------------------------+
|DeviceValidity | |DeviceValidity |
+----------------------------+----------+ +----------------------------+----------+
|deviceDesc:DeviceDescriptor | required | |deviceDesc:DeviceDescriptor | required |
|isValid:boolean | required | |isValid:boolean | required |
|reason:string | optional | |reason:string | optional |
+----------------------------+----------+ +----------------------------+----------+
skipping to change at page 45, line 5 skipping to change at page 45, line 5
+---------------------------+ +---------------------------+
|Error | |Error |
+----------------+----------+ +----------------+----------+
|code:int | required | |code:int | required |
|message:string | optional | |message:string | optional |
|data:any | optional | |data:any | optional |
+----------------+----------+ +----------------+----------+
Parameters: Parameters:
code: An integer code that indicates the error type. code: An integer code that indicates the error type. Values MUST be
within the range, -32768 to 32767, inclusive.
message: A description of the error. It MAY be in any language. message: A description of the error. It MAY be in any language.
The length of the value MUST NOT exceed 128 characters. The length of the value MUST NOT exceed 128 characters.
data: The Database MAY include additional data. For some errors, data: The Database MAY include additional data. For some errors,
additional data may be required. The Device MUST ignore any data additional data may be required. The Device MUST ignore any data
parameters it does not understand. parameters it does not understand.
The following table defines valid error codes. They are loosely The following table lists predefined and reserved error codes. They
grouped into the following categories: are loosely grouped into the following categories:
-100s: Indicates compatibility issues, e.g., version mismatch, -100s: Indicates compatibility issues, e.g., version mismatch,
unsupported or unimplemented features. unsupported or unimplemented features.
-200s: Indicates that the Device request contains an error that -200s: Indicates that the Device request contains an error that
needs to be modified before making another request. needs to be modified before making another request.
-300s: Indicates authorization-related issues. -300s: Indicates authorization-related issues.
Code Name Description Values that are not defined explicitly in the Error Codes Table
---- ---------------- ----------------------------------------------- (Table 1) below are unassigned.
-100 (reserved)
-101 VERSION The Database does not support the specified Code Name Description & Additional parameters
version of the message. ------ ---------------- ---------------------------------------------
-102 UNSUPPORTED The Database does not support the Device. For 0 (reserved)
example, it does not support the regulatory -100 (reserved)
domain specified in the request. -101 VERSION The Database does not support the specified
-103 UNIMPLEMENTED The Database does not implement the optional version of the message.
request or optional feature. -102 UNSUPPORTED The Database does not support the Device. For
-104 OUTSIDE_COVERAGE The specified geo-location is outside the example, it does not support the regulatory
coverage area of the Database. The Database MAY domain specified in the request.
include a list of alternate databases that -103 UNIMPLEMENTED The Database does not implement the optional
might be appropriate for the requested request or optional feature.
location. See OUTSIDE_COVERAGE Error -104 OUTSIDE_COVERAGE The specified geo-location is outside the
(Section 5.17.1). coverage area of the Database. The Database
-105 DATABASE_CHANGE The Database has changed its URI. The Database MAY include a DbUpdateSpec (Section 5.7)
MAY include a DbUpdateSpec (Section 5.7) parameter to provide a list of alternate
parameter in the error response to provide databases that might be appropriate for the
devices with one or more alternate database requested location. See OUTSIDE_COVERAGE
URIs. The Device SHOULD use the information to Error (Section 5.17.1) for more details.
update its list of preconfigured databases to
replace (only) its entry for the responding -105 DATABASE_CHANGE The Database has changed its URI. The
Database with the list of alternate database Database MAY include a DbUpdateSpec
URIs. See DATABASE_CHANGE Error (Section 5.7) parameter in the error response
(Section 5.17.2). to provide devices with one or more alternate
-200 (reserved) database URIs. The Device SHOULD use the
-201 REQUIRED A required parameter is missing. The Database information to update its list of
MUST include a list of the required parameter preconfigured databases to replace (only) its
names. The Database MAY include only names of entry for the responding Database with the
parameters that are missing, but MAY include a list of alternate database URIs. See
full list. Including the full list of missing DATABASE_CHANGE Error (Section 5.17.2) for
parameters may reduce the number of re-queries more details.
from the Device. See REQUIRED Error -200 (reserved)
(Section 5.17.3). -201 REQUIRED A required parameter is missing. The Database
-202 INVALID_VALUE A parameter value is invalid in some way. The MUST include a list of the required parameter
Database SHOULD include a message indicating names. The Database MAY include only names of
which parameter and why its value is invalid. parameters that are missing, but MAY include
-300 (reserved) a full list. Including the full list of
-301 UNAUTHORIZED The Device is not authorized to used the missing parameters may reduce the number of
Database. Authorization may be determined by re-queries from the Device. See REQUIRED
regulatory rules or be dependent on prior Error (Section 5.17.3) for more details.
arrangement between the Device and Database. -202 INVALID_VALUE A parameter value is invalid in some way. The
-302 NOT_REGISTERED Device registration required, but the Device is Database SHOULD include a message indicating
not registered. which parameter and why its value is invalid.
-300 (reserved)
-301 UNAUTHORIZED The Device is not authorized to used the
Database. Authorization may be determined by
regulatory rules or be dependent on prior
arrangement between the Device and Database.
-302 NOT_REGISTERED Device registration required, but the Device
is not registered.
-32000 (reserved) Reserved for JSON-RPC error codes.
to
-32768
Table 1: Error Codes Table 1: Error Codes
5.17.1. OUTSIDE_COVERAGE Error 5.17.1. OUTSIDE_COVERAGE Error
When the error code is OUTSIDE_COVERAGE, the Database MAY include an When the error code is OUTSIDE_COVERAGE, the Database MAY include an
ErrorData element within its Error response as the "data" field, and, ErrorData element within its Error response as the "data" field, and,
if present, the ErrorData MAY include a DbUpdateSpec (Section 5.7) if present, the ErrorData MAY include a DbUpdateSpec (Section 5.7)
element that provides a list of alternate databases that might be element that provides a list of alternate databases that might be
appropriate for the requested location. appropriate for the requested location.
skipping to change at page 92, line 19 skipping to change at page 93, line 19
Specification document(s): Reference to the document that specifies Specification document(s): Reference to the document that specifies
the parameter, preferably including a URI that can be used to the parameter, preferably including a URI that can be used to
retrieve a copy of the document. An indication of the relevant retrieve a copy of the document. An indication of the relevant
sections also may be included, but is not required. sections also may be included, but is not required.
9.1.2. Initial Registry Contents 9.1.2. Initial Registry Contents
The PAWS Parameters Registry enables protocol extensibility to The PAWS Parameters Registry enables protocol extensibility to
support any regulatory domain and ruleset. The initial contents of support any regulatory domain and ruleset. The initial contents of
the registry, however, include only FCC-specific and ETSI-specific the registry, however, include only FCC-specific and ETSI-specific
entries, because, as of this writing, it is the only regulatory entries, because, as of this writing, they are the only regulatory
domain that has finalized rules. There is no intent to restrict the domains that have established rules. There is no intent to restrict
protocol to FCC rules. the protocol to FCC and ETSI rules.
The PAWS Parameters Registry's initial contents are listed below. The PAWS Parameters Registry's initial contents are listed below;
each section corresponds to a row of the registry. The PAWS
Parameters Registry will include the following fields: 'Parameter
name', 'Parameter usage location', and 'Specification document(s)'.
IANA will post each registration template that is not included in the
text of an RFC.
FCC ID 9.1.2.1. FCC ID
Parameter name: fccId Parameter name: fccId
Parameter usage location: DeviceDescriptor (Section 5.2) Parameter usage location: DeviceDescriptor (Section 5.2)
Specification document(s): [[ this document ]] Specifies the Specification document(s): [[ this document ]] Specifies the
device's FCC certification identifier. The value is an identifier device's FCC certification identifier. The value is an identifier
string whose length MUST NOT exceed 32 characters. Note that, in string whose length MUST NOT exceed 32 characters. Note that, in
practice, a valid FCC ID may be limited to 19 characters, as practice, a valid FCC ID may be limited to 19 characters, as
proposed in FCC Administration Topics Review [FCC-Review-2012-10]. proposed in FCC Administration Topics Review [FCC-Review-2012-10].
FCC Device Type 9.1.2.2. FCC Device Type
Parameter name: fccTvbdDeviceType Parameter name: fccTvbdDeviceType
Parameter usage location: DeviceDescriptor (Section 5.2) Parameter usage location: DeviceDescriptor (Section 5.2)
Specification document(s): [[ this document ]] Specifies the TV Band Specification document(s): [[ this document ]] Specifies the TV Band
White Space device type, as defined by the FCC. Valid values are White Space device type, as defined by the FCC. Valid values are
"FIXED", "MODE_1", "MODE_2". "FIXED", "MODE_1", "MODE_2".
ETSI Device Type 9.1.2.3. ETSI Device Type
Parameter name: etsiEnDeviceType Parameter name: etsiEnDeviceType
Parameter usage location: DeviceDescriptor (Section 5.2) Parameter usage location: DeviceDescriptor (Section 5.2)
Specification document(s): Specifies the White Space Device type, as Specification document(s): Specifies the White Space Device type, as
defined by the ETSI Harmonised Standard [ETSI-EN-301-598]. Valid defined by the ETSI Harmonised Standard [ETSI-EN-301-598]. Valid
values are single-letter strings, such as "A", "B", etc. Consult values are single-letter strings, such as "A", "B", etc. Consult
the documentation for details about the device types. the documentation for details about the device types.
ETSI Device Emissions Class 9.1.2.4. ETSI Device Emissions Class
Parameter name: etsiEnDeviceEmissionsClass Parameter name: etsiEnDeviceEmissionsClass
Parameter usage location: DeviceDescriptor (Section 5.2) Parameter usage location: DeviceDescriptor (Section 5.2)
Specification document(s): Specifies the White Space Device Specification document(s): Specifies the White Space Device
emissions class, as defined by the ETSI Harmonised Standard emissions class, as defined by the ETSI Harmonised Standard
[ETSI-EN-301-598], that characterises the out-of-block emissions [ETSI-EN-301-598], that characterises the out-of-block emissions
of the device. The values are represented by numeric strings, of the device. The values are represented by numeric strings,
such as "1", "2", "3", etc. Consult the documentation for details such as "1", "2", "3", etc. Consult the documentation for details
about emissions classes about emissions classes
ETSI Technology Identifier 9.1.2.5. ETSI Technology Identifier
Parameter name: etsiEnTechnologyId Parameter name: etsiEnTechnologyId
Parameter usage location: DeviceDescriptor (Section 5.2) Parameter usage location: DeviceDescriptor (Section 5.2)
Specification document(s): Specifies the White Space Device Specification document(s): Specifies the White Space Device
technology identifier, as defined by the ETSI Harmonised Standard technology identifier, as defined by the ETSI Harmonised Standard
[ETSI-EN-301-598]. The string value MUST NOT exceed 64 characters [ETSI-EN-301-598]. The string value MUST NOT exceed 64 characters
in length. Consult the documentation for valid values. in length. Consult the documentation for valid values.
ETSI Device Category 9.1.2.6. ETSI Device Category
Parameter name: etsiEnDeviceCategory Parameter name: etsiEnDeviceCategory
Parameter usage location: DeviceDescriptor (Section 5.2) Parameter usage location: DeviceDescriptor (Section 5.2)
Specification document(s): Specifies the White Space Device Specification document(s): Specifies the White Space Device
category, as defined by the ETSI Harmonised Standard category, as defined by the ETSI Harmonised Standard
[ETSI-EN-301-598]. Valid values are the strings, "master" and [ETSI-EN-301-598]. Valid values are the strings, "master" and
"slave". It is case insensitive. "slave". It is case insensitive.
9.2. PAWS Ruleset ID Registry 9.2. PAWS Ruleset ID Registry
skipping to change at page 94, line 15 skipping to change at page 95, line 23
successful. successful.
IANA must only accept registry updates from the Designated Expert(s), IANA must only accept registry updates from the Designated Expert(s),
and should direct all requests for registration to the review mailing and should direct all requests for registration to the review mailing
list. list.
9.2.1. Registration Template 9.2.1. Registration Template
Ruleset name: The name of the ruleset. The length of the string Ruleset name: The name of the ruleset. The length of the string
MUST NOT exceed 64 characters. MUST NOT exceed 64 characters.
Additional message parameters: Additional parameters to associate Additional parameter requirements: List of additional parameters to
with the rulesetId parameter. New parameters MUST be registered associate with the ruleset ID and any additional requirements on
separately in the PAWS Parameters Registry, as described by message parameters. New parameters MUST be registered separately
Section 8.1. in the PAWS Parameters Registry, as described by Section 8.1.
Specification Document(s): Reference to the document that specifies Specification document(s): Reference to the document that specifies
the parameter, preferably including a URI that can be used to the parameter, preferably including a URI that can be used to
retrieve a copy of the document. An indication of the relevant retrieve a copy of the document. An indication of the relevant
sections also may be included, but is not required. sections also may be included, but is not required.
9.2.2. Initial Registry Contents 9.2.2. Initial Registry Contents
The PAWS Ruleset ID Registry enables protocol extensibility to The PAWS Ruleset ID Registry enables protocol extensibility to
support any regulatory domain and ruleset. The initial contents of support any regulatory domain and ruleset. The initial contents of
the registry, however, include only FCC-specific and ETSI-specific the registry, however, include only FCC-specific and ETSI-specific
entries, because, as of this writing, it is the only regulatory entries, because, as of this writing, it is the only regulatory
domain that has finalized rules. There is no intent to restrict the domain that has finalized rules. There is no intent to restrict the
protocol to FCC rules. protocol to FCC rules.
The initial contents of the PAWS Ruleset ID Registry are listed The initial contents of the PAWS Ruleset ID Registry are listed
below. below; each section corresponds to a single row in the registry. The
PAWS Ruleset ID Registry will include the following fields: 'Ruleset
name', 'Additional parameter requirements', and 'Specification
document(s)'. IANA will post each registration template that is not
included in the text of an RFC.
9.2.2.1. Federal Communications Commission (FCC) 9.2.2.1. Federal Communications Commission (FCC)
For the additional parameters that start with the "fcc" prefix, see For the additional parameters that start with the "fcc" prefix, see
PAWS Parameters Registry Initial Contents (Section 9.1.2) for more PAWS Parameters Registry Initial Contents (Section 9.1.2) for more
information. information.
Ruleset name: FccTvBandWhiteSpace-2010 Ruleset name: FccTvBandWhiteSpace-2010
Additional message parameters: Additional parameter requirements:
deviceDesc: The DeviceDescriptor (Section 5.2) parameter is deviceDesc: The DeviceDescriptor (Section 5.2) parameter is
REQUIRED for Available Spectrum Request (Section 4.4.1) and REQUIRED for Available Spectrum Request (Section 4.4.1) and
Available Spectrum Batch Request (Section 4.4.3). Available Spectrum Batch Request (Section 4.4.3).
fccId: Specifies a device's FCC certification ID. It is a fccId: Specifies a device's FCC certification ID. It is a
required parameter in DeviceDescriptor (Section 5.2). REQUIRED parameter in DeviceDescriptor (Section 5.2).
fccTvbdDeviceType: Specifies the type of TV-band White Space fccTvbdDeviceType: Specifies the type of TV-band White Space
device, as defined by the FCC rules. It is a required device, as defined by the FCC rules. It is a REQUIRED
parameter in DeviceDescriptor (Section 5.2). parameter in DeviceDescriptor (Section 5.2).
Additional DeviceOwner (Section 5.5) requirements:
owner: The owner vCard [RFC6350] entry MUST include the formatted
name of an individual or organization using the "fn" property.
When the name is that of an organization, the entry also MUST
include the "kind" property, with a value of "org".
operator: The operator vCard [RFC6350] entry MUST include the
following properties:
fn: Formatted name of a contact person responsible for the
device's operation.
adr: Address for the contact person.
tel: Phone number for the contact person.
email: E-mail address for the contact person.
Specification document(s): This ruleset refers to the FCC rules for Specification document(s): This ruleset refers to the FCC rules for
TV-band White Space operations established in the Code of Federal TV-band White Space operations established in the Code of Federal
Regulations (CFR), Title 47, Part 15, Subpart H [FCC-CFR47-15H]. Regulations (CFR), Title 47, Part 15, Subpart H [FCC-CFR47-15H].
Additional DeviceOwner (Section 5.5) requirements:
owner: The owner vCard [RFC6350] entry MUST include the formatted
name of an individual or organization using the "fn" property.
When the name is that of an organization, the entry also MUST
include the "kind" property, with a value of "org".
operator: The operator vCard [RFC6350] entry MUST include the
following properties:
fn: Formatted name of a contact person responsible for the
device's operation.
adr: Address for the contact person.
tel: Phone number for the contact person.
email: E-mail address for the contact person.
9.2.2.2. European Telecommunications Standards Institute (ETSI) 9.2.2.2. European Telecommunications Standards Institute (ETSI)
For the additional parameters that start with the "etsi" prefix, see For the additional parameters that start with the "etsi" prefix, see
PAWS Parameters Registry Initial Contents (Section 9.1.2) for more PAWS Parameters Registry Initial Contents (Section 9.1.2) for more
information. information.
Ruleset name: ETSI-EN-301-598-1.0.0-draft Ruleset name: ETSI-EN-301-598-1.0.0-draft
Additional message parameters: Additional parameter requirements:
manufacturerId: Specifies a device's manufacturer's identifier. manufacturerId: Specifies a device's manufacturer's identifier.
It is a REQUIRED parameter in DeviceDescriptor (Section 5.2). It is a REQUIRED parameter in DeviceDescriptor (Section 5.2).
modelId: Specifies a device's model identifier. It is a REQUIRED modelId: Specifies a device's model identifier. It is a REQUIRED
parameter in DeviceDescriptor (Section 5.2). parameter in DeviceDescriptor (Section 5.2).
etsiEnDeviceType: Specifies the device's ETSI device type. It is etsiEnDeviceType: Specifies the device's ETSI device type. It is
a REQUIRED parameter in DeviceDescriptor (Section 5.2). a REQUIRED parameter in DeviceDescriptor (Section 5.2).
etsiEnDeviceEmissionsClass: Specifies the device's ETSI device etsiEnDeviceEmissionsClass: Specifies the device's ETSI device
emissions class. It is a REQUIRED parameter in emissions class. It is a REQUIRED parameter in
DeviceDescriptor (Section 5.2). DeviceDescriptor (Section 5.2).
etsiEnTechnologyId: Specifies the device's ETSI technology ID. etsiEnTechnologyId: Specifies the device's ETSI technology ID.
It is a REQUIRED parameter in DeviceDescriptor (Section 5.2). It is a REQUIRED parameter in DeviceDescriptor (Section 5.2).
etsiEnDeviceCategory: Specifies the device's ETSI device etsiEnDeviceCategory: Specifies the device's ETSI device
category. It is a REQUIRED parameter in DeviceDescriptor category. It is a REQUIRED parameter in DeviceDescriptor
(Section 5.2). (Section 5.2).
requestType: Modifies the available-spectrum request type. It is requestType: Modifies the available-spectrum request type. It is
an OPTIONAL parameter in the AVAIL_SPECTRUM_REQ (Section 4.4.1) an OPTIONAL parameter in the AVAIL_SPECTRUM_REQ (Section 4.4.1)
and AVAIL_SPECTRUM_BATCH_REQ (Section 4.4.3) messages. If and AVAIL_SPECTRUM_BATCH_REQ (Section 4.4.3) messages. If
specified, the only valid value is, "Generic Slave", and the specified, the only valid value is, "Generic Slave", and the
Database MUST respond with generic operating parameters for any Database MUST respond with generic operating parameters for any
skipping to change at page 97, line 4 skipping to change at page 98, line 11
approve or deny the registration request, communicating this decision approve or deny the registration request, communicating this decision
to the review list and IANA. Denials should include an explanation to the review list and IANA. Denials should include an explanation
and, if applicable, suggestions as to how to make the request and, if applicable, suggestions as to how to make the request
successful. successful.
IANA must only accept registry updates from the Designated Expert(s), IANA must only accept registry updates from the Designated Expert(s),
and should direct all requests for registration to the review mailing and should direct all requests for registration to the review mailing
list. list.
9.3.1. Registration Template 9.3.1. Registration Template
Code: Integer value of the error code.
Code: Integer value of the error code. The value MUST be an
unassigned value in the range -32768 to 32767, inclusive.
Name: Name of the error. Name: Name of the error.
Description: Description of the error and its associated parameters,
if any.
Additional parameters: Additional parameters that are returned in Additional parameters: Additional parameters that are returned in
the data portion of the error (See Section 5.17). New parameters the data portion of the error (See Section 5.17). New parameters
MUST be registered separately in the PAWS Parameters Registry, as MUST be registered separately in the PAWS Parameters Registry, as
described by Section 9.1. described by Section 9.1.
Description: Description of the error and its associated parameters,
if any.
9.3.2. Initial Registry Contents 9.3.2. Initial Registry Contents
Initial registry contents are defined in the Table of Error Codes Initial registry contents are defined in the Table of Error Codes
(Table 1). (Table 1). Note that the third column, "Description & Additional
parameters", contains both the description of the error code and the
specification of additional parameters, when applicable.
The PAWS Error Code Registry will include the following fields:
'Code', 'Name', 'Description', and 'Additional parameters'. The
registry will also include the error-code categories describing
-100s, -200s, and -300s as a note (see Error Codes (Section 5.17)).
IANA will post each registration template that is not included in the
text of an RFC.
10. Security Considerations 10. Security Considerations
PAWS is a protocol whereby a Master Device requests a schedule of PAWS is a protocol whereby a Master Device requests a schedule of
available spectrum at its location (or location of its Slave Devices) available spectrum at its location (or location of its Slave Devices)
before it (they) can operate using those frequencies. Whereas the before it (they) can operate using those frequencies. Whereas the
information provided by the Database must be accurate and conform to information provided by the Database must be accurate and conform to
applicable regulatory rules, the Database cannot enforce, through the applicable regulatory rules, the Database cannot enforce, through the
protocol, that a client device uses only the spectrum it provided. protocol, that a client device uses only the spectrum it provided.
In other words, devices can put energy in the air and cause In other words, devices can put energy in the air and cause
skipping to change at page 102, line 27 skipping to change at page 103, line 41
[WGS-84] National Imagery and Mapping Agency, "Department of [WGS-84] National Imagery and Mapping Agency, "Department of
Defense World Geodetic System 1984, Its Definition and Defense World Geodetic System 1984, Its Definition and
Relationships with Local Geodetic Systems, NIMA TR8350.2 Relationships with Local Geodetic Systems, NIMA TR8350.2
Third Edition Amendment 1", January 2000, <http:// Third Edition Amendment 1", January 2000, <http://
earth-info.nga.mil/GandG/publications/tr8350.2/ earth-info.nga.mil/GandG/publications/tr8350.2/
tr8350_2.html>. tr8350_2.html>.
Appendix A. Changes / Author Notes. Appendix A. Changes / Author Notes.
Changes from 09:
o Updated format of the IANA section
Changes from 08: Changes from 08:
o Fix JSON typos. o Fix JSON typos.
o Added note that JSON schema is not intended to be formally o Added note that JSON schema is not intended to be formally
validated validated
o Finalize paws-iana-review@ietf.org as the email for updating the o Finalize paws-iana-review@ietf.org as the email for updating the
PAWS IANA registries PAWS IANA registries
o URLs to URIs o URLs to URIs
o Typo fixes o Typo fixes
Changes from 07: Changes from 07:
o Propose ruleset ID name for ETSI: ETSI-EN-301-598-1.0.0-draft o Propose ruleset ID name for ETSI: ETSI-EN-301-598-1.0.0-draft
o Change TBD email address to paws-iana-review@ietf.org for o Change TBD email address to paws-iana-review@ietf.org for
proposing changes to the PAWS IANA registries proposing changes to the PAWS IANA registries
o Moved discussion of required vCard properties to regulatory- o Moved discussion of required vCard properties to regulatory-
 End of changes. 35 change blocks. 
155 lines changed or deleted 189 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/