Alert-Info URNs for the Session Initiation Protocol (SIP)
draft-ietf-salud-alert-info-urns-06

The information below is for an old version of the document
Document Type Active Internet-Draft (salud WG)
Last updated 2012-04-05
Replaces draft-liess-dispatch-alert-info-urns
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
SALUD                                                      L. Liess, Ed.
Internet-Draft                                                 R. Jesske
Updates: 3261 (if approved)                          Deutsche Telekom AG
Intended status: Standards Track                             A. Johnston
Expires: October 7, 2012                                       D. Worley
                                                                   Avaya
                                                              P. Kyzivat
                                                           April 5, 2012

       Alert-Info URNs for the Session Initiation Protocol (SIP)
                  draft-ietf-salud-alert-info-urns-06

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 addresses only network resources with specific
   rendering properties.  There is currently no support for predefined
   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 this limitation
   and support new applications, a new family of URNs for use in SIP
   Alert-Info header fields is defined in this specification.

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

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

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

Liess, et al.            Expires October 7, 2012                [Page 1]
Internet-Draft               Alert-Info URNs                  April 2012

   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 7, 2012.

Copyright Notice

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

Liess, et al.            Expires October 7, 2012                [Page 2]
Internet-Draft               Alert-Info URNs                  April 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.1.  Motivation . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.2.  Alert-Info Header Field Usage Change . . . . . . . . . . .  6
     1.3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  7
   2.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  7
   3.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     3.1.  PBX Ring Tones . . . . . . . . . . . . . . . . . . . . . .  9
       3.1.1.  normal . . . . . . . . . . . . . . . . . . . . . . . .  9
       3.1.2.  external . . . . . . . . . . . . . . . . . . . . . . . 10
       3.1.3.  internal . . . . . . . . . . . . . . . . . . . . . . . 10
       3.1.4.  priority . . . . . . . . . . . . . . . . . . . . . . . 10
       3.1.5.  short  . . . . . . . . . . . . . . . . . . . . . . . . 10
       3.1.6.  delayed  . . . . . . . . . . . . . . . . . . . . . . . 10
     3.2.  Service Tones  . . . . . . . . . . . . . . . . . . . . . . 10
       3.2.1.  call-waiting . . . . . . . . . . . . . . . . . . . . . 10
Show full document text