[bess] Alissa Cooper's No Objection on draft-ietf-bess-evpn-df-election-framework-07: (with COMMENT)
Alissa Cooper <alissa@cooperw.in> Wed, 09 January 2019 16:21 UTC
Return-Path: <alissa@cooperw.in>
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 A6512130EEC; Wed, 9 Jan 2019 08:21:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
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: <154705089967.4856.11000730122396705744.idtracker@ietfa.amsl.com>
Date: Wed, 09 Jan 2019 08:21:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/ilZC3mFz6lGxrGZLVcs-r36KJ-I>
Subject: [bess] Alissa Cooper'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: Wed, 09 Jan 2019 16:21:40 -0000
Alissa Cooper 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: ---------------------------------------------------------------------- I know there has already been a bunch of discussion about whether this document should formally update RFC 7432. I wanted to ask specifically about Section 3.1. I may be completely misunderstanding this since I did not give RFC 7432 a thorough read, but it appears as though Section 3.1 specifically articulates details applicable to RFC 7432 (independent of what this draft specifies in 3.2 and later sections) that were not included in that RFC. That seems like it warrants the "Updates" relationship, because then people reading RFC 7432 in the future will know to look at this document for updates, and can at least find the FSM and its description there. There is not consensus about what "Updates" means (as evidenced by recent discussion instigated by the IESG [1]) and I don't think this is worth dying on a hill over, just wanted to raise that specifically in case people hadn't considered it. The introduction of this document is unusually long (more than a third of the substantive content of the document). You might consider having 1.1 start a new section rather than having 1.1, 1.2, and 1.3 be subsections of the introduction. [1] https://mailarchive.ietf.org/arch/msg/ietf/-1u_1-peHKAmUDuLyGAJYu0fPCE
- [bess] Alissa Cooper's No Objection on draft-ietf… Alissa Cooper
- Re: [bess] Alissa Cooper's No Objection on draft-… Rabadan, Jorge (Nokia - US/Mountain View)