draft-ietf-paws-protocol-16.txt   draft-ietf-paws-protocol-17.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: March 9, 2015 Applied Communication Sciences Expires: March 12, 2015 Applied Communication Sciences
L. Zhu L. Zhu
Huawei Huawei
J. Malyar J. Malyar
iconectiv iconectiv
P. McCann P. McCann
Huawei Huawei
September 5, 2014 September 8, 2014
Protocol to Access White-Space (PAWS) Databases Protocol to Access White-Space (PAWS) Databases
draft-ietf-paws-protocol-16 draft-ietf-paws-protocol-17
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 48 skipping to change at page 1, line 48
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 March 9, 2015. This Internet-Draft will expire on March 12, 2015.
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 15, line 52 skipping to change at page 15, line 52
registration parameters. To simplify its registration logic, the registration parameters. To simplify its registration logic, the
Master Device MAY send a union of the registration information Master Device MAY send a union of the registration information
required by all supported rulesets. The Database MUST ignore all required by all supported rulesets. The Database MUST ignore all
parameters it does not understand. Consult the PAWS Parameters parameters it does not understand. Consult the PAWS Parameters
Registry (Section 9.2) for possible additional parameters. Registry (Section 9.2) for possible additional parameters.
4.4.2. REGISTRATION_RESP 4.4.2. REGISTRATION_RESP
The registration response message acknowledges successful The registration response message acknowledges successful
registration by including a RulesetInfo message for each ruleset in registration by including a RulesetInfo message for each ruleset in
which the registration is accepted. If the Database accepts none the which the registration is accepted. If the Database accepts the
registration for its supported rulesets, the Database MUST return the registration for none of the specified rulesets, the Database MUST
NOT_REGISTERED error (See Error Codes (Section 5.17)). return the NOT_REGISTERED error (See Error Codes (Section 5.17)).
+---------------------------------------+ +---------------------------------------+
|REGISTRATION_RESP | |REGISTRATION_RESP |
+----------------------------+----------+ 1..* +-------------+ +----------------------------+----------+ 1..* +-------------+
|rulesetInfos:list | required |------->| RulesetInfo | |rulesetInfos:list | required |------->| RulesetInfo |
|databaseChange:DbUpdateSpec | optional | +-------------+ |databaseChange:DbUpdateSpec | optional | +-------------+
|............................|..........| |............................|..........|
|*other:any | optional | |*other:any | optional |
+----------------------------+----------+ +----------------------------+----------+
 End of changes. 5 change blocks. 
7 lines changed or deleted 7 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/