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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Qin Wu  , Dhruv Dhody  , Daniel King  , Diego Lopez  , Jeff Tantsura 
Last updated 2014-03-03
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: September 4, 2014                                       D. King
                                                      Old Dog Consulting
                                                                D. Lopez
                                                          Telefonica I+D
                                                             J. Tantsura
                                                                Ericsson
                                                           March 3, 2014

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

Abstract

   Discovery of the Path Computation Element (PCE) within an IGP area or
   routing domain is possible using OSPF [RFC5088] and IS-IS [RFC5089].
   However, it has been established that in certain deployment scenarios
   PCEs may not wish, or be able to participate within the IGP process.
   In those scenarios, it is beneficial for the Path Computation Client
   (PCC) (or other PCE) 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 PCE type and capability discovery via DNS.

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 September 4, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the

Wu, et al.              Expires September 4, 2014               [Page 1]
Internet-Draft               DNS based PCED                   March 2014

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
     1.2.  Requirements . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions used in this document  . . . . . . . . . . . . . .  5
   3.  Motivation . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     3.1.  Outside the Routing Domain . . . . . . . . . . . . . . . .  6
     3.2.  Discovery Mechanisms . . . . . . . . . . . . . . . . . . .  7
       3.2.1.  Query-Response versus Advertisement  . . . . . . . . .  7
     3.3.  Network Address Translation Gateway  . . . . . . . . . . .  7
   4.  Additional Capabilities  . . . . . . . . . . . . . . . . . . .  8
     4.1.  Load Sharing of Path Computation Requests  . . . . . . . .  8
   5.  Extended Naming Authority Pointer ( NAPTR )Service Field
       Format . . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     5.1.  IETF Standards Track PCE Applications  . . . . . . . . . . 10
   6.  Backwards Compatibility  . . . . . . . . . . . . . . . . . . . 11
   7.  Discovering a Path Computation Element . . . . . . . . . . . . 12
     7.1.  Determining the PCE Service and transport protocol . . . . 13
     7.2.  Determining the IP Address of the PCE  . . . . . . . . . . 13
       7.2.1.  Examples . . . . . . . . . . . . . . . . . . . . . . . 15
     7.3.  Determining the PCE domains and Neighbor PCE domains . . . 16
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 17
     8.1.  IETF PCE Application Service Tags  . . . . . . . . . . . . 17
     8.2.  PCE Application Protocol Tags  . . . . . . . . . . . . . . 17
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 18
   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
     11.1. Normative References . . . . . . . . . . . . . . . . . . . 20
Show full document text