Multiple Provisioning Domain Architecture
draft-anipko-mif-mpvd-arch-05
| Document | Type | Replaced Internet-Draft (candidate for mif WG) | |
|---|---|---|---|
| Last updated | 2013-12-07 (latest revision 2013-11-04) | ||
| Replaced by | RFC 7556 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-mif-mpvd-arch | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-anipko-mif-mpvd-arch-05.txt
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.
Authors
Dmitry Anipko (dmitry.anipko@microsoft.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)