Which indirectly references the desired content, or to the content The requirements can be classified as applying either to the URI, Requirements outlined for content indirection. Thisĭocument specifies the usage of RFC 2017 necessary to fulfill the Mechanism, RFC 2017 by itself is not a complete solution. Most of the functionality needed for a SIP content indirection Location of the content rather than protocol-specific parameters forįTP, etc., as originally defined in RFC2046. The extension that RFC 2017 makes allows a generic URI to specify the Message/external-body MIME type originally defined in RFC2046. RFC 2017 defines a strong candidate for a replacement for the These attributes might include version information, the MIME type of Is the ability to specify various attributes on a per-URI basis. Purpose content indirection mechanism in SIP. Simplicity (a list of URIs delimited by end-of-line markers), itįailed to satisfy a number of the requirements for a more general. Previous attempts at solving the content indirection problem made use RFC 4483 Content Indirection in SIP Messages May 2006Įquivalent to, and should have the same treatment as, in-line body With theĮxception of the transport mechanism, indirect body parts are The purpose of content indirection is purely to provide anĪlternative transport mechanism for SIP MIME body parts. Reference to retrieve the content via a non-SIP transfer channel such The receiving party would then use this indirect Whereby the SIP message can contain an indirect reference to theĭesired content. In such scenarios, it is desirable to have a mechanism That needs to be conveyed does not directly reside on the endpoint or There may also be scenarios where the session-related data (body) Into a potentially separate data transfer channel. The transfer of this content out of the SIP signaling network and Indirect content can remedy this by moving Overwhelm intermediate signaling proxies, thereby unnecessarily It is also possible that the content size to be transferred might To annotate the (indirect) content with meta-data, which may be usedīy the recipient to determine whether or not to retrieve the content For bandwidth-limitedĪpplications such as cellular wireless, indirection provides a means There are numerous reasons why it might be desirable to specify theĬontent of the SIP message body indirectly. Unlike HTTP, SIP is notĭesigned as a general-purpose data transport protocol. One or more headers, and an optional body. SIP messages, like HTTP, are syntactically composed of a start line, The purpose of the Session Initiation Protocol (SIP) is toĬreate, modify, or terminate sessions with one or more participants. Relationship to Call-Info, Error-Info, andĪlert-Info Headers. Supplying Additional Comments about the IndirectĬontent. Specifying a Hash Value for the Indirect Content. RFC 4483 Content Indirection in SIP Messages May 2006 5.12. Specifying Multiple URIs for Content Indirection. Specifying the Purpose of the Indirect Content. Specifying the Size of the Indirect Content. Specifying the type of the Indirect Content. Specifying Versioning Information for the URI. Specifying the Location of the Content via a URI. Specifying Support for Content Indirection. Application of RFC 2017 to the Content Indirection Problem. These extensions are aimed atĪllowing any MIME part in a SIP message to be referred to indirectlyġ. This document defines an extension to the URL MIME External-BodyĪccess-Type to satisfy the content indirection requirements for the Distribution of this memo is unlimited.Ĭopyright (C) The Internet Society (2006). Official Protocol Standards" (STD 1) for the standardization stateĪnd status of this protocol. Please refer to the current edition of the "Internet Internet community, and requests discussion and suggestions for This document specifies an Internet standards track protocol for the Request for Comments: 4483 Cantata Technolgy, Inc.Ī Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages RFC 4483: A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages Įrrata Exist Network Working Group E.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |