The MPLS WG Archive

[Steve Yao <syao@chiaro.com>]

>
>I'm not sure how you reach that conclusion.  There is both addr and
>neighbor in the IGP TE extensions for numbered interfaces.  The RRO
>hops match the neighbor side.  That gives the exact IGP LSAs or LSPDU
>TLVs and gives the near side (the one likely to arrive first).
>

>When a link goes down, one LSA or LSPDU fragment is originated by two
>LSR, one on each side of the link.  When either LSA/LSPDU arrives, the
>TE-LSDB unidirectional adjacency (or link) in both directions is
>considered down.  The two unidirectional data structures each have a
>set of MPLS LSP data structures linked to them (actually other small
>structures that point to the LSP, but that's some of the data
>structures 101 material).
>
>If you mean that the LSA/LSPDU for the type-2/pseudonode of a
>broadcast interface is not explicitly present, then quite frankly,
>knowing the node of the previous hop and the next interface this is
>not an incredibly hard problem to solve either.
>
>If that's not what you meant, please let me know.
>
>Curtis
>

Yes. You are right. I missed the link ID and pseudonode.
Then there is the case where RRO may be too large. What cases were you
thinking of?

Steve
----------------------------------------- (on Chiaro SMTP Relay)

This e-mail and any files transmitted with it are the property
of Chiaro Networks, Ltd., and may contain confidential and 
privileged material for the sole use of the intended recipient(s)
to whom this e-mail is addressed. If you are not one of the named
recipient(s), or otherwise have reason to believe that you have 
received this message in error, please notify the sender and 
delete all copies from your system.  Any other use, retention, 
dissemination, forwarding, printing or copying of this e-mail is 
strictly prohibited.


---------------------------------------------------------