MIME media types for DPNSS Objects
draft-mukundan-sipping-dpnss-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Anil Vydyam | ||
| Last updated | 2003-07-01 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes Multipart Internet Mail Extensions (MIME) type for application/Digital Private Network Signaling System (DPNSS) objects for use in Session Initiation Protocol (SIP) applications, according to the rules defined in RFC 2048. These types can be used to identify Digital Private Network Signaling System 1 (DPNSS 1) 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 DPNSS 1 based Private Networks. RFC 3204 addresses a similar need for Integrated Service Digital Network User Part (ISUP) and Q Signaling (QSIG).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)