Voir toute la rfc dans une seule page
Page : 2 / 4
Télécharger le PDF
Auteur(s) : T. Hansen
Classé sous : User agent
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.
Message-Context class name:
Summary of the message class:
Indicates a message whose primary content is a video mail message.
The primary content is video data. The context is usually a
message recorded on a video camera, or a message whose primary
purpose is to contain an external reference to a message recorded
on a video camera.
Person & email address to contact for further information:
Tony Hansen, firstname.lastname@example.org.
4. Security Considerations
This header is intended to be an indicator of message context only.
As such, it is only a hint and requires no behavior on the part of a
message user agent.
Hansen Standards Track [Page 2]