Session Initiation Protocol: Requirements on Reason Information beyond the Status Code
draft-camarillo-sipping-reason-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Gonzalo Camarillo | ||
| Last updated | 2002-04-08 | ||
| 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-camarillo-sipping-reason-00.txt
https://www.ietf.org/archive/id/draft-camarillo-sipping-reason-00.txt
Abstract
Some applications need to know why a particular SIP message was issued. This document describes those applications and provides a set of requirements that a mechanism used to transport this type of information has to fulfill.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)