RFC 4191: Default Router Preferences and More-Specific Routes

This document describes an optional extension to Router Advertisement messages for communicating default router preferences and more-specific routes from…

Read RFC 4191 on the RFC Editor

Outgoing relationships (7 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 3775: Mobility Support in IPv6
Normative reference — RFC 2461: Neighbor Discovery for IP Version 6 (IPv6)
Informative reference — RFC 3056: Connection of IPv6 Domains via IPv4 Clouds
Informative reference — RFC 3756: IPv6 Neighbor Discovery (ND) Trust Models and Threats
Informative reference — RFC 2080: RIPng for IPv6
Informative reference — RFC 2893: Transition Mechanisms for IPv6 Hosts and Routers

Incoming relationships (24 related RFCs)

Normatively referenced by — RFC 6550: RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks
Normatively referenced by — RFC 6775: Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)
Normatively referenced by — RFC 7084: Basic Requirements for IPv6 Customer Edge Routers
Normatively referenced by — RFC 8368: Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance (OAM)
Normatively referenced by — RFC 6204: Basic Requirements for IPv6 Customer Edge Routers
Normatively referenced by — RFC 7421: Analysis of the 64-bit Boundary in IPv6 Addressing
Normatively referenced by — RFC 8994: An Autonomic Control Plane (ACP)
Normatively referenced by — RFC 8801: Discovering Provisioning Domain Names and Data
Normatively referenced by — RFC 7157: IPv6 Multihoming without Network Address Translation
Normatively referenced by — RFC 7359: Layer 3 Virtual Private Network (VPN) Tunnel Traffic Leakages in Dual-Stack Hosts/Networks
Normatively referenced by — RFC 8885: Proxy Mobile IPv6 Extensions for Distributed Mobility Management
Normatively referenced by — RFC 6706: Asymmetric Extended Route Optimization (AERO)
Normatively referenced by — RFC 8678: Enterprise Multihoming using Provider-Assigned IPv6 Addresses without Network Prefix Translation: Requirements and Solutions
Normatively referenced by — RFC 9096: Improving the Reaction of Customer Edge Routers to IPv6 Renumbering Events
Informatively referenced by — RFC 4861: Neighbor Discovery for IP version 6 (IPv6)
Informatively referenced by — RFC 6724: Default Address Selection for Internet Protocol Version 6 (IPv6)
Informatively referenced by — RFC 4942: IPv6 Transition/Co-existence Security Considerations
Informatively referenced by — RFC 6434: IPv6 Node Requirements
Informatively referenced by — RFC 6343: Advisory Guidelines for 6to4 Deployment
Informatively referenced by — RFC 6104: Rogue IPv6 Router Advertisement Problem Statement
Informatively referenced by — RFC 6731: Improved Recursive DNS Server Selection for Multi-Interfaced Nodes
Informatively referenced by — RFC 6911: RADIUS Attributes for IPv6 Access Networks
Informatively referenced by — RFC 5175: IPv6 Router Advertisement Flags Option
Informatively referenced by — RFC 6629: Considerations on the Application of the Level 3 Multihoming Shim Protocol for IPv6 (Shim6)