draft-ietf-idr-bgpls-inter-as-topology-ext-08.txt   draft-ietf-idr-bgpls-inter-as-topology-ext-09.txt 
IDR Working Group A. Wang IDR Working Group A. Wang
Internet-Draft China Telecom Internet-Draft China Telecom
Intended status: Standards Track H. Chen Intended status: Standards Track H. Chen
Expires: October 4, 2020 Futurewei Expires: April 1, 2021 Futurewei
K. Talaulikar K. Talaulikar
Cisco Systems Cisco Systems
S. Zhuang S. Zhuang
Huawei Technologies Huawei Technologies
April 2, 2020 September 28, 2020
BGP-LS Extension for Inter-AS Topology Retrieval BGP-LS Extension for Inter-AS Topology Retrieval
draft-ietf-idr-bgpls-inter-as-topology-ext-08 draft-ietf-idr-bgpls-inter-as-topology-ext-09
Abstract Abstract
This document describes the process to build Border Gateway Protocol- This document describes the process to build Border Gateway Protocol-
Link State (BGP-LS) key parameters in inter-domain scenario, defines Link State (BGP-LS) key parameters in inter-domain scenario, defines
one new BGP-LS Network Layer Reachability Information (NLRI) type one new BGP-LS Network Layer Reachability Information (NLRI) type
(Stub Link NLRI) and some new inter Autonomous (inter-AS) Traffic (Stub Link NLRI) and some new inter Autonomous (inter-AS) Traffic
Engineering (TE) related Type-Length-Values (TLVs) for BGP-LS to let Engineering (TE) related Type-Length-Values (TLVs) for BGP-LS to let
Software Definition Network (SDN) controller retrieve the network Software Definition Network (SDN) controller retrieve the network
topology automatically under various inter-AS environments. topology automatically under various inter-AS environments.
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 4, 2020. This Internet-Draft will expire on April 1, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 5, line 30 skipping to change at page 5, line 30
In such situation, different domain may run different IGP protocol. In such situation, different domain may run different IGP protocol.
The operator needs to know the inter-as topology first to calculate The operator needs to know the inter-as topology first to calculate
the end to end optimal path centrally. the end to end optimal path centrally.
When IGP A or IGP B in Figure 1 runs native IS-IS/OSPF protocol, the When IGP A or IGP B in Figure 1 runs native IS-IS/OSPF protocol, the
operator can use passive feature for the inter-domain links to let operator can use passive feature for the inter-domain links to let
the routers within the IGP domain know these links. Such stub links the routers within the IGP domain know these links. Such stub links
information can then be carried within the Stub Link NLRI reported information can then be carried within the Stub Link NLRI reported
via the BGP-LS protocol to the SDN controller. via the BGP-LS protocol to the SDN controller.
For OSPF, when the interface is configured as passive, the "Linktype" For OSPFv2, when the interface is configured as passive, the
field in corresponding Router LSA will be set to 3, to indicate it "Linktype" field in corresponding Router LSA will be set to 3, to
connects with stub network. Other routers in the IGP domain can indicate it connects with stub network. Other routers in the IGP
identify such interfaces via this characteristics, and report them domain can identify such interfaces via this characteristics, and
via the newly defined "Stub Link NLRI". report them via the newly defined "Stub Link NLRI".
For ISIS, [I-D.wang-lsr-passive-interface-attribute] describe the For OSPFv3 and ISIS, [I-D.wang-lsr-passive-interface-attribute]
method to label the passive interfaces within the network. The describes the method to label the passive interfaces within the
router that runs BGP-LS can extract these passive interfaces from network. The router that runs BGP-LS can extract these passive
other interfaces that participate in the IGP protocol and report them interfaces from other interfaces that participate in the IGP protocol
via the newly defined "Stub Link NLRI". Or else such router can only and report them via the newly defined "Stub Link NLRI".
extract such information from the adjacency of interfaces. If the
number of adjacency of the interface is zero, then such interfaces
can be reported via the newly defined "Stub Link NLRI".
The "Local Node Descriptors" should describe the characteristics of The "Local Node Descriptors" should describe the characteristics of
ASBRs that are connected these stub links. ASBRs that are connected these stub links.
When such information is reported via the BGP-LS protocol, the SDN When such information is reported via the BGP-LS protocol, the SDN
controller can construct the underlay inter-domain topology according controller can construct the underlay inter-domain topology according
to procedure described in Section 7 to procedure described in Section 7
5.2. Inter-AS TE Scenario 5.2. Inter-AS TE Scenario
skipping to change at page 11, line 25 skipping to change at page 11, line 25
11.2. Informative References 11.2. Informative References
[I-D.ietf-idr-bgpls-segment-routing-epe] [I-D.ietf-idr-bgpls-segment-routing-epe]
Previdi, S., Talaulikar, K., Filsfils, C., Patel, K., Ray, Previdi, S., Talaulikar, K., Filsfils, C., Patel, K., Ray,
S., and J. Dong, "BGP-LS extensions for Segment Routing S., and J. Dong, "BGP-LS extensions for Segment Routing
BGP Egress Peer Engineering", draft-ietf-idr-bgpls- BGP Egress Peer Engineering", draft-ietf-idr-bgpls-
segment-routing-epe-19 (work in progress), May 2019. segment-routing-epe-19 (work in progress), May 2019.
[I-D.wang-lsr-passive-interface-attribute] [I-D.wang-lsr-passive-interface-attribute]
Wang, A. and Z. Hu, "Passive Interface Attribute", draft- Wang, A., Hu, Z., and G. Mishra, "Passive Interface
wang-lsr-passive-interface-attribute-00 (work in Attribute", draft-wang-lsr-passive-interface-attribute-03
progress), January 2020. (work in progress), September 2020.
Authors' Addresses Authors' Addresses
Aijun Wang Aijun Wang
China Telecom China Telecom
Beiqijia Town, Changping District Beiqijia Town, Changping District
Beijing, Beijing 102209 Beijing, Beijing 102209
China China
Email: wangaj3@chinatelecom.cn Email: wangaj3@chinatelecom.cn
 End of changes. 7 change blocks. 
20 lines changed or deleted 17 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/