PAWS meeting minutes The chair proposed the agenda, and there was no bashing. Pete Resnick explained the state of the protocol document. Now in AD review. In mid-review, some editorial comments. There is a mixing of regulatory requirements as opposed to protocol requirements that needs to be sorted.  Expect it to come back to the wg for review.  This is largely editorial. Vince Chen mentioned that he has edits prepared.  Vince will upload a new version. He presented changes.  Multiple rulesets now handled.  Shorten some names like hz & dbm.  Updated format of IANA section. Open item: ETSI modifications Should we go with 1.0.9 to match FCC rules or stick with 1.0.0 draft? Cesar Gutierrez suggested that the name would change. Pete: should we do this via a new IANA entry?  So leave things alone for now, review before approval by Pete.  If ETSI hasn't published yet, pull it out. Shortest time to approval is 3-4 weeks.  Likely it won't go to summer. No other comments received on the protocol document. Cesar: do we need a new parameter? Brian: We'll know when we see the new draft. Brian moved on to discovery. Gave an overview of LoST (RFC5222). Eliot: does the Swiss forest guide know just about neighbors? A: it knows about all other countries. Vince: is navigation done by client redirect or by recursion? A: can do either, but in emergency services they're doing it by recursion. Ray Bellis: this raises more questions than answers.  Is there one forest guide for a single service or multiple services? A: could be multiple services Ray: what sorts of entities operate the servers at the bottom of the tree? A: for emergency services, by governments Ray: how does the client discovery the local LoST server? Brian: Forest guides aggregate coverage below them to determine their coverage area. Brian: discovery: could be configured or discovered via DHCP Brian: the existing draft doesn't do an adequate job of explaining all of this Discussion Ray: what are you configuring? database server or database list server? Brian: assumption going in is that you know exactly where you are. Cesar: what are the regulatory requirements? In ETSI and UK, you must know where you are and you must get the list from the database list server. Eliot/Brian back and forth on clarification: LoST server does the polygon calculation for jurisdiction?  YES. Zhu Lei: list server/configure/LoST database discovery Peter: Do we just need a jurisdiction from LoST? #include Ray: what are the performance characteristics compared to a dynamic web pages? Brian: normal industrial server should handle 10s of thousands of queries per minute.  It's more calculation intensive than normal servers, but most queries are not near a border. You could deploy a LoST server could return a URI of a listing service. Eliot: why standardize this? Ray: want not to have to hardcode the regulatory listing service. Eliot: do database providers want this? Ray: don't mind, but it's really the device manufacturers that have to speak. Cesar: maybe it's too early to make a decision here? Pete Resnick: a little concerned that this might leave a hole.  Now that we have had this tutorial, are we over the hump? Brian: hum?  Interest? Ray: Pete made a compelling case. Vince: deployment and certification are a big deal. Hands: in the room: 6 for.  nobody objects. In jabber: 1 person. Boot Teco: is there open source? Brian: not at the moment, but it's a not a hard thing to do. Peter: good answer to what country are we in? LoST a good basis? In the room: 5 other options? no other. Peter says yes. Are we ready to adopt the draft as a WG item at this time? Not ready to adopt the draft. (no hands) AOB Adjourned.