IETF Logo Mail Archive

Re: [salud] Expanding where Alert-Info can appear

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 25 March 2013 23:08 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8188721F8820 for <salud@ietfa.amsl.com>; Mon, 25 Mar 2013 16:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.189
X-Spam-Level:
X-Spam-Status: No, score=-0.189 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VlW1A4OXA8Sq for <salud@ietfa.amsl.com>; Mon, 25 Mar 2013 16:08:52 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id 178A821F8804 for <salud@ietf.org>; Mon, 25 Mar 2013 16:08:51 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta02.westchester.pa.mail.comcast.net with comcast id Fm751l0021ei1Bg51z8rEH; Mon, 25 Mar 2013 23:08:51 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta24.westchester.pa.mail.comcast.net with comcast id Fz8r1l00H3ZTu2S3kz8rc1; Mon, 25 Mar 2013 23:08:51 +0000
Message-ID: <5150D902.2020500@alum.mit.edu>
Date: Tue, 26 Mar 2013 07:08:50 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: salud@ietf.org
References: <201303252138.r2PLcv0j1165544@shell01.TheWorld.com>
In-Reply-To: <201303252138.r2PLcv0j1165544@shell01.TheWorld.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1364252931; bh=nVgja2h1fhAFNRybmhERRzAPdIRDJztV+vYrYHkJ6uA=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=clXJH8JC5vOpjuwN+ZHuhFhwNik2c0sUl/5lIdE2WK4NNw7AbmNMOGz4yRILEq0nh HFa5lrYy7rrCRdP3xZgpB956L+8TP6Fk7flidyqjT/YVSbqkRP8O8Q992ybwv3elVZ O3oBRB3h0VIFVOxeJBWDZ0VB2JqciiUR6XRJllDcN3Qx1fbB7Dp/f/aeryU2lZM+cV 3Ky216o9REMmP0f+TG91Xzz0siTN7mjnUrQSTPGAVKLgmJktx1WYqorvp/UINAmwIo Y6SILDj+qrS9H0v5AP5gtzSaffeYS9IY01t7RIK0Myl4rT+qjsJoUTGsPbEcQNdAi+ SnWGoa5FBeHpw==
Subject: Re: [salud] Expanding where Alert-Info can appear
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 25 Mar 2013 23:08:53 -0000

WFM

On 3/26/13 5:38 AM, Dale R. Worley wrote:
> Currently, we have this text at the start of section 1.2:
>
>     1.2.  Alert-Info Header Field Usage Change
>
>     This specification 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).
>
> This is correct, but it suggests that Alert-Info may not now be used
> in provisional responses.  Looking at RFC 3261, Alert-Info may be used
> in 180 responses, but not other responses.  I believe that we intend
> to allow Alert-Info in all responses, so that it can be used in, for
> example, 181 Call Is Being Forwarded and 182 Call Is Being Queued
> responses, for which ringback tones are often provided.
>
> I think we should explain the situation more fully, perhaps by adding
>
>     Previously, the Alert-Info header field was only permitted in 180
>     (Ringing) responses.  But in telephony, other situations indicated
>     by SIP provisional responses, such as 181 (Call Is Being Forwarded)
>     and 182 (Call Is Being Queued), are often indicated by tones.
>     Extending the applicability of Alert-Info allows the telephony
>     practice to be implemented in SIP.
>
> Comments?
>
> Dale
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>

v2.23.0 | Report a Bug | By Email