PAWS Database Discovery draftweipawsdatabasediscovery00 PAWS WG IETF 86
PAWS Database Discovery draft-wei-paws-database-discovery-00 PAWS WG IETF 86 Xinpeng Zhu Lei Nokia Internal Use Only
1. Motivation • The pre-configuration and provisioning are valid approaches for WS master devices to get DB addresses. • Device management and other provisional approaches are to retrieve DB address in operator networks. • This proposal is a light use of Lo. ST (RFC 5222) for WSDB discovery, with advanced services of Lo. ST – In case, WSD is failure to access pre-configured or cached DB server. Nokia Internal Use Only
2. Services Lo. ST provides to DB discovery • Lo. ST (RFC 5222) architecture and services – Mapping locations to PSAP URLs – Architecture considerations: seekers, resolvers, trees, and forest guides • Find Lo. ST service by ‘DHCP extension to Lo. ST’ (RFC 5223) • WS master device behaves as seekers, receives DB address from resolvers. • Recursion and Iteration help resolve DB address list to location – Features useful to PAWS DB discovery: • Inputs: location profiles, output: service list, DB server(s) • Address validation • Service boundaries Nokia Internal Use Only
3. Specification Lo. ST: Location-to-Service Translation Protocol. An overview of Lo. ST protocol [RFC 5222] : Lo. ST Client Figure : Protocol stack for discovery mechanism Location info: Lo. ST supports GPS and postal address Service Id. : needs IANA registration. Extensions to Lo. ST protocol to address issues ? For example, if we need region while sending requests Lo. ST Reslover Request message(Location info, service identifier) Mapping location info+service identifier to service URL(s) Response message(service URLs) Nokia Internal Use Only
4. Issues to be clarified further • Paws uses JSON, Lo. ST encodes as xml: preference option is using HTTP boundary mark, otherwise, goes to specify Lo. ST JSON encoding. • Conveying of regulatory domain The regulatory domain information needs to be conveyed to the WSD for later use. Pro: shorten the list of WSDB service list. Quickly resolve WSDB DS and DB addresses. • Location information of longitude and latitude as inputs to Lo. ST server may add region info, in case a master device request a serving Lo. ST server. Nokia Internal Use Only
4 a. Issues to be clarified further • WSDB DS process is to ensure the ability to find serving DB server for master devices. • By applying Lo. ST service to WSDB discovery, how Lo. ST and WSDB discovery service deployed? Possible owners of WSDB service records: ISP sor DB service providers. • Recursion and iteration can resolve two cases. Nokia Internal Use Only
4 b. Issues to be clarified further • Still need paws protocol to Mutual Authentication – For case of a number of DB URLs received. – Keep business relationship of DB service provider and DB master devices. • If WSDB discovery needs regulatory domain information? – Pro: prioritize DB address by regulatory domain and service info. Choose proper DB to connect. Nokia Internal Use Only
Questions to follow up or confirm in mail list • 1)Lo. ST service discovery • 2) WSDB discovery service, location/WSDB service mapping provided by ISP, or provided by WSDB service providers • 3) WSDB DS responses multiple DB addresses, how business relationship works when receiving address list • 4) WSDB DS could response DB address by receiving GPS information and/or postal address. • 5) Question: If WSDB SD request would include region information with GPS information? • 6) Lo. ST relies on U-NAPTR, and we all know how difficult is to get DNS admins add new records to their zones. • 7) The WG seems to prefer JSON encoding to XML, to be able to support lightweight devices, Lo. ST uses XML. Nokia Internal Use Only
Thanks!!! Nokia Internal Use Only
Backup a. • Discovery Request procedure An example: location info service identifier Nokia Internal Use Only
Backup b. • Discovery Response procedure An example: regulatory body service boundary info service URLs Nokia Internal Use Only
Backup c. • Service Identifier A new service identifier for PAWS database discovery needs to be defined. According to RFC 5031 [RFC 5031], a top-level service and a subservice are defined here. Nokia Internal Use Only
- Slides: 12