Network Working Group T. Hansen
Request for Comments: 3938 AT&T Laboratories
Updates: 3458 October 2004
Category: Standards Track
Network Working Group T. Hansen
Request for Comments: 3938 AT&T Laboratories
Updates: 3458 October 2004
Category: Standards Track
Video-Message Message-Context
视频消息上下文
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.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
Abstract
摘要
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".
RFC 3458中定义的消息上下文标头描述消息的上下文（例如：传真消息或语音消息）。此规范使用一个额外的上下文值“video Message”扩展消息上下文头。
A receiving user agent (UA) may use this information as a hint to optimally present the message.
接收用户代理（UA）可以使用该信息作为最佳呈现消息的提示。
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 [1], 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 "none".
电子邮件可以用来传达许多不同形式的信息，用户将以不同的方式与不同类型的信息进行交互。如RFC 3458[1]中所述，消息的“消息上下文”传达有关用户期望与消息交互的方式的信息，例如显示哪个图标。RFC 3458然后为“语音消息”、“传真消息”、“寻呼机消息”、“多媒体消息”、“文本消息”和“无”注册消息上下文。
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:
电子邮件的一种形式是主要由视频流组成的消息。发送视频电子邮件的服务的示例包括连接到捕获视频流的手机的服务，以及使用连接到PC的网络摄像头的视频电子邮件服务。这些电子邮件目前包括两种类型，这两种类型都可以正确地视为视频消息：
1. those that embed the video stream internally within the message as a body part, and
1. 将视频流作为正文部分嵌入消息内部的那些，以及
2. those whose video stream is stored on a third party's video server.
2. 视频流存储在第三方视频服务器上的用户。
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.
但是，现有的消息上下文都不能正确识别此类视频消息。此规范使用一个额外的上下文值扩展消息上下文标头：video Message。
As specified in RFC 3458 [1], this document registers "video-message" in the "Internet Message Context Types" repository.
如RFC 3458[1]所述，本文档在“Internet消息上下文类型”存储库中注册“视频消息”。
Message-Context class name: video-message
消息上下文类名：视频消息
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.
message类摘要：指示其主要内容为视频邮件的邮件。主要内容是视频数据。上下文通常是录制在摄像机上的消息，或其主要目的是包含对录制在摄像机上的消息的外部引用的消息。
Person & email address to contact for further information: Tony Hansen, tony+msgctxt@maillennium.att.com.
联系人和电子邮件地址，以获取更多信息：Tony Hansen，Tony+msgctxt@maillennium.att.com.
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.
此标头仅用于指示消息上下文。因此，它只是一个提示，不需要消息用户代理的任何行为。
[1] Burger, E., Candell, E., Eliot, C., and G. Klyne, "Message Context for Internet Mail", RFC 3458, January 2003.
[1] Burger，E.，Candell，E.，Eliot，C.，和G.Klyne，“互联网邮件的消息上下文”，RFC 3458，2003年1月。
Tony Hansen AT&T Laboratories 200 Laurel Ave. Middletown, NJ 07748 USA
美国新泽西州米德尔顿劳雷尔大道200号托尼·汉森AT&T实验室，邮编：07748
EMail: tony+msgctxt@maillennium.att.com
EMail: tony+msgctxt@maillennium.att.com
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关IETF文件中权利的IETF程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。