A new Request for Comments is now available in online RFC libraries.


       RFC 1582:

        Title:      Extensions to RIP to Support Demand Circuits
        Author:     G. Meyer
        Mailbox:    gerry@spider.co.uk
        Pages:      29
        Characters: 63,271
        Updates/Obsoletes:  none


Running routing protocols on connection oriented Public Data Networks,
for example X.25 packet switched networks or ISDN, can be expensive if
the standard form of periodic broadcasting of routing information is
adhered to.  The high cost arises because a connection has to all
practical intents and purposes be kept open to every destination to
which routing information is to be sent, whether or not it is being
used to carry user data.  Routing information may also fail to be
propagated if the number of destinations to which the routing
information is to be sent exceeds the number of channels available to
the router on the Wide Area Network (WAN).

This memo defines a generalized modification which can be applied to
Bellman-Ford (or distance vector) algorithm information broadcasting
protocols, for example IP RIP, Netware RIP or Netware SAP, which
overcomes the limitations of the traditional methods described above.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute