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

"Worley, Dale R (Dale)" <dworley@avaya.com> Tue, 31 August 2010 15:36 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 DD3D13A6804 for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 08:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.389
X-Spam-Level:
X-Spam-Status: No, score=-102.389 tagged_above=-999 required=5 tests=[AWL=0.210, 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 otCcNPc+idE9 for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 08:36:40 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 58C053A69C6 for <sipcore@ietf.org>; Tue, 31 Aug 2010 08:36:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,298,1280721600"; d="scan'208";a="32480446"
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; 31 Aug 2010 11:36:50 -0400
X-IronPort-AV: E=Sophos;i="4.56,298,1280721600"; d="scan'208";a="504625079"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 31 Aug 2010 11:36:10 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.129]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Tue, 31 Aug 2010 11:36:10 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Tue, 31 Aug 2010 11:34:03 -0400
Thread-Topic: [sipcore] #2: Editorial: section 2 is really confusing
Thread-Index: ActIbNkTQNLW/wwQTzu3KR+4Ss11TQAtRf+Y
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FFC79BFD@DC-US1MBEX4.global.avaya.com>
References: <294E3E61-2DFE-4427-92F0-EDBDBE2888CC@acmepacket.com>
In-Reply-To: <294E3E61-2DFE-4427-92F0-EDBDBE2888CC@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
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 15:36:45 -0000

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

Do you not want to use the term "Divert" because of the Diversion header?

I think it's the only term left that isn't ambiguous... "retarget" is being used for any/all cases of changing the request-uri, and "forward" is used for generic message routing procedures, and "redirect" is used for 3xx cases.  So there isn't a term left I can think of that means "changing the target to a new user/identity" (i.e., "call forwarding" in the PSTN).

And really the draft would be clearer if there was a unique term for that, because a lot of use-cses depend on it: finding the previous or current diverted-to party.
______________________________________________

People use these various terms freely, but in reality, none of them are well-defined and people don't use the same definition for each term.  The current doc carries forward this confusion by deferring the meanings to previous documents.  The only useful way to deal with the situation is to define the terms we want to use ab initio in this document.

Dale