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 <ie...@btconnect.com> wrote: > 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 > then perform fast reroute. GIM>> Althtough the list odesn't have to be exaustive, we may add FRR per RFC 4090. > > > End-to-end protection technologies are usually > targeted at end-to-end TE paths, where the head-end detects TE path > failures and performs a rapid switchover. > GIM>> Indeed, the described behavior is characteristic to N:M protection. In some scenarios, redundant path may be used in 1+1 protection scheme. Then, it is the tail-end that detects the failure and switches to the backup path. > > There is no mechanism quickly to detect remote failures and invoke > repairs for non-TE paths. GIM>> Ain't you excluding multi-hop BFD? > > > This document proposes a framework for a path-aware, remote protection > mechanism for non-TE paths. > > with the abbreviations expanded as appropriate (but - of course - no > references!). > > HTH > > Tom Petch > > ________________________________________ > From: linchangwang <linchangwang.04...@h3c.com> > Sent: 18 October 2024 15:13 > To: RTGWG; rtgwg-chairs > Subject: Request for MORE reviews of > draft-liu-rtgwg-path-aware-remote-protection-02 > > Dear All, > > Since the last presentation, we have added a detailed description of path > information at both the per-neighbor and per-link levels in this draft. > We've also included two co-authors from Juniper and Broadcom. > > Current IP network protection mechanisms are mainly divided into local > protection and end-to-end protection. There is no mechanism to quickly > detect remote failures and initiate repairs for non-TE paths. > > The draft is simple and straightforward; it proposes a path-aware remote > protection mechanism and outlines its framework. > This includes the control plane, forwarding plane for remote path > awareness, > and a rapid notification framework for remote failures, which can be > applied to quick switching in a spine-leaf architecture. > > More reviews and comments are welcome! > > Thanks, > Changwang > > > -----邮件原件----- > 发件人: internet-dra...@ietf.org <internet-dra...@ietf.org> > 发送时间: 2024年9月14日 14:11 > 收件人: i-d-annou...@ietf.org > 主题: I-D Action: draft-liu-rtgwg-path-aware-remote-protection-02.txt > > Internet-Draft draft-liu-rtgwg-path-aware-remote-protection-02.txt is now > available. > > Title: Path-aware Remote Protection Framework > Authors: Yisong Liu > Changwang Lin > Mengxiao Chen > Zheng Zhang > Kevin Wang > Zongying He > Name: draft-liu-rtgwg-path-aware-remote-protection-02.txt > Pages: 16 > Dates: 2024-09-13 > > Abstract: > > This document describes the framework of path-aware remote > protection. > > The IETF datatracker status page for this Internet-Draft is: > > https://datatracker.ietf.org/doc/draft-liu-rtgwg-path-aware-remote-protection/ > > There is also an HTMLized version available at: > > https://datatracker.ietf.org/doc/html/draft-liu-rtgwg-path-aware-remote-protection-02 > > A diff from the previous version is available at: > > https://author-tools.ietf.org/iddiff?url2=draft-liu-rtgwg-path-aware-remote-protection-02 > > Internet-Drafts are also available by rsync at: > rsync.ietf.org::internet-drafts > > > _______________________________________________ > I-D-Announce mailing list -- i-d-annou...@ietf.org To unsubscribe send an > email to i-d-announce-le...@ietf.org > > ------------------------------------------------------------------------------------------------------------------------------------- > 本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出 > 的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、 > 或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本 > 邮件！ > This e-mail and its attachments contain confidential information from New > H3C, which is > intended only for the person or entity whose address is listed above. Any > use of the > information contained herein in any way (including, but not limited to, > total or partial > disclosure, reproduction, or dissemination) by persons other than the > intended > recipient(s) is prohibited. If you receive this e-mail in error, please > notify the sender > by phone or email immediately and delete it! > _______________________________________________ > rtgwg mailing list -- rtgwg@ietf.org > To unsubscribe send an email to rtgwg-le...@ietf.org > _______________________________________________ > rtgwg mailing list -- rtgwg@ietf.org > To unsubscribe send an email to rtgwg-le...@ietf.org >
_______________________________________________ rtgwg mailing list -- rtgwg@ietf.org To unsubscribe send an email to rtgwg-le...@ietf.org
