Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 8262

Content-ID Header Field in the Session Initiation Protocol (SIP),October 2017

File formats:
icon for text fileicon for PDFicon for HTML
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 listsipcore@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 theSession Initiation Protocol (SIP). This document also updates RFC5621, which only allows a Content-ID URL to reference a body partthat is part of a multipart message-body. This update enables aContent-ID URL to reference a complete message-body and metadataprovided by some additional SIP header fields.

This document updates RFC 5368 and RFC 6442 by clarifying their usageof the SIP Content-ID header field.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp