Re: [Secdispatch] Addition to saag agenda? (predictable numeric ids)

Eric Rescorla <ekr@rtfm.com> Tue, 12 March 2019 18:16 UTC

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 81C981277DE for <secdispatch@ietfa.amsl.com>; Tue, 12 Mar 2019 11:16:58 -0700 (PDT)
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, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 c9S3RC8EGzM0 for <secdispatch@ietfa.amsl.com>; Tue, 12 Mar 2019 11:16:56 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 193201275F3 for <secdispatch@ietf.org>; Tue, 12 Mar 2019 11:16:56 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id x13so3193396ljj.5 for <secdispatch@ietf.org>; Tue, 12 Mar 2019 11:16:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dBf+kUbZidSbNKtI6YOs/iMqhRiSNHzQFjXl3Joczk8=; b=NtVzxjdfJnEugiUsew1GzjY1jjCH2ueAhHLHj7QBwl2uVqMRgihYW2u/2P8DAE68B7 NIZ7OcKjnurXIIpC3dJYmRmeouY/vLFUyEKGwDAAdtgxVZG39AFAQmRNld+Dp6YyJPtB f1iBvMBjIOINrp/QyJKjI06sHrhoK3nxSusp2V4uTLc5BzAvicl9TL21wKXK6mup23mB +Uv7Zaoce9IL8FWHdMUsEG3BPGXKt7waqXnnUy6YOGN5vCjecJrnfYqnObyQ7iTR9GrB zT2BgWr8b48DM9Dh6fsHLTR9dvL+vzqd8/hHLZkvPq2EO6tQellnSpi1uHsOnVcgz+4s Dgow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dBf+kUbZidSbNKtI6YOs/iMqhRiSNHzQFjXl3Joczk8=; b=eIkE8la2/Y2CnjfELklE3jktAz6RKQYaI/RlfogAB5XUJXtYUv13jTtEGNM4hllxqM 5MzR3r7ZqVxbSZRNrv1gsON5HVT6X/OzrQp4i/OlJxzVaH4ZqDSDqwcb3D5UYbQMzifu FgvAP5vAzAghbRMOAQ4i4q82sU9aAn9+GlF1ZChmUsKJJ8dLVv0u95qHcLxEUhNZjCOL dVjtnsLea4xk+i6f1QVefDXNuzgrLsOfWeHXzU9uvKj9DFlq4jE+C4+4/7zCydtINtmR tv5g/JzIy234v6GEQ7067mI+ZQwlVEFt3ZNeRe22DOwKsyCOoMUY+iDYMFnDjEbQsLrp LLDg==
X-Gm-Message-State: APjAAAX+vu9x/sAxXa62yVjUhuIGpBDICSvTAp0RrHyUarj0/PM2FR5r 7ighIUwKgygwUdbnVtX+o5+l2jSdClmmiQB0Hjl/RQ==
X-Google-Smtp-Source: APXvYqw45IdB1CBrT5gX2l7xcHV7WEI9q7ylseNb9jAJ7gNfawasx4dt44E28QT3zCgQ/RCo36RaBAQQpeCj7vinG8g=
X-Received: by 2002:a2e:47c4:: with SMTP id u187mr20825325lja.10.1552414614151; Tue, 12 Mar 2019 11:16:54 -0700 (PDT)
MIME-Version: 1.0
References: <c77d0c40-3741-2c9f-1c4f-9aa6ecc0e234@si6networks.com> <CABcZeBMgnOd2Kw0nh9tOTBjcUpADjwgtvzqSna6_K5SqzzmFDQ@mail.gmail.com>
In-Reply-To: <CABcZeBMgnOd2Kw0nh9tOTBjcUpADjwgtvzqSna6_K5SqzzmFDQ@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 12 Mar 2019 11:16:15 -0700
Message-ID: <CABcZeBOfv=yO+pA8hVeijmR0tP9ijJGKEiSO2_nadmGFaR2KEQ@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>, IETF SecDispatch <secdispatch@ietf.org>
Cc: Benjamin Kaduk <kaduk@mit.edu>
Content-Type: multipart/alternative; boundary="0000000000009f02840583e9b143"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/M0NRuBIH5jXwa7OYMoLr7NJq3H0>
Subject: Re: [Secdispatch] Addition to saag agenda? (predictable numeric ids)
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Mar 2019 18:16:59 -0000

Oops, not to the chairs, I guess. Sorry about that.

On Tue, Mar 12, 2019 at 11:10 AM Eric Rescorla <ekr@rtfm.com> wrote:

> +SECDISPATCH chairs.
>
> This seems like it's more appropriate for SECDISPATCH.
>
> -Ekr
>
>
> On Tue, Mar 12, 2019 at 11:08 AM Fernando Gont <fgont@si6networks.com>
> wrote:
>
>> Folks,
>>
>> How about this one?
>>
>> * Title: "Security and Privacy Implications of Numeric Identifiers
>> Employed in Network Protocols"
>>
>> * Filename: draft-gont-predictable-numeric-ids
>>
>> * Presenter: Fernando Gont <fgont@si6networks.com>
>>
>>
>> * 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
>> >).
>>
>> The rfc3522bis died, but but this doc was stalled. Meanwhile, protocol
>> implementations employing predictable IDs kept popping up.
>>
>> I wonder if this is something that saag would like to see move forward?
>>
>> Thanks!
>>
>> Cheers,
>> --
>> Fernando Gont
>> SI6 Networks
>> e-mail: fgont@si6networks.com
>> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>>
>>
>>
>>
>>