GEOPRIV Layer 7 Location Configuration Protocol; Problem Statement and Requirements
draft-tschofenig-geopriv-l7-lcp-ps-03
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Hannes Tschofenig , Henning Schulzrinne | ||
Last updated | 2008-04-16 (Latest revision 2006-10-25) | ||
Replaced by | draft-ietf-geopriv-l7-lcp-ps | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-geopriv-l7-lcp-ps | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document provides a problem statement, lists requirements and captures discussions for a GEOPRIV Layer 7 Location Configuration Protocol (LCP). This protocol aims to allow an end host to obtain location information, by value or by reference, from a Location Information Server (LIS) that is located in the access network. The obtained location information can then be used for a variety of different protocols and purposes. For example, it can be used as input to the Location-to-Service Translation Protocol (LoST) or to convey location within SIP to other entities.
Authors
Hannes Tschofenig
Henning Schulzrinne
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)