Recommended Relationships between Different Types of Identifiers.
draft-schulzrinne-sipping-id-relationships-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Henning Schulzrinne , Eunsoo Shim | ||
| Last updated | 2005-07-11 | ||
| 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
Evolution of communications technologies brought us various types of identifiers or addresses that identify persons such as SIP URIs, email addresses, and telephone numbers. Proper relationships among different type of identifiers can enable various services, which, otherwise, are difficult to realize. This memo provides guidelines for managing relationships between SIP URIs other personal identifiers.
Authors
Henning Schulzrinne
Eunsoo Shim
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)