[bess] RtgDir review: draft-ietf-bess-evpn-usage-08.txt

2018-02-19 Thread 7riw77
Hello, I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide

[bess] Opsdir last call review of draft-ietf-bess-dci-evpn-overlay-08

2018-02-19 Thread Victor Kuarsingh
Reviewer: Victor Kuarsingh Review result: Ready Dear Authors, I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the

Re: [bess] Mirja Kühlewind's No Objection on draft-ietf-bess-evpn-usage-08: (with COMMENT)

2018-02-19 Thread Mirja Kuehlewind (IETF)
Ah, thanks. That’s much more clear to me! > Am 19.02.2018 um 20:47 schrieb Rabadan, Jorge (Nokia - US/Mountain View) > : > > Hi Mirja, > > It should be "must be enable". However you are right that the sentence may be > worded a bit better. > We can change it as

Re: [bess] Mirja Kühlewind's No Objection on draft-ietf-bess-evpn-usage-08: (with COMMENT)

2018-02-19 Thread Rabadan, Jorge (Nokia - US/Mountain View)
Hi Mirja, It should be "must be enable". However you are right that the sentence may be worded a bit better. We can change it as follows: It is worth noting that unknown unicast flooding must not be suppressed, unless (at least) one of the following two statements are given: a) control

Re: [bess] Call for adoption: draft-skr-bess-evpn-pim-proxy

2018-02-19 Thread Ali Sajassi (sajassi)
Hi Stephane, Matthew: Is there a process for WG call (or WG LC) call that you are following? I thought it is based on maturity of the draft, adoptions of the draft, history of the draft (how long it has been around), and a public request for it. I am a co-author of the above draft and

[bess] Mirja Kühlewind's No Objection on draft-ietf-bess-evpn-usage-08: (with COMMENT)

2018-02-19 Thread Mirja Kühlewind
Mirja Kühlewind has entered the following ballot position for draft-ietf-bess-evpn-usage-08: 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 refer

[bess] Mirja Kühlewind's No Objection on draft-ietf-bess-dci-evpn-overlay-08: (with COMMENT)

2018-02-19 Thread Mirja Kühlewind
Mirja Kühlewind has entered the following ballot position for draft-ietf-bess-dci-evpn-overlay-08: 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

[bess] The BESS WG has placed draft-skr-bess-evpn-pim-proxy in state "Call For Adoption By WG Issued"

2018-02-19 Thread IETF Secretariat
The BESS WG has placed draft-skr-bess-evpn-pim-proxy in state Call For Adoption By WG Issued (entered by Stephane Litkowski) The document is available at https://datatracker.ietf.org/doc/draft-skr-bess-evpn-pim-proxy/ ___ BESS mailing list

[bess] Call for adoption: draft-skr-bess-evpn-pim-proxy

2018-02-19 Thread stephane.litkowski
Hello working group, This email starts a two-week call for adoption on draft-skr-bess-evpn-pim-proxy-01 [1] as a BESS Working Group Document. Please state on the list if you support the adoption or not (in both cases, please also state the reasons). This poll runs until *the 5th of