Hi Robert,

please see inline:

On 23/08/2023 14:48, Robert Raszuk wrote:
Dear LSR WG,

I object on two basis ...

1)

The version -04 does not contain normative MUST that UPA shall only be used to trigger invalidation when end to end encapsulation is used for subject application(s). So as written is in fact quite undeployable in a mixed vendor and legacy node(s) environment doing hop by hop routing. We can't just hope that this is all about configuring the network in a proper way.

above looks more like a comment that can easily be addressed by additional text, which I'm willing to add, rather than an objection to draft becoming a WG document. Please let me know if you think otherwise.



2)

The solution is too pragmatic ...

Isn't that a good thing, isn't it? :)

It does not look at the problem holistically. Yes I still think the problem is worth solving but outside of link state IGP doing UPA blast flooding everywhere domain wide even if no nodes need that info. As discussed at length it could be done via either BGP indirection or via PUB-SUB model (as proposed).

I don't object to solve this problem in BGP, or elsewhere. But given that the problem we are trying to solve is created by the IGP summarization and the ultimate source of the prefix reachability or unreachibility comes from IGPs, having a solution in IGPs seems like a natural choice.

thanks,
Peter


Regards,
Robert


On Wed, Aug 23, 2023 at 10:07 PM Acee Lindem <[email protected] <mailto:[email protected]>> wrote:

    LSR Working Group,

    This begins the working group adoption call for “IGP Unreachable
    Prefix Announcement” - draft-ppsenak-lsr-igp-unreach-prefix-announce-04.
    Please indicate your support or objection on this list prior to
    September 7th, 2023.

    Thanks,
    Acee
    _______________________________________________
    Lsr mailing list
    [email protected] <mailto:[email protected]>
    https://www.ietf.org/mailman/listinfo/lsr
    <https://www.ietf.org/mailman/listinfo/lsr>


_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to