Updated Processing of Control Flags for BGP Virtual Private LAN Service (VPLS)
RFC 8614
| Document | Type |
RFC - Proposed Standard
(June 2019; No errata)
Updates RFC 4761
|
|
|---|---|---|---|
| Last updated | 2019-06-18 | ||
| Replaces | draft-singh-bess-bgp-vpls-control-flags | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Mach Chen | ||
| Shepherd write-up | Show (last changed 2019-01-29) | ||
| IESG | IESG state | RFC 8614 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Martin Vigoureux | ||
| Send notices to | Mach Chen <mach.chen@huawei.com> | ||
| IANA | IANA review state | IANA OK - No Actions Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) R. Singh
Request for Comments: 8614 K. Kompella
Updates: 4761 Juniper Networks
Category: Standards Track S. Palislamovic
ISSN: 2070-1721 Nokia
June 2019
Updated Processing of Control Flags for
BGP Virtual Private LAN Service (VPLS)
Abstract
This document updates the meaning of the Control Flags field in the
"Layer2 Info Extended Community" used for BGP Virtual Private LAN
Service (VPLS) Network Layer Reachability Information (NLRI) as
defined in RFC 4761. This document updates RFC 4761.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8614.
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.
Singh, et al. Standards Track [Page 1]
RFC 8614 Control Flags for BGP VPLS June 2019
Table of Contents
1. Introduction ....................................................2
1.1. Terminology ................................................3
2. Problem Description .............................................3
3. Updated Meaning of Control Flags in the Layer2 Info Extended
Community .......................................................3
3.1. Control Word (C-Bit) .......................................4
3.2. Sequence Flag (S-Bit) ......................................4
4. Using Point-to-Multipoint (P2MP) LSPs as Transport for
BGP VPLS ........................................................5
5. Illustrative Diagram ............................................6
6. Treatment of C-Bits and S-Bits in Multihoming Scenarios .........7
6.1. Control Word (C-Bit) .......................................7
6.2. Sequence Flag (S-Bit) ......................................7
7. Security Considerations .........................................8
8. IANA Considerations .............................................8
9. References ......................................................8
9.1. Normative References .......................................8
9.2. Informative References .....................................9
Authors' Addresses .................................................9
1. Introduction
"Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and
Signaling" [RFC4761] describes the concepts and signaling for using
the Border Gateway Protocol (BGP) to set up a VPLS. It specifies the
BGP VPLS Network Layer Reachability Information (NLRI) by which a
Provider Edge (PE) router may require other PEs in the same VPLS to
include (or not) the Control Word (CW) and sequencing information in
VPLS frames sent to this PE.
The use of the CW helps prevent the misordering of IPv4 or IPv6
Pseudowire (PW) traffic over Equal-Cost Multipath (ECMP) paths or
Link Aggregation Group (LAG) bundles. [RFC4385] describes the format
for the CW that may be used over point-to-point PWs and over a VPLS.
Along with [RFC3985], [RFC4385] also describes sequence number usage
for VPLS frames.
However, [RFC4761] does not specify the behavior of PEs in a mixed
environment where some PEs support CW/sequencing and others do not.
Singh, et al. Standards Track [Page 2]
RFC 8614 Control Flags for BGP VPLS June 2019
1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
Show full document text