[Trans] Policy for adding to IANA registries requested in 6962-bis

Eran Messeri <eranm@google.com> Mon, 12 December 2016 15:45 UTC

Return-Path: <eranm@google.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7DA7129C9E for <trans@ietfa.amsl.com>; Mon, 12 Dec 2016 07:45:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.896
X-Spam-Level:
X-Spam-Status: No, score=-4.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-2.896, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 f90BZIUw_8Eu for <trans@ietfa.amsl.com>; Mon, 12 Dec 2016 07:45:14 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 4C6AA129C8D for <trans@ietf.org>; Mon, 12 Dec 2016 07:45:01 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id f82so74153618wmf.1 for <trans@ietf.org>; Mon, 12 Dec 2016 07:45:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=1zH+Mg0Y7hVxvv6lemEgKeyP2bvxKWlttmXm+hsJL0g=; b=XcPuPGqtsqzgTah66TqNCEjYXycCPgkI7ZBcl8DizEoSZhIRdn4qcHq8LAMU+XtFst nwkxTgIMQQ/DVHuORPEHijpZTwDmzPRT4N1knB9Id/VR93AruYaWg+32lcTb8/PJfdOr 9BmecQpIy9Y3CiexiskoRc2F8/mGUXM2fp36XJjpI+lzAJPEKo0iyz6nt/nTq1FHLfl6 Gu6nayR8yyaqtv7g6XBazJ6UFMdTQ0ezIzyeMpaPVuiPl+QGC6MS0VVSccTbxrXCsmlC yVS/m0yT89KHMrwNsGXqEv0xXhvJDt3fyEGgdKebEudu97MjmcPHcGytOg7IdDFzJAKO hL4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=1zH+Mg0Y7hVxvv6lemEgKeyP2bvxKWlttmXm+hsJL0g=; b=A/VuS1eByMPsWhHlktvbYIVrKjFpyUgImZjso2FvVbaxpQ06g2n8G/l49ieZtthXCQ OdXESTVQWFqBfnGuGpnTeGwOwg7Bm3homKr9FwLnyDMEFPQpr32GT4PSqmFRZLjMg+23 hNXHRDPlWthwqY9EpwqydjuRZxOxAkFbmPYu3cZnSXduEhJWP2jrSUuyHLjMf8WRBNhg 2WLCiVuKN3+3rn2ajVSFBe1TQtyLYTqV3LaFkb1AzbdhRwBVWuOhddEDeVZ6RUgxWars Zlrr3/p4Mls9A0qF2IoQhH9bm0/d/jVm1hp498T5aW5QpWual++yrUQzvtTTiqAxeeDP l6SQ==
X-Gm-Message-State: AKaTC03+WIiWbOQyzehocrtMJTug9ZfAyuk48NQlafdb1zqQhsK1ZmQ4VNBw5iRE0UlZ0SpovRSgt9Z2L21+6QtZ
X-Received: by 10.28.7.130 with SMTP id 124mr17390673wmh.18.1481557499328; Mon, 12 Dec 2016 07:44:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.31.21 with HTTP; Mon, 12 Dec 2016 07:44:28 -0800 (PST)
From: Eran Messeri <eranm@google.com>
Date: Mon, 12 Dec 2016 15:44:28 +0000
Message-ID: <CALzYgEce25Z7tSz6T+kmFQCA+xbgO0ECknV6nE1m55-pey3vrQ@mail.gmail.com>
To: "trans@ietf.org" <trans@ietf.org>
Content-Type: multipart/alternative; boundary="001a1144267a781475054377fc3f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/KF_RMZiJMQudVM9vMUSAOJa6Kmw>
Subject: [Trans] Policy for adding to IANA registries requested in 6962-bis
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2016 15:45:16 -0000

No policy has been specified in 6962-bis for adding values to the IANA
registries requested.

In https://github.com/google/certificate-transparency-rfcs/pull/215 I
propose the following policies, all based on definitions in RFC5226:
* Hash algorithms and Signature algorithms: Expert Review
* SCT extensions and STH extensions: Specification Required
* Log ID 1, Log ID 2: First Come First Served.

Feedback welcome, since, as far as I recall, this topic was not discussed
on the list previously.

Eran