RFC 4770 - vCard Extensions for Instant Messaging (IM) 中文翻译

原文URL : https://datatracker.ietf.org/doc/html/rfc4770
文档标题 : RFC 4770 - 即时信息 (IM) 的 vCard 扩展功能
翻译方式 : 自动生成

Network Working Group                                        C. Jennings
Request for Comments: 4770                                 Cisco Systems
Category: Standards Track                                J. Reschke, Ed.
                                                              greenbytes
                                                            January 2007

vCard Extensions for Instant Messaging (IM)

即时信息 (IM) 的 vCard 扩展功能

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）。本备忘录的分发不受限制。

Abstract

摘要

This document describes an extension to vCard to support Instant Messaging (IM) and Presence Protocol (PP) applications. IM and PP are becoming increasingly common ways of communicating, and users want to save this contact information in their address books. It allows a URI that is associated with IM or PP to be specified inside a vCard.

本文档介绍了 vCard 的扩展，以支持即时信息（IM）和在岗协议（PP）应用程序。IM 和 PP 正成为日益普遍的通信方式，用户希望将这些联系人信息保存在他们的通讯录中。它允许在 vCard 中指定与 IM 或 PP 相关联的 URI。

Table of Contents

   1. Overview ........................................................2
   2. IANA Considerations .............................................3
   3. Formal Grammar ..................................................4
   4. Example .........................................................4
   5. Security Considerations .........................................4
   6. Acknowledgments .................................................4
   7. References ......................................................5
      7.1. Normative References .......................................5
      7.2. Informational References ...................................5

1. Overview

1. 概述

As more and more people use various instant messaging (IM) and presence protocol (PP) applications, it becomes important for them to be able to share this contact address information, along with the rest of their contact information. RFC 2425 [1] and RFC 2426 [2] define a standard format for this information, which is referred to as vCard. This document defines a new type in a vCard for representing instant IM and PP URIs. It is very similar to existing types for representing email address and telephone contact information.

随着越来越多的人使用各种即时信息（IM）和存在协议（PP）应用程序，能够与其他联系信息一起共享这些联系地址信息变得非常重要。RFC 2425 [1] 和 RFC 2426 [2] 为这种信息定义了一种标准格式，称为 vCard。本文档在 vCard 中定义了一种新类型，用于表示即时 IM 和 PP URI。它与现有的表示电子邮件地址和电话联系信息的类型非常相似。

The type entry to hold this new contact information is an IMPP type. The IMPP entry has a single URI (see RFC 3986 [3]) that indicates the address of a service that provides IM, PP, or both. Also defined are some parameters that give hints as to when certain URIs would be appropriate. A given vCard can have multiple IMPP entries, but each entry can contain only one URI. Each IMPP entry can contain multiple parameters. Any combination of parameters is valid, although a parameter should occur, at most, once in a given IMPP entry.

保存新联系信息的类型条目是 IMPP 类型。IMPP 条目有一个 URI（见 RFC 3986 [3]），表示提供 IM、PP 或两者的服务地址。此外，还定义了一些参数，提示何时适合使用某些 URI。一张给定的 vCard 可以有多个 IMPP 条目，但每个条目只能包含一个 URI。每个 IMPP 条目可以包含多个参数。任何参数组合都有效，但一个参数在给定的 IMPP 条目中最多只能出现一次。

The type of URI indicates what protocols might be usable for accessing it, but this document does not define any of the types. For example, a URI type of

URI 类型表示访问 URI 时可能使用的协议，但本文档没有定义任何类型。例如，URI 类型为

   o  "sip" [5] indicates to use SIP/SIMPLE,
   o  "xmpp" [6] indicates to use XMPP,
   o  "irc" indicates to use IRC,
   o  "ymsgr" indicates to use yahoo,
   o  "msn" might indicate to use Microsoft messenger,
   o  "aim" indicates to use AOL, and
   o  "im" [7] or "pres" [8] indicates that a CPIM or CPP gateway should
      be used.

The normative definition of this new vCard type is given in Section 2, and an informational ABNF is provided in Section 3.

第 2 节给出了这种新 vCard 类型的规范定义，第 3 节提供了信息 ABNF。

2. IANA Considerations

2. IANA考虑因素

The required email to define this extension (as defined in RFC 2425 [1]) was sent on October 29, 2004, to the [email protected] mailing list with the subject "Registration of text/directory MIME type IMPP" (see <http://www.imc.org/ietf-mime-direct/mail-archive/msg00068.html>).

定义该扩展名所需的电子邮件（如 RFC 2425 [1] 所定义）已于 2004 年 10 月 29 日发送至 [email protected] 邮件列表，主题为 "注册文本/目录 MIME 类型 IMPP"（见 <http://www.imc.org/ietf-mime-direct/mail-archive/msg00068.html>）。

This specification updates the "text/directory MIME Types" subregistry in the "text/directory MIME Registrations" registry at http://www.iana.org/assignments/text-directory-registrations with the following information:

本规范用以下信息更新了 http://www.iana.org/assignments/text-directory-registrations 的 "text/directory MIME Registrations "注册表中的 "text/directory MIME Types "子注册表：

Type name: IMPP

类型名称： IMPP

Type purpose: To specify the URI for instant messaging and presence protocol communications with the object the vCard represents.

类型用途：指定用于与 vCard 所代表的对象进行即时消息和出席协议通信的 URI。

Type encoding: 8bit

类型编码：8 位

Type value: A single URI. The type of the URI indicates the protocol that can be used for this contact.

类型值：单个 URI。URI 类型表示该联系人可使用的协议。

Type special notes: The type may include the type parameter "TYPE" to specify an intended use for the URI. The TYPE parameter values include one or more of the following:

类型特别说明：类型可包括类型参数 "TYPE"，以指定 URI 的预期用途。TYPE 参数值包括以下一个或多个参数：

o An indication of the type of communication for which this URI is appropriate. This can be a value of PERSONAL or BUSINESS.

o 表示该 URI 适用的通信类型。可以是 "个人 "或 "企业"。

o An indication of the location of a device associated with this URI. Values can be HOME, WORK, or MOBILE.

o 与此 URI 关联的设备的位置指示。值可以是 "家庭"、"工作 "或 "移动"。

o The value PREF indicates this is a preferred address and has the same semantics as the PREF value in a TEL type.

o PREF 值表示这是首选地址，其语义与 TEL 类型中的 PREF 值相同。

Additional information can be found in RFC 4770.

更多信息请参见 RFC 4770。

Intended usage: COMMON

预期用途：通用

3. Formal Grammar

3. 正式语法

The following ABNF grammar [4] extends the grammar found in RFC 2425 [1] (Section 5.8.2) and RFC 2426 [2] (Section 4).

以下 ABNF 语法 [4] 扩展了 RFC 2425 [1]（第 5.8.2 节）和 RFC 2426 [2]（第 4 节）中的语法。

   ;For name="IMPP"
    param      = impp-param ; Only impp parameters are allowed

value = URI ; URI defined in Section 3 of [3]

value = URI；[3] 第 3 节中定义的 URI

    impp-param = "TYPE" "=" impp-type *("," impp-type)

    impp-type  = "PERSONAL" / "BUSINESS" / ; purpose of communications
                 "HOME" / "WORK" / "MOBILE" /
                 "PREF" /
                 iana-token / x-name;
                 ; Values are case insensitive

4. Example

4. 示例

   BEGIN:vCard
   VERSION:3.0
   FN:Alice Doe
   IMPP;TYPE=personal,pref:im:[email protected]
   END:vCard

5. Security Considerations

5. 安全考虑因素

This does not introduce additional security issues beyond the current vCard specification. It is worth noting that many people consider their presence information more sensitive than other address information. Any system that stores or transfers vCards needs to carefully consider the privacy issues around this information.

除了当前的 vCard 规范外，这不会带来额外的安全问题。值得注意的是，许多人认为自己的存在信息比其他地址信息更敏感。任何存储或传输 vCard 的系统都需要仔细考虑与这些信息有关的隐私问题。

6. Acknowledgments

6. 致谢

Thanks to Brian Carpenter, Lars Eggert, Ted Hardie, Paul Hoffman, Sam Roberts, and Pekka Pessi for their comments.

感谢 Brian Carpenter、Lars Eggert、Ted Hardie、Paul Hoffman、Sam Roberts 和 Pekka Pessi 的意见。

7. References

7. 参考文献

7.1. Normative References

7.1. 规范性文献

[1] Howes, T., Smith, M., and F. Dawson, "A MIME Content-Type for Directory Information", RFC 2425, September 1998.

[2] Dawson, F. and T. Howes, "vCard MIME Directory Profile", RFC 2426, September 1998.

[3] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.

[4] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234, October 2005.

[4] Crocker, D., Ed. 和 P. Overell, "Augmented BNF for Syntax Specifications：ABNF"，RFC 4234，2005 年 10 月。

7.2. Informational References

7.2. 信息参考

[5] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002.

[6] Saint-Andre, P., "Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)", RFC 4622, July 2006.

[7] Peterson, J., "Common Profile for Instant Messaging (CPIM)", RFC 3860, August 2004.

[8] Peterson, J., "Common Profile for Presence (CPP)", RFC 3859, August 2004.

[8] Peterson, J., "Common Profile for Presence (CPP)"，RFC 3859，2004 年 8 月。

Authors' Addresses

作者地址

Cullen Jennings Cisco Systems 170 West Tasman Drive MS: SJC-21/2 San Jose, CA 95134 USA

Cullen Jennings 思科系统公司 170 West Tasman Drive MS: SJC-21/2 San Jose, CA 95134 USA

   Phone: +1 408 902-3341
   EMail: [email protected]

Julian F. Reschke (editor) greenbytes GmbH Hafenweg 16 Muenster, NW 48155 Germany

Julian F. Reschke（编辑） greenbytes GmbH Hafenweg 16 Muenster, NW 48155 德国

   Phone: +49 251 2807760
   EMail: [email protected]

Full Copyright Statement

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, THE IETF TRUST, 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.

本文档及其包含的信息按 "原样 "提供，撰稿人、其所代表或赞助的组织（如有）、互联网协会、IETF TRUST 和互联网工程工作组不作任何保证、明示或默示保证，包括但不限于使用本网站信息不侵犯任何权利的保证或适销性或特定用途适用性的默示保证。

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 procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

IETF 不对任何知识产权或其他权利的有效性或范围，或可能声称与本文档所述技术的实施或使用有关的权利，或在多大程度上可以或不可以获得此类权利下的任何许可采取任何立场；IETF 也不表示它已作出任何独立努力来确定任何此类权利。有关 RFC 文件中权利的程序信息，请参见 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 秘书处披露的知识产权副本、将提供的任何许可保证，或为本规范的实施者或用户使用此类专有权而试图获得一般许可或授权的结果，均可从 http://www.ietf.org/ipr 的 IETF 在线知识产权库中获取。

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 [email protected].

IETF 邀请任何有关方面提请其注意可能涉及实施本标准所需技术的任何版权、专利或专利申请，或其他专有权利。请将信息发送至 IETF：[email protected]。

Acknowledgement

致谢

Funding for the RFC Editor function is currently provided by the Internet Society.

RFC 编辑职能的经费目前由互联网协会提供。