Hi all, The I-D defining the IGP extensions to discover the PCEP security capabilities was presented to the PCE WG during IETF 105. Please be aware that it is progressing as an LSR WG document (https://mailarchive.ietf.org/arch/msg/lsr/1CqjNObC5hoZaKDMrVTGwO0Axd0) and note particularly the agreed wording of section 4: " The introduction of the additional sub-TLVs should be viewed as an exception to the [RFC5088][RFC5089] policy justified by the need to know the new information prior to establishing a PCEP session. The restrictions defined in [RFC5089][RFC5089] should still be considered to be in place. "
Cheers, Dhruv & Julien -------- Forwarded Message -------- Date: Thu, 31 Oct 2019 23:23:54 -0700 From: [email protected] A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Link State Routing WG of the IETF. Title : IGP extension for PCEP security capability support in the PCE discovery Authors : Diego R. Lopez Qin Wu Dhruv Dhody Michael Wang Daniel King Filename : draft-ietf-lsr-pce-discovery-security-support-03.txt Pages : 9 Date : 2019-10-31 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. In addition, this document updates RFC 5088 and RFC 5089 to allow advertisement of Key ID or Key Chain Name Sub-TLV to support TCP AO security capability. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lsr-pce-discovery-security-support/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-lsr-pce-discovery-security-support-03 https://datatracker.ietf.org/doc/html/draft-ietf-lsr-pce-discovery-security-support-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-lsr-pce-discovery-security-support-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
