Changed milestone "Submit specification for multicast VPN bidir
P-tunnels to IESG as PS", resolved as "Done".
Changed milestone "Submit specifications for E-VPN to IESG as PS",
resolved as "Done".
URL: https://datatracker.ietf.org/wg/bess/charter/
___
Hello working group,
This email starts a Working Group Last Call on draft-ietf-bess-ir-01
which is considered mature and ready for a final working group review.
Please read the document if you haven't read the most recent
version yet, and send your comments to the list, no later than
*October
Hi Ali and co-authors,
MEF defined E-Tree service in MEF6.1 in which each end point in the service
must have either root or leaf role (but not both); and forwarding rules among
e-tree service endpoints are specified according the endpoint role.
In order to make E-tree service across multiple SP
Support.
Thanks,
Sami
On Tue, Sep 15, 2015 at 12:43 AM, wrote:
> Hello working group,
>
> This email starts a two-week poll on adopting
> draft-singh-bess-bgp-vpls-control-flags-01 [1] as a working group item.
>
> Please send comments to the list and state if you support adoption or
> not (in
As a co-author, I am not aware of IPRs related to the draft.
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux
> Sent: Friday, September 18, 2015 12:14 PM
> To: BESS
> Subject: [bess] WG Last Call for Ingress Replication Tunnels in Multicast
>
I had some comments on this draft,
https://mailarchive.ietf.org/arch/search/?email_list=bess
that may be worth to think about.
Lucy
-Original Message-
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux
Sent: Friday, September 18, 2015 11:14 AM
To: BESS
Subject: [bess
Hi Lucy,
EVPN-ETREE allows a MEF compliant implementation, I think there is no doubt
about it.
The normal use-case would be a leaf/root site per PE or per AC. But simply
because it is possible in EVPN, I believe it is good to leave the door open to
new applications, and the leaf/root site per M
