UpdatedPROPOSED STANDARDIETF stream

RFC 3204: MIME media types for ISUP and QSIG Objects

Still current, but amended. Parts of this document are changed or extended by RFC 3459, RFC 5621. Read both.

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

This document describes MIME types for application/ISUP and application/QSIG objects for use in SIP applications, according to the rules defined in RFC 2048. These types can be used to identify ISUP and QSIG objects within a SIP message such as INVITE or INFO, as might be implemented when using SIP in an environment where part of the call involves interworking to the PSTN. [STANDARDS-TRACK]

Document record

Document ID
RFC3204
Published
December 2001
Authors
E. Zimmerer; J. Peterson; A. Vemuri; L. Ong; F. Audet; M. Watson; M. Zonoun
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
10
Also known as
Updated by:
RFC 3459, RFC 5621

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3204-mime-media-types-for-isup-and-qsig-objects