IETF Logo Mail Archive

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

Hadriel Kaplan <HKaplan@acmepacket.com> Sat, 20 November 2010 14:32 UTC

Return-Path: <HKaplan@acmepacket.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 2497A3A69D8 for <sipcore@core3.amsl.com>; Sat, 20 Nov 2010 06:32:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 tagged_above=-999 required=5 tests=[AWL=0.505, 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 q3QWz9MMc6Rl for <sipcore@core3.amsl.com>; Sat, 20 Nov 2010 06:32:31 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 163703A69D7 for <sipcore@ietf.org>; Sat, 20 Nov 2010 06:32:29 -0800 (PST)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sat, 20 Nov 2010 09:33:20 -0500
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Sat, 20 Nov 2010 09:33:20 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "<marianne.mohali@orange-ftgroup.com> <marianne.mohali@orange-ftgroup.com>" <marianne.mohali@orange-ftgroup.com>
Date: Sat, 20 Nov 2010 09:33:15 -0500
Thread-Topic: [sipcore] Why doesn't 4244bis cover Marianne's use-case?
Thread-Index: AcuIv98uHrJ4/VxiST+M4qwVm/gS+A==
Message-ID: <A9FE1CF3-FD8C-4F0D-8780-6191292640BE@acmepacket.com>
References: <2F27AF47-BD50-45FC-A832-DD845EEAA8FA@acmepacket.com><4CDCAC2F.2090904@nostrum.com> <479339F9-5AE2-4145-A132-36F53D011ECF@acmepacket.com> <B11765B89737A7498AF63EA84EC9F5771EF0BF@ftrdmel1>
In-Reply-To: <B11765B89737A7498AF63EA84EC9F5771EF0BF@ftrdmel1>
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: "sipcore@ietf.org" <sipcore@ietf.org>
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: Sat, 20 Nov 2010 14:32:35 -0000

On Nov 19, 2010, at 10:32 AM, <marianne.mohali@orange-ftgroup.com> <marianne.mohali@orange-ftgroup.com> wrote:

> Hadriel, you said "When I read Marianne's draft, it sounds like the use-case she's trying to cover is call-forwarding" 
> but the presented draft has really NO link with Call Forwarding (it is an other draft ;-).

Sorry for the confusion - I meant draft-mohali-sipcore-reason-call-forwarding-00 specifically.

-hadriel

v2.23.0 | Report a Bug | By Email