Re: [sipcore] #2: Editorial: section 2 is really confusing

Hadriel Kaplan <HKaplan@acmepacket.com> Tue, 31 August 2010 23:43 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 D9D0C3A681F for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 16:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level:
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[AWL=0.165, 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 guP5Foi3Q1PX for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 16:43:44 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id EBC633A67EF for <sipcore@ietf.org>; Tue, 31 Aug 2010 16:43:43 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Tue, 31 Aug 2010 19:44:14 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Tue, 31 Aug 2010 19:44:14 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Date: Tue, 31 Aug 2010 19:44:09 -0400
Thread-Topic: [sipcore] #2: Editorial: section 2 is really confusing
Thread-Index: ActJZmrev9r8fAZJR9eEGKhrb6C3yw==
Message-ID: <EE0E37D0-C68C-405A-8C9A-58EF4E1FAD16@acmepacket.com>
References: <294E3E61-2DFE-4427-92F0-EDBDBE2888CC@acmepacket.com> <CD5674C3CD99574EBA7432465FC13C1B21FFC79BFD@DC-US1MBEX4.global.avaya.com>, <AANLkTinnYZDcy7WLq-zeik65b9Cv-Q1Ck+-TW-c9_=KQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B21FFC79C02@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C02@DC-US1MBEX4.global.avaya.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: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] #2: Editorial: section 2 is really confusing
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: Tue, 31 Aug 2010 23:43:45 -0000

+1

On Aug 31, 2010, at 2:36 PM, Worley, Dale R (Dale) wrote:

> It seems to me that the definitions of "retargeting", "redirecting", etc. (with the possible exception of "diversion") are not clear and have never been clear.  Up until 4244bis, this hasn't mattered.  But in 4244bis these allegedly distinct operations cause different things to go on the wire, so we have to make the definitions unambiguous.
> 
> Dale