From owner-iptel-outgoing@lists.research.bell-labs.com Mon Jan 3 10:28:25 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02666 for ; Mon, 3 Jan 2000 10:28:25 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id E3B3F52D6; Mon, 3 Jan 2000 10:23:28 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 5CDA952DF; Mon, 3 Jan 2000 10:23:27 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com To: iptel@lists.research.bell-labs.com Date: Mon, 3 Jan 2000 10:21:14 -0500 Message-ID: <001d01bf55fd$c37254c0$0401a8c0@oleane.com> From: "Peter Lewis" Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk To: Subject: VoDSL 2000 Conference Date: Mon, 3 Jan 2000 16:18:09 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001A_01BF5606.1FBDFB00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 This is a multi-part message in MIME format. ------=_NextPart_000_001A_01BF5606.1FBDFB00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, =20 The VoDSL 2000 Conference will stand in Paris next 28-31 March. Key = speakers, case studies: take a look at: = http://www.upperside.fr/bavodsl.htm =20 Regards ------=_NextPart_000_001A_01BF5606.1FBDFB00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello,

The VoDSL 2000 Conference will stand = in Paris=20 next 28-31 March. Key speakers, case studies: take a look at: http://www.upperside.fr/bavo= dsl.htm

Regards

------=_NextPart_000_001A_01BF5606.1FBDFB00-- --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Fri Jan 7 20:05:45 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29724 for ; Fri, 7 Jan 2000 20:05:45 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id 51F5752D5; Fri, 7 Jan 2000 19:53:55 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id B3B0C52BB; Fri, 7 Jan 2000 19:53:49 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com Date: Fri, 7 Jan 2000 19:51:43 -0500 (EST) From: Henning Schulzrinne Message-Id: <200001080051.TAA16206@tune.cs.columbia.edu> To: iptel@lists.research.bell-labs.com Subject: CFP on JCN Special Issue on Internet QOS - Deadline Extended List: iptel@lists.research.bell-labs.com Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk JOURNAL OF COMMUNICATIONS AND NETWORKING (JCN) CALL FOR PAPERS - SPECIAL ISSUE ON QoS IN IP NETWORKS JUNE, 2000 ---> DEADLINE EXTENDED to January 31, 2000 A Special Issue of JCN dedicated to the realization of QoS-sensitive services in IP networks will be published in June, 2000. It will be Guest Edited by Prof. Henning Schulzrinne of Columbia University, Prof. Hideo Miyahara of Osaka University, and Prof. Luigi Fratta of the University of Milan. The topics include but are not limited to: Differentiated Services Integrated Services MPLS Real-time multicast IP network traffic engineering Performance measurement and evaluation Pricing and billing User perception of QOS QOS policy management Adaptive and other new service models Light-weight reservation protocols and aggregation Continuing JCN's tradition of fast turnaround together with full peer reviews, the following schedule has been set: Jan. 31, 2000 Submit manuscript via web page (see below) Mar. 31, 2000 First reviews returned to author, revisions returned within three weeks June, 2000 Special Issue published The guest editors are Prof. Luigi Fratta Prof. Hideo Miyahara Prof. Henning Schulzrinne Papers should be submitted via the procedure described at http://www.cs.columbia.edu/~hgs/edas/JCN Only PostScript and PDF formats are accepted. Further information about JCN is available at http://JCN.snu.ac.kr. JCN is a high-quality quarterly archival journal, published by the Korean Institute of Communications Sciences with the technical cosponsorship of the IEEE Communications Society, covering the fields of Communication Theory and Systems, Wireless Communications, and Networks and Services. JCN began publication in March, 1999. --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Tue Jan 11 05:49:16 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03220 for ; Tue, 11 Jan 2000 05:49:16 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id 8054152BB; Tue, 11 Jan 2000 05:43:26 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id F310452D6; Tue, 11 Jan 2000 05:43:25 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com To: iptel@lists.research.bell-labs.com Date: Tue, 11 Jan 2000 05:40:21 -0500 Message-ID: <007c01bf5c1f$e584f220$0401a8c0@oleane.com> From: "Peter Lewis" Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk To: Subject: SIP 2000 Date: Tue, 11 Jan 2000 11:37:43 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0079_01BF5C28.461CC100" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 This is a multi-part message in MIME format. ------=_NextPart_000_0079_01BF5C28.461CC100 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SIP 2000: beyond H.323?=20 Discussing and debating in Paris May 10-12. A CFP is online at: http://www.upperside.fr/basip.htm ------=_NextPart_000_0079_01BF5C28.461CC100 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

SIP 2000: beyond H.323? =

Discussing and debating in Paris May = 10-12.

A CFP is online at:

http://www.upperside.fr/basip.= htm

------=_NextPart_000_0079_01BF5C28.461CC100-- --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Wed Jan 12 00:58:03 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28055 for ; Wed, 12 Jan 2000 00:58:02 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id ED87052DC; Tue, 11 Jan 2000 23:57:03 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 4B85052DE; Tue, 11 Jan 2000 23:57:02 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com From: Message-Id: <3.0.5.32.20000111184831.0090a970@colmar.colmar.uha.fr> X-Sender: conf@colmar.colmar.uha.fr X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 11 Jan 2000 18:48:31 +0100 To: conf@colmar.colmar.uha.fr Subject: ECUMN - Extended Deadline Feb 11th. Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA28055 My sincere apology if you receive multiple copies of this CFP. Please feel free to pass the CFP to anyone who might be interested. Kind regards, ------------------------------------------------------------------------- CALL FOR PAPERS 1st IEEE European Conference on Universal Multiservice Networks ECUMN'2000 IP Networks Versus Conventional Switched Networks October 2-4, 2000 - CREF, Colmar, France URL: http://iutsun1.colmar.uha.fr/ECUMN2000.html Sponsors are the following national scientific societies in Europe, which cooperate under the roof of: EUREL, Brussels, Belgium: AEI, Milano (Italy), IEE, London (UK), ÖVE/GIT, Vienna (Austria), SEE, Paris (France), SEV/ITG, Fehraltorf, (Switzerland), VDE/ITG, Frankfurt (Germany), WSES as well as the IEEE Communications and Computer. Supported by: France Telecom Alcatel Newbridge Other Supporters pending: Conference Scope: This conference follows the two successful ATM conferences events held in Colmar, France in 1998 and 1999. The conference scope has been extended to deal with the different topics related to Multiservice Network Architectures, and Implementation, including among others, protocols, signaling, traffic flow, addressing schemes, … Fundamental questions still have to find an answer, such as: How will the Internet, symbol of freedom, compete with the world of traditional carrier networks or cooperate with it? Will alternate Technologies be needed to meet high level quality of service requirements ? What restrictions, if any, will result on the desired degree of freedom ? Emphasis shall be put upon network convergence, including fixed/mobile convergence satisfying the needs of person to person communications, as well as Information and Entertainment applications. The scope of ECUMN'2000 encompasses but is not limited to: Evolution of Telecommunication Networks Architecture: * Core network * Access networks * CPN (Customer Premise Networks including home networks) * Multiservice mobile networks * Interoperability issues, Interfaces and Reference points Packet, frame and cell protocols: * Addressing * Multicasting * Switching and routing * Signaling * Traffic control and QoS Network management and control: * Network design - Migration strategies * Active networks versus Intelligent networks Service impact (multimedia, VPN, ...) on network architecture: * Fixed-Mobile Convergence * Packetized voice * Experimentation and fields trials With such a variety of problems to be solved, and such high economical interests at stake there is a definite interest to exchange ideas, technical results and proposals, between the academic and industrial communities and this is the major goal of the conference. Instructions for Authors: Mail four paper versions or E-mail preferably in Word 6 format, or alternately a postscript version of a 2000-word extended abstract summarizing an original work finalized or in progress. All the manuscripts must be written in English. The top of the first page of each paper should include the title of the paper, authors' name, position, address, telephone and fax numbers, Email of the author responsible for correspondence and a list of four keywords at least. Authors of accepted papers will be invited to submit full-length manuscripts for inclusion in the proceedings. All submitted papers should be sent to the following address: Pascal LORENZ University of Haute Alsace IUT - Department GTR 34 rue du Grillenbreit 68008 Colmar, France Phone: +33 389202366 Fax: +33 389202359 Mobile: +33 603658042 E-mail: lorenz@colmar.uha.fr Important Deadlines: Extended abstract due: February 11, 2000 Notification of acceptance: April 10, 2000 Camera-ready full papers due (2 columns, 8 pages max): June 10, 2000 Best papers will be forwarded for consideration in a special issue of the journal "Annals of telecommunications". A competition for the best student paper will be organized to recognize and encourage excellence in graduate studies. Tutorials: Tutorials will present overviews of current high interest topics. Proposals tutorials are due by February 11, 2000. Conference Committees General Chair: Pascal Lorenz (France) - University of Haute Alsace Technical Program Chair: Annie Gravey (France) - France Telecom Cnet Tutorials Chair: Sylvie Ritzenthaler (France) - Newbridge Learned Societies Liaison Chair: Renato Israel (France) - SEE Prosper Chemouil (France) - France Telecom Cnet Michel Levy (France) - Alcatel Jean-Louis Pernin (France) - Consultant Guy Pujolle (France) - University of Versailles-Saint-Quentin Pierre Rolin (France) - France Telecom Cnet Scientific Program Committee: H. Afifi (France) - ENST Bretagne E. Biersack (France) - Eurecom M. Boari (Italy) - University of Bologna D. Bonjour (France) - France Telecom Cnet T. Braun (Switzerland) - University of Berne P. Brown (France) - France Telecom Cnet P. Chemouil (France) - France Telecom Cnet G. Colombo (Italy) - CSELT J.P. Coudreuse (France) - Mitsubishi W. Dabbous (France) - INRIA A. Danthine (Belgium) - University libre of Liège M . Diaz (France) - LAAS M. Erradi (Morocco) - ENSIAS S. Fdida (France) - LIP6 F. Ferrero (Italy) - CSELT G. Fiche (France) - Alcatel CIT A. Gravey (France) - France Telecom Cnet S.J. Halme (Finland) - Helsinki University of Technology G. Hébuterne (France) - INT H.G. Hegering (Germany) - University of Munich D. Hutchinson (UK) - Lancaster R. Israel (France) - SEE A. Jajszczyk (Poland) - University of Mining & Metallurgy M. Joubert (France) - Cegetel F. Kamoun (Tunisia) - ENSI M. Karpov (Russia) - St Petersburg University P. Key (UK) - Microsoft D. Kofman (France) - ENST Paris U. Korner (Sweden) - University of Lund U . Krieger (Germany) - Deutsche Telecom P. Kuhn (Germany) - University of Stuttgart G.S. Kuo (Taiwan) - National Central University M. Labetoulle (France) - Institut Eurecom Sophia-Antipolis M. Le Boudec (Switzerland) - EPFL F. Le Faucheur (France) - Cisco G. Leduc (Belgium) - University of Liege Y. Legrand (France) - Bouygues M. Levy (France) - Alcatel P. Lorenz (France) - University of Haute Alsace M. Loukola (Finland) - Helsinki University of Technology B. Maglaris (Greece) - National Technical University Athens H. Maher (Switzerland) - EPFL Z. Mammeri (France) - University of Toulouse S. Martignoni (Switzerland) - Ascom TechLtd N. Mastorakis (Greece) - Military Institutions of University Education U. Mocci (Italy) - FUB M. Nunes (Portugal) - IST/INESC G. Omiyar (USA) - Computer Sciences Corp J.J. Pansiot (France) - University of Strasbourg J.L. Pernin (France) - Consultant G. Petit (Belgium) - Alcatel Anvers M. Potts (Switzerland) - Martel G. Pujolle (France) - University of Versailles-Saint-Quentin S. Rao (Switzerland) - TELSCOM M. Renaldo (France) - SAGEM M. Riguidel (France) - Thomson S. Ritzenthaler (France) - Newbridge J. Roberts (France) - France Telecom Cnet P. Rolin (France) - France Telecom Cnet R. Schutz (France) - CS Telecom H. Tobiet (France) - Clemessy S. Tohme (France) - ENST Paris L. Toutain (France) - ENST Bretagne P. Tran Gia (Germany) - University of Würzburg P. Van Heck (The Netherlands) - Erasmus University P. Van Mieghem (The Netherlands) - Delft University of Technology E. Vazquez Gallo (Spain) - University of Madrid V.A. Villagra (Spain) - University of Madrid M. Villen (Spain) - Telefonica I+D --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Fri Jan 14 11:19:16 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19231 for ; Fri, 14 Jan 2000 11:19:16 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id E52EE52E8; Fri, 14 Jan 2000 11:11:28 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 6559552EB; Fri, 14 Jan 2000 11:11:27 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com Subject: TRIP To: iptel@lists.research.bell-labs.com From: Spencer.Giacalone@predictive.com Date: Fri, 14 Jan 2000 11:09:30 -0500 Message-ID: X-MIMETrack: Serialize by Router on Athena/Predictive(Release 5.0.2b (Intl)|16 December 1999) at 01/14/2000 11:11:06 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk Group, I read the TRIP draft, and I had some thoughts and questions: Section 5.2 (LS-IDs) Will TRIP use BGP "peering" statements? if not, would being able to have different LS-IDs be confusing or cause network (config) problems? What is the advantage of having different LS-IDs if you are not peering Differently (using peering statements)? Section 5.2.1.1, (IPSec) Is there any reason TRIP _couldn't_ rely on IPSec for security? Conversely, what about implementations that don't support IPSec? There might be a problem with problem re-hashing changing headers, etc, though I think the IPv6 specs address that. Would TRIP's specification seem incomplete without security of it's own? Section 5.2.1.2, (Capabilities) Might we define more "defined capabilities" around the types of service needed by the end stations, or perhaps the throughput of the end station's connection? The way GARP does this is interesting. Section 5.3.3.2, (next-hop) Being able to set the next-hop is nice, but would there be confusion pertaining to how next-hop should be implemented? Are the current the definition of default behaviors specific enough? Section 5.3.4.7 (community) Why _wouldn't_ we want the community attribute? TRIP relies on many BGP features, why not use this one as well? Section 6.3.1 (port addresses) In my opinion, I it is not necessary to have a subnetwork_address_field. However, I do think that next hop ITAD should be included, as filtering, etc may be based on this. Section 6.5 (routed path) I can see how a "routed path" might be more useful than an "advertisement path". Wouldn't one always prefer to know the path the _will_ be taken? Does TRIP need both advertisement path _and_ routed path? Would the Routed Path attribute be more useful if we relax some of the limitations on when an LS can change it (update the path), allowing it to be used more often? Section 6.9 Agree with updating topology when peer sets change, not using an intra-ITAD keepalive. Terminology Is it confusing for the TRIP spec use the term "route" when referring to "call" routes _and_ IP routes? Spencer Giacalone --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Fri Jan 14 14:38:25 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21643 for ; Fri, 14 Jan 2000 14:38:24 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id A319352EF; Fri, 14 Jan 2000 14:33:26 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 0330F52F0; Fri, 14 Jan 2000 14:33:25 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com Message-ID: <387F7985.4DBA6CAC@cisco.com> Date: Fri, 14 Jan 2000 11:31:17 -0800 From: "Hussein F. Salama" Reply-To: hsalama@cisco.com Organization: Cisco Systems X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Spencer.Giacalone@predictive.com Cc: iptel@lists.research.bell-labs.com Subject: Re: TRIP References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk Content-Transfer-Encoding: 7bit Spencer, Thanks for your comments. Below are responses to some of your questions. Hussein Spencer.Giacalone@predictive.com wrote: > > Group, > > I read the TRIP draft, and I had some thoughts and questions: > > Section 5.2 (LS-IDs) > Will TRIP use BGP "peering" statements? if not, would being able to have different LS-IDs be confusing or cause network (config) problems? > What is the advantage of having different LS-IDs if you are not peering > Differently (using peering statements)? Currently, TRIP's design focuses on only on address family: E.164. However, TRIP is generic enough to support multiple address families in the future. Different address families may be used by different applications. Each application/address family may have different requirements with respect to: - which LSs to peer with - defining the ITAD topology and boundaries Permitting the same LS to use different LS-IDs with different peers makes the above requirements possible. The effect will be like having multiple logical LSs in the same box. > > Section 5.2.1.1, (IPSec) > Is there any reason TRIP _couldn't_ rely on IPSec for security? Conversely, what about > implementations that don't support IPSec? There might be a problem with > problem re-hashing changing headers, etc, though I think the IPv6 specs > address that. Would TRIP's specification seem incomplete without security > of it's own? > > Section 5.2.1.2, (Capabilities) > Might we define more "defined capabilities" around the types of service > needed by the end stations, or perhaps the throughput of the end station's > connection? The way GARP does this is interesting. Such capabilities will be very difficult to aggregate, and I prefer to keep them out of TRIP. Or, if there is real need for such capabilities, they can be defined as optional attributes in separate drafts, similar to what has been decided for the cost and capacity attributes. > > Section 5.3.3.2, (next-hop) > Being able to set the next-hop is nice, but would there be confusion > pertaining to how next-hop should be implemented? Are the current > the definition of default behaviors specific enough? I don't think TRIP should address this issue. In some networks TRIP will be configured to set a new next hop at every intermediate ITAD along the advertisement route while in other networks TRIP LSs will only when call routes are aggregated. > > Section 5.3.4.7 (community) > Why _wouldn't_ we want the community attribute? TRIP relies on many BGP > features, why not use this one as well? The consensus at the last meeting was to add the community attribute to TRIP. > > Section 6.3.1 (port addresses) > In my opinion, I it is not necessary to have a subnetwork_address_field. > However, I do think that next hop ITAD should be included, as filtering, etc > may be based on this. > > Section 6.5 (routed path) > I can see how a "routed path" might be more useful than an "advertisement path". > Wouldn't one always prefer to know the path the _will_ be taken? Does TRIP need both advertisement path _and_ routed path? > The advertisement path is definitely needed to prevent advertisement loops. The routed path is useful, because it tracks the actual signaling path. > Would the Routed Path attribute be more useful if we relax some of the limitations on when an LS can change it (update the path), allowing > it to be used more often? What limitations are you referring to? > > Section 6.9 > Agree with updating topology when peer sets change, not using an intra-ITAD keepalive. > > Terminology > Is it confusing for the TRIP spec use the term "route" when referring > to "call" routes _and_ IP routes? Agreed, we'll revise this in a future revision of the draft. > > Spencer Giacalone > > --------- > This message came from the IETF IPTEL Working Group Mailing List. -- Hussein F. Salama Cisco Systems Mail Stop SJC6/3, 170 W. Tasman Drive, San Jose, CA 95134 Voice: +1 (408) 527-7147, Fax: +1 (408) 527-1714 --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Sun Jan 16 23:34:32 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15654 for ; Sun, 16 Jan 2000 23:34:32 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id 743F452D4; Sun, 16 Jan 2000 23:17:29 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 9A79E52BB; Sun, 16 Jan 2000 23:17:22 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com From: Mikhail Smirnov Date: Fri, 14 Jan 2000 22:37:30 +0100 Message-Id: <200001142137.WAA18984@dumbo.fokus.gmd.de > To: iptel@lists.research.bell-labs.com Subject: FYI: IPTel'2000 CfP Cc: smirnow@fokus.gmd.de X-Sun-Charset: US-ASCII Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk ------------------------------------------------------------------------ Call for Papers 1st IP Telephony workshop IPTel'2000 12- 13 April 2000 in Berlin, Germany http://www.fokus.gmd.de/events/iptel2000/ iptel2000@fokus.gmd.de Ext. abstracts submission (~2K words): 31.Jan.2000 Authors notification of acceptance: 29.Feb.2000 Camera-ready abstracts and slides: 31.Mar.2000 Invited talks include H. Schulzrinne The objective of the First IP Telephony Workshop is to bring together researchers, developers, vendors and service providers working in the IP telephony area to participate actively in a discussion on recent deployment experiences, innovative results and future directions. Topics include but are not limited to: Basic Technologies (SIP, ...), IP-Telephony Services, Business Deployment, Implementation reports. Demonstrations are welcome ------------------------------------------------------------------------ sorry if duplicated --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Tue Jan 18 14:01:52 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04687 for ; Tue, 18 Jan 2000 14:01:51 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id 3A33852E3; Tue, 18 Jan 2000 13:50:00 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 3825752E2; Tue, 18 Jan 2000 13:49:53 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com Message-ID: <3884B752.402CAE7F@dynamicsoft.com> Date: Tue, 18 Jan 2000 13:56:18 -0500 From: Jonathan Rosenberg Organization: dynamicsoft X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "James M. Polk" Cc: sip@lists.research.bell-labs.com, "iptel, list" Subject: Re: Gateways and registration References: <4.1.20000118112613.00cd1270@diablo.cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk Content-Transfer-Encoding: 7bit "James M. Polk" wrote: > > All > > Parallel question on the reliance of TRIP -- isn't it based on using > BGP? If that is strickly true, what happens to the SIP Device if BGP > isn't deployed within a VoIP network domain that still wants to locate > the Gateway? TRIP borrows many ideas from BGP, but it in no way whatsoever requires BGP to actually be running on routers in the network. TRIP runs at the application layer, between location servers. It doesn't matter one drop what the underlying layer 3 routing protocols are. -Jonathan R. -- Jonathan D. Rosenberg 200 Executive Drive Chief Scientist Suite 120 dynamicsoft West Orange, NJ 07052 jdrosen@dynamicsoft.com FAX: (732) 741-4778 http://www.cs.columbia.edu/~jdrosen PHONE: (732) 741-7244 http://www.dynamicsoft.com --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Wed Jan 19 20:16:29 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07099 for ; Wed, 19 Jan 2000 20:16:27 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id D323C52AB; Wed, 19 Jan 2000 20:11:28 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 4C7EE52DF; Wed, 19 Jan 2000 20:11:28 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com Message-ID: <38865FD3.AE5F7CD2@nortelnetworks.com> Date: Wed, 19 Jan 2000 20:07:31 -0500 From: "Matt Squire" Organization: Nortel Networks X-Mailer: Mozilla 4.7 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: hsalama@cisco.com Cc: Spencer.Giacalone@predictive.com, iptel@lists.research.bell-labs.com Subject: Re: TRIP References: <387F7985.4DBA6CAC@cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk Content-Transfer-Encoding: 7bit A couple additional comments... > > > > Section 5.2.1.1, (IPSec) > > Is there any reason TRIP _couldn't_ rely on IPSec for security? Conversely, what about > > implementations that don't support IPSec? There might be a problem with > > problem re-hashing changing headers, etc, though I think the IPv6 specs > > address that. Would TRIP's specification seem incomplete without security > > of it's own? > > We couldn't come up with any reason why IPSEC couldn't be relied on for security, except of course if an implentation that didn't support it. In the upcoming draft, we've removed references to bgp authentication mechanisms, added some text for signing individual attributes (what we called 'next-hop security' at the last ietf), but have yet to really address the use of IPSEC with regards to the keying issues. That should come in the next round I hope. > > > > Section 6.3.1 (port addresses) > > In my opinion, I it is not necessary to have a subnetwork_address_field. > > However, I do think that next hop ITAD should be included, as filtering, etc > > may be based on this. > > This is pretty much what we went with in the upcoming version. - Matt --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Mon Jan 24 06:46:37 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01545 for ; Mon, 24 Jan 2000 06:46:37 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id 0C60252C4; Mon, 24 Jan 2000 06:41:29 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 744D652BB; Mon, 24 Jan 2000 06:41:28 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com Message-Id: <200001241141.GAA01384@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: iptel@lists.research.bell-labs.com From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-iptel-trip-01.txt Date: Mon, 24 Jan 2000 06:41:00 -0500 Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk --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 : Telephony Routing over IP (TRIP) Author(s) : J. Rosenberg, H. Salama, M. Squire Filename : draft-ietf-iptel-trip-01.txt Pages : 62 Date : 21-Jan-00 This document presents the Telephony Routing over IP (TRIP). TRIP is a policy driven inter-administrative domain protocol for advertising the reachability of telephony destinations between location servers, and for advertising attributes of the routes to those destinations. TRIP's operation is independent of any signaling protocol, hence TRIP can serve as the telephony routing protocol for any signaling protocol. The Border Gateway Protocol (BGP-4) is used to distribute routing information between administrative domains. TRIP is used to distribute telephony routing information between telephony administrative domains. The similarity between the two protocols is obvious, and hence TRIP is modeled after BGP-4. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-trip-01.txt 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-trip-01.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-trip-01.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: <20000121104252.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-trip-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-trip-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000121104252.I-D@ietf.org> --OtherAccess-- --NextPart-- --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Wed Jan 26 05:40:17 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00907 for ; Wed, 26 Jan 2000 05:40:16 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id C39F052E3; Wed, 26 Jan 2000 05:35:27 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 4484752E7; Wed, 26 Jan 2000 05:35:27 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com To: iptel@lists.research.bell-labs.com Date: Wed, 26 Jan 2000 05:31:24 -0500 Message-ID: <008601bf67e8$1fef18e0$0401a8c0@oleane.com> From: "Peter Lewis" Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk To: Subject: SIP 2000 Call for Paper Date: Wed, 26 Jan 2000 11:28:41 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0083_01BF67F0.7F6990E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 This is a multi-part message in MIME format. ------=_NextPart_000_0083_01BF67F0.7F6990E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SIP 2000: Beyond H.323? A scientific committe composed of the most = eminent experts in this technology will review the abstracts submitted = from the Call For Papers: http://www.upperside.fr/basip.htm Take a look at the exhibition list. ------=_NextPart_000_0083_01BF67F0.7F6990E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

SIP 2000: Beyond H.323? A scientific = committe=20 composed of the most eminent experts in this technology will review the=20 abstracts submitted from the Call For Papers:

http://www.upperside.fr/basip.= htm

Take a look at the exhibition=20 list.

------=_NextPart_000_0083_01BF67F0.7F6990E0-- --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Fri Jan 28 02:20:50 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03492 for ; Fri, 28 Jan 2000 02:20:49 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id 418D052B6; Fri, 28 Jan 2000 02:13:47 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id AD50552BB; Fri, 28 Jan 2000 02:13:46 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com To: iptel@lists.research.bell-labs.com Date: Thu, 27 Jan 2000 02:54:34 -0500 Message-ID: From: P A Centre Visitor Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk To: Subject: RE: IEEE ICON' 2000 Conference - Call for Papers, Tutorials ... Date: Thu, 27 Jan 2000 15:48:17 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="ISO-8859-1" Dear All >The 8th IEEE International Conference On Networks will be held from >September 5- 8, 2000 in Singapore. ]The aim of the conference is to >provide >an international forum for experts to promote, share and discuss various >>issues and developments in the broad field of computer and communication networks. >>We thus seek and solicit your contributions >in the form of original/unpublished papers, tutorials, and topics for >special sessions/panel discussions. More information on the scope of the conference and the guidelines for the submission of contributions can >>>be obtained at this web site : http://www.comp.nus.edu.sg/~icon/ > >We look forward to your participation. Thank you. > >Icon 2000 organizing Committee Best Regards Catherine Kua (Mrs) ICON Secretariat c/o Professional Activities Centre Faculty of Engineering Tel: (65) 8745113 Fax: (65) 8745097 Email: engpac@nus.edu.sg --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Fri Jan 28 06:56:18 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06009 for ; Fri, 28 Jan 2000 06:56:18 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id B187D52D5; Fri, 28 Jan 2000 06:44:01 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 100EF52AB; Fri, 28 Jan 2000 06:43:55 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com Message-Id: <200001281141.GAA05573@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: iptel@lists.research.bell-labs.com From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-iptel-cpl-framework-02.txt Date: Fri, 28 Jan 2000 06:41:20 -0500 Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk --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 : Call Processing Language Framework and Requirements Author(s) : J. Lennox, H. Schulzrinne Filename : draft-ietf-iptel-cpl-framework-02.txt Pages : 25 Date : 27-Jan-00 A large number of the services we wish to make possible for Internet telephony require fairly elaborate combinations of signalling operations, often in network devices, to complete. We want a simple and standardized way to create such services to make them easier to implement and deploy. This document describes an architectural framework for such a mechanism, which we call a call processing language. It also outlines requirements for such a language. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-cpl-framework-02.txt 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-cpl-framework-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-cpl-framework-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: <20000127125914.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-cpl-framework-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-cpl-framework-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000127125914.I-D@ietf.org> --OtherAccess-- --NextPart-- --------- This message came from the IETF IPTEL Working Group Mailing List. From owner-iptel-outgoing@lists.research.bell-labs.com Mon Jan 31 02:02:53 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24660 for ; Mon, 31 Jan 2000 02:02:52 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id 7264152BB; Mon, 31 Jan 2000 01:57:30 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id C6E6752C4; Mon, 31 Jan 2000 01:57:29 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com Message-ID: <38953257.E223EFAD@dynamicsoft.com> Date: Mon, 31 Jan 2000 01:57:27 -0500 From: Jonathan Rosenberg Organization: dynamicsoft X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "iptel, list" Subject: [Fwd: I-D ACTION:draft-ietf-iptel-cpl-framework-02.txt] Content-Type: multipart/mixed; boundary="------------DD244FFE6B5F600A061BDE91" Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk This is a multi-part message in MIME format. --------------DD244FFE6B5F600A061BDE91 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Folks, As you may recall, we issued last call on this during the DC IETF. This revision incorporates comments received during the meeting, plus some additional cleanup. As there is no new content, I've sent it to IESG for consideration as an informational RFC. Thanks, Jonathan R. -- Jonathan D. Rosenberg 200 Executive Drive Chief Scientist Suite 120 dynamicsoft West Orange, NJ 07052 jdrosen@dynamicsoft.com FAX: (732) 741-4778 http://www.cs.columbia.edu/~jdrosen PHONE: (732) 741-7244 http://www.dynamicsoft.com --------------DD244FFE6B5F600A061BDE91 Content-Type: message/rfc822 Content-Disposition: inline Received: from wodc7mr3.ffx.ops.us.uu.net by wodc7ps1.ffx.ops.us.uu.net with ESMTP (peer crosschecked as: wodc7mr3.ffx.ops.us.uu.net [192.48.96.19]) id QQhzyd01090; Fri, 28 Jan 2000 11:55:15 GMT Received: from lists.research.bell-labs.com by wodc7mr3.ffx.ops.us.uu.net with ESMTP (peer crosschecked as: paperless.dnrc.bell-labs.com [135.180.161.172]) id QQhzyd24778; Fri, 28 Jan 2000 11:55:15 GMT Received: by lists.research.bell-labs.com (Postfix) id B187D52D5; Fri, 28 Jan 2000 06:44:01 -0500 (EST) Delivered-To: iptel-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 100EF52AB; Fri, 28 Jan 2000 06:43:55 -0500 (EST) Delivered-To: iptel-local@paperless.dnrc.bell-labs.com Message-Id: <200001281141.GAA05573@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce:; Cc: iptel@lists.research.bell-labs.com From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-iptel-cpl-framework-02.txt Date: Fri, 28 Jan 2000 06:41:20 -0500 Sender: owner-iptel@lists.research.bell-labs.com Precedence: bulk X-Mozilla-Status2: 00000000 --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 : Call Processing Language Framework and Requirements Author(s) : J. Lennox, H. Schulzrinne Filename : draft-ietf-iptel-cpl-framework-02.txt Pages : 25 Date : 27-Jan-00 A large number of the services we wish to make possible for Internet telephony require fairly elaborate combinations of signalling operations, often in network devices, to complete. We want a simple and standardized way to create such services to make them easier to implement and deploy. This document describes an architectural framework for such a mechanism, which we call a call processing language. It also outlines requirements for such a language. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-cpl-framework-02.txt 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-cpl-framework-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-cpl-framework-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: <20000127125914.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-cpl-framework-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-cpl-framework-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000127125914.I-D@ietf.org> --OtherAccess-- --NextPart-- --------- This message came from the IETF IPTEL Working Group Mailing List. --------------DD244FFE6B5F600A061BDE91-- --------- This message came from the IETF IPTEL Working Group Mailing List.