IETF Logo Mail Archive

Re: [Lake] Lake charter call for comments

"Salz, Rich" <rsalz@akamai.com> Tue, 10 September 2019 13:28 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: lake@ietfa.amsl.com
Delivered-To: lake@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33BBB12011D for <lake@ietfa.amsl.com>; Tue, 10 Sep 2019 06:28:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 kEHOWO-bhEYf for <lake@ietfa.amsl.com>; Tue, 10 Sep 2019 06:28:32 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 AA31A12011C for <lake@ietf.org>; Tue, 10 Sep 2019 06:28:32 -0700 (PDT)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id x8ADQwdJ009586; Tue, 10 Sep 2019 14:28:28 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=TP433Ogwy2xc2eET1AMWMUVgaHkr/ColhlB3e5Y3B2g=; b=NmN0ZjWK+d/4fKP2WjFC78HG55uya98ot7TIMBUpNO3RbzXiVVCLlkWJ6Q2y1DJGCDVf WbGk6mPHLt+96/otGUyRP8cfRB5AXhZ3n3NsqWFnGLyLqbjBjLiBufmKR9faRmvamWUj eX5B8sL72qi+J4Un0V9FWNXX8iIWsH0/RhBPlx0kC/8QTCjnRVEV0VYRGyUbjpQrg7Ox Jowhbc1htbUYaSvuZKM2ofaWA+oggs5Vn1420ihas+JvQgWCzX4xQnp/qXFMNV5fR2sB ulJTAfdG3+Oc07wkNGycNp0FwEGKSDj+XFzAHTwBJG6cagoEFZVcWuiY7tU29/IBsllb Kw==
Received: from prod-mail-ppoint6 (prod-mail-ppoint6.akamai.com [184.51.33.61] (may be forged)) by m0050093.ppops.net-00190b01. with ESMTP id 2uv3tpe0hw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 10 Sep 2019 14:28:28 +0100
Received: from pps.filterd (prod-mail-ppoint6.akamai.com [127.0.0.1]) by prod-mail-ppoint6.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x8ADKC6I024066; Tue, 10 Sep 2019 09:28:27 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint6.akamai.com with ESMTP id 2uv7vvwdc7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 10 Sep 2019 09:28:26 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag3mb4.msg.corp.akamai.com (172.27.123.56) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 10 Sep 2019 09:28:26 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 10 Sep 2019 09:28:25 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1473.005; Tue, 10 Sep 2019 09:28:25 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Göran Selander <goran.selander@ericsson.com>, Benjamin Kaduk <kaduk@mit.edu>, "lake@ietf.org" <lake@ietf.org>
Thread-Topic: [Lake] Lake charter call for comments
Thread-Index: AQHVYt01bGGMFWuPBUOv7ydUJigIracjl5IAgAFnhID///JugA==
Date: Tue, 10 Sep 2019 13:28:25 +0000
Message-ID: <03254E1C-4067-4994-8112-2A86E52D0EA0@akamai.com>
References: <20190904045654.GY58050@kduck.mit.edu> <D1F8429D-710A-4470-A8AC-4FF70AE56F97@akamai.com> <ADC3E3F3-E45C-430F-BC04-A3EEC68E8F43@ericsson.com>
In-Reply-To: <ADC3E3F3-E45C-430F-BC04-A3EEC68E8F43@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1d.0.190908
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.32.125]
Content-Type: text/plain; charset="utf-8"
Content-ID: <316B239276EE49438BD1D7790C5ED9AE@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-10_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909100130
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.70,1.0.8 definitions=2019-09-10_09:2019-09-10,2019-09-10 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 lowpriorityscore=0 clxscore=1011 impostorscore=0 priorityscore=1501 bulkscore=0 phishscore=0 adultscore=0 malwarescore=0 mlxscore=0 mlxlogscore=983 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1909100132
Archived-At: <https://mailarchive.ietf.org/arch/msg/lake/3vXOjAUtkShaIhoAwzdnDAFlAkI>
Subject: Re: [Lake] Lake charter call for comments
X-BeenThere: lake@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Lightweight Authenticated Key Exchange <lake.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lake>, <mailto:lake-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lake/>
List-Post: <mailto:lake@ietf.org>
List-Help: <mailto:lake-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lake>, <mailto:lake-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2019 13:28:34 -0000

Thanks for the answer, it makes sense.

I still think a general statement like "without unnecessarily sacrificing security properties" should be there somewhere.  My intent behind that is that if the WG decides to use ROT13 because some IoT pencils have limited capabilities, this should be explained in the documents.

Does that make sense?

v2.23.0 | Report a Bug | By Email