{"draft":"draft-ietf-sipcore-content-id-10","doc_id":"RFC8262","title":"Content-ID Header Field in the Session Initiation Protocol (SIP)","authors":["C. Holmberg","I. Sedlacek"],"format":["ASCII","HTML"],"page_count":"14","pub_status":"PROPOSED STANDARD","status":"PROPOSED STANDARD","source":"Session Initiation Protocol Core","abstract":"This document specifies the Content-ID header field for usage in the\r\nSession Initiation Protocol (SIP).  This document also updates RFC\r\n5621, which only allows a Content-ID URL to reference a body part\r\nthat is part of a multipart message-body.  This update enables a\r\nContent-ID URL to reference a complete message-body and metadata\r\nprovided by some additional SIP header fields.\r\n\r\nThis document updates RFC 5368 and RFC 6442 by clarifying their usage\r\nof the SIP Content-ID header field.","pub_date":"October 2017","keywords":["SIP"],"obsoletes":[],"obsoleted_by":[],"updates":["RFC5621","RFC5368","RFC6442"],"updated_by":[],"see_also":[],"doi":"10.17487\/RFC8262","errata_url":null}