Re: [Secdispatch] Call for agenda items for SecDispatch at IETF 101

Fernando Gont <fgont@si6networks.com> Wed, 28 February 2018 14:28 UTC

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>, "Iván Arce (Quarkslab)" <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