Skip to main content

Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Presence
RFC 7248

Revision differences

Document history

Date Rev. By Action
2015-10-14
09 (System) Notify list changed from stox-chairs@ietf.org, draft-ietf-stox-presence@ietf.org to (None)
2014-05-22
09 Jean Mahoney Closed request for Telechat review by GENART with state 'No Response'
2014-05-21
09 (System) RFC published
2014-05-19
09 (System) RFC Editor state changed to AUTH48-DONE from AUTH48
2014-05-12
09 (System) RFC Editor state changed to AUTH48 from RFC-EDITOR
2014-04-24
09 (System) RFC Editor state changed to RFC-EDITOR from EDIT
2014-02-26
09 (System) RFC Editor state changed to EDIT from MISSREF
2014-02-14
09 Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'No Response'
2014-02-12
09 Amy Vezza IESG state changed to RFC Ed Queue from Approved-announcement sent
2014-02-12
09 (System) RFC Editor state changed to MISSREF
2014-02-12
09 (System) Announcement was received by RFC Editor
2014-02-11
09 (System) IANA Action state changed to No IC from In Progress
2014-02-11
09 (System) IANA Action state changed to In Progress
2014-02-11
09 Amy Vezza IESG state changed to Approved-announcement sent from Approved-announcement to be sent
2014-02-11
09 Amy Vezza IESG has approved the document
2014-02-11
09 Amy Vezza Closed "Approve" ballot
2014-02-11
09 Amy Vezza Ballot approval text was generated
2014-02-11
09 Amy Vezza IESG state changed to Approved-announcement to be sent from IESG Evaluation::AD Followup
2014-02-09
09 Pete Resnick [Ballot comment]
This last version (and some conversation from the author) has answered my concerns with this document. Thanks.
2014-02-09
09 Pete Resnick [Ballot Position Update] Position for Pete Resnick has been changed to Yes from Discuss
2014-02-09
09 Peter Saint-Andre New version available: draft-ietf-stox-presence-09.txt
2014-02-07
08 (System) Sub state has been changed to AD Followup from Revised ID Needed
2014-02-07
08 Peter Saint-Andre IANA Review state changed to Version Changed - Review Needed from IANA OK - No Actions Needed
2014-02-07
08 Peter Saint-Andre New version available: draft-ietf-stox-presence-08.txt
2014-02-06
07 Tero Kivinen Request for Last Call review by SECDIR Completed: Has Nits. Reviewer: Ben Laurie.
2014-02-06
07 Cindy Morgan IESG state changed to IESG Evaluation::Revised I-D Needed from IESG Evaluation
2014-02-06
07 Ted Lemon [Ballot Position Update] New position, No Objection, has been recorded for Ted Lemon
2014-02-06
07 Stephen Farrell
[Ballot comment]

If the protocol between the gateways is not protected via
(D)TLS, then doesn't this (and probabaly all other gateway
functions) act in a …
[Ballot comment]

If the protocol between the gateways is not protected via
(D)TLS, then doesn't this (and probabaly all other gateway
functions) act in a potentially privacy unfriendly manner?
I would have thought that worth noting at least, e.g. say
that if (D)TLS is not used when gatewaying then the user
has lost whatever security they used to have for their
presence. (See also my comment on stox-core wrt turning on
or requiring implementation of (D)TLS beteen gateways.)

Sorry - forgot to note the change resulting from the
secdir review [1] just in case it gets forgotten in a
rush of some sort.

  [1] https://www.ietf.org/mail-archive/web/secdir/current/msg04581.html
2014-02-06
07 Stephen Farrell Ballot comment text updated for Stephen Farrell
2014-02-06
07 Stephen Farrell
[Ballot comment]

If the protocol between the gateways is not protected via
(D)TLS, then doesn't this (and probabaly all other gateway
functions) act in a …
[Ballot comment]

If the protocol between the gateways is not protected via
(D)TLS, then doesn't this (and probabaly all other gateway
functions) act in a potentially privacy unfriendly manner?
I would have thought that worth noting at least, e.g. say
that if (D)TLS is not used when gatewaying then the user
has lost whatever security they used to have for their
presence. (See also my comment on stox-core wrt turning on
or requiring implementation of (D)TLS beteen gateways.)
2014-02-06
07 Stephen Farrell [Ballot Position Update] New position, No Objection, has been recorded for Stephen Farrell
2014-02-05
07 Joel Jaeggli [Ballot Position Update] New position, No Objection, has been recorded for Joel Jaeggli
2014-02-05
07 Pete Resnick
[Ballot discuss]
I'm worried that the following might be real interoperability problems. Hopefully quickly cleared:

4.2.2: It seems to me that you need to describe …
[Ballot discuss]
I'm worried that the following might be real interoperability problems. Hopefully quickly cleared:

4.2.2: It seems to me that you need to describe the case where the gateway attempts to do a periodic refresh and it *fails*. Should that mean that the gateway should send an "unsubscribe" to the XMPP user, or should it maintain the XMPP subscription and try again later? Does it depend on the nature of the failure? I'm not sure of the answer, but I think this section should address it.

4.3.1:

  In any case, if the XMPP-SIP gateway receives a
  presence stanza of type "subscribed" from the XMPP user, it SHOULD
  silently discard the stanza and not transform it into a SIP request.
 
Doesn't the gateway need to turn that into a SIP OK in response to the SIP SUBSCRIBE?

4.3.2 and 4.3.3 seem to indicate (example 13) that upon SIP ending its presence session or the user canceling a subscription that both the 'to' and the 'from' subscription be unsubscribed. That seems wrong. Though I can see unsubscribing the 'from', I don't know why you would unsubscribe the 'to'. The XMPP user has not "ended their presence session".
2014-02-05
07 Pete Resnick [Ballot Position Update] New position, Discuss, has been recorded for Pete Resnick
2014-02-05
07 Sean Turner [Ballot Position Update] New position, Yes, has been recorded for Sean Turner
2014-02-05
07 Richard Barnes [Ballot Position Update] New position, Yes, has been recorded for Richard Barnes
2014-02-05
07 Barry Leiba [Ballot Position Update] New position, No Objection, has been recorded for Barry Leiba
2014-02-05
07 Brian Haberman [Ballot Position Update] New position, No Objection, has been recorded for Brian Haberman
2014-02-05
07 Jari Arkko [Ballot Position Update] New position, No Objection, has been recorded for Jari Arkko
2014-02-05
07 Stewart Bryant [Ballot Position Update] New position, No Objection, has been recorded for Stewart Bryant
2014-02-05
07 Adrian Farrel [Ballot Position Update] New position, No Objection, has been recorded for Adrian Farrel
2014-02-04
07 Benoît Claise [Ballot Position Update] New position, No Objection, has been recorded for Benoit Claise
2014-02-04
07 Spencer Dawkins [Ballot Position Update] New position, Yes, has been recorded for Spencer Dawkins
2014-02-04
07 Martin Stiemerling [Ballot Position Update] New position, No Objection, has been recorded for Martin Stiemerling
2014-01-31
07 Jean Mahoney Request for Telechat review by GENART is assigned to Joel Halpern
2014-01-31
07 Jean Mahoney Request for Telechat review by GENART is assigned to Joel Halpern
2014-01-23
07 (System) IANA Review state changed to IANA OK - No Actions Needed from Version Changed - Review Needed
2014-01-23
07 Gonzalo Camarillo Placed on agenda for telechat - 2014-02-06
2014-01-23
07 Gonzalo Camarillo State changed to IESG Evaluation from Waiting for Writeup::AD Followup
2014-01-23
07 Gonzalo Camarillo Ballot has been issued
2014-01-23
07 Gonzalo Camarillo [Ballot Position Update] New position, Yes, has been recorded for Gonzalo Camarillo
2014-01-23
07 Gonzalo Camarillo Created "Approve" ballot
2014-01-23
07 Gonzalo Camarillo Ballot writeup was changed
2014-01-22
07 (System) Sub state has been changed to AD Followup from Revised ID Needed
2014-01-22
07 Peter Saint-Andre IANA Review state changed to Version Changed - Review Needed from IANA OK - No Actions Needed
2014-01-22
07 Peter Saint-Andre New version available: draft-ietf-stox-presence-07.txt
2014-01-21
06 Gonzalo Camarillo State changed to Waiting for Writeup::Revised I-D Needed from Waiting for Writeup
2013-12-11
06 (System) IANA Review state changed to IANA OK - No Actions Needed from IANA - Review Needed
2013-12-11
06 Pearl Liang
IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-stox-presence-06, which is currently in Last Call, and has the following comments:

We understand that, upon approval of this …
IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-stox-presence-06, which is currently in Last Call, and has the following comments:

We understand that, upon approval of this document, there are no IANA
Actions that need completion.  IANA requests that the IANA Considerations section of the document remain in place upon publication.

If this assessment is not accurate, please respond as soon as possible.
2013-12-11
06 (System) State changed to Waiting for Writeup from In Last Call (ends 2013-12-11)
2013-12-04
06 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Mahalingam Mani
2013-12-04
06 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Mahalingam Mani
2013-12-04
06 Gunter Van de Velde Assignment of request for Last Call review by OPSDIR to Richard Woundy was rejected
2013-11-28
06 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Richard Woundy
2013-11-28
06 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Richard Woundy
2013-11-28
06 Tero Kivinen Request for Last Call review by SECDIR is assigned to Ben Laurie
2013-11-28
06 Tero Kivinen Request for Last Call review by SECDIR is assigned to Ben Laurie
2013-11-27
06 Jean Mahoney Request for Last Call review by GENART is assigned to Joel Halpern
2013-11-27
06 Jean Mahoney Request for Last Call review by GENART is assigned to Joel Halpern
2013-11-27
06 Amy Vezza IANA Review state changed to IANA - Review Needed
2013-11-27
06 Amy Vezza
The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC:
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Interworking between the Session Initiation …
The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC:
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Presence) to Proposed Standard


The IESG has received a request from the SIP-TO-XMPP WG (stox) to
consider the following document:
- 'Interworking between the Session Initiation Protocol (SIP) and the
  Extensible Messaging and Presence Protocol (XMPP): Presence'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-12-11. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  This document defines a bi-directional protocol mapping for the
  exchange of presence information between the Session Initiation
  Protocol (SIP) and the Extensible Messaging and Presence Protocol
  (XMPP).




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-stox-presence/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-stox-presence/ballot/


No IPR declarations have been submitted directly on this I-D.


2013-11-27
06 Amy Vezza State changed to In Last Call from Last Call Requested
2013-11-27
06 Gonzalo Camarillo Last call was requested
2013-11-27
06 Gonzalo Camarillo Ballot approval text was generated
2013-11-27
06 Gonzalo Camarillo Ballot writeup was generated
2013-11-27
06 Gonzalo Camarillo State changed to Last Call Requested from Publication Requested
2013-11-27
06 Gonzalo Camarillo Last call announcement was generated
2013-11-26
06 Yana Stamcheva IETF WG state changed to Submitted to IESG for Publication
2013-11-26
06 Yana Stamcheva IESG state changed to Publication Requested
2013-11-26
06 Yana Stamcheva
PROTO questionnaire for: draft-ietf-stox-presence-06

To be Published as: Proposed Standard

Prepared by: Yana Stamcheva (yana@jitsi.org)

(1) What type of RFC is being requested …
PROTO questionnaire for: draft-ietf-stox-presence-06

To be Published as: Proposed Standard

Prepared by: Yana Stamcheva (yana@jitsi.org)

(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?  Why
is this the proper type of RFC?  Is this type of RFC indicated in the
title page header?

This document is requested to be published as Proposed Standard.

(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:

Technical Summary

  Relevant content can frequently be found in the abstract
  and/or introduction of the document. If not, this may be
  an indication that there are deficiencies in the abstract
  or introduction.

This document defines a bi-directional protocol mapping for the exchange of presence information between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP).

Working Group Summary

  Was there anything in WG process that is worth noting? For
  example, was there controversy about particular points or
  were there decisions where the consensus was particularly
  rough?

This document has been initially reviewed in the DISPATCH WG as per the RAI area process for new work. The STOX WG has been chartered as a result of the submission of this and other documents that aim to define specifications for interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) based systems. This document has been subjected to a number of thorough reviews initially in the DISPATCH WG and in the STOX WG after its creation. There were no controversial points regarding it.

Document Quality

  Are there existing implementations of the protocol? Have a
  significant number of vendors indicated their plan to
  implement the specification? Are there any reviewers that
  merit special mention as having done a thorough review,
  e.g., one that resulted in important changes or a
  conclusion that the document had no substantive issues? If
  there was a MIB Doctor, Media Type or other expert review,
  what was its course (briefly)? In the case of a Media Type
  review, on what date was the request posted?

There are already several vendors having full or partial implementations of the specification, among which Jabber/Cisco, Kamailio (OpenSER), AG Projects (Silk Server). Some of the people behind these implementations have actively participated in the discussions in the WG.

Personnel

  Who is the Document Shepherd? Who is the Responsible Area
  Director?

Yana Stamcheva is the document shepherd. The responsible area director is Gonzalo Camarillo.

(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG.

The Document Shepherd has reviewed this version of the document and thinks it is ready for forwarding to IESG for publication.

(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed? 

No. The document has been out for a few years and was subjected to thorough reviews. All reviewers' comments have been addressed.

(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
took place.

No.

(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the
IESG should be aware of? For example, perhaps he or she is uncomfortable
with certain parts of the document, or has concerns whether there really
is a need for it. In any event, if the WG has discussed those issues and
has indicated that it still wishes to advance the document, detail those
concerns here.

I have no such concerns.

(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed. If not, explain why.

Yes.

(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
disclosures.

No IPR disclosure that references this document has been filed.

(9) How solid is the WG consensus behind this document? Does it
represent the strong concurrence of a few individuals, with others
being silent, or does the WG as a whole understand and agree with it? 

The WGLC has revealed a solid consensus among the active members of the STOX WG for this document going forward to publishing. There were no objections.

(10) Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director. (It should be in a
separate email because this questionnaire is publicly available.)

No.

(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.

The document was checked using idnits 2.13.00. There is a warning about the date which is innocuous as well two warnings about outdated references to earlier versions of drafts. All will naturally be addressed by the RFC Editor.

There's also a warning about a missing RFC 2119 boilerplate, which seems a false-positive, because it's already in the document and completely conform with RFC 2119.

(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.

No formal reviews other than review in the STOX WG are required for this document.

(13) Have all references within this document been identified as
either normative or informative?

Yes, all references in the document exist either in the normative or the informative sections.

(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?

No.

(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in
the Last Call procedure.

No.

(16) Will publication of this document change the status of any
existing RFCs? Are those RFCs listed on the title page header, listed
in the abstract, and discussed in the introduction? If the RFCs are not
listed in the Abstract and Introduction, explain why, and point to the
part of the document where the relationship of this document to the
other RFCs is discussed. If this information is not in the document,
explain why the WG considers it unnecessary.

No.

(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly
identified. Confirm that newly created IANA registries include a
detailed specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and a
reasonable name for the new registry has been suggested (see RFC 5226).

This document makes no requests of IANA.

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.

None.

(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.

The document contains a few XML schemas, which have been mechanically verified using the W3C validator at http://www.w3.org/2001/03/webdata/xsv.

2013-11-26
06 Yana Stamcheva State Change Notice email list changed to stox-chairs@tools.ietf.org, draft-ietf-stox-presence@tools.ietf.org
2013-11-26
06 Yana Stamcheva Responsible AD changed to Gonzalo Camarillo
2013-11-26
06 Yana Stamcheva Working group state set to Submitted to IESG for Publication
2013-11-26
06 Yana Stamcheva IESG state set to Publication Requested
2013-11-26
06 Yana Stamcheva IESG process started in state Publication Requested
2013-11-26
06 Yana Stamcheva Intended Status changed to Proposed Standard from None
2013-11-26
06 Yana Stamcheva Document shepherd changed to Yana Stamcheva
2013-11-26
06 Yana Stamcheva Changed document writeup
2013-10-18
06 Peter Saint-Andre New version available: draft-ietf-stox-presence-06.txt
2013-09-30
05 Peter Saint-Andre New version available: draft-ietf-stox-presence-05.txt
2013-09-05
04 Peter Saint-Andre New version available: draft-ietf-stox-presence-04.txt
2013-08-19
03 Peter Saint-Andre New version available: draft-ietf-stox-presence-03.txt
2013-08-16
02 Peter Saint-Andre New version available: draft-ietf-stox-presence-02.txt
2013-08-03
01 Peter Saint-Andre New version available: draft-ietf-stox-presence-01.txt
2013-07-01
00 Peter Saint-Andre New version available: draft-ietf-stox-presence-00.txt