IETF Logo Mail Archive

Re: [Lurk] [E] Re: IETF-96 LURK raw minutes

"Mishra, Sanjay" <sanjay.mishra@verizon.com> Mon, 25 July 2016 14:32 UTC

Return-Path: <sanjay.mishra@verizon.com>
X-Original-To: lurk@ietfa.amsl.com
Delivered-To: lurk@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9122B12D8E0 for <lurk@ietfa.amsl.com>; Mon, 25 Jul 2016 07:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-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 (1024-bit key) header.d=verizon.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 AsngZ4ID2uVm for <lurk@ietfa.amsl.com>; Mon, 25 Jul 2016 07:32:52 -0700 (PDT)
Received: from omzsmtpe01.verizonbusiness.com (omzsmtpe01.verizonbusiness.com [199.249.25.210]) (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 E597B12D8DD for <lurk@ietf.org>; Mon, 25 Jul 2016 07:32:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1469457172; x=1500993172; h=from:to:date:subject:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=5vnGNziibDMakYbZReesHC5Wxa0SHWKq8bmIwZMh6lw=; b=H01586g9bLsZejMTTfdKHbdz0Mq6TpsjVRqpv2Kb5vovG3YFbK3g3kzR teWS1nmXfe4llMNST6umh9xSQFvWPaj0DbVVlgOLRJPMzH/IkuTe3N6PU XUroKINuL08T64rYGFrvJUvhltky5fuJN//1dLnnkXMocBTvmLsUpUj4x A=;
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi03.verizon.com) ([166.68.71.145]) by omzsmtpe01.verizonbusiness.com with ESMTP; 25 Jul 2016 14:32:50 +0000
From: "Mishra, Sanjay" <sanjay.mishra@verizon.com>
X-IronPort-AV: E=Sophos;i="5.28,419,1464652800"; d="scan'208";a="173652010"
Received: from fhdp1lumxc7hb04.verizon.com (HELO FHDP1LUMXC7HB04.us.one.verizon.com) ([166.68.59.191]) by fldsmtpi03.verizon.com with ESMTP; 25 Jul 2016 14:31:51 +0000
Received: from fhdp1lumxc7v23.us.one.verizon.com ([166.68.59.159]) by FHDP1LUMXC7HB04.us.one.verizon.com ([166.68.59.191]) with mapi; Mon, 25 Jul 2016 10:31:21 -0400
To: Yaron Sheffer <yaronf.ietf@gmail.com>, LURK BoF <lurk@ietf.org>
Date: Mon, 25 Jul 2016 10:31:20 -0400
Thread-Topic: [E] Re: [Lurk] IETF-96 LURK raw minutes
Thread-Index: AdHkH1+KEIh0s2VDTZq8znSZyumNsgCXvIGg
Message-ID: <900A1E2059ADB149B905E3C8FA0046A62CED2A3825@FHDP1LUMXC7V23.us.one.verizon.com>
References: <20160718114902.Horde.6X9p5iABazUAMnOTCBLpDGU@box514.bluehost.com> <ece0f813-377a-4a9a-788e-0dece193c884@gmail.com>
In-Reply-To: <ece0f813-377a-4a9a-788e-0dece193c884@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lurk/i6fTfRFnHj5LUeswgXWRq8NEmhs>
Subject: Re: [Lurk] [E] Re: IETF-96 LURK raw minutes
X-BeenThere: lurk@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Limited Use of Remote Keys <lurk.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lurk>, <mailto:lurk-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lurk/>
List-Post: <mailto:lurk@ietf.org>
List-Help: <mailto:lurk-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lurk>, <mailto:lurk-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2016 14:32:54 -0000

The conversation at the LURK BOF, it appears to me, focused almost entirely on the draft "draft-mglt-lurk-tls",  and potentially limited/reduced any other conversation such as whether the use cases are something the community empathizes with and whether they can be and should be addressed? Also, due diligence at the BOF - perhaps discussion - on the 3rd draft "draft-erb-lurk-rsalg-01" could have been useful to at least debate whether it can stand up to the security (or not) as compared to the other two protocols?

-Sanjay

-----Original Message-----
From: Lurk [mailto:lurk-bounces@ietf.org] On Behalf Of Yaron Sheffer
Sent: Friday, July 22, 2016 9:46 AM
To: jeff.hodges@kingsmountain.com; LURK BoF
Subject: [E] Re: [Lurk] IETF-96 LURK raw minutes

I slightly edited the minutes for language and uploaded them: 
https://www.ietf.org/proceedings/96/minutes/minutes-96-lurk.

Thanks again to the minute takers!

	Yaron

_______________________________________________
Lurk mailing list
Lurk@ietf.org
https://www.ietf.org/mailman/listinfo/lurk

v2.23.0 | Report a Bug | By Email