[Search] [pdfized|bibtex] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]
Versions: 00 01 02 03 04 05 06 07 08 09 10 rfc3204       Standards Track
A new Request for Comments is now available in online RFC libraries.

        RFC 3204

        Title:      MIME media types for ISUP and QSIG Objects
        Author(s):  E. Zimmerer, J. Peterson, A. Vemuri, L. Ong,
                    F. Audet, M. Watson, M. Zonoun
        Status:     Standards Track
        Date:       December 2001
        Mailbox:    eric_zimmerer@yahoo.com, Aparna.Vemuri@Qwest.com,
                    jon.peterson@neustar.com, lyndon_ong@yahoo.com,
        Pages:      10
        Characters: 19712
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-sip-isup-mime-10.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3204.txt

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.

This document is a product of the Session Initiation Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.