BGP Enabled ServiceS (bess)

Resources changed to tracker https://trac.ietf.org/trac/bess/report/1 (Issue tracker), webpage https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw (Implementation Requirement Policy), wiki https://trac.ietf.org/trac/bess/wiki (Wiki - Retired. No longer maintained), wiki https://wiki.ietf.org/group/bess (WiKi), zulip https://zulip.ietf.org/#narrow/stream/109-bess (Zulip Stream) from tracker https://trac.ietf.org/trac/bess/report/1 (Issue tracker), webpage https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw (Implementation Requirement Policy), wiki https://trac.ietf.org/trac/bess/wiki (Wiki - Retired), wiki https://wiki.ietf.org/group/bess (WiKi), zulip https://zulip.ietf.org/#narrow/stream/109-bess (Zulip Stream)

Resources changed to tracker https://trac.ietf.org/trac/bess/report/1 (Issue tracker), webpage https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw (Implementation Requirement Policy), wiki https://trac.ietf.org/trac/bess/wiki (Wiki - Retired), wiki https://wiki.ietf.org/group/bess (WiKi), zulip https://zulip.ietf.org/#narrow/stream/109-bess (Zulip Stream) from tracker https://trac.ietf.org/trac/bess/report/1 (Issue tracker), webpage https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw (Implementation Requirement Policy), wiki https://trac.ietf.org/trac/bess/wiki (Wiki), zulip https://zulip.ietf.org/#narrow/stream/109-bess (Zulip Stream)

Resources changed to tracker https://trac.ietf.org/trac/bess/report/1 (Issue tracker), webpage https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw (Implementation Requirement Policy), wiki https://trac.ietf.org/trac/bess/wiki (Wiki), zulip https://zulip.ietf.org/#narrow/stream/109-bess (Zulip Stream) from tracker https://trac.ietf.org/trac/bess/report/1 (Issue tracker), webpage https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw (Implementation Requirement Policy), wiki https://trac.ietf.org/trac/bess/wiki (Wiki)

Changed milestone "Submit a Yang or SMI datamodel for E-VPN to IESG as PS", set due date to December 2020 from January 2019, added draft-ietf-bess-evpn-yang to milestone

Changed milestone "Submit a Yang or SMI datamodel for RFC4364 to IESG as PS", set due date to December 2020 from January 2019, added draft-ietf-bess-l3vpn-yang to milestone

The BGP Enabled Services (BESS) working group is responsible for defining, specifying, and extending network services based on BGP. In particular it focuses on BGP based L2VPN, L3VPN, EVPN, multicast VPN.

The current WG focus is mainly on EVPN which remains a brand new technology while still doing housekeeping on the other topics. An RFC7432bis will start to be prepared soon to fix the known issues in the original specification of EVPN.
The WG has a significant amount of work on flexible Designated Forwarder Election (DF election) procedures to forward Broadcast Unknown Multicast traffic within an EVPN. Such flexibility is required to accommodate various use cases. The framework for the flexible DF election has been published while multiple optional procedures are under discussions within the WG [2] [3] [4] [13] [14].
The WG is also actively working on YANG models for the VPN services [5] [6] [7] [8]. We are running late on this topic but we expect this work to be closed in 2020.
The WG is also working on service function chaining based on BGP [9] [10]. BGP NSH controlplane [9] is under review by the IESG. While [10] is on hold waiting for volunteers to finish the work as a significant amount of work is still require before publication.
The WG is finishing the work on Virtual Ethernet Segments [15] which will bring more flexibility in definition of ethernet segments.
The WG has started working on secure VPNs to ensure a secured transport of VPN services [12].


[Last Updated: March 2020.]

References:
[2] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-per-mcast-flow-df-election/
[3] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-pref-df/
[4] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-fast-df-recovery/
[5] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-yang/
[6] https://datatracker.ietf.org/doc/draft-ietf-bess-l2vpn-yang/
[7] https://datatracker.ietf.org/doc/draft-ietf-bess-l3vpn-yang/
[8] https://datatracker.ietf.org/doc/draft-liu-bess-mvpn-yang/
[9] https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/
[10] https://datatracker.ietf.org/doc/draft-ietf-bess-service-chaining/
[12] https://datatracker.ietf.org/doc/draft-sajassi-bess-secure-evpn/
[13] https://datatracker.ietf.org/doc/draft-mohanty-bess-weighted-hrw/
[14] https://datatracker.ietf.org/doc/draft-liu-bess-evpn-mcast-bw-quantity-df-election/
[15] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-virtual-eth-segment/

The BGP Enabled Services (BESS) working group is responsible for defining, specifying, and extending network services based on BGP. In particular it focuses on BGP based L2VPN, L3VPN, EVPN, multicast VPN.

The current WG focus is mainly on EVPN which remains a brand new technology while still doing housekeeping on the other topics. An RFC7432bis will start to be prepared soon to fix the known issues in the original specification of EVPN.
The WG has a significant amount of work on flexible Designated Forwarder Election (DF election) procedures to forward Broadcast Unknown Multicast traffic within an EVPN. Such flexibility is required to accommodate various use cases. The framework for the flexible DF election has been published while multiple optional procedures are under discussions within the WG [2] [3] [4] [13] [14].
The WG is also actively working on YANG models for the VPN services [5] [6] [7] [8]. We are running late on this topic but we expect this work to be closed in 2020.
The WG is also working on service function chaining based on BGP [9] [10]. BGP NSH controlplane [9] is under review by the IESG. While [10] is on hold waiting for volunteers to finish the work as a significant amount of work is still require before publication.
The WG is finishing the work on Virtual Ethernet Segments [14] which will bring more flexibility in definition of ethernet segments.
The WG has started working on secure VPNs to ensure a secured transport of VPN services [12].


[Last Updated: March 2020.]

References:
[2] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-per-mcast-flow-df-election/
[3] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-pref-df/
[4] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-fast-df-recovery/
[5] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-yang/
[6] https://datatracker.ietf.org/doc/draft-ietf-bess-l2vpn-yang/
[7] https://datatracker.ietf.org/doc/draft-ietf-bess-l3vpn-yang/
[8] https://datatracker.ietf.org/doc/draft-liu-bess-mvpn-yang/
[9] https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/
[10] https://datatracker.ietf.org/doc/draft-ietf-bess-service-chaining/
[12] https://datatracker.ietf.org/doc/draft-sajassi-bess-secure-evpn/
[13] https://datatracker.ietf.org/doc/draft-mohanty-bess-weighted-hrw/
[14] https://datatracker.ietf.org/doc/draft-liu-bess-evpn-mcast-bw-quantity-df-election/
[15] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-virtual-eth-segment/

The BGP Enabled Services (BESS) working group is responsible for defining, specifying, and extending network services based on BGP. In particular it focuses on BGP based L2VPN, L3VPN, EVPN, multicast VPN.

The current WG focus is mainly on EVPN which remains a brand new technology while still doing housekeeping on the other topics. An RFC7432bis will start to be prepared soon to fix the known issues in the original specification of EVPN.
The WG has a significant amount of work on flexible Designated Forwarder Election (DF election) procedures to forward Broadcast Unknown Multicast traffic within an EVPN. Such flexibility is required to accommodate various use cases. The framework for the flexible DF election has been published while multiple optional procedures are under discussions within the WG [2] [3] [4] [13] [14].
The WG is also actively working on YANG models for the VPN services [5] [6] [7] [8]. We expect this work to be closed in 2019.
The WG is also working on service function chaining based on BGP [9] [10]. We expect this work to be closed in 2019. [10] will be soon submitted to the IESG for a final review.
The WG has recently started working on secure VPNs to ensure a secured transport of VPN services [11] [12]. However it has been identified that other working groups (IDR and I2NSF) are also working on similar technology building blocks. Consolidation is on-going on this topic.


[Last Updated: July 2019.]

References:
[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/
[2] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-per-mcast-flow-df-election/
[3] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-pref-df/
[4] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-fast-df-recovery/
[5] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-yang/
[6] https://datatracker.ietf.org/doc/draft-ietf-bess-l2vpn-yang/
[7] https://datatracker.ietf.org/doc/draft-ietf-bess-l3vpn-yang/
[8] https://datatracker.ietf.org/doc/draft-liu-bess-mvpn-yang/
[9] https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/
[10] https://datatracker.ietf.org/doc/draft-ietf-bess-service-chaining/
[11] https://datatracker.ietf.org/doc/draft-bose-secure-l3vpn/
[12] https://datatracker.ietf.org/doc/draft-sajassi-bess-secure-evpn/
[13] https://datatracker.ietf.org/doc/draft-mohanty-bess-weighted-hrw/
[14] https://datatracker.ietf.org/doc/draft-liu-bess-evpn-mcast-bw-quantity-df-election/

The BGP Enabled Services (BESS) working group is responsible for defining, specifying, and extending network services based on BGP. In particular it focuses on BGP based L2VPN, L3VPN, EVPN, multicast VPN.

The current WG focus is mainly on EVPN which remains a brand new technology while still doing housekeeping on the other topics. An RFC7432bis will start to be prepared soon to fix the known issues in the original specification of EVPN.
The WG has a significant amount of work on flexible Designated Forwarder Election (DF election) procedures to forward Broadcast Unknown Multicast traffic within an EVPN. Such flexibility is required to accommodate various use cases. The framework for the flexible DF election [1] is almost ready to be published while multiple optional procedures are under discussions within the WG [2] [3] [4] [13] [14].
The WG is also actively working on YANG models for the VPN services [5] [6] [7] [8]. We expect this work to be closed in 2019.
The WG is also working on service function chaining based on BGP [9] [10]. We expect this work to be closed in 2019. [10] will be soon submitted to the IESG for a final review.
The WG has recently started working on secure VPNs to ensure a secured transport of VPN services [11] [12]. However it has been identified that other working groups (IDR and I2NSF) are also working on similar technology building blocks. The chairs will synchronize to ensure that the minimum set of building blocks is created to enable the various use cases.


[Last Updated: April 2019.]

References:
[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/
[2] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-per-mcast-flow-df-election/
[3] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-pref-df/
[4] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-fast-df-recovery/
[5] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-yang/
[6] https://datatracker.ietf.org/doc/draft-ietf-bess-l2vpn-yang/
[7] https://datatracker.ietf.org/doc/draft-ietf-bess-l3vpn-yang/
[8] https://datatracker.ietf.org/doc/draft-liu-bess-mvpn-yang/
[9] https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/
[10] https://datatracker.ietf.org/doc/draft-ietf-bess-service-chaining/
[11] https://datatracker.ietf.org/doc/draft-bose-secure-l3vpn/
[12] https://datatracker.ietf.org/doc/draft-sajassi-bess-secure-evpn/
[13] https://datatracker.ietf.org/doc/draft-mohanty-bess-weighted-hrw/
[14] https://datatracker.ietf.org/doc/draft-liu-bess-evpn-mcast-bw-quantity-df-election/

The BGP Enabled Services (BESS) working group is responsible for defining, specifying, and extending network services based on BGP. In particular it focuses on BGP based L2VPN, L3VPN, EVPN, multicast VPN.

The current WG focus is mainly on EVPN which remains a brand new technology while still doing housekeeping on the other topics.
The WG has a significant amount of work on flexible Designated Forwarder Election (DF election) procedures to forward Broadcast Unknown Multicast traffic within an EVPN. Such flexibility is required to accommodate various use cases. The framework for the flexible DF election [1] is almost ready while multiple optional procedures are under discussions within the WG [2] [3] [4].
The WG is also actively working on YANG models for the VPN services [5] [6] [7] [8]. We expect this work to be closed in 2019.
The WG is also working on service function chaining based on BGP [9] [10]. We expect this work to be closed in 2019.
The WG has recently started working on secure VPNs to ensure a secured transport of VPN services [11] [12].


[Last Updated: November 15, 2018.]

References:
[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/
[2] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-per-mcast-flow-df-election/
[3] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-pref-df/
[4] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-fast-df-recovery/
[5] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-yang/
[6] https://datatracker.ietf.org/doc/draft-ietf-bess-l2vpn-yang/
[7] https://datatracker.ietf.org/doc/draft-ietf-bess-l3vpn-yang/
[8] https://datatracker.ietf.org/doc/draft-liu-bess-mvpn-yang/
[9] https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/
[10] https://datatracker.ietf.org/doc/draft-ietf-bess-service-chaining/
[11] https://datatracker.ietf.org/doc/draft-bose-secure-l3vpn/
[12] https://datatracker.ietf.org/doc/draft-sajassi-bess-secure-evpn/

The BGP Enabled Services (BESS) working group is responsible for defining, specifying, and extending network services based on BGP. In particular it focuses on BGP based L2VPN, L3VPN, EVPN, multicast VPN.

The current WG focus is mainly on EVPN which remains a brand new technology while still doing housekeeping on the other topics.
The WG has a significant amount of work on flexible Designated Forwarder Election (DF election) procedures to forward Broadcast Unknown Multicast traffic within an EVPN. Such flexibility is required to accommodate various use cases. The framework for the flexible DF election [1] is almost ready while multiple optional procedures are under discussions within the WG [2] [3] [4].
The WG is also actively working on YANG models for the VPN services [5] [6] [7] [8]. We expect this work to be closed in 2019.
The WG is also working on service function chaining based on BGP [9] [10]. We expect this work to be closed in 2019.
The WG has recently started working on secure VPNs to ensure a secured transport of VPN services.


[Last Updated: November 15, 2018.]

References:
[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/
[2] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-per-mcast-flow-df-election/
[3] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-pref-df/
[4] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-fast-df-recovery/
[5] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-yang/
[6] https://datatracker.ietf.org/doc/draft-ietf-bess-l2vpn-yang/
[7] https://datatracker.ietf.org/doc/draft-ietf-bess-l3vpn-yang/
[8] https://datatracker.ietf.org/doc/draft-liu-bess-mvpn-yang/
[9] https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/
[10] https://datatracker.ietf.org/doc/draft-ietf-bess-service-chaining/
[11] https://datatracker.ietf.org/doc/draft-bose-secure-l3vpn/
[12] https://datatracker.ietf.org/doc/draft-sajassi-bess-secure-evpn/