[salud] I-D Action: draft-ietf-salud-alert-info-urns-13.txt

internet-drafts@ietf.org Mon, 21 July 2014 00:41 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id CCC841B2A99; Sun, 20 Jul 2014 17:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id NsiPefMBasye; Sun, 20 Jul 2014 17:41:25 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 772B81B2A64; Sun, 20 Jul 2014 17:41:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140721004125.13401.30696.idtracker@ietfa.amsl.com>
Date: Sun, 20 Jul 2014 17:41:25 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/w7bkEZBLQPv7LIVl9MzampTPNW0
Cc: salud@ietf.org
Subject: [salud] I-D Action: draft-ietf-salud-alert-info-urns-13.txt
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud/>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jul 2014 00:41:26 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Sip ALerting for User Devices Working Group of the IETF.

        Title           : URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)
        Authors         : Laura Liess
                          Roland Jesske
                          Alan Johnston
                          Dale R. Worley
                          Paul Kyzivat
	Filename        : draft-ietf-salud-alert-info-urns-13.txt
	Pages           : 45
	Date            : 2014-07-20

   The Session Initiation Protocol (SIP) supports the capability to
   provide a reference to a specific rendering to be used by the UA as
   an alerting signal (e.g., a ring tone or ringback tone) 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 RFC 3261, which defines the Session
   Initiation Protocol (SIP): It changes the usage of the Alert-Info
   header field defined in RFC 3261 by additionally allowing its use in
   all provisional responses to INVITE (except the 100 response).  This
   document also permits proxies to add and remove header field values
   from the Alert-Info header field.

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at: