Skip to main content

Multiple SIP Reason Header Field Values

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Robert Sparks
Last updated 2022-05-16 (Latest revision 2021-11-12)
Replaced by draft-ietf-sipcore-multiple-reasons
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Associated None milestone
Jun 2023
Multiple Reasons values per protocol (PS) to the IESG
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-sipcore-multiple-reasons
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:


The SIP Reason Header Field as defined in RFC 3326 allows only one Reason value per protocol value. Practice shows it is useful to allow multiple values with the same protocol value. This update to RFC 3326 allows multiple values for an indicated registered protocol when that protocol defines what the presence of multiple values means.


Robert Sparks

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)