RFC 1940: Source Demand Routing: Packet Format and Forwarding Specification (Version 1)
In plain English — editorial summary, not part of the RFC
The purpose of SDRP is to support source-initiated selection of routes to complement the route selection provided by existing routing protocols for both inter-domain and intra-domain routes. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1940
- Published
- May 1996
- Authors
- D. Estrin; T. Li; Y. Rekhter; K. Varadhan; D. Zappala
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1937"Local/Remote" Forwarding Decision in Switched Data Link SubnetworksCurrent
May 1996
- RFC 1949Scalable Multicast Key DistributionCurrent
May 1996
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 1923RIPv1 Applicability Statement for Historic StatusCurrent
March 1996
- RFC 1965Autonomous System Confederations for BGPObsoleted
June 1996
- RFC 1966BGP Route Reflection An alternative to full mesh IBGPObsoleted
June 1996
- RFC 1992The Nimrod Routing ArchitectureCurrent
August 1996
- RFC 1997BGP Communities AttributeUpdated
August 1996
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?