
From nobody Thu Feb 15 19:12:07 2018
Return-Path: <yakov@nightwatchcybersecurity.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5A0A126CD6 for <secdispatch@ietfa.amsl.com>; Thu, 15 Feb 2018 19:12:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nightwatchcybersecurity-com.20150623.gappssmtp.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 yrklsDACV5Wo for <secdispatch@ietfa.amsl.com>; Thu, 15 Feb 2018 19:12:04 -0800 (PST)
Received: from mail-ot0-x242.google.com (mail-ot0-x242.google.com [IPv6:2607:f8b0:4003:c0f::242]) (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 19FAD1243F3 for <secdispatch@ietf.org>; Thu, 15 Feb 2018 19:12:01 -0800 (PST)
Received: by mail-ot0-x242.google.com with SMTP id e64so1649120ote.4 for <secdispatch@ietf.org>; Thu, 15 Feb 2018 19:12:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nightwatchcybersecurity-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=AsM+IXIYW28gHSqp2PEjbodUsW2bgLvFtomulhEsB98=; b=FKbEjXR1BCGb7OydsAGVATpRaZepCIOk//D/M5UKQNt1NJuiANirI+O8pJSMElCzuG KhK7WeO6X7CsSQ8ir3SuQI7pnbpEYgpXHDiPlOFqiyAC6NLDrjzICVR2yhWLo6XiKVB9 HfXm7ATK76xFhJmCj9PFYCONataJc1auM7Iroo0Wm/YFSxCr8uQAvHbQBSk2ZdPYOjKG lh49Q7cg65ThpnAFfi49XgCrVDpN7/f//G9xV3TziVos34TUVE3Z5dKL9y7jUArjrqXU LQry0epQr3dWsk8VQ9dZsUrlZ9Yofo8nChLEGJezICOWNkmcvOfUyHAR0y4tEMJOVy1o pg7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=AsM+IXIYW28gHSqp2PEjbodUsW2bgLvFtomulhEsB98=; b=TUr1t55n+yJfJs92ScOj3uVMg1TWPgFEB52z1lDGBCAMb2eA23UWQXTJq/6HG1nWj8 8j153dyO1suZJAvcLZPt9pdq1jPVsd6xA88OalER8XpCsBOET4GI4w/BrYgvcCBYAwUr gJMzO15t+8/22fPWlQJabVI45lMPUEd59Eg3Fzxc1TgWpu4UumRMsRUFey3lRHsElb20 ry5xXjkCJO1LB+UFH7GgTjhQq0KQG6v9FFK/2t/x7Zytihi0SmYpOe2fDxixGWLHv/ZS HvFm67Qs2yoWKChaTuPKoxV1rYXeSvKj9SB8kKAi4vS2/npb3JONI3Ugn+haU+wJVLJO 8TQA==
X-Gm-Message-State: APf1xPC9UhGPFd9PmIJEo0iXPnWmWNJtWS+YVLerquFmP4PB18MnRfqr y1bWtGbMBF5MtBsSA6uIvfc4HTK3hocdRJ0zuW8n+EOfvHY=
X-Google-Smtp-Source: AH8x225Z/t7OGh8t9GqzbHhxdGbRcAPZyUh5Zv9B2NhcsM1QOkCrgq+dkKVS0bvhd3rV6sr8TmhCGHHh8wU+jix2qW0=
X-Received: by 10.157.27.145 with SMTP id z17mr3337192otd.285.1518750720253; Thu, 15 Feb 2018 19:12:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.23.5 with HTTP; Thu, 15 Feb 2018 19:11:19 -0800 (PST)
From: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>
Date: Thu, 15 Feb 2018 22:11:19 -0500
Message-ID: <CAAyEnSMgKPyW3DGBGW3KLi-LVywGr7XVkF2qW-kuQ6_u31Hw6w@mail.gmail.com>
To: secdispatch@ietf.org
Cc: Ed Overflow <contact@edoverflow.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/5A7fgmZUI2256jjdVctAubwODkc>
Subject: [Secdispatch] Request for time at IETF 101 / London - security.txt
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Feb 2018 03:12:06 -0000

Ed Foudil and others within the security community are working on an
Internet draft proposing a new standard for providing security contact
information via a standard file, similar to robots.txt. The most
current draft can be found here:
https://tools.ietf.org/html/draft-foudil-securitytxt-03

Additional resources here:
https://securitytxt.org/
https://github.com/securitytxt/security-txt
https://securitytext.org/ (alpha)

Several Internet sites are already publishing this on their websites:
https://www.google.com/.well-known/security.txt
https://www.dropbox.com/.well-known/security.txt
https://www.tumblr.com/.well-known/security.txt
https://www.facebook.com/.well-known/security.txt
https://www.openssl.org/.well-known/security.txt

Nevil Brownlee (the Independent Submissions Editor) has indicated that
this document is not a good candidate for the independent stream, so
the question now is whether this can be something that fall under the
security area.

I would like to ask for some time at IETF 101 to discuss this draft
during SECDISPATCH.

Thank you in advance


From nobody Tue Feb 20 13:36:32 2018
Return-Path: <housley@vigilsec.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E0D3124E15 for <secdispatch@ietfa.amsl.com>; Tue, 20 Feb 2018 13:36:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 NWXGaLZyFEvy for <secdispatch@ietfa.amsl.com>; Tue, 20 Feb 2018 13:36:29 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0B73120724 for <secdispatch@ietf.org>; Tue, 20 Feb 2018 13:36:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id BE82830066F for <secdispatch@ietf.org>; Tue, 20 Feb 2018 16:36:26 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id c1Ug-fQFOqh5 for <secdispatch@ietf.org>; Tue, 20 Feb 2018 16:36:26 -0500 (EST)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id F175B3004AA for <secdispatch@ietf.org>; Tue, 20 Feb 2018 16:36:25 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <38CEEA61-0190-4EE9-AD73-323630F453A0@vigilsec.com>
Date: Tue, 20 Feb 2018 16:36:27 -0500
To: IETF  SecDispatch <secdispatch@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/slDUqZH0R-kWUDRmVXA5BXmylFM>
Subject: [Secdispatch] I would like to present draft-housley-cms-mts-hash-sig in London
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Feb 2018 21:36:30 -0000

I would like to  present draft-housley-cms-mts-hash-sig during the =
SecDispatch session in London.

https://datatracker.ietf.org/doc/draft-housley-cms-mts-hash-sig/

I understand that presentations are expected to be about 10 minutes.  I =
plan to cover the problem that the draft is trying to solve, the =
proposed solution, and the desired next step.   Then should be plenty of =
time in the 10 minutes for open mic, allowing folks in the room voice =
agreement or offer other suggestions.

Russ


From nobody Tue Feb 20 13:53:46 2018
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6038712DA3D for <secdispatch@ietfa.amsl.com>; Tue, 20 Feb 2018 13:53:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=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 3TfKxWxobVbc for <secdispatch@ietfa.amsl.com>; Tue, 20 Feb 2018 13:53:34 -0800 (PST)
Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::22a]) (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 817321205D3 for <secdispatch@ietf.org>; Tue, 20 Feb 2018 13:53:34 -0800 (PST)
Received: by mail-wr0-x22a.google.com with SMTP id w77so18576294wrc.6 for <secdispatch@ietf.org>; Tue, 20 Feb 2018 13:53:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:mime-version:subject:message-id:date:to; bh=qmNFRdgcLzzt7vCSvyaPbdLbkCHwsfnHhcZb4rgp+1U=; b=ewJq9ZwIDvFOnSyTe50DytKq4SNneDKW/Ql3CCz9DslmfXtpa/EDycvy8A8lZnO+Kd 3qwK5EvwHGugL6J5jZBzBWu3kJTWNF7UQ5T+iTx+UMXsOswO6WfZEjOdBCcpS5q8YdT9 INUXu/e2k0RLWvipbv8RJ6y2coP0m6xB3qtQcA4JirELlQ+dDwKTFoyZmwQ2VdoDttg8 g1OeHqdUa2b8QSD8pPkSAmmA3ocSKFps0wqZEU5iz83eduoWFkfJ2p2t38MmkB/kKvwq F830UMIjFnZawydcPVsMefO4i9l9QEnUVEBp6ftrQVOquMYpQRaoaR26ggPbQeKWWmDC z+9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=qmNFRdgcLzzt7vCSvyaPbdLbkCHwsfnHhcZb4rgp+1U=; b=VfDnKB/D7pxYM+SxCYuvDVWO46TvBKGQrn+dm4OnVzVO9BuyYZHA5ig5pqQnlnf90P 4/xaIJkHSVZTlZE4hGapYR0f+WUKQXL04sSKbvOmBZWgU7zzTCwYJplYKf/U54j+4lNy EUNXGiPQeUkpTHz60ir19DX5W0RQZHEXHf1Sk2TBduN1DxpgLeGZEv79mc6XFwTroMNf sT2N9qFvf7xj5d2M7MMGSJyq74IRiYFSTxm2yfJo4kbpH64dPizdYd6UeCZhWRe/X0c9 T33FugnxXdBYLRYJenGLqPZR6QY2wJU1JzxfaPfmKy05kIQOERdd8Xpl6fRKfH6l87lJ D9NA==
X-Gm-Message-State: APf1xPDPOuSxNMFg5XGqPj17BpH814eRJXCK33pvGbHkigTk/5nT0D1N T7PWJ5RYHr86vDBvwqQfP33iUgeq
X-Google-Smtp-Source: AH8x2251PZ5AjH2aQeaub5K7w6dQhew7GcJm4O9RCfxU4dts6a5RqDH8Wq4a3xG2/gy/sJXt3C3cxg==
X-Received: by 10.223.200.2 with SMTP id d2mr927276wrh.81.1519163612897; Tue, 20 Feb 2018 13:53:32 -0800 (PST)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id e67sm33092642wmd.7.2018.02.20.13.53.32 for <secdispatch@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Feb 2018 13:53:32 -0800 (PST)
From: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C055506A-C705-4226-8DA7-5248A647E050"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Message-Id: <F636AEDE-A063-477C-84D2-E37314EEBBE9@gmail.com>
Date: Tue, 20 Feb 2018 23:53:30 +0200
To: secdispatch@ietf.org
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/LPxhRdgnhy20mZGZerAtHC4rbQw>
Subject: [Secdispatch] Considerations for Short-Term Certificates
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Feb 2018 21:53:36 -0000

--Apple-Mail=_C055506A-C705-4226-8DA7-5248A647E050
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi.

I=E2=80=99d like time to present our STAR draft [1].  In Singapore we =
had a side meeting with some good feedback. We=E2=80=99ll revise this =
document before London and we=E2=80=99ll be seeking a home for it.

Thanks,

Thomas, Yaron, and Yoav

[1] https://tools.ietf.org/html/draft-nir-saag-star-00 =
<https://tools.ietf.org/html/draft-nir-saag-star-00>=

--Apple-Mail=_C055506A-C705-4226-8DA7-5248A647E050
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Hi.<div class=3D""><br class=3D""></div><div class=3D"">I=E2=80=
=99d like time to present our STAR draft [1]. &nbsp;In Singapore we had =
a side meeting with some good feedback. We=E2=80=99ll revise this =
document before London and we=E2=80=99ll be seeking a home for it.<br =
class=3D""><br class=3D"">Thanks,<br class=3D""><br class=3D"">Thomas, =
Yaron, and Yoav<br class=3D""><br class=3D"">[1]&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-nir-saag-star-00" =
class=3D"">https://tools.ietf.org/html/draft-nir-saag-star-00</a></div></b=
ody></html>=

--Apple-Mail=_C055506A-C705-4226-8DA7-5248A647E050--


From nobody Tue Feb 20 14:59:36 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFCC212E03B for <secdispatch@ietfa.amsl.com>; Tue, 20 Feb 2018 14:59:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 ZnE1_vPnDN0U for <secdispatch@ietfa.amsl.com>; Tue, 20 Feb 2018 14:59:32 -0800 (PST)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 A6678126DFF for <secdispatch@ietf.org>; Tue, 20 Feb 2018 14:59:32 -0800 (PST)
Received: by mail-qk0-x232.google.com with SMTP id y137so12564179qka.4 for <secdispatch@ietf.org>; Tue, 20 Feb 2018 14:59:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uuc33BYpKZ0tRkfA5tSOnIXQVCLr7HR3qaqPDbOeydw=; b=DBNao7OJ9HVfCPs9cx7OLrdFOBXwzZwMgSJm7XHSHfsOzcMdovYkcVj7VqbMctBpxp vypB7KynErzT0xQHkx7jv4pA4ckD2/jujcHVh9o5GKhhIhUA16/RjImLXtPyFkGxStpo ee6f2XFEBbhIG0+8ssa4I1+9laU3JUMicQA83TDu3ZCut9wuPdZEGjWVm4qihlnC7EMx eUDIIwCCxKEqiPwQnbRkBxCi4qzKhZQpBg/58TmoXOgvWueUg10geaJgQ46iOj7nrPft bWlCayWR89PRmV9o7Kuma/KW8PEfEN5BzaSRT27r6C0Uk2f5m5OGvDPxM6Ugs7cWB50t ubmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uuc33BYpKZ0tRkfA5tSOnIXQVCLr7HR3qaqPDbOeydw=; b=Wnme2j+Y4I5jlxSbg6sFUfRzvZuVQW8Kl4mTCHWyBX+OpQNfYCT2AAV8D/3M0Uj2FG ilJCsB9vxr+TWfxv3ZTyr+Pw7MF0p/YK2wF7r7s3nnN1KB0JuJWWdHYOK6ymgEEbX5xo HxKOE9oNx1N3+2g6QKggITqLv+170yeO08/5eZSEbevHrsFlJB4N5kkwU0VNreVxsXSi yl5nsX2jAPbcMMCkiYM/RmNma7Vs1SCG0wnE+Oh/Ll5Vpz2gfWXWAF6x7JKT+2zcvGG7 3nUqMuv34Ju/3i7rny9OpBzOXwEZnUYtK7J6h1yaNIEOKTb/WKhBpGWXwNpAE68mGQkC /55Q==
X-Gm-Message-State: APf1xPAgvg5TWUSkYfhwr9ck6E+2515R4ZQwmflH1L582YTKNYdO5fNC DiNgQlE7+xsA7i8Qx989L0j9wZZs7UhiGuPSUA8Esw==
X-Google-Smtp-Source: AH8x2257WNbTpnUWtHIQpe5azdCNc3Tp7vqIBOEN+N6s4OOejmKi+oHTZ6R+TSr8AgYwjmRshCea7l8L6HrFN+U/OUQ=
X-Received: by 10.55.9.135 with SMTP id 129mr1948015qkj.221.1519167571733; Tue, 20 Feb 2018 14:59:31 -0800 (PST)
MIME-Version: 1.0
Received: by 10.200.37.176 with HTTP; Tue, 20 Feb 2018 14:58:51 -0800 (PST)
In-Reply-To: <38CEEA61-0190-4EE9-AD73-323630F453A0@vigilsec.com>
References: <38CEEA61-0190-4EE9-AD73-323630F453A0@vigilsec.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 20 Feb 2018 14:58:51 -0800
Message-ID: <CABcZeBPdR9T8RjTGdE0YCgXwB4hmbs5QZKMkudgbeZJBuqW_6g@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Cc: IETF SecDispatch <secdispatch@ietf.org>
Content-Type: multipart/alternative; boundary="001a11487b8c77cc930565acc362"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/QJ2ZP9wlTATqxAGPgWMj7Sp9ss4>
Subject: Re: [Secdispatch] I would like to present draft-housley-cms-mts-hash-sig in London
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Feb 2018 22:59:35 -0000

--001a11487b8c77cc930565acc362
Content-Type: text/plain; charset="UTF-8"

On Tue, Feb 20, 2018 at 1:36 PM, Russ Housley <housley@vigilsec.com> wrote:

> I would like to  present draft-housley-cms-mts-hash-sig during the
> SecDispatch session in London.
>
> https://datatracker.ietf.org/doc/draft-housley-cms-mts-hash-sig/
>
> I understand that presentations are expected to be about 10 minutes.  I
> plan to cover the problem that the draft is trying to solve, the proposed
> solution, and the desired next step.


I think it would be helpful if you said what that is, as it sounds like you
know.

-Ekr


>  Then should be plenty of time in the 10 minutes for open mic, allowing
> folks in the room voice agreement or offer other suggestions.
>
> Russ
>
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch
>

--001a11487b8c77cc930565acc362
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Feb 20, 2018 at 1:36 PM, Russ Housley <span dir=3D"ltr">&lt;<a =
href=3D"mailto:housley@vigilsec.com" target=3D"_blank">housley@vigilsec.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I would like to=C2=
=A0 present draft-housley-cms-mts-hash-sig during the SecDispatch session i=
n London.<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-housley-cms-mts-hash-sig/=
" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>do=
c/draft-housley-cms-mts-<wbr>hash-sig/</a><br>
<br>
I understand that presentations are expected to be about 10 minutes.=C2=A0 =
I plan to cover the problem that the draft is trying to solve, the proposed=
 solution, and the desired next step.=C2=A0</blockquote><div><br></div><div=
>I think it would be helpful if you said what that is, as it sounds like yo=
u know.</div><div><br></div><div>-Ekr</div><div>=C2=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"> =C2=A0Then should be plenty of time in the 10 minutes for =
open mic, allowing folks in the room voice agreement or offer other suggest=
ions.<br>
<br>
Russ<br>
<br>
______________________________<wbr>_________________<br>
Secdispatch mailing list<br>
<a href=3D"mailto:Secdispatch@ietf.org">Secdispatch@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/secdispatch" rel=3D"norefe=
rrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/secdispa=
tch</a><br>
</blockquote></div><br></div></div>

--001a11487b8c77cc930565acc362--


From nobody Wed Feb 21 06:27:47 2018
Return-Path: <rdd@cert.org>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A92E12D7F3 for <secdispatch@ietfa.amsl.com>; Wed, 21 Feb 2018 06:27:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 WWWIn2qEqRPs for <secdispatch@ietfa.amsl.com>; Wed, 21 Feb 2018 06:27:45 -0800 (PST)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (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 0F37912D7E6 for <secdispatch@ietf.org>; Wed, 21 Feb 2018 06:27:44 -0800 (PST)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id w1LERhbW029006 for <secdispatch@ietf.org>; Wed, 21 Feb 2018 09:27:43 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu w1LERhbW029006
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1519223263; bh=VpeoEG9S1M5IPxlUHWXDjAgMxqESmwb5MIAltWk5I18=; h=From:To:Subject:Date:From; b=afvLC6ROsNnFgdaQr8lRzqTqzAwlQndSpImy3gaKxSu3sCMFJ/ulzp5w93QfEXlkT cOLccZtTSJAfjPMFy7H4lyWNe274JZWroGuIeifvhzR2F/wQFW1sKd13g2MfRNFZPU f5/ta+60MDmzTjvSTMGOIW+PG7bAEvEEgj1CIdNs=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id w1LERfCA026620 for <secdispatch@ietf.org>; Wed, 21 Feb 2018 09:27:41 -0500
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0361.001; Wed, 21 Feb 2018 09:27:41 -0500
From: Roman Danyliw <rdd@cert.org>
To: "secdispatch@ietf.org" <secdispatch@ietf.org>
Thread-Topic: Call for agenda items for SecDispatch at IETF 101
Thread-Index: AdOrFIrvd2svV2J5SKC8b7/txIBTZg==
Date: Wed, 21 Feb 2018 14:27:40 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC013753251B@marathon>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/iK_Iu56ifqBBhI5A5setlHEnK7c>
Subject: [Secdispatch] Call for agenda items for SecDispatch at IETF 101
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2018 14:27:47 -0000

Hello!

SecDispatch has been tentatively scheduled at IETF 101 on Tuesday (March 20=
) at 0930-1200.  If you would like time on the agenda, send your request to=
 the mailing list.  Helpful items to include in your request (if known/appl=
icable) are:

** pointers to a draft(s)/document
** pointers to related background or prior discussion
** desired next steps

If needed, precedence will be given to documents that have demonstrated int=
erest in the form of active drafts and list discussion.

If you have questions, please reach out to the co-chairs.

Regards,
Roman and Richard


From nobody Wed Feb 21 08:16:31 2018
Return-Path: <housley@vigilsec.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DD5912D86F for <secdispatch@ietfa.amsl.com>; Wed, 21 Feb 2018 08:16:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no
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 uBe6acjDwCyU for <secdispatch@ietfa.amsl.com>; Wed, 21 Feb 2018 08:16:27 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84D2A127010 for <secdispatch@ietf.org>; Wed, 21 Feb 2018 08:16:27 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 5FABF300A07 for <secdispatch@ietf.org>; Wed, 21 Feb 2018 11:16:25 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id EHGHOdXcJIAc for <secdispatch@ietf.org>; Wed, 21 Feb 2018 11:16:24 -0500 (EST)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 4091E300441; Wed, 21 Feb 2018 11:16:24 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <B6A4956B-1524-424C-B080-883578B9A097@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_45F6C2E2-1C64-4F7B-9A42-D344170B2BA9"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 21 Feb 2018 11:16:28 -0500
In-Reply-To: <CABcZeBPdR9T8RjTGdE0YCgXwB4hmbs5QZKMkudgbeZJBuqW_6g@mail.gmail.com>
Cc: IETF  SecDispatch <secdispatch@ietf.org>
To: Eric Rescorla <ekr@rtfm.com>
References: <38CEEA61-0190-4EE9-AD73-323630F453A0@vigilsec.com> <CABcZeBPdR9T8RjTGdE0YCgXwB4hmbs5QZKMkudgbeZJBuqW_6g@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/t84WVd0DJPbL-6plp2rYbZop80Y>
Subject: Re: [Secdispatch] I would like to present draft-housley-cms-mts-hash-sig in London
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2018 16:16:29 -0000

--Apple-Mail=_45F6C2E2-1C64-4F7B-9A42-D344170B2BA9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


>=20
> I would like to  present draft-housley-cms-mts-hash-sig during the =
SecDispatch session in London.
>=20
> https://datatracker.ietf.org/doc/draft-housley-cms-mts-hash-sig/ =
<https://datatracker.ietf.org/doc/draft-housley-cms-mts-hash-sig/>
>=20
> I understand that presentations are expected to be about 10 minutes.  =
I plan to cover the problem that the draft is trying to solve, the =
proposed solution, and the desired next step.=20
>=20
> I think it would be helpful if you said what that is, as it sounds =
like you know.

I am pushing hash-based signatures on software and firmware downloads =
for two reasons.  First, we need to deploy a quantum-safe signature long =
before there is large-scale quantum computer, otherwise we will not be =
able to deploy the next generation of cryptographic algorithms without =
physically touching every device.  Second, the signature validation code =
in the bootloader is small and fast.  Verification being small and fast =
makes this attractive in the IoT environment.

The relationship to CMS makes LAMPS a reasonable place to proceed with =
this document.

The relationship to IoT firmware makes SUIT a reasonable place to =
proceed with this document.

Russ=

--Apple-Mail=_45F6C2E2-1C64-4F7B-9A42-D344170B2BA9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class=3D"">I =
would like to&nbsp; present draft-housley-cms-mts-hash-sig during the =
SecDispatch session in London.<br class=3D"">
<br class=3D"">
<a =
href=3D"https://datatracker.ietf.org/doc/draft-housley-cms-mts-hash-sig/" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://datatracker.ietf.org/<wbr =
class=3D"">doc/draft-housley-cms-mts-<wbr class=3D"">hash-sig/</a><br =
class=3D"">
<br class=3D"">
I understand that presentations are expected to be about 10 =
minutes.&nbsp; I plan to cover the problem that the draft is trying to =
solve, the proposed solution, and the desired next =
step.&nbsp;</blockquote><div class=3D""><br class=3D""></div><div =
class=3D"">I think it would be helpful if you said what that is, as it =
sounds like you know.</div></div></div></div></blockquote></div><br =
class=3D""><div class=3D"">I am pushing hash-based signatures on =
software and firmware downloads for two reasons. &nbsp;First, we need to =
deploy a quantum-safe signature long before there is large-scale quantum =
computer, otherwise we will not be able to deploy the next generation of =
cryptographic algorithms without physically touching every device. =
&nbsp;Second, the signature validation code in the bootloader is small =
and fast. &nbsp;Verification being small and fast makes this attractive =
in the IoT environment.</div><div class=3D""><br class=3D""></div><div =
class=3D"">The relationship to CMS makes LAMPS a reasonable place to =
proceed with this document.</div><div class=3D""><br class=3D""></div><div=
 class=3D"">The relationship to IoT firmware makes SUIT a reasonable =
place to proceed with this document.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Russ</div></body></html>=

--Apple-Mail=_45F6C2E2-1C64-4F7B-9A42-D344170B2BA9--


From nobody Wed Feb 28 06:28:12 2018
Return-Path: <fgont@si6networks.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 710C4128959 for <secdispatch@ietfa.amsl.com>; Wed, 28 Feb 2018 06:28:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 ruF2hecRwOm8 for <secdispatch@ietfa.amsl.com>; Wed, 28 Feb 2018 06:28:09 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0092D12D77E for <secdispatch@ietf.org>; Wed, 28 Feb 2018 06:28:08 -0800 (PST)
Received: from [192.168.3.68] (unknown [186.138.211.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 5CC5280C47; Wed, 28 Feb 2018 15:28:04 +0100 (CET)
To: secdispatch@ietf.org
From: Fernando Gont <fgont@si6networks.com>
Cc: Roman Danyliw <rdd@cert.org>, =?UTF-8?Q?Iv=c3=a1n_Arce_=28Quarkslab=29?= <iarce@quarkslab.com>
Message-ID: <0f2f887e-56c1-2e69-4762-65860c2cd303@si6networks.com>
Date: Wed, 28 Feb 2018 11:27:57 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/CXuvV5pW3Wik7Yl1fChZiNPkMwQ>
Subject: Re: [Secdispatch] Call for agenda items for SecDispatch at IETF 101
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Feb 2018 14:28:11 -0000

Hello, Roman,

> Hello!
> 
> SecDispatch has been tentatively scheduled at IETF 101 on Tuesday
> (March 20) at 0930-1200.  If you would like time on the agenda, send
> your request to the mailing list.  Helpful items to include in your
> request (if known/applicable) are:
> 
> ** pointers to a draft(s)/document ** pointers to related background
> or prior discussion ** desired next steps
> 
> If needed, precedence will be given to documents that have
> demonstrated interest in the form of active drafts and list
> discussion.

I'd like to request time on the agenda.

* Title: "Security and Privacy Implications of Numeric Identifiers
Employed in Network Protocols"

* Filename: draft-gont-predictable-numeric-ids-02

* Presenter: Fernando Gont <fgont@si6networks.com>

* Desired next steps:
 + Decide whether to pursue as single document, or to split the document
into separate smaller documents
 + Adopt as wg item

* Background/previous discussion:

This I-D was originally discussed on the SAAG list, and presented at the
SAAG meeting in Buenos Aires
(<https://www.ietf.org/proceedings/95/minutes/minutes-95-saag>). It
seemed that folks agreed that the I-D had valuable information. There
also seemed to be agreement to split the document in smaller bits,
roughly as follows:

   + Sample timeline of flawed IDs

https://www.ietf.org/internet-drafts/draft-gont-numeric-ids-history-03.txt

   + Advice on numeric ID generation

https://www.ietf.org/internet-drafts/draft-gont-numeric-ids-generation-02.txt

   + Update to RFC3552

https://www.ietf.org/internet-drafts/draft-gont-numeric-ids-sec-considerations-02.txt


At the time, the update to RFC3552 was put on hold because of the
rfc3552bis effort which was later aborted
(<https://mailarchive.ietf.org/arch/msg/saag/4vf5RtHjliFs7dgsG8MKmhmgOi8>).

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Feb 28 08:03:12 2018
Return-Path: <housley@vigilsec.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96D1712EB2E for <secdispatch@ietfa.amsl.com>; Wed, 28 Feb 2018 08:03:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 YOOTWi5noJlI for <secdispatch@ietfa.amsl.com>; Wed, 28 Feb 2018 08:03:06 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACF4312EB2D for <secdispatch@ietf.org>; Wed, 28 Feb 2018 08:03:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 8B242300590 for <secdispatch@ietf.org>; Wed, 28 Feb 2018 11:03:04 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 0_kGOfSHg4-1 for <secdispatch@ietf.org>; Wed, 28 Feb 2018 11:03:03 -0500 (EST)
Received: from [172.22.112.5] (unknown [65.132.39.155]) by mail.smeinc.net (Postfix) with ESMTPSA id 4E75430041E; Wed, 28 Feb 2018 11:03:03 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <0f2f887e-56c1-2e69-4762-65860c2cd303@si6networks.com>
Date: Wed, 28 Feb 2018 11:03:05 -0500
Cc: IETF  SecDispatch <secdispatch@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8CD0FFB6-212A-444B-8FDF-70C2D5F3CA5D@vigilsec.com>
References: <0f2f887e-56c1-2e69-4762-65860c2cd303@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/Y4BwQFkZSn8OoAGOsZP5l32-Ea0>
Subject: Re: [Secdispatch] Call for agenda items for SecDispatch at IETF 101
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Feb 2018 16:03:10 -0000

Fernando:

I do not think that SecDispatch will adopt any documents itself.  =
Instead, the idea is to suggest a way forward, and then have the people =
in the room discuss that suggestion.

Russ


> On Feb 28, 2018, at 9:27 AM, Fernando Gont <fgont@si6networks.com> =
wrote:
>=20
> Hello, Roman,
>=20
>> Hello!
>>=20
>> SecDispatch has been tentatively scheduled at IETF 101 on Tuesday
>> (March 20) at 0930-1200.  If you would like time on the agenda, send
>> your request to the mailing list.  Helpful items to include in your
>> request (if known/applicable) are:
>>=20
>> ** pointers to a draft(s)/document ** pointers to related background
>> or prior discussion ** desired next steps
>>=20
>> If needed, precedence will be given to documents that have
>> demonstrated interest in the form of active drafts and list
>> discussion.
>=20
> I'd like to request time on the agenda.
>=20
> * Title: "Security and Privacy Implications of Numeric Identifiers
> Employed in Network Protocols"
>=20
> * Filename: draft-gont-predictable-numeric-ids-02
>=20
> * Presenter: Fernando Gont <fgont@si6networks.com>
>=20
> * Desired next steps:
> + Decide whether to pursue as single document, or to split the =
document
> into separate smaller documents
> + Adopt as wg item
>=20
> * Background/previous discussion:
>=20
> This I-D was originally discussed on the SAAG list, and presented at =
the
> SAAG meeting in Buenos Aires
> (<https://www.ietf.org/proceedings/95/minutes/minutes-95-saag>). It
> seemed that folks agreed that the I-D had valuable information. There
> also seemed to be agreement to split the document in smaller bits,
> roughly as follows:
>=20
>   + Sample timeline of flawed IDs
>=20
> =
https://www.ietf.org/internet-drafts/draft-gont-numeric-ids-history-03.txt=

>=20
>   + Advice on numeric ID generation
>=20
> =
https://www.ietf.org/internet-drafts/draft-gont-numeric-ids-generation-02.=
txt
>=20
>   + Update to RFC3552
>=20
> =
https://www.ietf.org/internet-drafts/draft-gont-numeric-ids-sec-considerat=
ions-02.txt
>=20
>=20
> At the time, the update to RFC3552 was put on hold because of the
> rfc3552bis effort which was later aborted
> =
(<https://mailarchive.ietf.org/arch/msg/saag/4vf5RtHjliFs7dgsG8MKmhmgOi8>)=
.
>=20
> Thanks!
>=20
> Best regards,
> --=20
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch


From nobody Wed Feb 28 08:45:22 2018
Return-Path: <fgont@si6networks.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 409E412DA0C for <secdispatch@ietfa.amsl.com>; Wed, 28 Feb 2018 08:45:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 1uBSSUJf5a6l for <secdispatch@ietfa.amsl.com>; Wed, 28 Feb 2018 08:45:18 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1DA3126C22 for <secdispatch@ietf.org>; Wed, 28 Feb 2018 08:45:13 -0800 (PST)
Received: from [192.168.3.68] (unknown [186.138.211.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id C022D80DAD; Wed, 28 Feb 2018 17:45:09 +0100 (CET)
To: Russ Housley <housley@vigilsec.com>
Cc: IETF SecDispatch <secdispatch@ietf.org>
References: <0f2f887e-56c1-2e69-4762-65860c2cd303@si6networks.com> <8CD0FFB6-212A-444B-8FDF-70C2D5F3CA5D@vigilsec.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <eaf128a3-6fea-ef99-8777-6255086a2de7@si6networks.com>
Date: Wed, 28 Feb 2018 13:34:35 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <8CD0FFB6-212A-444B-8FDF-70C2D5F3CA5D@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/4mkNPJMJ2LTRg6OnVFZ-jXZB1nU>
Subject: Re: [Secdispatch] Call for agenda items for SecDispatch at IETF 101
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Feb 2018 16:45:21 -0000

Hi, Russ,

On 02/28/2018 01:03 PM, Russ Housley wrote:
> Fernando:
> 
> I do not think that SecDispatch will adopt any documents itself.  Instead, the idea is to suggest a way forward, and then have the people in the room discuss that suggestion.

Yes, my bad.

Thanks!
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Feb 28 09:16:24 2018
Return-Path: <rdd@cert.org>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6D8112D7F1 for <secdispatch@ietfa.amsl.com>; Wed, 28 Feb 2018 09:16:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 N0L143-1iGEP for <secdispatch@ietfa.amsl.com>; Wed, 28 Feb 2018 09:16:20 -0800 (PST)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (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 4852E1242F5 for <secdispatch@ietf.org>; Wed, 28 Feb 2018 09:16:20 -0800 (PST)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id w1SHGIV9028401; Wed, 28 Feb 2018 12:16:19 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu w1SHGIV9028401
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1519838179; bh=0t2wORiEus8dYaq7l2mDDsVKyszpS/Ql0ONaeskEfQI=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=b3cQM/Dd+41FtLVI28aiJEIqHzysRVZ+oZNpJ8sX/xr8clmATlYUjUCvskpeELBCm KIKQtXsDGzbsKBI+AGIc5X9SpkUDSjxyL7WD3IGMplW8DVdH4y4wOGy8ZeaxucFdOf JxWXLnISkpBnylQJKXqw6e/J91dBCl77wa5qKvDQ=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id w1SHGHiO008697; Wed, 28 Feb 2018 12:16:18 -0500
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0361.001; Wed, 28 Feb 2018 12:16:17 -0500
From: Roman Danyliw <rdd@cert.org>
To: Fernando Gont <fgont@si6networks.com>, Russ Housley <housley@vigilsec.com>
CC: IETF SecDispatch <secdispatch@ietf.org>
Thread-Topic: [Secdispatch] Call for agenda items for SecDispatch at IETF 101
Thread-Index: AQHTsKBf+LZtjlVbA0quG1oyA6tbRaO6TcyAgAAIzYD//6+QwA==
Date: Wed, 28 Feb 2018 17:16:16 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC0137F6B4B0@marathon>
References: <0f2f887e-56c1-2e69-4762-65860c2cd303@si6networks.com> <8CD0FFB6-212A-444B-8FDF-70C2D5F3CA5D@vigilsec.com> <eaf128a3-6fea-ef99-8777-6255086a2de7@si6networks.com>
In-Reply-To: <eaf128a3-6fea-ef99-8777-6255086a2de7@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/dC_BAL3FAE7yfSUnRoDtuMJVkyI>
Subject: Re: [Secdispatch] Call for agenda items for SecDispatch at IETF 101
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Feb 2018 17:16:22 -0000

Hi Fernando and Russ!

> -----Original Message-----
> From: Secdispatch [mailto:secdispatch-bounces@ietf.org] On Behalf Of
> Fernando Gont
> Sent: Wednesday, February 28, 2018 11:35 AM
> To: Russ Housley <housley@vigilsec.com>
> Cc: IETF SecDispatch <secdispatch@ietf.org>
> Subject: Re: [Secdispatch] Call for agenda items for SecDispatch at IETF =
101
>=20
> Hi, Russ,
>=20
> On 02/28/2018 01:03 PM, Russ Housley wrote:
> > Fernando:
> >
> > I do not think that SecDispatch will adopt any documents itself.  Inste=
ad, the
> idea is to suggest a way forward, and then have the people in the room di=
scuss
> that suggestion.
>=20
> Yes, my bad.

To provide further color to Russ's comment, the SecDispatch draft chart [1]=
 outlines the outcomes for items brought to the WG.  They are as follows:

--[snip]--
- Directing the work to an existing WG.
- Developing a proposal for a BOF.
- Developing a charter for a new WG.
- Making recommendations that documents be AD-sponsored (which ADs may or m=
ay not choose to follow).
- By agreement with SEC ADs, processing simple administrative documents.
- Deferring the decision for the new work.
- Rejecting the new work.
--[end]--

Bottom line, the WG will not adopt any documents for itself.

Regards,
Roman

[1] https://datatracker.ietf.org/wg/secdispatch/about/


