draft-ietf-paws-protocol-07.txt   draft-ietf-paws-protocol-08.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: June 5, 2014 Applied Communication Sciences Expires: July 18, 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
December 2, 2013 January 14, 2014
Protocol to Access White-Space (PAWS) Databases Protocol to Access White-Space (PAWS) Databases
draft-ietf-paws-protocol-07 draft-ietf-paws-protocol-08
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 June 5, 2014. This Internet-Draft will expire on July 18, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 6 skipping to change at page 3, line 6
4.5. Device Validation . . . . . . . . . . . . . . . . . . . . 26 4.5. Device Validation . . . . . . . . . . . . . . . . . . . . 26
4.5.1. DEV_VALID_REQ . . . . . . . . . . . . . . . . . . . . 28 4.5.1. DEV_VALID_REQ . . . . . . . . . . . . . . . . . . . . 28
4.5.2. DEV_VALID_RESP . . . . . . . . . . . . . . . . . . . 28 4.5.2. DEV_VALID_RESP . . . . . . . . . . . . . . . . . . . 28
5. Protocol Parameters . . . . . . . . . . . . . . . . . . . . . 29 5. Protocol Parameters . . . . . . . . . . . . . . . . . . . . . 29
5.1. GeoLocation . . . . . . . . . . . . . . . . . . . . . . . 29 5.1. GeoLocation . . . . . . . . . . . . . . . . . . . . . . . 29
5.2. DeviceDescriptor . . . . . . . . . . . . . . . . . . . . 31 5.2. DeviceDescriptor . . . . . . . . . . . . . . . . . . . . 31
5.3. AntennaCharacteristics . . . . . . . . . . . . . . . . . 32 5.3. AntennaCharacteristics . . . . . . . . . . . . . . . . . 32
5.4. DeviceCapabilities . . . . . . . . . . . . . . . . . . . 33 5.4. DeviceCapabilities . . . . . . . . . . . . . . . . . . . 33
5.5. DeviceOwner . . . . . . . . . . . . . . . . . . . . . . . 34 5.5. DeviceOwner . . . . . . . . . . . . . . . . . . . . . . . 34
5.6. RulesetInfo . . . . . . . . . . . . . . . . . . . . . . . 34 5.6. RulesetInfo . . . . . . . . . . . . . . . . . . . . . . . 34
5.7. DbUpdateSpec . . . . . . . . . . . . . . . . . . . . . . 36 5.7. DbUpdateSpec . . . . . . . . . . . . . . . . . . . . . . 35
5.8. DatabaseSpec . . . . . . . . . . . . . . . . . . . . . . 36 5.8. DatabaseSpec . . . . . . . . . . . . . . . . . . . . . . 36
5.9. SpectrumSpec . . . . . . . . . . . . . . . . . . . . . . 36 5.9. SpectrumSpec . . . . . . . . . . . . . . . . . . . . . . 36
5.10. SpectrumSchedule . . . . . . . . . . . . . . . . . . . . 38 5.10. SpectrumSchedule . . . . . . . . . . . . . . . . . . . . 38
5.11. Spectrum . . . . . . . . . . . . . . . . . . . . . . . . 39 5.11. Spectrum . . . . . . . . . . . . . . . . . . . . . . . . 38
5.12. SpectrumProfile . . . . . . . . . . . . . . . . . . . . . 41 5.12. SpectrumProfile . . . . . . . . . . . . . . . . . . . . . 41
5.13. FrequencyRange . . . . . . . . . . . . . . . . . . . . . 42 5.13. FrequencyRange . . . . . . . . . . . . . . . . . . . . . 42
5.14. EventTime . . . . . . . . . . . . . . . . . . . . . . . . 43 5.14. EventTime . . . . . . . . . . . . . . . . . . . . . . . . 42
5.15. GeoSpectrumSpec . . . . . . . . . . . . . . . . . . . . . 43 5.15. GeoSpectrumSpec . . . . . . . . . . . . . . . . . . . . . 43
5.16. DeviceValidity . . . . . . . . . . . . . . . . . . . . . 44 5.16. DeviceValidity . . . . . . . . . . . . . . . . . . . . . 44
5.17. Error Element . . . . . . . . . . . . . . . . . . . . . . 45 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 . . . . . . . . . . . . . . . . 47 5.17.2. DATABASE_CHANGE Error . . . . . . . . . . . . . . . . 46
5.17.3. REQUIRED Error . . . . . . . . . . . . . . . . . . . 47 5.17.3. REQUIRED Error . . . . . . . . . . . . . . . . . . . 47
6. Message Encoding . . . . . . . . . . . . . . . . . . . . . . 47 6. Message Encoding . . . . . . . . . . . . . . . . . . . . . . 47
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 . . . . . . . . . . . . . . . . . 49
6.2.2. INIT_RESP Parameters . . . . . . . . . . . . . . . . 51 6.2.2. INIT_RESP Parameters . . . . . . . . . . . . . . . . 51
6.3. register Method . . . . . . . . . . . . . . . . . . . . . 52 6.3. register Method . . . . . . . . . . . . . . . . . . . . . 52
6.3.1. REGISTRATION_REQ Parameters . . . . . . . . . . . . . 52 6.3.1. REGISTRATION_REQ Parameters . . . . . . . . . . . . . 52
6.3.2. REGISTRATION_RESP Parameters . . . . . . . . . . . . 53 6.3.2. REGISTRATION_RESP Parameters . . . . . . . . . . . . 53
6.4. getSpectrum Method . . . . . . . . . . . . . . . . . . . 54 6.4. getSpectrum Method . . . . . . . . . . . . . . . . . . . 54
skipping to change at page 4, line 26 skipping to change at page 4, line 26
9.1.1. Registration Template . . . . . . . . . . . . . . . . 89 9.1.1. Registration Template . . . . . . . . . . . . . . . . 89
9.1.2. Initial Registry Contents . . . . . . . . . . . . . . 89 9.1.2. Initial Registry Contents . . . . . . . . . . . . . . 89
9.2. PAWS Ruleset ID Registry . . . . . . . . . . . . . . . . 90 9.2. PAWS Ruleset ID Registry . . . . . . . . . . . . . . . . 90
9.2.1. Registration Template . . . . . . . . . . . . . . . . 91 9.2.1. Registration Template . . . . . . . . . . . . . . . . 91
9.2.2. Initial Registry Contents . . . . . . . . . . . . . . 91 9.2.2. Initial Registry Contents . . . . . . . . . . . . . . 91
9.3. PAWS Error Code Registry . . . . . . . . . . . . . . . . 93 9.3. PAWS Error Code Registry . . . . . . . . . . . . . . . . 93
9.3.1. Registration Template . . . . . . . . . . . . . . . . 94 9.3.1. Registration Template . . . . . . . . . . . . . . . . 94
9.3.2. Initial Registry Contents . . . . . . . . . . . . . . 94 9.3.2. Initial Registry Contents . . . . . . . . . . . . . . 94
10. Security Considerations . . . . . . . . . . . . . . . . . . . 94 10. Security Considerations . . . . . . . . . . . . . . . . . . . 94
10.1. Assurance of Proper Database . . . . . . . . . . . . . . 95 10.1. Assurance of Proper Database . . . . . . . . . . . . . . 95
10.2. Protection Against Modification . . . . . . . . . . . . . 95 10.2. Protection Against Modification . . . . . . . . . . . . . 96
10.3. Protection Against Eavesdropping . . . . . . . . . . . . 95 10.3. Protection Against Eavesdropping . . . . . . . . . . . . 96
10.4. Client Authentication Considerations . . . . . . . . . . 96 10.4. Client Authentication Considerations . . . . . . . . . . 96
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 96 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 96
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 97 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 97
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 97 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 97
13.1. Normative References . . . . . . . . . . . . . . . . . . 97 13.1. Normative References . . . . . . . . . . . . . . . . . . 97
13.2. Informative References . . . . . . . . . . . . . . . . . 98 13.2. Informative References . . . . . . . . . . . . . . . . . 98
Appendix A. Changes / Author Notes. . . . . . . . . . . . . . . 99 Appendix A. Changes / Author Notes. . . . . . . . . . . . . . . 99
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 102 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 102
1. Introduction 1. Introduction
skipping to change at page 34, line 27 skipping to change at page 34, line 27
Parameters: Parameters:
owner: The vCard contact information for the individual or business owner: The vCard contact information for the individual or business
that owns the Device is REQUIRED. that owns the Device is REQUIRED.
operator: The vCard contact information for the device operator is operator: The vCard contact information for the device operator is
OPTIONAL, but may be required by specific regulatory domains OPTIONAL, but may be required by specific regulatory domains
NOTE: Depending on the regulatory domain, the Database MAY be NOTE: Depending on the regulatory domain, the Database MAY be
required to validate the device-owner information. In these cases, required to validate the device-owner information. In these cases,
the Database MUST respond with an error if validation fails. the Database MUST respond with an error if validation fails. See
PAWS Ruleset ID Registry (Section 9.2) for regulatory-specific
requirements on mandatory vCard properties.
All contact information MUST be expressed using the structure defined All contact information MUST be expressed using the structure defined
by the vCard Format Specification [RFC6350]. Only the contact fields by the vCard Format Specification [RFC6350]. Note that the vCard
of vCard are supported: specification defines maximum lengths for each field, conforming to
X.520 [ITUT.X520.2008] recommendations.
fn Full name of an individual
org Name of the organization
adr Address fields
tel Telephone numbers
email Email addresses
Note that the vCard specification defines maximum lengths for each
field, conforming to X.520 [ITUT.X520.2008] recommendations.
5.6. RulesetInfo 5.6. RulesetInfo
This contains parameters for the ruleset of a regulatory domain that This contains parameters for the ruleset of a regulatory domain that
is communicated using the Initialization component (Section 4.2), is communicated using the Initialization component (Section 4.2),
Device Registration (Section 4.3), and Available Spectrum Query Device Registration (Section 4.3), and Available Spectrum Query
(Section 4.4) components. (Section 4.4) components.
+-----------------------------------+ +-----------------------------------+
|RulesetInfo | |RulesetInfo |
skipping to change at page 39, line 50 skipping to change at page 39, line 29
|profiles:list |required |---+ |profiles:list |required |---+
+---------------------+---------+ | 0..* +---------------------+---------+ | 0..*
V V
+-----------------------------+ +-----------------------------+
|SpectrumProfile | |SpectrumProfile |
+-------------------+---------+ +-------------------+---------+
|list |required | |list |required |
+-------------------+---------+ +-------------------+---------+
| |
V 2..* V 2..*
+------------------------------+ +----------------+---------+
|freqHz:float |required | |hz:float |required |
|powerDbmPerBw:float |required | |dbm:float |required |
+--------------------+---------+ +----------------+---------+
Parameters: Parameters:
psdBandwidthHz: This parameter is REQUIRED to define the resolution resolutionBwHz: This parameter is REQUIRED to define the resolution
bandwidth (in Hertz) over which permissible power spectral density bandwidth (in Hertz) over which permissible power spectral density
is defined. For example, FCC regulation would require one is defined. For example, FCC regulation would require one
spectrum specification at a bandwidth of 6MHz, and ETSI regulation spectrum specification at a bandwidth of 6MHz, and ETSI regulation
would require two specifications, at 0.1MHz and 8MHz. This would require two specifications, at 0.1MHz and 8MHz. This
parameter MAY be empty if there is no available spectrum. parameter MAY be empty if there is no available spectrum.
profiles: A SpectrumProfile (Section 5.12) list is REQUIRED to profiles: A SpectrumProfile (Section 5.12) list is REQUIRED to
specify permissible power levels over a set of frequency ranges. specify permissible power levels over a set of frequency ranges.
The list MAY be empty if there is no available spectrum. The list MAY be empty if there is no available spectrum.
Consider the following example with different permitted power Consider the following example with different permitted power
spectral densities for the same set of frequencies over different spectral densities for the same set of frequencies over different
resolution bandwidths (for illustrative purposes only): resolution bandwidths (for illustrative purposes only):
[ [
"spectrum": { "spectrum": {
"resolutionBwHz": 6e6, "resolutionBwHz": 6e6,
"profiles": [ "profiles": [
[ [
{"freqHz": 5.18e8, "powerDbmPerBw": 30.0}, {"hz": 5.18e8, "dbm": 30.0},
{"freqHz": 5.24e8, "powerDbmPerBw": 30.0}, {"hz": 5.24e8, "dbm": 30.0},
], ],
... ...
] ]
}, },
"spectrum": { "spectrum": {
"resolutionBwHz": 1e5, "resolutionBwHz": 1e5,
"profiles": [ "profiles": [
[ [
{"freqHz": 5.18e8, "powerDbmPerBw": 27.0}, {"hz": 5.18e8, "dbm": 27.0},
{"freqHz": 5.24e8, "powerDbmPerBw": 27.0}, {"hz": 5.24e8, "dbm": 27.0},
], ],
... ...
] ]
} }
] ]
This is interpreted as: This is interpreted as:
o Over any 6MHz within the frequency range, [518MHz, 524MHz), o Over any 6MHz within the frequency range, [518MHz, 524MHz),
maximum permitted power is 30.0dBm (1000mW), and maximum permitted power is 30.0dBm (1000mW), and
skipping to change at page 41, line 18 skipping to change at page 41, line 10
conditions. conditions.
The following example illustrates multiple spectrum profiles that has The following example illustrates multiple spectrum profiles that has
a gap from 530 MHz to 536 MHz: a gap from 530 MHz to 536 MHz:
[ [
"spectrum": { "spectrum": {
"resolutionBwHz": 6e6, "resolutionBwHz": 6e6,
"profiles": [ "profiles": [
[ [
{"freqHz": 5.18e8, "powerDbmPerBw": 30.0}, {"hz": 5.18e8, "dbm": 30.0},
{"freqHz": 5.24e8, "powerDbmPerBw": 30.0}, {"hz": 5.24e8, "dbm": 30.0},
{"freqHz": 5.24e8, "powerDbmPerBw": 36.0}, {"hz": 5.24e8, "dbm": 36.0},
{"freqHz": 5.30e8, "powerDbmPerBw": 36.0}, {"hz": 5.30e8, "dbm": 36.0},
], ],
[ [
{"freqHz": 5.36e8, "powerDbmPerBw": 30.0}, {"hz": 5.36e8, "dbm": 30.0},
{"freqHz": 5.42e8, "powerDbmPerBw": 30.0}, {"hz": 5.42e8, "dbm": 30.0},
], ],
... ...
] ]
}, },
"spectrum": { "spectrum": {
"resolutionBwHz": 1e5, "resolutionBwHz": 1e5,
"profiles": [ "profiles": [
[ [
{"freqHz": 5.18e8, "powerDbmPerBw": 27.0}, {"hz": 5.18e8, "dbm": 27.0},
{"freqHz": 5.24e8, "powerDbmPerBw": 27.0}, {"hz": 5.24e8, "dbm": 27.0},
{"freqHz": 5.24e8, "powerDbmPerBw": 30.0}, {"hz": 5.24e8, "dbm": 30.0},
{"freqHz": 5.30e8, "powerDbmPerBw": 30.0}, {"hz": 5.30e8, "dbm": 30.0},
], ],
[ [
{"freqHz": 5.36e8, "powerDbmPerBw": 27.0}, {"hz": 5.36e8, "dbm": 27.0},
{"freqHz": 5.42e8, "powerDbmPerBw": 27.0}, {"hz": 5.42e8, "dbm": 27.0},
], ],
... ...
] ]
} }
] ]
5.12. SpectrumProfile 5.12. SpectrumProfile
A spectrum profile is characterized by an ordered list of (frequency, A spectrum profile is characterized by an ordered list of (frequency,
power) points that represents the shape of maximum permissible power power) points that represents the shape of maximum permissible power
levels over a range of frequencies. levels over a range of frequencies.
o It MUST contain a minimum of two entries. o It MUST contain a minimum of two entries.
o The entries in the list MUST be ordered in non-decreasing o The entries in the list MUST be ordered in non-decreasing
frequency values. frequency values.
o Two consecutive points MAY have the same frequency value to o Two consecutive points MAY have the same frequency value to
represent a "step function". represent a "step function".
o Three or more points MAY NOT share the same frequency value.
o Three or more points MUST NOT share the same frequency value.
o The first frequency is inclusive; the last frequency is exclusive. o The first frequency is inclusive; the last frequency is exclusive.
The following figure defines the SpectrumProfile element. The following figure defines the SpectrumProfile element.
+-------------------------------+ +-------------------------------+
|SpectrumProfile | |SpectrumProfile |
+---------------------+---------+ +---------------------+---------+
|list |required |---+ |list |required |---+
+---------------------+---------+ | 2..* +---------------------+---------+ | 2..*
V V
+------------------------------+ +----------------+---------+
|freqHz:float |required | |hz:float |required |
|powerDbmPerBw:float |required | |dbm:float |required |
+--------------------+---------+ +----------------+---------+
Parameters of each point in the profile: Parameters of each point in the profile:
freqHz: The frequency, in Hertz, at which the power level is hz: The frequency, in Hertz, at which the power level is defined.
defined. dbm: The power level, expressed as dBm per resolution bandwidth, as
powerDbmPerBw: The power level, express as dBm per resolution defined by the "resolutionBwHz" element of the enclosing Spectrum
bandwidth, as defined by the "resolutionBwHz" element of the (Section 5.11) element.
enclosing Spectrum (Section 5.11) element.
5.13. FrequencyRange 5.13. FrequencyRange
The FrequencyRange parameter specifies a frequency range. The FrequencyRange parameter specifies a frequency range.
+--------------------------------+ +--------------------------------+
|FrequencyRange | |FrequencyRange |
+----------------------+---------+ +----------------------+---------+
|startHz:float |required | |startHz:float |required |
|stopHz:float |required | |stopHz:float |required |
skipping to change at page 53, line 20 skipping to change at page 53, line 20
"version": "1.0", "version": "1.0",
"deviceDesc": { "deviceDesc": {
"serialNumber": "XXX", "serialNumber": "XXX",
"fccId": "YYY", "fccId": "YYY",
... ...
}, },
"deviceOwner": { "deviceOwner": {
"owner": [ "owner": [
"vcard", [ "vcard", [
["version", {}, "text", "4.0"], ["version", {}, "text", "4.0"],
["org", {}, "text", "Racafrax, Inc."] ["kind", {}, "text", "org"],
["fn", {}, "text", "Racafrax, Inc."]
] ]
], ],
"operator": [ "operator": [
"vcard", [ "vcard", [
["version", {}, "text", "4.0"], ["version", {}, "text", "4.0"],
["fn", {}, "text", "John Frax"], ["fn", {}, "text", "John Frax"],
["adr", {}, "text", ["adr", {}, "text",
["", "", "100 Main Street", ["", "", "100 Main Street",
"Summersville", "CA", "90034", "USA" "Summersville", "CA", "90034", "USA"
] ]
skipping to change at page 59, line 27 skipping to change at page 59, line 27
"eventTime": { "eventTime": {
"startTime": "2013-03-02T14:30:21Z", "startTime": "2013-03-02T14:30:21Z",
"stopTime": "2013-03-02T20:00:00Z", "stopTime": "2013-03-02T20:00:00Z",
}, },
"spectra": [ "spectra": [
{ {
"resolutionBwHz": 6e6, "resolutionBwHz": 6e6,
"profiles": [ "profiles": [
... ...
[ [
{"freqHz":5.18e8, "powerDbmPerBw":30.0}, {"hz":5.18e8, "dbm":30.0},
{"freqHz":5.36e8, "powerDbmPerBw":30.0}, {"hz":5.36e8, "dbm":30.0},
{"freqHz":5.36e8, "powerDbmPerBw":36.0}, {"hz":5.36e8, "dbm":36.0},
{"freqHz":5.42e8, "powerDbmPerBw":36.0} {"hz":5.42e8, "dbm":36.0}
], ],
[ [
{"freqHz":6.20e8, "powerDbmPerBw":30.0}, {"hz":6.20e8, "dbm":30.0},
{"freqHz":6.26e8, "powerDbmPerBw":30.0}, {"hz":6.26e8, "dbm":30.0},
], ],
... ...
] ]
}, },
{ {
"resolutionBwHz": 1e5, "resolutionBwHz": 1e5,
"profiles": [ "profiles": [
... ...
[ [
{"freqHz":5.18e8, "powerDbmPerBw":27.0}, {"hz":5.18e8, "dbm":27.0},
{"freqHz":5.36e8, "powerDbmPerBw":27.0}, {"hz":5.36e8, "dbm":27.0},
{"freqHz":5.36e8, "powerDbmPerBw":30.0}, {"hz":5.36e8, "dbm":30.0},
{"freqHz":5.42e8, "powerDbmPerBw":30.0} {"hz":5.42e8, "dbm":30.0}
], ],
[ [
{"freqHz":6.20e8, "powerDbmPerBw":27.0}, {"hz":6.20e8, "dbm":27.0},
{"freqHz":6.26e8, "powerDbmPerBw":27.0}, {"hz":6.26e8, "dbm":27.0},
], ],
... ...
] ]
} }
] ]
}, },
{ {
"eventTime": { "eventTime": {
"startTime": "2013-03-02T22:00:00Z", "startTime": "2013-03-02T22:00:00Z",
skipping to change at page 64, line 35 skipping to change at page 64, line 35
"eventTime": { "eventTime": {
"startTime": "2013-03-02T14:30:21Z", "startTime": "2013-03-02T14:30:21Z",
"stopTime": "2013-03-02T20:00:00Z", "stopTime": "2013-03-02T20:00:00Z",
}, },
"spectra": [ "spectra": [
{ {
"resolutionBwHz": 6e6, "resolutionBwHz": 6e6,
"profiles": [ "profiles": [
... ...
[ [
{"freqHz":5.18e8, "powerDbmPerBw":30.0}, {"hz":5.18e8, "dbm":30.0},
{"freqHz":5.36e8, "powerDbmPerBw":30.0}, {"hz":5.36e8, "dbm":30.0},
{"freqHz":5.36e8, "powerDbmPerBw":36.0}, {"hz":5.36e8, "dbm":36.0},
{"freqHz":5.42e8, "powerDbmPerBw":36.0} {"hz":5.42e8, "dbm":36.0}
], ],
[ [
{"freqHz":6.20e8, "powerDbmPerBw":30.0}, {"hz":6.20e8, "dbm":30.0},
{"freqHz":6.26e8, "powerDbmPerBw":30.0}, {"hz":6.26e8, "dbm":30.0},
], ],
... ...
] ]
}, },
{ {
"resolutionBwHz": 1e5, "resolutionBwHz": 1e5,
"profiles": [ "profiles": [
... ...
[ [
{"freqHz":5.18e8, "powerDbmPerBw":27.0}, {"hz":5.18e8, "dbm":27.0},
{"freqHz":5.36e8, "powerDbmPerBw":27.0}, {"hz":5.36e8, "dbm":27.0},
{"freqHz":5.36e8, "powerDbmPerBw":30.0}, {"hz":5.36e8, "dbm":30.0},
{"freqHz":5.42e8, "powerDbmPerBw":30.0} {"hz":5.42e8, "dbm":30.0}
], ],
[ [
{"freqHz":6.20e8, "powerDbmPerBw":27.0}, {"hz":6.20e8, "dbm":27.0},
{"freqHz":6.26e8, "powerDbmPerBw":27.0}, {"hz":6.26e8, "dbm":27.0},
], ],
... ...
] ]
}, },
] ]
}, },
{ {
"eventTime": { "eventTime": {
"startTime": "2013-03-02T22:00:00Z", "startTime": "2013-03-02T22:00:00Z",
"stopTime": "2013-03-03T14:30:21Z", "stopTime": "2013-03-03T14:30:21Z",
skipping to change at page 67, line 26 skipping to change at page 67, line 26
"location": { "location": {
"point": { "point": {
"center": {"latitude": 37.0005, "longitude": -101.3005} "center": {"latitude": 37.0005, "longitude": -101.3005}
} }
}, },
"spectra": [ "spectra": [
{ {
"resolutionBwHz": 6e6, "resolutionBwHz": 6e6,
"profiles": [ "profiles": [
[ [
{"freqHz":5.18e8, "powerDbmPerBw":30.0}, {"hz":5.18e8, "dbm":30.0},
{"freqHz":5.24e8, "powerDbmPerBw":30.0} {"hz":5.24e8, "dbm":30.0}
] ]
] ]
}, },
] ]
}, },
"id": "xxxxxx" "id": "xxxxxx"
} }
6.6.2. SPECTRUM_USE_RESP Parameters 6.6.2. SPECTRUM_USE_RESP Parameters
skipping to change at page 77, line 10 skipping to change at page 77, line 10
} }
} }
Example: Example:
{ {
"deviceOwner": { "deviceOwner": {
"owner": [ "owner": [
"vcard", [ "vcard", [
["version", {}, "text", "4.0"], ["version", {}, "text", "4.0"],
["org", {}, "text", "Racafrax, Inc."] ["kind", {}, "text", "org"],
["fn", {}, "text", "Racafrax, Inc."]
] ]
], ],
"operator": [ "operator": [
"vcard", [ "vcard", [
["version", {}, "text", "4.0"], ["version", {}, "text", "4.0"],
["fn", {}, "text", "John Frax"], ["fn", {}, "text", "John Frax"],
["adr", {}, "text", ["adr", {}, "text",
["", "", "100 Main Street", ["", "", "100 Main Street",
"Summersville", "CA", "90034", "USA" "Summersville", "CA", "90034", "USA"
] ]
skipping to change at page 80, line 39 skipping to change at page 80, line 39
two entries is required.", two entries is required.",
"item": "SpectrumProfilePoint", "item": "SpectrumProfilePoint",
} }
{ {
"name": "SpectrumProfilePoint", "name": "SpectrumProfilePoint",
"type": "object", "type": "object",
"description": "A point defined by a frequency and power level "description": "A point defined by a frequency and power level
at that frequency.", at that frequency.",
"properties": { "properties": {
"freqHz": { "hz": {
"type": "number", "type": "number",
"description": "Frequency (Hz)", "description": "Frequency (Hz)",
"required": true "required": true
}, },
"powerDbmPerBw": { "dbm": {
"type": "number", "type": "number",
"description": "Power (dBm) per resolution bandwidth as "description": "Power (dBm) per resolution bandwidth as
defined by enclosing resolutionBwHz.", defined by enclosing resolutionBwHz.",
"required": true "required": true
} }
} }
} }
Example: Example:
{ {
"resolutionBwHz": 6e6, "resolutionBwHz": 6e6,
"profiles": [ "profiles": [
[ [
{"freqHz":5.18e8, "powerDbmPerBw":30.0}, {"hz":5.18e8, "dbm":30.0},
{"freqHz":5.36e8, "powerDbmPerBw":30.0}, {"hz":5.36e8, "dbm":30.0},
{"freqHz":5.36e8, "powerDbmPerBw":36.0}, {"hz":5.36e8, "dbm":36.0},
{"freqHz":5.42e8, "powerDbmPerBw":36.0} {"hz":5.42e8, "dbm":36.0}
], ],
[ [
{"freqHz":6.20e8, "powerDbmPerBw":30.0}, {"hz":6.20e8, "dbm":30.0},
{"freqHz":6.26e8, "powerDbmPerBw":30.0}, {"hz":6.26e8, "dbm":30.0},
] ]
] ]
} }
6.8.10. FrequencyRange 6.8.10. FrequencyRange
The FrequencyRange (Section 5.13) element describes a frequency range The FrequencyRange (Section 5.13) element describes a frequency range
and permissible power level within the specified range. and permissible power level within the specified range.
{ {
skipping to change at page 88, line 40 skipping to change at page 88, line 40
9. IANA Considerations 9. IANA Considerations
9.1. PAWS Parameters Registry 9.1. PAWS Parameters Registry
This specification establishes the PAWS Parameters Registry. This specification establishes the PAWS Parameters Registry.
Additional parameters for inclusion in the PAWS protocol requests, Additional parameters for inclusion in the PAWS protocol requests,
responses, or sub-messages are registered through the Specification responses, or sub-messages are registered through the Specification
Required [RFC5226] process, after a two-week review period on the Required [RFC5226] process, after a two-week review period on the
[TBD]@ietf.org mailing list, on the advice of one or more Designated [paws-iana-TBD]@ietf.org mailing list, on the advice of one or more
Experts. To allow for the allocation of values prior to publication, Designated Experts. To allow for the allocation of values prior to
the Designated Expert(s) may approve registration once they are publication, the Designated Expert(s) may approve registration once
satisfied that such a specification will be published. they are satisfied that such a specification will be published.
Registration requests must be sent to the [TBD]@ietf.org mailing list Registration requests must be sent to the [paws-iana-TBD]@ietf.org
for review and comment, with an appropriate subject (e.g., "Request mailing list for review and comment, with an appropriate subject
for parameter: example"). [[ Editor's Note: The name of the mailing (e.g., "Request for parameter: example"). [[ Editor's Note: The name
list should be determined in consultation with the IESG and IANA. of the mailing list should be determined in consultation with the
Suggested name: paws-ext-review. ]] IESG and IANA. Suggested name: paws-ext-review. ]]
Within the review period, the Designated Expert(s) will either Within the review period, the Designated Expert(s) will either
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.
skipping to change at page 90, line 27 skipping to change at page 90, line 27
the documentation for details about the device types. the documentation for details about the device types.
ETSI Device Emissions Class 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", 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 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.
skipping to change at page 91, line 7 skipping to change at page 91, line 7
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
This specification establishes the PAWS Ruleset ID Registry. This specification establishes the PAWS Ruleset ID Registry.
Ruleset type names for inclusion in the PAWS protocol messages are Ruleset type names for inclusion in the PAWS protocol messages are
registered through the Specification Required [RFC5226] process, registered through the Specification Required [RFC5226] process,
after a two-week review period on the [TBD]@ietf.org mailing list, on after a two-week review period on the [paws-iana-TBD]@ietf.org
the advice of one or more Designated Experts. To allow for the mailing list, on the advice of one or more Designated Experts. To
allocation of values prior to publication, the Designated Expert(s) allow for the allocation of values prior to publication, the
may approve registration once they are satisfied that such a Designated Expert(s) may approve registration once they are satisfied
specification will be published. that such a specification will be published.
Registration requests must be sent to the [TBD]@ietf.org mailing list Registration requests must be sent to the [paws-iana-TBD]@ietf.org
for review and comment, with an appropriate subject (e.g., "Request mailing list for review and comment, with an appropriate subject
for parameter: example"). [[ Editor's Note: The name of the mailing (e.g., "Request for parameter: example"). [[ Editor's Note: The name
list should be determined in consultation with the IESG and IANA. of the mailing list should be determined in consultation with the
Suggested name: paws-ext-review. ]] IESG and IANA. Suggested name: paws-ext-review. ]]
Within the review period, the Designated Expert(s) will either Within the review period, the Designated Expert(s) will either
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.
skipping to change at page 92, line 26 skipping to change at page 92, line 26
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).
Specification document(s): [[ this document ]] This ruleset refers Specification document(s): [[ this document ]] This ruleset refers
to the FCC rules for TV-band White Space operations established in to the FCC rules for TV-band White Space operations established in
the Code of Federal Regulations (CFR), Title 47, Part 15, Subpart the Code of Federal Regulations (CFR), Title 47, Part 15, Subpart
H [FCC-CFR47-15H]. 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: TBD Ruleset name: ETSI-EN-301-598-1.0.0-draft
Additional message parameters: Additional message parameters:
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
skipping to change at page 93, line 28 skipping to change at page 93, line 46
(Section 4.4.2) and AVAIL_SPECTRUM_BATCH_RESP (Section 4.4.4). (Section 4.4.2) and AVAIL_SPECTRUM_BATCH_RESP (Section 4.4.4).
Specification document(s): This ruleset refers to the ETSI Specification document(s): This ruleset refers to the ETSI
Harmonised Standard [ETSI-EN-301-598] established by ETSI. Harmonised Standard [ETSI-EN-301-598] established by ETSI.
9.3. PAWS Error Code Registry 9.3. PAWS Error Code Registry
This specification establishes the PAWS Error Code Registry. This specification establishes the PAWS Error Code Registry.
Additional error codes for inclusion in the PAWS protocol error Additional error codes for inclusion in the PAWS protocol error
message are registered through the Specification Required [RFC5226] message are registered through the Specification Required [RFC5226]
process, after a two-week review period on the [TBD]@ietf.org mailing process, after a two-week review period on the [paws-iana-TBD]@
list, on the advice of one or more Designated Experts. To allow for ietf.org mailing list, on the advice of one or more Designated
the allocation of values prior to publication, the Designated Experts. To allow for the allocation of values prior to publication,
Expert(s) may approve registration once they are satisfied that such the Designated Expert(s) may approve registration once they are
a specification will be published. satisfied that such a specification will be published.
Registration requests must be sent to the [TBD]@ietf.org mailing list Registration requests must be sent to the [paws-iana-TBD]@ietf.org
for review and comment, with an appropriate subject (e.g., "Request mailing list for review and comment, with an appropriate subject
for parameter: example"). [[ Editor's Note: The name of the mailing (e.g., "Request for parameter: example"). [[ Editor's Note: The name
list should be determined in consultation with the IESG and IANA. of the mailing list should be determined in consultation with the
Suggested name: paws-ext-review. ]] IESG and IANA. Suggested name: paws-ext-review. ]]
Within the review period, the Designated Expert(s) will either Within the review period, the Designated Expert(s) will either
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.
skipping to change at page 97, line 44 skipping to change at page 98, line 12
attribute types", November 2008, attribute types", November 2008,
<http://www.itu.int/rec/T-REC-X.520-200811-I>. <http://www.itu.int/rec/T-REC-X.520-200811-I>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002. Internet: Timestamps", RFC 3339, July 2002.
[RFC4627] Crockford, D., "The application/json Media Type for
JavaScript Object Notation (JSON)", RFC 4627, July 2006.
[RFC5077] Salowey, J., Zhou, H., Eronen, P., and H. Tschofenig, [RFC5077] Salowey, J., Zhou, H., Eronen, P., and H. Tschofenig,
"Transport Layer Security (TLS) Session Resumption without "Transport Layer Security (TLS) Session Resumption without
Server-Side State", RFC 5077, January 2008. Server-Side State", RFC 5077, January 2008.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
Presence Information Data Format Location Object (PIDF-LO) Presence Information Data Format Location Object (PIDF-LO)
Usage Clarification, Considerations, and Recommendations", Usage Clarification, Considerations, and Recommendations",
RFC 5491, March 2009. RFC 5491, March 2009.
[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,
August 2011. August 2011.
[RFC6953] Mancuso, A., Probasco, S., and B. Patil, "Protocol to
Access White-Space (PAWS) Databases: Use Cases and
Requirements", RFC 6953, May 2013.
[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>.
13.2. Informative References 13.2. Informative References
[ETSI-EN-301-598] [ETSI-EN-301-598]
European Telecommunication Standards Institute (ETSI), European Telecommunication Standards Institute (ETSI),
"TBD: (ETSI EN 301 598)", 2013, <TBD>. "Draft ETSI EN 301 598 (V1.0.0): White Space Devices
(WSD); Wireless Access Systems operating in the 470 MHz to
790 MHz frequency band; Harmonized EN covering the
essential requirements of article 3.2 of the R&TTE
Directive", July 2013, <http://www.etsi.org/deliver/
etsi_en/301500_301599/301598/01.00.00_20/
en_301598v010000a.pdf>.
[FCC-Review-2012-10] [FCC-Review-2012-10]
Federal Communications Commission, "Administration Topics Federal Communications Commission, "Administration Topics
Review", October 2012, <http://transition.fcc.gov/bureaus/ Review", October 2012, <http://transition.fcc.gov/bureaus/
oet/ea/presentations/files/oct12/ oet/ea/presentations/files/oct12/
2b-TCB-Admin-Issues-Oct-2012-GT.pdf>. 2b-TCB-Admin-Issues-Oct-2012-GT.pdf>.
[I-D.das-paws-protocol] [I-D.das-paws-protocol]
Das, S., Malyar, J., and D. Joslyn, "Device to Database Das, S., Malyar, J., and D. Joslyn, "Device to Database
Protocol for White Space", draft-das-paws-protocol-02 Protocol for White Space", draft-das-paws-protocol-02
(work in progress), July 2012. (work in progress), July 2012.
[I-D.wei-paws-framework] [I-D.wei-paws-framework]
Wei, X., Zhu, L., and P. McCann, "PAWS Framework", Wei, X., Zhu, L., and P. McCann, "PAWS Framework",
draft-wei-paws-framework-00 (work in progress), July 2012. draft-wei-paws-framework-00 (work in progress), July 2012.
[I-D.zyp-json-schema] [I-D.zyp-json-schema]
Zyp, K. and G. Court, "A JSON Media Type for Describing Galiegue, F., Zyp, K., and G. Court, "JSON Schema: core
the Structure and Meaning of JSON Documents", definitions and terminology", draft-zyp-json-schema-04
draft-zyp-json-schema-03 (work in progress), (work in progress), January 2013.
November 2010.
[ISO3166-1] [ISO3166-1]
"Country Codes", "Country Codes",
<http://www.iso.org/iso/country_codes.htm>. <http://www.iso.org/iso/country_codes.htm>.
[JSON-RPC] [JSON-RPC]
"JSON-RPC 2.0 Specification", "JSON-RPC 2.0 Specification",
<http://www.jsonrpc.org/specification>. <http://www.jsonrpc.org/specification>.
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
[RFC4627] Crockford, D., "The application/json Media Type for
JavaScript Object Notation (JSON)", RFC 4627, July 2006.
[RFC6953] Mancuso, A., Probasco, S., and B. Patil, "Protocol to
Access White-Space (PAWS) Databases: Use Cases and
Requirements", RFC 6953, May 2013.
Appendix A. Changes / Author Notes. Appendix A. Changes / Author Notes.
Changes from 07:
o Propose ruleset ID name for ETSI: ETSI-EN-301-598-1.0.0-draft
o Change TBD email address to paws-iana-TBD@ietf.org for proposing
changes to the PAWS IANA registries
o Moved discussion of required vCard properties to regulatory-
specific sections
o Fixed vCard examples for organization names: Use "fn" property,
but set "kind" to "org".
o Shorten parameter names:
* freqHz -> hz
* powerDbmPerBw -> dbm
Changes from 06: Changes from 06:
o Multi-ruleset support: o Multi-ruleset support:
* Changed RulesetInfo to have single ruleset ID * Changed RulesetInfo to have single ruleset ID
* Changed INIT_RESP to return a list of RulesetInfo parameters, * Changed INIT_RESP to return a list of RulesetInfo parameters,
rather than a single one rather than a single one
* Changed REGISTRATION_RESP to return a list of RulesetInfo * Changed REGISTRATION_RESP to return a list of RulesetInfo
parameters to indicate the regulatory domains for which parameters to indicate the regulatory domains for which
registration was accepted registration was accepted
* Added SpectrumSpec (Section 5.9) parameter to represent * Added SpectrumSpec (Section 5.9) parameter to represent
available-spectrum specification for one regulatory domain, available-spectrum specification for one regulatory domain,
 End of changes. 56 change blocks. 
136 lines changed or deleted 165 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/