[Idr] Regarding OSPF extension for inter-area topology retrieval

"Aijun Wang" <wangaijun@tsinghua.org.cn> Mon, 23 July 2018 07:17 UTC

Return-Path: <wangaijun@tsinghua.org.cn>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAEB3130E41 for <idr@ietfa.amsl.com>; Mon, 23 Jul 2018 00:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.802
X-Spam-Level:
X-Spam-Status: No, score=0.802 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DC_PNG_UNO_LARGO=0.001, HTML_IMAGE_RATIO_08=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 1xXmxwGURVN8 for <idr@ietfa.amsl.com>; Mon, 23 Jul 2018 00:17:01 -0700 (PDT)
Received: from m176115.mail.qiye.163.com (m176115.mail.qiye.163.com [59.111.176.115]) by ietfa.amsl.com (Postfix) with ESMTP id D7EE7130E17 for <idr@ietf.org>; Mon, 23 Jul 2018 00:16:58 -0700 (PDT)
Received: from WangajPC (unknown [219.142.69.77]) by m176115.mail.qiye.163.com (Hmail) with ESMTPA id 7CAE466104F; Mon, 23 Jul 2018 15:16:48 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Peter Psenak' <ppsenak@cisco.com>, chopps@chopps.org
Cc: idr@ietf.org, "'Acee Lindem (acee)'" <acee@cisco.com>, "'Ketan Talaulikar (ketant)'" <ketant@cisco.com>, "'Dongjie (Jimmy)'" <jie.dong@huawei.com>
Date: Mon, 23 Jul 2018 15:16:46 +0800
Message-ID: <000701d42255$1e5e2d40$5b1a87c0$@org.cn>
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----=_NextPart_000_0008_01D42298.2C816D40"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdQiVR2O/y14KzohRb+x/lA57qn80A==
Content-Language: zh-cn
X-HM-Spam-Status: e1kIGBQJHllBS1VLV1koWUFKTEtLSjdXWS1ZQUlXWQkOFx4IWUFZMjUtOj cyP0FLVUtZBg++
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6NBg6Aio4QzoiLTQXMR4fIi9P TjcKCUhVSlVKTkhJSEhLSUpNTklDVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxMWVdZCAFZQUhCQ05KNwY+
X-HM-Tid: 0a64c5ff6dd79373kuws7cae466104f
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-SsuRoaoAzqo0F7RWmyzEqv0HUg>
Subject: [Idr] Regarding OSPF extension for inter-area topology retrieval
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2018 07:17:05 -0000

Hi, Peter:

 

I am Aijun Wang from China Telecom, the author of draft about
<https://datatracker.ietf.org/doc/draft-wang-lsr-ospf-inter-area-topology-ex
t/> "OSPF extension for inter-area topology retrieval", which is presented
by Mr.Jie Dong during the IETF102 meeting.

Thanks for your comments on the presentation material
<https://datatracker.ietf.org/meeting/102/materials/slides-102-lsr-ospf-inte
r-area-topology-retrieval-00> .

Below are my explanation that regarding to the question about "how it
retrievals the inter-area topology based on the extension information":

 

Let's see the graph that illustrates in Fig.1 at section 3
<https://tools.ietf.org/html/draft-wang-lsr-ospf-inter-area-topology-ext-00#
section-3>  of the draft(I copy it also below for your conveniences ):

 



 

Assuming we want to rebuild the connection between router S1 and router S2
that locates in area 1:

1)       Normally, router S1 will advertise prefix N1 within its router LSA

2)       When this router LSA reaches the ABR router R1, it will convert it
into summary LSA, add the "Source Router Information", which is router id of
S1 in this example, as proposed in this draft.

3)       R1 then floods this extension summary LSA to R0, which is running
BGP-LS protocol with IP SDN Controller. The controller then knows the
prefixes of N1 is from S1.

4)       Router S2 will do the similar process, and the controller will also
knows the prefixes N1 is also from S2

5)       Then it can reconstruct the connection between S1 and S2, which
prefix is N1. The topology within Area 1 can then be recovered accordingly.


 

Does the above explanation can answer your question. if so, I can add it
into the context of this draft in updated version.

 

 

Best Regards.

 

Aijun Wang

Network R&D and Operation Support Department

China Telecom Corporation Limited Beijing Research Institute,Beijing, China.