Hi, Tony:
If we use pub/sub mechanism, why don't we accomplish it via the management system, or controller? No IGP extension needed then. Also no pressure for the ABR to keep the RDB(Registration Database) and the TCP/QUIC server connections Best Regards Aijun Wang China Telecom From: [email protected] <[email protected]> On Behalf Of Tony Li Sent: Wednesday, January 19, 2022 9:05 AM To: lsr <[email protected]> Subject: [Lsr] Fwd: New Version Notification for draft-li-lsr-liveness-00.txt FYI. This is a better alternative that PUA/Pulse. Tony Begin forwarded message: From: [email protected] <mailto:[email protected]> Subject: New Version Notification for draft-li-lsr-liveness-00.txt Date: January 18, 2022 at 5:04:22 PM PST To: <[email protected] <mailto:[email protected]> >, "Tony Li" <[email protected] <mailto:[email protected]> > A new version of I-D, draft-li-lsr-liveness-00.txt has been successfully submitted by Tony Li, and posted to the IETF repository. Name: draft-li-lsr-liveness Revision: 00 Title: Node Liveness Protocol Document date: 2022-01-18 Group: Individual Submission Pages: 9 URL: https://www.ietf.org/archive/id/draft-li-lsr-liveness-00.txt Status: https://datatracker.ietf.org/doc/draft-li-lsr-liveness/ Htmlized: https://datatracker.ietf.org/doc/html/draft-li-lsr-liveness Abstract: Prompt notification of the loss of node liveness or reachability is useful for restoring services in tunneled topologies. IGP summarization precludes remote nodes from directly observing the status of remote nodes. This document proposes a service that, in conjunction with the IGP, provides prompt notifications without impacting IGP summarization. The IETF Secretariat
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
