FYI: Work of the IETF as related to Emergency Services and Location Payloads on the Internet

A couple of weeks ago I took the action to provide some background 
information on the work of the Internet Engineering Task Force (IETF) and the 
Geopriv Working Group that may be relevant to the work of the EM TC. While the 
stated charter of this WG has to do with location and privacy (stating privacy 
rules in which a location payload can be embedded, the actual scope has gone way 
beyond this to address the general issue of expressing location in a number of 
existing internet standards, such as SIP, PIDF, DHCP, and RADIUS.

 

At the upcoming meetings of the 62nd meeting of the IETF, the following 
documents will be discussed:

 

   a)draft-ietf-geopriv-common-policy.
   a) 
draft-rosen-nena-geopriv-requirements (10 min)
   b) 
draft-winterbottom-geopriv-pdif-lo-profile (10 min)
   c) 
draft-winterbottom-http-location-delivery (10 min)
   d) 
draft-guenther-geopriv-saml-policy (10 min)
   e) 
draft-thomson-domain-auth (10 min)

 

There are also several other documents of relevance:

 

   a.) draft-ietf-geopriv-dhcp-civil-05: This document has gone 
into the formal process of adoption. Dynamic Host Configuration Protocol (DHCPv4 
and DHCPv6) Option for Civic Addresses Configuration Information. Use cases are 
emergency response driven.

   b.) draft-ietf-geopriv-pidf-lo-03: This document has gone into 
the formal process of adoption as an internet standard. Defines 
a Presence-based GEOPRIV Location Object Format. Uses OGC GML 3.1. PIDF is 
the Presence Information Data Format.

   c. draft-ietf-geopriv-radius-lo-02.txt: Carrying Location 
Objects in RADIUS. This document has gone into the formal process of adoption as 
an internet standard.

   d.) Internet RFC 3825: Dynamic Host Configuration Protocol 
Option for Coordinate-based Location Configuration Information

The URL to the Geopriv WG site is http://www.ietf.org/html.charters/geopriv-charter.html . 
Some of the documents can be accessed from that location.

 

Many of these existing and emerging Internet standards will specify how 
location (like addresses) will be expressed as part of the internet 
infrastructure and potentially how a CAP message is actually populated - such as 
an E-911 call goes to a PSAP about a gas leak which results in a CAP message 
being broadcast to responders.

 

Cheers

 

Carl

 

 

 

Carl Reed, PhD
CTO and Executive Director Specification 
Program
OGC

 

The OGC: Helping the World to Communicate Geographically

 

---------------------

 

 

 

This communication, including attachments, is for the exclusive use of 
addressee and may contain proprietary, confidential or privileged information. 
If you are not the intended recipient, any use, copying, disclosure, 
dissemination or distribution is strictly prohibited. If you are not the 
intended recipient, please notify the sender  immediately by return email 
and delete this communication and destroy all copies.