Petch
From: linchangwang
Sent: 22 October 2024 01:08
To: tom petch; Greg Mirsky
Cc: RTGWG; rtgwg-chairs
Subject: Re: Request for MORE reviews of
draft-liu-rtgwg-path-aware-remote-protection-02
Hi Tom, Greg,
Thank you for your valuable feedback.
We will
reviews of
draft-liu-rtgwg-path-aware-remote-protection-02
From: Greg Mirsky
Sent: 20 October 2024 22:40
Hi Tom,
thank you for your help in clarifying the scope of the draft. Please find
several notes below tagged GIM>> (not on the proposed mechanism but rather on
the general aspe
From: Greg Mirsky
Sent: 20 October 2024 22:40
Hi Tom,
thank you for your help in clarifying the scope of the draft. Please find
several notes below tagged GIM>> (not on the proposed mechanism but rather on
the general aspects of protection and redundancy).
Weelll if you look you will see that
From: Greg Mirsky
Sent: 20 October 2024 22:40
Hi Tom,
thank you for your help in clarifying the scope of the draft. Please find
several notes below tagged GIM>> (not on the proposed mechanism but rather on
the general aspects of protection and redundancy).
Weelll if you look you will see that
From: Greg Mirsky
Sent: 20 October 2024 22:40
Hi Tom,
thank you for your help in clarifying the scope of the draft. Please find
several notes below tagged GIM>> (not on the proposed mechanism but rather on
the general aspects of protection and redundancy).
Weelll if you look you will see that
Hi Tom,
thank you for your help in clarifying the scope of the draft. Please find
several notes below tagged GIM>> (not on the proposed mechanism but rather
on the general aspects of protection and redundancy).
Regards,
Greg
On Sun, Oct 20, 2024 at 2:14 AM tom petch wrote:
> Abstract is too sho
Abstract is too short - it fails to tell me whether or not I want to read
further.
Perhaps
Current IP network protection mechanisms can be divided into
local protection and end-to-end protection. Local protection
technologies, such as ECMP and TI-LFA, can only detect local failures and
