Hi Mark,

** **
>
> Apologies for the late comments. In the -04 rev, I noticed that the term
> “listing server” is used before it is defined. I suggest adding an entry
> for “Database Listing Server” to the Terminology section to improve
> readability.
>

Thanks. I'll add this to the Terminology section.


> ****
>
> ** **
>
> I also wanted to check my understanding of the database discovery clauses. In 
> section 4, the draft states that database discovery MUST be supported by 
> Master devices. I understand from the draft that there are two types of 
> database discovery: pre-configured database discovery and dynamic discovery. 
> For the pre-configured database discovery, a Master device would determine 
> its location and consult its local config to find the appropriate WSDB(s). 
> For dynamic discovery, it would use the procedures in section 4.1.1 and 
> contact a Database Listing Server. Is this understanding correct so far?
>
> I would characterize the second as a preconfiguration of a Database
Listing Server, so it's not completely "dynamic".
This is driven by Ofcom (and potentially the ETSI) requirement that a
regulator may dictate that a device MUST contact
a listing server operated by the regulator for an approved list of DBs.
This is behavior that must be built into the device.

For example, a DB can inform the device that it is in the UK, but the
device must map "UK" to the URL of the
listing server specified by the UK regulator.


> ****
>
> ** **
>
> In section 4.1.1 you state “Specific message formats are defined by the 
> regulators”. In some regulatory domains, the regulator has deferred protocol 
> definition to the market participants but I’m taking this to mean that LoST 
> could be one the “specific message formats” selected by a regulator. Is this 
> the correct interpretation?
>
>
I suppose LoST could be one of the formats. One reservation is that it
might result in XML vs JSON discussions again :)

> ****
>
>
>
> -vince
_______________________________________________
paws mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/paws

Reply via email to