rfc-3803

Content Duration MIME Header Definition

G. Vaudreuil, G. Parsons
date2004-06 streamIETF areaapp wgvpim statusDRAFT STANDARD pages5 canonicalhttps://www.rfc-editor.org/rfc/rfc3803 doi10.17487/RFC3803
This document describes the MIME header Content-Duration that is intended for use with any time varying media content (typically audio/* or video/*). [STANDARDS-TRACK]

obsoletes

Extracted elements (6)

design-rationale §2

The Content-Duration header allows simple determination of media duration without opening or decoding the content itself. Many encodings include duration internally, but a MIME header provides easy access without processing the binary data.

email

design-rationale §2.2

The time value in Content-Duration should be exact, but the exact value cannot be known without opening and playing the content. This mechanism simply allows placing a sender-determined value in the header; if an exact value is required, the content itself must be examined.

email

normative-requirement §3 MUST

All VPIM Messages MUST contain the audio/32KADPCM sub-type with the Content-Duration header field to carry the audio of a voice message.

email

protocol-element §2

The Content-Duration MIME header field specifies the time duration in seconds of time-varying media content (typically audio/* or video/*). The value is a single integer with no units tag.

email

security-consideration §4

In some environments, explicitly identifying the time duration of audio/* or video/* content in a header may be a security issue and should not be noted. Reliance on the Content-Duration header cannot be trusted for determining exact data size; the exact length must be determined by examining the data itself.

email, security

wire-format §2.1

The Content-Duration field syntax is: `duration := "Content-Duration" ":" 1*10DIGIT`. The value is 1 to 10 decimal digits representing seconds, with a practical upper bound of 2147483647 (2^31 - 1).

email