PCE support for Domain Diversity
draft-dwpz-pce-domain-diverse-06

Document Type Active Internet-Draft (individual)
Last updated 2016-10-28
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
PCE Working Group                                               D. Dhody
Internet-Draft                                                     Q. Wu
Intended status: Experimental                                   U. Palle
Expires: May 1, 2017                                            X. Zhang
                                                     Huawei Technologies
                                                        October 28, 2016

                    PCE support for Domain Diversity
                    draft-dwpz-pce-domain-diverse-06

Abstract

   The Path Computation Element (PCE) may be used for computing path for
   services that traverse multi-area and multi-AS Multiprotocol Label
   Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered (TE)
   networks.

   Path computation should facilitate the selection of paths with domain
   diversity.  This document examines the existing mechanisms to do so
   and further propose some extensions to Path Computation Element
   Protocol (PCEP).

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 May 1, 2017.

Copyright Notice

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

Dhody, et al.              Expires May 1, 2017                  [Page 1]
Internet-Draft               DOMAIN-DIVERSE                 October 2016

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Domain Diversity  . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Per Domain Path Computation . . . . . . . . . . . . . . .   4
     3.2.  Backward-Recursive PCE-based Computation  . . . . . . . .   4
     3.3.  Hierarchical PCE  . . . . . . . . . . . . . . . . . . . .   5
       3.3.1.  End to End Path . . . . . . . . . . . . . . . . . . .   5
       3.3.2.  Domain-Sequence . . . . . . . . . . . . . . . . . . .   5
   4.  Extension to PCEP . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  SVEC Object . . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Minimize Shared Domains . . . . . . . . . . . . . . . . .   7
     4.3.  Relationship between SVEC Diversity Flags and OF  . . . .   7
   5.  Other Considerations  . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Transit Domain Identifier . . . . . . . . . . . . . . . .   8
     5.2.  Diversity v/s Optimality  . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  Manageability Considerations  . . . . . . . . . . . . . . . .   9
     7.1.  Control of Function and Policy  . . . . . . . . . . . . .   9
     7.2.  Information and Data Models . . . . . . . . . . . . . . .   9
     7.3.  Liveness Detection and Monitoring . . . . . . . . . . . .   9
     7.4.  Verify Correct Operations . . . . . . . . . . . . . . . .   9
     7.5.  Requirements On Other Protocols . . . . . . . . . . . . .   9
     7.6.  Impact On Network Operations  . . . . . . . . . . . . . .  10
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Appendix A.  Contributor Addresses  . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13
Show full document text