Advertising SRv6 SIDs for Layer 2 Bundle Member Links in IGP
draft-dong-lsr-l2bundle-srv6-00
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Authors |
|
Jie Dong
,
Zhibo Hu
|
|
Last updated |
|
2021-02-19
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
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)
|
LSR Routing Working Group J. Dong
Internet-Draft Z. Hu
Intended status: Standards Track Huawei Technologies
Expires: August 24, 2021 February 20, 2021
Advertising SRv6 SIDs for Layer 2 Bundle Member Links in IGP
draft-dong-lsr-l2bundle-srv6-00
Abstract
There are deployments where the Layer-3 interface on which IGP
operates is a Layer-2 interface bundle. Existing IGP advertisements
only support advertising link attributes of the Layer-3 interface.
If entities external to IGP wish to control traffic flows on the
individual physical links that comprise the Layer-2 interface bundle,
link attribute information about the bundle members is advertised by
IGP extensions for Layer-2 (L2) bundle.
When Segment Routing over IPv6 (SRv6) is used with Layer-2 interface
bundle to control traffic flows on the individual member links, the
SRv6 SIDs which represent the Layer 2 member links of the L2 bundle
needs to be advertised in IGP.
This document proposes the IGP extensions to advertise the SRv6 SIDs
of the Layer 2 (L2) bundle member links.
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.
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."
Dong & Hu Expires August 24, 2021 [Page 1]
Internet-Draft IGP L2 bundle for SRv6 February 2021
This Internet-Draft will expire on August 24, 2021.
Copyright Notice
Copyright (c) 2021 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. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. SRv6 Function for L2 Bundle Member Links . . . . . . . . . . 3
4. Advertising SRv6 SIDs for L2 Bundle Members . . . . . . . . . 3
4.1. SRv6 SIDs Encodings for IS-IS L2 Bundle . . . . . . . . . 3
4.1.1. L2 Bundle Member SRv6 End.XU SID Sub-TLV . . . . . . 4
4.1.2. L2 Bundle Member SRv6 LAN End.XU SID Sub-TLV . . . . 5
4.2. SRv6 SIDs Encodings for OSPF L2 Bundle . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
There are deployments where the Layer-3 interface on which an IGP
adjacency is established is a Layer-2 interface bundle, for instance,
a Link Aggregation Group (LAG) [IEEE802.1AX]. This reduces the
number of adjacencies that need to be maintained by the routing
protocol in cases where there are parallel links between the
neighbors. Entities external to IS-IS such as Path Computation
Elements (PCEs) [RFC4655] may wish to control traffic flows on
individual members of the underlying Layer-2 bundle. In order to do
so, link attribute information about individual bundle members is
required.
Dong & Hu Expires August 24, 2021 [Page 2]
Internet-Draft IGP L2 bundle for SRv6 February 2021
[RFC8668] and [I-D.ietf-lsr-ospf-l2bundles] specify the IGP
Show full document text