[RTG-DIR]Re: [MBONED]draft-ietf-mboned-redundant-ingress-failover-07 early Rtgdir review

[[e-mail]]

Hi Yingzhen,
Thank you very much for your review!
Based on your comments, a new version of 08 (https://datatracker.ietf.org/doc/draft-ietf-mboned-redundant-ingress-failover/08/)  has been submitted.
Appreciate for your more review and feedback.
Best regards,
Sandy




Original


From: YingzhenQuviaDatatracker <[e-mail]>
To: [e-mail] <[e-mail]>;
Cc: [e-mail] <[e-mail]>;[e-mail] <[e-mail]>;
Date: 2025年08月09日 03:47
Subject: [MBONED]draft-ietf-mboned-redundant-ingress-failover-07 early Rtgdir review

Document: draft-ietf-mboned-redundant-ingress-failover
Title: Multicast Redundant Ingress Router Failover
Reviewer: Yingzhen Qu
Review result: Not Ready
 
Hello
 
I have been selected to do a routing directorate “early” review of this draft.
https://datatracker.ietf.org/doc/draft-ietf-mboned-redundant-ingress-failover/
 
The routing directorate will, on request from the working group chair, perform
an “early” review of a draft before it is submitted for publication to the
IESG. The early review can be performed at any time during the draft’s lifetime
as a working group document. The purpose of the early review depends on the
stage that the document has reached.
 
For more information about the Routing Directorate, please see
https://wiki.ietf.org/en/group/rtg/RtgDir
 
Document: draft-ietf-mboned-redundant-ingress-failover-07
Reviewer: Yingzhen Qu
Review Date: 06-August-2025
Intended Status: Informational
 
Summary:
This document analyzes the redundant ingress-router failover problem within a
multicast domain.
 
Comments:
The draft needs some editorial work.
 
Take the abstract as an example. The current one doesn't read one, please
consider the following suggestion: This document analyzes the problem of
failover between redundant ingress routers in multicast domains. It describes
cold, warm, and hot standby modes, detailing their advantages, limitations, and
deployment considerations to help operators select appropriate mechanisms.
 
Some sentences are too long and hard to read, for example:
" 
The redundant ingress routers may be deployed to forward the same multicast
flow with only one router active at a time while the others act as backups. " 
 
Terminology:
121      IR: The ingress router for multicast flows in a multicast domain.
Instead of "The ingress router", I think this should be "An ingress router",
considering there might be multiple ingress routers.
 
123      ER: The egress router for multicast flows in a multicast domain.
should be "An egress router".
 
125      SIR: The IR responsible for sending the multicast flow, or the IR
126      whose flow is received by the ER, is called Selected-IR, or SIR for
127      short.
Can you pleas clarify that instead of "or the IR whose flow is received by the
ER", should this be "and ...." Suggested text: The IR that actively sends the
multicast flow, whose traffic is received by the egress router, is referred as
the Selected-IR, or SIR for short.
 
"failover" and "switchover " seems to be interchangeable, please clarify.
 
For the different backup modes:
Cold Standby section could mention implications for control-plane churn (e.g.,
slow convergence due to PIM Join/Prune updates). Warm Standby could elaborate
on synchronization mechanisms between routers (state sync, sequence numbers, or
shared RPF logic). Hot Standby: The trade-off between duplicate traffic and
fast failover is good, but might benefit from a clear reference to seamless
protection mechanisms like BFD-assisted PIM or BI-DIR multicast. Adding some
examples may help.
 
A session about deployment consideration will be helpful. Especially for
multi-domain scenarios, how this failover will behave across AS boundaries?
 
Section 3.2, about the failure detection, more details and comparisons should
should be provided.
 
The table in section 4.4 can add more content about comparisons of different
failover modes, such as failover time, control plane load, typical use cases
etc.
 
 
_______________________________________________
MBONED mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]