RE: [Sip] RE: request for iptell to review "url" IDs
"Cullen Jennings" <fluffy@cisco.com> Tue, 19 November 2002 19:27 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 OAA14012 for <sip-archive@odin.ietf.org>; Tue, 19 Nov 2002 14:27:47 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gAJJTxe08132 for sip-archive@odin.ietf.org; Tue, 19 Nov 2002 14:29:59 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJJLfv07685; Tue, 19 Nov 2002 14:21:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJJ7Ev06796 for <sip@optimus.ietf.org>; Tue, 19 Nov 2002 14:07:14 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13320; Tue, 19 Nov 2002 14:04:31 -0500 (EST)
Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32]) by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id gAJJ6tsA027156; Tue, 19 Nov 2002 11:06:55 -0800 (PST)
Received: from CJ650 (ssh-sjc-1.cisco.com [171.68.225.134]) by mira-sjc5-9.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA) with SMTP id CSD00064; Tue, 19 Nov 2002 11:07:33 -0800 (PST)
From: Cullen Jennings <fluffy@cisco.com>
To: iptel@lists.bell-labs.com
Cc: sip@ietf.org, sipping@ietf.org
Subject: RE: [Sip] RE: request for iptell to review "url" IDs
Date: Tue, 19 Nov 2002 11:08:07 -0800
Message-ID: <MFEJKLHKCMNFOPKPHMBPGEKACDAA.fluffy@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <5E42C1C85C5D064A947CF92FADE6D82E38B311@stntexch1.va.neustar.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Can we try to keep the H.323 URL discussion on the iptel@ietf.org list please. Thanks, Cullen > -----Original Message----- > From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Yu, > James > Sent: Monday, November 18, 2002 8:30 AM > To: 'Orit Levin' > Cc: mankin@psg.com; 'Scott Bradner'; iptel@lists.bell-labs.com; > sip@ietf.org; sipping@ietf.org > Subject: [Sip] RE: request for iptell to review "url" IDs > > > Orit, > > I'm not familiar with the ITU-T H.323 Annex O. I assume that > h323 url is an > IETF standard (e.g., an IETF registered url). So it is better to include > the "user" parameter and others in this h323 url I-D. For the tel url and > its existing and future extensions, a general statement about how > the info. > (no need to describe the exact info.) can appear in the user part when > "user" parameter is present would be sufficient. Otherwise, > when this h323 > url I-D becomes a RFC, another I-D needs to be submitted to include the > "user" parameter and others that not included in this I-D. > > James > > > -----Original Message----- > > From: Orit Levin [mailto:orit@radvision.com] > > Sent: Monday, November 18, 2002 10:23 AM > > To: 'Yu, James' > > Cc: mankin@psg.com; 'Scott Bradner'; iptel@lists.bell-labs.com; > > sip@ietf.org; sipping@ietf.org > > Subject: RE: request for iptell to review "url" IDs > > > > > > James, > > Actually the exact "user" parameter appears in the H.323 Annex O which > > defines this and other parameters to H.323 URL. > > > > This Annex O is pending approval by the ITU-T because the > > telephone-URI > > (which it is dependant upon) hasn't been finalized yet within > > the IETF. > > > > I will present at my ENUM presentation today this "standardization > > dependencies" graph... > > > > BR, > > Orit Levin > > Chief Architect > > RADVISION > > Phone: +1.201.6896330 > > Video: +1.201.6896430 > > > > > > > -----Original Message----- > > > From: Yu, James [mailto:james.yu@neustar.biz] > > > Sent: Sunday, November 17, 2002 9:01 PM > > > To: orit@radvision.com > > > Cc: mankin@psg.com; 'Scott Bradner'; iptel@lists.bell-labs.com; > > > sip@ietf.org; sipping@ietf.org > > > Subject: RE: request for iptell to review "url" IDs > > > > > > Orit, > > > > > > The h323 url I-D currently does not define a parameter similar to > > > "user=phone" in the sip url to indicate that a telephone > > number is in the > > > user part of the h323 url. Suggest to add that in your I-D > > and clarify in > > > the I-D that tel url information including its extensions > > can appear in > > > the > > > user part when a telephone number is present in the user part. > > > > > > James > > > > > > > -----Original Message----- > > > > From: Scott Bradner [mailto:sob@harvard.edu] > > > > Sent: Monday, October 28, 2002 9:25 AM > > > > To: iptel@lists.bell-labs.com; sip@ietf.org; sipping@ietf.org > > > > Cc: antti.vaha-sipila@nokia.com; james.yu@neustar.biz; > > mankin@psg.com; > > > > orit@radvision.com; schulzrinne@cs.columbia.edu > > > > Subject: request for iptell to review "url" IDs > > > > > > > > > > > > > > > > > > > > msg from the TSV ADs > > > > > > > > we would like the iptel WG to take on the following 3 IDs > > > > > > > > draft-antti-rfc2806bis-05.txt > > > > draft-yu-tel-url-06.txt > > > > draft-levin-iptel-h323-url-scheme-04.txt > > > > > > > > we would like the WG to review the 3 IDs to be sure that > > they do not > > > > conflict in the use of terminology or technology and to work > > > > with the ID > > > > authors to resolve any conflicts > > > > > > > > anyone with opinions about these IDs should join the iptel > > > > list and discuss > > > > the issues there > > > > > > > > we expect that this task will be a short term one and we > > can move to > > > > getting these IDs published > > > > > > > > Scott & Allison > > > > > > > _______________________________________________ > Sip mailing list https://www1.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol > Use sip-implementors@cs.columbia.edu for questions on current sip > Use sipping@ietf.org for new developments on the application of sip > _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] request for iptell to review "url" IDs Scott Bradner
- [Sip] RE: request for iptell to review "url" IDs Yu, James
- [Sip] RE: request for iptell to review "url" IDs Orit Levin
- [Sip] RE: request for iptell to review "url" IDs Yu, James
- RE: [Sip] RE: request for iptell to review "url" … Cullen Jennings