Re: [Lsr] I-D Action: draft-ietf-lsr-pce-discovery-security-support-01.txt

Qin Wu <> Mon, 03 June 2019 12:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 96F4612022A for <>; Mon, 3 Jun 2019 05:09:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id C2XVwW9bnQnO for <>; Mon, 3 Jun 2019 05:09:27 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 81114120243 for <>; Mon, 3 Jun 2019 05:09:27 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 4BEDAF0C3EDF1F24E0D0 for <>; Mon, 3 Jun 2019 13:09:25 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 3 Jun 2019 13:09:24 +0100
Received: from ([]) by ([]) with mapi id 14.03.0415.000; Mon, 3 Jun 2019 20:09:18 +0800
From: Qin Wu <>
To: "Les Ginsberg (ginsberg)" <>, "" <>
Thread-Topic: [Lsr] I-D Action: draft-ietf-lsr-pce-discovery-security-support-01.txt
Thread-Index: AdUZ/kOJZ3UGJI/OTMGkC0pgYhv1Rw==
Date: Mon, 3 Jun 2019 12:09:18 +0000
Message-ID: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Lsr] I-D Action: draft-ietf-lsr-pce-discovery-security-support-01.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 03 Jun 2019 12:09:37 -0000

Hi, Les:
Thanks for your comments, see my reply inline.
发件人: Lsr [] 代表 Les Ginsberg (ginsberg)
发送时间: 2019年6月3日 14:22
主题: Re: [Lsr] I-D Action: draft-ietf-lsr-pce-discovery-security-support-01.txt

A few - somewhat tardy - concerns about this draft.

1)During adoption call it was mentioned that PCE WG had not taken a position on this draft. Since I don't follow PCE WG (apologies) I need to ask - has that status changed??

Due to low priority of this work in PCE and heavy agenda when we proceeded this work earlier in PCE, we made very little progress.
This has been a little bit changed during adoption call and we authors were also active in both PCE and LSR WG
see the following link:

2)As discussed during the adoption call, the draft removes the restriction specified in RFC 5088/5089 of not allowing further PCE related advertisements in Router Capability TLV/Router Information LSA.
Acee had mentioned that he thought this was no longer a concern because in RFC 7770 multiple OSPF Router Information LSA support was introduced. But this is really not relevant to the reason that the restriction was originally introduced.

The restriction was introduced because of general concern that using IGPs to advertise information not directly relevant to the operation of the IGP as a routing protocol is sub-optimal and negatively impacts the performance of the primary IGP functions.
[Qin]: It seems your argument also applies to RFC5088/5089.

I am aware that this is a line that has been crossed (in modest ways) more than once - and I am not categorically opposing the extensions proposed - but I do wonder if this is the most appropriate way to advertise the new attributes - particularly since this does not solve the general case - it only applies when the PCE is also an LSR. I think a broader discussion of this issue is warranted.
[Qin]: Sure, but RFC5088/89 has already provide way to carry additional info. We could use some other out-band mechanism to carry additional info beyond PCED sub-TLVs defined in RFC5088/89, but do you think
1. use one protocol to convey all information needed
2. use two protocol to convey information separately
Which one is optimal?

3)If the draft goes forward in its current form, it updates RFC 5088/5089 in a significant way (the removal of restriction against additional PCE related IGP advertisements) - in which case I wonder if it would be better to write an RFC 5088/89 bis document rather than an extension document.
[Qin]: We don't' have too many changes going to RFC5088/89, so it is expense to make bis document, it is cheaper to leverage RFC updates attribute tool.
And, BTW, do you know why the HTML version of the document has no table of contents?
[Qin]:It is weird, seems we are using wrong boilerplate, I will see how to fix this.


> -----Original Message-----
> From: Lsr <>; On Behalf Of
> Sent: Sunday, June 02, 2019 8:45 PM
> To:
> Cc:
> Subject: [Lsr] I-D Action: 
> draft-ietf-lsr-pce-discovery-security-support-01.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-01.txt
> 	Pages           : 10
> 	Date            : 2019-06-02
> 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:
> -
> support/
> There are also htmlized versions available at:
> ort-01
> urity-
> support-01
> A diff from the previous version is available at:
> y-
> support-01
> Please note that it may take a couple of minutes from the time of 
> submission until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> Lsr mailing list

Lsr mailing list