Video-Message Message-Context (RFC3938)
Original Publication Date: 2004-Oct-01
Included in the Prior Art Database: 2004-Oct-22
Internet Society Requests For Comment (RFCs)
The Message-Context header defined in RFC 3458 describes the context of a message (for example: fax-message or voice-message). This specification extends the Message-Context header with one additional context value: "video-message".
Network Working Group T. Hansen
Request for Comments: 3938 AT&T Laboratories
Updates: 3458 October 2004
Category: Standards Track
Status of this Memo
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.
Copyright (C) The Internet Society (2004).
The Message-Context header defined in RFC 3458 describes the context
of a message (for example: fax-message or voice-message). This
specification extends the Message-Context header with one additional
context value: "video-message".
A receiving user agent (UA) may use this information as a hint to
optimally present the message.
Email messages can be used to convey many different forms of
messages, and the user will interact with different types in
different ways. As explained in RFC 3458 , the "message context"
of the message conveys information about the way the user expects to
interact with the message, such as which icon to display. RFC 3458
then registers the message contexts for a "voice-message", "fax-
message", "pager-message", "multimedia-message", "text-message", and
Hansen Standards Track [Page 1]
RFC 3938 Video-Message Message-Context October 2004
2. Video Message
One form of email is a message that consists mostly of a video
stream. Examples of services that send video email are those
connected to cell phones that capture video streams, and video email
services that use webcams attached to a PC. These email messages
currently consist of two flavors, both of which can be properly
considered a video message:
1. those that embed the video stream internally within the message as
a body part, and
2. those whose video stream is stored on a third party's video
However, none of the existing message contexts properly identify such
video messages. This specification extends the Message-Context
header with one additional context value: video-message.
3. IANA Considerations
As specified in RFC 3458 , this document registers "video-message"
in the "Internet Message Context Types" repository.