[bess] Mirja Kühlewind's No Objection on draft-ietf-bess-evpn-df-election-framework-07: (with COMMENT)
Mirja Kühlewind <ietf@kuehlewind.net> Thu, 10 January 2019 11:16 UTC
Return-Path: <ietf@kuehlewind.net>
X-Original-To: bess@ietf.org
Delivered-To: bess@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D90A4130DC4; Thu, 10 Jan 2019 03:16:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kühlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-bess-evpn-df-election-framework@ietf.org, Stephane Litkowski <stephane.litkowski@orange.com>, bess-chairs@ietf.org, stephane.litkowski@orange.com, bess@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154711897687.30744.6994568426872803131.idtracker@ietfa.amsl.com>
Date: Thu, 10 Jan 2019 03:16:16 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/WjdPWCU5thu486MUUyFS5CLB96g>
Subject: [bess] Mirja Kühlewind's No Objection on draft-ietf-bess-evpn-df-election-framework-07: (with COMMENT)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jan 2019 11:16:17 -0000
Mirja Kühlewind has entered the following ballot position for draft-ietf-bess-evpn-df-election-framework-07: 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 to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- First one minor editorial comment: Sec 3.2 "Otherwise if even a single advertisement for the type-4 route is not received with the locally configured DF Alg and capability, the Default DF Election algorithm (modulus) algorithm MUST be used as in [RFC7432]." I believe you meant a single advertisement is received without the configured DF Alg and capability (or a different one I guess), and not that the advertisement is not received at all (because that might be hard to check), right? Maybe you can rephrase this sentence a bit to make the intention more clear! However, think about this further, I wondering if there is something here that such be discussed in the security considerations, e.g. how easy would it be for an attacker to disturb the algo selection and cause a fallback to the default scheme...?
- [bess] Mirja Kühlewind's No Objection on draft-ie… Mirja Kühlewind
- Re: [bess] Mirja Kühlewind's No Objection on draf… Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] Mirja Kühlewind's No Objection on draf… Mirja Kuehlewind (IETF)
- Re: [bess] Mirja Kühlewind's No Objection on draf… Luc Andre Burdet (lburdet)
- Re: [bess] Mirja Kühlewind's No Objection on draf… Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] Mirja Kühlewind's No Objection on draf… Mirja Kuehlewind (IETF)