Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF)
RFC 5196
|
Document |
Type |
|
RFC - Proposed Standard
(September 2008; No errata)
|
|
Authors |
|
Mikko Lonnfors
,
Krisztian Kiss
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
RFC 5196 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Jon Peterson
|
|
Send notices to |
|
(None)
|
Network Working Group M. Lonnfors
Request for Comments: 5196 K. Kiss
Category: Standards Track Nokia
September 2008
Session Initiation Protocol (SIP) User Agent Capability Extension to
Presence Information Data Format (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.
Abstract
Presence Information Data Format (PIDF) defines a common presence
data format for Common Profile for Presence (CPP) compliant presence
protocols. This memo defines a PIDF extension to represent SIP User
Agent capabilities.
Lonnfors & Kiss Standards Track [Page 1]
RFC 5196 User Agent Capability Presence Status September 2008
Table of Contents
1. Introduction ....................................................3
1.1. Motivation .................................................3
1.2. Scope ......................................................4
2. Conventions .....................................................4
3. Extension for "Indicating User Agent Capabilities in the
Session Initiation Protocol (SIP)" in PIDF Documents ............4
3.1. Overview of Operation ......................................4
3.2. Service capabilities .......................................5
3.2.1. <servcaps> Element ..................................5
3.2.2. <audio> Element .....................................5
3.2.3. <application> Element ...............................5
3.2.4. <data> Element ......................................6
3.2.5. <control> Element ...................................6
3.2.6. <video> Element .....................................6
3.2.7. <text> Element ......................................6
3.2.8. <message> Element ...................................7
3.2.9. <type> Element ......................................7
3.2.10. <automata> Element .................................7
3.2.11. <class> Element ....................................7
3.2.12. <duplex> Element ...................................8
3.2.13. <description> Element ..............................8
3.2.14. <event-packages> Element ...........................9
3.2.15. <priority> Element .................................9
3.2.16. <methods> Element .................................10
3.2.17. <extensions> Element ..............................11
3.2.18. <schemes> Element .................................11
3.2.19. <actor> Element ...................................12
3.2.20. <isfocus> Element .................................12
3.2.21. <languages> Element ...............................13
3.3. Device Capabilities .......................................13
3.3.1. <devcaps> Element ..................................13
3.3.2. <mobility> Element .................................14
3.3.3. <description> Element ..............................14
4. Usage Guidelines ...............................................15
4.1. Use of <supported> and <notsupported> Elements ............15
5. Examples .......................................................16
6. XML Schema Definitions .........................................17
7. IANA Considerations ............................................26
7.1. URN Sub-Namespace Registration for ........................26
7.2. Schema Registration for Schema ............................27
8. Security Considerations ........................................27
9. Acknowledgments ................................................27
10. References ....................................................27
10.1. Normative References .....................................27
10.2. Informative References ...................................28
Lonnfors & Kiss Standards Track [Page 2]
RFC 5196 User Agent Capability Presence Status September 2008
1. Introduction
Common Profile for Presence (CPP) [RFC3859] and Common Profile for
Instant Messaging (CPIM) [RFC3860] define common operations and
formats that all presence and instant messaging services must agree
upon so that basic interoperability is possible. The actual base
format for the presence is defined in the Presence Information
Show full document text