IETF Logo Mail Archive

Re: [Curdle] Kathleen Moriarty's Yes on draft-ietf-curdle-ssh-dh-group-exchange-05: (with COMMENT)

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Fri, 15 September 2017 16:18 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE19013352D; Fri, 15 Sep 2017 09:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FHf6rVC1RqwB; Fri, 15 Sep 2017 09:18:07 -0700 (PDT)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 441561335D1; Fri, 15 Sep 2017 09:18:07 -0700 (PDT)
Received: by mail-qt0-x235.google.com with SMTP id o52so2599442qtc.9; Fri, 15 Sep 2017 09:18:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=XXixmafDrkXhK7Ea2pLYy/hprGZ0BETvDg0rA9oovDU=; b=BeNJiAxsDzZnA4K55i4+qkmzrzXCsjiMDTkTEJ5+4Oh2sx3a0lsPWCvzMmZ4j3Iz+W KHByTA5mED/EA/uqKiGtR+ufxQCdHDmEYdv6W9sdBZRnnGMUBj31AIIOwReOBG0F9OYS JIz3c3CtrM2gJSxV1wK2yL2RSsffYVuKnr0fOv/SmiGXbtDlq4zzzW5+RXHi0/h6+RBe hrNxHrC02QzO1+UR1u2XoaWEwdJJtWKMcjmEXtsy6BUktjK4vOcsJrpdRiqfqXW5HQUA T+RkienZDAKwssRTbjQbVaBln1QyYpxJ8WMOpsI+V14VoSNAjTPq8AnZv1loYmdsUeEj naqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=XXixmafDrkXhK7Ea2pLYy/hprGZ0BETvDg0rA9oovDU=; b=V7oeoLXSJwqUaCCZBg8mzwTWW+cTc6hbgwwzFG9LMqtNVJfRMxxj7wdH8rv0tJLCFv M7b/Jei1fBP/DxR5q1BdOcHgBw6Avo8ldM7m/pVjCEI2FlDZbjSKtlB3CYa6qUoR+z74 rPQe1IJIblySfEh+I5AFtJWFcGWQiueqrIq2UkUJOZxFhwu2cUSWQ5GLe1rwBLaVx7c9 26ITQyzhe1m7zqSvL8I5RggA+ayJu9NoJs6+pdkaSaMPqzpmPR/nYQ0qTVtb20AKO9vv 8QdVyMJcq/l77a3HWl+F3vlYpIjFyPr/OmWCbJOE5NVpWkFjChg6JcxjMiNHwI5j3XEf mLyA==
X-Gm-Message-State: AHPjjUizK3rc9QvdTxBdRvQlNX0Z1HNipMsqJXhcRxwhI/5+E5i/Yb2R t2sDr9AeEplfpzejRkc=
X-Google-Smtp-Source: AOwi7QB7MhoAXu9GddRlYq7bwmRu65xsd5ssfvhWo6PTIN4lry0KxhGPF2CqUVgurPXywVw/Lguhgg==
X-Received: by 10.200.44.167 with SMTP id 36mr26741634qtw.285.1505492286044; Fri, 15 Sep 2017 09:18:06 -0700 (PDT)
Received: from ?IPv6:2600:380:5867:66a8:5a:3949:a2b9:b7cd? ([2600:380:5867:66a8:5a:3949:a2b9:b7cd]) by smtp.gmail.com with ESMTPSA id m93sm751255qte.72.2017.09.15.09.18.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Sep 2017 09:18:05 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Mailer: iPhone Mail (14F89)
In-Reply-To: <E44A4C52-F926-47FB-B6EA-788F0441A1B7@akamai.com>
Date: Fri, 15 Sep 2017 12:18:04 -0400
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Loganaden Velvindron <logan@hackers.mu>, draft-ietf-curdle-ssh-dh-group-exchange <draft-ietf-curdle-ssh-dh-group-exchange@ietf.org>, curdle <curdle@ietf.org>, curdle <curdle-chairs@ietf.org>, The IESG <iesg@ietf.org>, Daniel Migault <daniel.migault@ericsson.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0BF79C2-D43D-429A-9089-0DD46CF74FBF@gmail.com>
References: <150532612778.30489.12003202456500621755.idtracker@ietfa.amsl.com> <CAFDEUTdXRo4MG2=RR+gB0yYpnr1o229qpp+aOaMaDPc6qmnogg@mail.gmail.com> <CAKKJt-etZb1nnXuhxsDZVu2oRUaqUxyD3-xG_0gVVOaQZdZqbQ@mail.gmail.com> <7EAB674F-C7F9-41B1-B362-721F47B86914@gmail.com> <E44A4C52-F926-47FB-B6EA-788F0441A1B7@akamai.com>
To: "Salz, Rich" <rsalz@akamai.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/sotSxeTw8biy3Vy04ZAhox2xHSc>
Subject: Re: [Curdle] Kathleen Moriarty's Yes on draft-ietf-curdle-ssh-dh-group-exchange-05: (with COMMENT)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: Fri, 15 Sep 2017 16:18:08 -0000


Sent from my iPhone

> On Sep 15, 2017, at 11:15 AM, Salz, Rich <rsalz@akamai.com> wrote:
> 
> ➢ Hmm, I'd like to push on this a bit more.  First, do you still feel it's sufficient? 
> 
> The WG was comfortable with a SHOULD for now.  MUST was further than most people wanted to go.
> 
> ➢ Next, what's the explicit compatibility concern?  If your just waiting on a key rollover or something along those lines, it's fine for this RFC to draw a hard line.
> 
> I believe the concern is about upgrading the deployed base.

Ok, so why can't that just be done the next time the deployed base is ready?  Is there a reason why the deployed base needs to be compliant with this RFC?  Or will making 2048 a MUST help to drive the change?

Thank you,
Kathleen 
> 
>

v2.23.0 | Report a Bug | By Email