Qin - Thanx for addressing my comments - and for the update regarding PCE WG position.
The new version looks good to me. Les > -----Original Message----- > From: Lsr <lsr-boun...@ietf.org> On Behalf Of Qin Wu > Sent: Thursday, October 31, 2019 11:26 PM > To: lsr@ietf.org > Subject: Re: [Lsr] I-D Action: draft-ietf-lsr-pce-discovery-security-support- > 03.txt > > v-03 is posted to address additional comments from Les > https://datatracker.ietf.org/doc/html/draft-ietf-lsr-pce-discovery-security- > support-03 > Thanks Les for proposed change. > > -Qin > -----邮件原件----- > 发件人: Lsr [mailto:lsr-boun...@ietf.org] 代表 internet-dra...@ietf.org > 发送时间: 2019年11月1日 14:24 > 收件人: i-d-annou...@ietf.org > 抄送: lsr@ietf.org > 主题: [Lsr] I-D Action: draft-ietf-lsr-pce-discovery-security-support-03.txt > > > 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 > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > _______________________________________________ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr _______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
