Skip to main content

Multiple SIP Reason Header Field Values
RFC 9366

Revision differences

Document history

Date By Action
2023-03-07
(System)
Received changes through RFC Editor sync (created alias RFC 9366, changed abstract to 'The SIP Reason header field as defined in RFC 3326 allows …
Received changes through RFC Editor sync (created alias RFC 9366, changed abstract to 'The SIP Reason header field as defined in RFC 3326 allows only one Reason value per protocol value.  Experience with more recently defined protocols shows it is useful to allow multiple values with the same protocol value.  This document updates RFC 3326 to allow multiple values for an indicated registered protocol when that protocol defines what the presence of multiple values means.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2023-03-07, changed IESG state to RFC Published, created updates relation between draft-ietf-sipcore-multiple-reasons and RFC 3326)
2023-03-07
(System) RFC published