[bess] I-D Action: draft-ietf-bess-mvpn-evpn-aggregation-label-14.txt

internet-drafts@ietf.org Thu, 05 October 2023 00:08 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: bess@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: bess@ietf.org
Message-ID: <169646452734.58500.10674755822759389818@ietfa.amsl.com>
Date: Wed, 04 Oct 2023 17:08:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/a9SW0c-4KEY5IBBl9NrFohKW_Jw>
Subject: [bess] I-D Action: draft-ietf-bess-mvpn-evpn-aggregation-label-14.txt

Internet-Draft draft-ietf-bess-mvpn-evpn-aggregation-label-14.txt is now
available. It is a work item of the BGP Enabled ServiceS (BESS) WG of the
IETF.

   Title:   MVPN/EVPN Tunnel Aggregation with Common Labels
   Authors: Zhaohui Zhang
            Eric Rosen
            Wen Lin
            Zhenbin Li
            IJsbrand Wijnands
   Name:    draft-ietf-bess-mvpn-evpn-aggregation-label-14.txt
   Pages:   17
   Dates:   2023-10-04

Abstract:

   The MVPN specifications allow a single Point-to-Multipoint (P2MP)
   tunnel to carry traffic of multiple IP VPNs (abbreviated as VPNs).
   The EVPN specifications allow a single P2MP tunnel to carry traffic
   of multiple Broadcast Domains (BDs).  These features require the
   ingress router of the P2MP tunnel to allocate an upstream-assigned
   MPLS label for each VPN or for each BD.  A packet sent on a P2MP
   tunnel then carries the label that is mapped to its VPN or BD (in
   some cases, a distinct upstream-assigned label is needed for each
   flow.)  Since each ingress router allocates labels independently,
   with no coordination among the ingress routers, the egress routers
   may need to keep track of a large number of labels.  The number of
   labels may need to be as large (or larger) than the product of the
   number of ingress routers times the number of VPNs or BDs.  However,
   the number of labels can be greatly reduced if the association
   between a label and a VPN or BD is made by provisioning, so that all
   ingress routers assign the same label to a particular VPN or BD.  New
   procedures are needed in order to take advantage of such provisioned
   labels.  These new procedures also apply to Multipoint-to-Multipoint
   (MP2MP) tunnels.  This document updates RFCs 6514, 7432 and 7582 by
   specifying the necessary procedures.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-evpn-aggregation-label/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-bess-mvpn-evpn-aggregation-label-14

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-bess-mvpn-evpn-aggregation-label-14

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts

[bess] I-D Action: draft-ietf-bess-mvpn-evpn-aggr… internet-drafts