Network Working Group H. Schulzrinne
Request for Comments: 4482 Columbia U.
Category: Standards Track July 2006
Network Working Group H. Schulzrinne
Request for Comments: 4482 Columbia U.
Category: Standards Track July 2006
CIPID: Contact Information for the Presence Information Data Format
CIPID：状态信息数据格式的联系信息
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 (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
The Presence Information Data Format (PIDF) defines a basic XML format for presenting presence information for a presentity. The Contact Information for the Presence Information Data format (CIPID) is an extension that adds elements to PIDF that provide additional contact information about a presentity and its contacts, including references to address book entries and icons.
存在信息数据格式（PIDF）定义了一种基本的XML格式，用于表示存在实体的存在信息。状态信息数据格式（CIPID）的联系人信息是一个扩展，它向PIDF中添加元素，这些元素提供关于状态实体及其联系人的附加联系人信息，包括对通讯簿条目和图标的引用。
Table of Contents
目录
1. Introduction ....................................................2
2. Terminology and Conventions .....................................3
3. CIPID Elements ..................................................3
3.1. Card Element ...............................................3
3.2. Display-Name Element .......................................3
3.3. Homepage Element ...........................................3
3.4. Icon Element ...............................................4
3.5. Map Element ................................................4
3.6. Sound Element ..............................................4
4. Example .........................................................4
5. The XML Schema Definition .......................................6
6. IANA Considerations .............................................7
6.1. URN Sub-Namespace Registration for .........................7
'urn:ietf:params:xml:ns:pidf:cipid'
6.2. Schema Registration for Schema
'urn:ietf:params:xml:ns:pidf:cipid' ........................7
7. Internationalization Considerations .............................8
8. Security Considerations .........................................8
9. References ......................................................9
9.1. Normative References .......................................9
9.2. Informative References ....................................10
1. Introduction ....................................................2
2. Terminology and Conventions .....................................3
3. CIPID Elements ..................................................3
3.1. Card Element ...............................................3
3.2. Display-Name Element .......................................3
3.3. Homepage Element ...........................................3
3.4. Icon Element ...............................................4
3.5. Map Element ................................................4
3.6. Sound Element ..............................................4
4. Example .........................................................4
5. The XML Schema Definition .......................................6
6. IANA Considerations .............................................7
6.1. URN Sub-Namespace Registration for .........................7
'urn:ietf:params:xml:ns:pidf:cipid'
6.2. Schema Registration for Schema
'urn:ietf:params:xml:ns:pidf:cipid' ........................7
7. Internationalization Considerations .............................8
8. Security Considerations .........................................8
9. References ......................................................9
9.1. Normative References .......................................9
9.2. Informative References ....................................10
Presence information facilitates communication; its usefulness can be enhanced by providing basic information about a presentity or contact. This specification describes a basic set of information elements that allow a watcher to retrieve additional information about a presentity or contact.
在场信息有助于交流；它的有用性可以通过提供有关实体或联系人的基本信息来增强。本规范描述了一组基本信息元素，允许观察者检索有关实体或联系人的附加信息。
This specification defines extensions to the PIDF [9] Extensible Markup Language [7][8][10] (XML) document format.
本规范定义了对PIDF[9]可扩展标记语言[7][8][10]（XML）文档格式的扩展。
We describe elements for providing a "business card", references to the homepage, map, representative sound, display name, and an icon. This additional presence information can be used in PIDF [9] documents, together with Rich Presence Information Data format [11] (RPID), future-status [12], and other PIDF extensions.
我们描述了提供“名片”的元素、对主页的引用、地图、代表性声音、显示名称和图标。此附加的状态信息可与丰富的状态信息数据格式[11]（RPID）、未来状态[12]和其他PIDF扩展一起用于PIDF[9]文档中。
All elements extend the <person> or, less commonly, <tuple> element in the presence data model [13]. The <tuple> element is only extended with Contact Information for the Presence Information Data format (CIPID) elements if the information describes a service referring to another person that is marked by an RPID <relationship> element with a value other than 'self'. All elements described in this document are optional.
所有元素都扩展了状态数据模型中的<person>或<tuple>元素[13]。<tuple>元素仅在信息描述了引用另一个人的服务时，才使用状态信息数据格式（CIPID）元素的联系人信息进行扩展，该服务由RPID<relationship>元素标记，其值不是“self”。本文档中描述的所有元素都是可选的。
RPID and CIPID both provide "rich" presence that goes beyond the basic 'open' and 'closed' status information in PIDF. The presence information described in these two documents can be supplied independently, although in practice, both will often appear in the same PIDF document. CIPID elements describe the more static aspects of somebody's presence information, while RPID focuses on elements that will likely change throughout the day. Thus, CIPID information can often be statically configured by the user through the graphical user interface of a presence client; this is less likely to be sufficient for RPID.
RPID和CIPID都提供了“丰富”的状态信息，超出了PIDF中的基本“打开”和“关闭”状态信息。这两个文档中描述的状态信息可以独立提供，尽管在实践中，这两个信息通常出现在同一个PIDF文档中。CIPID元素描述某人的状态信息的更静态的方面，而RPID则关注可能在一天中改变的元素。因此，用户通常可以通过存在客户端的图形用户界面静态地配置CIPID信息；这对于RPID来说不太可能足够。
The namespace URI for these elements defined by this specification is a URN [2], using the namespace identifier 'ietf' defined by [4] and extended by [6]:
本规范定义的这些元素的命名空间URI是一个URN[2]，使用由[4]定义并由[6]扩展的命名空间标识符“ietf”：
urn:ietf:params:xml:ns:pidf:cipid
urn:ietf:params:xml:ns:pidf:cipid
The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in BCP 14, RFC 2119 [1].
本文件中的关键词“必须”、“不得”、“必需”、“应该”、“不应该”、“建议”、“可能”和“可选”应按照BCP 14、RFC 2119[1]中的说明进行解释。
Unless otherwise noted below, each element may only appear at most once.
除非下文另有说明，否则每个元素最多只能出现一次。
The <card> element includes a URI pointing to a business card, e.g., in LDAP Data Interchange Format [15] (LDIF) or vCard [14] format.
<card>元素包括指向名片的URI，例如LDAP数据交换格式[15]（LDIF）或vCard[14]格式。
The <display-name> element includes the name identifying the tuple or person that the presentity suggests should be shown by the watcher user interface. It is left to the watcher user interface design to choose whether to heed this suggestion or to use some other suitable string. The CIPID information MAY contain multiple display names, but only if they are labeled with different 'xml:lang' attributes. This allows a Korean-speaking presentity to convey its display name in different languages, Latin and Hangul, for example.
<display name>元素包括标识元组或人员的名称，该元组或人员是presentity建议由watcher用户界面显示的。观察者的用户界面设计可以选择是采纳这一建议，还是使用其他合适的字符串。CIPID信息可能包含多个显示名称，但前提是这些名称使用不同的“xml:lang”属性进行标记。这使得一个说韩语的实体可以用不同的语言，例如拉丁语和韩语来表达它的展示名称。
The <homepage> element provides a URI pointing to general information about the tuple or person, typically a web home page.
元素提供一个URI，指向元组或个人的一般信息，通常是web主页。
The <icon> element provides a URI pointing to an image (icon) representing the tuple or person. The watcher can use this information to represent the tuple or person in a graphical user interface. Presentities SHOULD provide images of sizes and aspect ratios that are appropriate for rendering as an icon. Support for JPEG, PNG, and GIF formats is REQUIRED.
元素提供一个URI，指向表示元组或人物的图像（图标）。观察者可以使用此信息在图形用户界面中表示元组或人物。存在实体应提供大小和纵横比适合作为图标渲染的图像。需要支持JPEG、PNG和GIF格式。
The <map> element provides a URI pointing to a map related to the tuple or person. The watcher can use this information to represent the tuple or person in a graphical user interface. The map may be either an image, an HTML client-side image map, or a geographical information system (GIS) document, e.g., encoded as GML. Support for images formatted as PNG and GIF is REQUIRED.
元素提供一个URI，指向与元组或人物相关的映射。观察者可以使用此信息在图形用户界面中表示元组或人物。地图可以是图像、HTML客户端图像地图或地理信息系统（GIS）文档，例如，编码为GML。需要支持格式为PNG和GIF的图像。
The <sound> element provides a URI pointing to a sound related to the tuple or person. The watcher MAY use the sound object, such as a MIDI or MP3 file, referenced by the URL to inform the watcher that the presentity has assumed the status OPEN. Implementors are advised to create user interfaces that provide the watcher with the opportunity to choose whether to play such sounds. Support for sounds coded as MPEG-2 Layer 3 (MP3) is RECOMMENDED. The sound object might also be used to indicate how to pronounce the presentity's name.
元素提供一个URI，指向与元组或人物相关的声音。观察者可以使用URL引用的声音对象（例如MIDI或MP3文件）来通知观察者存在实体已假定为打开状态。建议实现者创建用户界面，为观察者提供选择是否播放此类声音的机会。建议支持编码为MPEG-2第3层（MP3）的声音。声音对象也可以用来表示存在实体名称的发音。
An example using CIPID only is shown below:
仅使用CIPID的示例如下所示：
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:c="urn:ietf:params:xml:ns:pidf:cipid"
entity="pres:someone@example.com">
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:c="urn:ietf:params:xml:ns:pidf:cipid"
entity="pres:someone@example.com">
<tuple id="bs35r9">
<status>
<basic>open</basic>
</status>
<contact priority="0.8">im:alice@example.net</contact>
<timestamp>2005-11-21T16:14:29Z</timestamp>
</tuple>
<tuple id="bs35r9">
<status>
<basic>open</basic>
</status>
<contact priority="0.8">im:alice@example.net</contact>
<timestamp>2005-11-21T16:14:29Z</timestamp>
</tuple>
<dm:person id="p1">
<c:card>http://example.com/~alice/card.vcd</c:card>
<c:display-name>Alice Lewis</c:card>
<c:homepage>http://example.com/~alice</c:homepage>
<c:icon>http://example.com/~alice/me.png</c:icon>
<c:map>http://example.com/~alice/gml-map.xml</c:map>
<c:sound>http://example.com/~alice/hello.wav</c:sound>
<dm:timestamp>2005-11-21T09:00:00+05:00</dm:timestamp>
</dm:person>
</presence>
<dm:person id="p1">
<c:card>http://example.com/~alice/card.vcd</c:card>
<c:display-name>Alice Lewis</c:card>
<c:homepage>http://example.com/~alice</c:homepage>
<c:icon>http://example.com/~alice/me.png</c:icon>
<c:map>http://example.com/~alice/gml-map.xml</c:map>
<c:sound>http://example.com/~alice/hello.wav</c:sound>
<dm:timestamp>2005-11-21T09:00:00+05:00</dm:timestamp>
</dm:person>
</presence>
An example combining RPID and CIPID is shown below:
结合RPID和CIPID的示例如下所示：
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:c="urn:ietf:params:xml:ns:pidf:cipid"
xmlns:r="urn:ietf:params:xml:ns:pidf:rpid"
xsi:schemaLocation="urn:ietf:params:xml:ns:pidf pidf.xsd
urn:ietf:params:xml:ns:pidf:data-model data-model.xsd
urn:ietf:params:xml:ns:pidf:cipid cipid.xsd
urn:ietf:params:xml:ns:pidf:rpid rpid.xsd"
entity="pres:someone@example.com">
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:c="urn:ietf:params:xml:ns:pidf:cipid"
xmlns:r="urn:ietf:params:xml:ns:pidf:rpid"
xsi:schemaLocation="urn:ietf:params:xml:ns:pidf pidf.xsd
urn:ietf:params:xml:ns:pidf:data-model data-model.xsd
urn:ietf:params:xml:ns:pidf:cipid cipid.xsd
urn:ietf:params:xml:ns:pidf:rpid rpid.xsd"
entity="pres:someone@example.com">
<tuple id="bs35r9">
<status>
<basic>open</basic>
</status>
<contact priority="0.8">im:someone@mobile.example.net</contact>
<timestamp>2005-05-30T22:00:29Z</timestamp>
</tuple>
<tuple id="bs35r9">
<status>
<basic>open</basic>
</status>
<contact priority="0.8">im:someone@mobile.example.net</contact>
<timestamp>2005-05-30T22:00:29Z</timestamp>
</tuple>
<tuple id="bs78">
<status>
<basic>closed</basic>
</status>
<r:relationship><r:assistant/></r:relationship>
<c:card>http://example.com/~assistant/card.vcd</c:card>
<c:homepage>http://example.com/~assistant</c:homepage>
<contact priority="0.1">im:assistant@example.com</contact>
<timestamp>2005-05-30T22:00:29Z</timestamp>
</tuple>
<tuple id="bs78">
<status>
<basic>closed</basic>
</status>
<r:relationship><r:assistant/></r:relationship>
<c:card>http://example.com/~assistant/card.vcd</c:card>
<c:homepage>http://example.com/~assistant</c:homepage>
<contact priority="0.1">im:assistant@example.com</contact>
<timestamp>2005-05-30T22:00:29Z</timestamp>
</tuple>
<dm:person id="p1">
<c:card>http://example.com/~someone/card.vcd</c:card>
<c:homepage>http://example.com/~someone</c:homepage>
<c:icon>http://example.com/~someone/icon.gif</c:icon>
<dm:person id="p1">
<c:card>http://example.com/~someone/card.vcd</c:card>
<c:homepage>http://example.com/~someone</c:homepage>
<c:icon>http://example.com/~someone/icon.gif</c:icon>
<c:map>http://example.com/~someone/gml-map.xml</c:map>
<c:sound>http://example.com/~someone/whoosh.wav</c:sound>
<dm:timestamp>2005-05-30T22:02:44+05:00</dm:timestamp>
</dm:person>
</presence>
<c:map>http://example.com/~someone/gml-map.xml</c:map>
<c:sound>http://example.com/~someone/whoosh.wav</c:sound>
<dm:timestamp>2005-05-30T22:02:44+05:00</dm:timestamp>
</dm:person>
</presence>
The schema is shown below.
模式如下所示。
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:ietf:params:xml:ns:pidf:cipid"
xmlns:cipid="urn:ietf:params:xml:ns:pidf:cipid"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:ietf:params:xml:ns:pidf:cipid"
xmlns:cipid="urn:ietf:params:xml:ns:pidf:cipid"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:annotation>
<xs:documentation>
Describes CIPID tuple extensions for PIDF.
</xs:documentation>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Describes CIPID tuple extensions for PIDF.
</xs:documentation>
</xs:annotation>
<xs:element name="card" type="xs:anyURI"/>
<xs:element name="display-name" type="xs:string"/>
<xs:element name="homepage" type="xs:anyURI"/>
<xs:element name="icon" type="xs:anyURI"/>
<xs:element name="map" type="xs:anyURI"/>
<xs:element name="sound" type="xs:anyURI"/>
</xs:schema>
<xs:element name="card" type="xs:anyURI"/>
<xs:element name="display-name" type="xs:string"/>
<xs:element name="homepage" type="xs:anyURI"/>
<xs:element name="icon" type="xs:anyURI"/>
<xs:element name="map" type="xs:anyURI"/>
<xs:element name="sound" type="xs:anyURI"/>
</xs:schema>
Figure 1: CIPID schema
图1:CIPID模式
This document calls for IANA to register a new XML namespace URN and schema per [6].
本文档要求IANA根据[6]注册一个新的XML名称空间URN和模式。
6.1. URN Sub-Namespace Registration for
'urn:ietf:params:xml:ns:pidf:cipid'
6.1. URN Sub-Namespace Registration for
'urn:ietf:params:xml:ns:pidf:cipid'
URI: urn:ietf:params:xml:ns:pidf:cipid Description: This is the XML namespace for XML elements defined by RFC 4482 to describe contact information presence information extensions for the status element in the PIDF presence document format in the application/pidf+xml content type. Registrant Contact: IETF, SIMPLE working group, simple@ietf.org; Henning Schulzrinne, hgs@cs.columbia.edu XML:
URI:urn:ietf:params:xml:ns:pidf:cipid Description：这是RFC 4482定义的xml元素的xml名称空间，用于描述application/pidf+xml内容类型中pidf状态文档格式中状态元素的联系人信息状态信息扩展。注册人联系人：IETF，简单工作组，simple@ietf.org; 亨宁·舒尔兹林内，hgs@cs.columbia.eduXML:
BEGIN
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml
<head>
<meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/>
<title>CIPID: Contact Information for the Presence Information
Data Format</title>
</head>
<body>
<h1>Namespace for contact information presence extension
(status)</h1>
<h2>urn:ietf:params:xml:ns:pidf:cipid</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfc4482.txt">
RFC4482</a>.</p>
</body>
</html>
END
BEGIN
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml
<head>
<meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/>
<title>CIPID: Contact Information for the Presence Information
Data Format</title>
</head>
<body>
<h1>Namespace for contact information presence extension
(status)</h1>
<h2>urn:ietf:params:xml:ns:pidf:cipid</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfc4482.txt">
RFC4482</a>.</p>
</body>
</html>
END
URI: urn:ietf:params:xml:ns:pidf:cipid
Registrant Contact: IESG
XML: See Figure 1
URI: urn:ietf:params:xml:ns:pidf:cipid
Registrant Contact: IESG
XML: See Figure 1
CIPID delivers only URLs, except for the <display-name> element. The resolution of the URLs can negotiate appropriate language and character sets within the URL-designated protocol.
CIPID只提供url，除了<display name>元素。URL的解析可以在URL指定的协议中协商适当的语言和字符集。
For the display name and to handle Internationalized Resource Identifiers (IRIs) [16], since CIPID is represented in XML, it provides native support for encoding information using the Unicode character set and its more compact representations including UTF-8. Conformant XML processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is RECOMMENDED in environments where parser encoding support incompatibility exists.
对于显示名称和处理国际化资源标识符（IRIs）[16]，因为CIPID是用XML表示的，所以它为使用Unicode字符集及其更紧凑的表示（包括UTF-8）编码信息提供了本机支持。UTF-8和UTF-16兼容处理器。尽管XML包含通过在<？XML？>声明中使用“encoding”属性来识别和使用其他字符编码的规定，但在解析器编码支持不兼容的环境中，建议使用UTF-8。
The XML 'xml:lang' attribute can be used to identify the language and script for the <display-name> element. The specification allows multiple occurrences of this element so that the presentity can convey display names in multiple scripts and languages. If no 'xml: lang' attribute is provided, the default value is "i-default" [3].
XML'XML:lang'属性可用于标识<display name>元素的语言和脚本。该规范允许该元素多次出现，因此呈现实体可以用多种脚本和语言传递显示名称。如果未提供“xml:lang”属性，则默认值为“i-default”[3]。
The security issues are similar to those for RPID [11]. Watchers need to restrict which content types of content pointed to by <icon>, <homepage>, <map>, <sound>, and <vcard> elements they render.
安全问题与RPID的问题类似[11]。观察者需要限制他们呈现的<icon>、<homepage>、<map>、<sound>和<vcard>元素所指向的内容类型。
Also, when a watcher accesses these URIs, the presentity may deduce that the watcher is currently using the presence application. Thus, a presence application concerned about leaking this information may want to cache these objects for later use. (A presentity could easily customize the URLs for each watcher, so that it can tell who is referencing the objects.) This caching behavior may cause the information to become stale, out-of-sync with the current data until the cache is refreshed. Fortunately, the elements in CIPID are expected to retain the same content for periods measured in days, so that privacy-conscious applications may well decide to perform caching over durations that reveal little current activity information. Presentities need to keep in mind that clients may cache the content referenced by URIs for long periods as they use their presence system to construct presence documents using this extension. If the referenced content needs to change frequently, the presentity could, for example, update the presence document with a new URI to encourage clients to notice.
此外，当观察者访问这些URI时，存在实体可以推断观察者当前正在使用存在应用程序。因此，担心泄漏此信息的状态应用程序可能希望缓存这些对象以供以后使用。（存在实体可以轻松自定义每个观察者的URL，这样它就可以知道谁在引用对象。）这种缓存行为可能会导致信息过时，与当前数据不同步，直到刷新缓存为止。幸运的是，CIPID中的元素预计会在以天为单位的时间段内保留相同的内容，因此关注隐私的应用程序很可能决定在显示很少当前活动信息的时间段内执行缓存。呈现实体需要记住，当客户端使用其呈现系统使用此扩展构建呈现文档时，它们可能会长期缓存URI引用的内容。如果引用的内容需要频繁更改，则呈现实体可以（例如）使用新的URI更新呈现文档以鼓励客户端注意。
Icons and other URIs in this document could be used as a covert channel to convey messages to the watcher, outside the content monitoring that might be in place for instant messages or other communications channels. Thus, entities that worry about such channels may want to prohibit the usage of URLs pointing to resources outside their domain, for example.
本文档中的图标和其他URI可以用作隐蔽通道，在即时消息或其他通信通道的内容监控之外，将消息传递给观察者。因此，担心此类通道的实体可能希望禁止使用指向其域外资源的URL。
Implementors must take care to adhere to the mechanisms for verifying the identity in the referenced server's certificate against the URI. For instance, if the URI scheme is https, the requirements of RFC 2818 [5], section 3.1, must be met. In particular, the domain represented in the URI must match the subjectAltName in the certificate presented by the referenced server. If this identity check fails, the referenced content SHOULD NOT be retrieved and MUST NOT be used.
实现者必须注意遵守用于根据URI验证所引用服务器证书中的标识的机制。例如，如果URI方案是https，则必须满足RFC 2818[5]第3.1节的要求。特别是，URI中表示的域必须与引用服务器提供的证书中的subjectAltName匹配。如果此身份检查失败，则不应检索引用的内容，也不得使用该内容。
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[1] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[2] Moats, R., "URN Syntax", RFC 2141, May 1997.
[2] 护城河，R.，“瓮语法”，RFC 21411997年5月。
[3] Alvestrand, H., "IETF Policy on Character Sets and Languages", BCP 18, RFC 2277, January 1998.
[3] Alvestrand，H.，“IETF字符集和语言政策”，BCP 18，RFC 2277，1998年1月。
[4] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, August 1999.
[4] Moats，R.，“IETF文档的URN名称空间”，RFC 2648，1999年8月。
[5] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
[5] Rescorla，E.，“TLS上的HTTP”，RFC 2818，2000年5月。
[6] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[6] Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[7] Maloney, M., Beech, D., Thompson, H., and N. Mendelsohn, "XML Schema Part 1: Structures Second Edition", W3C REC REC-xmlschema-1-20041028, October 2004.
[7] Maloney，M.，Beech，D.，Thompson，H.，和N.Mendelsohn，“XML模式第1部分：结构第二版”，W3C REC-xmlschema-1-20041028，2004年10月。
[8] Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes Second Edition", W3C REC REC-xmlschema-2-20041028, October 2004.
[8] Malhotra，A.和P.Biron，“XML模式第2部分：数据类型第二版”，W3C REC REC-xmlschema-2-20041028，2004年10月。
[9] Sugano, H., Fujimoto, S., Klyne, G., Bateman, A., Carr, W., and J. Peterson, "Presence Information Data Format (PIDF)", RFC 3863, August 2004.
[9] Sugano，H.，Fujimoto，S.，Klyne，G.，Batman，A.，Carr，W.，和J.Peterson，“状态信息数据格式（PIDF）”，RFC 38632004年8月。
[10] Yergeau, F., Paoli, J., Sperberg-McQueen, C., Bray, T., and E. Maler, "Extensible Markup Language (XML) 1.0 (Third Edition)", W3C REC REC-xml-20040204, February 2004.
[10] Yergeau，F.，Paoli，J.，Sperberg McQueen，C.，Bray，T.，和E.Maler，“可扩展标记语言（XML）1.0（第三版）”，W3C REC REC-XML-200402042004年2月。
[11] Schulzrinne, H., Gurbani, V., Kyzivat, P., and J. Rosenberg, "RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)", RFC 4480, July 2006.
[11] Schulzrinne，H.，Gurbani，V.，Kyzivat，P.，和J.Rosenberg，“RPID：状态信息数据格式（PIDF）的丰富状态扩展”，RFC 44802006年7月。
[12] Schulzrinne, H., "Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals", RFC 4481, July 2006.
[12] Schulzrinne，H.，“状态信息数据格式（PIDF）的定时状态扩展，用于指示过去和未来时间间隔的状态信息”，RFC 4481，2006年7月。
[13] Rosenberg, J., "A Data Model for Presence", RFC 4479, July 2006.
[13] Rosenberg，J.，“存在的数据模型”，RFC 4479，2006年7月。
[14] Dawson, F. and T. Howes, "vCard MIME Directory Profile", RFC 2426, September 1998.
[14] Dawson，F.和T.Howes，“vCard MIME目录配置文件”，RFC24261998年9月。
[15] Good, G., "The LDAP Data Interchange Format (LDIF) - Technical Specification", RFC 2849, June 2000.
[15] Good，G.，“LDAP数据交换格式（LDIF）-技术规范”，RFC 28492000年6月。
[16] Duerst, M. and M. Suignard, "Internationalized Resource Identifiers (IRIs)", RFC 3987, January 2005.
[16] Duerst，M.和M.Suignard，“国际化资源标识符（IRIs）”，RFC 3987，2005年1月。
Acknowledgements
致谢
This document is based on discussions within the IETF SIMPLE working group. Spencer Dawkins, Vijay Gurbani, Avshalom Houri, Hisham Khartabil, Paul Kyzivat, Eva Leppanen, Mikko Lonnfors, Aki Niemi, Jon Peterson, Jonathan Rosenberg, and Robert Sparks provided helpful comments.
本文件基于IETF简单工作组内的讨论。斯宾塞·道金斯、维杰·古巴尼、阿夫沙洛姆·胡里、希沙姆·哈塔比尔、保罗·基齐瓦特、伊娃·莱普潘宁、米科·隆福斯、阿基·尼米、乔恩·彼得森、乔纳森·罗森博格和罗伯特·斯帕克斯提供了有益的评论。
Author's Address
作者地址
Henning Schulzrinne Columbia University Department of Computer Science 450 Computer Science Building New York, NY 10027 US
美国纽约州纽约市哥伦比亚大学计算机科学系计算机科学大楼450号
Phone: +1 212 939 7004
EMail: hgs+simple@cs.columbia.edu
URI: http://www.cs.columbia.edu
Phone: +1 212 939 7004
EMail: hgs+simple@cs.columbia.edu
URI: http://www.cs.columbia.edu
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
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 procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
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秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从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 provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。