From iptel-bounces@ietf.org Sat Oct 07 09:39:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GWCNb-0000W6-7v; Sat, 07 Oct 2006 09:38:15 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GWCNa-0000W1-8L for iptel@ietf.org; Sat, 07 Oct 2006 09:38:14 -0400 Received: from ihemail1.lucent.com ([135.245.0.33]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GWCNW-0008Mz-Uw for iptel@ietf.org; Sat, 07 Oct 2006 09:38:14 -0400 Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70]) by ihemail1.lucent.com (8.13.6/IER-o) with ESMTP id k97Dc5Bi002844; Sat, 7 Oct 2006 08:38:05 -0500 (CDT) Received: from [135.244.1.177] (vkg.lra.lucent.com [135.244.1.177]) by ihmail.ih.lucent.com (8.11.7p1+Sun/EMS-1.5 sol2) id k97Dc5r17205; Sat, 7 Oct 2006 08:38:05 -0500 (CDT) Message-ID: <4527ADC0.1080905@lucent.com> Date: Sat, 07 Oct 2006 08:38:08 -0500 From: "Vijay K. Gurbani" Organization: Bell Labs Security Technology Research Group User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: iptel@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: Cullen Jennings , jon.peterson@neustar.biz Subject: [Iptel] draft-ietf-iptel-trunk-group-09 X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org All: Based on AD evaluation, I have submitted a revised version of trunk-group I-D. The changes in -09 include clarifications to existing text. I have submitted -09 to the I-D editor; until it becomes available, you can get both a diff-marked copy and -09 from the following links: http://www.iit.edu/~gurbvij/I-D/draft-ietf-iptel-trunk-group-09.txt http://www.iit.edu/~gurbvij/I-D/diff-08-09.txt Thanks. - vijay -- Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} Bell Laboratories, Lucent Technologies, Inc. 2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA) _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Mon Oct 09 15:52:47 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GX19d-0001XH-R0; Mon, 09 Oct 2006 15:51:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GX191-000061-6Z; Mon, 09 Oct 2006 15:50:35 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GX191-0005fC-3H; Mon, 09 Oct 2006 15:50:35 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GX18y-0004Sl-IK; Mon, 09 Oct 2006 15:50:34 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 72E1C2AC6C; Mon, 9 Oct 2006 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GX18U-0007Qq-5P; Mon, 09 Oct 2006 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 09 Oct 2006 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: iptel@ietf.org Subject: [Iptel] I-D ACTION:draft-ietf-iptel-trunk-group-09.txt X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Telephony Working Group of the IETF. Title : Representing trunk groups in tel/sip Uniform Resource Identifiers (URIs) Author(s) : C. Jennings, V. Gurbani Filename : draft-ietf-iptel-trunk-group-09.txt Pages : 18 Date : 2006-10-9 This document describes a standardized mechanism to convey trunk group parameters in sip and tel Uniform Resource Identifiers (URIs). An extension to the tel URI is defined for this purpose. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-trunk-group-09.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-iptel-trunk-group-09.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-iptel-trunk-group-09.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-10-9114052.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-trunk-group-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-trunk-group-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-9114052.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel --NextPart-- From iptel-bounces@ietf.org Wed Oct 11 09:54:12 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXeVa-000083-4d; Wed, 11 Oct 2006 09:52:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXeVZ-00007y-FH for iptel@ietf.org; Wed, 11 Oct 2006 09:52:29 -0400 Received: from tcmail23.telekom.de ([217.6.95.237]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXeVW-0003jE-2O for iptel@ietf.org; Wed, 11 Oct 2006 09:52:29 -0400 Received: from S4DE9JSAANO.ost.t-com.de (S4DE9JSAANO.ost.t-com.de [10.125.177.105]) by tcmail21.telekom.de with ESMTP for iptel@ietf.org; Wed, 11 Oct 2006 15:52:19 +0200 Received: from S4DE9JSAAMW.ost.t-com.de ([10.125.177.114]) by S4DE9JSAANO.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.1830); Wed, 11 Oct 2006 15:52:19 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Wed, 11 Oct 2006 15:52:19 +0200 Message-Id: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Transfer of the trunk group in the backward direction Thread-Index: AcbtPHbr8xGMidfQSWq0kdhdDzDRrg== From: "Alexeitsev, D" To: X-OriginalArrivalTime: 11 Oct 2006 13:52:19.0583 (UTC) FILETIME=[782020F0:01C6ED3C] X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Subject: [Iptel] Transfer of the trunk group in the backward direction X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org Hello altogether The draft draft-ietf-iptel-trunk-group-09 currently defines the way of transporting the originating (incoming) trunk group information in the forward direction. Was it discussed to define the transport of the destination (outgoing) trunk group information in the backward direction?=20 The use case could be the indication of the sized outgoing circuit (TG2-2) from the breakout gateway (GW2) to the originator of the call.=20 GW1 SIP Proxy GW2 | | | ---IAM--->| | | +---INVITE----->| | | +---INVITE------->| Trunk TG2-2 | | +------IAM------>=20 | |<---200 Ok-------+=20 |<---200 Ok-----+ | | | |=20 Could the outgoing trunk group information be reported back for example in the Contact header of the 200 response to the INVITE? Greetings, Denis Alexeitsev _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Fri Oct 13 03:58:47 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYHul-0008QT-BT; Fri, 13 Oct 2006 03:57:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYHuj-0008QK-V3 for iptel@ietf.org; Fri, 13 Oct 2006 03:57:06 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYHuj-0006En-Hq for iptel@ietf.org; Fri, 13 Oct 2006 03:57:05 -0400 Received: from stntsmtp01.cis.neustar.com (smartexch.neustar.com [10.31.13.96]) by ns1.neustar.com (Postfix) with ESMTP id 80C5D26E1B; Fri, 13 Oct 2006 07:57:05 +0000 (GMT) Received: from stntexch05.cis.neustar.com ([10.31.13.78]) by stntsmtp01.cis.neustar.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 13 Oct 2006 03:57:04 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 13 Oct 2006 03:57:03 -0400 Message-ID: <3F6C5AC720AE7744AD1F1573CFAE5CDE032FA96B@stntexch05.cis.neustar.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-yu-tel-dai-00.txt Thread-Index: AcbFNI2dKEvqgYapTh+mIaUsg+EsvgpZx+GA From: "Yu, James" To: "Jonathan Rosenberg" X-OriginalArrivalTime: 13 Oct 2006 07:57:04.0877 (UTC) FILETIME=[2C6599D0:01C6EE9D] X-Spam-Score: -0.9 (/) X-Scan-Signature: bb7a33d18683bf5063a44e640cf125f1 Cc: Cullen Jennings , iptel@ietf.org, "Peterson, Jon" Subject: [Iptel] draft-yu-tel-dai-00.txt X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1092156272==" Errors-To: iptel-bounces@ietf.org This is a multi-part message in MIME format. --===============1092156272== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6EE9D.2C1CB66F" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6EE9D.2C1CB66F Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Jonathan, The I-D below is intended for the iptel group. James > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Monday, October 09, 2006 3:50 PM > To: i-d-announce@ietf.org > Subject: I-D ACTION:draft-yu-tel-dai-00.txt >=20 > A New Internet-Draft is available from the on-line Internet-Drafts=20 > directories. >=20 >=20 > Title : DAI Parameter for the ^tel^ URI > Author(s) : J. Yu > Filename : draft-yu-tel-dai-00.txt > Pages : 15 > Date : 2006-10-9 >=20 > This document defines a _dai_ parameter for the ""tel"" Uniform > Resource Identifier (URI) to support the Dial Around Indicator > (DAI). The ""dai"" parameter is associated with the ""cic"" parameter > and indicates how the carrier identified in the ""cic"" parameter is > chosen to handle the call. >=20 >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-yu-tel-dai-00.txt >=20 > To remove yourself from the I-D Announcement list, send a message to=20 > i-d-announce-request@ietf.org with the word unsubscribe in the body of > the message. > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. >=20 > Internet-Drafts are also available by anonymous FTP. Login with the=20 > username "anonymous" and a password of your e-mail address. After=20 > logging in, type "cd internet-drafts" and then "get=20 > draft-yu-tel-dai-00.txt". >=20 > A list of Internet-Drafts directories can be found in=20 > http://www.ietf.org/shadow.html or=20 > ftp://ftp.ietf.org/ietf/1shadow-sites.txt >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-yu-tel-dai-00.txt". =20 ------_=_NextPart_001_01C6EE9D.2C1CB66F Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Jonathan,

The I-D below is = intended for the iptel group.

James<= /span>

> -----Original Message-----

> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org<= /a>]

> Sent: Monday, = October 09, 2006 3:50 PM

> To: i-d-announce@ietf.org

> Subject: I-D ACTION:draft-yu-tel-dai-00.txt

> =

> A New = Internet-Draft is available from the on-line Internet-Drafts

> = directories.

> =

> =

> =     Title       : DAI Parameter for the ^tel^ URI

> =     Author(s)   : J. Yu

> =     Filename    : draft-yu-tel-dai-00.txt

> =     Pages       : 15

> =     Date        : 2006-10-9

> =

>    This document defines a _dai_ parameter for the ""tel"" = Uniform

>    Resource Identifier (URI) to support the Dial Around = Indicator

>    (DAI).  The ""dai"" parameter is associated = with the ""cic"" parameter

>    and indicates how the carrier identified in the ""cic"" parameter is

>    chosen to handle the call.

> =

> =

> A URL for this Internet-Draft is:

> http= ://www.ietf.org/internet-drafts/draft-yu-tel-dai-00.txt

> =

> To remove = yourself from the I-D Announcement list, send a message to =

> i-d-announce-request@ietf.org with the word unsubscribe in the body of =

> the = message.

> You can also = visit https://www1= .ietf.org/mailman/listinfo/I-D-announce

> to change your subscription settings.

> =

> = Internet-Drafts are also available by anonymous FTP. Login with the =

> username "anonymous" and a password of your e-mail address. After =

> logging in, = type "cd internet-drafts" and then "get =

> draft-yu-tel-dai-00.txt".

> =

> A list of Internet-Drafts directories can be found in =

> http://www.ietf.org/shadow.html<= /a> or

> ftp://ftp.ietf.org/iet= f/1shadow-sites.txt

> =

> = Internet-Drafts can also be obtained by e-mail.

> =

> Send a message = to:

> =     mailserv@ietf.org.

> In the body = type:

> =     "FILE /internet-drafts/draft-yu-tel-dai-00.txt".<= /p>



 

------_=_NextPart_001_01C6EE9D.2C1CB66F-- --===============1092156272== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel --===============1092156272==-- From iptel-bounces@ietf.org Wed Oct 18 17:44:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaJBq-0002do-NR; Wed, 18 Oct 2006 17:43:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaJBn-0002c5-Oi; Wed, 18 Oct 2006 17:43:03 -0400 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaJBl-00087x-QH; Wed, 18 Oct 2006 17:43:03 -0400 Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 18 Oct 2006 14:43:01 -0700 Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9ILh1el004662; Wed, 18 Oct 2006 17:43:01 -0400 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k9ILh1YJ028785; Wed, 18 Oct 2006 17:43:01 -0400 (EDT) Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 17:43:01 -0400 Received: from [161.44.55.215] ([161.44.55.215]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 17:43:01 -0400 Message-ID: <45369FE5.8060106@cisco.com> Date: Wed, 18 Oct 2006 17:43:01 -0400 From: Jonathan Rosenberg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en-us, en MIME-Version: 1.0 To: IETF SIP List , IETF Sipping List , enum@ietf.org, list iptel Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Oct 2006 21:43:01.0078 (UTC) FILETIME=[62428760:01C6F2FE] DKIM-Signature: a=rsa-sha1; q=dns; l=1111; t=1161207781; x=1162071781; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:Jonathan=20Rosenberg=20 |Subject:New=20I-D=20on=20usage=20of=20phone=20numbers=20in=20SIP=20[DO=20NOT=20R EPLY!] |To:IETF=20SIP=20List=20, =20IETF=20Sipping=20List=20, =0A=20=20=20=20=20=20=20=20enum@ietf.org, =20list=20iptel=20; X=v=3Dcisco.com=3B=20h=3Dx2VOK/URLoBX55duy//nU8RGxVg=3D; b=da0NjqSIGQtGuiwGOXjONOa6aUAwrwZSmZOqSCxt3+Vss4JjLFj4CTOARm5Va36WBUULCSwv Du9ADHrxWyf1Zx1TUlM2QENvD+jUexS0AgOOIjV61V7+3zMeYe5nKs/4; Authentication-Results: rtp-dkim-2.cisco.com; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: Subject: [Iptel] New I-D on usage of phone numbers in SIP [DO NOT REPLY!] X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org PLEASE DO NOT REPLY TO THIS POST. My apologies for the cross post. I have submitted the following I-D: http://www.ietf.org/internet-drafts/draft-rosenberg-rai-phone-names-numbers-00.txt I gave it a -rai moniker since it touches on issues central to at least four working groups. If you are interested in discussion this document, please let us do so only on sipping@ietf.org. The document proposes a framework and architecture for the usage of phone numbers with SIP. It tries to answer questions like the difference between a tel URI and SIP URI with user=phone, when to use each, what the meaning of concepts like LNP and freephone are in a pure-SIP world, the architectural role of ENUM, and impacts on PSTN interoperability, and so on. Thanks, Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Cisco Fellow Parsippany, NJ 07054-2711 Cisco Systems jdrosen@cisco.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.cisco.com _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Thu Oct 19 15:25:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GadUg-0005SD-2b; Thu, 19 Oct 2006 15:23:54 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GadUe-0005Na-6P; Thu, 19 Oct 2006 15:23:52 -0400 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GadUc-0003xD-RP; Thu, 19 Oct 2006 15:23:52 -0400 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 19 Oct 2006 12:23:51 -0700 Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9JJNotj004329; Thu, 19 Oct 2006 15:23:50 -0400 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k9JJNlYP028366; Thu, 19 Oct 2006 15:23:50 -0400 (EDT) Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 15:23:49 -0400 Received: from [161.44.55.227] ([161.44.55.227]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 15:23:48 -0400 Message-ID: <4537D0C4.5020105@cisco.com> Date: Thu, 19 Oct 2006 15:23:48 -0400 From: Jonathan Rosenberg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en-us, en MIME-Version: 1.0 To: avt@ietf.org, ecrit@ietf.org, enum@ietf.org, geopriv@ietf.org, ieprep@ietf.org, iptel@ietf.org, mmusic@ietf.org, sigtran@ietf.org, simple@ietf.org, sip@ietf.org, sipping@ietf.org, speechsc@ietf.org, speermint@ietf.org, xcon@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Oct 2006 19:23:48.0914 (UTC) FILETIME=[1A653120:01C6F3B4] DKIM-Signature: a=rsa-sha1; q=dns; l=1561; t=1161285830; x=1162149830; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:Jonathan=20Rosenberg=20 |Subject:ICE=20Tutorial=20during=20IETF=2067!=20[DO=20NOT=20REPLY] |To:avt@ietf.org, =20ecrit@ietf.org, =20enum@ietf.org, =20geopriv@ietf.org, =0A= 20=20=20=20=20=20=20=20ieprep@ietf.org, =20iptel@ietf.org, =20mmusic@ietf.org , =20sigtran@ietf.org, =0A=20=20=20=20=20=20=20=20simple@ietf.org, =20sip@ietf .org, =20sipping@ietf.org, =20speechsc@ietf.org, =0A=20=20=20=20=20=20=20=20sp eermint@ietf.org,=20xcon@ietf.org; X=v=3Dcisco.com=3B=20h=3DIVH9amnYVaV4pfzKKjl/WmQt0Lg=3D; b=KrOzK3fR06ATri/gT7YJZroJcol7TSpMYe5BZE33gFcC/1PSyZC+oxmWK+oIC+fJQIbVoFL+ nf48uscnxvpV77HTZ0nnFeZmJMX4MuuOimxi0aG7+C8ixmvrHWsG0fmT; Authentication-Results: rtp-dkim-1.cisco.com; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 1.2 (+) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: Subject: [Iptel] ICE Tutorial during IETF 67! [DO NOT REPLY] X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org (Apologies to multiple recipients) (DO NOT REPLY) WHAT: Tutorial on Interactive Connectivity Establishment (ICE) (http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-11.txt) WHEN: Tuesday, November 7 1130-1300 (lunch logistics are in progress and will be announced ASAP) WHERE: Grande Ballroom A WHO: Anyone with an interest in RAI work that would like to learn more about ICE. WHY: ICE is one of the 'core' SIP specifications (according to the SIP hitchhikers guide) and seeing some good adoption. It's the IETF tool for NAT traversal for SIP-based media. However, it's a complex specification. The tutorial will assume only basic familiarity with SIP, SDP and NAT, and explain the rest. Participants will emerge with a high level understanding of the operation of ICE. The tutorial will be based on the pending -12 version. RSVP: Please send a note to me with the Subject line "ice-is-nice" (mailto:jdrosen@cisco.com?Subject=ice-is-nice) so I can get a count of the number of participants for lunch purposes. !DO NOT REPLY TO THIS NOTE! -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Cisco Fellow Parsippany, NJ 07054-2711 Cisco Systems jdrosen@cisco.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.cisco.com _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Thu Oct 19 15:32:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gadcj-0000fM-GN; Thu, 19 Oct 2006 15:32:13 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gadci-0000f5-KH for iptel@ietf.org; Thu, 19 Oct 2006 15:32:12 -0400 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gadch-0005JI-Aq for iptel@ietf.org; Thu, 19 Oct 2006 15:32:12 -0400 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 19 Oct 2006 15:32:11 -0400 Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9JJWB28007245 for ; Thu, 19 Oct 2006 15:32:11 -0400 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k9JJW7DO007341 for ; Thu, 19 Oct 2006 15:32:11 -0400 (EDT) Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 15:32:10 -0400 Received: from [161.44.55.227] ([161.44.55.227]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 15:32:10 -0400 Message-ID: <4537D2BA.6060803@cisco.com> Date: Thu, 19 Oct 2006 15:32:10 -0400 From: Jonathan Rosenberg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en-us, en MIME-Version: 1.0 To: iptel@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Oct 2006 19:32:10.0531 (UTC) FILETIME=[4561DF30:01C6F3B5] DKIM-Signature: a=rsa-sha1; q=dns; l=1561; t=1161286331; x=1162150331; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:Jonathan=20Rosenberg=20 |Subject:ICE=20Tutorial=20during=20IETF=2067!=20[DO=20NOT=20REPLY] |To:iptel@ietf.org; X=v=3Dcisco.com=3B=20h=3DIVH9amnYVaV4pfzKKjl/WmQt0Lg=3D; b=DzpxOUrN9HO/AT3Qw1cVrJrIKnlmfFkp93on/Gh+IqrBctSAn2XadhLYvdeNFlunyQTXOyC6 oIxPOsWNriZg3qXSjeZxNvLtCk/p8rA9Jzstvx2N8X8B2vNtxTF8cD+C; Authentication-Results: rtp-dkim-1.cisco.com; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Subject: [Iptel] ICE Tutorial during IETF 67! [DO NOT REPLY] X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org (Apologies to multiple recipients) (DO NOT REPLY) WHAT: Tutorial on Interactive Connectivity Establishment (ICE) (http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-11.txt) WHEN: Tuesday, November 7 1130-1300 (lunch logistics are in progress and will be announced ASAP) WHERE: Grande Ballroom A WHO: Anyone with an interest in RAI work that would like to learn more about ICE. WHY: ICE is one of the 'core' SIP specifications (according to the SIP hitchhikers guide) and seeing some good adoption. It's the IETF tool for NAT traversal for SIP-based media. However, it's a complex specification. The tutorial will assume only basic familiarity with SIP, SDP and NAT, and explain the rest. Participants will emerge with a high level understanding of the operation of ICE. The tutorial will be based on the pending -12 version. RSVP: Please send a note to me with the Subject line "ice-is-nice" (mailto:jdrosen@cisco.com?Subject=ice-is-nice) so I can get a count of the number of participants for lunch purposes. !DO NOT REPLY TO THIS NOTE! -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Cisco Fellow Parsippany, NJ 07054-2711 Cisco Systems jdrosen@cisco.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.cisco.com _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Fri Oct 20 17:24:36 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gb1qQ-0003tW-Dr; Fri, 20 Oct 2006 17:23:58 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gb1qP-0003tR-4s for iptel@ietf.org; Fri, 20 Oct 2006 17:23:57 -0400 Received: from cdx28.winwebhosting.com ([70.85.255.82]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gb1qN-0005nv-TY for iptel@ietf.org; Fri, 20 Oct 2006 17:23:57 -0400 Received: from neustargw.va.neustar.com ([209.173.53.233] helo=BROSENLT40xp) by cdx28.winwebhosting.com with esmtpa (Exim 4.52) id 1Gb1qC-0005o0-1s for iptel@ietf.org; Fri, 20 Oct 2006 16:23:45 -0500 From: "Brian Rosen" To: Date: Fri, 20 Oct 2006 17:23:48 -0400 Message-ID: <017201c6f48e$0ad480f0$640fa8c0@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Thread-Index: Acb0jXuZTcpqMVNmQES8Mge39cWZBAAAHhpg X-PopBeforeSMTPSenders: br@brianrosen.net,brosen X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cdx28.winwebhosting.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - brianrosen.net X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: [Iptel] draft-rosen-iptel-dialstring-05 X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org I have submitted an update to -dialstring. Until it appears in the archives, you may pick up a copy from: http://www.brianrosen.net/internet-drafts/draft-rosen-iptel-dialstring-05.tx t an .html is also available. The changes in this version are: 1. After lengthy discussion, I changed the position of the phone-context parameter to match what a tel uri with a phone-context parameter looks like when converted to a sip URI. This means it goes before the '@' 2. I created an ABNF description of this, defining a new "dialstring" alternative for 'user-info' in a sip URI. 3. I expanded the definition of the dialstring syntax to include "*" and "#" (as well as E and F) 4. I added a SHOULD NOT use a dialstring as an AoR in a Register Hopefully, this resolves all issues, and the draft is ready for the IESG to progress Brian _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From akstccmcsmartmnsdgs@cmcsmart.com Sat Oct 21 09:18:40 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbGkK-0005i8-1F; Sat, 21 Oct 2006 09:18:40 -0400 Received: from chello082119127053.chello.sk ([82.119.127.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GbGkD-0004VF-O5; Sat, 21 Oct 2006 09:18:40 -0400 Received: from 81.23.235.184 (HELO pool-mx.host-my-mail.com) by lists.ietf.org with esmtp (SM123PP47 HAL0J) id QOS389-7MN3T8-5N for iporpr-archive@lists.ietf.org; Sat, 21 Nov 2006 13:18:51 -0060 Date: Sat, 21 Nov 2006 13:18:51 -0060 From: "Dorthy Anthony" X-Mailer: The Bat! (v3.0.1.33) UNREG / CD5BF9353B3B7091 X-Priority: 3 (Normal) Message-ID: <543631793.51363873415769@thebat.net> To: iporpr-archive@lists.ietf.org Subject: volume boomed in day, see it triple MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------5DA14DA1B09F4DA9" X-Spam: Not detected X-Spam-Score: 4.3 (++++) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 ------------5DA14DA1B09F4DA9 Content-Type: multipart/alternative; boundary="----------4D3C098FB01B01B0" ------------4D3C098FB01B01B0 Content-Type: text/plain; charset=windows-1250 Content-Transfer-Encoding: 7bit SORD - Add it NOW!Major PR campaign starting next week on SORD - GET it early!WATCH SORD trde on monday - act Now.always bordering on the uncivil, and i never spoke to you without rather wishing to give you pain thana similar occasion, five-and-twenty years ago."i leave it to yourself to determine," said mr. bennet.elizabeth was sitting with her mother and sisters, reflecting on what she had heard, and doubtingbetween him and darcy there was a very steady friendship, in spite of great opposition of"but you-how are you?" cried elizabeth. "you look pale. how much you must have goneadded something to their knowledge of the officers' names and connections. their lodgings were notcontempt seemed abundantly increasing with the length of his second speech, and at the end of it he"not yet," replied jane. "but now that my dear uncle is come, i hope everything will be well."be; for the young man wanted only regimentals to make him completely charming. his appearance was"yes; where else can they be so well concealed?"and congratulated both him and herself in warm terms on the happy prospect or their nearerdo not make allowance enough for difference of situation and temper. consider mr. collins'sY>Y>Y>Y>Y>Y>Y>Y>Y>Y>Y>Y>Y>Y> ------------4D3C098FB01B01B0 Content-Type: text/html; charset=windows-1250 Content-Transfer-Encoding: 7bit high volume
SORD - Add it NOW!
Major PR campaign starting next week on SORD - GET it early!
WATCH SORD trde on monday - act Now.

always bordering on the uncivil, and i never spoke to you without rather wishing to give you pain thana similar occasion, five-and-twenty years ago.
"i leave it to yourself to determine," said mr. bennet.elizabeth was sitting with her mother and sisters, reflecting on what she had heard, and doubting
between him and darcy there was a very steady friendship, in spite of great opposition of
"but you-how are you?" cried elizabeth. "you look pale. how much you must have goneadded something to their knowledge of the officers' names and connections. their lodgings were not
contempt seemed abundantly increasing with the length of his second speech, and at the end of it he
"not yet," replied jane. "but now that my dear uncle is come, i hope everything will be well."
be; for the young man wanted only regimentals to make him completely charming. his appearance was"yes; where else can they be so well concealed?"
and congratulated both him and herself in warm terms on the happy prospect or their nearerdo not make allowance enough for difference of situation and temper. consider mr. collins's
------------4D3C098FB01B01B0-- ------------5DA14DA1B09F4DA9 Content-Type: image/gif; name="mjmk.gif" Content-ID: Content-Transfer-Encoding: base64 R0lGODdhAQABAKIAAP////8AAMwzzGbMADOZmQAAAAAAAAAAACwAAAAAAQABAAADAggJADs= ------------5DA14DA1B09F4DA9-- From iptel-bounces@ietf.org Sat Oct 21 10:55:14 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbIEx-0005m7-IR; Sat, 21 Oct 2006 10:54:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbI9m-0004TS-DJ for iptel@ietf.org; Sat, 21 Oct 2006 10:49:02 -0400 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GbI0h-0002eD-QI for iptel@ietf.org; Sat, 21 Oct 2006 10:39:44 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: [Iptel] draft-rosen-iptel-dialstring-05 Date: Sat, 21 Oct 2006 16:38:53 +0200 Message-ID: <32755D354E6B65498C3BD9FD496C7D462C4BB6@oefeg-s04.oefeg.loc> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Iptel] draft-rosen-iptel-dialstring-05 Thread-Index: Acb0jXuZTcpqMVNmQES8Mge39cWZBAAAHhpgACO90gk= References: <017201c6f48e$0ad480f0$640fa8c0@cis.neustar.com> From: "Stastny Richard" To: "Brian Rosen" , X-Spam-Score: 0.0 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 Cc: X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org >Hopefully, this resolves all issues, and the draft is ready for the = IESG to >progress =20 I hope too ;-) Congratulations =20 There is only one additional item left: =20 A proxy server or Back to Back User Agent (B2BUA) [RFC3261] which is authoritative for the context may translate the dial string to a telephone number or service invocation URI. If such a translation is performed, the proxy server MUST change the URI parameter value from "user=3Ddialstring" to "user=3Dphone". This translation MUST occur = prior to the call leaving the domain of the context. =20 Considering the explanation of user=3Dphone in draft-rosenberg-rai-phones-names-numbers-00: =20 "RFC 3261 is clear that user=3Dphone is used when the user part is formatted as a phone number. However, this document argues that when used in a SIP URI there is an additional, deeper meaning. The domain part of the SIP URI serves two important purposes. First, it specifies the host to which the request should be delivered. However, this is secondary to its more important meaning - it is an identifier for the owner of the namespace from which the user part is selected. Consequently, when the user part is a global phone number, it is asserting ownership of that global phone number by that domain. Thus, the SIP URI form with user=3Dphone MUST only be used when the entity constructing the URI has knowledge from an authoritative source that the domain in the URI is the owner of the phone number in the left hand side. Such knowledge comes from databases such as ENUM or PSTN-based local number portability tables, in additional to localized knowledge within the domain that knows definitively that it owns the number." =20 Ok, so we have to refomulate the para, e.g. =20 A proxy server or Back to Back User Agent (B2BUA) [RFC3261] which is authoritative for the context may translate the dial string to a telephone number or service invocation URI. The telephone number MAY be expressed as a global or local tel: URI or as a sip: or sips: = URI. =20 This translation MUST occur prior to the call leaving the domain of the context. =20 best regards Richard ________________________________ Von: Brian Rosen [mailto:br@brianrosen.net] Gesendet: Fr 20.10.2006 23:23 An: iptel@ietf.org Betreff: [Iptel] draft-rosen-iptel-dialstring-05 I have submitted an update to -dialstring. Until it appears in the archives, you may pick up a copy from: http://www.brianrosen.net/internet-drafts/draft-rosen-iptel-dialstring-05= .tx t an .html is also available. The changes in this version are: 1. After lengthy discussion, I changed the position of the phone-context parameter to match what a tel uri with a phone-context parameter looks = like when converted to a sip URI. This means it goes before the '@' 2. I created an ABNF description of this, defining a new "dialstring" alternative for 'user-info' in a sip URI. 3. I expanded the definition of the dialstring syntax to include "*" and = "#" (as well as E and F) 4. I added a SHOULD NOT use a dialstring as an AoR in a Register Hopefully, this resolves all issues, and the draft is ready for the IESG = to progress Brian _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Sun Oct 22 20:15:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbnSb-0007MN-Ku; Sun, 22 Oct 2006 20:14:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbnSZ-0007Lq-OG for iptel@ietf.org; Sun, 22 Oct 2006 20:14:31 -0400 Received: from zcars04f.nortel.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GbnSX-00058N-T4 for iptel@ietf.org; Sun, 22 Oct 2006 20:14:31 -0400 Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nort...s0.corp.nortel.com [47.129.230.89]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id k9N0EOI19244; Sun, 22 Oct 2006 20:14:24 -0400 (EDT) Received: from [127.0.0.1] ([47.130.24.140] RDNS failed) by zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 22 Oct 2006 20:14:24 -0400 Message-ID: <453C095B.7070806@nortel.com> Date: Sun, 22 Oct 2006 20:14:19 -0400 From: "Tom-PT Taylor" User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Stastny Richard Subject: Re: [Iptel] draft-rosen-iptel-dialstring-05 References: <017201c6f48e$0ad480f0$640fa8c0@cis.neustar.com> <32755D354E6B65498C3BD9FD496C7D462C4BB6@oefeg-s04.oefeg.loc> In-Reply-To: <32755D354E6B65498C3BD9FD496C7D462C4BB6@oefeg-s04.oefeg.loc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Oct 2006 00:14:24.0517 (UTC) FILETIME=[32105350:01C6F638] X-Spam-Score: 0.0 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db Cc: iptel@ietf.org X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org That's if you accept Jonathan's argument. I'm not sure I do. As an example, consider a 3GPP end point shipping a call to the PSTN to its home network, because that it where it has to go to get service. Stastny Richard wrote: >> Hopefully, this resolves all issues, and the draft is ready for the IESG to >> progress > > I hope too ;-) > Congratulations > > There is only one additional item left: > > A proxy server or Back to Back User Agent (B2BUA) [RFC3261] which is > authoritative for the context may translate the dial string to a > telephone number or service invocation URI. If such a translation is > performed, the proxy server MUST change the URI parameter value from > "user=dialstring" to "user=phone". This translation MUST occur prior > to the call leaving the domain of the context. > > Considering the explanation of user=phone in > draft-rosenberg-rai-phones-names-numbers-00: > > "RFC 3261 is clear that user=phone is used when the user part is > formatted as a phone number. However, this document argues that when > used in a SIP URI there is an additional, deeper meaning. The domain > part of the SIP URI serves two important purposes. First, it > specifies the host to which the request should be delivered. > However, this is secondary to its more important meaning - it is an > identifier for the owner of the namespace from which the user part is > selected. Consequently, when the user part is a global phone number, > it is asserting ownership of that global phone number by that domain. > Thus, the SIP URI form with user=phone MUST only be used when the > entity constructing the URI has knowledge from an authoritative > source that the domain in the URI is the owner of the phone number in > the left hand side. Such knowledge comes from databases such as ENUM > or PSTN-based local number portability tables, in additional to > localized knowledge within the domain that knows definitively that it > owns the number." > > Ok, so we have to refomulate the para, e.g. > > A proxy server or Back to Back User Agent (B2BUA) [RFC3261] which is > authoritative for the context may translate the dial string to a > telephone number or service invocation URI. The telephone number > MAY be expressed as a global or local tel: URI or as a sip: or sips: URI. > This translation MUST occur prior > to the call leaving the domain of the context. > > best regards > Richard > > ________________________________ > > Von: Brian Rosen [mailto:br@brianrosen.net] > Gesendet: Fr 20.10.2006 23:23 > An: iptel@ietf.org > Betreff: [Iptel] draft-rosen-iptel-dialstring-05 > > > > I have submitted an update to -dialstring. Until it appears in the > archives, you may pick up a copy from: > http://www.brianrosen.net/internet-drafts/draft-rosen-iptel-dialstring-05.tx > t > > an .html is also available. > > The changes in this version are: > 1. After lengthy discussion, I changed the position of the phone-context > parameter to match what a tel uri with a phone-context parameter looks like > when converted to a sip URI. This means it goes before the '@' > 2. I created an ABNF description of this, defining a new "dialstring" > alternative for 'user-info' in a sip URI. > 3. I expanded the definition of the dialstring syntax to include "*" and "#" > (as well as E and F) > 4. I added a SHOULD NOT use a dialstring as an AoR in a Register > > Hopefully, this resolves all issues, and the draft is ready for the IESG to > progress > > Brian > > > _______________________________________________ > Iptel mailing list > Iptel@ietf.org > https://www1.ietf.org/mailman/listinfo/iptel > > > > _______________________________________________ > Iptel mailing list > Iptel@ietf.org > https://www1.ietf.org/mailman/listinfo/iptel > _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Mon Oct 23 04:18:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gbv0U-00038k-SO; Mon, 23 Oct 2006 04:18:02 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gbv0S-000377-NZ for iptel@ietf.org; Mon, 23 Oct 2006 04:18:00 -0400 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gbv0P-00061P-QM for iptel@ietf.org; Mon, 23 Oct 2006 04:18:00 -0400 Subject: RE: [Iptel] draft-rosen-iptel-dialstring-05 Date: Mon, 23 Oct 2006 10:17:01 +0200 Message-ID: <32755D354E6B65498C3BD9FD496C7D463C51F1@oefeg-s04.oefeg.loc> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable In-Reply-To: <453C095B.7070806@nortel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-class: urn:content-classes:message Thread-Topic: [Iptel] draft-rosen-iptel-dialstring-05 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 thread-index: Acb2OBrcRrBwdLfxQFa5Zcn7bhxV0QAQbL9Q From: "Stastny Richard" To: "Tom-PT Taylor" X-Spam-Score: 0.0 (/) X-Scan-Signature: d16ce744298aacf98517bc7c108bd198 Cc: iptel@ietf.org X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org Tom wrote:=20 > That's if you accept Jonathan's argument.=20 Yes, or at least IMO the various formats of sip URIs containing phone numbers have to be clarified before this para can be finished > I'm not sure I do. As an > example, consider a 3GPP end point shipping a call to the PSTN to its > home network, because that it where it has to go to get service. Good point. 3GPP is using ENUM to resolve the translation from E.164 to sip URIs There has to be a clear definition what kind of URIs you enter in the different cases: If the destination network is reachable via IP Interconnect, one must enter a sip:+xxx@homenetwork.com;user=3Dphone and SPEERMINT is resolving the routing on IP If the destination is only reachable via the PSTN, one must enter a tel: URI (it may enter in addition eventually a sip URI as above, but without user=3Dphone?) I do not see any other case Regards Richard >=20 > Stastny Richard wrote: > >> Hopefully, this resolves all issues, and the draft is ready for the > IESG to > >> progress > > > > I hope too ;-) > > Congratulations > > > > There is only one additional item left: > > > > A proxy server or Back to Back User Agent (B2BUA) [RFC3261] which is > > authoritative for the context may translate the dial string to a > > telephone number or service invocation URI. If such a translation is > > performed, the proxy server MUST change the URI parameter value from > > "user=3Ddialstring" to "user=3Dphone". This translation MUST = occur prior > > to the call leaving the domain of the context. > > > > Considering the explanation of user=3Dphone in > > draft-rosenberg-rai-phones-names-numbers-00: > > > > "RFC 3261 is clear that user=3Dphone is used when the user part is > > formatted as a phone number. However, this document argues that when > > used in a SIP URI there is an additional, deeper meaning. The domain > > part of the SIP URI serves two important purposes. First, it > > specifies the host to which the request should be delivered. > > However, this is secondary to its more important meaning - it is an > > identifier for the owner of the namespace from which the user part is > > selected. Consequently, when the user part is a global phone number, > > it is asserting ownership of that global phone number by that domain. > > Thus, the SIP URI form with user=3Dphone MUST only be used when = the > > entity constructing the URI has knowledge from an authoritative > > source that the domain in the URI is the owner of the phone number in > > the left hand side. Such knowledge comes from databases such as ENUM > > or PSTN-based local number portability tables, in additional to > > localized knowledge within the domain that knows definitively that it > > owns the number." > > > > Ok, so we have to refomulate the para, e.g. > > > > A proxy server or Back to Back User Agent (B2BUA) [RFC3261] which is > > authoritative for the context may translate the dial string to a > > telephone number or service invocation URI. The telephone number > > MAY be expressed as a global or local tel: URI or as a sip: or sips: > URI. > > This translation MUST occur prior > > to the call leaving the domain of the context. > > > > best regards > > Richard > > > > ________________________________ > > > > Von: Brian Rosen [mailto:br@brianrosen.net] > > Gesendet: Fr 20.10.2006 23:23 > > An: iptel@ietf.org > > Betreff: [Iptel] draft-rosen-iptel-dialstring-05 > > > > > > > > I have submitted an update to -dialstring. Until it appears in the > > archives, you may pick up a copy from: > > http://www.brianrosen.net/internet-drafts/draft-rosen-iptel-dialstring- > 05.tx > > t > > > > an .html is also available. > > > > The changes in this version are: > > 1. After lengthy discussion, I changed the position of the phone-context > > parameter to match what a tel uri with a phone-context parameter looks > like > > when converted to a sip URI. This means it goes before the '@' > > 2. I created an ABNF description of this, defining a new "dialstring" > > alternative for 'user-info' in a sip URI. > > 3. I expanded the definition of the dialstring syntax to include "*" and > "#" > > (as well as E and F) > > 4. I added a SHOULD NOT use a dialstring as an AoR in a Register > > > > Hopefully, this resolves all issues, and the draft is ready for the IESG > to > > progress > > > > Brian > > > > > > _______________________________________________ > > Iptel mailing list > > Iptel@ietf.org > > https://www1.ietf.org/mailman/listinfo/iptel > > > > > > > > _______________________________________________ > > Iptel mailing list > > Iptel@ietf.org > > https://www1.ietf.org/mailman/listinfo/iptel > > _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Mon Oct 23 09:26:14 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gbzo5-0006NE-Pw; Mon, 23 Oct 2006 09:25:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gbzo4-0006Ib-Tu for iptel@ietf.org; Mon, 23 Oct 2006 09:25:32 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gbznv-0007rl-Ag for iptel@ietf.org; Mon, 23 Oct 2006 09:25:32 -0400 Received: from sj-dkim-7.cisco.com ([171.68.10.88]) by sj-iport-5.cisco.com with ESMTP; 23 Oct 2006 06:25:23 -0700 Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-7.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9NDPMAB007230; Mon, 23 Oct 2006 06:25:22 -0700 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k9NDOYP5026951; Mon, 23 Oct 2006 06:25:21 -0700 (PDT) Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 09:25:09 -0400 Received: from [161.44.79.182] ([161.44.79.182]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 09:25:08 -0400 Message-ID: <453CC2B4.90104@cisco.com> Date: Mon, 23 Oct 2006 09:25:08 -0400 From: Paul Kyzivat User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Stastny Richard Subject: Re: [Iptel] draft-rosen-iptel-dialstring-05 References: <017201c6f48e$0ad480f0$640fa8c0@cis.neustar.com> <32755D354E6B65498C3BD9FD496C7D462C4BB6@oefeg-s04.oefeg.loc> In-Reply-To: <32755D354E6B65498C3BD9FD496C7D462C4BB6@oefeg-s04.oefeg.loc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Oct 2006 13:25:08.0771 (UTC) FILETIME=[A90AF730:01C6F6A6] DKIM-Signature: a=rsa-sha1; q=dns; l=2632; t=1161609922; x=1162473922; c=relaxed/simple; s=sjdkim7002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:Paul=20Kyzivat=20 |Subject:Re=3A=20[Iptel]=20draft-rosen-iptel-dialstring-05; X=v=3Dcisco.com=3B=20h=3D+A9bAihhVMvx1gjeQB8Zzh8GGbg=3D; b=nKKfnJ0EfbhoSOLDfPEqnVC3xfNNvK7ry1Yh4cNJEfORAyFRNoUfx/2COstJYOkovoU3OSh+ KYfUOkE7aeLSo83713wro8x5xhoyK3vvVsmGCNd4aZz9pUGbLV4eo33g; Authentication-Results: sj-dkim-7.cisco.com; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Cc: iptel@ietf.org X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org Stastny Richard wrote: > There is only one additional item left: > > A proxy server or Back to Back User Agent (B2BUA) [RFC3261] which is > authoritative for the context may translate the dial string to a > telephone number or service invocation URI. If such a translation is > performed, the proxy server MUST change the URI parameter value from > "user=dialstring" to "user=phone". This translation MUST occur prior > to the call leaving the domain of the context. I question the last MUST, though I agree with SHOULD here. There are no rules regarding which domains understand a particular context. (The context is just a name. Anybody *could* understand it.) Its always possible that once leaving server that happens to understand the context, it may eventually reach another domain that also understands it. Of course this is risky - there is also a very good chance that it will get to someplace that doesn't understand it, and that must give up for lack of options. A case I have in mind for this is a REFER request that contains a Refer-To containing a user=dialstring URI. (This is probably a bad idea, but its possible it could arise somehow.) For example: REFER sip:bob@sp2.com To: sip:bob@sp2.com From: sip:alice@sp1.com Refer-To: sip:1234;phone-context=atlanta.sp1.com@sp1.com ;user=dialstring Route: sip:proxy.sp1.com There are at least three potential times when this dial string could be translated: - when the REFER is first being processed by proxy.sp1.com for the outgoing request from alice. It may well understand the context atlanta.sp1.com. But This requires it to look into all sorts of headers, not just the R-URI. - when the resulting INVITE, sent by Bob, reaches a proxy in Bob's domain (proxy.sp2.com). At this time the dialstring will be in the R-URI. But at this time the domain of the R-URI does not match that of the proxy, so it shouldn't take place then. - when the resulting INVITE reaches some proxy in the sp1.com domain, as a result of 3263 processing of the dialstring uri. This may be proxy.sp1.com again, or it might be some other proxy serving sp1. Ideally, sp1 will have set things up so that all its proxies know all its contexts, or else it could potentially have routing rules based on the context, that route the request to a proxy that does understand those rules and can translate the dialstring. There are a variety of options here, some better, some worse. I don't think it is necessary to get overly normative about when this gets done. Paul _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Mon Oct 23 10:19:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gc0eT-0004iO-8G; Mon, 23 Oct 2006 10:19:41 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gc0eS-0004iA-Hg for iptel@ietf.org; Mon, 23 Oct 2006 10:19:40 -0400 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gc0eP-00042H-66 for iptel@ietf.org; Mon, 23 Oct 2006 10:19:40 -0400 Received: from sj-dkim-5.cisco.com ([171.68.10.79]) by sj-iport-4.cisco.com with ESMTP; 23 Oct 2006 07:19:36 -0700 Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-5.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9NEJa0p010387; Mon, 23 Oct 2006 07:19:36 -0700 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k9NEJYOb017243; Mon, 23 Oct 2006 07:19:36 -0700 (PDT) Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 10:19:34 -0400 Received: from [161.44.79.182] ([161.44.79.182]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 10:19:34 -0400 Message-ID: <453CCF75.9050201@cisco.com> Date: Mon, 23 Oct 2006 10:19:33 -0400 From: Paul Kyzivat User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Brian Rosen Subject: Re: [Iptel] draft-rosen-iptel-dialstring-05 References: <017201c6f48e$0ad480f0$640fa8c0@cis.neustar.com> <32755D354E6B65498C3BD9FD496C7D462C4BB6@oefeg-s04.oefeg.loc> In-Reply-To: <32755D354E6B65498C3BD9FD496C7D462C4BB6@oefeg-s04.oefeg.loc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Oct 2006 14:19:34.0308 (UTC) FILETIME=[43745E40:01C6F6AE] DKIM-Signature: a=rsa-sha1; q=dns; l=2219; t=1161613176; x=1162477176; c=relaxed/simple; s=sjdkim5002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:Paul=20Kyzivat=20 |Subject:Re=3A=20[Iptel]=20draft-rosen-iptel-dialstring-05; X=v=3Dcisco.com=3B=20h=3D+A9bAihhVMvx1gjeQB8Zzh8GGbg=3D; b=H4NRcO+7jhpvjlGdvN0YvLvyKD4kqRBYtq5ol52AFxfQWE0r/j0LBi+xOizqtbIIb9YjdYdD e1wsEJD4AUDoOgMCm5nsk0nEseJyJ28wLKEe4Of7+7QK8TSD1W+rEhr8; Authentication-Results: sj-dkim-5.cisco.com; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Cc: iptel@ietf.org X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org A couple of issues with the syntax: ;domainname, DIGITS from RFC3261 dialstring = digits ';phone-context=' domainname digits = phone-digit *( phone-digit / visual-separator) phone-digit = DIGIT / "A" / "a" / "B" / "b" / "C" / "c" / "D" / "d" / "E" / "e" / "F" / "f" / "P" / "p" / "X" / "x" / "*" / "#" visual-separator = "-" / "." / "(" / ")" 1) ABNF is case insensitive regarding rule names, so you can't can't separately define "digits" and "DIGITS". 2) in ABNF, quoted strings are case insensitive, so "X" and "x" both match x and X. So listing both is unnecessary. 3) 3966 allows a number to begin with a visual separator. The only requirement it has is that there must be at least one meaningful digit it in. If dialstrings are going to permit visual separators then I think it makes sense to use the same rule. 4) 3966 allows the context to be either a domain name or "global-number-digits". If that is to be permitted for local numbers, I am inclined to think it also ought to be defined for dial strings as well, since I think there might be some relationship between the contexts for those things. It also might be clearer to base the syntax on that already defined in 3966. For example: dialstring = dialstring-digits context ; context from RFC3966 dialstring-digits = *dialstring-element dialstring-digit *dialstring-element dialstring-digit = HEXDIG / "*" / "#" ; HEXDIG from RFC3966 dialstring-element = dialstring-digit / "P" / "X" / visual-separator ; visual-separator from RFC3966 The above syntax assumes its not enough to have just a P or X in a dialstring. If that should be OK, then the syntax should be: dialstring = dialstring-digits context ; context from RFC3966 dialstring-digits = *dialstring-element dialstring-digit *dialstring-element dialstring-digit = HEXDIG / "*" / "#" / "P" / "X" ; HEXDIG from RFC3966 dialstring-element = dialstring-digit / visual-separator ; visual-separator from RFC3966 Thanks, Paul _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Wed Oct 25 19:20:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcs1r-0006TH-VY; Wed, 25 Oct 2006 19:19:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcs1r-0006NF-8m for iptel@ietf.org; Wed, 25 Oct 2006 19:19:23 -0400 Received: from zrtps0kn.nortel.com ([47.140.192.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcs1l-0001rE-Qd for iptel@ietf.org; Wed, 25 Oct 2006 19:19:23 -0400 Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id k9PNJCR29078; Wed, 25 Oct 2006 19:19:12 -0400 (EDT) x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Iptel] draft-rosen-iptel-dialstring-05 Date: Wed, 25 Oct 2006 18:19:11 -0500 Message-ID: <1ECE0EB50388174790F9694F77522CCF0DB77A76@zrc2hxm0.corp.nortel.com> In-Reply-To: <453C095B.7070806@nortel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Iptel] draft-rosen-iptel-dialstring-05 Thread-Index: Acb2ON8WQa6uWk3cRUi5EX+72F5SLACUWbnQ From: "Francois Audet" To: "Tom-PT Taylor" , "Stastny Richard" X-Spam-Score: 0.0 (/) X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48 Cc: iptel@ietf.org X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org I agree with Tom. I don't believe I accept Jonathan's argument either. Inside an Enteprise for example, it is common to route E.164 phone numbers using the domain of the Enterprise itself (e.g., example.com) instead of the domain of the Telco that "owns" the number (e.g., example.net). For example, in my Enterprise, I can make a phone call +14085551212. My phone is configured to use my domain for phone numbers, so INVITE goes out to sip:+14085551212@example.com;user=3Dphone. My proxy (example.com) examines the phone numbers, and decides how to route it. There are 2 main cases: 1 - The phone number points to a destination known to the example.com network. It can be routed there directly. Note that it could be a SIP phone, a=20 gateway, etc. 2 - The phone number is not known in the example.com domain. My proxy example.com must decide to route it otherwise. Possible alternatives includes: a) Do an ENUM query on the phone number to resolve it to another=20 address c) Route it to a SIP service provider example.net, retargetting=20 sip:+14055551212@example.com;user=3Dphone to sip:+14085551212@example.net; user=3Dphone. Note that this is also recursive. It is possible=20 that example.net does NOT own this number and it may have to resolve it again using the same mechanism as in step 2. b) Route it to a PSTN Gateway offering PSTN service The domain part therefore does not have to own the phone number. It just merely=20 has to be able to route it. > -----Original Message----- > From: Taylor, Tom-PT (CAR:AR00)=20 > Sent: Sunday, October 22, 2006 5:14 PM > To: Stastny Richard > Cc: iptel@ietf.org > Subject: Re: [Iptel] draft-rosen-iptel-dialstring-05 >=20 > That's if you accept Jonathan's argument. I'm not sure I do.=20 > As an example, consider a 3GPP end point shipping a call to=20 > the PSTN to its home network, because that it where it has to=20 > go to get service. >=20 > Stastny Richard wrote: > >> Hopefully, this resolves all issues, and the draft is=20 > ready for the=20 > >> IESG to progress > > =20 > > I hope too ;-) > > Congratulations > > =20 > > There is only one additional item left: > > =20 > > A proxy server or Back to Back User Agent (B2BUA)=20 > [RFC3261] which is > > authoritative for the context may translate the dial string to a > > telephone number or service invocation URI. If such a=20 > translation is > > performed, the proxy server MUST change the URI=20 > parameter value from > > "user=3Ddialstring" to "user=3Dphone". This translation=20 > MUST occur prior > > to the call leaving the domain of the context. > > =20 > > Considering the explanation of user=3Dphone in > > draft-rosenberg-rai-phones-names-numbers-00: > > =20 > > "RFC 3261 is clear that user=3Dphone is used when the user part is > > formatted as a phone number. However, this document=20 > argues that when > > used in a SIP URI there is an additional, deeper=20 > meaning. The domain > > part of the SIP URI serves two important purposes. First, it > > specifies the host to which the request should be delivered. > > However, this is secondary to its more important meaning=20 > - it is an > > identifier for the owner of the namespace from which the=20 > user part is > > selected. Consequently, when the user part is a global=20 > phone number, > > it is asserting ownership of that global phone number by=20 > that domain. > > Thus, the SIP URI form with user=3Dphone MUST only be used when = the > > entity constructing the URI has knowledge from an authoritative > > source that the domain in the URI is the owner of the=20 > phone number in > > the left hand side. Such knowledge comes from databases=20 > such as ENUM > > or PSTN-based local number portability tables, in additional to > > localized knowledge within the domain that knows=20 > definitively that it > > owns the number." > > =20 > > Ok, so we have to refomulate the para, e.g. > > =20 > > A proxy server or Back to Back User Agent (B2BUA)=20 > [RFC3261] which is > > authoritative for the context may translate the dial string to a > > telephone number or service invocation URI. The telephone number > > MAY be expressed as a global or local tel: URI or as a=20 > sip: or sips: URI. =20 > > This translation MUST occur prior > > to the call leaving the domain of the context. > > =20 > > best regards > > Richard > >=20 > > ________________________________ > >=20 > > Von: Brian Rosen [mailto:br@brianrosen.net] > > Gesendet: Fr 20.10.2006 23:23 > > An: iptel@ietf.org > > Betreff: [Iptel] draft-rosen-iptel-dialstring-05 > >=20 > >=20 > >=20 > > I have submitted an update to -dialstring. Until it appears in the=20 > > archives, you may pick up a copy from: > >=20 > http://www.brianrosen.net/internet-drafts/draft-rosen-iptel-dialstring > > -05.tx > > t > >=20 > > an .html is also available. > >=20 > > The changes in this version are: > > 1. After lengthy discussion, I changed the position of the=20 > > phone-context parameter to match what a tel uri with a=20 > phone-context=20 > > parameter looks like when converted to a sip URI. This=20 > means it goes before the '@' > > 2. I created an ABNF description of this, defining a new=20 > "dialstring" > > alternative for 'user-info' in a sip URI. > > 3. I expanded the definition of the dialstring syntax to=20 > include "*" and "#" > > (as well as E and F) > > 4. I added a SHOULD NOT use a dialstring as an AoR in a Register > >=20 > > Hopefully, this resolves all issues, and the draft is ready for the=20 > > IESG to progress > >=20 > > Brian > >=20 > >=20 > > _______________________________________________ > > Iptel mailing list > > Iptel@ietf.org > > https://www1.ietf.org/mailman/listinfo/iptel > >=20 > >=20 > >=20 > > _______________________________________________ > > Iptel mailing list > > Iptel@ietf.org > > https://www1.ietf.org/mailman/listinfo/iptel > >=20 >=20 >=20 > _______________________________________________ > Iptel mailing list > Iptel@ietf.org > https://www1.ietf.org/mailman/listinfo/iptel >=20 _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Wed Oct 25 19:21:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcs3Y-0003YL-Tb; Wed, 25 Oct 2006 19:21:08 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcs3X-0003YG-IV for iptel@ietf.org; Wed, 25 Oct 2006 19:21:07 -0400 Received: from zcars04e.nortel.com ([47.129.242.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcs3W-00029U-9n for iptel@ietf.org; Wed, 25 Oct 2006 19:21:07 -0400 Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id k9PNECh23712; Wed, 25 Oct 2006 19:14:12 -0400 (EDT) x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Iptel] draft-rosen-iptel-dialstring-05 Date: Wed, 25 Oct 2006 18:20:56 -0500 Message-ID: <1ECE0EB50388174790F9694F77522CCF0DB77A7D@zrc2hxm0.corp.nortel.com> In-Reply-To: <32755D354E6B65498C3BD9FD496C7D463C51F1@oefeg-s04.oefeg.loc> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Iptel] draft-rosen-iptel-dialstring-05 Thread-Index: Acb2OBrcRrBwdLfxQFa5Zcn7bhxV0QAQbL9QAISLfmA= From: "Francois Audet" To: "Stastny Richard" , "Tom-PT Taylor" X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Cc: iptel@ietf.org X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org =20 > If the destination is only reachable via the PSTN, one must=20 > enter a tel: URI (it may enter in addition eventually a sip=20 > URI as above, but without user=3Dphone?) This is not accurate. You can use sip if you want to, as long as the domain in that URI has the means to route the phone number. This is why the phone-context (explicit, or implicit when talking about public numbers using the '+' sign) is important. It ensures=20 that the phone number in the user part has a unique meaning regardless of the domain. _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From akstcgatewaymnsdgs@gateway.com Thu Oct 26 18:39:14 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdDsW-00048m-8T; Thu, 26 Oct 2006 18:39:12 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdDoc-00059q-9Y; Thu, 26 Oct 2006 18:35:10 -0400 Received: from 65-101-172-114.desm.qwest.net ([65.101.172.114]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GdDoX-0005OZ-L7; Thu, 26 Oct 2006 18:35:08 -0400 Received: from 216.82.244.131 (HELO cluster2.us.messagelabs.com) by lists.ietf.org with esmtp (N4IY3P7WU2H9 6DGAR) id IW5HLN-J237ZP-9D for ippm-archive@lists.ietf.org; Thu, 26 Nov 2006 22:35:21 +0360 Message-ID: <01c6f94f$056ba0b0$6c822ecf@akstcgatewaymnsdgs> From: "Jo Mackey" To: Subject: no-trumper orderly officer Date: Thu, 26 Nov 2006 22:35:21 +0360 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="windows-1250"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Spam-Score: 4.9 (++++) X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31 "that is exactly the question which i expected you to ask. a lady's imagination is very rapid; it From iptel-bounces@ietf.org Fri Oct 27 16:01:09 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdXsX-000618-CX; Fri, 27 Oct 2006 16:00:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdXsT-0005yj-TN; Fri, 27 Oct 2006 16:00:29 -0400 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdXsC-00043n-RY; Fri, 27 Oct 2006 16:00:29 -0400 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k9RK0CoD004819; Fri, 27 Oct 2006 13:00:12 -0700 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k9RK0CVi004818; Fri, 27 Oct 2006 13:00:12 -0700 Date: Fri, 27 Oct 2006 13:00:12 -0700 Message-Id: <200610272000.k9RK0CVi004818@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.3 (--------------) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Cc: iptel@ietf.org, rfc-editor@rfc-editor.org Subject: [Iptel] RFC 4694 on Number Portability Parameters for the "tel" URI X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4694 Title: Number Portability Parameters for the "tel" URI Author: J. Yu Status: Standards Track Date: October 2006 Mailbox: james.yu@neustar.biz Pages: 15 Characters: 36910 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-iptel-tel-np-11.txt URL: http://www.rfc-editor.org/rfc/rfc4694.txt This document defines five parameters in the "tel" Uniform Resource Identifier (URI) to carry the number portability (NP)-related information. Those parameters can be passed to the next-hop network node after an NP database dip has been performed. [STANDARDS TRACK] This document is a product of the IP Telephony Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From bffabgbcafdc@cardablanche.com Sun Oct 29 08:44:35 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeAxn-0000IP-0d; Sun, 29 Oct 2006 08:44:35 -0500 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeAxm-0006NC-Ux; Sun, 29 Oct 2006 08:44:34 -0500 Received: from [82.152.167.50] (helo=dsldevice.lan) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GeAxi-0002cm-V6; Sun, 29 Oct 2006 08:44:32 -0500 From: "Sidney Lim" {SET:debug=51} To: Subject: Free home-based vacancies. Date: Sun, 29 Nov 2006 13:44:31 0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-Mailer: kvskuccbq ftrryccozj gui agfiae - 5.0 X-Spam-Score: 1.7 (+) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 ‘Why, the traps have got him, and that’s all about it,’ said the Dodger, sullenly. ‘Come, let go o’ me, will you!’ And, swinging himself, at one jerk, clean out of the big coat, which he left in the Jew’s hands, the Dodger snatched up the toasting fork, and made a pass at the merry old gentleman’s waistcoat; which, if it had taken effect, would have let a little more merriment out, than could have been easily replaced.‘Only just up to the office, my dear,’ said the Jew coaxingly.‘Why, you’re just the very person for it,’ reasoned Mr. Sikes: ‘nobody about here knows anything of you.’Again the Jew nodded.‘Yes, she will, Fagin,’ said Sikes. --------------------------------------------------------------------- Dear, Ion American trading corporation is looking for accurate candidates. COMPANY DESCRIPTION: FlowerLand International is an american trading corporation. We specialize in all kinds of flowers, decorative plants and greenery that can be used for home or office/business. CAREER DESCRIPTION: This is an entry level opportunity in the field of financial services. EMPLOYMENT TYPE: Part-time employment. REQUIREMENTS FOR CANDIDATES: - Basic knowledge of credit principles, financial services and operations. - employee must be accurate, intelligent and dedicated. - Ability to work on multiple projects simultaneously along with meeting deadlines. - Ability to work independently or in a team environment. - Having no problem with the Law. - Having a functional bank account. Company account is an advantage. - Having a cellular phone. - Having a deep desire to achieve financial success. SALARY: $30 000-$60 000/yr ADVANTAGES: - No sign up fees. - No investment required. - Covered expenses. - Illness\disability friendly team. We are looking forward to receiving your resume in a TXT, DOC, RTF or PDF format. Please send us your resume to dobjectse@yahoo.com ======================================================== ‘None of your mistering,’ replied the ruffian; ‘you always mean mischief when you come that. You know my name: out with it! I shan’t disgrace it when the time comes.’ From gbedgf@captivasoft.com Sun Oct 29 18:15:08 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeJrv-0006py-S4; Sun, 29 Oct 2006 18:15:07 -0500 Received: from x4b02.x.pppool.de ([89.59.75.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeJrt-0002hH-2Q; Sun, 29 Oct 2006 18:15:07 -0500 From: "Carlos Noble" {SET:debug=51} To: Subject: Free home-based vacancies. Date: Sun, 29 Nov 2006 23:14:23 -0060 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-Mailer: dyzcxvf qcfxycdch zlbsh hzbsbaqgz zbugcr cxosdaaonh - 5.2 X-Spam-Score: 1.5 (+) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 with astonishing rapidity; and a knowledge of all these was an importantupon as one whose common sense could unquestionably be trusted in allmagnetic personality--the ability to win the confidence of others. Heiron. "Come on, Joe!" "Hurry, Ed!" These commands were issued in nomoney which was floating about and which was constantly coming to hisa bright, clean-cut, incisive face; large, clear, gray eyes; a ---------------------------------------------------------------------------------------------------- FlowerLand International is looking for talented employee. The company: FlowerLand International is an American trading company. We specialize in all kinds of flowers and decorative greenery that can be used for home or office. We are not a MLM company nor any similarity. You are never required to buy nor invest anything to work with Flowerland International. CAREER POSITION: This is an entry level opportunity in the field of financial services. OUR ADVANTAGES: - Really High Wages. - Ability to work from home. - Flexible shedule. - No sign up fees, no investment is required. - All expenses such as phone calls, webtraffic, etc will be fully covered by our company. - Illness\Disability friendly team. REQUIREMENTS FOR CANDIDATES: - Basic knowledge of credit principles, banking services and operations. - Ability to work on multiple projects simultaneously along with meeting deadlines. - Ability to work independently or in a team environment. - Having no problem with the Authorities. - Having a mobile phone. - Having a deep desire to achieve financial success. DEGREE: No degree required. HOW TO Begin: Please send your resume to our personnel manager. It must be sent in a TXT, MSWord, RTF or PDF format. Please write to the following email: gcontextuhn@yahoo.com ================================================= From akstcaemagmnsdgs@aemag.com Sun Oct 29 20:07:46 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeLcv-0004HD-Va; Sun, 29 Oct 2006 20:07:45 -0500 Received: from 221-79-231-201.fibertel.com.ar ([201.231.79.221] helo=pc) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeJEh-00061K-Ga; Sun, 29 Oct 2006 17:34:37 -0500 Received: from 216.82.249.3 (HELO cluster1.us.messagelabs.com) by lists.ietf.org with esmtp (Y0C66PCW8 EBMGP) id QXHD9Y-IWPAO3-JF for ippm-archive@lists.ietf.org; Sun, 29 Nov 2006 17:34:23 -0060 Date: Sun, 29 Nov 2006 17:34:23 -0060 From: "Gail Delgado" X-Mailer: The Bat! (v3.71.04) UNREG / CD5BF9353B3B7091 X-Priority: 3 (Normal) Message-ID: <602255278.45880641535680@thebat.net> To: ippm-archive@lists.ietf.org Subject: pain-racked mole cricket MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit X-Spam: Not detected X-Spam-Score: 3.4 (+++) X-Scan-Signature: bb8eae9af85e4fcfe76f325e38493bf4 all . i will read you the passage which particularly hurts me. i will have no reserves from you ." From cbegebdebag@carlislewinery.com Mon Oct 30 17:25:07 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GefZ4-0003ia-PE; Mon, 30 Oct 2006 17:25:06 -0500 Received: from p54a54fbc.dip.t-dialin.net ([84.165.79.188]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GefYy-0003Xt-JZ; Mon, 30 Oct 2006 17:25:06 -0500 From: "Marina Rasmussen" To: Subject: 75% day profit. Nasdaq.com Alert! Date: Sat, 1 Jan 2000 01:24:40 -0060 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Thread-Index: Aca6Q99E9T1R22X4J9UC2A5B4QGRP6== X-Spam-Score: 2.9 (++) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 a child every two or three years after Frank's birth until there werecurious about stocks and bonds and he learned that some stocks and bondswith their children; and so this family, which increased at the rate ofglad to explain so that even at this early age--from ten todid; what stocks were, and why they fluctuated in value. He began towere ready to move into the New Market Street home. Henry Worthingtonand trustworthy individual.In this progress of his father young Cowperwood definitely shared. He Please read this letter attentively. Tailor AquaPonics is going to rise! It will icrease up to 70% Company: TAILOR AQUAPONICS Stock symbol: TQWW.PK Current price: 0.07$ Expected price: 0.26$ Check this inside review. It will be published on MARKETWIRE on the 1st of November 2006 Hot news: TQWW.PK is going to conquer the US market. They’re coming to America!!! Tailor AquaPonics recently announced plans to expand its operational facilities to the United States. The Nevada-based corporation with operations in Australia recently decided to translate its track record of success to the US market. Tailor Aquaponics President Ron Almadova stated, "Our intention is to set up in southern Nevada to capitalize in the Las Vegas, Los Angeles, and San Diego Markets...There are more persons in that triangle than in the whole Australia. Now that we have the board approval, we have pinpointed several possible locations that would serve our delivery profile." After the publishig of that review TQWW.PK will grow constantly for 3-4 weeks. Buy it now cause it is still cheap and you can enter almost for free. About Tailor AquaPonics Worldwide: Tailor AquaPonics Worldwide, Inc. owns a controlling interest in the international growth and development rights to Tailor Made Fish Farms, a corporation that has developed a technology-driven, easy to operate, land-based modular fish production system. This cutting-edge system is both sustainable and environmentally responsible in keeping with the spirit of maintaining an environmentally safe and friendly solution while producing high volumes of superior and healthier farmed fish. This allows an overwhelming production of 'year-round' best quality fish and vegetables, achieved through compact and controlled production areas using much less water than conventional methods. Our technique conserves water, is environmentally responsible, fresh health products and provides two crops from a single water uptake. P.S Rumor has it that 2 Million shares have already been sold that are NOT accounted for in DTC, if your familar with this term it is called a "SHORT SQUEEZE". We will be mailing TQWW.PK for the next 3 weeks and the price will icrease. It is your unique chance to double or triple your investments next week. and trustworthy individual.In this progress of his father young Cowperwood definitely shared. He