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

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 25 March 2015 21:44 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 0E31D1A00D8 for <salud@ietfa.amsl.com>; Wed, 25 Mar 2015 14:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 L992ZcfKCRQP for <salud@ietfa.amsl.com>; Wed, 25 Mar 2015 14:44:23 -0700 (PDT)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EA251A1A2D for <salud@ietf.org>; Wed, 25 Mar 2015 14:44:23 -0700 (PDT)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-03v.sys.comcast.net with comcast id 7xkB1q0012Qkjl901xkNmR; Wed, 25 Mar 2015 21:44:22 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-15v.sys.comcast.net with comcast id 7xkN1q00C3Ge9ey01xkNcL; Wed, 25 Mar 2015 21:44:22 +0000
Message-ID: <55132C35.3060909@alum.mit.edu>
Date: Wed, 25 Mar 2015 17:44:21 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: salud@ietf.org
References: <20150325160916.B331618046D@rfc-editor.org>
In-Reply-To: <20150325160916.B331618046D@rfc-editor.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1427319862; bh=LxABICsUMA3Ji3s8pNzoUUZ3/2puFX7b93cXUhs1n/g=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=h2BpHJ/BQmhjiiJR76LTE0QXJns5RHsLKavbdHMs+VjftVWoleHyanrJlMcyu34QI jJNCKOEqhWSk1m9izofpOzQT2rkHwQbf8A0QCHT9szXszyVqSP6ftYFHm3daoCJEW1 1V+I6ZMcXihiEt98PPpuPFXrd7IGiPBUCMZV+mfHXikU9EAUQsx27MqIxQ+q4H9mK0 wq9oSJRUL89YbtthA7sAlwn8f/B7phVHfmAGKw5ghzOkUkArslZVlgLlIVk1QE9/u/ G+RMfe0HYg3r794BO72w9z7Oz2vu4uTly+PGJ0K2pefYRAVuIIKVSDSxJpqpw8H3I1 8HFbqT1THWVaA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/salud/eGYS4lf02KTqp5VPZJSljeTjQwI>
Subject: Re: [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 21:44:25 -0000

TA DA!!!

Special thanks to Dale, who did all the heavy lifting on this one.

	Thanks,
	Paul

On 3/25/15 12:09 PM, rfc-editor@rfc-editor.org wrote:
> 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
>
>
>