RFC 2260: Scalable Support for Multi-homed Multi-provider Connectivity
In plain English — editorial summary, not part of the RFC
This document describes addressing and routing strategies for multi- homed enterprises attached to multiple Internet Service Providers (ISPs) that are intended to reduce the routing overhead due to these enterprises in the global Internet routing system. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2260
- Published
- January 1998
- Authors
- T. Bates; Y. Rekhter
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3178IPv6 Multihoming Support at Site Exit RoutersCurrent
October 2001
- RFC 2267Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address SpoofingObsoleted
January 1998
- RFC 2430A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)Current
October 1998
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
- RFC 2194Review of Roaming ImplementationsCurrent
September 1997
- RFC 2477Criteria for Evaluating Roaming ProtocolsCurrent
January 1999
- RFC 2353APPN/HPR in IP Networks APPN Implementers' Workshop Closed Pages DocumentCurrent
May 1998
- RFC 1911Voice Profile for Internet MailObsoleted
February 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?