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

List:       ms-ospf
Subject:    Re: OSPF/Unnumbered
From:       Acee Lindem <acee () REDBACK ! COM>
Date:       2004-10-08 12:55:26
Message-ID: 03a201c4ad36$15379560$0202a8c0 () aceeinspiron
[Download RAW message or body]

Hi Fabien,

While this solution would simplify the virtual link neighbor address selection,
I don't think we should change the LSA link format at this time. Many
implementations use a heuristic of determining whether the best path
link data is a valid IP address and, if not, searching the virtual link
endpoint router's backbone router LSA for a routable address. You
can look at an example of this in John Moy's GPL ospf
implementation (www.ospf.org).

Hope this helps,
Acee

----- Original Message -----
From: "Fabien Verhaeghe" <fabien.verhaeghe@ATOSORIGIN.COM>
To: <OSPF@PEACH.EASE.LSOFT.COM>
Sent: Friday, October 08, 2004 2:15 AM
Subject: OSPF/Unnumbered


> Hi,
>
> RFC2328 section 12.4.1.1 describing how to encode P2P link into a router LSA required to set the
> MIB-II
> interface index in case of unnumbered interface.
> But there is no mean for other router receiving the LSA to guess if a P2P link is unnumbered or not.
>
> This may be a problem when a virtual link path is terminated on such an unnumbered interface.
> As explained in section 15 this will prevent such virtual link to be up. Indeed on virtual link, the
> Hello packet
> are monocasted to the IP address found in the router LSA link that point back to the virtual link.
> If it is
> an unnumbered interface the router will eventually send Hello using the MIB-II If index as
> destination IP address.
>
> Isn't it better to encode a valid router IP address instead of the MIB-II index in the router LSA
> type 1 link
> when describing unnumbered interface?
> Do you see any interop problem?
>
> Regards,
> Fabien
>
> ====================================================================================================
> ===
> This electronic transmission and any files attached to it are strictly confidential and intended
> solely for the addressee.   If you are not the intended addressee, you must not disclose, copy or
> take any action in reliance of this transmission.  If you have received this transmission in error,
> please notify us by return and delete the same.  The views expressed in this electronic transmission
> do not necessarily reflect those of Atos Origin or any of its subsidiary companies. Although the
> sender endeavours to maintain a computer virus free network, the sender does not warrant that this
> transmission is virus-free and will not be liable for any damages resulting from any virus
> transmitted.  Thank You.
> ====================================================================================================
> ===
[prev in list] [next in list] [prev in thread] [next in thread]