BGP-LS Extension for Inter-AS Topology Retrieval
draft-ietf-idr-bgpls-inter-as-topology-ext-07
IDR Working Group A. Wang
Internet-Draft China Telecom
Intended status: Standards Track H. Chen
Expires: April 2, 2020 Futurewei
K. Talaulikar
Cisco Systems
S. Zhuang
Huawei Technologies
S. Ma
Mellanox Technologies
September 30, 2019
BGP-LS Extension for Inter-AS Topology Retrieval
draft-ietf-idr-bgpls-inter-as-topology-ext-07
Abstract
This document describes the process to build Border Gateway Protocol-
Link State (BGP-LS) key parameters in inter-domain scenario, defines
one new BGP-LS Network Layer Reachability Information (NLRI) type
(Stub Link NLRI) and some new inter Autonomous (inter-AS) Traffic
Engineering (TE) related Type-Length-Values (TLVs) for BGP-LS to let
Software Definition Network (SDN) controller retrieve the network
topology automatically under various inter-AS environments.
Such extension and process can enable the network operator to collect
the interconnect information between different domains and then
calculate the overall network topology automatically based on the
information provided by BGP-LS protocol.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 2, 2020.
Wang, et al. Expires April 2, 2020 [Page 1]
Internet-Draft BGP-LS-Inter-AS-Ext September 2019
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Inter-AS Domain Scenarios. . . . . . . . . . . . . . . . . . 3
5. Stub Link NLRI . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. Inter-AS Native IP Scenario . . . . . . . . . . . . . . . 5
5.2. Inter-AS TE Scenario . . . . . . . . . . . . . . . . . . 6
6. Inter-AS TE NLRI related TLVs . . . . . . . . . . . . . . . . 6
6.1. Remote AS Number TLV . . . . . . . . . . . . . . . . . . 7
6.2. IPv4 Remote ASBR ID . . . . . . . . . . . . . . . . . . . 7
6.3. IPv6 Remote ASBR ID . . . . . . . . . . . . . . . . . . . 8
7. Topology Reconstruction. . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 9
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
9.1. New BGP-LS NLRI type . . . . . . . . . . . . . . . . . . 9
9.2. New Link Descriptors . . . . . . . . . . . . . . . . . . 10
10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 10
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
11.1. Normative References . . . . . . . . . . . . . . . . . . 10
11.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
BGP-LS [RFC7752] describes the methodology that using BGP protocol to
transfer the Link-State information. Such method can enable SDN
controller to collect the underlay network topology automatically,
Show full document text