[Curdle] Warren Kumari's Discuss on draft-ietf-curdle-rc4-die-die-die-16: (with DISCUSS and COMMENT)
Warren Kumari via Datatracker <noreply@ietf.org> Sun, 15 September 2019 19:10 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: curdle@ietf.org
Delivered-To: curdle@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ECD4A12020A; Sun, 15 Sep 2019 12:10:11 -0700 (PDT)
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-curdle-rc4-die-die-die@ietf.org, Daniel Migault <daniel.migault@ericsson.com>, curdle-chairs@ietf.org, daniel.migault@ericsson.com, curdle@ietf.org, fredbaker.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Warren Kumari <warren@kumari.net>
Message-ID: <156857461188.20743.17202052894273131847.idtracker@ietfa.amsl.com>
Date: Sun, 15 Sep 2019 12:10:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/nbBbe2QYmIf4MJK58aH1OMa6mvM>
Subject: [Curdle] Warren Kumari's Discuss on draft-ietf-curdle-rc4-die-die-die-16: (with DISCUSS and COMMENT)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Sep 2019 19:10:12 -0000
Warren Kumari has entered the following ballot position for draft-ietf-curdle-rc4-die-die-die-16: 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-curdle-rc4-die-die-die/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Be ye not alarmed -- this should be super-trivial to address, either by telling my why I'm wrong, or fixing it -- in either case, I'll change to a YES. I'm also fine with this being addressed in AUTH48, etc (if I'm not on the telechat, no need to for Revised ID Needed on my behalf) The IANA considerations section says: ----- The IANA is requested to update the Encryption Algorithm Name Registry of the Secure Shell (SSH) Protocol Parameters [IANA]. The Registration procedure is IETF Review which is achieved by this document. The registry should be updated as follows: +------------------------------+------------+------+ | Encryption Algorithm Name | Reference | Note | +------------------------------+------------+------+ | arcfour | arcfour128 | arcfour256 +------------------------------+------------+------+ Where TBD is the RFC number assigned to the document. --- I think it would be vastly preferable to include a Note saying something along the lines of: "DEPRECATED" (or "HISTORIC" like for des-cbc). Someone implementing SSH / updating their implementation may look at the IANA page and not read all of the links. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you very much for writing this -- it's important, well written, etc. Also thanks to Fred for the OpsDir review.
- [Curdle] Warren Kumari's Discuss on draft-ietf-cu… Warren Kumari via Datatracker