Session Initiation Protocol Location Requirements
draft-polk-sipping-location-requirements-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | James Polk | ||
| Last updated | 2003-10-27 | ||
| 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
This document presents the requirements for an extension to the Session Initiation Protocol (SIP) [1] for conveyance of user location information from one Session Initiation Protocol (SIP) User Agent to another SIP User Agent. The idea that in some cases the UAC's location could affect proper routing of the SIP message is explored as well.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)