Analysis of TISPAN requirements for Connected Identity in the Session Initiation Protocol (SIP)
draft-elwell-sip-tispan-connected-identity-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2006-06-28 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-elwell-sip-tispan-connected-identity-01.txt
Abstract
ETSI TISPAN has presented Next Generation Network (NGN) requirements for the delivery of two identities for the caller and two identities for the callee in a SIP INVITE-initiated dialog. Although the solution for this in SIP is relatively straightforward for caller identity, the delivery of callee identity presents some additional problems. This document discusses the issues and suggests some candidate solutions. This work is being discussed on the sip@ietf.org mailing list.
Authors
John Elwell (john.elwell@siemens.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)