BGP-LS Extensions for Advertising Path MTU
draft-zhu-idr-bgp-ls-path-mtu-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-07-03
|
|
Replaces |
|
draft-hu-idr-bgp-ls-path-mtu
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group Y. Zhu
Internet-Draft China Telecom
Intended status: Standards Track Z. Hu
Expires: January 4, 2020 G. Yan
J. Yao
Huawei Technologies
July 3, 2019
BGP-LS Extensions for Advertising Path MTU
draft-zhu-idr-bgp-ls-path-mtu-01
Abstract
BGP Link State (BGP-LS) describes a mechanism by which link-state and
TE information can be collected from networks and shared with
external components using the BGP routing protocol. The centralized
controller (PCE/SDN) completes the service path calculation based on
the information transmitted by the BGP-LS and delivers the result to
the Path Computation Client (PCC) through the PCEP or BGP protocol.
Segment Routing (SR) leverages the source routing paradigm, which can
be directly applied to the MPLS architecture with no change on the
forwarding plane and applied to the IPv6 architecture, with a new
type of routing header, called SRH. The SR uses the IGP protocol as
the control protocol. Compared to the MPLS tunneling technology, the
SR does not require additional signaling. Therefore, the SR does not
support the negotiation of the Path MTU. Since Multiple labels or
SRv6 SIDs are pushed in the packets, it is more likely that the
packet size exceeds the path mtu of SR tunnel.
This document specify the extension to BGP Link State (BGP-LS) to
carry maximum transmission unit (MTU) messages of link. The PCE/SDN
calculates the Path MTU while completing the service path calculation
based on the information transmitted by the BGP-LS.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Zhu, et al. Expires January 4, 2020 [Page 1]
Internet-Draft BGP-LS Extensions for Advertising Path MTU July 2019
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 January 4, 2020.
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. Deploying scenarios . . . . . . . . . . . . . . . . . . . . . 4
3. BGP_LS Extensions for Path MTU . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
[RFC7752]describes the implementation mechanism of BGP-LS by which
link-state and TE information can be collected from networks and
shared with external components using the BGP routing protocol
[RFC4271]. BGP-LS allows the necessary Link-State Database (LSDB)
and Traffic Engineering Database (TED) information to be collected
Zhu, et al. Expires January 4, 2020 [Page 2]
Internet-Draft BGP-LS Extensions for Advertising Path MTU July 2019
Show full document text