RFC 7556: Multiple Provisioning Domain Architecture
In plain English — editorial summary, not part of the RFC
This document is a product of the work of the Multiple Interfaces Architecture Design team. It outlines a solution framework for some of the issues experienced by nodes that can be attached to multiple networks simultaneously. The framework defines the concept of a Provisioning Domain (PvD), which is a consistent set of network configuration information. PvD-aware nodes learn PvD-specific information from the networks they are attached to and/or other sources. PvDs are used to enable separation and configuration consistency in the presence of multiple concurrent connections.
Document record
- Document ID
- RFC7556
- Published
- June 2015
- Authors
- D. Anipko
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 25
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7558Requirements for Scalable DNS-Based Service Discovery (DNS-SD) / Multicast DNS (mDNS) ExtensionsCurrent
July 2015
- RFC 7554Using IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the Internet of Things (IoT): Problem StatementCurrent
May 2015
- RFC 7559Packet-Loss Resiliency for Router SolicitationsCurrent
May 2015
- RFC 7561Mapping Quality of Service (QoS) Procedures of Proxy Mobile IPv6 (PMIPv6) and WLANCurrent
June 2015
- RFC 7550Issues and Recommendations with Multiple Stateful DHCPv6 OptionsObsoleted
May 2015
- RFC 7563Extensions to the Proxy Mobile IPv6 (PMIPv6) Access Network Identifier OptionCurrent
June 2015
- RFC 7527Enhanced Duplicate Address DetectionCurrent
April 2015
- RFC 7588A Widely Deployed Solution to the Generic Routing Encapsulation (GRE) Fragmentation ProblemCurrent
July 2015
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?