RFC 2194: Review of Roaming Implementations
In plain English — editorial summary, not part of the RFC
This document reviews the design and functionality of existing roaming implementations. Examples of cases where roaming capability might be required include ISP "confederations" and ISP-provided corporate network access support. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2194
- Published
- September 1997
- Authors
- B. Aboba; J. Lu; J. Alsop; J. Ding; W. Wang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 35
- 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 2260Scalable Support for Multi-homed Multi-provider ConnectivityCurrent
January 1998
- 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 2477Criteria for Evaluating Roaming ProtocolsCurrent
January 1999
- RFC 2269Using the MARS Model in non-ATM NBMA NetworksCurrent
January 1998
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
- RFC 2180IMAP4 Multi-Accessed Mailbox PracticeCurrent
July 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?