RFC 6418: Multiple Interfaces and Provisioning Domains Problem Statement
In plain English — editorial summary, not part of the RFC
This document describes issues encountered by a node attached to multiple provisioning domains. This node receives configuration information from each of its provisioning domains, where some configuration objects are global to the node and others are local to the interface. Issues such as selecting the wrong interface to send traffic happen when conflicting node-scoped configuration objects are received and inappropriately used. Moreover, other issues are the result of simultaneous attachment to multiple networks, such as domain selection or addressing and naming space overlaps, regardless of the provisioning mechanism. While multiple provisioning domains are typically seen on nodes with multiple interfaces, this document also discusses situations involving single-interface nodes. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6418
- Published
- November 2011
- Authors
- M. Blanchet; P. Seite
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6419Current Practices for Multiple-Interface HostsCurrent
November 2011
- RFC 3646DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
December 2003
- RFC 3397Dynamic Host Configuration Protocol (DHCP) Domain Search OptionCurrent
November 2002
- RFC 6604xNAME RCODE and Status Bits ClarificationCurrent
April 2012
- RFC 6704Forcerenew Nonce AuthenticationCurrent
August 2012
- RFC 6731Improved Recursive DNS Server Selection for Multi-Interfaced NodesCurrent
December 2012
- RFC 6097Local Mobility Anchor (LMA) Discovery for Proxy Mobile IPv6Current
February 2011
- RFC 5966DNS Transport over TCP - Implementation RequirementsObsoleted
August 2010
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?