Hi Hannes, Thanks for the explanation. Some comments/questions are inline below.
> -----Original Message----- > From: Hannes Tschofenig [mailto:[email protected]] > Sent: May-22-13 12:17 PM > To: Mark Jones > Cc: Hannes Tschofenig; 'Weixinpeng'; [email protected]; 'Peter McCann' > Subject: Re: [paws] draft-wei-paws-database-discovery-01 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Hi Mark, > > if this follows LoST closely then the mechanisms are pretty much standard > procedures used in a number of other protocols as well: > > First, you can pre-configure your server (since LoST would allow you to get a > response regardless where it enters the system). This makes a sense since > you may get your server configured statically as part of the software default > configuration. > Understood but I thought the goal of this draft was to get away from device pre-configuration. If one still has to configure the device with a URL then why not eliminate LoST and configure it with the URL of its "home WSDB" instead. If the device is roaming then it could get a redirect off the initial PAWS INIT_REQ/INIT_RESP to give it the URL of the WSDB appropriate for its roaming location. I realize that I'm coming late to these discussions so perhaps I missed a regulatory requirement that the WSDB DS provider be distinct from the WSDB provider. I don’t have an anti-LoST agenda here. I'm just trying to understand the motivation for a separate service. > Second, you can dynamically obtain information about a server that is closer > to your device via DHCP or (if that does not work) via a DNS lookup that first > uses a reverse DNS lookup of the public IP address. > These DHCP or reverse DNS methods assume that the non-WS IP connectivity provider (backhaul provider) has some business relationship with a WSDB DS provider for a given location. Is that correct? > Does this help? > It does but I think this needs to be elaborated further in this draft. This is the mandatory first step in the discovery procedure so I think it needs more than an "out of scope", e.g. a few examples referring to the scenarios in the requirements draft. Regards Mark > Ciao > Hannes > > On May 22, 2013, at 6:29 PM, Mark Jones wrote: > > > I’m unclear on how the Master device obtains the URL of a trusted > discovery server unless there is some pre-configuration involved. I > understand that DNS could be used if the Master device is already pre- > configured with a preferred/home TVWS DS URL (or a preferred/home > domain that is then resolved with U-NAPTR) but I don’t see how DHCP could > be used to bootstrap this information in the TVWS scenarios. Please could > you elaborate. > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.19 (Darwin) > Comment: GPGTools - http://gpgtools.org > > iQEcBAEBCgAGBQJRnO+aAAoJEGhJURNOOiAtt8IH/AoLd2re9qEoSKNTJnf2pE > UC > /wz7QnJ8q77JKGwWY9imoeHMBp35M+1wnIS6dbKmRQQQYaFfbW/9ffkEhB > VYPBga > HWpjl6acEulUBq4HaKJYQE4JZ7FMVlH1LZrblkNRTGYaflNFGFFlKf9jhxGOXZzi > grV/FOb6wATFp8lhGscwZ2iIK7j6p0rpx231YJtb5IqGc7wXho6wuGFlaaB8k+v+ > ayFVi7k/KUzXuk2madYwSXGDZjHwlwQfO1kvwZ1FC8oHHNDfZOI65rzawM+5 > 9n6T > 6hpkRE1AnFdn26+zD14QTFkyWeHzjntkJK0BFamyi6TReHozmyQ4BCBeFTO8+ > u0= > =LCBT > -----END PGP SIGNATURE----- _______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
