Virtual Enterprise Traversal (VET)
draft-templin-intarea-vet-33

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in rtg area)
Last updated 2012-03-16 (latest revision 2011-12-19)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state (None)
Document shepherd None
IESG IESG state AD Evaluation
Telechat date
Responsible AD Ralph Droms
Send notices to fltemplin@acm.org, draft-templin-intarea-vet@tools.ietf.org
RFC Editor RFC Editor state ISR
Network Working Group                                    F. Templin, Ed.
Internet-Draft                              Boeing Research & Technology
Intended status: Informational                         December 19, 2011
Expires: June 21, 2012

                   Virtual Enterprise Traversal (VET)
                    draft-templin-intarea-vet-33.txt

Abstract

   Enterprise networks connect hosts and routers over various link
   types, and often also connect to provider networks and/or the global
   Internet.  Enterprise network nodes require a means to automatically
   provision addresses/prefixes and support internetworking operation in
   a wide variety of use cases including Small Office, Home Office
   (SOHO) networks, Mobile Ad hoc Networks (MANETs), ISP networks,
   multi-organizational corporate networks and the interdomain core of
   the global Internet itself.  This document specifies a Virtual
   Enterprise Traversal (VET) abstraction for autoconfiguration and
   operation of nodes in enterprise networks.

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 June 21, 2012.

Copyright Notice

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

Templin                   Expires June 21, 2012                 [Page 1]
Internet-Draft                     VET                     December 2011

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  6
   3.  Enterprise Network Characteristics . . . . . . . . . . . . . . 11
   4.  Autoconfiguration  . . . . . . . . . . . . . . . . . . . . . . 13
     4.1.  Enterprise Router (ER) Autoconfiguration . . . . . . . . . 13
     4.2.  VET Border Router (VBR) Autoconfiguration  . . . . . . . . 15
       4.2.1.  VET Interface Initialization . . . . . . . . . . . . . 15
       4.2.2.  Potential Router List (PRL) Discovery  . . . . . . . . 16
       4.2.3.  Provider-Aggregated (PA) EID Prefix
               Autoconfiguration  . . . . . . . . . . . . . . . . . . 16
       4.2.4.  ISP-Independent EID Prefix Autoconfiguration . . . . . 18
     4.3.  VET Border Gateway (VBG) Autoconfiguration . . . . . . . . 19
     4.4.  VET Host Autoconfiguration . . . . . . . . . . . . . . . . 19
   5.  Internetworking Operation  . . . . . . . . . . . . . . . . . . 20
     5.1.  Routing Protocol Participation . . . . . . . . . . . . . . 20
       5.1.1.  PI Prefix Routing Considerations . . . . . . . . . . . 21
       5.1.2.  Client Prefix (CP) Routing Considerations  . . . . . . 21
     5.2.  Default Route Configuration and Selection  . . . . . . . . 21
     5.3.  Address Selection  . . . . . . . . . . . . . . . . . . . . 22
     5.4.  Next Hop Determination . . . . . . . . . . . . . . . . . . 22
     5.5.  VET Interface Encapsulation/Decapsulation  . . . . . . . . 23
       5.5.1.  Inner Network Layer Protocol . . . . . . . . . . . . . 24
       5.5.2.  SEAL Encapsulation . . . . . . . . . . . . . . . . . . 24
       5.5.3.  Outer Transport-Layer Header Encapsulation . . . . . . 24
       5.5.4.  Outer IP Header Encapsulation  . . . . . . . . . . . . 25
       5.5.5.  Decapsulation and Re-Encapsulation . . . . . . . . . . 26
     5.6.  Neighbor Coordination on VET Interfaces that use SEAL  . . 26
       5.6.1.  Router Discovery . . . . . . . . . . . . . . . . . . . 27
       5.6.2.  Neighbor Unreachability Detection  . . . . . . . . . . 28
       5.6.3.  Redirection  . . . . . . . . . . . . . . . . . . . . . 28
       5.6.4.  Bidirectional Neighbor Synchronization . . . . . . . . 30
Show full document text