IETF Logo Mail Archive

Re: [Secdispatch] Numeric IDs: Update to RFC3552

Eric Rescorla <ekr@rtfm.com> Thu, 18 April 2019 13:45 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 9D498120159 for <secdispatch@ietfa.amsl.com>; Thu, 18 Apr 2019 06:45:58 -0700 (PDT)
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, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable 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 Rq0L04iUD6tY for <secdispatch@ietfa.amsl.com>; Thu, 18 Apr 2019 06:45:53 -0700 (PDT)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 F3DB6120334 for <secdispatch@ietf.org>; Thu, 18 Apr 2019 06:45:52 -0700 (PDT)
Received: by mail-lf1-x12f.google.com with SMTP id h18so1665652lfj.11 for <secdispatch@ietf.org>; Thu, 18 Apr 2019 06:45:52 -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=ryK04+SKt7tX14hhOjTAk5N9hPjirwAgBapb4n6wHVY=; b=Jn5yuM60kWhcBNmdYo9cGRQ+/vYGlxPfbZq0IKJlktkLIF+xB7KwAZQ+B8kXbB+uoj S0HNmhoWCJMoefvyu2iCp/aCM414hYD59alG3JxdeDcSE0DLOd7rLTjWtW+c8B3CzTj6 UKC/Tvdjn8rW1aNEaU8d5YlHpLJgSm8+6N2TF4Li4nTZrSXA5BV83RC/InAa2oaG3I7G KDN6/DgMUd9FitSGaFRv270CwhuETKxxjSJEyrZeamf4kZ+bwVSneAirZbUIFo3DWRLl pap9n6q8CzY9feQyUiwY/Sl+COb6e8RjFr4Nm/egq8rKoyjzH0EqqIL0+/3y2Xh0QAIo 3k6g==
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=ryK04+SKt7tX14hhOjTAk5N9hPjirwAgBapb4n6wHVY=; b=egO55tBp+4CIszDqRM96xnjj2879fClIhWiXlWgonf1ayQQVJcELKIbraP/UUvqLkA txEIPeH8rpqOa5YBNyV9Dzjm6JPmQ1lgMlf0sL/3ZvWiNR/gV3PmlyDRMnCZd17iFzhF iHWgOyB9BOd5QHH8AbYU1nNZWmCrEab/JekrGRYlUIonMG84oKYXMea/T/qBRjSz/MGv 7KUCLSAz76ONpV6U/BqbZeJpMKNUGJfGylr5CZ1ZOh+Hd/Y0Q+M90g7jzrVD4GloHVpn HlAzMLVDninLq1RvlgRzjON18hO4pHrDBJN2gyyMgd6uJDfe6GyFGGQ1S1UHORt6Vgq8 zSKw==
X-Gm-Message-State: APjAAAU2M1cqB9nhFg+CkDcvyg4OOGUtVdOeNW6SftSLLEcm9Kp/d8Qo RHQ7JwPHLYGvxt/2t2K62fcvv4SOY4C2hotyEZ35xsGF
X-Google-Smtp-Source: APXvYqwmvoRmz4PTthV/f9Sw5yI+sCSVUa2nNg3zu4xwfO1hD0ImFXp237W/Pm3jIstOISip1BLpUZFlLZ6SpPV87RY=
X-Received: by 2002:a19:7911:: with SMTP id u17mr18951679lfc.90.1555595150957; Thu, 18 Apr 2019 06:45:50 -0700 (PDT)
MIME-Version: 1.0
References: <4ac730a6-73ca-74cd-e848-4a6645bd0403@si6networks.com>
In-Reply-To: <4ac730a6-73ca-74cd-e848-4a6645bd0403@si6networks.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 18 Apr 2019 06:45:10 -0700
Message-ID: <CABcZeBOy6MB0OG2cs=EE6hWB4pXBuNzW=LcQ+1dKmJzHBOUR-g@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: IETF SecDispatch <secdispatch@ietf.org>, secdispatch-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000063342d0586ce38e1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/zIIsVh5vc71Amd0tuSkYNPZSx2s>
Subject: Re: [Secdispatch] Numeric IDs: Update to RFC3552
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: Thu, 18 Apr 2019 13:45:59 -0000

On Tue, Apr 16, 2019 at 2:07 AM Fernando Gont <fgont@si6networks.com> wrote:

> Folks,
>
> At the last secdispatch meeting I presented our I-D
> draft-gont-predictable-numeric-ids.
>
> >From the meeting discussion, it would seem to me that there is support
> for this work.
>
> It would also seem to me that part of this work is to be pursued in an
> appropriate IRTF rg, while the update to RFC3552
> (draft-gont-numeric-ids-sec-considerations) should be pursued as an
> AD-sponsored document.
>

I'm somewhat skeptical on an update to 3552; the proposed set of things to
be improved seems unclear.

I don't think that the material in this document should be added to 3552,
as the purpose of 3552 is not really to go into that kind of detail about
any specific topic.

-Ekr


> We're wondering how to proceed here.
>
> Thanks!
>
> Cheers,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch
>

v2.8.10 | Report a Bug | By Email