[bess] Last Call: <draft-ietf-bess-mvpn-evpn-aggregation-label-10.txt> (MVPN/EVPN Tunnel Aggregation with Common Labels) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 28 June 2023 19:23 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: andrew-ietf@liquid.tech, bess-chairs@ietf.org, bess@ietf.org, draft-ietf-bess-mvpn-evpn-aggregation-label@ietf.org, slitkows.ietf@gmail.com
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <168798020789.21029.199124616864048115@ietfa.amsl.com>
Date: Wed, 28 Jun 2023 12:23:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/7vB3uqBA8eJj0h3k2It1zjZD81Y>
Subject: [bess] Last Call: <draft-ietf-bess-mvpn-evpn-aggregation-label-10.txt> (MVPN/EVPN Tunnel Aggregation with Common Labels) to Proposed Standard

The IESG has received a request from the BGP Enabled ServiceS WG (bess) to
consider the following document: - 'MVPN/EVPN Tunnel Aggregation with Common
Labels'
  <draft-ietf-bess-mvpn-evpn-aggregation-label-10.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2023-07-12. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   The MVPN specifications allow a single Point-to-Multipoint (P2MP)
   tunnel to carry traffic of multiple 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 file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-evpn-aggregation-label/


The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/4571/
   https://datatracker.ietf.org/ipr/3341/

[bess] Last Call: <draft-ietf-bess-mvpn-evpn-aggr… The IESG