Multiple Provisioning Domain Architecture
RFC 7556
|
| Document |
Type |
|
RFC - Informational
(June 2015; Errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-anipko-mif-mpvd-arch
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
Mar 2014
Jun 2014
|
|
Document shepherd |
|
DENG Hui
|
|
Shepherd write-up |
|
Show
(last changed 2014-09-17)
|
| IESG |
IESG state |
|
RFC 7556 (Informational)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Ted Lemon
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
IANA OK - No Actions Needed
|
|
IANA action state |
|
No IC
|
Internet Engineering Task Force (IETF) D. Anipko, Ed.
Request for Comments: 7556 Unaffiliated
Category: Informational June 2015
ISSN: 2070-1721
Multiple Provisioning Domain Architecture
Abstract
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.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7556.
Anipko Informational [Page 1]
RFC 7556 MPvD Architecture June 2015
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Anipko Informational [Page 2]
RFC 7556 MPvD Architecture June 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Definitions and Types of PvDs . . . . . . . . . . . . . . . . 5
2.1. Explicit PvDs . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Implicit PvDs and Incremental Adoption of Explicit PvDs . 6
2.3. Relationship between PvDs and Interfaces . . . . . . . . 7
2.4. PvD Identity/Naming . . . . . . . . . . . . . . . . . . . 8
2.5. The Relationship to Dual-Stack Networks . . . . . . . . . 8
3. Conveying PvD Information . . . . . . . . . . . . . . . . . . 9
3.1. Separate Messages or One Message? . . . . . . . . . . . . 9
3.2. Securing PvD Information . . . . . . . . . . . . . . . . 10
3.3. Backward Compatibility . . . . . . . . . . . . . . . . . 10
3.4. Retracting/Updating PvD Information . . . . . . . . . . . 10
3.5. Conveying Configuration Information Using IKEv2 . . . . . 10
4. Example Network Configurations . . . . . . . . . . . . . . . 11
4.1. A Mobile Node . . . . . . . . . . . . . . . . . . . . . . 11
4.2. A Node with a VPN Connection . . . . . . . . . . . . . . 12
4.3. A Home Network and a Network Operator with Multiple PvDs 12
5. Reference Model for the PvD-Aware Node . . . . . . . . . . . 13
5.1. Constructions and Maintenance of Separate PvDs . . . . . 13
5.2. Consistent Use of PvDs for Network Connections . . . . . 14
5.2.1. Name Resolution . . . . . . . . . . . . . . . . . . . 14
5.2.2. Next-Hop and Source Address Selection . . . . . . . . 15
5.2.3. Listening Applications . . . . . . . . . . . . . . . 16
5.2.3.1. Processing of Incoming Traffic . . . . . . . . . 16
5.2.4. Enforcement of Security Policies . . . . . . . . . . 17
5.3. Connectivity Tests . . . . . . . . . . . . . . . . . . . 18
5.4. Relationship to Interface Management and Connection
Managers . . . . . . . . . . . . . . . . . . . . . . . . 18
6. PvD Support in APIs . . . . . . . . . . . . . . . . . . . . . 19
6.1. Basic . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Show full document text