[Curdle] Mirja Kühlewind's No Objection on draft-ietf-curdle-ssh-ext-info-12: (with COMMENT)
Mirja Kühlewind <ietf@kuehlewind.net> Mon, 04 September 2017 12:18 UTC
Return-Path: <ietf@kuehlewind.net>
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 17A39126DD9; Mon, 4 Sep 2017 05:18:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kühlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-curdle-ssh-ext-info@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.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150452751108.452.17402297157409789400.idtracker@ietfa.amsl.com>
Date: Mon, 04 Sep 2017 05:18:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/B_TitXtGjwmrn3kS5o8Xr-NVNHM>
Subject: [Curdle] Mirja Kühlewind's No Objection on draft-ietf-curdle-ssh-ext-info-12: (with COMMENT)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 04 Sep 2017 12:18:31 -0000
Mirja Kühlewind has entered the following ballot position for draft-ietf-curdle-ssh-ext-info-12: 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-curdle-ssh-ext-info/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- 1) What happens if the server received more than one (different) EXT_INFO messages or the client receives more than two? 2) One question regarding flow control: I understood that some implementation simply set the max value for the initial window, however, if you don't even have a max window how do you ensure that the receiver is not over loaded and what do you do if you receive more data that you can handle? 3) I'm by far not an expert but I would have expected that there are additional security consideration for elevation and mybe even flow control... no? 4) Thanks for quickly addressing the genart review!
- [Curdle] Mirja Kühlewind's No Objection on draft-… Mirja Kühlewind
- Re: [Curdle] Mirja Kühlewind's No Objection on dr… denis bider