RFC 2091: Triggered Extensions to RIP to Support Demand Circuits
In plain English — editorial summary, not part of the RFC
This document defines a modification which can be applied to Bellman- Ford (distance vector) algorithm information broadcasting protocols. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2091
- Published
- January 1997
- Authors
- G. Meyer; S. Sherry
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2092Protocol Analysis for Triggered RIPCurrent
January 1997
- RFC 2096IP Forwarding Table MIBObsoleted
January 1997
- RFC 2082RIP-2 MD5 AuthenticationObsoleted
January 1997
- RFC 2081RIPng Protocol Applicability StatementCurrent
January 1997
- RFC 2102Multicast Support for Nimrod : Requirements and Solution ApproachesCurrent
February 1997
- RFC 2080RIPng for IPv6Current
January 1997
- RFC 2103Mobility Support for Nimrod : Challenges and Solution ApproachesCurrent
February 1997
- RFC 2117Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol SpecificationObsoleted
June 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?