IETF Logo Mail Archive

Re: [sipcore] Why doesn't 4244bis cover Marianne's use-case?

"Worley, Dale R (Dale)" <dworley@avaya.com> Fri, 19 November 2010 16:45 UTC

Return-Path: <dworley@avaya.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 0E3073A684F for <sipcore@core3.amsl.com>; Fri, 19 Nov 2010 08:45:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.469
X-Spam-Level:
X-Spam-Status: No, score=-102.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, 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 QtmBWnLwJ9SP for <sipcore@core3.amsl.com>; Fri, 19 Nov 2010 08:45:38 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 264DD3A67F2 for <sipcore@ietf.org>; Fri, 19 Nov 2010 08:45:38 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHo45kyHCzI1/2dsb2JhbACiYXGkFQKZM4VLBIRaiSk
X-IronPort-AV: E=Sophos;i="4.59,224,1288584000"; d="scan'208";a="46340221"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 19 Nov 2010 11:46:27 -0500
X-IronPort-AV: E=Sophos;i="4.59,224,1288584000"; d="scan'208";a="541491481"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 19 Nov 2010 11:45:57 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 19 Nov 2010 11:45:56 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>, "sipcore@ietf.org WG" <sipcore@ietf.org>
Date: Fri, 19 Nov 2010 11:42:57 -0500
Thread-Topic: Why doesn't 4244bis cover Marianne's use-case?
Thread-Index: AcuCDjF+SApIdspJSNqP2SboPfuUGAF+qBD9
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288A40@DC-US1MBEX4.global.avaya.com>
References: <2F27AF47-BD50-45FC-A832-DD845EEAA8FA@acmepacket.com>
In-Reply-To: <2F27AF47-BD50-45FC-A832-DD845EEAA8FA@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [sipcore] Why doesn't 4244bis cover Marianne's use-case?
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: Fri, 19 Nov 2010 16:45:39 -0000

________________________________________
From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On Behalf Of Hadriel Kaplan [HKaplan@acmepacket.com]

It was unfortunate that we ran out of time in sipcore to talk about Marianne's draft, because I think it's a kind of litmus test of rfc4244bis.  Or else I think I must be missing something very basic. (easily the case)
_______________________________________________

As others have said in other terms,  draft-mohali-diversion-history-info is orthogonal to 4244bis.  draft-mohali provides additional Reason values that provide more detailed information on why a call was routed as it was.  Those Reason values will be recorded in H-I according to 4244bis.  In a sense, draft-mohali *is* a litmus test of 4244bis, because without H-I, the value of the new Reason values would be dramatically reduced.  But since the two are orthogonal, draft-mohali needs to be specified, but it can be specified separately.

Dale

v2.23.0 | Report a Bug | By Email