Instant Messaging and Presence Purpose for the Call-Info Header Field in the Session Initiation Protocol (SIP)
draft-saintandre-impp-call-info-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-05-14 (latest revision 2013-04-16)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd None
IESG IESG state Waiting for AD Go-Ahead
Telechat date
Responsible AD Gonzalo Camarillo
IESG note The document shepherd is Yana Stamcheva (yana@jitsi.org).
Send notices to psaintan@cisco.com, draft-saintandre-impp-call-info@tools.ietf.org, yana@jitsi.org
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                     P. Saint-Andre
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                          April 16, 2013
Expires: October 18, 2013

Instant Messaging and Presence Purpose for the Call-Info Header Field in
                 the Session Initiation Protocol (SIP)
                   draft-saintandre-impp-call-info-02

Abstract

   This document defines and registers a value of "impp" ("instant
   messaging and presence protocol") for the "purpose" header field
   parameter of the Call-Info header field in the Session Initiation
   Protocol (SIP).

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 18, 2013.

Copyright Notice

   Copyright (c) 2013 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             Expires October 18, 2013                [Page 1]
Internet-Draft          Call-Info Purpose: IMPP               April 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Security Considerations . . . . . . . . . . . . . . . . . . .   2
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
     4.2.  Informative References  . . . . . . . . . . . . . . . . .   3
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   To improve interoperability among real-time communication endpoints
   that support the combined use of the Session Initiation Protocol
   (SIP) [RFC3261] and the Extensible Messaging and Presence Protocol
   (XMPP) [RFC6120] (so-called "CUSAX" endpoints [I-D.ivov-xmpp-cusax]),
   it can be helpful to communicate the endpoint's SIP address over XMPP
   and the endpoint's XMPP address over SIP to provide hints about the
   endpoints communication capabilities.  The former feature is enabled
   by an XMPP extension protocol called Reachability Addresses
   [XEP-0152].  As to the latter feature, discussion in the SIP
   community led to the conclusion that it would be best to use the
   Call-Info header field [RFC3261] with a value of "impp" ("instant
   messaging and presence protocol") for the "purpose" header field
   parameter.  This document defines and registers the "impp" value.

   (Although CUSAX endpoints constitute the primary use case for the
   "impp" purpose, a Uniform Resource Identifier (URI) [RFC3986] for an
   instant messaging and presence protocol other than XMPP could be
   included in the Call-Info header field.)

2.  Security Considerations

   Advertising an endpoint's XMPP address over SIP could inform
   malicious entities about an alternative attack vector.  Because the
   "purpose" header field parameter could be spoofed, the receiving
   endpoint ought to check the value against an authoritative source
   such as a user directory.  Clients can integrity protect and encrypt
   this header field using end-to-end mechanisms such as S/MIME or hop-
   by-hop mechanisms such as TLS.

Saint-Andre             Expires October 18, 2013                [Page 2]
Internet-Draft          Call-Info Purpose: IMPP               April 2013
Show full document text