| 1 |
'''Content Duration MIME Header Definition'''
|
| 2 |
- Network Working Group
|
| 3 |
-Request for Comments: [DEL(rfc3803)[2424]] [INS(rfc3803)[3803]]
|
| 4 |
-[INS(rfc3803)[Obsoletes: 2424]]
|
| 5 |
-Category: Standards Track
|
| 6 |
- G. Vaudreuil
|
| 7 |
- Lucent Technologies
|
| 8 |
- G. Parsons
|
| 9 |
- [DEL(rfc3803)[Northern Telecom]]
|
| 10 |
- [INS(rfc3803)[Nortel Networks]]
|
| 11 |
- [DEL(rfc3803)[September 1998]]
|
| 12 |
- [INS(rfc3803)[June 2004]]
|
| 13 |
|
| 14 |
* Status of this Memo
|
| 15 |
|
| 16 |
This document specifies an Internet standards track protocol for the
|
| 17 |
Internet community, and requests discussion and suggestions for
|
| 18 |
improvements. Please refer to the current edition of the "Internet
|
| 19 |
Official Protocol Standards" (STD 1) for the standardization state
|
| 20 |
and status of this protocol. Distribution of this memo is unlimited.
|
| 21 |
|
| 22 |
* Copyright Notice
|
| 23 |
> Copyright (C) The Internet Society [DEL(rfc3803)[(1998)]] [INS(rfc3803)[(2004)]]. [DEL(rfc3803)[All Rights Reserved.]]
|
| 24 |
|
| 25 |
* [DEL(rfc3803)[Overview]] [INS(rfc3803)[Abstract]]
|
| 26 |
> This document describes the MIME header Content-Duration that is
|
| 27 |
intended for use with any [DEL(rfc3803)[timed]] [INS(rfc3803)[time varying]] media content (typically audio/* or video/*).
|
| 28 |
|
| 29 |
*1. [DEL(rfc3803)[Abstract]] [INS(rfc3803)[Introduction]]
|
| 30 |
> This document describes the MIME header Content-Duration that is
|
| 31 |
intended for use with any time varying media content (typically
|
| 32 |
audio/* or video/*). The length of time is represented in seconds
|
| 33 |
without any units indication. [DEL(rfc3803)[This document obsoletes RFC 2424.]]
|
| 34 |
|
| 35 |
[INS(rfc3803)[
|
| 36 |
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
|
| 37 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
|
| 38 |
document are to be interpreted as described in RFC 2119 [REQ].
|
| 39 |
]INS]
|
| 40 |
|
| 41 |
* 2. Content-Duration Header Field
|
| 42 |
> Time varying media contents, for example, a spoken voice message or a
|
| 43 |
video clip, have an inherent time duration. Many audio and video
|
| 44 |
encodings may include their duration as header information or may
|
| 45 |
allow accurate calculation based on the byte length of the data.
|
| 46 |
However, it may be useful to present the time duration of the content
|
| 47 |
in a MIME header to allow its simple determination without dealing
|
| 48 |
with the actual content.
|
| 49 |
|
| 50 |
時変化媒体内容、例えば話し声メッセージやビデオは元から時間を持っています。
|
| 51 |
多くの音声や動画の符号化はこの時間情報を頭部情報として含めていたり、
|
| 52 |
データのバイト長に基づいて正確に計算できたりします。
|
| 53 |
しかし、実際の内容を処理せずに MIME
|
| 54 |
頭で簡単に内容の時間を決定できれば便利です。
|
| 55 |
|
| 56 |
[DEL(rfc3803)[
|
| 57 |
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
|
| 58 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
|
| 59 |
document are to be interpreted as described in [REQ].
|
| 60 |
]DEL]
|
| 61 |
|
| 62 |
**2.1[INS(rfc3803)[.]] Syntax
|
| 63 |
> The Content-Duration field's value is a single number specifying the
|
| 64 |
time duration in seconds of the content. Formally:
|
| 65 |
|
| 66 |
[CODE(MIME)[Content-Duration]] 欄の値は数値1つで、
|
| 67 |
内容の時間を秒数で指定します。
|
| 68 |
|
| 69 |
> duration := "Content-Duration" ":" 1*10DIGIT
|
| 70 |
|
| 71 |
> Note that practically (though highly unlikely in MIME media), the
|
| 72 |
upper bound on the numerical value of the time duration is (2^^31 -1)
|
| 73 |
or 2147483647.
|
| 74 |
|
| 75 |
実際上は (MIME 媒体ではありそうにありませんが) 時間の数値の上限は
|
| 76 |
[CODE(math)[2[SUP[31]] − 1]] (2147483647) であることに注意して下さい。
|
| 77 |
|
| 78 |
*2.2[INS(rfc3803)[.]] Semantics
|
| 79 |
> This field represents the time duration of the associated time
|
| 80 |
varying media content. The time duration is noted in seconds with no
|
| 81 |
units tag. The time value should be exact, however the exact value of
|
| 82 |
the time duration cannot be known without opening the content and
|
| 83 |
playing it. If an exact value must be known, then the latter method
|
| 84 |
should be used. This mechanism simply allows placing a sender
|
| 85 |
determined time duration value in the header for easy access.
|
| 86 |
|
| 87 |
この欄は時変化媒体内容に関する時間を表します。
|
| 88 |
時間は単位指定なしで秒単位で記述します。
|
| 89 |
時間値は、正確には内容を開いて演奏するまでわからないかもしれませんが、
|
| 90 |
正確であるべきです。
|
| 91 |
正確な値が分からないと行けない時には、実際に開いて確かめてみるべきです。
|
| 92 |
この方法簡単に時間値を決定できるように送信者が値を置けるようにするだけのものです。
|
| 93 |
|
| 94 |
> Though there are several ways to present this duration to the
|
| 95 |
recipient (e.g.[INS(rfc3803)[,]] with the inbox headers, when audio attachment
|
| 96 |
opened), the actual use of this field on reception is a local
|
| 97 |
implementation issue.
|
| 98 |
|
| 99 |
この時間を受信者に示す方法は色々あります
|
| 100 |
(例えば添付音声を開いた時に受信箱の頭部に提示) が、
|
| 101 |
受信者側でのこの欄の実際の用法は各実装の問題です。
|
| 102 |
|
| 103 |
*2.3[INS(rfc3803)[.]] Example
|
| 104 |
> In this example the content duration represents 33 seconds:
|
| 105 |
> Content-Duration: 33
|
| 106 |
|
| 107 |
この例では内容の時間は33秒です。
|
| 108 |
|
| 109 |
* 3. VPIM Usage
|
| 110 |
> The Content-Duration header field for the audio/32KADPCM sub-type is
|
| 111 |
a useful component of the VPIM specification [VPIM2]. All VPIM
|
| 112 |
Messages MUST contain this sub-type to carry the audio of a voice
|
| 113 |
message. It may be useful in some instances (e.g.[INS(rfc3803)[,]] viewing on a
|
| 114 |
simple MIME or non-MIME desktop) to have the time duration of the
|
| 115 |
voice message available without having to open the audio content.
|
| 116 |
|
| 117 |
[CODE(MIME)[[[audio/32kadpcm]]]] 亜型に対する
|
| 118 |
[CODE(MIME)[[[Content-Duration]]]] 頭欄は [[VPIM]]
|
| 119 |
仕様の便利な部品です。すべての VPIM
|
| 120 |
部品は動画メッセージの音声を伝達するためにこの亜型を含めなければ'''なりません'''。
|
| 121 |
場合によっては音声内容を開かなくても同がメッセージの時間が分かると
|
| 122 |
(例えば単純 MIME 机上や非 MIME 机上で見るのに) 便利です。
|
| 123 |
|
| 124 |
* 4. Security Considerations
|
| 125 |
> This definition introduces the option of explicitly identifying the
|
| 126 |
time duration of an audio/* or video/* content outside of the binary
|
| 127 |
data that forms the content. In some environments (though likely not
|
| 128 |
the majority), the identification of the actual time duration in a
|
| 129 |
header field may be a security issue and as a result should not be
|
| 130 |
noted. Reliance on the time indicated in this header field cannot be
|
| 131 |
trusted for the purposes of determining the exact size of the data.
|
| 132 |
The exact length of the data must be determined by examining the data
|
| 133 |
itself.
|
| 134 |
|
| 135 |
この定義は [CODE(MIME)[[[audio/[VAR[*]]]]]] や
|
| 136 |
[CODE(MIME)[[[video/[VAR[*]]]]]] の内容の時間を、
|
| 137 |
その内容を形成するバイナリ・データの外部で明示的に識別するという選択肢を導入します。
|
| 138 |
環境によっては (大部分ではないにしろ) 頭欄で実際の時間を識別すると安全上問題となり、
|
| 139 |
結果として示すべきではないとなるかもしれません。
|
| 140 |
この頭欄で示す次官はデータの実際の大きさを決定する目的では信頼できません。
|
| 141 |
データの実際の長さはデータ自体を検査して決定しなければなりません。
|
| 142 |
|
| 143 |
*5. References
|
| 144 |
**5.1. Normative References
|
| 145 |
[INS(rfc3803)[
|
| 146 |
>
|
| 147 |
[MIME2] Gellens, R., "The Text/Plain Format Parameter", RFC 2646,
|
| 148 |
August 1999.
|
| 149 |
|
| 150 |
[VPIM2R2] Vaudreuil, G., and G. Parsons, "Voice Profile for Internet
|
| 151 |
Mail - version 2 (VPIMv2)", RFC 3801, June 2004.
|
| 152 |
|
| 153 |
[REQ] Bradner, S., "Key words for use in RFCs to Indicate
|
| 154 |
Requirement Levels", BCP 14, RFC 2119, March 1997.
|
| 155 |
]INS]
|
| 156 |
**5.2. Informative References
|
| 157 |
[INS(rfc3803)[
|
| 158 |
>
|
| 159 |
[DUR] Parsons, G. and G. Vaudreuil, "Content Duration MIME Header
|
| 160 |
Definition", RFC 2424, September 1998.
|
| 161 |
|
| 162 |
[VPIM2] Vaudreuil, G. and G. Parsons, "Voice Profile for Internet
|
| 163 |
Mail - version 2", RFC 2421, September 1998.
|
| 164 |
]INS]
|
| 165 |
*6. Changes from RFC 2424
|
| 166 |
[INS(rfc3803)[
|
| 167 |
> Only editorial and boilerplate changes from RFC 2424 have been made
|
| 168 |
to this document.
|
| 169 |
]INS]
|
| 170 |
|
| 171 |
*[DEL(rfc3803)[5.]] [INS(rfc3803)[7.]] Authors' Addresses
|
| 172 |
[INS(rfc3803)[
|
| 173 |
>
|
| 174 |
Gregory M. Vaudreuil
|
| 175 |
Lucent Technologies
|
| 176 |
7291 Williamson Rd
|
| 177 |
Dallas, TX 75214
|
| 178 |
United States
|
| 179 |
|
| 180 |
EMail: gregv@ieee.org
|
| 181 |
]DEL]
|
| 182 |
|
| 183 |
>
|
| 184 |
Glenn W. Parsons
|
| 185 |
[DEL(rfc3803)[Northern Telecom]]
|
| 186 |
[INS(rfc3803)[Nortel Networks]]
|
| 187 |
P.O. Box 3511, Station C
|
| 188 |
Ottawa, ON K1Y 4H7
|
| 189 |
Canada
|
| 190 |
|
| 191 |
Phone: +1-613-763-7582
|
| 192 |
Fax: [DEL(rfc3803)[+1-613-763-4461]] [INS(rfc3803)[+1-613-763-2697]]
|
| 193 |
EMail: [DEL(rfc3803)[Glenn.Parsons@Nortel.ca]] [INS(rfc3803)[gparsons@nortelnetworks.com]]
|
| 194 |
|
| 195 |
[DEL(rfc3803)[
|
| 196 |
>
|
| 197 |
Gregory M. Vaudreuil
|
| 198 |
Lucent Technologies
|
| 199 |
17080 Dallas Parkway
|
| 200 |
Dallas, TX 75248-1905
|
| 201 |
United States
|
| 202 |
|
| 203 |
Phone/Fax: +1-972-733-2722
|
| 204 |
EMail: GregV@Lucent.Com
|
| 205 |
]DEL]
|
| 206 |
|
| 207 |
*6. References
|
| 208 |
[DEL(rfc3803)[
|
| 209 |
>
|
| 210 |
[MIME2] Freed, N., and N. Borenstein, "Multipurpose Internet Mail
|
| 211 |
Extensions (MIME) Part Two: Media Types", RFC 2046, November
|
| 212 |
1996.
|
| 213 |
|
| 214 |
[VPIM2] Vaudreuil, G., and G. Parsons, "Voice Profile for Internet
|
| 215 |
Mail - version 2", RFC 2421, September 1998.
|
| 216 |
|
| 217 |
[REQ] Bradner, S., "Key words for use in RFCs to Indicate Requirement
|
| 218 |
Levels", BCP 14, RFC 2119, March 1997.
|
| 219 |
]DEL]
|
| 220 |
|
| 221 |
*7. Full Copyright Statement
|
| 222 |
[DEL(rfc3803)[
|
| 223 |
> Copyright (C) The Internet Society (1998). All Rights Reserved.
|
| 224 |
|
| 225 |
This document and translations of it may be copied and furnished to
|
| 226 |
others, and derivative works that comment on or otherwise explain it
|
| 227 |
or assist in its implementation may be prepared, copied, published
|
| 228 |
and distributed, in whole or in part, without restriction of any
|
| 229 |
kind, provided that the above copyright notice and this paragraph are
|
| 230 |
included on all such copies and derivative works. However, this
|
| 231 |
document itself may not be modified in any way, such as by removing
|
| 232 |
the copyright notice or references to the Internet Society or other
|
| 233 |
Internet organizations, except as needed for the purpose of
|
| 234 |
developing Internet standards in which case the procedures for
|
| 235 |
copyrights defined in the Internet Standards process must be
|
| 236 |
followed, or as required to translate it into languages other than
|
| 237 |
English.
|
| 238 |
|
| 239 |
The limited permissions granted above are perpetual and will not be
|
| 240 |
revoked by the Internet Society or its successors or assigns.
|
| 241 |
|
| 242 |
This document and the information contained herein is provided on an
|
| 243 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
|
| 244 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
|
| 245 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
|
| 246 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
|
| 247 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
|
| 248 |
]DEL]
|
| 249 |
|
| 250 |
*8. Full Copyright Statement
|
| 251 |
[INS(rfc3803)[
|
| 252 |
Copyright (C) The Internet Society (2004). This document is subject
|
| 253 |
to the rights, licenses and restrictions contained in BCP 78, and
|
| 254 |
except as set forth therein, the authors retain all their rights.
|
| 255 |
|
| 256 |
This document and the information contained herein are provided on an
|
| 257 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
|
| 258 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
|
| 259 |
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
|
| 260 |
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
|
| 261 |
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
|
| 262 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
|
| 263 |
]INS]
|
| 264 |
|
| 265 |
*Intellectual Property
|
| 266 |
[INS(rfc3803)[
|
| 267 |
The IETF takes no position regarding the validity or scope of any
|
| 268 |
Intellectual Property Rights or other rights that might be claimed to
|
| 269 |
pertain to the implementation or use of the technology described in
|
| 270 |
this document or the extent to which any license under such rights
|
| 271 |
might or might not be available; nor does it represent that it has
|
| 272 |
made any independent effort to identify any such rights. Information
|
| 273 |
on the procedures with respect to rights in RFC documents can be
|
| 274 |
found in BCP 78 and BCP 79.
|
| 275 |
|
| 276 |
Copies of IPR disclosures made to the IETF Secretariat and any
|
| 277 |
assurances of licenses to be made available, or the result of an
|
| 278 |
attempt made to obtain a general license or permission for the use of
|
| 279 |
such proprietary rights by implementers or users of this
|
| 280 |
specification can be obtained from the IETF on-line IPR repository at
|
| 281 |
http://www.ietf.org/ipr.
|
| 282 |
|
| 283 |
The IETF invites any interested party to bring to its attention any
|
| 284 |
copyrights, patents or patent applications, or other proprietary
|
| 285 |
rights that may cover technology that may be required to implement
|
| 286 |
this standard. Please address the information to the IETF at ietf-
|
| 287 |
ipr@ietf.org.
|
| 288 |
]INS]
|
| 289 |
|
| 290 |
*Acknowledgement
|
| 291 |
[INS(rfc3803)[
|
| 292 |
> Funding for the RFC Editor function is currently provided by the
|
| 293 |
Internet Society.
|
| 294 |
]INS]
|
| 295 |
|
| 296 |
*memo |
Parent Directory
| 
Revision Log