RE: WG Review: Call Control UUI for SIP (cuss)

"WORLEY, Dale R (Dale)" <dworley@avaya.com> Thu, 15 July 2010 17:42 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80B633A6B44; Thu, 15 Jul 2010 10:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.163
X-Spam-Level:
X-Spam-Status: No, score=-2.163 tagged_above=-999 required=5 tests=[AWL=0.436, BAYES_00=-2.599]
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 1ItBgHV3DOyc; Thu, 15 Jul 2010 10:42:23 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 7E6A83A6A68; Thu, 15 Jul 2010 10:42:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.55,209,1278302400"; d="scan'208";a="228042454"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 15 Jul 2010 13:42:34 -0400
X-IronPort-AV: E=Sophos;i="4.55,209,1278302400"; d="scan'208";a="492037241"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 15 Jul 2010 13:42:33 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.161]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 15 Jul 2010 13:42:33 -0400
From: "WORLEY, Dale R (Dale)" <dworley@avaya.com>
To: Cullen Jennings <fluffy@cisco.com>, Gonzalo Camarillo <gcamaril@gmail.com>
Date: Thu, 15 Jul 2010 13:40:35 -0400
Subject: RE: WG Review: Call Control UUI for SIP (cuss)
Thread-Topic: WG Review: Call Control UUI for SIP (cuss)
Thread-Index: AcskJubCPZh5hVQqSOqC2oSZjXlHwAAHe2ih
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FE98EECE@DC-US1MBEX4.global.avaya.com>
References: <4C28F980.3040702@ericsson.com> <AANLkTinf6-mtUKbdtw0p2j0xJQPBr4S-XCiimSNoKNdC@mail.gmail.com> <0010F1C2-2436-474D-BC1C-05AFC8A9E4C5@cisco.com> <4C3D7496.8020905@gmail.com>, <71EA364F-6D56-45B3-BB9C-9C9AE1E1266C@cisco.com>
In-Reply-To: <71EA364F-6D56-45B3-BB9C-9C9AE1E1266C@cisco.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
Cc: DISPATCH list <dispatch@ietf.org>, IESG IESG <iesg@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 17:42:24 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Cullen Jennings [fluffy@cisco.com]

I don't think this resolves the issue. The issue is if this information is used for a call control. Basically do proxies need to be able to look at this to make decision about what they are going to do. We at least need a Yes/No answer to this question from the proponents of this work and the charter to make that clear.
_______________________________________________

>From the discussion, it seems that proxies will not make call control decisions based on the *contents* of UUI, but they may make call control decisions (specifically, rejection) based on the *presence* of UUI.  So whether the anser is Yes or No depends on exactly how you phrase the question.

Dale