Gabor, There is one more issue that has come to my attention.
When the Master Device is requesting the available spectrum on behalf of a Slave Device, the request message should have an optional field for identifying the Master Device (in addition to the one that already identifies the Slave Device). This should be a simple addition. -vince On Thu, May 16, 2013 at 2:35 PM, <[email protected]> wrote: > Vince, **** > > ** ** > > What are the remaining open issues in this latest draft, you or any of the > co-authors are aware of?**** > > Since there has been not much feedback, if you think there aren’t open > issues left, we could issue a working group last call.**** > > ** ** > > **- **gabor**** > > ** ** > > *From:* [email protected] [mailto:[email protected]] *On Behalf > Of *ext Vincent Chen > *Sent:* Tuesday, May 07, 2013 10:02 PM > *To:* [email protected] > *Subject:* Re: [paws] I-D Action: draft-ietf-paws-protocol-04.txt**** > > ** ** > > All,**** > > ** ** > > I have uploaded a new version that incorporates the items discussed at the > previous F2F and**** > > on the list.**** > > ** ** > > Diff: > http://www.ietf.org/rfcdiff?url1=draft-ietf-paws-protocol-03&difftype=--html&submit=Go%21&url2=draft-ietf-paws-protocol-04 > **** > > ** ** > > Summary of changes:**** > > ** ** > > o Expanded the Database Discovery mechanism to describe in more**** > > detail pre-configuration with URIs of databases and database-**** > > listing services, including mechanisms for updating the**** > > configurations when things change**** > > * Add database-change field to Available Spectrum Response**** > > (Section 4.4.2)**** > > o Added fields that are anticipated to be needed by the ETSI**** > > harmonized standard for White Space Devices:**** > > * Added bandwidth constraints to the Available Spectrum Response*** > * > > (Section 4.4.2)**** > > * Updated Available Spectrum Response to return RulesetInfo,**** > > rather than just a rule-set identifier**** > > * Added optional device-manufacturer and device-model IDs to the*** > * > > DeviceDescriptor (Section 5.2). message. Also moved fccId from** > ** > > this message to the IANA section.**** > > * Expanded IANA (Section 9) sections**** > > o Clarified restrictions on the specification of the vertices of a**** > > Polygon.**** > > o Changed default confidence level to 95% for a point with**** > > uncertainty**** > > o Clarified how devices without absolute time source can use the**** > > timestamps in the response messages**** > > o Change method names to start with "spectrum.paws." prefix**** > > o Added maximum string lengths**** > > o Updated author contact info**** > > o More typo fixes**** > > ** ** > > There are still some TBDs associated with the ETSI additions, but > otherwise has addressed all our prior open issues.**** > > ** ** > > -vince**** > > ** ** > > On Tue, May 7, 2013 at 9:56 PM, <[email protected]> wrote:**** > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Protocol to Access WS database Working > Group of the IETF. > > Title : Protocol to Access Spectrum Database > Author(s) : Vincent Chen > Subir Das > Lei Zhu > John Malyar > Peter J. McCann > Filename : draft-ietf-paws-protocol-04.txt > Pages : 88 > Date : 2013-05-07 > > Abstract: > Portions of the radio spectrum that are allocated to licensees are > available for non-interfering use. This available spectrum is called > "White Space." Allowing secondary users access to available spectrum > "unlocks" existing spectrum to maximize its utilization and to > provide opportunities for innovation, resulting in greater overall > spectrum utilization. > > One approach to manage spectrum sharing uses databases to report > spectrum availability to devices. To achieve interoperability among > multiple devices and databases, a standardized protocol must be > defined and implemented. This document defines such a protocol, the > "Protocol to Access White Space database" (PAWS). > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-paws-protocol > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-paws-protocol-04 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-paws-protocol-04 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > paws mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/paws**** > > > > **** > > ** ** > > -- > -vince **** > -- -vince
_______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
