Multiple Provisioning Domain Architecture
draft-ietf-mif-mpvd-arch-08

The information below is for an old version of the document
Document Type Active Internet-Draft (mif WG)
Last updated 2015-01-10
Replaces draft-anipko-mif-mpvd-arch
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication (wg milestones: Mar 2014 - Initial draft on MPv..., Jun 2014 - MPvD Architecture dr... )
Document shepherd Hui Deng
Shepherd write-up Show (last changed 2014-09-17)
IESG IESG state AD Evaluation::AD Followup
Consensus Boilerplate Unknown
Telechat date
Responsible AD Ted Lemon
Send notices to denghui02@hotmail.com, mif@ietf.org, mif-chairs@tools.ietf.org, draft-ietf-mif-mpvd-arch.all@tools.ietf.org
MIF Working Group                                         D. Anipko, Ed.
Internet-Draft                                              Unaffiliated
Intended status: Informational                          January 10, 2015
Expires: July 12, 2015

               Multiple Provisioning Domain Architecture
                      draft-ietf-mif-mpvd-arch-08

Abstract

   This document is a product of the work of the MIF 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 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 presence of
   multiple concurrent connections.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 12, 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

Anipko                   Expires July 12, 2015                  [Page 1]
Internet-Draft             MPVD architecture                January 2015

   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  3
   2.  Definitions and Types of PvDs  . . . . . . . . . . . . . . . .  4
     2.1.  Explicit PvDs  . . . . . . . . . . . . . . . . . . . . . .  4
     2.2.  Implicit PvDs and Incremental Adoption of Explicit PvDs  .  5
     2.3.  Relationship Between PvDs and Interfaces . . . . . . . . .  6
     2.4.  PvD Identity / Naming  . . . . . . . . . . . . . . . . . .  6
     2.5.  The Relationship to Dual-Stack Networks  . . . . . . . . .  7
   3.  Conveying PvD information using DHCPv6 and Router Advertisement 8
     3.1.  Separate Messages or One Message?  . . . . . . . . . . . .  8
     3.2.  Securing PvD Information . . . . . . . . . . . . . . . . .  8
     3.3.  Backward Compatibility . . . . . . . . . . . . . . . . . .  8
     3.4.  Selective Propagation  . . . . . . . . . . . . . . . . . .  9
     3.5.  Retracting / Updating PvD Information  . . . . . . . . . .  9
     3.6.  Conveying Configuration Information using IKEv2  . . . . .  9
   4.  Example Network Configurations . . . . . . . . . . . . . . . . 10
     4.1.  A Mobile Node  . . . . . . . . . . . . . . . . . . . . . . 10
     4.2.  A Node with a VPN Connection . . . . . . . . . . . . . . . 11
     4.3.  A Home Network and a Network Operator with Multiple PvDs . 12
   5.  Reference Model for the PvD-aware Node . . . . . . . . . . . . 12
     5.1.  Constructions and Maintenance of Separate PvDs . . . . . . 13
     5.2.  Consistent use of PvDs for Network Connections . . . . . . 13
       5.2.1.  Name Resolution  . . . . . . . . . . . . . . . . . . . 13
       5.2.2.  Next-hop and Source Address Selection  . . . . . . . . 14
       5.2.3.  Listening Applications . . . . . . . . . . . . . . . . 15
         5.2.3.1.  Processing of Incoming Traffic . . . . . . . . . . 15
           5.2.3.1.1.  Connection-oriented APIs . . . . . . . . . . . 15
           5.2.3.1.2.  Connectionless APIs  . . . . . . . . . . . . . 16
       5.2.4.  Enforcement of Security Policies . . . . . . . . . . . 16
     5.3.  Connectivity Tests . . . . . . . . . . . . . . . . . . . . 16
     5.4.  Relationship to Interface Management and Connection Manage 17
   6.  PvD support in APIs  . . . . . . . . . . . . . . . . . . . . . 17
     6.1.  Basic  . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Show full document text