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

MIF Working Group                                         D. Anipko, Ed.
Internet-Draft                                     Microsoft Corporation
Intended status: Informational                         February 02, 2014
Expires: August 04, 2014

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

Abstract

   This document is a product of the work of MIF architecture design
   team.  It outlines a solution framework for some of the issues,
   experienced by nodes that can be attached to multiple networks.  The
   framework defines the notion of a Provisioning Domain (PVD) - a
   consistent set of network configuration information, and PVD-aware
   nodes - nodes which learn PVDs from the attached network(s) and/or
   other sources and manage and use multiple PVDs for connectivity
   separately and consistently.

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 August 04, 2014.

Copyright Notice

   Copyright (c) 2014 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

Anipko                  Expires August 04, 2014                 [Page 1]
Internet-Draft             MPVD architecture               February 2014

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  3
   2.  Definitions and types of PVDs  . . . . . . . . . . . . . . . .  3
     2.1.  Explicit PVDs  . . . . . . . . . . . . . . . . . . . . . .  4
     2.2.  Implicit PVDs and incremental adoption of the explicit PVDs 5
     2.3.  Relationship between PVDs and interfaces . . . . . . . . .  5
     2.4.  PVD identity/naming  . . . . . . . . . . . . . . . . . . .  6
     2.5.  Relationship to dual-stack networks  . . . . . . . . . . .  6
     2.6.  Elements of PVD  . . . . . . . . . . . . . . . . . . . . .  7
   3.  Conveying PVD information using DHCPv6 and Router Advertisement 7
     3.1.  Separate messages or one message . . . . . . . . . . . . .  7
     3.2.  Securing the PVD information . . . . . . . . . . . . . . .  7
     3.3.  Backward compatibility . . . . . . . . . . . . . . . . . .  8
     3.4.  Selective propagation  . . . . . . . . . . . . . . . . . .  8
     3.5.  Retracting/updating PvD information  . . . . . . . . . . .  9
     3.6.  Conveying configuration information using IKEv2  . . . . .  9
   4.  Example network configurations and number of PVDs  . . . . . .  9
   5.  Reference model of PVD-aware node  . . . . . . . . . . . . . .  9
     5.1.  Constructions and maintenance of separate PVDs . . . . . .  9
     5.2.  Consistent use of PVDs for network connections . . . . . . 10
       5.2.1.  Name resolution  . . . . . . . . . . . . . . . . . . . 10
       5.2.2.  Next-hop and source address selection  . . . . . . . . 11
     5.3.  Connectivity tests . . . . . . . . . . . . . . . . . . . . 11
     5.4.  Relationship to interface management and connection manage 12
   6.  PVD support in APIs  . . . . . . . . . . . . . . . . . . . . . 12
     6.1.  Basic  . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     6.2.  Intermediate . . . . . . . . . . . . . . . . . . . . . . . 12
     6.3.  Advanced . . . . . . . . . . . . . . . . . . . . . . . . . 13
   7.  PVD-aware nodes trust to PVDs  . . . . . . . . . . . . . . . . 13
     7.1.  Untrusted PVDs . . . . . . . . . . . . . . . . . . . . . . 13
     7.2.  Trusted PVDs . . . . . . . . . . . . . . . . . . . . . . . 13
       7.2.1.  Authenticated PVDs . . . . . . . . . . . . . . . . . . 14
       7.2.2.  PVDs trusted by attachment . . . . . . . . . . . . . . 14