* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Bess Status Pages

BGP Enabled ServiceS (Active WG)
Rtg Area: Alvaro Retana, Deborah Brungard, Martin Vigoureux | 2014-Oct-17 —  

2020-01-10 charter

BGP Enabled ServiceS (bess)


 Current Status: Active

     Matthew Bocci <matthew.bocci@nokia.com>
     Stephane Litkowski <slitkows.ietf@gmail.com>

 Routing Area Directors:
     Deborah Brungard <db3546@att.com>
     Alvaro Retana <aretana.ietf@gmail.com>
     Martin Vigoureux <martin.vigoureux@nokia.com>

 Routing Area Advisor:
     Martin Vigoureux <martin.vigoureux@nokia.com>

     mankamana mishra <mankamis@cisco.com>

 Mailing Lists:
     General Discussion: bess@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/bess
     Archive:            https://mailarchive.ietf.org/arch/browse/bess/

Description of Working Group:

  BGP is established as a protocol for provisioning and operating Layer-3
  (routed) Virtual Private Networks (L3VPNs). It is also used in certain
  Layer-2  Virtual Private Networks (L2VPNs).

  The BGP Enabled Services (BESS) working group is responsible for
  defining, specifying, and extending network services based on BGP. In
  particular, the working group will work on the following services:

   - BGP/MPLS IP VPN solutions (based on RFC4364 and RFC4659) for
     supporting provider-provisioned L3VPNs including methods for enabling
     multicast over BGP/MPLS VPNs.

   - BGP-enabled L2VPNs (as described in RFC 4664) that operate over IP or
     MPLS packet switched network tunnels. All types of L2VPN are in scope
     provided they utilize BGP for discovery, signaling, or for some other
     purposes related to the VPN. But L2VPN solutions that operate over
     pseudowires or use LDP and that do not utilize BGP will be addressed
     by the PALS working group. Any contention in placement of the work
     between these working groups will be resolved by the chairs.

   - BGP-enabled VPN solutions for use in the data center networking.
     This work includes consideration of VPN scaling issues and
     mechanisms applicable to such environments.

   - Extensions to BGP-enabled VPN solutions for the construction of
     virtual topologies in support of services such as Service Function

  The working group may also suggest new services to be supported by BGP
  and these may be added to the working group charter subject to

  The working group may work on:

   - Mechanisms to support BGP-enabled services in the presence of multi-
     homing of Customer Edge (CE) devices to multiple Provider Edge (PE)
     devices to provide load-balancing and resilience.

   - Auto-discovery of sites that participate in the BGP-enabled service.

   - Data models for modeling, managing, and operating BGP-based services
     using SMI or YANG.

   - OAM or resiliency mechanisms operating over BGP-enabled services. But
     native data plane OAM mechanisms may be worked on only in conjunction
     with the working groups responsible for the relevant data planes.

   - Extensions to BGP and extensions to YANG models for BGP. All such
     work must be reviewed by the IDR WG, but the decision to request
     publication of such work remains with the BESS WG.

  The working group will also coordinate with other working groups where
  appropriate. For example, with the MPLS working group for issues
  related to the MPLS architecture, and the NVO3 working group for
  coordination of protocols to support data center VPNs.

  The BESS working group will not define new data plane or forwarding
  plane encapsulations.

Goals and Milestones:
  Dec 2015 - Submit E-VPN OAM to IESG as PS
  Dec 2018 - Submit specifications for VPLS multi-homing to IESG as PS
  Jan 2019 - Submit a Yang or SMI datamodel for RFC4364 to IESG as PS
  Jan 2019 - Submit a Yang or SMI datamodel for E-VPN to IESG as PS
  Jan 2019 - Submit a YANG datamodel for L2VPN to IESG as PS
  Mar 2019 - Submit specification for BGP NSH controlplane to IESG as PS
  Jun 2019 - Submit a YANG datamodel for mVPN to IESG as PS
  Done     - Submit specification of the BGP ACCEPT_OWN Community Attribute to IESG as PS
  Done     - Submit specification for multicast VPN bidir P-tunnels to IESG as PS
  Done     - Submit specifications for E-VPN to IESG as PS
  Done     - Submit specification for extranet support in multicast VPNs to IESG as PS
  Done     - Submit specification of a multicast VPN MIB to IESG as PS
  Done     - Submit specification for the use of E-VPN for datacenter overlays  to IESG as PS
  Done     - Submit specifications for PBB/E-VPN interoperability to IESG as PS
  Done     - Submit specifications for SPB-M/E-VPN interoperability to IESG as PS

All charter page changes, including changes to draft-list, rfc-list and milestones:

Generated from PyHt script /wg/bess/charters.pyht Latest update: 24 Oct 2012 16:51 GMT -