metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 9366: Multiple SIP Reason Header Field Values

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9366
Published
March 2023
Authors
R. Sparks
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
4
Also known as
—
Updates:
RFC 3326

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9366-multiple-sip-reason-header-field-values