Secure Transport for PCEP
draft-lopez-pce-pceps-02
Document | Type |
Replaced Internet-Draft
(pce WG)
Expired & archived
|
|
---|---|---|---|
Authors | Diego R. Lopez , Oscar Gonzalez de Dios , Qin Wu , Dhruv Dhody | ||
Last updated | 2014-03-10 (Latest revision 2014-02-14) | ||
Replaced by | draft-ietf-pce-pceps | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-pce-pceps | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Path Computation Element Communication Protocol (PCEP) defines the mechanisms for the communication between a Path Computation Client (PCC) and a Path Computation Element (PCE), or among PCEs. This document describe the usage of Transport Layer Security (TLS) to enhance PCEP security, hence the PCEPS acronym proposed for it. The additional security mechanisms are provided by the transport protocol supporting PCEP, and therefore they do not affect its flexibility and extensibility.
Authors
Diego R. Lopez
Oscar Gonzalez de Dios
Qin Wu
Dhruv Dhody
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)