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

Hadriel Kaplan <HKaplan@acmepacket.com> Wed, 01 September 2010 14:49 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 07DC53A6812 for <sipcore@core3.amsl.com>; Wed, 1 Sep 2010 07:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[AWL=0.151, 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 Ed-5MapSeavL for <sipcore@core3.amsl.com>; Wed, 1 Sep 2010 07:49:43 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 3083D3A6965 for <sipcore@ietf.org>; Wed, 1 Sep 2010 07:49: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; Wed, 1 Sep 2010 10:50:11 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Wed, 1 Sep 2010 10:50:02 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Date: Wed, 01 Sep 2010 10:50:00 -0400
Thread-Topic: [sipcore] #2: Editorial: section 2 is really confusing
Thread-Index: ActJ5PSOf8Afg4LoTMu70lI4aJJwbw==
Message-ID: <3A1175B1-93F3-440E-9965-5073BB426D8B@acmepacket.com>
References: <294E3E61-2DFE-4427-92F0-EDBDBE2888CC@acmepacket.com> <CD5674C3CD99574EBA7432465FC13C1B21FFC79BFD@DC-US1MBEX4.global.avaya.com> <EDC0A1AE77C57744B664A310A0B23AE214D298AE@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE214D298AE@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.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: "Worley, Dale R (Dale)" <dworley@avaya.com>, "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: Wed, 01 Sep 2010 14:49:45 -0000

Oh, excellent point.  In fact, mapping in the freephone sense isn't really the same "kind" as mapping in the call-forwarding sense, and will make it neigh impossible to distinguish at the UAS.  How will a UAS actually be able to tell apart diversions from others? (for example, to interwork to Diversion or to ISDN)

Perhaps what we really need is a specific tag for actual diverting - for the case of changing the identity of the target such that the new identity has no inherent relation to the previous target, for example with a "dv" param; whereas the freephone case the new target is much closer to "mapping" in the common english sense and would use a "mp".  No?

-hadriel


On Sep 1, 2010, at 10:01 AM, DRAGE, Keith (Keith) wrote:

> I prefer not to use the term "diversion" because there is a well defined set of ISDN diversion services, and while the use of History-Info does encompass equivalents of such services, it encompasses much more. 
> 
> Changing the target to a new Request-URI may encompass diversion (in the ISDN sense), but it could also encompass a number of other cases, including freephone and number portability.
> 
> regards
> 
> Keith
>>