Re: [Sipping] SUMMARY: Trunk groups in R-URI

Mpierce1@aol.com Thu, 05 September 2002 18:40 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01808 for <sipping-archive@odin.ietf.org>; Thu, 5 Sep 2002 14:40:29 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g85Ifdq20623 for sipping-archive@odin.ietf.org; Thu, 5 Sep 2002 14:41:39 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Ifdp20620 for <sipping-web-archive@optimus.ietf.org>; Thu, 5 Sep 2002 14:41:39 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01793 for <sipping-web-archive@ietf.org>; Thu, 5 Sep 2002 14:39:59 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85IbCp19694; Thu, 5 Sep 2002 14:37:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85IIQp17820 for <sipping@optimus.ietf.org>; Thu, 5 Sep 2002 14:18:26 -0400
Received: from imo-r05.mx.aol.com (imo-r05.mx.aol.com [152.163.225.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00448 for <sipping@ietf.org>; Thu, 5 Sep 2002 14:16:46 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com by imo-r05.mx.aol.com (mail_out_v34.10.) id g.173.dfd98ce (3940); Thu, 5 Sep 2002 14:17:37 -0400 (EDT)
Message-ID: <173.dfd98ce.2aa8f9c1@aol.com>
Date: Thu, 05 Sep 2002 14:17:37 -0400
Subject: Re: [Sipping] SUMMARY: Trunk groups in R-URI
To: jon.peterson@neustar.biz, vkg@lucent.com, sipping@ietf.org
CC: fluffy@cisco.com, adam@dynamicsoft.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_173.dfd98ce.2aa8f9c1_boundary"
X-Mailer: AOL 6.0 for Windows US sub 353
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>

In a message dated 9/4/02 7:21:45 PM Eastern Daylight Time, 
jon.peterson@neustar.biz writes:


> SIP in general has no use for a concept of 'trunk groups';
> this is within the scope of telephony addressing, and belongs in the tel
> URL.
> 

[MAP] I'm further confused. If SIP has no use for the concept of 'trunk 
groups', why is this discussion going on?

I don't see that it is within the scope of "telephony addressing" either. I 
understand the tel:url to be intended to carry the telephone number. The 
current draft-antti-rfc2806bis-05.txt states that it is "for specifying the 
address of a terminal in the phone network". Isn't that what "tel" means? I 
suppose one could say that "tel" means "telephony" and that the header is 
intended to carry all the extraneous parameters associated with "telephony", 
but I din't think this was the accepted approach.

From a functional point of view, if a need to carry a trunk group identifier 
between entities really exists, it does not belong with the telephone number. 
I think we need to determine where such a thing "functionally" fits, not 
where it goes to keep the protocol pretty.

Mike Pierce
Artel