rfc7545v3.txt		rfc7545.txt
	skipping to change at page 2, line 22		skipping to change at page 3, line 7
	(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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
	2. Conventions and Terminology . . . . . . . . . . . . . . . . . 4		2. Conventions and Terminology . . . . . . . . . . . . . . . . . 5
	2.1. Conventions Used in This Document . . . . . . . . . . . . 4		2.1. Conventions Used in This Document . . . . . . . . . . . . 5
	2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5		2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6
	3. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 6		3. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 7
	3.1. Multi-ruleset Support . . . . . . . . . . . . . . . . . . 7		3.1. Multi-ruleset Support . . . . . . . . . . . . . . . . . . 8
	4. Protocol Functionalities . . . . . . . . . . . . . . . . . . 8		4. Protocol Functionalities . . . . . . . . . . . . . . . . . . 9
	4.1. Database Discovery . . . . . . . . . . . . . . . . . . . 10		4.1. Database Discovery . . . . . . . . . . . . . . . . . . . 11
	4.1.1. Preconfiguration . . . . . . . . . . . . . . . . . . 10		4.1.1. Preconfiguration . . . . . . . . . . . . . . . . . . 11
	4.1.2. Configuration Update: Database URI Changes . . . . . 10		4.1.2. Configuration Update: Database URI Changes . . . . . 11
	4.1.3. Error Handling . . . . . . . . . . . . . . . . . . . 10		4.1.3. Error Handling . . . . . . . . . . . . . . . . . . . 12
	4.2. PAWS Version . . . . . . . . . . . . . . . . . . . . . . 11		4.2. PAWS Version . . . . . . . . . . . . . . . . . . . . . . 12
	4.3. Initialization . . . . . . . . . . . . . . . . . . . . . 11		4.3. Initialization . . . . . . . . . . . . . . . . . . . . . 12
	4.3.1. INIT_REQ . . . . . . . . . . . . . . . . . . . . . . 12		4.3.1. INIT_REQ . . . . . . . . . . . . . . . . . . . . . . 13
	4.3.2. INIT_RESP . . . . . . . . . . . . . . . . . . . . . . 13		4.3.2. INIT_RESP . . . . . . . . . . . . . . . . . . . . . . 14
	4.4. Device Registration . . . . . . . . . . . . . . . . . . . 14		4.4. Device Registration . . . . . . . . . . . . . . . . . . . 15
	4.4.1. REGISTRATION_REQ . . . . . . . . . . . . . . . . . . 15		4.4.1. REGISTRATION_REQ . . . . . . . . . . . . . . . . . . 16
	4.4.2. REGISTRATION_RESP . . . . . . . . . . . . . . . . . . 15		4.4.2. REGISTRATION_RESP . . . . . . . . . . . . . . . . . . 17
	4.5. Available Spectrum Query . . . . . . . . . . . . . . . . 16		4.5. Available Spectrum Query . . . . . . . . . . . . . . . . 18
	4.5.1. AVAIL_SPECTRUM_REQ . . . . . . . . . . . . . . . . . 19		4.5.1. AVAIL_SPECTRUM_REQ . . . . . . . . . . . . . . . . . 21
	4.5.2. AVAIL_SPECTRUM_RESP . . . . . . . . . . . . . . . . . 21		4.5.2. AVAIL_SPECTRUM_RESP . . . . . . . . . . . . . . . . . 23
	4.5.3. AVAIL_SPECTRUM_BATCH_REQ . . . . . . . . . . . . . . 24		4.5.3. AVAIL_SPECTRUM_BATCH_REQ . . . . . . . . . . . . . . 25
	4.5.4. AVAIL_SPECTRUM_BATCH_RESP . . . . . . . . . . . . . . 27		4.5.4. AVAIL_SPECTRUM_BATCH_RESP . . . . . . . . . . . . . . 26
	4.5.5. SPECTRUM_USE_NOTIFY . . . . . . . . . . . . . . . . . 28		4.5.5. SPECTRUM_USE_NOTIFY . . . . . . . . . . . . . . . . . 28
	4.5.6. SPECTRUM_USE_RESP . . . . . . . . . . . . . . . . . . 29		4.5.6. SPECTRUM_USE_RESP . . . . . . . . . . . . . . . . . . 29
	4.6. Device Validation . . . . . . . . . . . . . . . . . . . . 30		4.6. Device Validation . . . . . . . . . . . . . . . . . . . . 31
	4.6.1. DEV_VALID_REQ . . . . . . . . . . . . . . . . . . . . 31		4.6.1. DEV_VALID_REQ . . . . . . . . . . . . . . . . . . . . 31
	4.6.2. DEV_VALID_RESP . . . . . . . . . . . . . . . . . . . 32		4.6.2. DEV_VALID_RESP . . . . . . . . . . . . . . . . . . . 32
	5. Protocol Parameters . . . . . . . . . . . . . . . . . . . . . 32		5. Protocol Parameters . . . . . . . . . . . . . . . . . . . . . 33
	5.1. GeoLocation . . . . . . . . . . . . . . . . . . . . . . . 32		5.1. GeoLocation . . . . . . . . . . . . . . . . . . . . . . . 34
	5.2. DeviceDescriptor . . . . . . . . . . . . . . . . . . . . 35		5.2. DeviceDescriptor . . . . . . . . . . . . . . . . . . . . 37
	5.3. AntennaCharacteristics . . . . . . . . . . . . . . . . . 36		5.3. AntennaCharacteristics . . . . . . . . . . . . . . . . . 38
	5.4. DeviceCapabilities . . . . . . . . . . . . . . . . . . . 37		5.4. DeviceCapabilities . . . . . . . . . . . . . . . . . . . 39
	5.5. DeviceOwner . . . . . . . . . . . . . . . . . . . . . . . 37		5.5. DeviceOwner . . . . . . . . . . . . . . . . . . . . . . . 39
	5.6. RulesetInfo . . . . . . . . . . . . . . . . . . . . . . . 38		5.6. RulesetInfo . . . . . . . . . . . . . . . . . . . . . . . 40
	5.7. DbUpdateSpec . . . . . . . . . . . . . . . . . . . . . . 39		5.7. DbUpdateSpec . . . . . . . . . . . . . . . . . . . . . . 41
	5.8. DatabaseSpec . . . . . . . . . . . . . . . . . . . . . . 40		5.8. DatabaseSpec . . . . . . . . . . . . . . . . . . . . . . 42
	5.9. SpectrumSpec . . . . . . . . . . . . . . . . . . . . . . 40		5.9. SpectrumSpec . . . . . . . . . . . . . . . . . . . . . . 42
	5.10. SpectrumSchedule . . . . . . . . . . . . . . . . . . . . 42		5.10. SpectrumSchedule . . . . . . . . . . . . . . . . . . . . 44
	5.11. Spectrum . . . . . . . . . . . . . . . . . . . . . . . . 42		5.11. Spectrum . . . . . . . . . . . . . . . . . . . . . . . . 44
	5.12. SpectrumProfile . . . . . . . . . . . . . . . . . . . . . 47		5.12. SpectrumProfile . . . . . . . . . . . . . . . . . . . . . 50
	5.13. FrequencyRange . . . . . . . . . . . . . . . . . . . . . 48		5.13. FrequencyRange . . . . . . . . . . . . . . . . . . . . . 51
	5.14. EventTime . . . . . . . . . . . . . . . . . . . . . . . . 49		5.14. EventTime . . . . . . . . . . . . . . . . . . . . . . . . 51
	5.15. GeoSpectrumSpec . . . . . . . . . . . . . . . . . . . . . 49		5.15. GeoSpectrumSpec . . . . . . . . . . . . . . . . . . . . . 52
	5.16. DeviceValidity . . . . . . . . . . . . . . . . . . . . . 50		5.16. DeviceValidity . . . . . . . . . . . . . . . . . . . . . 53
	5.17. Error Element . . . . . . . . . . . . . . . . . . . . . . 51		5.17. Error Element . . . . . . . . . . . . . . . . . . . . . . 53
	5.17.1. OUTSIDE_COVERAGE Error . . . . . . . . . . . . . . . 53		5.17.1. OUTSIDE_COVERAGE Error . . . . . . . . . . . . . . . 55
	5.17.2. DATABASE_CHANGE Error . . . . . . . . . . . . . . . 53		5.17.2. DATABASE_CHANGE Error . . . . . . . . . . . . . . . 56
	5.17.3. MISSING Error . . . . . . . . . . . . . . . . . . . 53		5.17.3. MISSING Error . . . . . . . . . . . . . . . . . . . 56
	6. Message Encoding . . . . . . . . . . . . . . . . . . . . . . 54		6. Message Encoding . . . . . . . . . . . . . . . . . . . . . . 57
	6.1. JSON-RPC Binding . . . . . . . . . . . . . . . . . . . . 54		6.1. JSON-RPC Binding . . . . . . . . . . . . . . . . . . . . 57
	6.1.1. Method Names . . . . . . . . . . . . . . . . . . . . 56		6.1.1. Method Names . . . . . . . . . . . . . . . . . . . . 59
	6.1.2. JSON Encoding of Data Models . . . . . . . . . . . . 56		6.1.2. JSON Encoding of Data Models . . . . . . . . . . . . 59
	6.2. Example Encoding: spectrum.paws.init Method . . . . . . . 57		6.2. Example Encoding: spectrum.paws.init Method . . . . . . . 61
	6.3. Example Encoding: spectrum.paws.getSpectrum Method . . . 58		6.3. Example Encoding: spectrum.paws.getSpectrum Method . . . 62
	6.4. Example Encoding: DeviceOwner vCard . . . . . . . . . . . 62		6.4. Example Encoding: DeviceOwner vCard . . . . . . . . . . . 66
	7. HTTPS Binding . . . . . . . . . . . . . . . . . . . . . . . . 63		7. HTTPS Binding . . . . . . . . . . . . . . . . . . . . . . . . 66
	8. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 65		8. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 68
	8.1. Defining Ruleset Identifiers . . . . . . . . . . . . . . 65		8.1. Defining Ruleset Identifiers . . . . . . . . . . . . . . 68
	8.2. Defining New Message Parameters . . . . . . . . . . . . . 65		8.2. Defining New Message Parameters . . . . . . . . . . . . . 69
	8.3. Defining Additional Error Codes . . . . . . . . . . . . . 66		8.3. Defining Additional Error Codes . . . . . . . . . . . . . 69
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 66		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69
	9.1. PAWS Ruleset ID Registry . . . . . . . . . . . . . . . . 67		9.1. PAWS Ruleset ID Registry . . . . . . . . . . . . . . . . 70
	9.1.1. Registration Template . . . . . . . . . . . . . . . . 67		9.1.1. Registration Template . . . . . . . . . . . . . . . . 70
	9.1.2. Initial Registry Contents . . . . . . . . . . . . . . 68		9.1.2. Initial Registry Contents . . . . . . . . . . . . . . 72
	9.2. PAWS Parameters Registry . . . . . . . . . . . . . . . . 74		9.2. PAWS Parameters Registry . . . . . . . . . . . . . . . . 78
	9.2.1. Registration Template . . . . . . . . . . . . . . . . 75		9.2.1. Registration Template . . . . . . . . . . . . . . . . 78
	9.2.2. Initial Registry Contents . . . . . . . . . . . . . . 75		9.2.2. Initial Registry Contents . . . . . . . . . . . . . . 78
	9.3. PAWS Error Code Registry . . . . . . . . . . . . . . . . 77		9.3. PAWS Error Code Registry . . . . . . . . . . . . . . . . 80
	9.3.1. Registration Template . . . . . . . . . . . . . . . . 78		9.3.1. Registration Template . . . . . . . . . . . . . . . . 81
	9.3.2. Initial Registry Contents . . . . . . . . . . . . . . 78		9.3.2. Initial Registry Contents . . . . . . . . . . . . . . 81
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 78		10. Security Considerations . . . . . . . . . . . . . . . . . . . 81
	10.1. Assurance of Proper Database . . . . . . . . . . . . . . 80		10.1. Assurance of Proper Database . . . . . . . . . . . . . . 83
	10.2. Protection against Modification . . . . . . . . . . . . 80		10.2. Protection against Modification . . . . . . . . . . . . 84
	10.3. Protection against Eavesdropping . . . . . . . . . . . . 81		10.3. Protection against Eavesdropping . . . . . . . . . . . . 84
	10.4. Client Authentication Considerations . . . . . . . . . . 81		10.4. Client Authentication Considerations . . . . . . . . . . 84
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 81		11. References . . . . . . . . . . . . . . . . . . . . . . . . . 85
	11.1. Normative References . . . . . . . . . . . . . . . . . . 81		11.1. Normative References . . . . . . . . . . . . . . . . . . 85
	11.2. Informative References . . . . . . . . . . . . . . . . . 83		11.2. Informative References . . . . . . . . . . . . . . . . . 86
			Appendix A. Database Listing Server Support . . . . . . . . . . 88
	Appendix A. Database Listing Server Support . . . . . . . . . . 85		Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 89
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 86		Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 89
	Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 86		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 90
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 86
	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		are strongly encouraged to read "Protocol to Access White-Space
	(PAWS) Databases: Use Cases and Requirements" [RFC6953] for use		(PAWS) Databases: Use Cases and Requirements" [RFC6953] for use
	cases, requirements, and additional background.		cases, 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 25, line 17		skipping to change at page 26, line 27
	batch requests, it MUST return an UNIMPLEMENTED error (see Table 1).		batch requests, it MUST return an UNIMPLEMENTED error (see Table 1).
	NOTE: Whether anticipated locations are allowed depends on the		NOTE: Whether anticipated locations are allowed depends on the
	specified ruleset. A parameter marked as optional may be required by		specified ruleset. A parameter marked as optional may be required by
	some rulesets.		some rulesets.
	+---------------------------------------------------+		+---------------------------------------------------+
	|AVAIL_SPECTRUM_BATCH_REQ |		|AVAIL_SPECTRUM_BATCH_REQ |
	+---------------------------------+-----------------+		+---------------------------------+-----------------+
	|deviceDesc:DeviceDescriptor | see description |		|deviceDesc:DeviceDescriptor | see description |
	|locations:list | required |--+		|locations:list | REQUIRED |--+
	|owner:DeviceOwner | optional | |		|owner:DeviceOwner | OPTIONAL | |
	|antenna:AntennaCharacteristics | optional | |		|antenna:AntennaCharacteristics | OPTIONAL | |
	|capabilities:DeviceCapabilities | optional | |		|capabilities:DeviceCapabilities | OPTIONAL | |
	|masterDeviceDesc:DeviceDescriptor| optional | |		|masterDeviceDesc:DeviceDescriptor| OPTIONAL | |
	|masterDeviceLocation:GeoLocation | see description | |		|masterDeviceLocation:GeoLocation | see description | |
	|requestType:string | optional | |		|requestType:string | OPTIONAL | |
	+.................................+.................+ |		+.................................+.................+ |
	|*other:any | optional | |		|*other:any | OPTIONAL | |
	+---------------------------------+-----------------+ |		+---------------------------------+-----------------+ |
	|		|
	1..* V		1..* V
	+-------------+		+-------------+
	| GeoLocation |		| GeoLocation |
	+-------------+		+-------------+
	Parameters:		Parameters:
	deviceDesc: The DeviceDescriptor (Section 5.2) for the device		deviceDesc: The DeviceDescriptor (Section 5.2) for the device
	skipping to change at page 28, line 23		skipping to change at page 29, line 30
	update its available spectrum data.		update its available spectrum data.
	4.5.5. SPECTRUM_USE_NOTIFY		4.5.5. SPECTRUM_USE_NOTIFY
	The spectrum-use notification message indicates the spectrum		The spectrum-use notification message indicates the spectrum
	anticipated to be used by the device.		anticipated to be used by the device.
	+---------------------------------------------------+		+---------------------------------------------------+
	|SPECTRUM_USE_NOTIFY |		|SPECTRUM_USE_NOTIFY |
	+---------------------------------+-----------------+		+---------------------------------+-----------------+
	|deviceDesc:DeviceDescriptor | required |		|deviceDesc:DeviceDescriptor | REQUIRED |
	|location:GeoLocation | see description |		|location:GeoLocation | see description |
	|masterDeviceDesc:DeviceDescriptor| optional |		|masterDeviceDesc:DeviceDescriptor| OPTIONAL |
	|masterDeviceLocation:GeoLocation | see description |		|masterDeviceLocation:GeoLocation | see description |
	|spectra:list | required |--+		|spectra:list | REQUIRED |--+
	|...................................................| |		|...................................................| |
	|*other:any | optional | |		|*other:any | OPTIONAL | |
	+---------------------------------+-----------------+ | 0..*		+---------------------------------+-----------------+ | 0..*
	V		V
	+--------------------------------+		+--------------------------------+
	|Spectrum |		|Spectrum |
	+---------------------+----------+		+---------------------+----------+
	|resolutionBwHz:float | REQUIRED |		|resolutionBwHz:float | REQUIRED |
	|profiles:list | REQUIRED |		|profiles:list | REQUIRED |
	+---------------------+----------+		+---------------------+----------+
	Parameters:		Parameters:
	skipping to change at page 33, line 22		skipping to change at page 35, line 12
	uncertainty parameters may be required by some rulesets (see also		uncertainty parameters may be required by some rulesets (see also
	[RFC7459]).		[RFC7459]).
	The data model for GeoLocation is illustrated below:		The data model for GeoLocation is illustrated below:
	+------------------------------------+		+------------------------------------+
	|GeoLocation |		|GeoLocation |
	+------------------+-----------------+		+------------------+-----------------+
	|point:Ellipse | see description |		|point:Ellipse | see description |
	|region:Polygon | see description |		|region:Polygon | see description |
	|confidence:int | optional |		|confidence:int | OPTIONAL |
	+------------------+-----------------+		+------------------+-----------------+
	Note: Point and region are mutually exclusive. Exactly one must		Note: Point and region are mutually exclusive. Exactly one must
	be present.		be present.
	+-------------------------------+		+-------------------------------+
	|Ellipse |		|Ellipse |
	+--------------------+----------+		+--------------------+----------+
	|center:Point | REQUIRED |--+		|center:Point | REQUIRED |--+
	|semiMajorAxis:float | OPTIONAL | |		|semiMajorAxis:float | OPTIONAL | |
	|semiMinorAxis:float | OPTIONAL | |		|semiMinorAxis:float | OPTIONAL | |
	skipping to change at page 33, line 45		skipping to change at page 35, line 35
	+---------------------------+		+---------------------------+
	|Point |		|Point |
	+----------------+----------+		+----------------+----------+
	|latitude:float | REQUIRED |		|latitude:float | REQUIRED |
	|longitude:float | REQUIRED |		|longitude:float | REQUIRED |
	+----------------+----------+		+----------------+----------+
	+-------------------------------+		+-------------------------------+
	|Polygon |		|Polygon |
	+-------------------+-----------+ 4..* +---------------------------+		+-------------------+-----------+ 4..* +---------------------------+
	|exterior:list | required |------>|Point |		|exterior:list | REQUIRED |------>|Point |
	+-------------------+-----------+ +----------------+----------+		+-------------------+-----------+ +----------------+----------+
	|latitude:float | REQUIRED |		|latitude:float | REQUIRED |
	|longitude:float | REQUIRED |		|longitude:float | REQUIRED |
	+----------------+----------+		+----------------+----------+
	Parameters:		Parameters:
	point: If present, it specifies the GeoLocation as a point.		point: If present, it specifies the GeoLocation as a point.
	Paradoxically, a "point" is parameterized using an Ellipse, where		Paradoxically, a "point" is parameterized using an Ellipse, where
	the center represents the location of the point and the distances		the center represents the location of the point and the distances
	skipping to change at page 37, line 20		skipping to change at page 39, line 16
	Device capabilities provide additional information that may be used		Device capabilities provide additional information that may be used
	by the device to provide additional information to the Database that		by the device to provide additional information to the Database that
	can help it to determine available spectrum. If the Database does		can help it to determine available spectrum. If the Database does
	not support device capabilities, it MUST ignore the parameter		not support device capabilities, it MUST ignore the parameter
	altogether.		altogether.
	+-------------------------------+		+-------------------------------+
	|DeviceCapabilities |		|DeviceCapabilities |
	+---------------------+---------+		+---------------------+---------+
	|frequencyRanges:list |optional |--+		|frequencyRanges:list |OPTIONAL |--+
	|.....................|.........| |		|.....................|.........| |
	|*other:any |optional | |		|*other:any |OPTIONAL | |
	+---------------------+---------+ | 0..*		+---------------------+---------+ | 0..*
	V		V
	+--------------------------------+		+--------------------------------+
	|FrequencyRange |		|FrequencyRange |
	+----------------------+---------+		+----------------------+---------+
	|startHz:float |required |		|startHz:float |REQUIRED |
	|stopHz:float |required |		|stopHz:float |REQUIRED |
	+----------------------+---------+		+----------------------+---------+
	Parameters:		Parameters:
	frequencyRanges: Optional FrequencyRange (Section 5.13) list. Each		frequencyRanges: Optional FrequencyRange (Section 5.13) list. Each
	FrequencyRange element contains start and stop frequencies in		FrequencyRange element contains start and stop frequencies in
	which the device can operate. When specified, the Database SHOULD		which the device can operate. When specified, the Database SHOULD
	NOT return available spectrum that falls outside these ranges.		NOT return available spectrum that falls outside these ranges.
	other Consult the PAWS Parameters Registry (Section 9.2) for		other Consult the PAWS Parameters Registry (Section 9.2) for
	skipping to change at page 38, line 42		skipping to change at page 40, line 34
	5.6. RulesetInfo		5.6. RulesetInfo
	RulesetInfo contains parameters for the ruleset of a regulatory		RulesetInfo contains parameters for the ruleset of a regulatory
	domain that is communicated using the Initialization (Section 4.3),		domain that is communicated using the Initialization (Section 4.3),
	Device Registration (Section 4.4), and Available Spectrum Query		Device Registration (Section 4.4), and Available Spectrum Query
	(Section 4.5) components.		(Section 4.5) components.
	+------------------------------------------+		+------------------------------------------+
	|RulesetInfo |		|RulesetInfo |
	+------------------------------------------+		+------------------------------------------+
	|authority:string | required |		|authority:string | REQUIRED |
	|rulesetId:string | required |		|rulesetId:string | REQUIRED |
	|maxLocationChange:float | see description |		|maxLocationChange:float | see description |
	|maxPollingSecs:int | see description |		|maxPollingSecs:int | see description |
	|..........................................|		|..........................................|
	|*other:any | optional |		|*other:any | OPTIONAL |
	+------------------------+-----------------+		+------------------------+-----------------+
	Parameters:		Parameters:
	authority: A string that indicates the regulatory domain to which		authority: A string that indicates the regulatory domain to which
	the ruleset applies is REQUIRED. It will normally be a 2-letter		the ruleset applies is REQUIRED. It will normally be a 2-letter
	country code defined by Country Codes - ISO 3166 [ISO3166-1].		country code defined by Country Codes - ISO 3166 [ISO3166-1].
	rulesetId: The ID of a ruleset for the specified authority (see		rulesetId: The ID of a ruleset for the specified authority (see
	Ruleset ID Registry (Section 9.1)). The device can use this to		Ruleset ID Registry (Section 9.1)). The device can use this to
	skipping to change at page 39, line 45		skipping to change at page 41, line 41
	for possible additional parameters.		for possible additional parameters.
	5.7. DbUpdateSpec		5.7. DbUpdateSpec
	This element is provided by the Database to notify devices of an		This element is provided by the Database to notify devices of an
	upcoming change to the database URI.		upcoming change to the database URI.
	+-------------------------------+		+-------------------------------+
	|DbUpdateSpec |		|DbUpdateSpec |
	+---------------------+---------+ +--------------------------+		+---------------------+---------+ +--------------------------+
	|databases:list |required |------>|DatabaseSpec |		|databases:list |REQUIRED |------>|DatabaseSpec |
	+---------------------+---------+ 1..* +---------------+----------+		+---------------------+---------+ 1..* +---------------+----------+
	|name:string | REQUIRED |		|name:string | REQUIRED |
	|uri:string | REQUIRED |		|uri:string | REQUIRED |
	+---------------+----------+		+---------------+----------+
	Parameters:		Parameters:
	databases: List of one or more DatabaseSpec (Section 5.8) entries.		databases: List of one or more DatabaseSpec (Section 5.8) entries.
	A device needs to update its preconfigured entry for the		A device needs to update its preconfigured entry for the
	responding Database with the alternate Databases listed in the		responding Database with the alternate Databases listed in the
	skipping to change at page 44, line 8		skipping to change at page 46, line 8
	o Gaps in frequencies between consecutive spectrum profiles		o Gaps in frequencies between consecutive spectrum profiles
	represent unavailability for those frequencies.		represent unavailability for those frequencies.
	The following figure illustrates the Spectrum element and the		The following figure illustrates the Spectrum element and the
	SpectrumProfile list.		SpectrumProfile list.
	+-------------------------------+		+-------------------------------+
	|Spectrum |		|Spectrum |
	+---------------------+---------+		+---------------------+---------+
	|resolutionBwHz:float |required |		|resolutionBwHz:float |REQUIRED |
	|profiles:list |required |---+		|profiles:list |REQUIRED |---+
	+---------------------+---------+ | 0..*		+---------------------+---------+ | 0..*
	V		V
	+-----------------------------+		+-----------------------------+
	|SpectrumProfile |		|SpectrumProfile |
	+-------------------+---------+		+-------------------+---------+
	|list |required |		|list |REQUIRED |
	+-------------------+---------+		+-------------------+---------+
	|		|
	V 2..*		V 2..*
	+--------------------------+		+--------------------------+
	|SpectrumProfilePoint |		|SpectrumProfilePoint |
	+----------------+---------+		+----------------+---------+
	|hz:float |required |		|hz:float |REQUIRED |
	|dbm:float |required |		|dbm:float |REQUIRED |
	+----------------+---------+		+----------------+---------+
	Parameters:		Parameters:
	resolutionBwHz: This parameter defines the resolution bandwidth (in		resolutionBwHz: This parameter defines the resolution bandwidth (in
	hertz) over which permissible power spectral density is defined.		hertz) over which permissible power spectral density is defined.
	For example, FCC regulation would require one spectrum		For example, FCC regulation would require one spectrum
	specification at a bandwidth of 6 MHz, and ETSI regulation would		specification at a bandwidth of 6 MHz, and ETSI regulation would
	require two specifications, at 0.1 MHz and 8 MHz.		require two specifications, at 0.1 MHz and 8 MHz.
	skipping to change at page 48, line 17		skipping to change at page 50, line 31
	o The first frequency is inclusive; the last frequency is exclusive.		o The first frequency is inclusive; the last frequency is exclusive.
	NOTE: This encoding allows presentation of "ramps" where the slope of		NOTE: This encoding allows presentation of "ramps" where the slope of
	a line segment may be finite and non-zero.		a line segment may be finite and non-zero.
	The following figure illustrates the SpectrumProfile element.		The following figure illustrates the SpectrumProfile element.
	+-------------------------------+		+-------------------------------+
	|SpectrumProfile |		|SpectrumProfile |
	+---------------------+---------+		+---------------------+---------+
	|list |required |---+		|list |REQUIRED |---+
	+---------------------+---------+ | 2..*		+---------------------+---------+ | 2..*
	V		V
	+--------------------------+		+--------------------------+
	|SpectrumProfilePoint |		|SpectrumProfilePoint |
	+----------------+---------+		+----------------+---------+
	|hz:float |required |		|hz:float |REQUIRED |
	|dbm:float |required |		|dbm:float |REQUIRED |
	+----------------+---------+		+----------------+---------+
	Parameters of each point in the profile:		Parameters of each point in the profile:
	hz: The frequency, in hertz, at which the power level is defined.		hz: The frequency, in hertz, at which the power level is defined.
	dbm: The power level, expressed as dBm per resolution bandwidth, as		dbm: The power level, expressed as dBm per resolution bandwidth, as
	defined by the resolutionBwHz element of the enclosing Spectrum		defined by the resolutionBwHz element of the enclosing Spectrum
	(Section 5.11) element.		(Section 5.11) element.
	5.13. FrequencyRange		5.13. FrequencyRange
	FrequencyRange specifies a frequency range.		FrequencyRange specifies a frequency range.
	+--------------------------------+		+--------------------------------+
	|FrequencyRange |		|FrequencyRange |
	+----------------------+---------+		+----------------------+---------+
	|startHz:float |required |		|startHz:float |REQUIRED |
	|stopHz:float |required |		|stopHz:float |REQUIRED |
	+----------------------+---------+		+----------------------+---------+
	Parameters:		Parameters:
	startHz: The inclusive start of the frequency range (in hertz) is		startHz: The inclusive start of the frequency range (in hertz) is
	REQUIRED.		REQUIRED.
	stopHz: The exclusive end of the frequency range (in hertz) is		stopHz: The exclusive end of the frequency range (in hertz) is
	REQUIRED.		REQUIRED.
	5.14. EventTime		5.14. EventTime
	The EventTime element specifies the start and stop times of an		The EventTime element specifies the start and stop times of an
	"event". This is used to indicate the time period for which a		"event". This is used to indicate the time period for which a
	Spectrum (Section 5.11) is valid.		Spectrum (Section 5.11) is valid.
	+---------------------------+		+---------------------------+
	|EventTime |		|EventTime |
	+-----------------+---------+		+-----------------+---------+
	|startTime:string |required |		|startTime:string |REQUIRED |
	|stopTime:string |required |		|stopTime:string |REQUIRED |
	+-----------------+---------+		+-----------------+---------+
	Parameters:		Parameters:
	startTime: The inclusive start of the event is REQUIRED.		startTime: The inclusive start of the event is REQUIRED.
	stopTime: The exclusive end of the event is REQUIRED.		stopTime: The exclusive end of the event is REQUIRED.
	Both times are expressed using the format, YYYY-MM-DDThh:mm:ssZ, as		Both times are expressed using the format, YYYY-MM-DDThh:mm:ssZ, as
	defined by "Date and Time on the Internet: Timestamps" [RFC3339].		defined by "Date and Time on the Internet: Timestamps" [RFC3339].
	skipping to change at page 51, line 13		skipping to change at page 53, line 38
	length is 128 octets.		length is 128 octets.
	5.17. Error Element		5.17. Error Element
	If the Database responds to a PAWS request message with an error, it		If the Database responds to a PAWS request message with an error, it
	MUST include an Error element.		MUST include an Error element.
	+----------------------------------+		+----------------------------------+
	|Error |		|Error |
	+----------------+-----------------+		+----------------+-----------------+
	|code:int | required |		|code:int | REQUIRED |
	|message:string | optional |		|message:string | OPTIONAL |
	|data:any | see description |		|data:any | see description |
	+----------------+-----------------+		+----------------+-----------------+
	Parameters:		Parameters:
	code: An integer code that indicates the error type is REQUIRED.		code: An integer code that indicates the error type is REQUIRED.
	Values MUST be within the range -32768 to 32767, inclusive.		Values MUST be within the range -32768 to 32767, inclusive.
	message: A description of the error is OPTIONAL. It MAY be in any		message: A description of the error is OPTIONAL. It MAY be in any
	language. Its maximum length is 128 octets.		language. Its maximum length is 128 octets.
	skipping to change at page 82, line 6		skipping to change at page 85, line 20
	11. References		11. References
	11.1. Normative References		11.1. Normative References
	[JSON-RPC]		[JSON-RPC]
	"JSON-RPC 2.0 Specification",		"JSON-RPC 2.0 Specification",
	<http://www.jsonrpc.org/specification>.		<http://www.jsonrpc.org/specification>.
	[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,
			DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://www.rfc-editor.org/info/rfc2119>.
	[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000,		[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818,
			DOI 10.17487/RFC2818, May 2000,
	<http://www.rfc-editor.org/info/rfc2818>.		<http://www.rfc-editor.org/info/rfc2818>.
	[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:		[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
	Timestamps", RFC 3339, July 2002,		Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
	<http://www.rfc-editor.org/info/rfc3339>.		<http://www.rfc-editor.org/info/rfc3339>.
	[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, DOI 10.17487/RFC5077,
	<http://www.rfc-editor.org/info/rfc5077>.		January 2008, <http://www.rfc-editor.org/info/rfc5077>.
	[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, <http://www.rfc-editor.org/info/rfc5226>.		DOI 10.17487/RFC5226, May 2008,
			<http://www.rfc-editor.org/info/rfc5226>.
	[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax		[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
	Specifications: ABNF", STD 68, RFC 5234, January 2008,		Specifications: ABNF", STD 68, RFC 5234,
			DOI 10.17487/RFC5234, January 2008,
	<http://www.rfc-editor.org/info/rfc5234>.		<http://www.rfc-editor.org/info/rfc5234>.
	[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,
			DOI 10.17487/RFC5246, August 2008,
	<http://www.rfc-editor.org/info/rfc5246>.		<http://www.rfc-editor.org/info/rfc5246>.
	[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, DOI 10.17487/RFC5491, March 2009,
	<http://www.rfc-editor.org/info/rfc5491>.		<http://www.rfc-editor.org/info/rfc5491>.
	[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,		[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,
	August 2011, <http://www.rfc-editor.org/info/rfc6350>.		DOI 10.17487/RFC6350, August 2011,
			<http://www.rfc-editor.org/info/rfc6350>.
	[RFC7095] Kewisch, P., "jCard: The JSON Format for vCard", RFC 7095,		[RFC7095] Kewisch, P., "jCard: The JSON Format for vCard", RFC 7095,
	January 2014, <http://www.rfc-editor.org/info/rfc7095>.		DOI 10.17487/RFC7095, January 2014,
			<http://www.rfc-editor.org/info/rfc7095>.
	[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data		[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
	Interchange Format", RFC 7159, March 2014,		Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March
	<http://www.rfc-editor.org/info/rfc7159>.		2014, <http://www.rfc-editor.org/info/rfc7159>.
	[RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer		[RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
	Protocol (HTTP/1.1): Semantics and Content", RFC 7231,		Protocol (HTTP/1.1): Semantics and Content", RFC 7231,
	June 2014, <http://www.rfc-editor.org/info/rfc7231>.		DOI 10.17487/RFC7231, June 2014,
			<http://www.rfc-editor.org/info/rfc7231>.
	[RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre,		[RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre,
	"Recommendations for Secure Use of TLS and DTLS", RFC		"Recommendations for Secure Use of Transport Layer
	7525, April 2015,		Security (TLS) and Datagram Transport Layer Security
	<http://www.rfc-editor.org/info/rfc7525>.		(DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May
			2015, <http://www.rfc-editor.org/info/rfc7525>.
	11.2. Informative References		11.2. Informative References
	[ETSI-EN-301-598]		[ETSI-EN-301-598]
	European Telecommunication Standards Institute (ETSI),		European Telecommunication Standards Institute (ETSI),
	"ETSI EN 301 598 (V1.1.1): White Space Devices (WSD);		"ETSI EN 301 598 (V1.1.1): White Space Devices (WSD);
	Wireless Access Systems operating in the 470 MHz to 790		Wireless Access Systems operating in the 470 MHz to 790
	MHz TV broadcast band; Harmonized EN covering the		MHz TV broadcast band; Harmonized EN covering the
	essential requirements of article 3.2 of the R&TTE		essential requirements of article 3.2 of the R&TTE
	Directive", April 2014, <http://www.etsi.org/deliver/		Directive", April 2014, <http://www.etsi.org/deliver/
	skipping to change at page 83, line 40		skipping to change at page 87, line 17
	Review", October 2012,		Review", October 2012,
	<http://transition.fcc.gov/bureaus/oet/ea/presentations/		<http://transition.fcc.gov/bureaus/oet/ea/presentations/
	files/oct12/2b-TCB-Admin-Issues-Oct-2012-GT.pdf>.		files/oct12/2b-TCB-Admin-Issues-Oct-2012-GT.pdf>.
	[ISO3166-1]		[ISO3166-1]
	"Country Codes",		"Country Codes",
	<http://www.iso.org/iso/country_codes.htm>.		<http://www.iso.org/iso/country_codes.htm>.
	[RFC6953] Mancuso, A., Ed., Probasco, S., and B. Patil, "Protocol to		[RFC6953] Mancuso, A., Ed., Probasco, S., and B. Patil, "Protocol to
	Access White-Space (PAWS) Databases: Use Cases and		Access White-Space (PAWS) Databases: Use Cases and
	Requirements", RFC 6953, May 2013,		Requirements", RFC 6953, DOI 10.17487/RFC6953, May 2013,
	<http://www.rfc-editor.org/info/rfc6953>.		<http://www.rfc-editor.org/info/rfc6953>.
	[RFC7459] Thomson, M. and J. Winterbottom, "Representation of		[RFC7459] Thomson, M. and J. Winterbottom, "Representation of
	Uncertainty and Confidence in the Presence Information		Uncertainty and Confidence in the Presence Information
	Data Format Location Object (PIDF-LO)", RFC 7459, February		Data Format Location Object (PIDF-LO)", RFC 7459,
	2015, <http://www.rfc-editor.org/info/rfc7459>.		DOI 10.17487/RFC7459, February 2015,
			<http://www.rfc-editor.org/info/rfc7459>.
	[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,		Third Edition, Amendment 1, January 2000,
	<http://earth-info.nga.mil/GandG/publications/tr8350.2/		<http://earth-info.nga.mil/GandG/publications/tr8350.2/
	tr8350_2.html>.		tr8350_2.html>.
	Appendix A. Database Listing Server Support		Appendix A. Database Listing Server Support
	skipping to change at page 86, line 23		skipping to change at page 89, line 23
	The authors gratefully acknowledge the contributions of: Gabor Bajko,		The authors gratefully acknowledge the contributions of: Gabor Bajko,
	Ray Bellis, Teco Boot, Nancy Bravin, Rex Buddenberg, Gerald		Ray Bellis, Teco Boot, Nancy Bravin, Rex Buddenberg, Gerald
	Chouinard, Stephen Farrell, Michael Fitch, Joel M. Halpern, Daniel		Chouinard, Stephen Farrell, Michael Fitch, Joel M. Halpern, Daniel
	Harasty, Michael Head, Jussi Kahtava, Kalle Kulsmanen, Warren Kumari,		Harasty, Michael Head, Jussi Kahtava, Kalle Kulsmanen, Warren Kumari,
	Paul Lambert, Andy Lee, Anthony Mancuso, Basavaraj Patil, Scott		Paul Lambert, Andy Lee, Anthony Mancuso, Basavaraj Patil, Scott
	Probasco, Brian Rosen, Andy Sago, Peter Stanforth, John Stine, and		Probasco, Brian Rosen, Andy Sago, Peter Stanforth, John Stine, and
	Juan Carlos Zuniga.		Juan Carlos Zuniga.
	Contributors		Contributors
	This document draws heavily from draft-das-paws-protocol and draft-		This document draws heavily from draft-das-paws-protocol and
	wei-paws-framework. The editor would like to specifically call out		draft-wei-paws-framework. The editor would like to specifically call
	and thank the contributing authors of those two documents.		out and thank the contributing authors of those two documents.
	Donald Joslyn		Donald Joslyn
	Spectrum Bridge Inc.		Spectrum Bridge Inc.
	1064 Greenwood Blvd.		1064 Greenwood Blvd.
	Lake Mary, FL 32746		Lake Mary, FL 32746
	United States		United States
	EMail: d.joslyn@spectrumbridge.com		EMail: d.joslyn@spectrumbridge.com
	Xinpeng Wei		Xinpeng Wei
	Huawei		Huawei
End of changes. 42 change blocks.
	138 lines changed or deleted		147 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/