PCE support for Maximizing Diversity
draft-dhody-pce-of-diverse-07

Document Type Active Internet-Draft (individual)
Last updated 2017-05-17
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: Standards Track                     Huawei Technologies
Expires: November 18, 2017                                  May 17, 2017

                  PCE support for Maximizing Diversity
                     draft-dhody-pce-of-diverse-07

Abstract

   The computation of one or a set of Traffic Engineering Label Switched
   Paths (TE LSPs) in MultiProtocol Label Switching (MPLS) and
   Generalized MPLS (GMPLS) networks is subject to a set of one or more
   specific optimization criteria, referred to as objective functions.

   In the Path Computation Element (PCE) architecture, a Path
   Computation Client (PCC) may want a set of services that are required
   to be diverse (disjointed) from each other.  In case when full
   diversity could not be achieved, it is helpful to maximize diversity
   as much as possible (or in other words, minimize the common shared
   resources).

   This document defines objective function code types for three new
   objective functions for this purpose to be applied to a set of
   synchronized path computation requests.

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 November 18, 2017.

Dhody & Wu              Expires November 18, 2017               [Page 1]
Internet-Draft                 OF-DIVERSE                       May 2017

Copyright Notice

   Copyright (c) 2017 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 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.  Extension to PCEP . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Other Considerations  . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Relationship between SVEC Diversity Flags and OF  . . . .   4
     4.2.  Inter-Domain Considerations . . . . . . . . . . . . . . .   5
     4.3.  Domain Diversity  . . . . . . . . . . . . . . . . . . . .   5
     4.4.  Diversity v/s Optimality  . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  Manageability Considerations  . . . . . . . . . . . . . . . .   6
     6.1.  Control of Function and Policy  . . . . . . . . . . . . .   6
     6.2.  Information and Data Models . . . . . . . . . . . . . . .   6
     6.3.  Liveness Detection and Monitoring . . . . . . . . . . . .   6
     6.4.  Verify Correct Operations . . . . . . . . . . . . . . . .   6
     6.5.  Requirements On Other Protocols . . . . . . . . . . . . .   6
     6.6.  Impact On Network Operations  . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Appendix A.  Contributor Addresses  . . . . . . . . . . . . . . .   9
   Appendix B.  Example  . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   [RFC5440] describes the specifications for the Path Computation
   Element Communication Protocol (PCEP).  PCEP specifies the
   communication between a Path Computation Client (PCC) and a Path
Show full document text