Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07658; 7 Feb 95 15:41 EST Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa12952; 7 Feb 95 15:41 EST Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07643; 7 Feb 95 15:41 EST Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa06941; 7 Feb 95 15:04 EST Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; cc: ospf@gated.cornell.edu 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-ietf-ospf-demand-02.txt Date: Tue, 07 Feb 95 15:04:18 -0500 X-Orig-Sender: cclark@CNRI.Reston.VA.US Message-ID: <9502071504.aa06941@IETF.CNRI.Reston.VA.US> --NextPart A Revised Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Open Shortest Path First IGP Working Group of the IETF. Title : Extending OSPF to support demand circuits Author(s) : J. Moy Filename : draft-ietf-ospf-demand-02.txt Pages : 32 Date : 02/06/1995 This memo defines enhancements to the OSPF protocol that allow efficient operation over "demand circuits". Demand circuits are network segments whose costs vary with usage; charges can be based both on connect time and on bytes/packets transmitted. Examples of demand circuits include ISDN circuits, X.25 SVCs, and dial-up lines. The periodic nature of OSPF routing traffic has until now required a demand circuit's underlying data-link connection to be constantly open, resulting in unwanted usage charges. With the modifications described herein, OSPF Hellos and the refresh of OSPF routing information are suppressed on demand circuits, allowing the underlying data-link connections to be closed when not carrying application traffic. Demand circuits and regular network segments (e.g., leased lines) are allowed to be combined in any manner. In other words, there are no topological restrictions on the demand circuit support. However, while any OSPF network segment can be defined as a demand circuit, only point-to-point networks receive the full benefit. When broadcast and NBMA networks are declared demand circuits, routing update traffic is reduced but the periodic sending of Hellos is not, which in effect still requires that the data-link connections remain constantly open. 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-ietf-ospf-demand-02.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-ospf-demand-02.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-ietf-ospf-demand-02.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: <19950206161327.I-D@CNRI.Reston.VA.US> ENCODING mime FILE /internet-drafts/draft-ietf-ospf-demand-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ospf-demand-02.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19950206161327.I-D@CNRI.Reston.VA.US> --OtherAccess-- --NextPart--   Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa12837; 23 Feb 95 17:33 EST Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa18950; 23 Feb 95 17:33 EST Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12796; 23 Feb 95 17:33 EST Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa12571; 23 Feb 95 17:29 EST Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa18806; 23 Feb 95 17:29 EST Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa12565; 23 Feb 95 17:29 EST To: IETF-Announce: ; cc: ospf@gated.cornell.edu Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US From: IESG Secretary Subject: Last Call: Extending OSPF to support demand circuits to Proposed Standard Date: Thu, 23 Feb 95 17:29:41 -0500 X-Orig-Sender: scoya@CNRI.Reston.VA.US Message-ID: <9502231729.aa12565@IETF.CNRI.Reston.VA.US> The IESG has received a request from the Open Shortest Path First IGP Working Group to consider "Extending OSPF to support demand circuits" for the status of 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@cnri.reston.va.us or ietf@cnri.reston.va.us mailing lists by March 8, 1995. IESG Secretary   Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14881; 23 Feb 95 19:12 EST Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa20865; 23 Feb 95 19:12 EST Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14860; 23 Feb 95 19:12 EST Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14802; 23 Feb 95 19:09 EST Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa20791; 23 Feb 95 19:09 EST Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa14797; 23 Feb 95 19:09 EST To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: ospf@gated.cornell.edu Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US From: IESG Secretary Subject: Document Action: OSPF Database Overflow to Experimental Date: Thu, 23 Feb 95 19:09:11 -0500 X-Orig-Sender: scoya@CNRI.Reston.VA.US Message-ID: <9502231909.aa14797@IETF.CNRI.Reston.VA.US> The IESG has reviewed the Internet-Draft "OSPF Database Overflow" and recommends that it be published by the RFC Editor as an Experimental RFC. This document is the product of the Open Shortest Path First IGP Working Group. The IESG contact person is Joel Halpern.