Speaking as WG member and longtime steward of the IGPs:
Hi Aijun,
My opinion is that we should not overload the base IGP topology advertisements
with everyone's favorite obscure use case. Hence, I think it would be a big
mistake to add this stub link TLV to the base LSAs.
Rather, exactly what problem are you trying to solve? Previously, you were
trying to associate the passive interface attribute with a prefix and making
some inference related to an inter-AS boundary (this was not entirely clear).
What problem are you trying to solve? Precisely, what do you want the
controller to learn (i.e., address or interface index) and what is it going to
do with it.
Please don't try and solve the CFN problem as the requirements are not clear
(anycast, unicast, impact on routing, scope, etc).
Thanks,
Acee
On 11/17/20, 1:08 AM, "wang...@chinatelecom.cn on behalf of Aijun Wang"
<wang...@chinatelecom.cn> wrote:
Hi, Acee:
As discussed on the list and during the 109 meeting, we have updated the
draft to reflect the comments from the LSR community.
Please see whether you have still other concerns or not and if there is no
further comments on this direction, can we begin the WG adoption call then?
Thanks you and Peter for your intense discussions for this draft.
Thanks in advance.
Best Regards
Aijun Wang
China Telecom
> -----Original Message-----
> From: internet-dra...@ietf.org <internet-dra...@ietf.org>
> Sent: Sunday, November 15, 2020 7:44 AM
> To: Zhibo Hu <huzh...@huawei.com>; Aijun Wang
> <wang...@chinatelecom.cn>; Gyan S. Mishra <gyan.s.mis...@verizon.com>;
> Gyan Mishra <gyan.s.mis...@verizon.com>
> Subject: New Version Notification for
> draft-wang-lsr-passive-interface-attribute-06.txt
>
>
> A new version of I-D, draft-wang-lsr-passive-interface-attribute-06.txt
> has been successfully submitted by Aijun Wang and posted to the IETF
> repository.
>
> Name: draft-wang-lsr-passive-interface-attribute
> Revision: 06
> Title: Passive Interface Attribute
> Document date: 2020-11-15
> Group: Individual Submission
> Pages: 10
> URL:
>
https://www.ietf.org/archive/id/draft-wang-lsr-passive-interface-attribute-06.t
> xt
> Status:
>
https://datatracker.ietf.org/doc/draft-wang-lsr-passive-interface-attribute/
> Htmlized:
>
https://datatracker.ietf.org/doc/html/draft-wang-lsr-passive-interface-attribut
> e
> Htmlized:
> https://tools.ietf.org/html/draft-wang-lsr-passive-interface-attribute-06
> Diff:
>
https://www.ietf.org/rfcdiff?url2=draft-wang-lsr-passive-interface-attribute-06
>
> Abstract:
> This document describes the mechanism that can be used to
> differentiate the passive interfaces from the normal interfaces
> within ISIS or OSPF domain.
>
>
>
>
> 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.
>
> The IETF Secretariat
>
_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
