Item for discussion: draft-rekhter-ip-atm-architecture-00.txt
Andy Malis <malis@maelstrom.timeplex.com> Tue, 31 January 1995 21:26 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09979;
31 Jan 95 16:26 EST
Received: from acton.timeplex.com by IETF.CNRI.Reston.VA.US id aa09975;
31 Jan 95 16:26 EST
Received: from enigma.acton.timeplex.com (enigma.acton.timeplex.com
[134.196.22.57]) by maelstrom.acton.timeplex.com (8.6.9/ACTON-MAIN-1.2) with
ESMTP id QAA19008; Tue, 31 Jan 1995 16:12:41 -0500
Received: from maelstrom.timeplex.com (malis@localhost) by
enigma.acton.timeplex.com (8.6.9/ACTON-SUB-1.0) with ESMTP id QAA01136;
Tue, 31 Jan 1995 16:12:38 -0500
Message-Id: <199501312112.QAA01136@enigma.acton.timeplex.com>
To: rolc@maelstrom.acton.timeplex.com
cc: malis@maelstrom.acton.timeplex.com, yakov@watson.ibm.com,
kandlur@watson.ibm.com, jhalpern@newbridge.com
Subject: Item for discussion: draft-rekhter-ip-atm-architecture-00.txt
Date: Tue, 31 Jan 1995 16:12:37 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andy Malis <malis@maelstrom.timeplex.com>
Yakov Rekhter and Dilip Kandlur have posted a new Internet Draft that discusses a topic of great interest to the ROLC WG - determining when ATM hosts should establish direct (inter-LIS) circuits as opposed to using the router overlay on a large cloud. While it is more a directional piece than a protocol specification, any further work based upon the I-D has implications for both IP/ATM and NHRP. I've forwarded the I-D announcement below, in case you missed it. Please retrieve and read it (retrieval instructions, including by email, are included), and post comments to the rolc mailing list. Thanks, Andy __________________________________________________________________________ Andrew G. Malis malis@maelstrom.timeplex.com +1 508 266-4522 Ascom Timeplex 289 Great Rd., Acton MA 01720 USA FAX: +1 508 264-4999 ------- Forwarded Message Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce:; Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US From: Internet-Drafts@CNRI.Reston.VA.US Reply-to: Internet-Drafts@CNRI.Reston.VA.US Subject: I-D ACTION:draft-rekhter-ip-atm-architecture-00.txt Date: Thu, 26 Jan 95 12:55:04 -0500 X-Orig-Sender: cclark@CNRI.Reston.VA.US Message-ID: <9501261255.aa05126@IETF.CNRI.Reston.VA.US> - --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IP Architecture Extensions for ATM Author(s) : Y. Rekhter, D. Kandlur Filename : draft-rekhter-ip-atm-architecture-00.txt Pages : 8 Date : 01/25/1995 The original IP architecture assumes that each Data Link subnetwork is labeled with a single IP network number. As indicated in RFC1620, this assumption may be violated for large data networks, including ATM-based networks. The architecture works even when this assumption is violated, but it imposes constraints on communication among hosts and routers through an ATM-based network, which in turn may preclude full utilization of ATM capabilities. This document describes extensions to the IP architecture that relaxes these constraints, thus enabling the full utilization of the services provided by ATM. Internet-Drafts are 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-rekhter-ip-atm-architecture-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-rekhter-ip-atm-architecture-00.txt Internet-Drafts directories are located at: o Africa Address: ftp.is.co.za (196.4.160.2) o Europe Address: nic.nordu.net (192.36.148.17) o Pacific Rim Address: munnari.oz.au (128.250.1.21) o US East Coast Address: ds.internic.net (198.49.45.10) o US West Coast Address: ftp.isi.edu (128.9.0.32) Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-rekhter-ip-atm-architecture-00.txt". NOTE: The mail server at ds.internic.net 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. For questions, please mail to Internet-Drafts@cnri.reston.va.us. 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@ds.internic.net" Content-Type: text/plain Content-ID: <19950125165425.I-D@CNRI.Reston.VA.US> ENCODING mime FILE /internet-drafts/draft-rekhter-ip-atm-architecture-00.txt - --OtherAccess Content-Type: Message/External-body; name="draft-rekhter-ip-atm-architecture-00.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19950125165425.I-D@CNRI.Reston.VA.US> - --OtherAccess-- - --NextPart-- ------- End of Forwarded Message