Coexistence of P-Asserted-ID and SIP Identity
draft-rosenberg-sip-identity-coexistence-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Jonathan Rosenberg | ||
| Last updated | 2006-06-21 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-rosenberg-sip-identity-coexistence-00.txt
https://www.ietf.org/archive/id/draft-rosenberg-sip-identity-coexistence-00.txt
Abstract
Two mechanisms have been defined to support forms of authenticated caller identity in the Session Initiation Protocol (SIP). The first, specified in RFC 3325, is the P-Asserted-ID header field. The second, termed "SIP Identity", defines the Identity and Identity-Info header fields and provides cryptographically verifiable identities. This document discusses how to use these mechanisms together.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)