[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-ospf
Subject:    Re: [Lsr] Min Links for Multiple Failures on Flooding Topology
From:       tony.li () tony ! li
Date:       2019-04-29 16:08:45
Message-ID: F449F616-2E7F-427A-A121-0CE0716A6F2B () tony ! li
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi Huaimo,

> You've computed the backup paths: [R4, R3, R6, R7] and [R5, R2, R9, R8].  This \
> results in enabling flooding on (R3, R6) and on (R5, R2), (R2, R9), (R9, R8). 
> [HC]: The enhanced algorithm enables the temporary flooding on (R3, R6) and (R2, \
> R9). It does not enable flooding on (R5, R2) or (R9, R8).


Thank you, yes, I missed that.


> Per the existing algorithm, the temporary additions would be (R3, R6) and (R2, R9). \
> As it has less flooding, this seems like a better solution. 
> [HC]: It seems that the existing (rate limiting) algorithm may result more flooding \
> in some cases. For example, if there are links (R4, R8) and (R5, R7) in Fig. 1, it \
> seems that these two links may also be added to the FT for flooding temporarily.


Ok, that's possible.  However, if those links existed, wouldn't your algorithm also \
make use of them?

I understand that your algorithm might pick only one path, but given that the path \
might not be functional, it seems like there would also be cases where a bit more \
flooding turns out to be the right answer.

Tony


[Attachment #5 (unknown)]

<html><head><meta http-equiv="Content-Type" content="text/html; \
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
line-break: after-white-space;" class=""><div class=""><br class=""></div>Hi \
Huaimo,<div class=""><br class=""></div><div class=""><div><blockquote type="cite" \
class=""><div class=""><div class="WordSection1" style="page: WordSection1; \
caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: \
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; \
text-align: start; text-indent: 0px; text-transform: none; white-space: normal; \
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div \
class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: \
&quot;Times New Roman&quot;, serif;" class="">You've computed the backup paths: [R4, \
R3, R6, R7] and [R5, R2, R9, R8]. &nbsp;This results in enabling flooding on (R3, R6) \
and on (R5, R2), (R2, R9), (R9, R8).<o:p class=""></o:p></div><div style="margin: 0in \
0in 0.0001pt; font-size: 12pt; font-family: &quot;Times New Roman&quot;, serif;" \
class=""><o:p class="">&nbsp;</o:p></div><div style="margin: 0in 0in 0.0001pt; \
font-size: 12pt; font-family: &quot;Times New Roman&quot;, serif;" class=""><span \
style="color: rgb(46, 117, 182);" class="">[HC]: The enhanced algorithm enables the \
temporary flooding on (R3, R6) and (R2, R9). It does not enable flooding on (R5, R2) \
or (R9, R8).</span></div></div></div></div></blockquote><div><br \
class=""></div><div><br class=""></div>Thank you, yes, I missed that.</div><div><br \
class=""></div><div><br class=""><blockquote type="cite" class=""><div \
class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); \
font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: \
normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: \
0px; text-transform: none; white-space: normal; word-spacing: 0px; \
-webkit-text-stroke-width: 0px; text-decoration: none;"><div class=""><div \
style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: &quot;Times New \
Roman&quot;, serif;" class=""><span style="color: rgb(46, 117, 182);" class=""><o:p \
class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; \
font-size: 12pt; font-family: &quot;Times New Roman&quot;, serif;" class="">Per the \
existing algorithm, the temporary additions would be (R3, R6) and (R2, R9). &nbsp;As \
it has less flooding, this seems like a better solution.<o:p \
class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; \
font-family: &quot;Times New Roman&quot;, serif;" class=""><o:p \
class="">&nbsp;</o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; \
font-family: &quot;Times New Roman&quot;, serif;" class=""><span style="color: \
rgb(46, 117, 182);" class="">[HC]: It seems that the existing (rate limiting) \
algorithm may result more flooding in some cases. For example, if there are links \
(R4, R8) and (R5, R7) in Fig. 1, it seems that these two links may also be added to \
the FT for flooding temporarily.<o:p \
class=""></o:p></span></div></div></div></blockquote><br class=""></div><div><br \
class=""></div><div>Ok, that's possible. &nbsp;However, if those links existed, \
wouldn't your algorithm also make use of them?</div><div><br class=""></div>I \
understand that your algorithm might pick only one path, but given that the path \
might not be functional, it seems like there would also be cases where a bit more \
flooding turns out to be the right answer.</div><div class=""><br class=""></div><div \
class="">Tony</div><div class=""><br class=""></div></body></html>



_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic