PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 26
- 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 describes PCEPS -- the usage of Transport Layer Security (TLS) to provide a secure transport for PCEP. The additional security mechanisms are provided by the transport protocol supporting PCEP; therefore, they do not affect the flexibility and extensibility of PCEP. This document updates RFC 5440 in regards to the PCEP initialization phase procedures.
- Publication Date
- 2017-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC8253- Link
- https://doi.org/10.17487/RFC8253
- Author(s)
- Diego LopezOscar Gonzalez de DiosQin WuDhruv Dhody
- Keyword(s)
- PCE, PCEP, Security, Authentication, Encryption, TLS
Latest version of IETF RFC 8253
Document Versions — IETF RFC 8253
-
▶ IETF RFC 8253 (2017-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- NIST FIPS 180-4 [Active]
- IETF RFC 2119 [Active*]
- IETF RFC 5246 [Superseded*]
- IETF RFC 5280 [Active, Amended*]
- IETF RFC 5440 [Active*]
- IETF RFC 6066 [Active*]
- IETF RFC 6125 [Superseded*]
- IETF RFC 6698 [Active*]
- IETF RFC 7525 [Superseded*]
- IETF RFC 7671 [Active*]
- IETF RFC 8174 [Active*]
Bibliographic Reference(s)
- IETF.draft-ietf-pce-pcep-yang-05 — PCEP-YANG EXTERNAL
- IETF.draft-wu-pce-discovery-pceps-support-07 — PCE-DISCOVERY-PCEPS-SUPPORT EXTERNAL
- IETF.draft-wu-pce-dns-pce-discovery-10 — PCE-DISCOVERY-DNS EXTERNAL
- IETF RFC 4492 [Superseded*]
- IETF RFC 4513 [Active*]
- IETF RFC 5088 [Active*]
- IETF RFC 5089 [Active*]
- IETF RFC 5925 [Active*]
- IETF RFC 6460 [Active*]
- IETF RFC 6614 [Active*]
- IETF RFC 6952 [Active*]
- RFC7420 — RFC7420 EXTERNAL
- IETF RFC 7457 [Active*]
- RFC8232 — RFC8232 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8253.json
Amends:
IETF RFC 5440 [Active*]
Amended by:
RFC9916 NOT IN REGISTRY
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 8253, PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP). Available at https://doi.org/10.17487/RFC8253
Snippet:
IETF RFC 8253, PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP). Available at https://doi.org/10.17487/RFC8253
HTML (ISO 690 compliant)
Preview:
IETF RFC 8253, PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP). Available at https://doi.org/10.17487/RFC8253
Snippet:
<span class="citation"><cite>IETF RFC 8253</cite>, PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP). Available at <a href="https://doi.org/10.17487/RFC8253" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8253</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 8253, PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)
doi: 10.17487/RFC8253
url: https://doi.org/10.17487/RFC8253
doi: 10.17487/RFC8253
url: https://doi.org/10.17487/RFC8253
Snippet:
<li> <cite id="bib-rfc8253">IETF RFC 8253</cite>, PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP) <span class="doi">10.17487/RFC8253</span> </li>
Referenced By
- IETF RFC 9353 [Active*]
- IETF RFC 9488 [Active*]