Session Initiation Protocol (SIP) History-Info Header Call Flow Examples with PASSporT Diversion
draft-barnes-stir-passport-div-hi-callflows-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Mary Barnes | ||
| Last updated | 2018-01-04 (Latest revision 2017-07-03) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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 describes use cases and call flows which include the History-Info header field and a SIP Identity header field [I-D.ietf-stir-rfc4474bis] with a PASSport with diversion information in cases of retargeting. These use cases are derived from those provided in [RFC7131]. The objective is to describe the optimal way to correlate the History-Info header fields with a PASSporT with diversion information to increase the level of confidence in the History-Info header field by the terminating entity making use of the information.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)