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

meicong <meicong@huawei.com> Thu, 24 September 2020 06:23 UTC

From: meicong <meicong@huawei.com>
To: "lsr@ietf.org" <lsr@ietf.org>
CC: "Jiangyu (China)" <china.jiangyu@huawei.com>, Huzhibo <huzhibo@huawei.com>
Thread-Topic: some doubt about RFC 5185 (Multi Area Adjacency)
Thread-Index: AdaRcorsVON76dDOSTSXE4Q5MMLqbAAyGwtA
Date: Thu, 24 Sep 2020 06:23:08 +0000
Message-ID: <C45D89487DC65947BCBD4149DD0967C334E0AE27@dggeml523-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
Content-Type: multipart/alternative; boundary="_000_C45D89487DC65947BCBD4149DD0967C334E0AE27dggeml523mbschi_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/pkcmy3_o-zXoKi2GHQ6INECoH9Y>
Subject: [Lsr] some doubt about RFC 5185 (Multi Area Adjacency)
Precedence: list


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?







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

[Lsr] some doubt about RFC 5185 (Multi Area Adjac… meicong
Re: [Lsr] some doubt about RFC 5185 (Multi Area A… Acee Lindem (acee)