RFC 2477: Criteria for Evaluating Roaming Protocols

In plain English — editorial summary, not part of the RFC

This document describes requirements for the provisioning of "roaming capability" for dialup Internet users. "Roaming capability" is defined as the ability to use multiple Internet service providers (ISPs), while maintaining a formal, customer-vendor relationship with only one. This memo provides information for the Internet community.

Document record

Document ID

RFC2477

Published

January 1999

Authors

B. Aboba; G. Zorn

Status

INFORMATIONAL

Stream

IETF

Area

ops

Pages

12

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC2477

Topics

• ISP
• internet
• service
• providers
• operations

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent

  January 1998

• RFC 3098How to Advertise Responsibly Using E-Mail and Newsgroups or - how NOT to $$$$$ MAKE ENEMIES FAST! $$$$$Current

  April 2001

• RFC 3178IPv6 Multihoming Support at Site Exit RoutersCurrent

  October 2001

• RFC 2430A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)Current

  October 1998

• RFC 2267Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address SpoofingObsoleted

  January 1998

• RFC 2260Scalable Support for Multi-homed Multi-provider ConnectivityCurrent

  January 1998

• RFC 2194Review of Roaming ImplementationsCurrent

  September 1997

• RFC 2779Instant Messaging / Presence Protocol RequirementsCurrent

  February 2000

Also filed under

• INFORMATIONAL
• 1999
• IETF stream
• ops area