RFC 4191: Default Router Preferences and More-Specific Routes
In plain English — editorial summary, not part of the RFC
This document describes an optional extension to Router Advertisement messages for communicating default router preferences and more-specific routes from routers to hosts. This improves the ability of hosts to pick an appropriate router, especially when the host is multi-homed and the routers are on different links. The preference values and specific routes advertised to hosts require administrative configuration; they are not automatically derived from routing tables. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4191
- Published
- November 2005
- Authors
- R. Draves; D. Thaler
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4193Unique Local IPv6 Unicast AddressesCurrent
October 2005
- RFC 4174The IPv4 Dynamic Host Configuration Protocol (DHCP) Option for the Internet Storage Name ServiceUpdated
September 2005
- RFC 4225Mobile IP Version 6 Route Optimization Security Design BackgroundCurrent
December 2005
- RFC 4140Hierarchical Mobile IPv6 Mobility Management (HMIPv6)Obsoleted
August 2005
- RFC 4242Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
November 2005
- RFC 4243Vendor-Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent OptionCurrent
December 2005
- RFC 4137State Machines for Extensible Authentication Protocol (EAP) Peer and AuthenticatorCurrent
August 2005
- RFC 4135Goals of Detecting Network Attachment in IPv6Current
August 2005
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?