[{"author": "Man Zhang", "text": "

Good mornig

", "time": "2023-03-27T00:33:14Z"}, {"author": "Man Zhang", "text": "

good morning, everyone, this is Zhiwei Yan

", "time": "2023-03-27T00:33:38Z"}, {"author": "Erik Kline", "text": "

Reminder to all to wear masks while in the meeting room (and not speaking at the mic).

", "time": "2023-03-27T01:00:37Z"}, {"author": "Erik Kline", "text": "

RFC 6225 might be helpful?

", "time": "2023-03-27T01:35:24Z"}, {"author": "Satoru Matsushima", "text": "

DHCP?

", "time": "2023-03-27T01:37:07Z"}, {"author": "Erik Kline", "text": "

yeah, but can give clients a location

", "time": "2023-03-27T01:37:37Z"}, {"author": "Satoru Matsushima", "text": "

wifi may have their own mechanism in the spec

", "time": "2023-03-27T01:38:30Z"}, {"author": "Sri Gundavelli", "text": "

There are two aspects to this. DHCP Server can signal Civic Location to the STA. The STA in turn may signal some other location in the SIP headers. How can the e911 system be certain the signalled

", "time": "2023-03-27T01:48:10Z"}, {"author": "Sri Gundavelli", "text": "

location is indeed the right location

", "time": "2023-03-27T01:48:24Z"}, {"author": "Sri Gundavelli", "text": "

What the spec is saying is to generate a Secure Location Tag, which is more an index into the real location. The AP/AN will signal the SLT and the real location to the backend system.

", "time": "2023-03-27T01:49:44Z"}]