[Curdle] Roman Danyliw's Yes on draft-ietf-curdle-rc4-die-die-die-16: (with COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Thu, 12 September 2019 18:15 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 268691201E0; Thu, 12 Sep 2019 11:15:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw 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
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <156831213210.16522.8242066996251939437.idtracker@ietfa.amsl.com>
Date: Thu, 12 Sep 2019 11:15:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/0vdvGOBHW6BkLNV9He0gmbryyRQ>
Subject: [Curdle] Roman Danyliw's Yes on draft-ietf-curdle-rc4-die-die-die-16: (with 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: Thu, 12 Sep 2019 18:15:32 -0000
Roman Danyliw has entered the following ballot position for draft-ietf-curdle-rc4-die-die-die-16: Yes 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/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- (1) Section 1. Per '[RFC4345] specifies and allocates the "arcfour-128" and "arcfour-256" ciphers for SSH', RFC4345 seems to call these allocations “arcfour128” and “arcfour256” (no hyphen). (2) Editorial -- Abstract. Editorial. s/Therefore, this document formally moves to Historic RFC4345/Therefore, this document formally moves to RFC4345 to Historic status/ -- Section 1. s/Historic/Historic status/ -- Section 2. s/The current document updates the status/This document updates the status/ -- Section 2. s/The current document updates [RFC4253] Section 6.3/This document updates [RFC4254 Section 6.3/ -- Section 2. Typo. s/weakenesses/weaknesses/
- [Curdle] Roman Danyliw's Yes on draft-ietf-curdle… Roman Danyliw via Datatracker