Path Computation Element (PCE) Discovery using Domain Name System(DNS)
draft-wu-pce-dns-pce-discovery-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Qin Wu  , Dhruv Dhody 
Last updated 2013-07-15
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)
PCE Working Group                                                  Q. Wu
Internet-Draft                                                  D. Dhody
Intended status: Standards Track                                  Huawei
Expires: January 16, 2014                                  July 15, 2013

 Path Computation Element (PCE) Discovery using Domain Name System(DNS)
                   draft-wu-pce-dns-pce-discovery-01

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) (or other PCEs) 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 discovery via DNS for PCE.

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 16, 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 & Dhody              Expires January 16, 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
     3.4.  Multiple PCE Servers . . . . . . . . . . . . . . . . . . .  6
     3.5.  End to End Path Computation  . . . . . . . . . . . . . . .  6
   4.  Discovering a Path Computation Element . . . . . . . . . . . .  7
     4.1.  Determining the PCE Service and transport protocol . . . .  8
     4.2.  Determining the IP Address of the PCE  . . . . . . . . . .  8
     4.3.  Determining path computation scope,the PCE domains and
           Neighbor PCE domains . . . . . . . . . . . . . . . . . . .  9
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   7.  Acknowledges . . . . . . . . . . . . . . . . . . . . . . . . . 13
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 14
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 15
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16

Wu & Dhody              Expires January 16, 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[RFC4655].  In order to be
   able to direct path computation requests to the Path Computation
   Element (PCE), a Path Computation Client (PCC) (or other PCEs) 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 (or PCE) to learn the
   identity 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.  Scope of the advertisement is limited to IGP area/level or
Show full document text