Support
Jim Uttaro
From: BESS On Behalf Of Jeff Tantsura
Sent: Thursday, June 06, 2019 1:54 AM
To: stephane.litkow...@orange.com
Cc: aldrin.i...@gmail.com; bess-cha...@ietf.org; bess@ietf.org
Subject: Re: [bess] WG adoption poll and IPR poll for
draft-boutros-bess-evpn-geneve
Stephane,
I supp
Hi Adrian,
I'm not comfortable with the time-out of controlplane informations.
How do you handle a situation where there is an unknown SFIR-RD in a hop TLV
for a valid reason (the SF is down for a while !), so you are timing out the
SFPR, and eventually the SF is restored and comes back online ?
I'm not aware of any IPR
Yours Irrespectively,
John
Juniper Internal
From: BESS On Behalf Of stephane.litkow...@orange.com
Sent: Wednesday, May 22, 2019 9:55 AM
To: bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: [bess] WG adoption poll and IPR poll for draft-boutros-bess-evpn-geneve
Hi,
T
Hi,
We can't time-out an attribute, we would have to time-out the SFPR w/ which it
is associated. However, I don't think we should do that.
Rather, I think what we should do is indicate that at any point in time an SFF
selects its next hop from the intersection of the set of next hop RDs
conta
Hi,
I like this proposal.
I don't think we need to put a strong requirement on the originator to withdraw
the route. This could be seen as optional OR we could say that each BGP speaker
should validate the path of the SFPR, if the path is invalid, it becomes
unusable (like an unreachable nextho
Hello authors –
The FXC draft expired last October and needs refreshing.
Thanks,
Himanshu
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the BGP Enabled ServiceS WG of the IETF.
Title : EVPN VPWS Flexible Cross-Connect Service
Authors : A. Sajassi
P. Brissette
Done.
Cheers,
Ali
From: "Shah, Himanshu"
Date: Thursday, June 6, 2019 at 8:30 AM
To: "draft-ietf-bess-evpn-vpws-...@ietf.org"
, "bess@ietf.org"
Subject: FXC draft refresh
Resent-From:
Resent-To: Cisco Employee , ,
, , ,
,
Resent-Date: Thursday, June 6, 2019 at 8:30 AM
Hello authors –
Th
