Download L7LCP-ESW06 - Emergency Services Workshop

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts
no text concepts found
Transcript
Location
Configuration at
Layer 7
Andrew Newton, SunRocket, Inc.
GEOPRIV Working Group Co-chair, IETF
SDO Emergency Services Coordination Workshop
(ESW06)
Columbia University, New York, NY, US
6 October 2006
•
Overview
Location Configuration at the UA
•
•
•
This is the first step in conveying information from the
end user to the first responder.
In GEOPRIV terminology, the act of acquiring
location information of a “target” is called “sighting”.
Numerous methods.
•
•
•
Manual
Sensor measurements.
From/with the network, associated with layer
configuration
•
802 LLDP, DHCP, Layer 7 LCP, etc...
Location Configuration at Layer 7 - SDO Emergency Services Coordination Workshop (ESW06) - New York, NY - 6 October 2006
L7LCP
(Layer 7 Location
Configuration
• Justification:
Lower
layers doProtocol)
not
always provide location configuration.
• Desired by IP network operators.
• Usable to VSPs.
• Not restricted to subnet boundaries.
• Potential to circumvent NATs.
• Perceived extensibility (aka XML) and
enhanced security (aka TLS, XML
DSig) at application layer.
Location Configuration at Layer 7 - SDO Emergency Services Coordination Workshop (ESW06) - New York, NY - 6 October 2006
Challenges
• LIS discovery
•
because if the lower layer isn’t providing location information, it is
likely not pointing to it either
• End host location retrieval identifier
•
known to the end host and the LIS, but nobody else.
•
pervades the GEOPRIV model, but starts here
• Location-by-Reference
• Location signing.
Useful or not?
Location Configuration at Layer 7 - SDO Emergency Services Coordination Workshop (ESW06) - New York, NY - 6 October 2006
•
•
Location-byReference
Push vs. Poll; pres: vs. http:
End host may off-load publication of location information
to a 3rd party.
•
•
•
•
•
De-reference could offer tailored response to PSAP.
De-reference could be limited to PSAPs... but then
how do you know it is a PSAP. Security & Privacy
issue.
Network operator could keep location information out
of the hands of the customer. For emergencies, this
seems more harmful than helpful.
End host may subscribe to its own location from the
network (useful for mobility).
Seems more palatable for location configuration, very
controversial for location conveyance.
Location Configuration at Layer 7 - SDO Emergency Services Coordination Workshop (ESW06) - New York, NY - 6 October 2006
Location Signing
•
•
Signed location without an identity is not helpful. Easy to
copy.
Too much coordination required for it to work at Internet
scale.
•
•
PSAPs may regard calls without signatures as suspect. Is
that useful?
•
•
Thousands of PSAPS, millions of voice service providers
(aka businesses)
Only relevant to calls where no human contact is
established?
Caller identity, not network identity, is more useful for
accountability.
Location Configuration at Layer 7 - SDO Emergency Services Coordination Workshop (ESW06) - New York, NY - 6 October 2006
Work Status
• Design Team: drafted problem
statement and requirements.
• Next step: get approval of entire
working group.
• Then pick the protocol proposal that
best matches our requirements.
• Refine it.
• Ratify it in the working group.
• Ratify it in the IETF.
Location Configuration at Layer 7 - SDO Emergency Services Coordination Workshop (ESW06) - New York, NY - 6 October 2006
•
•
•
•
L7LCP Proposals
HELD
•
•
draft-winterbottom-http-location-delivery
http://www.ietf.org/internet-drafts/draft-winterbottom-httplocation-delivery-03.txt
LCP
•
•
draft-linsner-geopriv-lcp-00
expired
RELO
•
•
draft-schulzrinne-geopriv-relo
http://www.ietf.org/internet-drafts/draft-schulzrinnegeopriv-relo-00.txt
One more on the way...
Location Configuration at Layer 7 - SDO Emergency Services Coordination Workshop (ESW06) - New York, NY - 6 October 2006
•
References
L7 LCP Problem Statement & Requirements
•
•
•
IETF RFC 3693
IETF RFC 3694
DHCP Coordinate Based Location Configuration Information
•
•
http://www.ietf.org/internet-drafts/draft-tschofenig-geopriv-l7-lcp-ps02.txt
GEOPRIV Requirements and Security Threats Analysis
•
•
•
draft-tschofenig-geopriv-l7-lcp-ps
IETF RFC 3825
DHCP Option for Civic Address Configuration
•
•
draft-ietf-geopriv-dhcp-civil
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-civil-09.txt
Location Configuration at Layer 7 - SDO Emergency Services Coordination Workshop (ESW06) - New York, NY - 6 October 2006