|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Yasuhiro Ohara (yasu_at_SFC.WIDE.AD.JP)
Date: Fri Oct 18 2002 - 09:10:43 CDT
acee> > acee> > Do we apply any gating for MaxAge LSAs in OSPF v3. There is this
acee> > acee> > MinLSAInterval timer which is applied to all LSA originations in OSPF v2.
acee> > acee> > Does this hold true in OSPF v3 also? And specially for the Max Age LSAs.
acee> > acee>
acee> > acee> The MinLSAInterval delay is retained from OSPF v2.
acee> > acee>
acee> > acee> > Dont we have this concept of "Bad news fast .. Good news slow" here.
acee> > acee>
acee> > acee> With respect to LSA origination, MinLSAInterval is applied
acee> > acee> equally to re-originations and purging.
acee> >
acee> > Actually, RFC 2328 is ambiguous about it.
acee>
acee> Hello Yasu,
acee>
acee> RFC 2328 does say that say a number of times that the "fundamental mechanisms
acee> of OSPF (flooding, DR election, area support, etc) remain unchanged".
acee>
acee> > Because it does not mention about it, I think that MinLSInterval
acee> > should not be applied to premature agings, as it lengthen the
acee> > convergence time ... I think we should take the concept "Bad new fast".
"remain unchanged" from what ? is that sentence from RFC *2740*, isn't
it ?
What I'm talking about is not the difference between OSPFv2 and
OSPFv3.
I said "original OSPFv2 (and hence also OSPFv3) specification is
ambiguous about whether to apply MinLSInterval when purging of LSA
(i.e. premature aging)".
Am I missing something ?
regards,
yasu
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]