datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)
draft-ietf-salud-alert-info-urns-12

SALUD                                                      L. Liess, Ed.
Internet-Draft                                                 R. Jesske
Updates: 3261 (if approved)                          Deutsche Telekom AG
Intended status: Standards Track                             A. Johnston
Expires: September 4, 2014                                         Avaya
                                                               D. Worley
                                                                 Ariadne
                                                              P. Kyzivat
                                                                  Huawei
                                                           March 3, 2014

URNs for the Alert-Info Header Field of the Session Initiation Protocol
                                 (SIP)
                  draft-ietf-salud-alert-info-urns-12

Abstract

   The Session Initiation Protocol (SIP) supports the capability to
   provide a reference to a specific rendering to be used by the UA when
   the user is alerted.  This is done using the Alert-Info header field.
   However, the reference (typically a URL) addresses only a specific
   network resource with specific rendering properties.  There is
   currently no support for standard identifiers for describing the
   semantics of the alerting situation or the characteristics of the
   alerting signal, without being tied to a particular rendering.  To
   overcome these limitations and support new applications, a new family
   of URNs for use in Alert-Info header fields (and situations with
   similar requirements) is defined in this specification.

   This document normatively updates the RFC 3261, which defines the
   Session Initiation Protocol (SIP): It changes the usage of the Alert-
   Info header field defined in the RFC 3261 by additionally allowing
   its use in all provisional responses to INVITE (except the 100
   response).

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

Liess, et al.           Expires September 4, 2014               [Page 1]
Internet-Draft                 Alert URNs                     March 2014

   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 September 4, 2014.

Copyright Notice

   Copyright (c) 2014 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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   6
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Update to RFC 3261  . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  New text replacing the text of the 1st paragraph of
           section 20.4 of       RFC 3261  . . . . . . . . . . . . .   7
   5.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   9

[include full document text]