Path Computation Element (PCE) Discovery using DNS
draft-wu-pce-dns-pce-discovery-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Qin Wu 
Last updated 2013-07-04
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized 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)
Path Computation Element Working Group                             Q. Wu
Internet-Draft                                                    Huawei
Intended status: Standards Track                            July 5, 2013
Expires: January 6, 2014

           Path Computation Element (PCE) Discovery using DNS
                   draft-wu-pce-dns-pce-discovery-00

Abstract

   Discovery of the (Path Computation Element (PCE) within an IGP area
   or domain is possible using OSPF [RFC5088] and IS-IS [RFC5089].
   However, in some deployment scenarios PCEs may not wish, or be able,
   to participate within the IGP process.  Therefore it would be
   beneficial for the Path Computation Client (PCC) to discover PCEs via
   an alternative mechanism to those proposed in [RFC5088] and
   [RFC5089].

   This document specifies the requirements, use cases, procedures and
   extensions to support DNS for PCE discovery.

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 January 6, 2014.

Copyright Notice

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

Wu                       Expires January 6, 2014                [Page 1]
Internet-Draft               DNS based PCED                    July 2013

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Requirements . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions used in this document  . . . . . . . . . . . . . .  4
   3.  Motivation . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Load Sharing of Path Computation Requests  . . . . . . . .  5
     3.2.  Network Address Translation Gateway  . . . . . . . . . . .  5
     3.3.  Multiple-Provider Domains  . . . . . . . . . . . . . . . .  5
   4.  Discovering a Path Computation Element . . . . . . . . . . . .  6
     4.1.  Determining the PCE Service and transport protocol . . . .  7
     4.2.  Determining the IP Address of the PCE  . . . . . . . . . .  7
     4.3.  Determining path computation scope,the PCE domains and
           Neighbor PCE domains . . . . . . . . . . . . . . . . . . .  8
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 12
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 13
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14

Wu                       Expires January 6, 2014                [Page 2]
Internet-Draft               DNS based PCED                    July 2013

1.  Introduction

   The Path Computation Element Communication Protocol (PCEP) is a
   transaction-based protocol carried over TCP.  In order to be able to
   direct path computation requests to the Path Computation Element
   (PCE), a Path Computation Client (PCC) needs to know the location and
   capability of a PCE.

   In a network where an IGP is used and where the PCE participates in
   the IGP, discovery mechanisms exist for PCC to learn the identify and
   capability of each PCE.  [RFC5088] defines a PCE Discovery (PCED) TLV
   carried in an OSPF Router LSA.  Similarly, [RFC5089] defines the PCED
   sub-TLV for use in PCE Discovery using IS-IS.

   However in certain scenarios not all PCEs will participate in the IGP
   instance, section 3 (Motivation) outlines a number of use cases.  In
   these cases, current PCE Discovery mechanisms are therefore not
   appropriate and another PCE announcement and discovery function would
   be required.

1.1.  Requirements

   As described in [RFC4674], the PCE Discovery information should at
Show full document text