Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Presence
RFC 8048
| Document | Type |
RFC - Proposed Standard
(December 2016; No errata)
Obsoletes RFC 7248
|
|
|---|---|---|---|
| Last updated | 2016-12-28 | ||
| Replaces | draft-saintandre-stox-7248bis | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Saúl Corretgé | ||
| Shepherd write-up | Show (last changed 2015-09-16) | ||
| IESG | IESG state | RFC 8048 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Ben Campbell | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) P. Saint-Andre
Request for Comments: 8048 Filament
Obsoletes: 7248 December 2016
Category: Standards Track
ISSN: 2070-1721
Interworking between the Session Initiation Protocol (SIP) and the
Extensible Messaging and Presence Protocol (XMPP): Presence
Abstract
This document defines a bidirectional protocol mapping for the
exchange of presence information between the Session Initiation
Protocol (SIP) and the Extensible Messaging and Presence Protocol
(XMPP). This document obsoletes RFC 7248.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8048.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Saint-Andre Standards Track [Page 1]
RFC 8048 SIP-XMPP Interworking: Presence December 2016
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Intended Audience . . . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Architectural Assumptions . . . . . . . . . . . . . . . . . . 5
5. Presence Authorizations . . . . . . . . . . . . . . . . . . . 6
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 6
5.2. XMPP to SIP . . . . . . . . . . . . . . . . . . . . . . . 7
5.2.1. Requesting a Presence Authorization . . . . . . . . . 7
5.2.2. Refreshing a Notification Dialog . . . . . . . . . . 11
5.2.3. Cancelling a Presence Authorization . . . . . . . . . 11
5.3. SIP to XMPP . . . . . . . . . . . . . . . . . . . . . . . 15
5.3.1. Requesting a Presence Authorization . . . . . . . . . 15
5.3.2. Refreshing a Notification Dialog . . . . . . . . . . 18
5.3.3. Cancelling a Presence Authorization . . . . . . . . . 19
6. Notifications of Presence Information . . . . . . . . . . . . 19
6.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 19
6.2. XMPP to SIP . . . . . . . . . . . . . . . . . . . . . . . 20
6.3. SIP to XMPP . . . . . . . . . . . . . . . . . . . . . . . 25
7. Polling for Presence Information . . . . . . . . . . . . . . 27
7.1. XMPP to SIP . . . . . . . . . . . . . . . . . . . . . . . 27
7.2. SIP to XMPP . . . . . . . . . . . . . . . . . . . . . . . 28
8. Privacy and Security Considerations . . . . . . . . . . . . . 28
8.1. Amplification Attacks . . . . . . . . . . . . . . . . . . 28
8.2. Presence Leaks . . . . . . . . . . . . . . . . . . . . . 29
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 30
9.1. Normative References . . . . . . . . . . . . . . . . . . 30
9.2. Informative References . . . . . . . . . . . . . . . . . 31
Appendix A. Changes from RFC 7248 . . . . . . . . . . . . . . . 33
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 34
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 34
Saint-Andre Standards Track [Page 2]
RFC 8048 SIP-XMPP Interworking: Presence December 2016
1. Introduction
Presence is information about the availability of an entity (such as
network availability or availability for communication). Presence
features in both SIP and XMPP involve several aspects:
o A long-lived authorization for a user to receive notifications
about a contact's presence across presence and notification
sessions; such an authorization is formally requested by the user,
approved (or not) by the contact, and often associated with a
record in an address list or "buddy list".
Show full document text