draft-ietf-sipping-content-indirect-00.txt   draft-ietf-sipping-content-indirect-01.txt 
SIPPING S. Olson SIPPING S. Olson
Internet-Draft Microsoft Internet-Draft Microsoft
Expires: December 18, 2002 June 19, 2002 Expires: November 30, 2002 June 2002
Requirements for Content Indirection in SIP Messages Requirements for Content Indirection in SIP Messages
draft-ietf-sipping-content-indirect-00 draft-ietf-sipping-content-indirect-01
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 18, 2002. This Internet-Draft will expire on November 30, 2002.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
Various applications of the Session Initiation Protocol (SIP) require Various applications of the Session Initiation Protocol (SIP) require
the exchange of information between endpoints that is potentially too the exchange of information between endpoints that is potentially too
large to reasonably send directly in a SIP message. This Internet- large to reasonably send directly in a SIP message. This Internet-
skipping to change at page 6, line 35 skipping to change at page 6, line 35
the content itself. the content itself.
It MUST be possible for the UAC and the UAS to indicate support of It MUST be possible for the UAC and the UAS to indicate support of
this content indirection mechanism. A fallback mechanism SHOULD this content indirection mechanism. A fallback mechanism SHOULD
be specified in the event that one of the parties is unable to be specified in the event that one of the parties is unable to
support content indirection. support content indirection.
It MUST be possible for the UAC and UAS to negotiate content types It MUST be possible for the UAC and UAS to negotiate content types
when using the content indirection mechanism. when using the content indirection mechanism.
It MUST be possible for the UAC and UAS to negotiate support for
URL scheme(s) to be used in the content indirection mechanism.
This is in addition to the ability to negotiate the content type.
It SHOULD be possible to ensure the integrity of the URLs when It SHOULD be possible to ensure the integrity of the URLs when
they are received by the remote party. they are received by the remote party.
It MUST be possible to process the content indirection without It MUST be possible to process the content indirection without
human intervention. human intervention.
It MUST allow for indirect transference of content in any SIP It MUST allow for indirect transference of content in any SIP
message which would otherwise carry that content as a body. message which would otherwise carry that content as a body.
The content indirection mechanism MUST be usable as part of a MIME The content indirection mechanism MUST be usable as part of a MIME
multipart body. [4] multipart body. [4]
References References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, March 1997. Levels", RFC 2119, March 1997.
[2] Rosenberg, J., Schulzrinne, Camarillo, Johnston, Peterson, [2] Rosenberg, J., Schulzrinne, Camarillo, Johnston, Peterson,
Sparks, Handley and Schooler, "SIP: Session Initiation Sparks, Handley and Schooler, "SIP: Session Initiation
Protocol", Internet Draft draft-ietf-sip-rfc2543bis-09, February Protocol", RFC 3261, June 2002.
2002.
[3] Berners-Lee, Fielding and Masinter, "Uniform Resource [3] Berners-Lee, Fielding and Masinter, "Uniform Resource
Identifiers (URI): Generic Syntax", RFC 2396, August 1996. Identifiers (URI): Generic Syntax", RFC 2396, August 1996.
[4] Freed and Borenstein, "Multipurpose Internet Mail Extensions [4] Freed and Borenstein, "Multipurpose Internet Mail Extensions
(MIME) Part Two: Media Types", RFC 2046, November 1996. (MIME) Part Two: Media Types", RFC 2046, November 1996.
Author's Address Author's Address
Sean Olson Sean Olson
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/