IETF Logo Mail Archive

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

Laura Liess <laura.liess.dt@googlemail.com> Tue, 26 March 2013 12:34 UTC

Return-Path: <laura.liess.dt@googlemail.com>
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 8CF5121F8A5E for <salud@ietfa.amsl.com>; Tue, 26 Mar 2013 05:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 gueIIU0tN+XR for <salud@ietfa.amsl.com>; Tue, 26 Mar 2013 05:34:07 -0700 (PDT)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 8F08621F8A55 for <salud@ietf.org>; Tue, 26 Mar 2013 05:34:07 -0700 (PDT)
Received: by mail-la0-f42.google.com with SMTP id fe20so13494700lab.15 for <salud@ietf.org>; Tue, 26 Mar 2013 05:34:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=QccGhBAD5CMHO5EzfCb+vKaiGQAkRDFJdUCMMtwpqRg=; b=lh1ihiz+pkTQ7l+YIoydtPeACJ4arH1Y7Y0vRCOadXPKDO05PlCih9tzJrbk2QbQ/2 tA/3sNSHvAdwtiCLNgaH27rAKULiirAVDyU7gTcQUGuqurlsHqm3wY85LNSmPY7iCf0X Shw682i9aO5v5nzRdJpN5r+ughl7UWPvYzrxLKxWulvCvMGwiqq8xMaiaOmSnk84GP95 Sg4A7mHUyC43bU5Y/nYlaXJniz4cZvgDJ9wLWNS/kAZfkpoW2hXOc/7ggB0O6/1JzrfW qbRUv2Lvd9f5YvBt/moACjpAqEaPsZnc27GJnG9Ji/EqE4ChOh54IxBDZ9azPMrUAPp6 rKdg==
MIME-Version: 1.0
X-Received: by 10.152.104.80 with SMTP id gc16mr8174766lab.49.1364301246394; Tue, 26 Mar 2013 05:34:06 -0700 (PDT)
Received: by 10.114.95.99 with HTTP; Tue, 26 Mar 2013 05:34:06 -0700 (PDT)
In-Reply-To: <201303252138.r2PLcv0j1165544@shell01.TheWorld.com>
References: <201303252138.r2PLcv0j1165544@shell01.TheWorld.com>
Date: Tue, 26 Mar 2013 13:34:06 +0100
Message-ID: <CACWXZj36HgcpB1XnA+CdBTaBOJehiTA6a0WA17D7pcjyXKQuJA@mail.gmail.com>
From: Laura Liess <laura.liess.dt@googlemail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary="f46d040714d52876bf04d8d3232c"
Cc: salud@ietf.org
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: Tue, 26 Mar 2013 12:34:08 -0000

I am fine with the added text.

Thank you,
Laura

2013/3/25 Dale R. Worley <worley@ariadne.com>

> 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