[Lsr] 答复: 答复: Regarding OSPF extension for inter-area topology retrieval

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

Return-Path: <wangaijun@tsinghua.org.cn>
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 D178D130E6F for <lsr@ietfa.amsl.com>; Mon, 23 Jul 2018 04:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable 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 PCGGOafI3T_n for <lsr@ietfa.amsl.com>; Mon, 23 Jul 2018 04:07:54 -0700 (PDT)
Received: from m88102.mail.qiye.163.com (m88102.mail.qiye.163.com [106.2.88.102]) by ietfa.amsl.com (Postfix) with ESMTP id A99C0130E6D for <lsr@ietf.org>; Mon, 23 Jul 2018 04:07:53 -0700 (PDT)
Received: from WangajPC (unknown [219.142.69.77]) by m88102.mail.qiye.163.com (Hmail) with ESMTPA id 7BA6C4279B; Mon, 23 Jul 2018 19:07:40 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Peter Psenak' <ppsenak=40cisco.com@dmarc.ietf.org>, chopps@chopps.org
Cc: lsr@ietf.org, "'Ketan Talaulikar (ketant)'" <ketant@cisco.com>, "'Acee Lindem (acee)'" <acee@cisco.com>, "'Dongjie (Jimmy)'" <jie.dong@huawei.com>
References: <001601d42259$a860fff0$f922ffd0$@org.cn> <5B558E76.3010703@cisco.com> <003201d42265$cd011af0$670350d0$@org.cn> <5B55ABB5.60806@cisco.com>
In-Reply-To: <5B55ABB5.60806@cisco.com>
Date: Mon, 23 Jul 2018 19:07:38 +0800
Message-ID: <003f01d42275$5ec00eb0$1c402c10$@org.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdQibrpsHc6O2WhISBWkZYHRwC1xLwAA8G4w
Content-Language: zh-cn
X-HM-Spam-Status: e1ktWUFJV1koWUFKTEtLSjdXWQgYFAkeWUFLVUtXWQkOFx4IWUFZMjUtOj cyP0FLVUtZBg++
X-HM-Sender-Digest: e1kSHx4VD1lBWUc6NBw6Iyo5KzoiITRWNQwCLRU1LSwwCkhVSlVKTkhJ SE9PS0xLSE1CVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZDB4ZWUEdGhcIHldZ CAFZQUxITkw3V1kSC1lBWUlKQlVKT0lVTUJVTExZBg++
X-HM-Tid: 0a64c6d2cb389865kuuu7ba6c4279b
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/_RQBa4yDT7JXGIlnTm1OdwyRwag>
Subject: [Lsr] 答复: 答复: Regarding OSPF extension for inter-area topology retrieval
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.27
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: Mon, 23 Jul 2018 11:07:58 -0000

Hi, Peter:

For routers that connected by LAN, the router will establish adjacent
neighbor with DR, but not only DR advertises the connected prefixes. DR and
DRother will all advertise type 1 and type 2 LSA with each other, then the
process and proposal described in this draft will still work.
We seldom use the ip unnumbered features in our network, can we ignore it
then? Or other persons has some idea on such situation?
Anycast prefixes are often /32 long, this can be easily filtered by SDN
controller because the link prefixes between two routers will be no larger
than /32 for IPv4 network.

Best Regards.

Aijun Wang
Network R&D and Operation Support Department
China Telecom Corporation Limited Beijing Research Institute,Beijing, China.

-----邮件原件-----
发件人: Peter Psenak [mailto:ppsenak=40cisco.com@dmarc.ietf.org] 
发送时间: 2018年7月23日 18:20
收件人: Aijun Wang; 'Peter Psenak'; chopps@chopps.org
抄送: lsr@ietf.org; 'Ketan Talaulikar (ketant)'; 'Acee Lindem (acee)';
'Dongjie (Jimmy)'
主题: Re: [Lsr] 答复: Regarding OSPF extension for inter-area topology
retrieval

Hi Aijun,

On 23/07/18 11:16 , Aijun Wang wrote:
> Hi, Peter:
> 
> Actually, I consider mainly the point-to-point connection and the 
> numbered interface, which are normal in our network.
> For the two situations that you mentioned, I will investigation the 
> possible solutions and feedback you later.
> 
> For the point-to-point and numbered interface, do you have other 
> questions then?

the fact that two routers announce the same subnet, does not mean they are
connected together by p2p link. Anycast prefix is an example.

The idea you are proposing simply does not work.

thanks,
Peter


> 
> Best Regards.
> 
> Aijun Wang
> Network R&D and Operation Support Department China Telecom Corporation 
> Limited Beijing Research Institute,Beijing, China.
> 
> -----邮件原件-----
> 发件人: Peter Psenak [mailto:ppsenak=40cisco.com@dmarc.ietf.org]
> 发送时间: 2018年7月23日 16:15
> 收件人: Aijun Wang; chopps@chopps.org
> 抄送: lsr@ietf.org; 'Ketan Talaulikar (ketant)'; 'Acee Lindem (acee)'; 
> 'Dongjie (Jimmy)'
> 主题: Re: [Lsr] Regarding OSPF extension for inter-area topology 
> retrieval
> 
> Hi Aijun,
> 
> you are trying to reconstruct the topology of the remote area based on 
> the fact that two routers are connected to the same subnet. It does 
> not work
> because:
> 
> 1. connections between routers can be unnumbered 2. routers can be 
> connected via LAN, in which case only DR announces the prefix.
> 
> In summary, what you propose does not work.
> 
> thanks,
> Peter
> 
> 
> 
> On 23/07/18 09:49 , Aijun Wang wrote:
>> (Sorry for my previous mail sent wrongly to the IDR mail list, please 
>> reply on this thread within the LSR wg)
>>
>> Hi, Peter:
>>
>> I am Aijun Wang from China Telecom, the author of draft about “OSPF 
>> extension for inter-area topology retrieval”
>> <https://datatracker.ietf.org/doc/draft-wang-lsr-ospf-inter-area-topo
>> l ogy-ext/>, 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-osp
> f-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-
>> e xt-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.
>>
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
> 

_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr