1 / 19

IETF GEOPRIV Status

IETF GEOPRIV Status. Richard L. Barnes BBN Technologies GEOPRIV Secretary Emergency Services Workshop 5 21-23 October 2008. Agenda. GEOPRIV scope and context Current and upcoming GEOPRIV documents Integration points with other SDOs. GEOPRIV Overview.

gerda
Télécharger la présentation

IETF GEOPRIV Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IETF GEOPRIV Status Richard L. BarnesBBN TechnologiesGEOPRIV Secretary Emergency Services Workshop 5 21-23 October 2008

  2. Agenda • GEOPRIV scope and context • Current and upcoming GEOPRIV documents • Integration points with other SDOs

  3. GEOPRIV Overview

  4. GEOPRIV is the IETF working group for location and location privacy Develop Internet protocols for location functions: Configuring endpoints with location Transmitting location between points Requesting location information Location aspects of other protocols (e.g., SIP) These protocols are often the building blocks for work by other SDOs Scope of the GEOPRIV Working Group LocationServer LocationRecipient LocationDereferenceProtocol LocationFormats LocationConveyanceProtocol LocationConfigurationProtocol Client

  5. IETF scope is InternetProtocols Internet Protocols Focus on protocols (bits on the wire) between Internet / IP hosts Not what is said, or who (what host) says it How things are said Specify things only to the extent required for interoperability What: The semantics available in the protocol Who: Functional roles within the protocol • Focus on interoperable protocols for use over the Internet protocol (IP) • Generally, the only assumption used is that the devices use IP • No particular physical access or control plane • No particular network configuration • General mechanisms that can be specified to individual deployment cases

  6. Author submits an Internet Draft on a topic of interest to an IETF Working Group Working Group decides whether to take on the draft as a work item Once draft is adopted, it goes through rounds of comments and edits until it reaches consensus (passes “Working Group Last Call”) Cognizant Area Director forward the draft to the IESG (if approved) for final review IESG and Security Directorate reviews IETF Last Call for comments from the IETF at large IETF Process Flow RFC Publication IESG Approval SECDIR Review IETF Last Call Area Director Approval Working Group Last Call Working GroupProcessing Working Group Adoption Initial Draft

  7. Document Status

  8. GEOPRIV Documents • HTTP-Enabled Location Delivery (HELD) • Location Objects in RADIUS and Diameter • PIDF-LO Profile • Geolocation Policy • Layer-7 LCP Problem Statement / Requirements • Location by Reference Requirements • Binary Format for Geodetic Location in DHCP • Location Information Server Discovery • DHCP Option for Location by Reference IESG Processing Passed WGLC Still in Working Group Many items queued up behind HELD

  9. HTTP-Enabled Location Delivery (HELD) • HELD is a generic, application-layer protocol for requesting location • This document defines HELD as a Location Configuration Protocol (LCP), i.e., a way for end hosts to request location from the network • XML request/response carried over HTTP • Server bases positioning on IP address of incoming query • This is the base version of HELD, expected to be extended • Status: Awaiting revision to address IETF last call comments Positioning Resources HELDClient HELDServer(LIS) Database HELD Physical/MAC-layer info Other protocols draft-ietf-geopriv-http-location-delivery-07

  10. Location Objects in RADIUS / Diameter • A mechanism for embedding location information (in a binary format) into the RADIUS and Diameter AAA protocols • Provisioning of location information • Registration of endpoint-generated location • Many other SDOs are expected to make incorporate this mechanism in their AAA and location management functions • 3GPP IMS • WiMAX • TISPAN • Status: Waiting for new version to address IETF last call comments draft-ietf-geopriv-radius-lo-19

  11. PIDF-LO Profile • A set of clarifications and simplifications to the PIDF-LO format • The 9 rules of PIDF-LO usability, e.g. • Each GEOPRIV element MUST represent a discrete location • Different <geopriv> elements in the same PIDF MUST refer to the same location, or else be contained within different element types • When multiple PIDF-LO documents are received together, selection SHOULD be based on document order, the first being preferred • Restricts the set of shapes that can be used in a geodetic location to those specified in an OGC document profiling GML for IETF use • This document updates the PIDF-LO standard to constrain how implementations construct and use PIDF-LO documents • At the level of XML syntax, the format remains unchanged • Status: Submitted to IESG, awaiting action draft-ietf-geopriv-pdif-lo-profile-11

  12. Geolocation Policy • IETF long ago defined presence policy languages • Geolocation policy defines location-based policy • Grant access to location when target is within a given region • Grant access to location to a certain granularity • Passed WGLC several revisions ago, but was stalled by questions from the IESG, e.g., related to how uncertain location is used with these policies • May be relevant to OMA LOCSIP use cases (e.g., location-based instant messaging) • Status: Chair working to determine if current draft resolves IESG issues draft-ietf-geopriv-http-location-delivery-07

  13. Other WG items (still in progress) • Layer-7 LCP Problem Statement / Requirements • Requirements for an application layer LCP (i.e., HELD) • Mature; to be submitted for publication once HELD is finished • Location by Reference Requirements • Requirements for location by reference, and dereference protocols in particular (e.g., usage of SIP, HTTP, HELD for location retrieval) • Should be more mature before LbyR standards are published (e.g., the proposed usage of HELD as a dereference protocol) • Binary Format for Geodetic Location in DHCP • Document began as a way to convert DHCP binary geo format to decimal, but many in WG are calling for it to update how the binary format represents uncertainty • Significant digits vs. explicit error bars • Chair to produce a proposal on how to proceed

  14. Other WG items (cont’d) • Location Information Server Discovery • How an endpoint discovers a HELD server in the network • Critical to HELD deployment, probably non-controversial • DHCP Option for Location by Reference • How to embed a location URI in DHCP • Privacy concerns given lack of DHCP confidentiality

  15. Upcoming Items • To be added as milestones in next charter update • Update to GEOPRIV privacy architecture • Expressing Austrian civic addresses in the RFC 5139 XML format • Several HELD extensions that may be adopted • Usage of HELD for location-by-reference • Additional identifiers for HELD clients • Measurements for various positioning techniques • RTD, BSID, RSSI, GPS pseudo-ranges, etc. • Usage of HELD to obtain GPS assistance data

  16. Interactions with other SDOs

  17. Inter-SDO Interactions • GEOPRIV is beginning to have more interactions with other SDOs that are developing location systems over IP • At this point, mostly informal, through joint participants • WiMAX Forum is building a location solution using HELD • Requirement for “base” HELD, plus several extensions • WiMAX needs will inform order of HELD extensions • OMA LOCSIP has a lot of overlap with prior IETF work on location in SIP • Working with LOCSIP to determine how well existing IETF products fit OMA • Adapting IETF filter/trigger work to meet LOCSIP requirements • Beginning to discuss how to align HELD and SUPL… • Are there other SDOs that we should be working with?

  18. Summary • GEOPRIV defines location-relevant protocols for the Internet • Generic to the Internet, but adaptable to many types of access network • Focused on protocols, need other people to define how protocols are used • Most work right now is gated on publication of HELD • Next to do: Finish up some long-outstanding items, re-charter • Several HELD extensions in the queue • Beginning to coordinate with other SDOs, especially WiMAX and OMA

  19. IETF GEOPRIV Status Questions?

More Related