Re: [sipcore] I-D Action: draft-mohali-sipcore-reason-extension-application-01
Paul Kyzivat <pkyzivat@cisco.com> Mon, 28 February 2011 23:15 UTC
Return-Path: <pkyzivat@cisco.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CD103A6A21 for <sipcore@core3.amsl.com>; Mon, 28 Feb 2011 15:15:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.431
X-Spam-Level:
X-Spam-Status: No, score=-109.431 tagged_above=-999 required=5 tests=[AWL=-1.132, BAYES_00=-2.599, MANGLED_EXTNSN=2.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DcwdBcVfR3G7 for <sipcore@core3.amsl.com>; Mon, 28 Feb 2011 15:15:06 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id F12563A6835 for <sipcore@ietf.org>; Mon, 28 Feb 2011 15:15:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=4176; q=dns/txt; s=iport; t=1298934967; x=1300144567; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=iBE8zrSl0LC828VwundhZYC6J7+3AO/MMI9Ksoc57Pg=; b=LExIUoL3LC2v3tfPZzznc0Vssc5EzsDx2Ox3CZ57lCjysA8Rq2aAifTb HjDIK6o9il5uHvfC3+lxrTtF88L7YeGKCaql1sbf+7DWSrXVmJKwBEo8g BL4LXzfV4ruocqiAAofSlkjH1F3VUISjTv3YEYROuvmcDUB6mdKXXme9f g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAAe7a01AZnwM/2dsb2JhbACmR3SfaZtjgxiCSQSFEocNgz4
X-IronPort-AV: E=Sophos;i="4.62,243,1297036800"; d="scan'208";a="220903809"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 28 Feb 2011 23:16:06 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p1SNG6pu007903 for <sipcore@ietf.org>; Mon, 28 Feb 2011 23:16:06 GMT
Message-ID: <4D6C2CB6.4040800@cisco.com>
Date: Mon, 28 Feb 2011 18:16:06 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: sipcore@ietf.org
References: <B11765B89737A7498AF63EA84EC9F5775D36A6@ftrdmel1>
In-Reply-To: <B11765B89737A7498AF63EA84EC9F5775D36A6@ftrdmel1>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [sipcore] I-D Action: draft-mohali-sipcore-reason-extension-application-01
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 23:15:07 -0000
(As individual)
Marianne,
I'm still struggling to make sense of this in the form proposed.
I look at the various cause values, and all the descriptions are of the
form. E.g.:
Cause value: 2
Reason text: Freephone
Description: A Freephone application has influenced processing of
the call (e.g. by translating a dialed Free Phone number to a
routable directory number).
I can't figure out how to make any actionable decision based on this.
Rather, it seems I need to make a number of leaps of faith before I can
decide what to do.
For instance, if I get an error, it *might* be because I dialed a
freephone number, and it isn't supported from my calling location. (E.g.
maybe I'm dialing +1-800-555-1234, but I'm doing so from France, and
calling that number is only supported in the USA.
But getting a application reason code with cause 2 doesn't really tell
me that is what happened. It could be that the call indeed was routed
through a freephone application, and it properly routed the call, and
the call failed for some other reason. But the cause is there because
the application *did* influence the call routing.
Also, these "applications" are not, AFAIK, mutually exclusive. E.g. I
could be using a prepaid service to make a directory assistance call
that costs extra $$$ that I don't have credits to cover. But you can't
include two cause values for the same protocol. (But it is true that you
*can* have a number of servers each put one cause into *their* H-I entry.)
So *maybe* I would see that my call failed, and that there is both a
reason indicating a prepaid application on one H-I entry, and another
indicating a another H-I indicating a directory service application. But
what can I conclude from that?
Bottom line, I just can't make sense how this could be used in a well
defined and interoperable way.
Thanks,
Paul
On 2/28/2011 9:58 AM, marianne.mohali@orange-ftgroup.com wrote:
> Hello,
>
> Here is the new version of the draft.
> Main changes are following:
> - More details about the registration procedure for new values
> - Clearer text in section 3.2
> - Add of Public and Private status for registered values.
> - Add of a range for cause values registration
>
> Best Regards,
> Marianne Mohali
>
> -----Message d'origine-----
> Objet : New Version Notification for
> draft-mohali-sipcore-reason-extension-application-01
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
> Title : Extending the Session Initiation Protocol
> (SIP) Reason Header for Applications
> Author(s) : M. Mohali, B. Chatras
> Filename :
> draft-mohali-sipcore-reason-extension-application-01.txt
> Pages : 10
> Date : 2011-02-24
>
> This document defines a new protocol value "Application" for the
> Reason Header field and a new IANA Registry for registering
> application types. This new value enables signaling that a request
> or response has been issued as a result of a decision made by a
> particular type of application or that an initial request has been
> retargeted as a result of an application decision.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-mohali-sipcore-reason-extensio
> n-application-01.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
> <ftp://ftp.ietf.org/internet-drafts/draft-mohali-sipcore-reason-extensio
> n-application-01.txt>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>
- [sipcore] I-D Action: draft-mohali-sipcore-reason… marianne.mohali
- Re: [sipcore] I-D Action: draft-mohali-sipcore-re… Paul Kyzivat
- Re: [sipcore] I-DAction: draft-mohali-sipcore-rea… marianne.mohali
- Re: [sipcore] I-DAction: draft-mohali-sipcore-rea… Paul Kyzivat
- Re: [sipcore] I-DAction: draft-mohali-sipcore-rea… Elwell, John
- Re: [sipcore] I-DAction: draft-mohali-sipcore-rea… marianne.mohali
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… marianne.mohali
- Re: [sipcore] I-DAction: draft-mohali-sipcore-rea… Paul Kyzivat
- Re: [sipcore] I-DAction: draft-mohali-sipcore-rea… Worley, Dale R (Dale)
- Re: [sipcore] I-DAction: draft-mohali-sipcore-rea… marianne.mohali
- Re: [sipcore] I-DAction: draft-mohali-sipcore-rea… Christer Holmberg
- Re: [sipcore] I-DAction: draft-mohali-sipcore-rea… Christer Holmberg
- Re: [sipcore] I-DAction: draft-mohali-sipcore-rea… Paul Kyzivat
- Re: [sipcore] I-DAction: draft-mohali-sipcore-rea… marianne.mohali
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… marianne.mohali
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… Worley, Dale R (Dale)
- Re: [sipcore] I-DAction: draft-mohali-sipcore-rea… Elwell, John
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… marianne.mohali
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… marianne.mohali
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… marianne.mohali
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… Elwell, John
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… marianne.mohali
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… Elwell, John
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… Paul Kyzivat
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… Paul Kyzivat
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… marianne.mohali
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… Paul Kyzivat
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… marianne.mohali
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… Mary Barnes
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… marianne.mohali
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… Mary Barnes
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… marianne.mohali
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… marianne.mohali
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… Worley, Dale R (Dale)
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… Shida Schubert
- Re: [sipcore] I-DAction:draft-mohali-sipcore-reas… marianne.mohali