Skip to main content

BGP Enabled ServiceS (bess)

Group history

Date By Action
2022-07-01 Liz Flynn sent scheduled notification for IETF-114
2022-05-04 Tina Dang
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 …
2022-03-23 Amy K. Vezza Area Director changed to Andrew Alston from Martin Vigoureux
2022-02-25 Liz Flynn sent scheduled notification for IETF-113
2021-10-15 Liz Flynn sent scheduled notification for IETF-112
2021-07-02 Liz Flynn sent scheduled notification for IETF-111
2021-02-12 Liz Flynn sent scheduled notification for IETF-110
2020-10-23 Liz Flynn sent scheduled notification for IETF-109
2020-07-02 Liz Flynn sent scheduled notification for IETF-108
2020-03-03 Stephane Litkowski Changed milestone "Submit a YANG datamodel for mVPN to IESG as PS", set due date to December 2020 from June 2019, added draft-ietf-bess-mvpn-yang to milestone
2020-03-03 Stephane Litkowski Changed milestone "Submit a YANG datamodel for L2VPN to IESG as PS", set due date to December 2020 from January 2019, added draft-ietf-bess-l2vpn-yang to milestone
2020-03-03 Stephane Litkowski
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 …
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
2020-03-03 Stephane Litkowski
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 …
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
2020-03-03 Stephane Litkowski Changed milestone "Submit specifications for VPLS multi-homing to IESG as PS", resolved as "Done", added draft-ietf-bess-vpls-multihoming to milestone
2020-03-03 Stephane Litkowski Changed milestone "Submit specification for BGP NSH controlplane to IESG as PS", resolved as "Done", added draft-ietf-bess-nsh-bgp-control-plane to milestone
2020-03-03 Stephane Litkowski
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 …
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/
2020-03-03 Stephane Litkowski
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 …
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/
2020-02-28 Liz Flynn sent scheduled notification for IETF-107
2019-10-25 Liz Flynn sent scheduled notification for IETF-106
2019-08-20 Stephane Litkowski Chairs changed to Matthew Bocci, Stephane Litkowski from Matthew Bocci, Stephane Litkowski
2019-07-26 Stephane Litkowski
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 …
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/
2019-06-28 Liz Flynn sent scheduled notification for IETF-105
2019-04-03 Stephane Litkowski
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 …
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/
2019-03-01 Liz Flynn sent scheduled notification for IETF-104
2018-11-21 Stephane Litkowski Urls changed to https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw (Implementation Requirement Policy), https://trac.ietf.org/trac/bess/report/1 (Issue tracker), https://trac.ietf.org/trac/bess/wiki (Wiki) from https://trac.ietf.org/trac/bess/report/1 (Issue tracker), https://trac.ietf.org/trac/bess/wiki (Wiki)
2018-11-15 Martin Vigoureux Changed milestone "Submit a YANG datamodel for mVPN to IESG as PS", set state to active from review, accepting new milestone
2018-11-15 Martin Vigoureux Changed milestone "Submit specification for BGP NSH controlplane to IESG as PS", set state to active from review, accepting new milestone
2018-11-15 Martin Vigoureux Changed milestone "Submit a YANG datamodel for L2VPN to IESG as PS", set state to active from review, accepting new milestone
2018-11-15 Stephane Litkowski Added milestone "Submit specification for BGP NSH controlplane to IESG as PS" for review, due March 2019
2018-11-15 Stephane Litkowski Added milestone "Submit a YANG datamodel for mVPN to IESG as PS" for review, due June 2019
2018-11-15 Stephane Litkowski Added milestone "Submit a YANG datamodel for L2VPN to IESG as PS" for review, due January 2019
2018-11-15 Stephane Litkowski Changed milestone "Submit a Yang or SMI datamodel for E-VPN to IESG as PS", added draft-ietf-bess-evpn-yang to milestone
2018-11-15 Stephane Litkowski Changed milestone "Submit a Yang or SMI datamodel for RFC4364 to IESG as PS", added draft-ietf-bess-l3vpn-yang to milestone
2018-11-15 Stephane Litkowski Changed milestone "Submit specifications for VPLS multi-homing to IESG as PS", set due date to December 2018 from July 2015, added draft-ietf-bess-vpls-multihoming to milestone
2018-11-15 Stephane Litkowski Changed milestone "Submit a Yang or SMI datamodel for E-VPN to IESG as PS", set due date to January 2019 from June 2016
2018-11-15 Stephane Litkowski Changed milestone "Submit a Yang or SMI datamodel for RFC4364 to IESG as PS", set due date to January 2019 from June 2016
2018-11-15 Stephane Litkowski Deleted milestone "Submit specifications for TRILL/E-VPN interoperability to IESG as PS"
2018-11-15 Stephane Litkowski Changed milestone "Submit specification of a multicast VPN MIB to IESG as PS", resolved as "Done"
2018-11-15 Stephane Litkowski Deleted milestone "Submit specification of BGP as an MVPN PE-CE protocol to IESG as PS"
2018-11-15 Stephane Litkowski Deleted milestone "Submit specification of BGP-signaled end-system IP/VPNs to IESG as PS"
2018-11-15 Stephane Litkowski
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 …
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/
2018-11-15 Stephane Litkowski
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 …
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/
2018-10-19 Liz Flynn sent scheduled notification for IETF-103
2018-08-09 Matthew Bocci Secretaries changed to mankamana mishra from
2018-07-03 Liz Flynn sent scheduled notification for IETF-102
2018-03-21 Amy K. Vezza Shepherding AD changed to Martin Vigoureux from Alvaro Retana
2018-03-21 Amy K. Vezza Chairs changed to Matthew Bocci, Stephane Litkowski from Matthew Bocci, Stephane Litkowski, Martin Vigoureux
2018-02-27 Liz Flynn sent scheduled notification for IETF-101
2018-02-13 Alvaro Retana Chairs changed to Martin Vigoureux, Matthew Bocci, Stephane Litkowski from Martin Vigoureux, Stephane Litkowski
2017-12-01 Alvaro Retana Chairs changed to Martin Vigoureux, Stephane Litkowski from Martin Vigoureux, Thomas Morin
2017-10-20 Stephanie McCammon sent scheduled notification for IETF-100
2017-08-03 Martin Vigoureux Changed milestone "Submit specification for the use of E-VPN for datacenter overlays  to IESG as PS", resolved as "Done", added draft-ietf-bess-evpn-overlay to milestone
2017-06-23 Stephanie McCammon sent scheduled notification for IETF-99
2017-03-03 Stephanie McCammon sent scheduled notification for IETF-98
2016-10-21 Stephanie McCammon sent scheduled notification for IETF-97
2016-06-24 Stephanie McCammon sent scheduled notification for IETF-96
2016-04-06 Martin Vigoureux Name changed to BGP Enabled ServiceS from BGP Enabled Services
2016-03-11 Stephanie McCammon sent scheduled notification for IETF-95
2016-01-26 Martin Vigoureux Changed milestone "Submit specifications for PBB/E-VPN interoperability to IESG as PS", resolved as "Done"
2016-01-26 Martin Vigoureux Changed milestone "Submit specifications for SPB-M/E-VPN interoperability to IESG as PS", resolved as "Done", added draft-ietf-bess-spbm-evpn to milestone, removed draft-ietf-l2vpn-spbm-evpn from milestone
2016-01-26 Martin Vigoureux Changed milestone "Submit specification for extranet support in multicast VPNs to IESG as PS", resolved as "Done", added draft-ietf-bess-mvpn-extranet to milestone, removed draft-ietf-l3vpn-mvpn-extranet from milestone
2015-10-09 Stephanie McCammon sent scheduled notification for IETF-94
2015-09-18 Martin Vigoureux Changed milestone "Submit specifications for E-VPN to IESG as PS", resolved as "Done"
2015-09-18 Martin Vigoureux Changed milestone "Submit specification for multicast VPN bidir P-tunnels to IESG as PS", resolved as "Done"
2015-06-26 Stephanie McCammon sent scheduled notification for IETF-93
2015-06-15 Cindy Morgan Mailing list archive changed to https://mailarchive.ietf.org/arch/browse/bess/ from http://www.ietf.org/mail-archive/web/bess/
2015-03-25 Amy K. Vezza Shepherding AD changed to Alvaro Retana from
2015-02-27 Stephanie McCammon sent scheduled notification for IETF-92
2014-12-11 Thomas Morin Changed milestone "Submit specification of the BGP ACCEPT_OWN Community Attribute to IESG as PS", resolved as "Done"
2014-10-17 Cindy Morgan Added milestone "Submit a Yang or SMI datamodel for E-VPN to IESG as PS", due 2016-06-30, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit a Yang or SMI datamodel for RFC4364 to IESG as PS", due 2016-06-30, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit E-VPN OAM to IESG as PS", due 2015-12-31, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit specifications for TRILL/E-VPN interoperability to IESG as PS", due 2015-11-30, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit specifications for SPB-M/E-VPN interoperability to IESG as PS", due 2015-11-30, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit specifications for PBB/E-VPN interoperability to IESG as PS", due 2015-09-30, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit specifications for VPLS multi-homing to IESG as PS", due 2015-07-31, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit specification for the use of E-VPN for datacenter overlays  to IESG as PS", due 2015-06-30, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit specification of a multicast VPN MIB to IESG as PS", due 2015-06-30, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit specification of BGP as an MVPN PE-CE protocol to IESG as PS", due 2015-04-30, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit specification of BGP-signaled end-system IP/VPNs to IESG as PS", due 2015-02-28, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit specification for extranet support in multicast VPNs to IESG as PS", due 2015-02-28, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit specifications for E-VPN to IESG as PS", due 2014-12-31, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit specification for multicast VPN bidir P-tunnels to IESG as PS", due 2014-12-31, from approved charter
2014-10-17 Cindy Morgan Added milestone "Submit specification of the BGP ACCEPT_OWN Community Attribute to IESG as PS", due 2014-11-30, from approved charter
2014-10-17 Cindy Morgan Charter approved, group active
2014-09-25 Adrian Farrel Group created in state Proposed