All,
the agenda for the BESS WG session is available here:
https://www.ietf.org/proceedings/95/agenda/agenda-95-bess
Speakers, please send your slides no later than Sunday the 3rd of April,
midnight (local time).
Thanks
m&t
___
BESS mailing list
B
Hi Eric,
Thanks for your reply. Very much appreciated.
Sorry for the delay in responding, but I wanted more time to think about it.
I'm fine with all your point, except one. Please see inline [Bruno].
> From: Eric C Rosen [mailto:ero...@juniper.net]
> Sent: Friday, January 15, 2016 7:01 PM
>
Dear BESS WG chairs -
The authors of the draft-shah-bess-l2vpn-yang-01.txt request the adoption of
this draft
as working group document.
We have been holding design team meeting every week since months and have had
very active
participation and contribution from a lot of members (evident from t
On 3/24/2016 11:17 AM, bruno.decra...@orange.com wrote:
I don't see why the IETF would want to create a bis which is not compatible
with the original RFC,
It's typical in a bis draft to remove features that haven't been used.
especially since this incompatibility may be very disruptive in ex
Sami and co-authors,
I have some comments & questions on this draft.
I noticed that the following terms are used in a mixed way and that adds
confusion. Perhaps it could be straightened out?
Service node, service edge node, service edge gateway, access node
Also in Figure 1, "AN" and "SE" ar
