RFC 3420: Internet Media Type message/sipfrag

In plain English — editorial summary, not part of the RFC

This document registers the message/sipfrag Multipurpose Internet Mail Extensions (MIME) media type. This type is similar to message/sip, but allows certain subsets of well formed Session Initiation Protocol (SIP) messages to be represented instead of requiring a complete SIP message. In addition to end-to-end security uses, message/sipfrag is used with the REFER method to convey information about the status of a referenced request. [STANDARDS-TRACK]

Document record

Document ID

RFC3420

Published

November 2002

Authors

R. Sparks

Status

PROPOSED STANDARD

Stream

IETF

Area

rai

Pages

8

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC3420
• Reported errata exist →

Topics

• mime
• multipurpose internet mail extensions

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 3464An Extensible Message Format for Delivery Status NotificationsUpdated

  January 2003

• RFC 3335MIME-based Secure Peer-to-Peer Business Data Interchange over the InternetCurrent

  September 2002

• RFC 3302Tag Image File Format (TIFF) - image/tiff MIME Sub-type RegistrationCurrent

  September 2002

• RFC 3745MIME Type Registrations for JPEG 2000 (ISO/IEC 15444)Current

  April 2004

• RFC 3798Message Disposition NotificationObsoleted

  May 2004

• RFC 3850Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate HandlingObsoleted

  July 2004

• RFC 3854Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME)Current

  July 2004

Also filed under

• PROPOSED STANDARD
• 2002
• IETF stream
• rai area