[Curdle] should we meet at next IETF?
"Salz, Rich" <rsalz@akamai.com> Wed, 19 April 2017 13:12 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 74D00129431 for <curdle@ietfa.amsl.com>; Wed, 19 Apr 2017 06:12:23 -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, HTML_MESSAGE=0.001, 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=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 bHfTzWrwG-IR for <curdle@ietfa.amsl.com>; Wed, 19 Apr 2017 06:12:22 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 E6C25124BFA for <curdle@ietf.org>; Wed, 19 Apr 2017 06:12:21 -0700 (PDT)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.21/8.16.0.21) with SMTP id v3JD05sC003087 for <curdle@ietf.org>; Wed, 19 Apr 2017 14:12:19 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : content-type : mime-version; s=jan2016.eng; bh=Oi7UaoqHo/owmeGLbK9pw0yW5Rm15LI3OnIL/ma8bMc=; b=XWGya+fJEi1R3bjLkwbQYNPGZ83JSjyfvLCHfYtSlqp9y1bz20Egfz7uGbDlg9d7zFVh 3xgdglXLUaKUeguCwOxFLA6raHCs58zur6MUezA+nU4JS+BIFfsyp3lOU/9fgSkmvBmu MtFRllNc/tW7+MiR/5SBLzSLhkjiSt0+xvGK2xnBL6i6LkF37EWf2kg3s5bSfecwUVA5 4DAzo5mfYCnXpEMnzZiCFHlDeKfGmdXvdUP2+8f/ZSp2DtSbspsSoi8FyYmAiwcwxJYd ojk3J8ROnwgEmBFiDcAtBwSuAG6nEPsx25LkakSgl01afHzh59TsRHDOhAsTKrSHCn9f hg==
Received: from prod-mail-ppoint2 (a184-51-33-19.deploy.static.akamaitechnologies.com [184.51.33.19] (may be forged)) by m0050096.ppops.net-00190b01. with ESMTP id 29wxsa2pja-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <curdle@ietf.org>; Wed, 19 Apr 2017 14:12:18 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.17/8.16.0.17) with SMTP id v3JDBKGA023408 for <curdle@ietf.org>; Wed, 19 Apr 2017 09:12:18 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint2.akamai.com with ESMTP id 29wqn5gdpd-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <curdle@ietf.org>; Wed, 19 Apr 2017 09:12:18 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 19 Apr 2017 06:12:17 -0700
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.1263.5; Wed, 19 Apr 2017 09:12:17 -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.1263.000; Wed, 19 Apr 2017 09:12:17 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "curdle@ietf.org" <curdle@ietf.org>
Thread-Topic: should we meet at next IETF?
Thread-Index: AdK5DmFhyaKtZZBaSUCdX5RUsO48vA==
Date: Wed, 19 Apr 2017 13:12:16 +0000
Message-ID: <6e92834ad9e647149bbc75ae673d9788@usma1ex-dag1mb1.msg.corp.akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.33.42]
Content-Type: multipart/alternative; boundary="_000_6e92834ad9e647149bbc75ae673d9788usma1exdag1mb1msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-19_11:, , 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-1703280000 definitions=main-1704190116
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-19_11:, , 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-1703280000 definitions=main-1704190115
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/AeD9Xczw70-5asW2GNI6k8RwpMI>
Subject: [Curdle] should we meet at next IETF?
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: Wed, 19 Apr 2017 13:12:23 -0000
Daniel and I are thinking that we don't need to meet at the next IETF (in Prague). Anyone with relatively strong feelings in favor of meeting? -- Senior Architect, Akamai Technologies Member, OpenSSL Dev Team IM: richsalz@jabber.at Twitter: RichSalz
- [Curdle] should we meet at next IETF? Salz, Rich