Re: [Lsr] some doubt about RFC 5185 (Multi Area Adjacency)

["Acee Lindem (acee)" <[e-mail]>]

Hi Meicong,

From: Lsr <[e-mail]> on behalf of meicong <[e-mail]>
Date: Thursday, September 24, 2020 at 2:23 AM
To: "[e-mail]" <[e-mail]>
Cc: Huzhibo <[e-mail]>, "Jiangyu (China)" <[e-mail]>
Subject: [Lsr] some doubt about RFC 5185 (Multi Area Adjacency)



Hi ALL,
About rfc5185  OSPF Multi-Area Adjacency section 2.7 Advertising Multi-Area Adjacencies:

     Link ID = Remote's Router ID



I have the following questions:



1、I'm not sure whether “Neighbor's IP Address” means “local interface IP address” or “remote interface IP address”.

2、If it is remote interface IP address， why not use local interface IP address,  Any special considerations?



In looking at this again, I believe using the remote interface IP address is unnecessary since the interface area ID can be used to disambiguate the usage for multiple adjacencies.



Thanks,
Acee







Thanks,

In section 2.7，
Link Data = Neighbor's IP Address


2.7.  Advertising Multi-Area Adjacencies



   Multi-area adjacencies are announced as point-to-point links.  Once

   the router's multi-area adjacency reaches the FULL state, it will be

   added as a link type 1 to the Router Link State Advertisement (LSA)

   with:



      Link ID = Remote's Router ID



      Link Data = Neighbor's IP Address or IfIndex (if the underlying

      interface is unnumbered).


rfc5185  OSPF Multi-Area Adjacency