ISL Architectural Considerations
draft-nyckelgard-isl-arch-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | John A. Loughney , Soren Nyckelgard | ||
| Last updated | 2000-03-16 | ||
| 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
As more and more wireless devices interact with IP networks, location becomes an important parameter in providing and accessing services. This draft strives to provide an architecture to answer the following questions: 1) How can a terminal obtain its coordinates? 2) Where should a terminal store or register its coordinates? 3) How can a called party obtain the calling party's coordinates? 4) How can a terminal 'advertise' its location information
Authors
John A. Loughney
Soren Nyckelgard
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)