RFC 4483: A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages
In plain English — editorial summary, not part of the RFC
This document defines an extension to the URL MIME External-Body Access-Type to satisfy the content indirection requirements for the Session Initiation Protocol (SIP). These extensions are aimed at allowing any MIME part in a SIP message to be referred to indirectly via a URI. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4483
- Published
- May 2006
- Authors
- E. Burger
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3555MIME Type Registration of RTP Payload FormatsObsoleted
July 2003
- RFC 3420Internet Media Type message/sipfragCurrent
November 2002
- RFC 5621Message Body Handling in the Session Initiation Protocol (SIP)Updated
September 2009
- RFC 5686RTP Payload Format for mU-law EMbedded Codec for Low-delay IP Communication (UEMCLIP) Speech CodecCurrent
October 2009
- RFC 3204MIME media types for ISUP and QSIG ObjectsUpdated
December 2001
- RFC 3009Registration of parityfec MIME typesObsoleted
November 2000
- RFC 4510Lightweight Directory Access Protocol (LDAP): Technical Specification Road MapCurrent
June 2006
- RFC 4374The application/xv+xml Media TypeCurrent
January 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?