[salud] RFC 7462 on URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)

rfc-editor@rfc-editor.org Wed, 25 March 2015 16:11 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F7121B2AB9; Wed, 25 Mar 2015 09:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7L-KTJiwN4qA; Wed, 25 Mar 2015 09:11:31 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id EDE391B2AA5; Wed, 25 Mar 2015 09:10:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B331618046D; Wed, 25 Mar 2015 09:09:16 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150325160916.B331618046D@rfc-editor.org>
Date: Wed, 25 Mar 2015 09:09:16 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/salud/pZpAHYEWxLXE0IgUDN9IE9S112E>
Cc: drafts-update-ref@iana.org, salud@ietf.org, rfc-editor@rfc-editor.org
Subject: [salud] RFC 7462 on URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Wed, 25 Mar 2015 16:11:33 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7462

        Title:      URNs for the Alert-Info Header 
                    Field of the Session Initiation Protocol (SIP) 
        Author:     L. Liess, Ed.,
                    R. Jesske, A. Johnston,
                    D. Worley, P. Kyzivat
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2015
        Mailbox:    laura.liess.dt@gmail.com, 
                    r.jesske@telekom.de, 
                    alan.b.johnston@gmail.com,
                    worley@ariadne.com, 
                    pkyzivat@alum.mit.edu
        Pages:      46
        Characters: 97730
        Updates:    RFC 3261

        I-D Tag:    draft-ietf-salud-alert-info-urns-14.txt

        URL:        https://www.rfc-editor.org/info/rfc7462

The Session Initiation Protocol (SIP) supports the capability to
provide a reference to a specific rendering to be used by the User
Agent (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
any non-100 provisional response to INVITE.  This document also
permits proxies to add or remove an Alert-Info header field and to
add or remove Alert-Info header field values.

This document is a product of the Sip ALerting for User Devices Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC