RFC 8262
Content-ID Header Field in the Session Initiation Protocol (SIP), October 2017
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 5621, RFC 5368, RFC 6442
- Authors:
- C. Holmberg
I. Sedlacek - Stream:
- IETF
- Source:
- sipcore (art)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8262
Discuss this RFC: Send questions or comments to the mailing list sipcore@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8262
Abstract
This document specifies the Content-ID header field for usage in the Session Initiation Protocol (SIP). This document also updates RFC 5621, which only allows a Content-ID URL to reference a body part that is part of a multipart message-body. This update enables a Content-ID URL to reference a complete message-body and metadata provided by some additional SIP header fields.
This document updates RFC 5368 and RFC 6442 by clarifying their usage of the SIP Content-ID header field.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.