From iptel-bounces@ietf.org Wed Jul 05 04:42:57 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy2yB-00051w-4Q; Wed, 05 Jul 2006 04:42:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy2yA-00051o-1H for iptel@ietf.org; Wed, 05 Jul 2006 04:42:50 -0400 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Fy2y8-0003Xl-Gn for iptel@ietf.org; Wed, 05 Jul 2006 04:42:50 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C6A00F.92452CC0" Date: Wed, 5 Jul 2006 10:46:56 +0200 Message-ID: <32755D354E6B65498C3BD9FD496C7D462C4AFF@oefeg-s04.oefeg.loc> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: I-D ACTION:draft-rosen-iptel-dialstring-04.txt Thread-Index: AcaaPRuqWaa+H6NGSQawCiIPTCajHgF0ViFp References: From: "Stastny Richard" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 Cc: brian.rosen@neustar.biz Subject: [Iptel] Re: I-D ACTION:draft-rosen-iptel-dialstring-04.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 This is a multi-part message in MIME format. ------_=_NextPart_001_01C6A00F.92452CC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Brian, =20 IMHO the examples are wrong: =20 e.g.: sip:123@sippbx.example.com;user=3Ddialstring; phone-context=3Datlanta.example.com should read: sip:123;phone-context=3Datlanta.example.com@sippbx.example.com;user=3Ddia= lstring =20 Phone-context is part of the tel: URI and not from the sip URI =20 -sta ________________________________ Von: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Gesendet: Mi 28.06.2006 00:50 An: i-d-announce@ietf.org Betreff: I-D ACTION:draft-rosen-iptel-dialstring-04.txt=20 A New Internet-Draft is available from the on-line Internet-Drafts = directories. Title : Dialstring parameter for the Session Initiation Protocol Uniform Resource Identifier Author(s) : B. Rosen Filename : draft-rosen-iptel-dialstring-04.txt Pages : 8 Date : 2006-6-27 =20 RFC3966 explicitly states that 'tel' URIs may not represent a dial string. That leaves no way specify a dial string in a standardized way. Great confusion exists with the SIP URI parameter = "user=3Dphone", and specifically, if it can represent a dial string. This memo creates a new value for the user parameter "dialstring", so that one may specify "user=3Ddialstring" to encode a dial string as a 'sip:' = or 'sips:' URI. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-rosen-iptel-dialstring-04.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.=20 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-rosen-iptel-dialstring-04.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-rosen-iptel-dialstring-04.txt". =20 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. =20 =20 Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------_=_NextPart_001_01C6A00F.92452CC0 Content-Type: text/plain; name="ATT58395.txt" Content-Transfer-Encoding: base64 Content-Description: ATT58395.txt Content-Disposition: attachment; filename="ATT58395.txt" X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmll dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo= ------_=_NextPart_001_01C6A00F.92452CC0 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_001_01C6A00F.92452CC0-- From iptel-bounces@ietf.org Wed Jul 05 17:20:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FyEnE-0008TX-Jh; Wed, 05 Jul 2006 17:20:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FyEnD-0008TS-2W for iptel@ietf.org; Wed, 05 Jul 2006 17:20:19 -0400 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyEnA-0006x0-AP for iptel@ietf.org; Wed, 05 Jul 2006 17:20:19 -0400 Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 05 Jul 2006 14:20:15 -0700 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.06,210,1149490800"; d="scan'208"; a="31208932:sNHT54874864" Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k65LKDnq028623; Wed, 5 Jul 2006 17:20:14 -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.211); Wed, 5 Jul 2006 17:20:13 -0400 Received: from [10.86.240.9] ([10.86.240.9]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 5 Jul 2006 17:20:12 -0400 Message-ID: <44AC2D0A.7030302@cisco.com> Date: Wed, 05 Jul 2006 17:20:10 -0400 From: Paul Kyzivat User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Stastny Richard Subject: Re: [Iptel] Re: I-D ACTION:draft-rosen-iptel-dialstring-04.txt References: <32755D354E6B65498C3BD9FD496C7D462C4AFF@oefeg-s04.oefeg.loc> In-Reply-To: <32755D354E6B65498C3BD9FD496C7D462C4AFF@oefeg-s04.oefeg.loc> Content-Type: multipart/mixed; boundary="------------020502000800030803040900" X-OriginalArrivalTime: 05 Jul 2006 21:20:12.0067 (UTC) FILETIME=[CCE44730:01C6A078] X-Spam-Score: 0.5 (/) X-Scan-Signature: 4fc59e88b356924367ae169e6a06365d Cc: iptel@ietf.org, brian.rosen@neustar.biz 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 This is a multi-part message in MIME format. --------------020502000800030803040900 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I agree with Richard. And I brought it up on the -03 (and the -02 I think) versions as well. There is also the issue of * & #. I'm attaching an old message that covers most of that. Paul Stastny Richard wrote: > Hi Brian, > > IMHO the examples are wrong: > > e.g.: > sip:123@sippbx.example.com;user=dialstring; > phone-context=atlanta.example.com > > should read: > sip:123;phone-context=atlanta.example.com@sippbx.example.com;user=dialstring > > Phone-context is part of the tel: URI and not from the sip URI > > -sta > > ________________________________ > > Von: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Gesendet: Mi 28.06.2006 00:50 > An: i-d-announce@ietf.org > Betreff: I-D ACTION:draft-rosen-iptel-dialstring-04.txt > > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title : Dialstring parameter for the Session > Initiation Protocol Uniform Resource > Identifier > Author(s) : B. Rosen > Filename : draft-rosen-iptel-dialstring-04.txt > Pages : 8 > Date : 2006-6-27 > > RFC3966 explicitly states that 'tel' URIs may not represent a dial > string. That leaves no way specify a dial string in a standardized > way. Great confusion exists with the SIP URI parameter "user=phone", > and specifically, if it can represent a dial string. This memo > creates a new value for the user parameter "dialstring", so that one > may specify "user=dialstring" to encode a dial string as a 'sip:' or > 'sips:' URI. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-rosen-iptel-dialstring-04.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-rosen-iptel-dialstring-04.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-rosen-iptel-dialstring-04.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. > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce > > > ------------------------------------------------------------------------ > > _______________________________________________ > Iptel mailing list > Iptel@ietf.org > https://www1.ietf.org/mailman/listinfo/iptel --------------020502000800030803040900 Content-Type: message/rfc822; name="Attached Message" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Attached Message" X-Account-Key: account2 Received: from xbh-rtp-211.amer.cisco.com ([64.102.31.102]) by xmb-rtp-213.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 26 Apr 2006 12:34:18 -0400 Received: from xbh-sjc-231.amer.cisco.com ([128.107.191.100]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 26 Apr 2006 12:34:18 -0400 Received: from sj-iport-3.cisco.com ([171.71.176.72]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 26 Apr 2006 09:34:16 -0700 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 26 Apr 2006 09:34:16 -0700 Received: from sj-inbound-a.cisco.com (sj-inbound-a.cisco.com [128.107.234.204]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k3QGYFRT006237 for ; Wed, 26 Apr 2006 09:34:15 -0700 (PDT) Received: from host10.216.41.24.conversent.net (HELO acmepacket.com) ([216.41.24.10]) by sj-inbound-a.cisco.com with ESMTP; 26 Apr 2006 09:34:09 -0700 X-from-outside-Cisco: 216.41.24.10 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAQAAA+k= X-IronPort-AV: i="4.04,158,1144047600"; d="scan'208"; a="460713483:sNHT38351352" Received: from BPenfield [10.0.200.6] by acmepacket.com with ESMTP (SMTPD-9.03) id A0E80420; Wed, 26 Apr 2006 12:33:44 -0400 Message-ID: <002601c6694f$2ed9b3f0$800101df@acmepacket.com> From: "Bob Penfield" To: "Paul Kyzivat" , "Tom-PT Taylor" Cc: , , "Peterson,Jon" References: <444F6947.7060608@nortel.com> <444F9639.4070407@cisco.com> Subject: Re: [Iptel] Gen-art review of draft-rosen-iptel-dialstring-03.txt Date: Wed, 26 Apr 2006 12:33:43 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Return-Path: BPenfield@acmepacket.com X-OriginalArrivalTime: 26 Apr 2006 16:34:16.0152 (UTC) FILETIME=[4240E580:01C6694F] I agree with Paul on the phone-context point. Just as user=phone hints/indicates that the userinfo is a phone number including its phone-context, dialstring should mean the same sort of construct. The phone-context is an attribute of the userinfo part of the URI. What would a phone-context SIP-URI parameter mean when there was no user parameter? or with a user=phone URI parameter? cheers, (-:bob Robert F. Penfield Chief Software Architect Acme Packet, Inc. 71 Third Avenue Burlington, MA 01803 bpenfield@acmepacket.com ----- Original Message ----- From: "Paul Kyzivat" To: "Tom-PT Taylor" Cc: ; ; "Peterson,Jon" Sent: Wednesday, April 26, 2006 11:48 AM Subject: Re: [Iptel] Gen-art review of draft-rosen-iptel-dialstring-03.txt > There was other discussion of this back in March that, AFAIK, did not come > to a conclusion. Are that discussion and the Gen-ART review running in > parallel, or has the earlier discussion been forgotten? > > I had brought up two issues: > > - I propose that the phone-context parameter, reused from 3966, > should be used the way other parameters from 3966 are used > with a sip uri - in the user part. (If a phone-context parameter > is to be used as a sip URI parameter, then the syntax of the > sip URI will need to be updated to reflect this. But I don't > think that is the right thing to do.) > > - allowing use of # and * in dial strings. (Brian did agree to this.) > > Paul > > Tom-PT Taylor wrote: >> I am the assigned Gen-ART reviewer for >> draft-rosen-iptel-dialstring-03.txt. For background on Gen-ART, please >> see the FAQ at >> . >> >> This draft is basically acceptable, but needs a few fixes. I have also >> identified a number of editorial issues. I suppose I'm going to get hell >> for not reviewing this draft in the two years it has been around, but >> better late than never. >> >> Substantive comments: >> ===================== >> >> 1. I believe the problem is mis-stated in the second paragraph of section >> 1. Ignoring the matter of RFC 2806-based implementations, the user part >> of a SIP URI with the "user=phone" parameter is, without ambiguity, a >> phone number. The real problem is that before the transformation occurs >> (and the "user=phone" parameter is added if applicable), entities beyond >> the originating point cannot distinguish between a dial string and an >> user part that happens to consist of the characters that can be present >> in a dial string. I suggest that the second paragraph be replaced by the >> following: >> >> "There is a problem here. The intermediary can apply its transformation >> only if it recognizes that the user part of the SIP URI is a dial string. >> However, there is currently no way to distinguish an user part consisting >> of a dial string from an user part that happens to be composed of >> characters that would appear in a dial string." >> >> It is also necessary to change the second-last requirement in section 3 >> as follows: >> >> Current text: >> " It MUST be possible to distinguish between a dialstring and a phone >> number." >> >> New text: >> " It MUST be possible to distinguish between a dialstring and an user >> part that happens to consist of the same characters." >> >> >> 2. The requirement in section 3 that a context be present is unmotivated. >> I suggest adding the following sentence at the end of the first paragraph >> of section 1: >> >> " The intermediary is able to perform this transform provided that it >> knows the context (i.e., dialling plan) within which the number was >> dialled." >> >> 3. In section 3, a dial string is defined to consist of a certain set of >> characters, but then the requirement to convey pause and "wait for call >> completion" is added. It would be cleaner to include the characters for >> the latter functions in the definition of dial string in the first place. >> I therefore suggest the following changes: >> >> -- move the requirement to represent pause and "wait for call >> completion" from its present position near the end of the section to >> follow the first sentence/requirement of the section. >> >> -- add the following bullet point to the list of characters in a dial >> string: >> >> <* Characters to express "pause" and "wait for call completion".> >> >> Editorial comments >> ================== >> >> General: "user part" and "dial string" (except as a parameter value), not >> "userpart" and "dialstring". >> >> Section 1, para 1, second sentence: "One enters ..." -> "The user enters >> ...". >> >> Section 1, para 1, third sentence: >> "The entered sequence, called a "dialstring", may ..." >> ^ ^^^ >> >> Section 1, para 3, first sentence: "post dial" -> "after the initial >> number has been dialled". >> >> Section 1, para 3, second sentence: "functions" -> "function". >> >> Section 1, para 3, end of third sentence: "as DTMF" -> "as a series of >> DTMF digits". >> >> Section 1, para 3: add this sentence at the end to make the point of the >> paragraph: >> >> "This is another case where the ability to indicate that a dialstring is >> being presented would be useful." >> >> Section 3, dial string character list, third bullet: >> "* The MF digits A-D" -> "* The DTMF digits A-D" >> >> Section 3, note on DTMF following the bullets: suggest this be indented >> (empty list item in XML2RFC) to show its informative status. >> >> Section 4 para 1, final sentence: >> "E represent *" -> "E represents *" >> -> > completion"> >> >> Section 4 para 2, final sentence: >> current: >> proposed: > "user=phone".> >> >> Section 4, voicemail example: to be consistent with the motivation in >> section 1, one would expect the dial string to be 4500X4123 rather than >> 4500P4123. >> >> Section 5, second para, second sentence: "This RFC would" -> "This RFC >> must". >> >> Section 5, third para, end: "[RFC3969]" -> "[RFC3966]" >> >> References, [RFC3969] repeats citation for [RFC3966] rather than giving >> the details for RFC 3969. >> >> Tom Taylor >> >> >> >> >> >> >> _______________________________________________ >> 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 > --------------020502000800030803040900 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 --------------020502000800030803040900-- From iptel-bounces@ietf.org Sun Jul 09 13:16:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fzcsu-0005m0-UZ; Sun, 09 Jul 2006 13:15:56 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fzcst-0005lv-1j for iptel@ietf.org; Sun, 09 Jul 2006 13:15:55 -0400 Received: from cdx28.winwebhosting.com ([70.85.255.82]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fzcsq-0007ay-Lz for iptel@ietf.org; Sun, 09 Jul 2006 13:15:55 -0400 Received: from neustargw.va.neustar.com ([209.173.53.233] helo=BROSENLT40xp) by cdx28.winwebhosting.com with esmtpa (Exim 4.52) id 1Fzcsi-0001dJ-I9; Sun, 09 Jul 2006 12:15:45 -0500 From: "Brian Rosen" To: "'Paul Kyzivat'" , "Stastny Richard" Subject: RE: [Iptel] Re: I-D ACTION:draft-rosen-iptel-dialstring-04.txt Date: Sun, 9 Jul 2006 13:15:33 -0400 Message-ID: <1b2101c6a37b$53b7fef0$08f65341@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 In-Reply-To: <44AC2D0A.7030302@cisco.com> Thread-Index: AcageNBHysirBagFSoCrxn9dk5YxNADAnHDQ 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 - [47 12] / [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: b2809b6f39decc6de467dcf252f42af1 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 The form of the parameter is an open issue; I don't agree that it should be a URI parameter. The * & # is an oversight, and I'll get it fixed one way or another. Brian -----Original Message----- From: Paul Kyzivat [mailto:pkyzivat@cisco.com] Sent: Wednesday, July 05, 2006 5:20 PM To: Stastny Richard Cc: iptel@ietf.org; Rosen, Brian Subject: Re: [Iptel] Re: I-D ACTION:draft-rosen-iptel-dialstring-04.txt I agree with Richard. And I brought it up on the -03 (and the -02 I think) versions as well. There is also the issue of * & #. I'm attaching an old message that covers most of that. Paul Stastny Richard wrote: > Hi Brian, > > IMHO the examples are wrong: > > e.g.: > sip:123@sippbx.example.com;user=dialstring; > phone-context=atlanta.example.com > > should read: > sip:123;phone-context=atlanta.example.com@sippbx.example.com;user=dialstring > > Phone-context is part of the tel: URI and not from the sip URI > > -sta > > ________________________________ > > Von: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Gesendet: Mi 28.06.2006 00:50 > An: i-d-announce@ietf.org > Betreff: I-D ACTION:draft-rosen-iptel-dialstring-04.txt > > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title : Dialstring parameter for the Session > Initiation Protocol Uniform Resource > Identifier > Author(s) : B. Rosen > Filename : draft-rosen-iptel-dialstring-04.txt > Pages : 8 > Date : 2006-6-27 > > RFC3966 explicitly states that 'tel' URIs may not represent a dial > string. That leaves no way specify a dial string in a standardized > way. Great confusion exists with the SIP URI parameter "user=phone", > and specifically, if it can represent a dial string. This memo > creates a new value for the user parameter "dialstring", so that one > may specify "user=dialstring" to encode a dial string as a 'sip:' or > 'sips:' URI. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-rosen-iptel-dialstring-04.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-rosen-iptel-dialstring-04.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-rosen-iptel-dialstring-04.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. > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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 6kbg5Dk8Xn@mail.ru Wed Jul 12 09:53:12 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0f9M-0002IZ-87; Wed, 12 Jul 2006 09:53: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 1G0f9M-0005ro-6N; Wed, 12 Jul 2006 09:53:12 -0400 Received: from bb121-6-126-251.singnet.com.sg ([121.6.126.251]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G0f9J-0004xp-MR; Wed, 12 Jul 2006 09:53:12 -0400 Date: Wed, 12 Jul 2006 13:53:11 -0480 From: "Deirdre Ziegler" X-Mailer: The Bat! (v3.01 RC8) Educational Reply-To: "Deirdre Ziegler" X-Priority: 3 (Normal) Message-ID: <08071250.20060712135311@mail.ru> To: ipo-archive@lists.ietf.org Subject: RYX MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 4.2 (++++) X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4 "Well, if you can't, you can't. I understand you, Red, and I can't pass miles an hour in the entry! You have to be smooth! Firm but smooth, He wants to go up. And what if something gets you at twenty yards? "We're free to go where we wish and to be what we are," Jonathan From komatsu@kamposv.kampo2002.net Wed Jul 12 13:23:59 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0iRL-00079O-78 for iptel-archive@lists.ietf.org; Wed, 12 Jul 2006 13:23:59 -0400 Received: from [219.163.126.184] (helo=kamposv.kampo2002.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0iRI-0007op-AS for iptel-archive@lists.ietf.org; Wed, 12 Jul 2006 13:23:59 -0400 Received: (from komatsu@localhost) by kamposv.kampo2002.net (8.11.6p2/8.11.6) id k6CHjpS29081; Thu, 13 Jul 2006 02:45:52 +0900 Date: Thu, 13 Jul 2006 02:45:52 +0900 Message-Id: <200607121745.k6CHjpS29081@kamposv.kampo2002.net> To: iptel-archive@lists.ietf.org Subject: Message from eBay Member From: eBay-Mitglied gret Content-Type: text/html X-Spam-Score: 4.8 (++++) X-Scan-Signature: fca7d4b87f391aa4d413f865ce6efe79

eBay sent this message.
Your registered name is included to show this message originated from eBay. Learn more.
Question from eBay Member -- Respond Now eBay
eBay sent this message on behalf of an eBay member via My Messages. Responses sent using email will not reach the eBay member. Use the Respond Now button below to respond to this message.
 Question from gret
Activity with gret (last 90 days):
- I have bid on 0 items from gret
gret( 2)
Positive Feedback: 100%
Member Since: Oct-30-03
Location: CA, United States
Registered On: www.ebay.com
Hello,
I recently placed a bid on item#5669378843 being a wheelchair for me that i really need do to my age(87 years old) and it seems that i can not find the auction anymore...May i please know if you are the seller of the item above?
Regards,
Greta
Respond to this question in My Messages.
Respond Now
Thank you for using eBay!
http://www.ebay.com/
Marketplace Safety Tip Marketplace Safety Tip
Do not respond to the sender (through the eBay system or your email provider) if this message is an offer to buy or sell an item. This type of offer is against eBay policy, may be fraudulent, and is not covered by buyer protection programs.

Second Chance Offer emails with the subject of “Message from eBay Member” are fake. Real Second Chance Offers come directly from eBay and appear in My Messages with a blue background and subject stating, “eBay Second Chance Offer for Item...".

Never pay for your eBay item using instant cash wire transfer services through  Western Union or MoneyGram. These payment methods are unsafe when paying someone you don’t know.

Learn more about sending payments.
Is this email inappropriate? Does it violate eBay policy? Help protect the community by reporting it.
Learn how you can protect yourself from spoof (fake) emails at:
http://pages.ebay.com/education/spooftutorial
This eBay notice was sent to you on behalf of another eBay member through the eBay platform and in accordance with our Privacy Policy. If you would like to receive this email in text format, change your notification preferences.
See our Privacy Policy and User Agreement if you have questions about eBay's communication policies.
Privacy Policy: http://pages.ebay.com/help/policies/privacy-policy.html
User Agreement: http://pages.ebay.com/help/policies/user-agreement.html
Copyright © 2006 eBay, Inc. All Rights Reserved.
Designated trademarks and brands are the property of their respective owners.
eBay and the eBay logo are registered trademarks or trademarks of eBay, Inc.
eBay is located at 2145 Hamilton Avenue, San Jose, CA 95125.

From abbcd@0451.com Thu Jul 27 12:40:02 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G68u2-0007vn-5N; Thu, 27 Jul 2006 12:40:02 -0400 Received: from static-213-182-106-63.teleos-web.de ([213.182.106.63]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G68tx-0006r5-Jf; Thu, 27 Jul 2006 12:40:02 -0400 Date: Thu, 27 Jul 2006 16:40:25 -0060 From: "Elisa Fox" X-Mailer: The Bat! (v2.00) Personal Reply-To: "Elisa Fox" X-Priority: 3 (Normal) Message-ID: <403527804.20060727164025@0451.com> To: iporpr-archive@lists.ietf.org Subject: Your cash, passing strake MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 4.2 (++++) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Even if you have no erectin problems SOFT CIAYLIS would help you to make BETTER SEWX MORE OFTEN! and to bring unimagnable plesure to her. Just disolve half a pil under your tongue and get ready for action in 15 minutes. The tests showed that the majority of men after taking this medic ation were able to have PERFECT ERJECTION during 36 hours! VISIT US, AND GET OUR SPECIAL 70% DISC1OUNT OFER! http://wfwrcl.bigbacks.info/?99865114 ========== Outcast. "Family?" "... for his reckless irresponsibility " the solemn voice intoned, "There is a steady leak of materials from the Visitation Zones into the was very nearly Fletcher's top speed. twenty feet away and it's completely rusted out, but they look like they've inventiveness marvelous to behold. "At ease, sergeant," said. "I'm pleased."