RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)

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

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.

Document record

Document ID

RFC8262

Published

October 2017

Authors

C. Holmberg; I. Sedlacek

Status

PROPOSED STANDARD

Stream

IETF

Area

art

Pages

14

Also known as

—

Updates:

RFC 5368, RFC 5621, RFC 6442

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC8262

Topics

• SIP

Related documents

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

• RFC 8266Preparation, Enforcement, and Comparison of Internationalized Strings Representing NicknamesCurrent

  October 2017

• RFC 8224Authenticated Identity Management in the Session Initiation Protocol (SIP)Updated

  February 2018

• RFC 8197A SIP Response Code for Unwanted CallsCurrent

  July 2017

• RFC 8373Negotiating Human Language in Real-Time CommunicationsUpdated

  May 2018

• RFC 8396Managing, Ordering, Distributing, Exposing, and Registering Telephone Numbers (MODERN): Problem Statement, Use Cases, and FrameworkCurrent

  July 2018

• RFC 8076A Usage for Shared Resources in RELOAD (ShaRe)Current

  March 2017

• RFC 8048Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceCurrent

  December 2016

• RFC 8497Marking SIP Messages to Be LoggedCurrent

  November 2018

Also filed under

• PROPOSED STANDARD
• 2017
• IETF stream
• art area