From iptel-bounces@ietf.org Fri May 05 12:22:53 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc34Z-0000UF-9b; Fri, 05 May 2006 12:22:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc33m-0008Kr-Ov for iptel@ietf.org; Fri, 05 May 2006 12:21:42 -0400 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fc2ob-00026o-2b for iptel@ietf.org; Fri, 05 May 2006 12:06:01 -0400 Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 05 May 2006 12:06:00 -0400 X-IronPort-AV: i="4.05,93,1146456000"; d="scan'208,217"; a="87973023:sNHT94345708" 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 k45G60vH007199 for ; Fri, 5 May 2006 12:06:00 -0400 (EDT) Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 5 May 2006 12:06:00 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: [Iptel] Suggestion for draft-munakata-iptel-isub-type-01.txt Date: Fri, 5 May 2006 12:05:56 -0400 Message-ID: <072C5B76F7CEAB488172C6F64B30B5E301703754@xmb-rtp-20b.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Iptel] Suggestion for draft-munakata-iptel-isub-type-01.txt Thread-Index: AcZwXcskHxb58+jHS9ywk/wBgT3dUg== From: "Michael Hammer \(mhammer\)" To: "IETF IPTEL WG" X-OriginalArrivalTime: 05 May 2006 16:06:00.0427 (UTC) FILETIME=[CD3D8BB0:01C6705D] X-Spam-Score: 0.0 (/) X-Scan-Signature: 31b28e25e9d13a22020d8b7aedc9832c 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="===============1188547487==" Errors-To: iptel-bounces@ietf.org This is a multi-part message in MIME format. --===============1188547487== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6705D.CD12EB7B" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6705D.CD12EB7B Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I was thinking that adding a binary example might make this much easier to comprehend. Below is some suggested text that could be added into the document somewhere. =20 begin/ =20 NSAP=3D20 octets =20 Octet Example 1 Example 2 Example 3 1 AFI 0101 0000 or 0100 1000 or 1111 1111 2 ? 0011 0001 (same) (same) 3 DSP 0011 0010 | | 4 | 0011 0011 v v 5 v 0011 0100 6 0011 0101 7 0011 0110 8 0011 0111 9 0011 1000 10 0100 1001 11 0100 0001 12 0100 0010 13 0100 0011 14 0100 0100 15 0100 0101 16 0100 0110 17 0100 0111 18 0100 1000 19 0100 1001 20 0100 1010 =20 Example 1: isub=3D123456789ABCDEFGHIJ;isub-type=3D"nsap-ia5" Note that: AFI (50) is not included, IDI is null (octet 2 is part of DSP), and=20 isub is 19 characters long =20 Example 2: isub=3D3132333435363738394142434445464748494A;isub-type=3D"nsap-bcd" Note that: AFI (48) is not included, IDI is null (octet 2 is part of DSP), and=20 isub is 38 characters long =20 Example 3: isub=3DFF3132333435363738394142434445464748494A;isub-type=3D"nsap" Note that: AFI (FF) is included, IDI may or may not be octet 2 value "31" or further values, and=20 isub is 40 characters long =20 /end =20 Comment: I selected FF arbitrarily and did not check to see whether it was assigned or not. It is=20 intended to represent a value for which we don't know and don't care so long as it is transmitted. Note that the trade-off between adding "-bcd" and not including "48" is minimal. =20 Thanks, Mike =20 ------_=_NextPart_001_01C6705D.CD12EB7B Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
I was = thinking that=20 adding a binary example might make this much easier to comprehend.  = Below=20 is some suggested text that could be added into the document=20 somewhere.
 
begin/
 
NSAP=3D20 octets
 
Octet    Example = 1   =20 Example 2    Example 3
 1   AFI 0101 = 0000 or=20 0100 1000 or 1111 1111
 2    ?  0011=20 0001     (same)      =20 (same)
 3   DSP 0011=20 0010       =20 |           =20 |
 4    |  0011=20 0011       =20 v           =20 v
 5    v  0011=20 0100
 6       0011=20 0101
 7       0011=20 0110
 8       0011=20 0111
 9       0011=20 1000
10       0100=20 1001
11       0100=20 0001
12       0100=20 0010
13       0100=20 0011
14       0100=20 0100
15       0100=20 0101
16       0100=20 0110
17       0100=20 0111
18       0100=20 1000
19       0100=20 1001
20       0100 1010
 
Example 1: =20 isub=3D123456789ABCDEFGHIJ;isub-type=3D"nsap-ia5"
   &n= bsp;       =20 Note=20 that:
          &nbs= p;   =20 AFI (50) is not=20 included,
          =     =20 IDI is null (octet 2 is part of = DSP), and=20
           &nb= sp;  =20 isub is 19 characters long
 
Example 2: =20 isub=3D3132333435363738394142434445464748494A;isub-type=3D"nsap-bcd"
&= nbsp;          =20 Note=20 that:
          &nbs= p;   =20 AFI (48) is not=20 included,
          =     =20 IDI is null (octet 2 is part of = DSP), and=20
           &nb= sp;  =20 isub is 38 characters long
 
Example 3: =20 isub=3DFF3132333435363738394142434445464748494A;isub-type=3D"nsap"
&nb= sp;          =20 Note=20 that:
          &nbs= p;   =20 AFI (FF) is=20 included,
          =     =20 IDI may or may not be octet 2 = value=20 "31" or further values, and=20
           &nb= sp;  =20 isub is 40 characters long
 
/end
 
Comment:  I selected FF arbitrarily and = did not=20 check to see whether it was assigned or not.  It is
intended to represent a value for which we = don't know=20 and don't care so long as it is transmitted.
Note that the = trade-off=20 between adding "-bcd" and not including "48" is = minimal.
 
Thanks,
Mike
 
------_=_NextPart_001_01C6705D.CD12EB7B-- --===============1188547487== 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 --===============1188547487==-- From iptel-bounces@ietf.org Sun May 07 01:15:11 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FcbbI-0005y4-Oc; Sun, 07 May 2006 01:14:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FcbbH-0005xz-Fn for iptel@ietf.org; Sun, 07 May 2006 01:14:35 -0400 Received: from agnada.com ([69.36.182.244]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FcbbE-0006cU-DI for iptel@ietf.org; Sun, 07 May 2006 01:14:34 -0400 Received: from [192.168.0.101] (S010600095b9792b5.vc.shawcable.net [70.79.6.118]) (authenticated) by agnada.com (8.11.6/8.11.6) with ESMTP id k475ETg30131; Sat, 6 May 2006 23:14:29 -0600 Message-ID: <445D8234.3020306@ntt-at.com> Date: Sat, 06 May 2006 22:14:28 -0700 From: Shida Schubert User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: "Michael Hammer (mhammer)" Subject: Re: [Iptel] Suggestion for draft-munakata-iptel-isub-type-01.txt References: <072C5B76F7CEAB488172C6F64B30B5E301703754@xmb-rtp-20b.amer.cisco.com> In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E301703754@xmb-rtp-20b.amer.cisco.com> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Cc: IETF IPTEL WG X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: shida@ntt-at.com List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org Few other reviewers did indeed suggest to add a table to make it easier for people to comprehend. And we really should have done that. Thanks for detailed suggestion, we will add this to appendix in the next revision. Regards Shida Schubert Michael Hammer (mhammer) wrote: > I was thinking that adding a binary example might make this much > easier to comprehend. Below is some suggested text that could be added > into the document somewhere. > begin/ > NSAP=20 octets > Octet Example 1 Example 2 Example 3 > 1 AFI 0101 0000 or 0100 1000 or 1111 1111 > 2 ? 0011 0001 (same) (same) > 3 DSP 0011 0010 | | > 4 | 0011 0011 v v > 5 v 0011 0100 > 6 0011 0101 > 7 0011 0110 > 8 0011 0111 > 9 0011 1000 > 10 0100 1001 > 11 0100 0001 > 12 0100 0010 > 13 0100 0011 > 14 0100 0100 > 15 0100 0101 > 16 0100 0110 > 17 0100 0111 > 18 0100 1000 > 19 0100 1001 > 20 0100 1010 > Example 1: isub=123456789ABCDEFGHIJ;isub-type="nsap-ia5" > Note that: > AFI (50) is not included, > IDI is null (octet 2 is part of DSP), and > isub is 19 characters long > Example 2: > isub=3132333435363738394142434445464748494A;isub-type="nsap-bcd" > Note that: > AFI (48) is not included, > IDI is null (octet 2 is part of DSP), and > isub is 38 characters long > Example 3: isub=FF3132333435363738394142434445464748494A;isub-type="nsap" > Note that: > AFI (FF) is included, > IDI may or may not be octet 2 value "31" or further values, and > isub is 40 characters long > /end > Comment: I selected FF arbitrarily and did not check to see whether it > was assigned or not. It is > intended to represent a value for which we don't know and don't care > so long as it is transmitted. > Note that the trade-off between adding "-bcd" and not including "48" > is minimal. > Thanks, > Mike > ------------------------------------------------------------------------ > > _______________________________________________ > 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 Tue May 09 05:39:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FdOg1-0005ri-Es; Tue, 09 May 2006 05:38:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FdOfz-0005qY-IX for iptel@ietf.org; Tue, 09 May 2006 05:38:43 -0400 Received: from smtp7.clb.oleane.net ([213.56.31.27]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdOfy-0005rh-5W for iptel@ietf.org; Tue, 09 May 2006 05:38:43 -0400 Received: from Pavillonquatre ([194.3.133.88]) by smtp7.clb.oleane.net with ESMTP id k499caiB020648 for ; Tue, 9 May 2006 11:38:36 +0200 Message-Id: <200605090938.k499caiB020648@smtp7.clb.oleane.net> From: "Chantal Ladouce" To: Date: Tue, 9 May 2006 11:37:22 +0200 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Thread-Index: AcZzTCvQrDFeAnuvSq6sPJ+hfB0Jpw== X-Spam-Score: 0.2 (/) X-Scan-Signature: 225414c974e0d6437992164e91287a51 Subject: [Iptel] Wireless/WiFi Convergence Conference 2006 - Paris - France 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="===============1974213007==" Errors-To: iptel-bounces@ietf.org This is a multi-part message in MIME format. --===============1974213007== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0282_01C6735C.EFC8FD70" This is a multi-part message in MIME format. ------=_NextPart_000_0282_01C6735C.EFC8FD70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit UMA how? IMS when? Don't miss the 2006 Wireless/WiFi Convergence Conference to be held next week in Paris (on May 16 to May 19). Distinguished experts and key players in the convergence field will address technical issues. Registration is still open. Get all details at: http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006intro.htm ------=_NextPart_000_0282_01C6735C.EFC8FD70 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

UMA how? = IMS when?

=

Don't miss the 2006 Wireless/WiFi Convergence Conference = to be held next week in Paris (on May 16 to May 19). Distinguished experts and key players in the convergence field will = address technical issues.

Registration is still = open.

Get all details = at:

 

http://www.upperside.fr/wirelessconvergence2006/wwconvergenc= e2006intro.htm

=

 

 

------=_NextPart_000_0282_01C6735C.EFC8FD70-- --===============1974213007== 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 --===============1974213007==-- From iptel-bounces@ietf.org Mon May 15 15:50:59 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ffj52-0005aV-Bl; Mon, 15 May 2006 15:50:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ffj4t-0005X7-Iu; Mon, 15 May 2006 15:50:03 -0400 Received: from willow.neustar.com ([209.173.53.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ffj4s-00053J-TU; Mon, 15 May 2006 15:50:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k4FJo21I002867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 May 2006 19:50:02 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Ffj4s-0007VE-E6; Mon, 15 May 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, 15 May 2006 15:50:02 -0400 X-Spam-Score: 0.3 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: iptel@ietf.org Subject: [Iptel] I-D ACTION:draft-ietf-iptel-tel-enumdi-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 --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 : The ENUM Dip Indicator parameter for the "tel" URI Author(s) : R. Stastny, et al. Filename : draft-ietf-iptel-tel-enumdi-04.txt Pages : 9 Date : 2006-5-15 This document defines a new parameter "enumdi" for the "tel" Uniform Resource Identifier (URI) to support the handling of ENUM queries in VoIP (Voice over Internet Protocol) network elements. A VoIP network element may receive an URI containing an E.164 number, where that URI contains an "enumdi" parameter. The presence of the "enumdi" parameter indicates that an ENUM query has already been performed on the E.164 number by a previous VoIP network element. Equally, if a VoIP network element sends such an URI, it asserts that an ENUM query has been carried out on this number. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-tel-enumdi-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-ietf-iptel-tel-enumdi-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-ietf-iptel-tel-enumdi-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. --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-5-15110802.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-tel-enumdi-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-tel-enumdi-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-5-15110802.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 Tue May 16 16:42:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg6ML-000345-BH; Tue, 16 May 2006 16:41:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg6MK-00033x-7k; Tue, 16 May 2006 16:41:36 -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 1Fg5im-0003UQ-EF; Tue, 16 May 2006 16:00:44 -0400 Received: from pine.neustar.com ([209.173.57.70]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Fg5YQ-0001aT-2q; Tue, 16 May 2006 15:50:06 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k4GJo1XO032593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 May 2006 19:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Fg5YP-0007kz-Mf; Tue, 16 May 2006 15:50:01 -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: Tue, 16 May 2006 15:50:01 -0400 X-Spam-Score: -2.6 (--) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: iptel@ietf.org Subject: [Iptel] I-D ACTION:draft-ietf-iptel-trunk-group-08.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-08.txt Pages : 17 Date : 2006-5-16 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-08.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-08.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-08.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-5-16132426.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-trunk-group-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-trunk-group-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-5-16132426.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 May 17 03:11:59 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FgGBg-0006Hj-2i; Wed, 17 May 2006 03:11:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FgGBe-0006HN-61 for iptel@ietf.org; Wed, 17 May 2006 03:11:14 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FgGBb-0005Qz-FK for iptel@ietf.org; Wed, 17 May 2006 03:11:14 -0400 Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-5.cisco.com with ESMTP; 17 May 2006 00:11:11 -0700 X-IronPort-AV: i="4.05,136,1146466800"; d="txt'?scan'208"; a="278064884:sNHT42407104" Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id k4H7BA2S007817 for ; Wed, 17 May 2006 00:11:10 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k4H7ADBL002223 for ; Wed, 17 May 2006 00:11:10 -0700 (PDT) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 May 2006 00:10:51 -0700 Received: from [65.241.177.248] ([10.21.121.229]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 May 2006 00:10:50 -0700 Message-ID: <446ACC79.6030404@cisco.com> Date: Wed, 17 May 2006 03:10:49 -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 References: In-Reply-To: Content-Type: multipart/mixed; boundary="------------000605010604030509080904" X-OriginalArrivalTime: 17 May 2006 07:10:50.0612 (UTC) FILETIME=[07419B40:01C67981] DKIM-Signature: a=rsa-sha1; q=dns; l=10009; t=1147849870; x=1148713870; c=relaxed/simple; s=sjdkim4001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:Jonathan=20Rosenberg=20 |Subject:Re=3A=20I-D=20ACTION=3Adraft-ietf-iptel-trunk-group-08.txt; X=v=3Dcisco.com=3B=20h=3DFefjzXuP2yIBkWn6ROeGz9Lwnrc=3D; b=hDRA0Z0lUCaydMFGUnF4GZdoZysAe25Q06go+q3SDYrWxa0MMNTQnOX9izUVIohCBFKnVu30 2qe+GcI3ElQkV3T3G5kGiUHlHpem4enQKU1yVDNBisuTOCB8zbT4llVk; Authentication-Results: sj-dkim-4.cisco.com; header.From=jdrosen@cisco.com; dkim=pass ( 42 extraneous bytes; sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 8a85b14f27c9dcbe0719e27d46abc1f8 Subject: [Iptel] Re: I-D ACTION:draft-ietf-iptel-trunk-group-08.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. --------------000605010604030509080904 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I've just sent a note to IESG asking them to consider this version for PS. Folks may be familiar with the proto process (http://www.ietf.org/internet-drafts/draft-ietf-proto-wgchair-doc-shepherding-06.txt), which requires the WG chair to help move the document along. As part of this, I do a writeup that describes the history of the document. Here is the writeup I sent, FYI. Thanks, Jonathan R. Internet-Drafts@ietf.org wrote: > 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-08.txt > Pages : 17 > Date : 2006-5-16 > > 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-08.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-08.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-08.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 -- 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 --------------000605010604030509080904 Content-Type: text/plain; name="trunk-group-shepherd-writeup.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="trunk-group-shepherd-writeup.txt" 1.a) Have the chairs personally reviewed this version of the Internet Draft (ID), and in particular, do they believe this ID is ready to forward to the IESG for publication? Which chair is the WG Chair Shepherd for this document? Yes, the chair (Jonathan Rosenberg) has personally reviewed this version of the document. The chair believes the I-D is ready to forward for publication. The sole chair is the shepherd. 1.b) Has the document had adequate review from both key WG members and key non-WG members? Do you have any concerns about the depth or breadth of the reviews that have been performed? The document has had review from key WG members. Besides a detailed review from the chair, the document was reviewed after IETF 61 from Rohan Mahy and Tom Taylor. Between the three, this brings adequate review of both telephony issues (Tom's speciality) along with general SIP and URI issues (Jonathan and Rohan). There are no concerns regarding lack of depth or breadth of reviews. The document has not had a review from outside of the working group. 1.c) Do you have concerns that the document needs more review from a particular (broader) perspective (e.g., security, operational complexity, someone familiar with AAA, internationalization, XML, etc.)? No. The document needs reviews from experts in SIP and telephony, and it has had those. 1.d) Do you have any specific concerns/issues with this document that you believe the ADs and/or IESG should be aware of? For example, perhaps you are uncomfortable with certain parts of the document, or have concerns whether there really is a need for it. In any event, if your issues have been discussed in the WG and the WG has indicated it that it still wishes to advance the document, detail those concerns in the write-up. The primary source of discomfort for the chair is merely that the document (and many of the others produced by the working group) serve the purpose of 'leaking' various pieces of PSTN functionality into SIP. However, there is no disagreement that the problem addressed by this specification needs to be resolved, nor is there dispute that this specification represents the best way to solve it at this time. It would just be nice if we didn't have to address these kinds of problems. Unfortunately we do. 1.e) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? Working group consensus is good. The group agreed to adopt the item in early 2003. The group itself is relatively small with just a few active participants. However, amongst those who do participate, the draft has good support and it has not been contentious. 1.f) Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarise the areas of conflict in separate email to the Responsible Area Director. (It should be separate email because this questionnaire will be entered into the tracker). No. 1.g) Have the chairs verified that the document checks out against all the ID nits? (see http://www.ietf.org/ID-Checklist.html). Boilerplate checks are not enough; this check needs to be thorough. Yes. 1.h) Has the document split its references into normative and informative? Yes. Are there normative references to IDs, where the IDs are not also ready for advancement or are otherwise in an unclear state? No. All normative references are to RFCs. The RFC Editor will not publish an RFC with normative references to IDs (will delay the publication until all such IDs are also ready for RFC publicatioin). If the normative references are behind, what is the strategy for their completion? On a related matter, are there normative references that are downward references, as described in BCP 97, RFC 3967 RFC 3967 [RFC3967]? No. Listing these supports the Area Director in the Last Call downref procedure specified in RFC 3967. 1.i) For Standards Track and BCP documents, the IESG approval announcement includes a write-up section with the following sections: * Technical Summary The trunk group extension to the tel URI defines two new URI parameters for use with the tel URI (defined in RFC 3966). These two new URI parameters, "tgrp" and "trunk-context" indicate the name and namespace scope for a trunk group. A trunk group is a collection of circuits in the Public Switched Telephone Network (PSTN) which are managed as a group. One trunk group, for example, can be used for toll free calls, while another one used for calls to a certain carrier, and another for calls to a certain local calling area. Consequently, when connecting calls from the PSTN into a VoIP network, and connecting calls from a VoIP network into the PSTN, it is necessary to convey trunk group information in the VoIP domain. For example, a SIP proxy may route a call towards a PSTN gateway, and need to indicate that a specific trunk group should be used. As another example, a call from a PSTN gateway towards a SIP proxy might need to indicate that the call arrived from a specific trunk group, so that the SIP proxy might make appropriate call routing decisions. The specification defines the syntax for these parameters, matching rules, and usage of them with SIP. * Working Group Summary The draft is a charter item of the IP Telephony (iptel) working group, and is targeted for Proposed Standard. It was adopted as a working group item in early 2003 and discussed on the mailing list and in many meetings since its adoption. * Protocol Quality The specification has been implemented in many products and there are known deployments of it. The specification itself has received reviews from telephony experts as well as SIP experts. --------------000605010604030509080904 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 --------------000605010604030509080904-- From iptel-bounces@ietf.org Wed May 24 15:50:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FizMv-0004Df-Fa; Wed, 24 May 2006 15:50:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FizMp-0004C0-5h; Wed, 24 May 2006 15:50:03 -0400 Received: from oak.neustar.com ([209.173.53.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FizMn-0003EO-SV; Wed, 24 May 2006 15:50:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k4OJo1et018460 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 May 2006 19:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FizMn-0004MK-LY; Wed, 24 May 2006 15:50:01 -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: Wed, 24 May 2006 15:50:01 -0400 X-Spam-Score: 0.3 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: iptel@ietf.org Subject: [Iptel] I-D ACTION:draft-ietf-iptel-tel-np-10.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 : NP Parameters for the "tel" URI Author(s) : J. Yu Filename : draft-ietf-iptel-tel-np-10.txt Pages : 15 Date : 2006-5-24 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-tel-np-10.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-tel-np-10.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-tel-np-10.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-5-24132908.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-tel-np-10.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-tel-np-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-5-24132908.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 May 24 18:53:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fj2DA-0002sI-Lq; Wed, 24 May 2006 18:52:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fj2D9-0002sD-8V for iptel@ietf.org; Wed, 24 May 2006 18:52:15 -0400 Received: from web36406.mail.mud.yahoo.com ([209.191.85.141]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Fj2D7-0007Lh-Vz for iptel@ietf.org; Wed, 24 May 2006 18:52:15 -0400 Received: (qmail 65199 invoked by uid 60001); 24 May 2006 22:52:12 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=NgYKDv6LyA1JJhL6NJK9NFGIrQQ5SaQvR5FASCokhZ5Za3ppqMim3OctwHR1Nwxo4RmKMMoI8DoylTL2BGs4918hDdihXFvrndVNQQnwtiiQuL8VhLk+35G6gKcTiktc5BWElTz7laXr+LKq8tmma5IdOVNScbwdIVmj9po63TM= ; Message-ID: <20060524225212.65197.qmail@web36406.mail.mud.yahoo.com> Received: from [201.198.239.67] by web36406.mail.mud.yahoo.com via HTTP; Wed, 24 May 2006 17:52:12 CDT Date: Wed, 24 May 2006 17:52:12 -0500 (CDT) From: Randall Solano To: iptel@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Subject: [Iptel] Firewall 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 All: Is it necesary to use Firewall between MGC and MG? i.e.: MGC-------/firewall/-------MG Cheers, Ran __________________________________________________ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.espanol.yahoo.com/ _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Fri May 26 15:47:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjiGp-00062G-Tg; Fri, 26 May 2006 15:46:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjiGo-000625-Kp; Fri, 26 May 2006 15:46:50 -0400 Received: from willow.neustar.com ([209.173.53.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FjiGm-0004kV-DG; Fri, 26 May 2006 15:46:50 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k4QJkm1I013972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 26 May 2006 19:46:48 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FjiGm-0005FQ-79; Fri, 26 May 2006 15:46:48 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Fri, 26 May 2006 15:46:48 -0400 X-Spam-Score: 0.1 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: iptel@ietf.org Subject: [Iptel] Last Call: 'The ENUM Dip Indicator parameter for the "tel" URI' to Proposed Standard (draft-ietf-iptel-tel-enumdi) X-BeenThere: iptel@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: IP Telephony List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: iptel-bounces@ietf.org The IESG has received a request from the IP Telephony WG to consider the following document: - 'The ENUM Dip Indicator parameter for the "tel" URI ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2006-06-09. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-iptel-tel-enumdi-04.txt _______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel From iptel-bounces@ietf.org Fri May 26 15:50:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjiK5-0002b6-HX; Fri, 26 May 2006 15:50:13 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjiJu-0002Qs-Nw; Fri, 26 May 2006 15:50:02 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=pine.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FjiJu-0005L9-Bi; Fri, 26 May 2006 15:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k4QJo1XO007679 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 26 May 2006 19:50:02 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FjiJt-0005fq-QJ; Fri, 26 May 2006 15:50:01 -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: Fri, 26 May 2006 15:50:01 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: iptel@ietf.org Subject: [Iptel] I-D ACTION:draft-ietf-iptel-tel-reg-02.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 : The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter Registry Author(s) : C. Jennings, V. Gurbani Filename : draft-ietf-iptel-tel-reg-02.txt Pages : 8 Date : 2006-5-26 This document creates an Internet Assigned Number Authority (IANA) registry for tel Uniform Resource Identifier (URI) parameters and their values. It populates the registry with the parameters defined in the tel URI specification, along with the parameters in tel URI extensions defined for number portability and trunk groups. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-tel-reg-02.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-tel-reg-02.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-tel-reg-02.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-5-26141219.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-tel-reg-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-tel-reg-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-5-26141219.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--