IETF Logo Mail Archive

Re: [sipcore] draft-barnes-sipcore-rfc4244bis

"Worley, Dale R (Dale)" <dworley@avaya.com> Thu, 11 November 2010 10:41 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 6AD2E3A68C6 for <sipcore@core3.amsl.com>; Thu, 11 Nov 2010 02:41:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.41
X-Spam-Level:
X-Spam-Status: No, score=-102.41 tagged_above=-999 required=5 tests=[AWL=0.189, 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 5AtnTdyHfA7A for <sipcore@core3.amsl.com>; Thu, 11 Nov 2010 02:41:33 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 956AD3A6933 for <sipcore@ietf.org>; Thu, 11 Nov 2010 02:41:31 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAAtX20zGmAcF/2dsb2JhbACiQXGmZgKZPIVKBIRaiSM
X-IronPort-AV: E=Sophos;i="4.59,182,1288584000"; d="scan'208";a="218082025"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 11 Nov 2010 05:41:59 -0500
X-IronPort-AV: E=Sophos;i="4.59,182,1288584000"; d="scan'208";a="539233088"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 11 Nov 2010 05:41:58 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Thu, 11 Nov 2010 05:41:58 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Cullen Jennings <fluffy@cisco.com>, "sipcore@ietf.org" <sipcore@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Thu, 11 Nov 2010 05:39:46 -0500
Thread-Topic: [sipcore] draft-barnes-sipcore-rfc4244bis
Thread-Index: AcuBhKpVmXrHPIR2S6Cvc/vbGh0vQgACBe03
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288A0A@DC-US1MBEX4.global.avaya.com>
References: <14FFF078-E5D1-45F2-8D9A-AD52DE677CEF@cisco.com>
In-Reply-To: <14FFF078-E5D1-45F2-8D9A-AD52DE677CEF@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
Subject: Re: [sipcore] draft-barnes-sipcore-rfc4244bis
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: Thu, 11 Nov 2010 10:41:36 -0000

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

Specifically I would like to see normative language on how a voicemail system can use the tags found in an incoming invite to determined which mailbox the call should be delivered too.
_______________________________________________

I don't think we should (or even can) make such an algorithm normative, but the draft should include example algorithms to demonstrate how applications can do the things that we want to support.

Dale

v2.23.0 | Report a Bug | By Email