Re: [Iptel] Is trunk group a new namespace?

Cullen Jennings <fluffy@cisco.com> Sun, 23 January 2005 14:53 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16971 for <iptel-web-archive@ietf.org>; Sun, 23 Jan 2005 09:53:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CsjNf-0003xe-DC for iptel-web-archive@ietf.org; Sun, 23 Jan 2005 10:10:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Csj6A-0004DW-NB; Sun, 23 Jan 2005 09:52:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Csj5V-00047z-VH for iptel@megatron.ietf.org; Sun, 23 Jan 2005 09:51:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16886 for <iptel@ietf.org>; Sun, 23 Jan 2005 09:51:36 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CsjLo-0003uM-Iw for iptel@ietf.org; Sun, 23 Jan 2005 10:08:29 -0500
Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-4.cisco.com with ESMTP; 23 Jan 2005 06:52:59 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com [171.70.93.57]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j0NEoiRi012943; Sun, 23 Jan 2005 06:51:03 -0800 (PST)
Received: e2k4.cisco.com 171.70.93.57 from 10.21.80.13 10.21.80.13 via HTTP with MS-WebStorage 6.5.6944
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Sat, 22 Jan 2005 20:15:55 -0800
Subject: Re: [Iptel] Is trunk group a new namespace?
From: Cullen Jennings <fluffy@cisco.com>
To: "Vijay K. Gurbani" <vkg@lucent.com>, Jonathan Rosenberg <jdrosen@cisco.com>
Message-ID: <BE1864FB.2470B%fluffy@cisco.com>
In-Reply-To: <41F127D7.2030002@lucent.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.6 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: "iptel@ietf.org" <iptel@ietf.org>
X-BeenThere: iptel@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Telephony <iptel.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/iptel>
List-Post: <mailto:iptel@ietf.org>
List-Help: <mailto:iptel-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=subscribe>
Sender: iptel-bounces@ietf.org
Errors-To: iptel-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit

On 1/21/05 6:03 AM, "Vijay K. Gurbani" <vkg@lucent.com> wrote:

>> I'd rather not do that. Instead, I'd rather declare this problem
>> (indicating a trunk group without a phone number) as out of scope. This
>> is not a tel URI issue at all - its an ISUP to SIP mapping issue. Our
>> job is to define a way to extend the tel URI to be able to indicate
>> trunk groups, and nothing more.
> 
> As I have so learnt in the past couple of weeks, the calling number
> is optional in ISUP.  So, I would also agree that mapping an
> absent ISUP parameter to a SIP element is an ISUP to SIP mapping
> issue and outside the scopr of the trunk-group I-D.
> 
> I will consider this issue resolved, and will rev up the draft
> with the WGLC and other discussions shortly.

This sounds like the best path forward to me. I'm happy with this.

Cullen - not as chair.

Actually as chair, after listening to all the options, I really think this
is the only path that has a good chance of closing this issues anytime in
next year to two. Given the WG desire to finish this work, I think this is
the best path forward with my chair hat on too :-)



_______________________________________________
Iptel mailing list
Iptel@ietf.org
https://www1.ietf.org/mailman/listinfo/iptel