A Mechanism for Content Indirection in SIP Messages
draft-olson-sip-content-indirect-mech-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Sean Olson | ||
Last updated | 2002-08-09 | ||
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 Internet-Draft proposes an extension to the URL MIME External- Body Access-Type as defined in RFC2017 [7] to satisfy the content indirection requirements defined in draft-ietf-sipping-content- indirect-00 [1]. These extensions are aimed at allowing any MIME part in a SIP message to be referred to indirectly via a URL [4].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)