IETF Logo Mail Archive

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

"Salz, Rich" <rsalz@akamai.com> Fri, 15 September 2017 15:16 UTC

Return-Path: <rsalz@akamai.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 A2265133011; Fri, 15 Sep 2017 08:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level:
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 txr6btqcFobI; Fri, 15 Sep 2017 08:16:10 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [67.231.157.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78559132153; Fri, 15 Sep 2017 08:16:10 -0700 (PDT)
Received: from pps.filterd (m0122330.ppops.net [127.0.0.1]) by m0122330.ppops.net-00190b01. (8.16.0.21/8.16.0.21) with SMTP id v8FF91O8008611; Fri, 15 Sep 2017 16:16:05 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=MdMeCmFdz1oTffrVrDNbzSACOisK6QN2Ev0DicN43M4=; b=Zu7eY1nNrlA3AWGpgFG0htYClRsLJpdaVdoGJfzDabe6M2iAt6HVupSmVpav5OdY/aDV Cm2TWkkg/hhx8zO8zCiJUmq403rlZQrN+WmKpyLmkGAghJQTPNsLamXjJlHQ5AhrjJe2 ExFKq2dCUsF7MxRmwCpbqltugCSNdfXJqQ8ZUg4oh0D7D/AVO2uBnsTGNiN6p8ZHi9RD GlfK/RUIrU0IMA80VWToDscrj36AYIbltiIf5V1s/IGoByZfWAfuJpmZYuNQQ8/iuzxT UHKOQF3jBz9E0Bix62I2kOc6X7T8bohZQZbQyKXybLWSSb9Zi4Xnw5cDP3Jj4IsjwiSX BA==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18]) by mx0b-00190b01.pphosted.com with ESMTP id 2d0gv0g96w-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 15 Sep 2017 16:16:04 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.21/8.16.0.21) with SMTP id v8FF5xbR031173; Fri, 15 Sep 2017 11:16:01 -0400
Received: from email.msg.corp.akamai.com ([172.27.25.32]) by prod-mail-ppoint1.akamai.com with ESMTP id 2cwwqkyu9k-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 15 Sep 2017 11:16:01 -0400
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.27.101) by ustx2ex-dag1mb2.msg.corp.akamai.com (172.27.27.102) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 15 Sep 2017 10:16:00 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.6.131]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.6.131]) with mapi id 15.00.1263.000; Fri, 15 Sep 2017 10:16:00 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
CC: 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>
Thread-Topic: Kathleen Moriarty's Yes on draft-ietf-curdle-ssh-dh-group-exchange-05: (with COMMENT)
Thread-Index: AQHTLLtaStH0N4x45ECDj/E/tj4A4aK2Hl4AgAAzGYCAABLUAP//vhOA
Date: Fri, 15 Sep 2017 15:15:59 +0000
Message-ID: <E44A4C52-F926-47FB-B6EA-788F0441A1B7@akamai.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>
In-Reply-To: <7EAB674F-C7F9-41B1-B362-721F47B86914@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1b.0.161010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.34.200]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B274E9640DAB7C41BA4CDE3459DB96CF@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-09-15_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1709150220
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-09-15_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1709150220
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/Rgd2lT2s09vriuaTNPq7n6cg_Wo>
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 15:16:12 -0000

➢ 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.

v2.23.0 | Report a Bug | By Email