IGP extension for PCEP security capability support in the PCE discovery
draft-wu-pce-discovery-pceps-support-07
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Diego Lopez , Qin Wu , Dhruv Dhody , Daniel King | ||
| Last updated | 2017-09-29 (latest revision 2017-03-28) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-wu-pce-discovery-pceps-support-07.txt
Abstract
When a Path Computation Element (PCE) is a Label Switching Router (LSR) participating in the Interior Gateway Protocol (IGP), or even a server participating in IGP, its presence and path computation capabilities can be advertised using IGP flooding. The IGP extensions for PCE discovery (RFC 5088 and RFC 5089) define a method to advertise path computation capabilities using IGP flooding for OSPF and IS-IS respectively. However these specifications lack a method to advertise PCEP security (e.g., Transport Layer Security(TLS),TCP Authentication Option (TCP-AO)) support capability. This document proposes new capability flag bits for PCE-CAP-FLAGS sub- TLV that can be announced as attribute in the IGP advertisement to distribute PCEP security support information.
Authors
Diego Lopez
(diego.r.lopez@telefonica.com)
Qin Wu
(bill.wu@huawei.com)
Dhruv Dhody
(dhruv.ietf@gmail.com)
Daniel King
(daniel@olddog.co.uk)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)