Hi Thomas,
Referencing the section 8 of idr-tunnel-encap draft is too wide a scope
IMHO and maybe confusing, thus I'd like to narrow it down. I went over the
both sections 3.5 and 8 of the idr-tunnel-encap draft and with respect to
your comment, I’d like to narrow it to only section 8.2.2.2. ("Wh
Hi Jeffrey,
A few points:
1) There have been lots of discussions on this topic but you were not in
attendance for some of them including the ones held at the last IETF in
Bones Aires. So, before jumping into a haste conclusion that there were
not consensus on section 10, please check with your
Dear Andrew Dolganow, Jayant Kotalwar, Eric C. Rosen, Zhaohui (Jeffrey) Zhang:
An IPR disclosure that pertains to your Internet-Draft entitled "Explicit
Tracking with Wild Card Routes in Multicast VPN"
(draft-dolganow-bess-mvpn-expl-track) was submitted to the IETF Secretariat on
and has been po
Thomas,
I completely agree. This is an excellent way to provide linkage with the
tunnel encaps draft.
Yours Irrespectively,
John
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin
> Sent: Monday, June 13, 2016 11:49 AM
> To: bess@ietf.org
> Sub
Hi Ali,
The changes in -04 look good.
I would have one suggestion: say explicitly that the "use the label as
the VNI" behavior is the same as what the tunnel encap says.
This could be done by adding something like the following to section
5.1.3 :
Note that the procedure defined here to u
Hello Working Group,
(Please read carefully, this e-mail contains new elements compared to WG
LCs we were doing in a still recent past.)
This email starts a Working Group Last Call on
draft-ietf-bess-evpn-overlay [1].
* Please read the document if you haven't read the most recent
version yet,
