[Idr] 答复: FW: New Version Notification for draft-wang-idr-bgpls-inter-as-topology-ext-01.txt
"Aijun Wang" <wangaijun@tsinghua.org.cn> Mon, 23 July 2018 08:38 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 F371C130E40 for <idr@ietfa.amsl.com>; Mon, 23 Jul 2018 01:38:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.019
X-Spam-Level: *
X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_BL=0.01, RCVD_IN_MSPIKE_L3=2.899, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=no 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 FJfIL68u5-Sc for <idr@ietfa.amsl.com>; Mon, 23 Jul 2018 01:38:48 -0700 (PDT)
Received: from m21397.mail.qiye.163.com (m21397.mail.qiye.163.com [223.252.213.97]) by ietfa.amsl.com (Postfix) with ESMTP id 611F4130E57 for <idr@ietf.org>; Mon, 23 Jul 2018 01:38:41 -0700 (PDT)
Received: from WangajPC (unknown [219.142.69.77]) by m21397.mail.qiye.163.com (Hmail) with ESMTPA id 0FD1D141A92; Mon, 23 Jul 2018 16:38:30 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Jeff Tantsura' <jefftant.ietf@gmail.com>, "'Ketan Talaulikar (ketant)'" <ketant@cisco.com>
Cc: idr@ietf.org
References: <008501d40f72$8d7ee8e0$a87cbaa0$@org.cn>
In-Reply-To: <008501d40f72$8d7ee8e0$a87cbaa0$@org.cn>
Date: Mon, 23 Jul 2018 16:38:28 +0800
Message-ID: <002501d42260$87d5fd60$9781f820$@org.cn>
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----=_NextPart_000_0026_01D422A3.95F93D60"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdQPcFXAn6SaPOKOT52Eyiv0xhncSQAAUxHgAAA0c8AEuf0JkA==
Content-Language: zh-cn
X-HM-Spam-Status: e1ktWUFJV1koWUFKTEtLSjdXWQgYFAkeWUFLVUtXWQkOFx4IWUFZMjUtOj cyP0FLVUtZBg++
X-HM-Sender-Digest: e1kSHx4VD1lBWUc6MRA6HCo6PzoiDzQJCT0#VkkJHklPCj5VSlVKTkhJ SEhOSkpDTUNPVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZDB4ZWUEdGhcIHldZ CAFZQUNPTExDN1dZEgtZQVlJSkJVSk9JVU1CVUxMWQY+
X-HM-Tid: 0a64c64a381f7f6bkuuk0fd1d141a92
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/3uN2wCkkR57vhIEqifyCV6S_qs0>
Subject: [Idr] 答复: FW: New Version Notification for draft-wang-idr-bgpls-inter-as-topology-ext-01.txt
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 08:38:51 -0000
Hi, Jeff and Ketan: Thanks for your comments on the presentation <https://datatracker.ietf.org/meeting/102/materials/slides-102-idr-sessb-bgp-ls-extend-for-inter-as-topology-retrieval-00> at the IETF 102 meeting, below are the responses for your comments and questions: Ketan: It would be good to describe the new TLVs in the document [Aijun Wang]: Yes, I will describe them in detail in the updated version. Jeff Tantsura: The address space used on the interconnection address space is uncommon to be imported into the IGP. The address space from other operator does not belong in your IGP address space. [Aijun Wang]: As I described in the scenario slide(I copy it also for your convenience), it is common for one operator occupy several IGP domains that composited by its backbone network and several MAN(Metrio-Area-Network)s/IDCs. When they do Traffic Engineering from end to end that spans MAN-Backbone-IDC, they need to know the inter-as topology via the proposals that described in this draft. Then it is naturally to redistribute the interconnection prefixes. If these IGP domains belong to different operators, it is uncommon do inter-as traffic engineering under one PCE/SDN controller/, then it is unnecessary to get the inter-as topology. But redistributing the interconnection prefixes will do no harm to their networks, because the redistributed interconnection link prefixes belongs to both of them, they are also the interfaces address on the border routers. If the above explanation acceptable, I can add it to the “security consideration” part of the updated version of this draft. Thanks in advance. Best Regards. Aijun Wang Network R&D and Operation Support Department China Telecom Corporation Limited Beijing Research Institute,Beijing, China. -----邮件原件----- 发件人: Aijun Wang [mailto:wangaijun@tsinghua.org.cn] 发送时间: 2018年6月29日 14:30 收件人: idr@ietf.org 主题: [Idr] FW: New Version Notification for draft-wang-idr-bgpls-inter-as-topology-ext-01.txt Hi, All IDRer: We have uploaded the updated version of the draft about BGP-LS extension for inter-AS topology retrieval, which addresses the valuable comments from Acee and Ketan during IETF 101 meeting in London. The draft can be access at <https://tools.ietf.org/html/draft-wang-idr-bgpls-inter-as-topology-ext-01> https://tools.ietf.org/html/draft-wang-idr-bgpls-inter-as-topology-ext-01 Any comments and suggestions are welcome. Best Regards. Aijun Wang Network R&D and Operation Support Department China Telecom Corporation Limited Beijing Research Institute,Beijing, China. -----邮件原件----- 发件人: <mailto:internet-drafts@ietf.org> internet-drafts@ietf.org [ <mailto:internet-drafts@ietf.org> mailto:internet-drafts@ietf.org] 发送时间: 2018年6月29日 14:14 收件人: Aijun Wang 主题: New Version Notification for draft-wang-idr-bgpls-inter-as-topology-ext-01.txt A new version of I-D, draft-wang-idr-bgpls-inter-as-topology-ext-01.txt has been successfully submitted by Aijun Wang and posted to the IETF repository. Name: draft-wang-idr-bgpls-inter-as-topology-ext Revision: 01 Title: BGP-LS Extend for Inter-AS Topology Retrieval Document date: 2018-06-28 Group: Individual Submission Pages: 7 URL: <https://www.ietf.org/internet-drafts/draft-wang-idr-bgpls-inter-as-topology-ext-01.txt> https://www.ietf.org/internet-drafts/draft-wang-idr-bgpls-inter-as-topology-ext-01.txt Status: <https://datatracker.ietf.org/doc/draft-wang-idr-bgpls-inter-as-topology-ext/> https://datatracker.ietf.org/doc/draft-wang-idr-bgpls-inter-as-topology-ext/ Htmlized: <https://tools.ietf.org/html/draft-wang-idr-bgpls-inter-as-topology-ext-01> https://tools.ietf.org/html/draft-wang-idr-bgpls-inter-as-topology-ext-01 Htmlized: <https://datatracker.ietf.org/doc/html/draft-wang-idr-bgpls-inter-as-topology-ext> https://datatracker.ietf.org/doc/html/draft-wang-idr-bgpls-inter-as-topology-ext Diff: <https://www.ietf.org/rfcdiff?url2=draft-wang-idr-bgpls-inter-as-topology-ext-01> https://www.ietf.org/rfcdiff?url2=draft-wang-idr-bgpls-inter-as-topology-ext-01 Abstract: This document describes the process to build BGP-LS key parameters in Native IP multi-domain scenario and defines some new inter-AS TE related TLVs for BGP-LS to let SDN controller retrieve the network topology automatically under various environments. Such process and extension can expand the usage of BGP-LS protocol to multi- domain, enable the network operator to collect the connection relationship between different AS domains and then calculate the overall network topology automatically based on the information provided by BGP-LS protocol. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat _______________________________________________ Idr mailing list <mailto:Idr@ietf.org> Idr@ietf.org <https://www.ietf.org/mailman/listinfo/idr> https://www.ietf.org/mailman/listinfo/idr