I-D Action: draft-ietf-lsr-pce-discovery-security-support-04.txt

internet-drafts@ietf.org Wed, 21 October 2020 11:45 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: lsr@ietf.org
Subject: I-D Action: draft-ietf-lsr-pce-discovery-security-support-04.txt
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: lsr@ietf.org
Message-ID: <160328075362.17080.14877441583529674415@ietfa.amsl.com>
Date: Wed, 21 Oct 2020 04:45:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/Pc_V6ZnAdP6CqeMnjElqvLElm4c>

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
                          Qiufang Ma
                          Daniel King
	Filename        : draft-ietf-lsr-pce-discovery-security-support-04.txt
	Pages           : 10
	Date            : 2020-10-21

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-04
https://datatracker.ietf.org/doc/html/draft-ietf-lsr-pce-discovery-security-support-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lsr-pce-discovery-security-support-04


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/

I-D Action: draft-ietf-lsr-pce-discovery-security… internet-drafts