Network Working Group H. Schulzrinne
Request for Comments: 4481 Columbia U.
Category: Standards Track July 2006
Network Working Group H. Schulzrinne
Request for Comments: 4481 Columbia U.
Category: Standards Track July 2006
Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals
状态信息数据格式（PIDF）的定时状态扩展，用于指示过去和未来时间间隔的状态信息
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. This document extends PIDF, adding a timed status extension (<timed-status> element) that allows a presentity to declare its status for a time interval fully in the future or the past.
存在信息数据格式（PIDF）定义了一种基本的XML格式，用于表示存在实体的存在信息。本文档扩展了PIDF，添加了一个timed status扩展（<timed status>元素），允许实体在未来或过去的某个时间间隔内完全声明其状态。
Table of Contents
目录
1. Introduction ....................................................2
2. Terminology and Conventions .....................................2
3. Timed-Status Element ............................................3
4. Example .........................................................4
5. The XML Schema Definition .......................................5
6. IANA Considerations .............................................6
6.1. URN Sub-Namespace Registration for
'urn:ietf:params:xml:ns:pidf:timed-status' .................6
6.2. Schema Registration for Schema
'urn:ietf:params:xml:ns:pidf:timed-status' .................7
7. Security Considerations .........................................7
8. References ......................................................7
8.1. Normative References .......................................7
8.2. Informative References .....................................7
Contributor's Address ..............................................8
Acknowledgements ...................................................8
1. Introduction ....................................................2
2. Terminology and Conventions .....................................2
3. Timed-Status Element ............................................3
4. Example .........................................................4
5. The XML Schema Definition .......................................5
6. IANA Considerations .............................................6
6.1. URN Sub-Namespace Registration for
'urn:ietf:params:xml:ns:pidf:timed-status' .................6
6.2. Schema Registration for Schema
'urn:ietf:params:xml:ns:pidf:timed-status' .................7
7. Security Considerations .........................................7
8. References ......................................................7
8.1. Normative References .......................................7
8.2. Informative References .....................................7
Contributor's Address ..............................................8
Acknowledgements ...................................................8
Traditionally, presence information, e.g., represented as Presence Information Data Format [3] (PIDF) and augmented by Rich Presence Information Data format [9] (RPID), describes the current state of the presentity. However, a watcher can better plan communications if it knows about the presentity's future plans. For example, if a watcher knows that the presentity is about to travel, it might place a phone call earlier.
传统上，存在信息（例如，表示为存在信息数据格式[3]（PIDF）并由丰富的存在信息数据格式[9]（RPID）扩充）描述存在实体的当前状态。然而，如果观察者知道当前实体的未来计划，则可以更好地规划通信。例如，如果观察者知道该实体即将旅行，它可能会提前打电话。
In this document, we use terms defined in RFC 2778 [7]. In particular, a "presentity", abbreviating presence entity, provides presence information to a presence service. It is typically a uniquely-identified person.
在本文件中，我们使用RFC 2778[7]中定义的术语。具体而言，“存在实体”（缩写为存在实体）向存在服务提供存在信息。它通常是唯一标识的人。
RPID already allows a presentity to indicate the period when a particular aspect of its presence is valid. However, the <status> element in the PIDF <tuple> does not have this facility, so that it is not possible to indicate that a presentity will be OPEN or CLOSED in the future, for example.
RPID已经允许存在实体指示其存在的特定方面有效的时间段。但是，PIDF<tuple>中的<status>元素没有此功能，因此，例如，无法指示存在实体将在将来打开或关闭。
It is also occasionally useful to represent past information since it may be the only known presence information; it may give watchers an indication of the current status. For example, indicating that the presentity was at an off-site meeting that ended an hour ago indicates that the presentity is likely in transit at the current time.
表示过去的信息有时也很有用，因为它可能是唯一已知的存在信息；它可以向观察者提供当前状态的指示。例如，表明该实体在一小时前结束的非现场会议上，表明该实体可能在当前时间正在运输中。
It is unfortunately not possible to simply add time range attributes to the PIDF <status> element, as PIDF parsers without this capability would ignore these attributes and thus not be able to distinguish current from future presence status information.
不幸的是，无法简单地将时间范围属性添加到PIDF<status>元素，因为没有此功能的PIDF解析器将忽略这些属性，因此无法区分当前和未来的状态信息。
This document defines the <timed-status> element that describes the status of a presentity that is either no longer valid or covers some future time period.
本文档定义了<timed status>元素，用于描述不再有效或涵盖未来某个时间段的实体的状态。
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]中的说明进行解释。
The <timed-status> element is a child of the <tuple> element and MUST NOT appear as a child of a PIDF <status> element or another <timed-status> element. More than one such element MAY appear within a PIDF <tuple> element.
<timed status>元素是<tuple>元素的子元素，不能作为PIDF<status>元素或另一个<timed status>元素的子元素出现。PIDF<tuple>元素中可能会出现多个这样的元素。
Sources of <timed-status> information should avoid elements that overlap in time, but since overlapping appointments are common in calendars, for example, receivers MUST be able to render such overlapping <timed-status> indications.
<timed status>信息的来源应避免时间重叠的元素，但由于重叠约会在日历中很常见，例如，接收者必须能够呈现此类重叠的<timed status>指示。
The <timed-status> element MUST be qualified with the 'from' attribute and MAY be qualified with an 'until' attribute to describe the time when the status assumed this value and the time until which this element is expected to be valid. If the 'until' attribute is missing, the information is assumed valid until the tuple is explicitly overridden or expires as defined by the publication mechanism used. The time range MUST NOT encompass the present time, i.e., the PIDF <timestamp> value, as that would provide an unnecessary and confusing alternate mechanism to describe presence. Thus, the 'from' attribute for tuples without an 'until' attribute MUST refer to the future.
<timed status>元素必须使用“from”属性限定，也可以使用“until”属性限定，以描述状态采用该值的时间以及该元素预期有效的时间。如果缺少'until'属性，则假定该信息在元组被显式重写或按照所用发布机制的定义过期之前有效。时间范围不得包含当前时间，即PIDF<timestamp>值，因为这将提供一种不必要且令人困惑的替代机制来描述存在。因此，没有“直到”属性的元组的“from”属性必须指向未来。
During composition, a presence agent (PA) may encounter a stored <timed-status> element that covers the present time. The PA MAY either discard that element or MAY convert it to a regular <status> element if it considers that information more credible.
在合成期间，存在代理（PA）可能遇到覆盖当前时间的存储的<timed status>元素。如果PA认为该信息更可信，则可以放弃该元素或将其转换为常规<status>元素。
The <timed-status> element may contain the <basic> and <note> elements, as well as any other element that is appropriate as a PIDF <status> extension and that has a limited validity period. Examples include the PIDF-LO [8] extensions for location objects.
<timed status>元素可以包含<basic>和<note>元素，以及任何其他适合作为PIDF<status>扩展且有效期有限的元素。示例包括位置对象的PIDF-LO[8]扩展。
This extension chose absolute rather than relative times, since relative times would be too hard to keep properly updated when spacing notifications, for example. Originators of presence information MUST generate time values in the <timed-status> elements that are fully in the past or future relative to local real (wallclock) time and the time information contained in the optional PIDF <timestamp> element.
此扩展选择绝对时间而不是相对时间，因为相对时间在间隔通知时很难保持正确更新。状态信息的发起人必须在<timed status>元素中生成时间值，这些时间值完全在过去或未来相对于本地实时（wallclock）时间和可选PIDF<timestamp>元素中包含的时间信息。
An example combining PIDF and timed-status is shown below:
结合PIDF和定时状态的示例如下所示：
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:ts="urn:ietf:params:xml:ns:pidf:timed-status"
entity="pres:someone@example.com">
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:ts="urn:ietf:params:xml:ns:pidf:timed-status"
entity="pres:someone@example.com">
<tuple id="c8dqui">
<status>
<basic>open</basic>
</status>
<ts:timed-status from="2005-08-15T10:20:00.000-05:00"
until="2005-08-22T19:30:00.000-05:00">
<ts:basic>closed</ts:basic>
</ts:timed-status>
<contact>sip:someone@example.com</contact>
</tuple>
<note>I'll be in Tokyo next week</note>
</presence>
<tuple id="c8dqui">
<status>
<basic>open</basic>
</status>
<ts:timed-status from="2005-08-15T10:20:00.000-05:00"
until="2005-08-22T19:30:00.000-05:00">
<ts:basic>closed</ts:basic>
</ts:timed-status>
<contact>sip:someone@example.com</contact>
</tuple>
<note>I'll be in Tokyo next week</note>
</presence>
The XML [4] schema [5][6] is shown below.
XML[4]模式[5][6]如下所示。
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:ts="urn:ietf:params:xml:ns:pidf:timed-status"
xmlns:pidf="urn:ietf:params:xml:ns:pidf"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:pidf:timed-status"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:ts="urn:ietf:params:xml:ns:pidf:timed-status"
xmlns:pidf="urn:ietf:params:xml:ns:pidf"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:pidf:timed-status"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="urn:ietf:params:xml:ns:pidf"/>
<xs:import namespace="urn:ietf:params:xml:ns:pidf"/>
<xs:annotation>
<xs:documentation>
Describes timed-status tuple extensions for PIDF.
</xs:documentation>
</xs:annotation>
<xs:element name="timed-status" type="ts:timed-status"/>
<xs:complexType name="timed-status">
<xs:sequence>
<xs:element name="basic" type="pidf:basic" minOccurs="0"/>
<xs:element name="note" type="pidf:note" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="from" type="xs:dateTime" use="required"/>
<xs:attribute name="until" type="xs:dateTime"/>
</xs:complexType>
</xs:schema>
<xs:annotation>
<xs:documentation>
Describes timed-status tuple extensions for PIDF.
</xs:documentation>
</xs:annotation>
<xs:element name="timed-status" type="ts:timed-status"/>
<xs:complexType name="timed-status">
<xs:sequence>
<xs:element name="basic" type="pidf:basic" minOccurs="0"/>
<xs:element name="note" type="pidf:note" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="from" type="xs:dateTime" use="required"/>
<xs:attribute name="until" type="xs:dateTime"/>
</xs:complexType>
</xs:schema>
This document calls for IANA to register a new XML namespace URN and schema per [2].
本文档要求IANA根据[2]注册一个新的XML名称空间URN和模式。
6.1. URN Sub-Namespace Registration for
'urn:ietf:params:xml:ns:pidf:timed-status'
6.1. URN Sub-Namespace Registration for
'urn:ietf:params:xml:ns:pidf:timed-status'
URI: urn:ietf:params:xml:ns:pidf:timed-status
URI: urn:ietf:params:xml:ns:pidf:timed-status
Description: This is the XML namespace for XML elements defined by RFC 4481 to describe timed-status presence information extensions for the status element in the PIDF presence document format in the application/pidf+xml content type.
描述：这是RFC 4481定义的XML元素的XML命名空间，用于描述应用程序/PIDF+XML内容类型中PIDF状态文档格式的状态元素的定时状态状态信息扩展。
Registrant Contact: IETF, SIMPLE working group, simple@ietf.org;
Henning Schulzrinne, hgs@cs.columbia.edu
Registrant Contact: IETF, SIMPLE working group, simple@ietf.org;
Henning Schulzrinne, hgs@cs.columbia.edu
XML:
XML:
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>Timed Presence Extensions to the Presence
Information Data Format (PIDF) to Indicate Status
Information for Past and Future Time Intervals</title>
</head>
<body>
<h1>Namespace for timed-status presence extension</h1>
<h2>urn:ietf:params:xml:ns:pidf:timed-status</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfc4481.txt">
RFC4481</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>Timed Presence Extensions to the Presence
Information Data Format (PIDF) to Indicate Status
Information for Past and Future Time Intervals</title>
</head>
<body>
<h1>Namespace for timed-status presence extension</h1>
<h2>urn:ietf:params:xml:ns:pidf:timed-status</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfc4481.txt">
RFC4481</a>.</p>
</body>
</html>
END
6.2. Schema Registration for Schema
'urn:ietf:params:xml:ns:pidf:timed-status'
6.2. Schema Registration for Schema
'urn:ietf:params:xml:ns:pidf:timed-status'
URI: urn:ietf:params:xml:ns:pidf:timed-status
URI: urn:ietf:params:xml:ns:pidf:timed-status
Registrant Contact: IESG
注册联系人：IESG
XML: See Section 5
XML：见第5节
The security issues are similar to those for RPID [9].
安全问题与RPID的问题类似[9]。
[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] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[2] Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[3] Sugano, H., Fujimoto, S., Klyne, G., Bateman, A., Carr, W., and J. Peterson, "Presence Information Data Format (PIDF)", RFC 3863, August 2004.
[3] Sugano，H.，Fujimoto，S.，Klyne，G.，Batman，A.，Carr，W.，和J.Peterson，“状态信息数据格式（PIDF）”，RFC 38632004年8月。
[4] 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.
[4] Yergeau，F.，Paoli，J.，Sperberg McQueen，C.，Bray，T.，和E.Maler，“可扩展标记语言（XML）1.0（第三版）”，W3C REC REC-XML-200402042004年2月。
[5] Maloney, M., Beech, D., Thompson, H., and N. Mendelsohn, "XML Schema Part 1: Structures Second Edition", W3C REC REC-xmlschema-1-20041028, October 2004.
[5] Maloney，M.，Beech，D.，Thompson，H.，和N.Mendelsohn，“XML模式第1部分：结构第二版”，W3C REC-xmlschema-1-20041028，2004年10月。
[6] Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes Second Edition", W3C REC REC-xmlschema-2-20041028, October 2004.
[6] Malhotra，A.和P.Biron，“XML模式第2部分：数据类型第二版”，W3C REC REC-xmlschema-2-20041028，2004年10月。
[7] Day, M., Rosenberg, J., and H. Sugano, "A Model for Presence and Instant Messaging", RFC 2778, February 2000.
[7] Day，M.，Rosenberg，J.，和H.Sugano，“状态和即时信息模型”，RFC 27782000年2月。
[8] Peterson, J., "A Presence-based GEOPRIV Location Object Format", RFC 4119, December 2005.
[8] Peterson，J.，“基于状态的GEOPRIV定位对象格式”，RFC 4119，2005年12月。
[9] Schulzrinne, H., Gurbani, V., Kyzivat, P., and J. Rosenberg, "RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)", RFC 4480, July 2006.
[9] Schulzrinne，H.，Gurbani，V.，Kyzivat，P.，和J.Rosenberg，“RPID：状态信息数据格式（PIDF）的丰富状态扩展”，RFC 44802006年7月。
Contributor's Address
投稿人地址
Jonathan Rosenberg dynamicsoft 600 Lanidex Plaza Parsippany, NJ 07054-2711 USA EMail: jdrosen@dynamicsoft.com
Jonathan Rosenberg dynamicsoft 600美国新泽西州帕西帕尼拉尼德斯广场07054-2711电子邮件：jdrosen@dynamicsoft.com
Acknowledgements
致谢
This document is based on the discussions within the IETF SIMPLE working group. Mary Barnes, Avri Doria, Miguel Garcia, Vijay Gurbani, Hisham Khartabil, Paul Kyzivat, Mikko Lonnfors, Yannis Pavlidis and Jon Peterson provided helpful comments.
本文件基于IETF简单工作组内的讨论。Mary Barnes、Avri Doria、Miguel Garcia、Vijay Gurbani、Hisham Khartabil、Paul Kyzivat、Mikko Lonnfors、Yannis Pavlidis和Jon Peterson提供了有益的评论。
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）提供。