[babel] Alissa Cooper's Discuss on draft-ietf-babel-rfc6126bis-12: (with DISCUSS and COMMENT)
Alissa Cooper via Datatracker <noreply@ietf.org> Thu, 08 August 2019 13:06 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 80E01120075; Thu, 8 Aug 2019 06:06:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-babel-rfc6126bis@ietf.org, Donald Eastlake <d3e3e3@gmail.com>, babel-chairs@ietf.org, d3e3e3@gmail.com, babel@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <156526956251.7467.592630566164228470.idtracker@ietfa.amsl.com>
Date: Thu, 08 Aug 2019 06:06:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/whONQ0F_D5JDjQF2e1XodV8yh1c>
Subject: [babel] Alissa Cooper's Discuss on draft-ietf-babel-rfc6126bis-12: (with DISCUSS and COMMENT)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2019 13:06:03 -0000
Alissa Cooper has entered the following ballot position for draft-ietf-babel-rfc6126bis-12: 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 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-babel-rfc6126bis/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- I support Roman's DISCUSS. I'm also unclear on the over-arching recommendation this document is making for securely deploying this protocol. Given that the protocol itself is insecure, I would have expected some normative requirement for correcting that (e.g., Minimally, Babel deployments MUST be secured using a lower-layer security mechanism, Babel over DTLS, or HMAC-based authentication.) This still would not bring it into line with BCP 61 Section 7, but perhaps there is some argument for making an exception for this protocol. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I support Suresh's DISCUSS. An explanation of why this document obsoletes RFC 6126 and RFC 7557 needs to appear in the introduction of this document. Section 3.2.3: It's a bit odd that the Multicast Hello is introduced here but the difference between the two kinds of hellos is not explained until Section 3.4.1. It makes me wonder if 3.2 should come after 3.4. Section 3.6: s/is not left-distributive Section 3.5.2/is not left-distributive (Section 3.5.2)/ Appendix C: This section should be in the body of the document.
- [babel] Alissa Cooper's Discuss on draft-ietf-bab… Alissa Cooper via Datatracker
- Re: [babel] Alissa Cooper's Discuss on draft-ietf… Juliusz Chroboczek