Protocol Action: Triggered Extensions to RIP to Support Demand Circuits to Proposed Standard
The IESG <iesg-secretary@CNRI.Reston.VA.US> Fri, 11 October 1996 13:55 UTC
Received: from ietf.org by ietf.org id aa21054; 11 Oct 96 9:55 EDT
Received: from localhost by ietf.org id aa20370; 11 Oct 96 9:24 EDT
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: ietf-rip@xylogics.com
Sender: ietf-announce-request@ietf.org
From: The IESG <iesg-secretary@CNRI.Reston.VA.US>
Subject: Protocol Action: Triggered Extensions to RIP to Support Demand Circuits to Proposed Standard
Date: Fri, 11 Oct 1996 09:23:59 -0400
X-Orig-Sender: scoya@ietf.org
Message-ID: <9610110924.aa20370@ietf.org>
The IESG has approved the Internet-Draft "Triggered Extensions to RIP to Support Demand Circuits" <draft-ietf-rip-trigger-rip-02.txt> as a Proposed Standard. The IESG also approved publication of the Internet-Draft "Protocol Analysis for Triggered RIP" <draft-ietf-rip-trigger-analysis-02.txt> as an Informational RFC. These documents are the product of the Routing Information Protocol Working Group. The IESG contact person is Joel Halpern. Technical Summary This protocol provides an additional mechanism for operating RIP over demand circuits. It provides for bringing down the circuit without intrinsically losing the reachability information. It is an alternative to the current proposed standard for Extensions to RIP to Support Demand Circuits (RFC 1582). It has several significant improvements relative to that RFC. There is no conflict with RFC 1582 as this protocol uses a different mechanism to identify its operation. Working Group Summary There was strong support in the working group for this specification. Protocol Quality This protocol has been reviewed by the Routing Area Director, Joel M. Halpern. It appears to be a sound extension to RIP. There are multiple independent implementations (Xyplex, DEC, and Meridian TC were reported by the WG Chair).