ECRIT Location Scope Requirements
draft-winterbottom-ecrit-location-scope-req-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | James Winterbottom | ||
| Last updated | 2005-02-09 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Special kinds of services require user location information to be authenticated and validated within a specific operating domain. An example of such a service is the emergency services network, where the location of a caller is known with in the domain of the telephone network, while the name or true identity of the caller is not intrinsically known. This paper describes the entities and key requirements necessary to provide such a service in an internet environment.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)