[babel] Warren Kumari's Discuss on draft-ietf-babel-rtt-extension-05: (with DISCUSS)
Warren Kumari via Datatracker <noreply@ietf.org> Thu, 15 February 2024 01:37 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 AF16EC14F5EE; Wed, 14 Feb 2024 17:37:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Warren Kumari via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-babel-rtt-extension@ietf.org, babel-chairs@ietf.org, babel@ietf.org, Donald Eastlake <d3e3e3@gmail.com>, d3e3e3@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 12.5.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Warren Kumari <warren@kumari.net>
Message-ID: <170796102570.42141.4171938216931566688@ietfa.amsl.com>
Date: Wed, 14 Feb 2024 17:37:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/-yP3I-EhWeNXwtfmgF0NzitoYt4>
Subject: [babel] Warren Kumari's Discuss on draft-ietf-babel-rtt-extension-05: (with DISCUSS)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.39
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, 15 Feb 2024 01:37:05 -0000
Warren Kumari has entered the following ballot position for draft-ietf-babel-rtt-extension-05: 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/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-babel-rtt-extension/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Be strong and of a good courage; be ye not afraid, neither be thou dismayed by this DISCUSS position. Instead, take heart and readeth https://www.ietf.org/blog/handling-iesg-ballot-positions/ , which contains many words on handling ballots. For, as it sayeth upon the lid of the tin: "A DISCUSS ballot is a request to have a discussion"... First off, let me start by saying that I like the general idea and concept in this document, but, like others, I think that it needs more formalism. One major concern of mine is that it says: "Updates: 8967 (if approved)" The shepherds writeup notes that this document is Standards Track because it needs to update a Standards Track document, but no-where in the document does it actually say **how** it updates RFC8967. Perhaps the header intended to say that the documents updates RFC8966? Even if that is the case, the document doesn't actually say **how** it updates it... The Abstract should say "This document updates RFC896X by fooing the bar and twiddling the baz." (or similar)
- [babel] Warren Kumari's Discuss on draft-ietf-bab… Warren Kumari via Datatracker
- Re: [babel] Warren Kumari's Discuss on draft-ietf… Juliusz Chroboczek
- Re: [babel] Warren Kumari's Discuss on draft-ietf… Gunter van de Velde (Nokia)