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

meicong <meicong@huawei.com> Wed, 23 September 2020 06:27 UTC

Return-Path: <meicong@huawei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B53FC3A09EC for <lsr@ietfa.amsl.com>; Tue, 22 Sep 2020 23:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2E2qvn-8aMMr for <lsr@ietfa.amsl.com>; Tue, 22 Sep 2020 23:27:27 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89DEB3A09E9 for <lsr@ietf.org>; Tue, 22 Sep 2020 23:27:27 -0700 (PDT)
Received: from lhreml736-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id B27B890ADE3AA1BF6C86 for <lsr@ietf.org>; Wed, 23 Sep 2020 07:27:24 +0100 (IST)
Received: from lhreml736-chm.china.huawei.com (10.201.108.87) by lhreml736-chm.china.huawei.com (10.201.108.87) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 23 Sep 2020 07:27:24 +0100
Received: from DGGEML402-HUB.china.huawei.com (10.3.17.38) by lhreml736-chm.china.huawei.com (10.201.108.87) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Wed, 23 Sep 2020 07:27:23 +0100
Received: from DGGEML523-MBS.china.huawei.com ([169.254.3.235]) by DGGEML402-HUB.china.huawei.com ([fe80::fca6:7568:4ee3:c776%31]) with mapi id 14.03.0487.000; Wed, 23 Sep 2020 14:27:12 +0800
From: meicong <meicong@huawei.com>
To: "lsr@ietf.org" <lsr@ietf.org>
CC: "Jiangyu (China)" <china.jiangyu@huawei.com>
Thread-Topic: some doubt about RFC 5185 (Multi Area Adjacency)
Thread-Index: AdaRcorsVON76dDOSTSXE4Q5MMLqbA==
Date: Wed, 23 Sep 2020 06:27:12 +0000
Message-ID: <C45D89487DC65947BCBD4149DD0967C334E0A974@dggeml523-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.45]
Content-Type: multipart/alternative; boundary="_000_C45D89487DC65947BCBD4149DD0967C334E0A974dggeml523mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/up-WrPbFfD2pLoVOW7chaZoaQeo>
Subject: [Lsr] some doubt about RFC 5185 (Multi Area Adjacency)
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2020 06:27:30 -0000

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”.



I have test cisco’s new version, it is set Link Data as local interface IP address.



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







Thanks,
xxx

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


Authors' Addresses

   Sina Mirtorabi
   Nuova Systems
   3 West Plumeria Drive
   San Jose, CA  95134
   USA

   EMail: sina@nuovasystems.com<mailto:sina@nuovasystems.com>

   Peter Psenak
   Cisco Systems
   Apollo Business Center
   Mlynske nivy 43
   821 09 Bratislava
   Slovakia

   EMail: ppsenak@cisco.com<mailto:ppsenak@cisco.com>

   Acee Lindem (editor)
   Redback Networks
   102 Carric Bend Court
   Cary, NC  27519
   USA

   EMail: acee@redback.com<mailto:acee@redback.com>

   Anand Oswal
   Redback Networks
   300 Holger Way
   San Jose, CA  95134
   USA

   EMail: aoswal@redback.com<mailto:aoswal@redback.com>