[bess] Benoit Claise's Discuss on draft-ietf-l3vpn-acceptown-community-09: (with DISCUSS)

2015-02-04 Thread Benoit Claise
Benoit Claise has entered the following ballot position for draft-ietf-l3vpn-acceptown-community-09: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please

[bess] Pete Resnick's No Objection on draft-ietf-l3vpn-acceptown-community-09: (with COMMENT)

2015-02-04 Thread Pete Resnick
Pete Resnick has entered the following ballot position for draft-ietf-l3vpn-acceptown-community-09: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please

Re: [bess] EVPN Draft Comments

2015-02-04 Thread John E Drake
Russ Comments inline. I think my original comment describes the state of play: Just because you don't like/understand it doesn't necessarily mean it's wrong.. Yours Irrespectively, John -Original Message- From: Russ White [mailto:ru...@riw.us] Sent: Wednesday, February 04,

Re: [bess] EVPN Draft Comments

2015-02-04 Thread Russ White
Comments inline. I think my original comment describes the state of play: Just because you don't like/understand it doesn't necessarily mean it's wrong.. John -- Irrespectively, as you like to say -- again, calling me stupid isn't helping anything here. The approach of A/B/C

[bess] Last Call: draft-ietf-bess-orf-covering-prefixes-03.txt (Covering Prefixes Outbound Route Filter for BGP-4) to Proposed Standard

2015-02-04 Thread The IESG
The IESG has received a request from the BGP Enabled Services WG (bess) to consider the following document: - 'Covering Prefixes Outbound Route Filter for BGP-4' draft-ietf-bess-orf-covering-prefixes-03.txt as Proposed Standard The IESG plans to make a decision in the next few weeks, and

Re: [bess] EVPN Draft Comments

2015-02-04 Thread Russ White
The approach of A/B/C independently generating route to X only based on local MAC learning works even if physical link failure detection is not an option. And in most practical cases, X will have enough active flows that it will cause local learning on A/B/C to hopefully happen well before