Hi Peter,

Good comment. I will add another step to the registration service, step 3, to 
include an acknowledgement from the database to the master, with a result code.

Kind Regards,
Scott

From: "ext com>" <[email protected]<mailto:[email protected]>>
Date: Sat, 4 Feb 2012 08:30:07 -0500
To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Subject: [paws] registration protocol

Section 4.1.2 below describes the registration protocol

4.1.2. Device registration with trusted Database

<Delete>This use case</Delete><Insert>Registration</Insert> is
preliminary to creating a radio network using <Delete>TV</Delete>
white space; it is a prerequisite to
<Delete>other</Delete><Insert>the</Insert> use cases
<Insert>below</Insert>. The radio
network is created by a master device. Before the master device can
transmit in <Delete>TV</Delete> white space spectrum, it must contact a
trusted
database where the device can learn if any channels are available for
it to use. Before the database will provide information on available
<Delete>TV</Delete><Insert>radio</Insert> channels, the master device
must register with the trusted
database. Specific requirements for registration come from
individual regulatory domains and may be different.


This does not include any acknowledgement. This is something we do support in 
our FCC protocol. The reason being so we can accurately inform the device if 
the registration attempt fails. Listed below are some of the reasons, though I 
am sure there are more, we consider returning a failure code to the device:

malformed request (e.g., required fields missing)
FCC identifier not recognized or supported
FCC designated no channels available
location outside of regulatory domain
antenna height above 30 meters
HAAT above 76 meters

_______________________________________________ paws mailing list 
[email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/paws
_______________________________________________
paws mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/paws

Reply via email to