| draft-ietf-sipcore-content-id-09.txt | draft-ietf-sipcore-content-id-10.txt | |||
|---|---|---|---|---|
| SIPCORE Working Group C. Holmberg | SIPCORE Working Group C. Holmberg | |||
| Internet-Draft I. Sedlacek | Internet-Draft I. Sedlacek | |||
| Updates: 5621, 5368, 6442 (if approved) Ericsson | Updates: 5621, 5368, 6442 (if approved) Ericsson | |||
| Intended status: Standards Track September 1, 2017 | Intended status: Standards Track September 2, 2017 | |||
| Expires: March 5, 2018 | Expires: March 6, 2018 | |||
| Content-ID header field in Session Initiation Protocol (SIP) | Content-ID header field in Session Initiation Protocol (SIP) | |||
| draft-ietf-sipcore-content-id-09 | draft-ietf-sipcore-content-id-10 | |||
| Abstract | Abstract | |||
| This document specifies the Content-ID header field for usage in the | This document specifies the Content-ID header field for usage in the | |||
| Session Initiation Protocol (SIP). The document also updates RFC | Session Initiation Protocol (SIP). The document also updates RFC | |||
| 5621, which only allows a Content-ID URL to reference a body part | 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 | that is part of a multipart message-body. This update enables a | |||
| Content-ID URL to reference a complete message-body and metadata | Content-ID URL to reference a complete message-body and metadata | |||
| provided by some additional SIP header fields. | provided by some additional SIP header fields. | |||
| skipping to change at page 1, line 39 ¶ | skipping to change at page 1, line 39 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on March 5, 2018. | This Internet-Draft will expire on March 6, 2018. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2017 IETF Trust and the persons identified as the | Copyright (c) 2017 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 3, line 46 ¶ | skipping to change at page 3, line 46 ¶ | |||
| 1.3. Problem statement | 1.3. Problem statement | |||
| It is currently not specified how to uniquely identify a complete | It is currently not specified how to uniquely identify a complete | |||
| message-body of a SIP message using a Content-ID header field, and | message-body of a SIP message using a Content-ID header field, and | |||
| how to reference a complete message-body using a Content-ID URL. | how to reference a complete message-body using a Content-ID URL. | |||
| NOTE: In [RFC5621], the Content-ID URL references a specific body | NOTE: In [RFC5621], the Content-ID URL references a specific body | |||
| part only. | part only. | |||
| Some existing specifications, for example [RFC5368], contain examples | Some existing specifications, such as [RFC5368], contain examples | |||
| that show usage of a SIP Content-ID header field referencing a | that show usage of a SIP Content-ID header field referencing a | |||
| complete message-body, eventhough such usage has never been | complete message-body, even though such usage has never been | |||
| specified. | specified. Many implementors have interpreted these examples to | |||
| indicate that such usage is allowed by the corresponding | ||||
| specification, despite the absence of language allowing it. This | ||||
| document updates the normative language in the affected documents to | ||||
| explicitly allow such usage. | ||||
| 1.4. Consequences | 1.4. Consequences | |||
| The examples below shows the consequences of the problem described | The examples below shows the consequences of the problem described | |||
| above. | above. | |||
| 1.4.1. Example 1 | 1.4.1. Example 1 | |||
| If a User Agent Client (UAC) sends an INVITE request conveying | If a User Agent Client (UAC) sends an INVITE request conveying | |||
| location as specified in [RFC6442], if the UAC decides not to include | location as specified in [RFC6442], if the UAC decides not to include | |||
| skipping to change at page 13, line 24 ¶ | skipping to change at page 13, line 24 ¶ | |||
| Header Name: Content-ID | Header Name: Content-ID | |||
| compact: | compact: | |||
| Reference: RFCXXXX | Reference: RFCXXXX | |||
| 9. Change log | 9. Change log | |||
| [RFC EDITOR NOTE: Please remove this section when publishing] | [RFC EDITOR NOTE: Please remove this section when publishing] | |||
| Changes from draft-ietf-sipcore-content-id-09 | ||||
| o Editorial change based on comment from Adam Roach. | ||||
| Changes from draft-ietf-sipcore-content-id-08 | Changes from draft-ietf-sipcore-content-id-08 | |||
| o Editorial change based on comment from Ben Campbell. | o Editorial change based on comment from Ben Campbell. | |||
| Changes from draft-ietf-sipcore-content-id-07 | Changes from draft-ietf-sipcore-content-id-07 | |||
| o Updates to affected RFCs. | o Updates to affected RFCs. | |||
| o Editorial changes and clarifications based on IESG review. | o Editorial changes and clarifications based on IESG review. | |||
| Changes from draft-ietf-sipcore-content-id-06 | Changes from draft-ietf-sipcore-content-id-06 | |||
| o Editorial changes and clarifications based on Gen-ART review from | o Editorial changes and clarifications based on Gen-ART review from | |||
| Elwyn Davies. | Elwyn Davies. | |||
| Changes from draft-ietf-sipcore-content-id-05 | Changes from draft-ietf-sipcore-content-id-05 | |||
| o Changes based on AD comments from Ben Campell: | o Changes based on AD comments from Ben Campbell: | |||
| o - Clarifying that Content-ID header field value is unique within | o - Clarifying that Content-ID header field value is unique within | |||
| the scope of a SIP message. | the scope of a SIP message. | |||
| Changes from draft-ietf-sipcore-content-id-04 | Changes from draft-ietf-sipcore-content-id-04 | |||
| o Minor editorial fix. | o Minor editorial fix. | |||
| Changes from draft-ietf-sipcore-content-id-03 | Changes from draft-ietf-sipcore-content-id-03 | |||
| o Changes based on doc shepherd review: | ||||
| o Changes based on doc shepard review: | ||||
| o - Reference to RFC 5234 added. | o - Reference to RFC 5234 added. | |||
| o - SIP message example added. | o - SIP message example added. | |||
| o - Editorial changes. | o - Editorial changes. | |||
| Changes from draft-ietf-sipcore-content-id-02 | Changes from draft-ietf-sipcore-content-id-02 | |||
| o Editorial changes based on comments from Paul Kyzivat. | o Editorial changes based on comments from Paul Kyzivat. | |||
| Changes from draft-ietf-sipcore-content-id-01 | Changes from draft-ietf-sipcore-content-id-01 | |||
| o Update to RFC 5621 added. | o Update to RFC 5621 added. | |||
| o Editorial changes. | o Editorial changes. | |||
| End of changes. 9 change blocks. | ||||
| 11 lines changed or deleted | 17 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||