Internet DRAFT - draft-manral-pce-tcp-port

draft-manral-pce-tcp-port




Network Working Group                                          V. Manral
Internet-Draft                                     Hewlett-Packard Corp.
Intended status: Standards-Track                         April 17, 2012
Expires: October 20, 2012


 Path Computation Element (PCE) Communication Protocol (PCEP) TCP port
                             number changes
                      draft-manral-pce-tcp-port-02

Abstract

   Path Computation Element (PCE) Communication Protocol (PCEP) defined
   in [RFC 5440] states that "All PCEP messages MUST be sent using the
   registered TCP port for the source and destination TCP port."  This
   has however lead to a lot of restrictions for the implementation.
   With these considerations in mind this document updates the TCP
   behavior.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC 2119].

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 October 20, 2012.

Copyright Notice

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



Manral                  Expires October 20, 2012                [Page 1]

Internet-Draft        PCEP TCP port number changes           April 2012  


   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
   2.  TCP Port changes  . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 3
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 3

































Manral                  Expires October 20, 2012                [Page 2]

Internet-Draft        PCEP TCP port number changes           April 2012  


1.  Introduction

   PCEP defined in [RFC 5440] uses TCP as the transport protocol to
   transfer all PCEP messages.  The PCEP specification states that:

   "All PCEP messages MUST be sent using the registered TCP port for the
   source and destination TCP port."

   However as PCEP can be used as communication between PCEP clients and
   servers as well as between servers.  This has caused issues in
   implementations on various platforms, besides most implementations do
   not follow the same behavior.  It is with this background that an
   alternate reccomendation is given here.


2.  TCP Port changes

   PCEP listens on PCE TCP port (4189).  The restriction of the source port
   to be the same has been removed.  This allows the requirements of
   reliable messaging and flow control to be met without further
   protocol work.

   The protocol needs to take care that there is only one request from a
   particular client, to prevent any DoS attacks, that may occur.


3.  IANA Considerations

   No new IANA consideration are raised by this document.


4.  Security Considerations

   This document raises no new security issues.


5.  Acknowledgements

   PCE group.












Manral                  Expires October 20, 2012                [Page 3]

Internet-Draft        PCEP TCP port number changes           April 2012  


Author's Address

   Vishwas Manral
   Hewlett-Packard Corp.
   191111 Pruneridge Ave.
   Cupertino, CA  95014
   US

   Phone: 408-447-1497      
   Email: vishwas.manral@hp.com
   URI:








































Manral                  Expires October 20, 2012                [Page 4]