Hi,
Please find few comments below, based on my reading of the spec.
1. Section 2.2 states Slave device as a device without geolocation
capability. I think the phrasing there need to be different. A Slave device
may or may not have geolocation capability, but does not directly query the
database. Also a mobile Slave device, can it not switch as master device in
adhoc?
2. It will be a good thing to include 'timestamp:string |
requirted' paramter in all the protocol transactions
3. Section 4.3.2 REGISTRATION_RESP should include 'rulesetInfo:RulesetInfo
as required' parameter.
4. Section 4.4.4 AVAIL_SPECTRUM_REQ, Can this also include an optional
requirement of minimum usage time? That is a master prefers to use the
available spectrum for a minimum duration without interruption, and the
database responds accordingly. This will help in ensuring QoS for whitespace
transmission.
5. REGISTRATION_REQ, and SPECTRUM_USE_NOTIFY transctions; can it have
repsonses like accepted/denied by database?
Thanks and Regards,
Sajeev
-----Original Message-----
From: Sajeev Manikkoth [mailto:[email protected]]
Sent: Wednesday, July 24, 2013 7:30 PM
To: '[email protected]'; '[email protected]'
Subject: RE: [paws] Reviews requested for
http://tools.ietf.org/html/draft-ietf-paws-protocol-06
Hi,
Please find few comments below, based on my reading of the spec.
1. Section 2.2 states Slave device as a device without geolocation
capability. I think the phrasing there need to be different. A Slave device
may or may not have geolocation capability, but does not directly query the
database. Also a mobile Slave device, can it not switch as master device in
adhoc?
2. It will be a good thing to include 'timestamp:string |
requirted' paramter in all the protocol transactions
3. Section 4.3.2 REGISTRATION_RESP should include 'rulesetInfo:RulesetInfo
as required' parameter.
4. Section 4.4.4 AVAIL_SPECTRUM_REQ, Can this also include an optional
requirement of minimum usage time? That is a master prefers to use the
available spectrum for a minimum duration without interruption, and the
database responds accordingly. This will help in ensuring QoS for whitespace
transmission.
5. REGISTRATION_REQ, and SPECTRUM_USE_NOTIFY transctions; can it have
repsonses like accepted/denied by database?
Thanks and Regards,
Sajeev
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
[email protected]
Sent: Friday, July 19, 2013 4:13 AM
To: [email protected]
Subject: [paws] Reviews requested for
http://tools.ietf.org/html/draft-ietf-paws-protocol-06
Folks,
I issued a WGLC on this document 4 weeks ago, and there was no feedback
received at all.
If you care about this document, you should review it and send your comments
to the list. If you review it and you have no comments, then please send a
mail to the list stating that you have reviewed the document and have no
comments.
Without reviews, we cannot make progress with the document. I cannot send it
to the IESG requesting publication.
- Gabor
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Bajko Gabor (Nokia-CIC/SiliconValley)
Sent: Wednesday, June 19, 2013 10:18 AM
To: [email protected]
Subject: [paws] WGLC on
http://tools.ietf.org/html/draft-ietf-paws-protocol-06
All,
The Editor of the document posted a new version and indicated that all open
issues raised on the list were resolved, and that there are no more open
issues he is aware of.
Therefore, I'd like to issue a wg last call on the document. We need reviews
and feedback in order to be able to progress the document.
Please read through the draft and send any comments you may have to the list
in the next 2-3 weeks.
If you review the draft and have no comments, send a note to the list that
the draft is good as it is, we need these notes as much as we need the
actual comments.
Thanks, Gabor
_______________________________________________
paws mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/paws
_______________________________________________
paws mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/paws
_______________________________________________
paws mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/paws
