Content-ID Header Field in the Session Initiation Protocol
RFC 8262, “Content-ID Header Field in the Session Initiation Protocol”, is a Proposed Standard document published in October 2017 by C. Holmberg, I. Sedlacek. It updates RFC 5368, RFC 5621, RFC 6442. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8262 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8261 Datagram Transport Layer Security Encapsulation of SCTP Packets
- RFC 8263 Group Domain of Interpretation GROUPKEY-PUSH Acknowledgement Message
- RFC 8260 Stream Schedulers and User Message Interleaving for the Stream Control Transmission Protocol
- RFC 8264 PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols
- RFC 8259 The JavaScript Object Notation Data Interchange Format
- RFC 8265 Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords
- RFC 8258 Generalized SCSI: A Generic Structure for Interface Switching Capability Descriptor Switching Capability Specific Information
- RFC 8266 Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames