rfc-3938

Video-Message Message-Context

T. Hansen

date2004-10 streamIETF wgnon working group statusPROPOSED STANDARD pages4 canonicalhttps://www.rfc-editor.org/rfc/rfc3938 doi10.17487/RFC3938

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. [STANDARDS-TRACK]

updates

rfc-3458 — Message Context for Internet Mail

Extracted elements (4)

design-rationale §2

No existing message context value (voice-message, fax-message, pager-message, multimedia-message, text-message, none) adequately identified video messages, motivating a new dedicated 'video-message' context value to cover video email from cell phones and webcam-based services.

protocol-element §2

The 'video-message' Message-Context value extends the Message-Context header (RFC 3458) to identify messages whose primary content is a video stream. It covers both messages that embed video internally as a body part and those referencing video stored on a third-party server.

registry §3.1

Registers the 'video-message' context value in the 'Internet Message Context Types' repository, as defined by RFC 3458. The primary content is video data, typically a message recorded on a video camera or a message referencing such content on an external server.

email, registry

security-consideration §4

The Message-Context header is intended only as a hint about message context and requires no mandatory behavior from a message user agent; it cannot be relied upon for security decisions.

email, security