
From nobody Fri Mar  1 15:13:05 2019
Return-Path: <jmh@joelhalpern.com>
X-Original-To: trans@ietf.org
Delivered-To: trans@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BFBF12D4E6; Fri,  1 Mar 2019 15:13:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-trans-rfc6962-bis.all@ietf.org, trans@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.92.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155148198458.6254.15247203587880068135@ietfa.amsl.com>
Date: Fri, 01 Mar 2019 15:13:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/_Lfb3yRkmuhZSSNWpYNMir3LU9U>
Subject: [Trans] Genart last call review of draft-ietf-trans-rfc6962-bis-31
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 01 Mar 2019 23:13:05 -0000

Reviewer: Joel Halpern
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-trans-rfc6962-bis-31
Reviewer: Joel Halpern
Review Date: 2019-03-01
IETF LC End Date: 2019-03-14
IESG Telechat date: 2019-03-14

Summary: This document is ready for publication as an Experimental RFC

Major issues: N/A

Minor issues: N/A

Nits/editorial comments: N/A



From nobody Sat Mar  2 10:08:09 2019
Return-Path: <paul@nohats.ca>
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 35CA7130E66; Sat,  2 Mar 2019 10:08:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 L5gfcLIo5g5i; Sat,  2 Mar 2019 10:07:59 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 CF5FC12D4F0; Sat,  2 Mar 2019 10:07:58 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 44BZ5R5RLkzCFb; Sat,  2 Mar 2019 19:07:55 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1551550075; bh=r03N7MfvUsE73gw/cE/kJbjSJjkvIndZFA6Fg/nk1TU=; h=Date:From:To:cc:Subject; b=D8wjUmk2c06aBu07qeJgjWEDfPhUUd0QYNUfj7c7n5/wVQzvKfMIFRxSNRK2GqJgS AvAxEzCA5kjvv9bowCCpa8CwhttuA2r4iGMtfQkyk4USidh0wxJJaGVnwzYFraGOjn eqmZY8QJORjlUG0GBmrSA69CqtBci7MEJdPtAjSw=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id iGqSpmowMYu8; Sat,  2 Mar 2019 19:07:54 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Sat,  2 Mar 2019 19:07:53 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id D12EA36FBA; Sat,  2 Mar 2019 13:07:52 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca D12EA36FBA
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C58A640D358A; Sat,  2 Mar 2019 13:07:52 -0500 (EST)
Date: Sat, 2 Mar 2019 13:07:52 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: tls-reg-review@ietf.org
cc: Trans <trans@ietf.org>
Message-ID: <alpine.LRH.2.21.1903021301470.23660@bofh.nohats.ca>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/WbNlOfKkoqIRGvINjDibHgzqBVU>
Subject: [Trans] Request to register value transparency_info(TBD) to the "TLS ExtensionType Values" registry
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 02 Mar 2019 18:08:01 -0000

Hi,

For the 6962bis document we are requesting a value in the "TLS
ExtensionType Values" registry:

https://tools.ietf.org/html/draft-ietf-trans-rfc6962-bis-31#section-10.1

    10.1.  New Entry to the TLS ExtensionType Registry

    IANA is asked to add an entry for "transparency_info(TBD)" to the
    "TLS ExtensionType Values" registry defined in [RFC8446], setting the
    "Recommended" value to "Y", setting the "TLS 1.3" value to "CH, CR,
    CT", and citing this document as the "Reference".


As per https://tools.ietf.org/html/rfc8447#section-17 we are requesting
a review of this request by the designed Expert Pool for TLS.

Paul & Melinda


From taavieomae@gmail.com  Mon Mar  4 16:50:22 2019
Return-Path: <taavieomae@gmail.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 7CDFD13124F for <trans@ietfa.amsl.com>; Mon,  4 Mar 2019 16:50:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.969
X-Spam-Level: 
X-Spam-Status: No, score=0.969 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, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, 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=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 UFXAbQN28U7f for <trans@ietfa.amsl.com>; Mon,  4 Mar 2019 16:50:20 -0800 (PST)
Received: from mail-it1-x12a.google.com (mail-it1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (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 22F2613124B for <trans@ietf.org>; Mon,  4 Mar 2019 16:50:20 -0800 (PST)
Received: by mail-it1-x12a.google.com with SMTP id w18so1710172itj.4 for <trans@ietf.org>; Mon, 04 Mar 2019 16:50:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=C1SuZcnpXYTgoiYXfcLNZiinnPKv8/YQrfrhWBSdTac=; b=khtUq4CTdG7XPfs9//a5ZUfSTxlNzhdUz3rEcFfg2rN5pzZuXt+YfdCuyfjq6IxHL6 7OYdX5IQAa5jPrytcYhobRHdEboT8nshM2VKJ0q+XGEd+wy3Puf3xYZH7OiIOBd22I2p BBOo0SaES9S8YpxKxwIb9dZil8XblRVN8uDJR3/qYB1tPnuTsaR5hrmCpwdbZJhSwrXd g66IwuNrWoVrA5gV5bQb1l3p6nCYfEnEcbFu6cBD2DcYwz3Cmy3DPDa66ItkMAcqmKbX HEj097vp9naYGY2eya5mcSTDrsv5F7hO54UK11d+ugKWG0nk8aSHgGQDTkIz4scKQDJ3 RqZg==
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; bh=C1SuZcnpXYTgoiYXfcLNZiinnPKv8/YQrfrhWBSdTac=; b=N1dhkBHKen1p4w9Ds0GTPLOp4YSNxwJldEW3NZKC+Ub7jkR34gLRB/fw9JGs2V3aLn LLkdEZxBqP6kKV6wIl9ITlg/t0IBu3/HKNeF2NnNrgDFEgRtu9+LL5UxF+O/kVfBdk6F WVpfn+Ve8+a8Ctxovr5yNEJu7rg8hpu6kjjljuFM0Ro7EZYoDxW4hHXW6tY7G1Ksh2/o MFAZzadYG1Ke48aRSt8dlMaiMbwFEDid/oqe+dYt2CoxRpJVKb/z+ZIKqYJXxyoEI3k9 9ca+QJk4TTqmXcz0Vh8ohqYX+xeevB0X9N1QRNhWyPUs1uRcT52He6Y5ugh4pnpsI8Wr SqqA==
X-Gm-Message-State: APjAAAWkE1WLBgH2KOQsk8EwFj+3ARNdXmpMNnYJg8DCO+NjnSujv7i6 QZ9MhW0HHl2GZg2bdEtGdfjDLcRX4sWhi9KTD40aYTefr/s=
X-Google-Smtp-Source: APXvYqxBQoi7UlU1CnpZw/oYBMHYe8z+CfW+5DB452khocg624uLiFfioXEqizjB+zvkt+kmmPrSfc6Aw+OF0HOUz2s=
X-Received: by 2002:a24:4d4b:: with SMTP id l72mr1148770itb.177.1551747018960;  Mon, 04 Mar 2019 16:50:18 -0800 (PST)
MIME-Version: 1.0
From: =?UTF-8?B?VGFhdmkgRW9tw6Rl?= <taavieomae@gmail.com>
Date: Tue, 5 Mar 2019 02:50:07 +0200
Message-ID: <CALfTr+qwijKjXPrRXK8Q9um5sRXrnjVYiSF9D_NcWnMN3YNtxA@mail.gmail.com>
To: trans@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d8b5b605834e4197"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/wbbeAI4I2AwtH-18QpiHeozBSFQ>
Subject: [Trans] Certificate Transparency log GDPR compliance
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 05 Mar 2019 00:51:16 -0000

--000000000000d8b5b605834e4197
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi

I hope this is the right place to ask this question. The question itself is
quite simple, how resilient is Certificate Transparency logs to GDPR
takedown requests and what are the methods of removing a certificate from
public logs without compromising the integrity of the logs?

The reason why I'm asking this seemingly simple question is because Estonia
has been issuing certificates to it's citizens since 2003, they're issued
by a public CA and some of the certificates already exist in current logs (
https://ct.googleapis.com/rocketeer/ct/v1/get-entries?start=3D110654446&end=
=3D110654446
<https://www.google.com/url?q=3Dhttps://ct.googleapis.com/rocketeer/ct/v1/g=
et-entries?start%3D110654446%26end%3D110654446&sa=3DD&usg=3DAFQjCNEbCbHE9Ov=
VwN9nQWP0i2m38mSbcw>).
But if I'm not mistaken, GDPR applies to CT as well, those certificates
contain PII, thus those certificates should be under the "mercy" of who's
PII it is, but as far as I've searched, noone has discussed this
previously, am I wrong?





Taavi Eom=C3=A4e

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

<div dir=3D"ltr">Hi<br><br>I hope this is the right place to ask this=C2=A0=
question. The question itself is quite simple, how resilient is Certificate=
 Transparency logs to GDPR takedown requests and what are the methods of re=
moving a certificate from public logs without compromising the integrity of=
 the logs?<div><br></div><div>The reason why I&#39;m asking this seemingly =
simple question is because Estonia has been issuing certificates to it&#39;=
s citizens since 2003, they&#39;re issued by a public CA and some of the ce=
rtificates already exist in current logs (<a href=3D"https://www.google.com=
/url?q=3Dhttps://ct.googleapis.com/rocketeer/ct/v1/get-entries?start%3D1106=
54446%26end%3D110654446&amp;sa=3DD&amp;usg=3DAFQjCNEbCbHE9OvVwN9nQWP0i2m38m=
Sbcw" target=3D"_blank" rel=3D"noreferrer nofollow" style=3D"font-size:13px=
;margin:0px;border:0px;outline:0px;vertical-align:baseline;text-decoration-=
line:none;color:rgb(102,17,204)">https://ct.googleapis.com/rocketeer/ct/v1/=
get-entries?start=3D110654446&amp;end=3D110654446</a>). But if I&#39;m not =
mistaken, GDPR applies to CT as well, those certificates contain PII, thus =
those certificates should be under the &quot;mercy&quot; of who&#39;s PII i=
t is, but as far as I&#39;ve searched, noone has discussed this previously,=
 am I wrong?<br><br><br><br><br><br>Taavi Eom=C3=A4e</div></div>

--000000000000d8b5b605834e4197--


From nobody Tue Mar 12 06:37:23 2019
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 9A844126C87 for <trans@ietfa.amsl.com>; Tue, 12 Mar 2019 06:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.511
X-Spam-Level: 
X-Spam-Status: No, score=-15.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] 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 U1_XqGiuPP7o for <trans@ietfa.amsl.com>; Tue, 12 Mar 2019 06:37:19 -0700 (PDT)
Received: from mail-yw1-xc2c.google.com (mail-yw1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) (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 617AD1277CC for <trans@ietf.org>; Tue, 12 Mar 2019 06:37:19 -0700 (PDT)
Received: by mail-yw1-xc2c.google.com with SMTP id u70so2065948ywf.7 for <trans@ietf.org>; Tue, 12 Mar 2019 06:37:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Z2WnOSPEF08IBGU9O31y62ukAU0vQsE0OcdFSZtQlIM=; b=h3x37cJUuxzr0YdhDFYWQ9Xik4lVJ5CemUzQiWUKMcdfSjQru3XYp99VT0IrpHf83G oTQxcsZcsK8LAHjwOMWD4Pwh7VtgAP5/A1SExYubY8AikW0ylOdS8jHOZ8+q6WyELhpf iR0p2ZKp8IFCF8q3yCeiqzMA2FeirJHkckHMwATUqR/WKoOiW4ySbkl8FcKyDr7JChMo ljoq4U34nEBShgAVZTSWfPy/EaNZrhtBZ/6Dfy182D/9zL57eXQQMaMaP4pffrt2M58B bZcBCGxOCKiEiKiUFXCK7krIiLpelCGS3Ak3V1frDPfE/GRCRuDIKUrXTSrfjZEr31Q3 2QQQ==
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=Z2WnOSPEF08IBGU9O31y62ukAU0vQsE0OcdFSZtQlIM=; b=j19+n6ilqXAFXZxni8w4NFMAvijqXiJ4onR2zP/J/sJPoAl6BRY+Bd6hQxyDEot+Jn cGfyGtN3wrVwrOpW7ocDNbCaOvU0vjb21HH15aYlKH7a4exnw2rKT4ZGZItbmsBbJsT/ yibojrtO9Bs/ZamcgG4jNmxUNBsf/hD5pyjklA8xv3sqLtmR2gsfITcPPHkOe3YMP6eH 3IYauF9PpNmsYbYIzPBOMRef2+g7RoCcCjVgGgVc8cYzfxGYph891imzQBURqHLFN9vy mgd6p3Fn1rBZhl3p7iGk3D6JC7Y84I/vnX9dk/QKDRZC+oz+EEU+zMPFuL0OCYARJpnF 9Vjg==
X-Gm-Message-State: APjAAAW7yuT3KUGr/bAs5CRE29GHHmLi9lqveQ7QgdE5M8tR4spcjNrN PgM4Qb1UiHpkx4VPcQZJ3M0LiRG2BDMnMu5g9wKUehnr
X-Google-Smtp-Source: APXvYqzodRwgIlIYdmLvdGUfV9JniRpTYlw0LKM5N+fIqhMCspVTqkyJjWrzBkoMNDgWL5Tqsrh867k/lGaxIvZoxAs=
X-Received: by 2002:a81:6385:: with SMTP id x127mr30102701ywb.450.1552397838384;  Tue, 12 Mar 2019 06:37:18 -0700 (PDT)
MIME-Version: 1.0
References: <CALfTr+qwijKjXPrRXK8Q9um5sRXrnjVYiSF9D_NcWnMN3YNtxA@mail.gmail.com>
In-Reply-To: <CALfTr+qwijKjXPrRXK8Q9um5sRXrnjVYiSF9D_NcWnMN3YNtxA@mail.gmail.com>
From: Eran Messeri <eranm@google.com>
Date: Tue, 12 Mar 2019 13:36:52 +0000
Message-ID: <CALzYgEeoo4ADCfufXHJDGUeqt405h5+c_3RopvZTNjzOY1TXvA@mail.gmail.com>
To: =?UTF-8?B?VGFhdmkgRW9tw6Rl?= <taavieomae@gmail.com>
Cc: "trans@ietf.org" <trans@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b578ae0583e5c935"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/4rIsYEkYjOXtA73vd43T9EVJLMo>
Subject: Re: [Trans] Certificate Transparency log GDPR compliance
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 12 Mar 2019 13:37:21 -0000

--000000000000b578ae0583e5c935
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

This issue has been discussed in the past, at least on one CT policy day I
recall.

There's currently no mechanism to remove a certificate from a public log -
mechanisms to do so were proposed (e.g. replacing the certificate with a
leaf that contains only its hash and a forward-pointer to a record in the
log explaining why it was removed) but IIRC the consensus was that  all
such mechanisms would be open to mis-use as there would be no way to
automatically/programatically verify that the reason specified for a
removal of a certificate is a valid one.

Eran

On Tue, Mar 5, 2019 at 12:51 AM Taavi Eom=C3=A4e <taavieomae@gmail.com> wro=
te:

> Hi
>
> I hope this is the right place to ask this question. The question itself
> is quite simple, how resilient is Certificate Transparency logs to GDPR
> takedown requests and what are the methods of removing a certificate from
> public logs without compromising the integrity of the logs?
>
> The reason why I'm asking this seemingly simple question is because
> Estonia has been issuing certificates to it's citizens since 2003, they'r=
e
> issued by a public CA and some of the certificates already exist in curre=
nt
> logs (
> https://ct.googleapis.com/rocketeer/ct/v1/get-entries?start=3D110654446&e=
nd=3D110654446
> <https://www.google.com/url?q=3Dhttps://ct.googleapis.com/rocketeer/ct/v1=
/get-entries?start%3D110654446%26end%3D110654446&sa=3DD&usg=3DAFQjCNEbCbHE9=
OvVwN9nQWP0i2m38mSbcw>).
> But if I'm not mistaken, GDPR applies to CT as well, those certificates
> contain PII, thus those certificates should be under the "mercy" of who's
> PII it is, but as far as I've searched, noone has discussed this
> previously, am I wrong?
>
>
>
>
>
> Taavi Eom=C3=A4e
> _______________________________________________
> Trans mailing list
> Trans@ietf.org
> https://www.ietf.org/mailman/listinfo/trans
>

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

<div dir=3D"ltr">Hi,<div><br></div><div>This issue has been discussed in th=
e past, at least on one CT policy day I recall.</div><div><br></div><div>Th=
ere&#39;s currently no mechanism to remove a certificate from a public log =
- mechanisms to do so were proposed (e.g. replacing the certificate with a =
leaf that contains only its hash and a forward-pointer to a record in the l=
og explaining why it was removed) but IIRC the consensus was that=C2=A0 all=
 such mechanisms would be open to mis-use as there would be no way to autom=
atically/programatically verify that the reason specified for a removal of =
a certificate is a valid one.</div><div><br></div><div>Eran</div></div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Ma=
r 5, 2019 at 12:51 AM Taavi Eom=C3=A4e &lt;<a href=3D"mailto:taavieomae@gma=
il.com">taavieomae@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><div dir=3D"ltr">Hi<br><br>I hope this is the r=
ight place to ask this=C2=A0question. The question itself is quite simple, =
how resilient is Certificate Transparency logs to GDPR takedown requests an=
d what are the methods of removing a certificate from public logs without c=
ompromising the integrity of the logs?<div><br></div><div>The reason why I&=
#39;m asking this seemingly simple question is because Estonia has been iss=
uing certificates to it&#39;s citizens since 2003, they&#39;re issued by a =
public CA and some of the certificates already exist in current logs (<a hr=
ef=3D"https://www.google.com/url?q=3Dhttps://ct.googleapis.com/rocketeer/ct=
/v1/get-entries?start%3D110654446%26end%3D110654446&amp;sa=3DD&amp;usg=3DAF=
QjCNEbCbHE9OvVwN9nQWP0i2m38mSbcw" rel=3D"noreferrer nofollow" style=3D"font=
-size:13px;margin:0px;border:0px;outline:0px;vertical-align:baseline;text-d=
ecoration-line:none;color:rgb(102,17,204)" target=3D"_blank">https://ct.goo=
gleapis.com/rocketeer/ct/v1/get-entries?start=3D110654446&amp;end=3D1106544=
46</a>). But if I&#39;m not mistaken, GDPR applies to CT as well, those cer=
tificates contain PII, thus those certificates should be under the &quot;me=
rcy&quot; of who&#39;s PII it is, but as far as I&#39;ve searched, noone ha=
s discussed this previously, am I wrong?<br><br><br><br><br><br>Taavi Eom=
=C3=A4e</div></div>
_______________________________________________<br>
Trans mailing list<br>
<a href=3D"mailto:Trans@ietf.org" target=3D"_blank">Trans@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/trans" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/trans</a><br>
</blockquote></div>

--000000000000b578ae0583e5c935--


From nobody Tue Mar 12 23:36:51 2019
Return-Path: <noreply@ietf.org>
X-Original-To: trans@ietf.org
Delivered-To: trans@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A299130EA0; Tue, 12 Mar 2019 23:36:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Adam Roach via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-trans-rfc6962-bis@ietf.org, Paul Wouters <paul@nohats.ca>, trans-chairs@ietf.org, paul@nohats.ca, trans@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.93.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155245900142.5466.15600148045977298644.idtracker@ietfa.amsl.com>
Date: Tue, 12 Mar 2019 23:36:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/chxqyRh4aa3JfXRdcvOWdNeRq6c>
Subject: [Trans] Adam Roach's Discuss on draft-ietf-trans-rfc6962-bis-31: (with DISCUSS and COMMENT)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Mar 2019 06:36:43 -0000

Adam Roach has entered the following ballot position for
draft-ietf-trans-rfc6962-bis-31: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thanks to everyone who worked on updating this protocol to reflect experience
gathered from the initial CT protocol. I have one blocking comment, and a small
number of editorial suggestions.

---------------------------------------------------------------------------

§5:

>  Clients are configured with a base URL for a log and construct URLs
>  for requests by appending suffixes to this base URL.  This structure
>  places some degree of restriction on how log operators can deploy
>  these services, as noted in [RFC7320].  However, operational
>  experience with version 1 of this protocol has not indicated that
>  these restrictions are a problem in practice.

The synthesis of URLs by a protocol in this fashion is prohibited by BCP 190:

   Scheme definitions define the presence, format, and semantics of a
   path component in URIs; all other specifications MUST NOT constrain,
   or define the structure or the semantics for any path component.

Unless the intention of this document is to update BCP 190 to change this
normative requirement, we can't publish it in its current form. Note that doing
so would require a change of venue, as updates to BCP 190 would not be covered
by the current TRANS charter.

Please see BCP 190 section 3 for alternate approaches. All three approaches
could be made to work for CT, and I would be happy to explain how to do so if
clarification is desired.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

§1.1:

>  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>  "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>  document are to be interpreted as described in [RFC2119].

Consider using the boilerplate from RFC 8174.

---------------------------------------------------------------------------

§1.3:

>  This document revises and obsoletes the experimental CT 1.0 [RFC6962]
>  protocol, drawing on insights gained from CT 1.0 deployments and on
>  feedback from the community.

Given that *this* document is also experimental, it seems a bit odd to call out
RFC 6962 as experimental.

---------------------------------------------------------------------------

§2.1.1:

>  We have established a registry of acceptable hash algorithms (see

The use of first person here is awkward. Consider: "This document
establishes..."

---------------------------------------------------------------------------

§10.2:

>  | 0x01 - | Unassigned |                        | Specification      |
>  | 0xDF   |            |                        | Required and       |
>  |        |            |                        | Expert Review      |

The policy being cited here is confusing. It is unclear whether the intention is
that values can be registered under both §4.5 and §4.6 of RFC 8126. I suspect
the intention here is the policy specified in RFC 8126 §4.6 only, without
reference to the policy in §4.5. If so, please use the formal name
"Specification Required."

---------------------------------------------------------------------------

§10.4:

>  | 0x0008 -    | Unassigned           | Specification Required and   |
>  | 0xDFFF      |                      | Expert Review                |

Same comment as above.

---------------------------------------------------------------------------

§10.5:

>  | 0x0000 -      | Unassigned | n/a | Specification Required and     |
>  | 0xDFFF        |            |     | Expert Review                  |

Same comment as above.



From nobody Wed Mar 13 06:28:46 2019
Return-Path: <ekr@rtfm.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 8C550130ECF for <trans@ietfa.amsl.com>; Wed, 13 Mar 2019 06:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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 ZnIZupVPQehz for <trans@ietfa.amsl.com>; Wed, 13 Mar 2019 06:28:43 -0700 (PDT)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::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 D0FB4130DCB for <trans@ietf.org>; Wed, 13 Mar 2019 06:28:42 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id z25so1554738ljk.8 for <trans@ietf.org>; Wed, 13 Mar 2019 06:28:42 -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=IAF2N78o1TP4f9jUr/5MKu/23sruYaVKeee5of2xXB4=; b=1Sr2e9Y4u2+uf8M/h472XxHb6NmVk3tyWBFK8SiyNQPFaae8vkAvDkcVsgunCG91j1 MrIx3XmRKVPSkp/N8vZzunkHadC7yAI+CjBg8CHA18N2gyjpjcqsrl7fIeluRhMkgtYP jBkNzv7ZxnMHpEyB/fydG3A6FmXh1aWZf9viwogMIFq0fKNof6lLorYZe29/wZENoW9e gHJdSZ6ajtyhQ7yN7KC7rbPwyfC22g7RO1FiHPJTbOnH8M5LychOG9v2veP2oIIYTpnQ 2rtvfOQXIQ6B5QH4cznJfeOffuLn0owDQIPM9x7k8U8+q0SXKK6U6cz4U8SnhmID4ePd b7HA==
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=IAF2N78o1TP4f9jUr/5MKu/23sruYaVKeee5of2xXB4=; b=HN6B0r3v46LHwdE6MDfQ5D11o9WrjZvxjEPnzIievqYzHlW338C+dafDaKQl1YZ94u s9i2f3atxJO5OGd4SAImkmvE/a+TByjmXR1wrJOn3HBej3TYdVeyz2kKi/+EqI1ez5Cc Fp6kbdE2+vioFHDHT1nz26l38LVijxHkXZKhNWhRx0NIRjOfRjVizsZnhA8xVDNR/Sr0 /bDQiO2f1kCXSGJfATlExgEt8WaqlOpRTTiiTJ+QADTtzIPZwVoWp3hpgZ102ZlKlQbI CvDo4JqNvlBB8yMhLtyBJQ2XjuTycifP/SuvADJLrRauSww8AyqKSg+mfexnkD1OANhD ts5g==
X-Gm-Message-State: APjAAAUcbHF/BBSRT4rxMrK//BUTsQ5gu/TSAIZrO4LJ6kUzK7zTJ1gK b/54keqPB+xXNmd658ejZPSqNy3v4DT+JXhXVZ5rS+/o
X-Google-Smtp-Source: APXvYqyrXHc5NLVKvtuA5e08GGNoENmMuHuyP42M63GFxofWSsX6xOoRUKAixwb2kgUNFBvq2JOufPhEvphjwzu6CZM=
X-Received: by 2002:a2e:8e86:: with SMTP id z6mr5100994ljk.28.1552483720726; Wed, 13 Mar 2019 06:28:40 -0700 (PDT)
MIME-Version: 1.0
References: <155245900142.5466.15600148045977298644.idtracker@ietfa.amsl.com>
In-Reply-To: <155245900142.5466.15600148045977298644.idtracker@ietfa.amsl.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 13 Mar 2019 06:28:04 -0700
Message-ID: <CABcZeBNMt8y7EoFr3PXR84zPgvssp5=B2x7-7sQOb4wM_94RGg@mail.gmail.com>
To: Adam Roach via Datatracker <noreply@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-trans-rfc6962-bis@ietf.org,  Paul Wouters <paul@nohats.ca>, Trans <trans@ietf.org>, trans-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b19e8a0583f9c8e6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/_TovnKsZNdK5h_gtDjbzIivHkdw>
Subject: Re: [Trans] Adam Roach's Discuss on draft-ietf-trans-rfc6962-bis-31: (with DISCUSS and COMMENT)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Mar 2019 13:28:46 -0000

--000000000000b19e8a0583f9c8e6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 12, 2019 at 11:36 PM Adam Roach via Datatracker <
noreply@ietf.org> wrote:

> Adam Roach has entered the following ballot position for
> draft-ietf-trans-rfc6962-bis-31: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Thanks to everyone who worked on updating this protocol to reflect
> experience
> gathered from the initial CT protocol. I have one blocking comment, and a
> small
> number of editorial suggestions.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A75:
>
> >  Clients are configured with a base URL for a log and construct URLs
> >  for requests by appending suffixes to this base URL.  This structure
> >  places some degree of restriction on how log operators can deploy
> >  these services, as noted in [RFC7320].  However, operational
> >  experience with version 1 of this protocol has not indicated that
> >  these restrictions are a problem in practice.
>
> The synthesis of URLs by a protocol in this fashion is prohibited by BCP
> 190:
>
>    Scheme definitions define the presence, format, and semantics of a
>    path component in URIs; all other specifications MUST NOT constrain,
>    or define the structure or the semantics for any path component.
>
> Unless the intention of this document is to update BCP 190 to change this
> normative requirement, we can't publish it in its current form. Note that
> doing
> so would require a change of venue, as updates to BCP 190 would not be
> covered
> by the current TRANS charter.
>
> Please see BCP 190 section 3 for alternate approaches. All three approach=
es
> could be made to work for CT, and I would be happy to explain how to do s=
o
> if
> clarification is desired.
>

While I agree that this is forbidden by BCP 190, this structure is
inherited from
RFC 6962, which predated 7320, so making that change seems like it's going
to be fairly disruptive. This seems like it is falling into our discussion
the other
day about what must be changed in -bis documents.

-Ekr


>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> =C2=A71.1:
>
> >  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> >  "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> >  document are to be interpreted as described in [RFC2119].
>
> Consider using the boilerplate from RFC 8174.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A71.3:
>
> >  This document revises and obsoletes the experimental CT 1.0 [RFC6962]
> >  protocol, drawing on insights gained from CT 1.0 deployments and on
> >  feedback from the community.
>
> Given that *this* document is also experimental, it seems a bit odd to
> call out
> RFC 6962 as experimental.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A72.1.1:
>
> >  We have established a registry of acceptable hash algorithms (see
>
> The use of first person here is awkward. Consider: "This document
> establishes..."
>
> -------------------------------------------------------------------------=
--
>
> =C2=A710.2:
>
> >  | 0x01 - | Unassigned |                        | Specification      |
> >  | 0xDF   |            |                        | Required and       |
> >  |        |            |                        | Expert Review      |
>
> The policy being cited here is confusing. It is unclear whether the
> intention is
> that values can be registered under both =C2=A74.5 and =C2=A74.6 of RFC 8=
126. I
> suspect
> the intention here is the policy specified in RFC 8126 =C2=A74.6 only, wi=
thout
> reference to the policy in =C2=A74.5. If so, please use the formal name
> "Specification Required."
>
> -------------------------------------------------------------------------=
--
>
> =C2=A710.4:
>
> >  | 0x0008 -    | Unassigned           | Specification Required and   |
> >  | 0xDFFF      |                      | Expert Review                |
>
> Same comment as above.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A710.5:
>
> >  | 0x0000 -      | Unassigned | n/a | Specification Required and     |
> >  | 0xDFFF        |            |     | Expert Review                  |
>
> Same comment as above.
>
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, Mar 12, 2019 at 11:36 PM Adam=
 Roach via Datatracker &lt;<a href=3D"mailto:noreply@ietf.org">noreply@ietf=
.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">Adam Roach has entered the following ballot position for<br>
draft-ietf-trans-rfc6962-bis-31: Discuss<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss-crit=
eria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/iesg/s=
tatement/discuss-criteria.html</a><br>
for more information about IESG DISCUSS and COMMENT positions.<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/" =
rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draft=
-ietf-trans-rfc6962-bis/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
DISCUSS:<br>
----------------------------------------------------------------------<br>
<br>
Thanks to everyone who worked on updating this protocol to reflect experien=
ce<br>
gathered from the initial CT protocol. I have one blocking comment, and a s=
mall<br>
number of editorial suggestions.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A75:<br>
<br>
&gt;=C2=A0 Clients are configured with a base URL for a log and construct U=
RLs<br>
&gt;=C2=A0 for requests by appending suffixes to this base URL.=C2=A0 This =
structure<br>
&gt;=C2=A0 places some degree of restriction on how log operators can deplo=
y<br>
&gt;=C2=A0 these services, as noted in [RFC7320].=C2=A0 However, operationa=
l<br>
&gt;=C2=A0 experience with version 1 of this protocol has not indicated tha=
t<br>
&gt;=C2=A0 these restrictions are a problem in practice.<br>
<br>
The synthesis of URLs by a protocol in this fashion is prohibited by BCP 19=
0:<br>
<br>
=C2=A0 =C2=A0Scheme definitions define the presence, format, and semantics =
of a<br>
=C2=A0 =C2=A0path component in URIs; all other specifications MUST NOT cons=
train,<br>
=C2=A0 =C2=A0or define the structure or the semantics for any path componen=
t.<br>
<br>
Unless the intention of this document is to update BCP 190 to change this<b=
r>
normative requirement, we can&#39;t publish it in its current form. Note th=
at doing<br>
so would require a change of venue, as updates to BCP 190 would not be cove=
red<br>
by the current TRANS charter.<br>
<br>
Please see BCP 190 section 3 for alternate approaches. All three approaches=
<br>
could be made to work for CT, and I would be happy to explain how to do so =
if<br>
clarification is desired.<br></blockquote><div><br></div><div>While I agree=
 that this is forbidden by BCP 190, this structure is inherited from</div><=
div>RFC 6962, which predated 7320, so making that change seems like it&#39;=
s going</div><div>to be fairly disruptive. This seems like it is falling in=
to our discussion the other</div><div>day about what must be changed in -bi=
s documents.<br></div><div><br></div><div>-Ekr</div><div><br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
=C2=A71.1:<br>
<br>
&gt;=C2=A0 The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQU=
IRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,<br>
&gt;=C2=A0 &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&qu=
ot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this<br>
&gt;=C2=A0 document are to be interpreted as described in [RFC2119].<br>
<br>
Consider using the boilerplate from RFC 8174.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A71.3:<br>
<br>
&gt;=C2=A0 This document revises and obsoletes the experimental CT 1.0 [RFC=
6962]<br>
&gt;=C2=A0 protocol, drawing on insights gained from CT 1.0 deployments and=
 on<br>
&gt;=C2=A0 feedback from the community.<br>
<br>
Given that *this* document is also experimental, it seems a bit odd to call=
 out<br>
RFC 6962 as experimental.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A72.1.1:<br>
<br>
&gt;=C2=A0 We have established a registry of acceptable hash algorithms (se=
e<br>
<br>
The use of first person here is awkward. Consider: &quot;This document<br>
establishes...&quot;<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A710.2:<br>
<br>
&gt;=C2=A0 | 0x01 - | Unassigned |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Specification=C2=A0 =C2=A0 =C2=
=A0 |<br>
&gt;=C2=A0 | 0xDF=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 | Required and=C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 | Expert Review=C2=A0 =C2=A0 =C2=A0 |<br>
<br>
The policy being cited here is confusing. It is unclear whether the intenti=
on is<br>
that values can be registered under both =C2=A74.5 and =C2=A74.6 of RFC 812=
6. I suspect<br>
the intention here is the policy specified in RFC 8126 =C2=A74.6 only, with=
out<br>
reference to the policy in =C2=A74.5. If so, please use the formal name<br>
&quot;Specification Required.&quot;<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A710.4:<br>
<br>
&gt;=C2=A0 | 0x0008 -=C2=A0 =C2=A0 | Unassigned=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0| Specification Required and=C2=A0 =C2=A0|<br>
&gt;=C2=A0 | 0xDFFF=C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Expert Review=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
<br>
Same comment as above.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A710.5:<br>
<br>
&gt;=C2=A0 | 0x0000 -=C2=A0 =C2=A0 =C2=A0 | Unassigned | n/a | Specificatio=
n Required and=C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 | 0xDFFF=C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0| Expert Review=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
<br>
Same comment as above.<br>
<br>
<br>
</blockquote></div></div>

--000000000000b19e8a0583f9c8e6--


From nobody Wed Mar 13 07:19:39 2019
Return-Path: <ietf@kuehlewind.net>
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 2B0E51277CC; Wed, 13 Mar 2019 07:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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 tjBB4kkNA-qo; Wed, 13 Mar 2019 07:19:33 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 BD3CF130EE9; Wed, 13 Mar 2019 07:19:33 -0700 (PDT)
Received: from [129.192.10.2] (helo=[10.149.2.6]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1h44jC-00087p-Lo; Wed, 13 Mar 2019 15:19:30 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <CABcZeBNMt8y7EoFr3PXR84zPgvssp5=B2x7-7sQOb4wM_94RGg@mail.gmail.com>
Date: Wed, 13 Mar 2019 15:19:30 +0100
Cc: Adam Roach via Datatracker <noreply@ietf.org>, draft-ietf-trans-rfc6962-bis@ietf.org, Paul Wouters <paul@nohats.ca>, Trans <trans@ietf.org>, The IESG <iesg@ietf.org>, trans-chairs@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <7017B332-62F8-47BC-94EE-02ABDB7C1B14@kuehlewind.net>
References: <155245900142.5466.15600148045977298644.idtracker@ietfa.amsl.com> <CABcZeBNMt8y7EoFr3PXR84zPgvssp5=B2x7-7sQOb4wM_94RGg@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
X-Mailer: Apple Mail (2.3445.101.1)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1552486773;f6c4f472;
X-HE-SMSGID: 1h44jC-00087p-Lo
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/Dbyjt0CM-sC2PfxzuwkefIaG5BM>
Subject: Re: [Trans] Adam Roach's Discuss on draft-ietf-trans-rfc6962-bis-31: (with DISCUSS and COMMENT)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Mar 2019 14:19:37 -0000

HI Ekr,

I actually have a related question. As this document is rather =
specifying a new version than =E2=80=9Cjust=E2=80=9D correcting an =
existing spec, it=E2=80=99s not really clear to me if the obsolete tag =
is the right choice here. I know some other protocols do this in a =
similar fashion, but I would rather recommend to only update the =
previous version RFC (in order to create a link to this new spec) or =
declare it historic if usage is not recommended anymore. I think that's =
also something we should discuss on the IESG.

Coming back to your original question about how much should be changed =
in a bis document. I think this is a valid question for bis doc that =
correct known errors. However, in case of this document that specifies a =
new version, I think it is the right thing to do to also align such a =
new version with the guidelines we follow at the time of publication.

Mirja


> On 13. Mar 2019, at 14:28, Eric Rescorla <ekr@rtfm.com> wrote:
>=20
>=20
>=20
> On Tue, Mar 12, 2019 at 11:36 PM Adam Roach via Datatracker =
<noreply@ietf..org> wrote:
> Adam Roach has entered the following ballot position for
> draft-ietf-trans-rfc6962-bis-31: Discuss
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut =
this
> introductory paragraph, however.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>=20
> Thanks to everyone who worked on updating this protocol to reflect =
experience
> gathered from the initial CT protocol. I have one blocking comment, =
and a small
> number of editorial suggestions.
>=20
> =
--------------------------------------------------------------------------=
-
>=20
> =C2=A75:
>=20
> >  Clients are configured with a base URL for a log and construct URLs
> >  for requests by appending suffixes to this base URL.  This =
structure
> >  places some degree of restriction on how log operators can deploy
> >  these services, as noted in [RFC7320].  However, operational
> >  experience with version 1 of this protocol has not indicated that
> >  these restrictions are a problem in practice.
>=20
> The synthesis of URLs by a protocol in this fashion is prohibited by =
BCP 190:
>=20
>    Scheme definitions define the presence, format, and semantics of a
>    path component in URIs; all other specifications MUST NOT =
constrain,
>    or define the structure or the semantics for any path component.
>=20
> Unless the intention of this document is to update BCP 190 to change =
this
> normative requirement, we can't publish it in its current form. Note =
that doing
> so would require a change of venue, as updates to BCP 190 would not be =
covered
> by the current TRANS charter.
>=20
> Please see BCP 190 section 3 for alternate approaches. All three =
approaches
> could be made to work for CT, and I would be happy to explain how to =
do so if
> clarification is desired.
>=20
> While I agree that this is forbidden by BCP 190, this structure is =
inherited from
> RFC 6962, which predated 7320, so making that change seems like it's =
going
> to be fairly disruptive. This seems like it is falling into our =
discussion the other
> day about what must be changed in -bis documents.
>=20
> -Ekr
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> =C2=A71.1:
>=20
> >  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> >  "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in =
this
> >  document are to be interpreted as described in [RFC2119].
>=20
> Consider using the boilerplate from RFC 8174.
>=20
> =
--------------------------------------------------------------------------=
-
>=20
> =C2=A71.3:
>=20
> >  This document revises and obsoletes the experimental CT 1.0 =
[RFC6962]
> >  protocol, drawing on insights gained from CT 1.0 deployments and on
> >  feedback from the community.
>=20
> Given that *this* document is also experimental, it seems a bit odd to =
call out
> RFC 6962 as experimental.
>=20
> =
--------------------------------------------------------------------------=
-
>=20
> =C2=A72.1.1:
>=20
> >  We have established a registry of acceptable hash algorithms (see
>=20
> The use of first person here is awkward. Consider: "This document
> establishes..."
>=20
> =
--------------------------------------------------------------------------=
-
>=20
> =C2=A710.2:
>=20
> >  | 0x01 - | Unassigned |                        | Specification      =
|
> >  | 0xDF   |            |                        | Required and       =
|
> >  |        |            |                        | Expert Review      =
|
>=20
> The policy being cited here is confusing. It is unclear whether the =
intention is
> that values can be registered under both =C2=A74.5 and =C2=A74.6 of =
RFC 8126. I suspect
> the intention here is the policy specified in RFC 8126 =C2=A74.6 only, =
without
> reference to the policy in =C2=A74.5. If so, please use the formal =
name
> "Specification Required."
>=20
> =
--------------------------------------------------------------------------=
-
>=20
> =C2=A710.4:
>=20
> >  | 0x0008 -    | Unassigned           | Specification Required and   =
|
> >  | 0xDFFF      |                      | Expert Review                =
|
>=20
> Same comment as above.
>=20
> =
--------------------------------------------------------------------------=
-
>=20
> =C2=A710.5:
>=20
> >  | 0x0000 -      | Unassigned | n/a | Specification Required and     =
|
> >  | 0xDFFF        |            |     | Expert Review                  =
|
>=20
> Same comment as above.
>=20
>=20


From nobody Wed Mar 13 07:45:03 2019
Return-Path: <ekr@rtfm.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 21C8112788F for <trans@ietfa.amsl.com>; Wed, 13 Mar 2019 07:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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=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 UPiQTyku4woh for <trans@ietfa.amsl.com>; Wed, 13 Mar 2019 07:44:55 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 C11311279AD for <trans@ietf.org>; Wed, 13 Mar 2019 07:44:50 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id a17so1826176ljd.4 for <trans@ietf.org>; Wed, 13 Mar 2019 07:44:50 -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=mbpm5YYMEBrh0jYdKjkWk2oFTb2RBBAuLVFj0MaI0PI=; b=0SMkji1ZO9rp+LQLHhLQwpaJDD4I1EahcQC0+NWC/uYhv8Ekg3cvPKUAQb+7erY6xD PpgXd3MqhXVKyoHAceUqbn0Uc6xoc9lYj1cy13u9zDd/eopwCfs8eMHrDeSSTcSECCmZ fEl4Pp2UJ7CKAz2Sb0SyrrarZ6mROwjT7A6Xlqv2E3jjtGml2zhCbl9aQlcMiu55SfB9 y5MuJvDp9MEIsRflQYK2sH9sKKsa8goxy10f8ycujnAqNE4lp7dQ8K1Ezyv8h8+HPH0H hpYNqeJHZe0wDROU+/y9ndO41Dz15cKqMr1FuY3Kxba7FHBliZYWenHcP9VaOxQxPSgx u57A==
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=mbpm5YYMEBrh0jYdKjkWk2oFTb2RBBAuLVFj0MaI0PI=; b=bqluw9YXGHHfisiEHaNv7Ui84TslfirUoRIkfCuefOAs5hMTwkpDe8SAAB/FiPWhJr A9EWZAzDVH2Takl8z3KQjgGQgFLC6RbysZXN4J55YTI9bo5mWsJpvV+YZ7acbAoNVs9M 36gZ8FeBo0IQzBhdVQbSQErWQvlsLnRyteT7eVOOXm7dve3c3bBbq6/3xYxtGOrP6bQM QzDjUu5NXLYpboYqLLMaiFkuw/fflBiAGbc4I7khT3ZKAitzSr0e6tG2rlqONf588YVL j77peo+S8kbhaT6IwO4vgabc49Qs6YOWxgB9uihF1AtYBcdGPIzDIGVlaJo5vfzpdjBp 19Sw==
X-Gm-Message-State: APjAAAVPecm8KWMInq40lV0nv3FPjRkeE+co2ozUc2YrP/VkhuHfBmXa 8F+pPxx2UXOBru9igz6iWTpBGQt5PugTR3o9TLso7Q==
X-Google-Smtp-Source: APXvYqwSECf9YcXWzwbDuZwnejEvtca7njBvm/brmtBH1bL315TcG8xBjiPzoXATgb7nph0NXPv7mEDU84KnFOOQT/A=
X-Received: by 2002:a2e:3c19:: with SMTP id j25mr23603741lja.72.1552488288779;  Wed, 13 Mar 2019 07:44:48 -0700 (PDT)
MIME-Version: 1.0
References: <155245900142.5466.15600148045977298644.idtracker@ietfa.amsl.com> <CABcZeBNMt8y7EoFr3PXR84zPgvssp5=B2x7-7sQOb4wM_94RGg@mail.gmail.com> <7017B332-62F8-47BC-94EE-02ABDB7C1B14@kuehlewind.net>
In-Reply-To: <7017B332-62F8-47BC-94EE-02ABDB7C1B14@kuehlewind.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 13 Mar 2019 07:44:12 -0700
Message-ID: <CABcZeBMU3MnqLcnMqrRvEAtTA5frNd4=8CWkXYbPPg2tVRdBjw@mail.gmail.com>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
Cc: Adam Roach via Datatracker <noreply@ietf.org>, draft-ietf-trans-rfc6962-bis@ietf.org,  Paul Wouters <paul@nohats.ca>, Trans <trans@ietf.org>, The IESG <iesg@ietf.org>, trans-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f893910583fad8b8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/ceKexkniQ73fkjYd3oHlg7b6wHA>
Subject: Re: [Trans] Adam Roach's Discuss on draft-ietf-trans-rfc6962-bis-31: (with DISCUSS and COMMENT)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Mar 2019 14:44:57 -0000

--000000000000f893910583fad8b8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 13, 2019 at 7:19 AM Mirja Kuehlewind <ietf@kuehlewind.net>
wrote:

> HI Ekr,
>
> I actually have a related question. As this document is rather specifying
> a new version than =E2=80=9Cjust=E2=80=9D correcting an existing spec, it=
=E2=80=99s not really
> clear to me if the obsolete tag is the right choice here. I know some oth=
er
> protocols do this in a similar fashion, but I would rather recommend to
> only update the previous version RFC (in order to create a link to this n=
ew
> spec) or declare it historic if usage is not recommended anymore. I think
> that's also something we should discuss on the IESG.
>

First let me say that I find these tags mostly useless and not worth the
energy that seems to go into maintaining them. With that said, I think
"this is a new version of this protocol and you should stop using the old
and and start using this one" is a pretty clear case for Obsoletes. And the
question of whether that's the intended sementic is a clear WG decision.
So, if the IESG wants people to follow a different practice, it really
needs to publish explicit guidance.



> Coming back to your original question about how much should be changed in
> a bis document. I think this is a valid question for bis doc that correct
> known errors. However, in case of this document that specifies a new
> version, I think it is the right thing to do to also align such a new
> version with the guidelines we follow at the time of publication.
>

Hmm... This does not seem like the policy we have been applying so far. I'd
be interested to see an IETF statement on this matter.

-Ekr


> Mirja
>
>
> > On 13. Mar 2019, at 14:28, Eric Rescorla <ekr@rtfm.com> wrote:
> >
> >
> >
> > On Tue, Mar 12, 2019 at 11:36 PM Adam Roach via Datatracker
> <noreply@ietf..org> wrote:
> > Adam Roach has entered the following ballot position for
> > draft-ietf-trans-rfc6962-bis-31: Discuss
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to
> https://www.ietf.org/iesg/statement/discuss-criteria.html
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/
> >
> >
> >
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> >
> > Thanks to everyone who worked on updating this protocol to reflect
> experience
> > gathered from the initial CT protocol. I have one blocking comment, and
> a small
> > number of editorial suggestions.
> >
> >
> -------------------------------------------------------------------------=
--
> >
> > =C2=A75:
> >
> > >  Clients are configured with a base URL for a log and construct URLs
> > >  for requests by appending suffixes to this base URL.  This structure
> > >  places some degree of restriction on how log operators can deploy
> > >  these services, as noted in [RFC7320].  However, operational
> > >  experience with version 1 of this protocol has not indicated that
> > >  these restrictions are a problem in practice.
> >
> > The synthesis of URLs by a protocol in this fashion is prohibited by BC=
P
> 190:
> >
> >    Scheme definitions define the presence, format, and semantics of a
> >    path component in URIs; all other specifications MUST NOT constrain,
> >    or define the structure or the semantics for any path component.
> >
> > Unless the intention of this document is to update BCP 190 to change th=
is
> > normative requirement, we can't publish it in its current form. Note
> that doing
> > so would require a change of venue, as updates to BCP 190 would not be
> covered
> > by the current TRANS charter.
> >
> > Please see BCP 190 section 3 for alternate approaches. All three
> approaches
> > could be made to work for CT, and I would be happy to explain how to do
> so if
> > clarification is desired.
> >
> > While I agree that this is forbidden by BCP 190, this structure is
> inherited from
> > RFC 6962, which predated 7320, so making that change seems like it's
> going
> > to be fairly disruptive. This seems like it is falling into our
> discussion the other
> > day about what must be changed in -bis documents.
> >
> > -Ekr
> >
> >
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > =C2=A71.1:
> >
> > >  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> > >  "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> > >  document are to be interpreted as described in [RFC2119].
> >
> > Consider using the boilerplate from RFC 8174.
> >
> >
> -------------------------------------------------------------------------=
--
> >
> > =C2=A71.3:
> >
> > >  This document revises and obsoletes the experimental CT 1.0 [RFC6962=
]
> > >  protocol, drawing on insights gained from CT 1.0 deployments and on
> > >  feedback from the community.
> >
> > Given that *this* document is also experimental, it seems a bit odd to
> call out
> > RFC 6962 as experimental.
> >
> >
> -------------------------------------------------------------------------=
--
> >
> > =C2=A72.1.1:
> >
> > >  We have established a registry of acceptable hash algorithms (see
> >
> > The use of first person here is awkward. Consider: "This document
> > establishes..."
> >
> >
> -------------------------------------------------------------------------=
--
> >
> > =C2=A710.2:
> >
> > >  | 0x01 - | Unassigned |                        | Specification      =
|
> > >  | 0xDF   |            |                        | Required and       =
|
> > >  |        |            |                        | Expert Review      =
|
> >
> > The policy being cited here is confusing. It is unclear whether the
> intention is
> > that values can be registered under both =C2=A74.5 and =C2=A74.6 of RFC=
 8126. I
> suspect
> > the intention here is the policy specified in RFC 8126 =C2=A74.6 only, =
without
> > reference to the policy in =C2=A74.5. If so, please use the formal name
> > "Specification Required."
> >
> >
> -------------------------------------------------------------------------=
--
> >
> > =C2=A710.4:
> >
> > >  | 0x0008 -    | Unassigned           | Specification Required and   =
|
> > >  | 0xDFFF      |                      | Expert Review                =
|
> >
> > Same comment as above.
> >
> >
> -------------------------------------------------------------------------=
--
> >
> > =C2=A710.5:
> >
> > >  | 0x0000 -      | Unassigned | n/a | Specification Required and     =
|
> > >  | 0xDFFF        |            |     | Expert Review                  =
|
> >
> > Same comment as above.
> >
> >
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div dir=3D"ltr"><br></div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Ma=
r 13, 2019 at 7:19 AM Mirja Kuehlewind &lt;<a href=3D"mailto:ietf@kuehlewin=
d.net" target=3D"_blank">ietf@kuehlewind.net</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex">HI Ekr,<br>
<br>
I actually have a related question. As this document is rather specifying a=
 new version than =E2=80=9Cjust=E2=80=9D correcting an existing spec, it=E2=
=80=99s not really clear to me if the obsolete tag is the right choice here=
. I know some other protocols do this in a similar fashion, but I would rat=
her recommend to only update the previous version RFC (in order to create a=
 link to this new spec) or declare it historic if usage is not recommended =
anymore. I think that&#39;s also something we should discuss on the IESG.<b=
r></blockquote><div><br></div><div>First let me say that I find these tags =
mostly useless and not worth the energy that seems to go into maintaining t=
hem. With that said, I think &quot;this is a new version of this protocol a=
nd you should stop using the old and and start using this one&quot; is a pr=
etty clear case for Obsoletes. And the question of whether that&#39;s the i=
ntended sementic is a clear WG decision. So, if the IESG wants people to fo=
llow a different practice, it really needs to publish explicit guidance.<br=
></div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex">
Coming back to your original question about how much should be changed in a=
 bis document. I think this is a valid question for bis doc that correct kn=
own errors. However, in case of this document that specifies a new version,=
 I think it is the right thing to do to also align such a new version with =
the guidelines we follow at the time of publication.<br></blockquote><div><=
br></div><div>Hmm... This does not seem like the policy we have been applyi=
ng so far. I&#39;d be interested to see an IETF statement on this matter.<b=
r></div><div><br></div><div>-Ekr</div><div><br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">
<br>
Mirja<br>
<br>
<br>
&gt; On 13. Mar 2019, at 14:28, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtf=
m.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; On Tue, Mar 12, 2019 at 11:36 PM Adam Roach via Datatracker &lt;norepl=
y@ietf..org&gt; wrote:<br>
&gt; Adam Roach has entered the following ballot position for<br>
&gt; draft-ietf-trans-rfc6962-bis-31: Discuss<br>
&gt; <br>
&gt; When responding, please keep the subject line intact and reply to all<=
br>
&gt; email addresses included in the To and CC lines. (Feel free to cut thi=
s<br>
&gt; introductory paragraph, however.)<br>
&gt; <br>
&gt; <br>
&gt; Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss=
-criteria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/i=
esg/statement/discuss-criteria.html</a><br>
&gt; for more information about IESG DISCUSS and COMMENT positions.<br>
&gt; <br>
&gt; <br>
&gt; The document, along with other ballot positions, can be found here:<br=
>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-b=
is/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/=
draft-ietf-trans-rfc6962-bis/</a><br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
<br>
&gt; DISCUSS:<br>
&gt; ----------------------------------------------------------------------=
<br>
&gt; <br>
&gt; Thanks to everyone who worked on updating this protocol to reflect exp=
erience<br>
&gt; gathered from the initial CT protocol. I have one blocking comment, an=
d a small<br>
&gt; number of editorial suggestions.<br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
-----<br>
&gt; <br>
&gt; =C2=A75:<br>
&gt; <br>
&gt; &gt;=C2=A0 Clients are configured with a base URL for a log and constr=
uct URLs<br>
&gt; &gt;=C2=A0 for requests by appending suffixes to this base URL.=C2=A0 =
This structure<br>
&gt; &gt;=C2=A0 places some degree of restriction on how log operators can =
deploy<br>
&gt; &gt;=C2=A0 these services, as noted in [RFC7320].=C2=A0 However, opera=
tional<br>
&gt; &gt;=C2=A0 experience with version 1 of this protocol has not indicate=
d that<br>
&gt; &gt;=C2=A0 these restrictions are a problem in practice.<br>
&gt; <br>
&gt; The synthesis of URLs by a protocol in this fashion is prohibited by B=
CP 190:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 Scheme definitions define the presence, format, and seman=
tics of a<br>
&gt;=C2=A0 =C2=A0 path component in URIs; all other specifications MUST NOT=
 constrain,<br>
&gt;=C2=A0 =C2=A0 or define the structure or the semantics for any path com=
ponent.<br>
&gt; <br>
&gt; Unless the intention of this document is to update BCP 190 to change t=
his<br>
&gt; normative requirement, we can&#39;t publish it in its current form. No=
te that doing<br>
&gt; so would require a change of venue, as updates to BCP 190 would not be=
 covered<br>
&gt; by the current TRANS charter.<br>
&gt; <br>
&gt; Please see BCP 190 section 3 for alternate approaches. All three appro=
aches<br>
&gt; could be made to work for CT, and I would be happy to explain how to d=
o so if<br>
&gt; clarification is desired.<br>
&gt; <br>
&gt; While I agree that this is forbidden by BCP 190, this structure is inh=
erited from<br>
&gt; RFC 6962, which predated 7320, so making that change seems like it&#39=
;s going<br>
&gt; to be fairly disruptive. This seems like it is falling into our discus=
sion the other<br>
&gt; day about what must be changed in -bis documents.<br>
&gt; <br>
&gt; -Ekr<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
<br>
&gt; COMMENT:<br>
&gt; ----------------------------------------------------------------------=
<br>
&gt; <br>
&gt; =C2=A71.1:<br>
&gt; <br>
&gt; &gt;=C2=A0 The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot=
;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,<br>
&gt; &gt;=C2=A0 &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMEND=
ED&quot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this<br>
&gt; &gt;=C2=A0 document are to be interpreted as described in [RFC2119].<b=
r>
&gt; <br>
&gt; Consider using the boilerplate from RFC 8174.<br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
-----<br>
&gt; <br>
&gt; =C2=A71.3:<br>
&gt; <br>
&gt; &gt;=C2=A0 This document revises and obsoletes the experimental CT 1.0=
 [RFC6962]<br>
&gt; &gt;=C2=A0 protocol, drawing on insights gained from CT 1.0 deployment=
s and on<br>
&gt; &gt;=C2=A0 feedback from the community.<br>
&gt; <br>
&gt; Given that *this* document is also experimental, it seems a bit odd to=
 call out<br>
&gt; RFC 6962 as experimental.<br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
-----<br>
&gt; <br>
&gt; =C2=A72.1.1:<br>
&gt; <br>
&gt; &gt;=C2=A0 We have established a registry of acceptable hash algorithm=
s (see<br>
&gt; <br>
&gt; The use of first person here is awkward. Consider: &quot;This document=
<br>
&gt; establishes...&quot;<br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
-----<br>
&gt; <br>
&gt; =C2=A710.2:<br>
&gt; <br>
&gt; &gt;=C2=A0 | 0x01 - | Unassigned |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Specification=C2=A0 =C2=
=A0 =C2=A0 |<br>
&gt; &gt;=C2=A0 | 0xDF=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 | Required and=C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt; &gt;=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 | Expert Review=C2=A0 =C2=A0 =C2=A0 |<br>
&gt; <br>
&gt; The policy being cited here is confusing. It is unclear whether the in=
tention is<br>
&gt; that values can be registered under both =C2=A74.5 and =C2=A74.6 of RF=
C 8126. I suspect<br>
&gt; the intention here is the policy specified in RFC 8126 =C2=A74.6 only,=
 without<br>
&gt; reference to the policy in =C2=A74.5. If so, please use the formal nam=
e<br>
&gt; &quot;Specification Required.&quot;<br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
-----<br>
&gt; <br>
&gt; =C2=A710.4:<br>
&gt; <br>
&gt; &gt;=C2=A0 | 0x0008 -=C2=A0 =C2=A0 | Unassigned=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0| Specification Required and=C2=A0 =C2=A0|<br>
&gt; &gt;=C2=A0 | 0xDFFF=C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Expert Review=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt; <br>
&gt; Same comment as above.<br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
-----<br>
&gt; <br>
&gt; =C2=A710.5:<br>
&gt; <br>
&gt; &gt;=C2=A0 | 0x0000 -=C2=A0 =C2=A0 =C2=A0 | Unassigned | n/a | Specifi=
cation Required and=C2=A0 =C2=A0 =C2=A0|<br>
&gt; &gt;=C2=A0 | 0xDFFF=C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0| Expert Review=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt; <br>
&gt; Same comment as above.<br>
&gt; <br>
&gt; <br>
<br>
</blockquote></div></div>

--000000000000f893910583fad8b8--


From nobody Wed Mar 13 07:46:15 2019
Return-Path: <rlb@ipv.sx>
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 B2603127133 for <trans@ietfa.amsl.com>; Wed, 13 Mar 2019 07:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.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 rZkfBTJlPUEl for <trans@ietfa.amsl.com>; Wed, 13 Mar 2019 07:46:11 -0700 (PDT)
Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::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 AC30E12D7EA for <trans@ietf.org>; Wed, 13 Mar 2019 07:46:05 -0700 (PDT)
Received: by mail-oi1-x22a.google.com with SMTP id u128so1630900oie.2 for <trans@ietf.org>; Wed, 13 Mar 2019 07:46:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XpV1Scjqvd8CCB6uhdN3T1JHiB/Gh/1ySi9FN95F4z0=; b=q1hWuIX9m7TX1sECMrzWll9FpsGiScse8Ag3g9J00XUBdgz1ClZN9489UNnTdwdqZo GBsbMXQq+UsFD4OPEiYH0EsRefxsF9kacK1wsht6cj99sGlTPcEjaNke7jp0LZdHNWWR Pf0XgWc6QsR17+g+GpM3p7+47VNqNRqGpgA/awxqSSpERYkTXxPb074NZ+KiomByaFMS 56zHDoPcb85bQzsle/k8zYiL4HtWsFcutOjINLwCe/SnkoEhHRE6L4kfZK/PER/K+6TE 9DxXPd+TNry3fXB2QQLD+23J/U/u7Kt+bUTA8r4biqCK+/Ela1Cw41E8mvQrA/5KWKf0 JnyA==
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=XpV1Scjqvd8CCB6uhdN3T1JHiB/Gh/1ySi9FN95F4z0=; b=TjPo2/vSi8t8wPSQuhkVjAVwtiNov+4OSOLrGm18RA4oOKIFqeaN3zsKd42qh1YZ5s APW3YDQthsxvK4zdVfY2dcdsuSzL2HaE3MREPCvuFuvTiekmT1lNPr6UIRbLUYPCs1UY hwKk8/ZwUA68vGk02fXQQwQZOWywKTHLmuEF/tOflXyUzGKmqZOMYSjGsNHsQ2hW10eb jtiaLyn0Qo8S+jT/KzbpZFfjKhQnMq5du8IqeolG1FQInaetKC1K3ohqmKJh45OWHeMK uTYTlydjyHFrEnOO7bcBO2Eery9LChCmaz7cWoDMz0AKWPMFlRS5i4KtDqVE1+Ez+GtD /6zw==
X-Gm-Message-State: APjAAAUZED7CaffQIrR8lsI5FWiPci+XWKBD0ZdI3g51NtPXFeA39Umi HKr54gSG1sQlPb9cCKF3LLeuGHK04MXj59d42PZLFg==
X-Google-Smtp-Source: APXvYqz7M5GfFG6HdnWMm7YfHtxxpiuVr4O4qvlE7WoFwPTE/ALwxBWzsMDG4jS18LgPrDH8oa0LtidY30zRAofqFMM=
X-Received: by 2002:aca:3687:: with SMTP id d129mr1826406oia.51.1552488364738;  Wed, 13 Mar 2019 07:46:04 -0700 (PDT)
MIME-Version: 1.0
References: <155245900142.5466.15600148045977298644.idtracker@ietfa.amsl.com> <CABcZeBNMt8y7EoFr3PXR84zPgvssp5=B2x7-7sQOb4wM_94RGg@mail.gmail.com> <7017B332-62F8-47BC-94EE-02ABDB7C1B14@kuehlewind.net>
In-Reply-To: <7017B332-62F8-47BC-94EE-02ABDB7C1B14@kuehlewind.net>
From: Richard Barnes <rlb@ipv.sx>
Date: Wed, 13 Mar 2019 10:45:35 -0400
Message-ID: <CAL02cgRHDyrWfii6NwwShVsD+T0-BQhiakzjmx0zTDJKWwYV7w@mail.gmail.com>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
Cc: Eric Rescorla <ekr@rtfm.com>, trans-chairs@ietf.org, Trans <trans@ietf.org>, Adam Roach via Datatracker <noreply@ietf.org>, draft-ietf-trans-rfc6962-bis@ietf.org,  The IESG <iesg@ietf.org>, Paul Wouters <paul@nohats.ca>
Content-Type: multipart/alternative; boundary="0000000000007fad7b0583fadd59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/jE6yndGOqZrfybwXXLsAz77pK64>
Subject: Re: [Trans] Adam Roach's Discuss on draft-ietf-trans-rfc6962-bis-31: (with DISCUSS and COMMENT)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Mar 2019 14:46:14 -0000

--0000000000007fad7b0583fadd59
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 13, 2019 at 10:19 AM Mirja Kuehlewind <ietf@kuehlewind.net>
wrote:

> HI Ekr,
>
> I actually have a related question. As this document is rather specifying
> a new version than =E2=80=9Cjust=E2=80=9D correcting an existing spec, it=
=E2=80=99s not really
> clear to me if the obsolete tag is the right choice here. I know some oth=
er
> protocols do this in a similar fashion, but I would rather recommend to
> only update the previous version RFC (in order to create a link to this n=
ew
> spec) or declare it historic if usage is not recommended anymore. I think
> that's also something we should discuss on the IESG.
>

Strongly disagree with this reasoning.  Much like with TLS 1.2 -> 1.3, we
want people to deploy the new version, not the old version.  The tool we
have to communicate "Don't use this old version" is "Obsoletes".

--Richard



>
> Coming back to your original question about how much should be changed in
> a bis document. I think this is a valid question for bis doc that correct
> known errors. However, in case of this document that specifies a new
> version, I think it is the right thing to do to also align such a new
> version with the guidelines we follow at the time of publication.
>
> Mirja
>
>
> > On 13. Mar 2019, at 14:28, Eric Rescorla <ekr@rtfm.com> wrote:
> >
> >
> >
> > On Tue, Mar 12, 2019 at 11:36 PM Adam Roach via Datatracker
> <noreply@ietf..org> wrote:
> > Adam Roach has entered the following ballot position for
> > draft-ietf-trans-rfc6962-bis-31: Discuss
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to
> https://www.ietf.org/iesg/statement/discuss-criteria.html
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/
> >
> >
> >
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> >
> > Thanks to everyone who worked on updating this protocol to reflect
> experience
> > gathered from the initial CT protocol. I have one blocking comment, and
> a small
> > number of editorial suggestions.
> >
> >
> -------------------------------------------------------------------------=
--
> >
> > =C2=A75:
> >
> > >  Clients are configured with a base URL for a log and construct URLs
> > >  for requests by appending suffixes to this base URL.  This structure
> > >  places some degree of restriction on how log operators can deploy
> > >  these services, as noted in [RFC7320].  However, operational
> > >  experience with version 1 of this protocol has not indicated that
> > >  these restrictions are a problem in practice.
> >
> > The synthesis of URLs by a protocol in this fashion is prohibited by BC=
P
> 190:
> >
> >    Scheme definitions define the presence, format, and semantics of a
> >    path component in URIs; all other specifications MUST NOT constrain,
> >    or define the structure or the semantics for any path component.
> >
> > Unless the intention of this document is to update BCP 190 to change th=
is
> > normative requirement, we can't publish it in its current form. Note
> that doing
> > so would require a change of venue, as updates to BCP 190 would not be
> covered
> > by the current TRANS charter.
> >
> > Please see BCP 190 section 3 for alternate approaches. All three
> approaches
> > could be made to work for CT, and I would be happy to explain how to do
> so if
> > clarification is desired.
> >
> > While I agree that this is forbidden by BCP 190, this structure is
> inherited from
> > RFC 6962, which predated 7320, so making that change seems like it's
> going
> > to be fairly disruptive. This seems like it is falling into our
> discussion the other
> > day about what must be changed in -bis documents.
> >
> > -Ekr
> >
> >
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > =C2=A71.1:
> >
> > >  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> > >  "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> > >  document are to be interpreted as described in [RFC2119].
> >
> > Consider using the boilerplate from RFC 8174.
> >
> >
> -------------------------------------------------------------------------=
--
> >
> > =C2=A71.3:
> >
> > >  This document revises and obsoletes the experimental CT 1.0 [RFC6962=
]
> > >  protocol, drawing on insights gained from CT 1.0 deployments and on
> > >  feedback from the community.
> >
> > Given that *this* document is also experimental, it seems a bit odd to
> call out
> > RFC 6962 as experimental.
> >
> >
> -------------------------------------------------------------------------=
--
> >
> > =C2=A72.1.1:
> >
> > >  We have established a registry of acceptable hash algorithms (see
> >
> > The use of first person here is awkward. Consider: "This document
> > establishes..."
> >
> >
> -------------------------------------------------------------------------=
--
> >
> > =C2=A710.2:
> >
> > >  | 0x01 - | Unassigned |                        | Specification      =
|
> > >  | 0xDF   |            |                        | Required and       =
|
> > >  |        |            |                        | Expert Review      =
|
> >
> > The policy being cited here is confusing. It is unclear whether the
> intention is
> > that values can be registered under both =C2=A74.5 and =C2=A74.6 of RFC=
 8126. I
> suspect
> > the intention here is the policy specified in RFC 8126 =C2=A74.6 only, =
without
> > reference to the policy in =C2=A74.5. If so, please use the formal name
> > "Specification Required."
> >
> >
> -------------------------------------------------------------------------=
--
> >
> > =C2=A710.4:
> >
> > >  | 0x0008 -    | Unassigned           | Specification Required and   =
|
> > >  | 0xDFFF      |                      | Expert Review                =
|
> >
> > Same comment as above.
> >
> >
> -------------------------------------------------------------------------=
--
> >
> > =C2=A710.5:
> >
> > >  | 0x0000 -      | Unassigned | n/a | Specification Required and     =
|
> > >  | 0xDFFF        |            |     | Expert Review                  =
|
> >
> > Same comment as above.
> >
> >
>
> _______________________________________________
> Trans mailing list
> Trans@ietf.org
> https://www.ietf.org/mailman/listinfo/trans
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Mar 13, 2019 at 10:19 AM Mirj=
a Kuehlewind &lt;<a href=3D"mailto:ietf@kuehlewind.net">ietf@kuehlewind.net=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
HI Ekr,<br>
<br>
I actually have a related question. As this document is rather specifying a=
 new version than =E2=80=9Cjust=E2=80=9D correcting an existing spec, it=E2=
=80=99s not really clear to me if the obsolete tag is the right choice here=
. I know some other protocols do this in a similar fashion, but I would rat=
her recommend to only update the previous version RFC (in order to create a=
 link to this new spec) or declare it historic if usage is not recommended =
anymore. I think that&#39;s also something we should discuss on the IESG.<b=
r></blockquote><div><br></div><div>Strongly disagree with this reasoning.=
=C2=A0 Much like with TLS 1.2 -&gt; 1.3, we want people to deploy the new v=
ersion, not the old version.=C2=A0 The tool we have to communicate &quot;Do=
n&#39;t use this old version&quot; is &quot;Obsoletes&quot;.</div><div><br>=
</div><div>--Richard<br></div><div><br></div><div>=C2=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">
<br>
Coming back to your original question about how much should be changed in a=
 bis document. I think this is a valid question for bis doc that correct kn=
own errors. However, in case of this document that specifies a new version,=
 I think it is the right thing to do to also align such a new version with =
the guidelines we follow at the time of publication.<br>
<br>
Mirja<br>
<br>
<br>
&gt; On 13. Mar 2019, at 14:28, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtf=
m.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; On Tue, Mar 12, 2019 at 11:36 PM Adam Roach via Datatracker &lt;norepl=
y@ietf..org&gt; wrote:<br>
&gt; Adam Roach has entered the following ballot position for<br>
&gt; draft-ietf-trans-rfc6962-bis-31: Discuss<br>
&gt; <br>
&gt; When responding, please keep the subject line intact and reply to all<=
br>
&gt; email addresses included in the To and CC lines. (Feel free to cut thi=
s<br>
&gt; introductory paragraph, however.)<br>
&gt; <br>
&gt; <br>
&gt; Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss=
-criteria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/i=
esg/statement/discuss-criteria.html</a><br>
&gt; for more information about IESG DISCUSS and COMMENT positions.<br>
&gt; <br>
&gt; <br>
&gt; The document, along with other ballot positions, can be found here:<br=
>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-b=
is/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/=
draft-ietf-trans-rfc6962-bis/</a><br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
<br>
&gt; DISCUSS:<br>
&gt; ----------------------------------------------------------------------=
<br>
&gt; <br>
&gt; Thanks to everyone who worked on updating this protocol to reflect exp=
erience<br>
&gt; gathered from the initial CT protocol. I have one blocking comment, an=
d a small<br>
&gt; number of editorial suggestions.<br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
-----<br>
&gt; <br>
&gt; =C2=A75:<br>
&gt; <br>
&gt; &gt;=C2=A0 Clients are configured with a base URL for a log and constr=
uct URLs<br>
&gt; &gt;=C2=A0 for requests by appending suffixes to this base URL.=C2=A0 =
This structure<br>
&gt; &gt;=C2=A0 places some degree of restriction on how log operators can =
deploy<br>
&gt; &gt;=C2=A0 these services, as noted in [RFC7320].=C2=A0 However, opera=
tional<br>
&gt; &gt;=C2=A0 experience with version 1 of this protocol has not indicate=
d that<br>
&gt; &gt;=C2=A0 these restrictions are a problem in practice.<br>
&gt; <br>
&gt; The synthesis of URLs by a protocol in this fashion is prohibited by B=
CP 190:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 Scheme definitions define the presence, format, and seman=
tics of a<br>
&gt;=C2=A0 =C2=A0 path component in URIs; all other specifications MUST NOT=
 constrain,<br>
&gt;=C2=A0 =C2=A0 or define the structure or the semantics for any path com=
ponent.<br>
&gt; <br>
&gt; Unless the intention of this document is to update BCP 190 to change t=
his<br>
&gt; normative requirement, we can&#39;t publish it in its current form. No=
te that doing<br>
&gt; so would require a change of venue, as updates to BCP 190 would not be=
 covered<br>
&gt; by the current TRANS charter.<br>
&gt; <br>
&gt; Please see BCP 190 section 3 for alternate approaches. All three appro=
aches<br>
&gt; could be made to work for CT, and I would be happy to explain how to d=
o so if<br>
&gt; clarification is desired.<br>
&gt; <br>
&gt; While I agree that this is forbidden by BCP 190, this structure is inh=
erited from<br>
&gt; RFC 6962, which predated 7320, so making that change seems like it&#39=
;s going<br>
&gt; to be fairly disruptive. This seems like it is falling into our discus=
sion the other<br>
&gt; day about what must be changed in -bis documents.<br>
&gt; <br>
&gt; -Ekr<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
<br>
&gt; COMMENT:<br>
&gt; ----------------------------------------------------------------------=
<br>
&gt; <br>
&gt; =C2=A71.1:<br>
&gt; <br>
&gt; &gt;=C2=A0 The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot=
;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,<br>
&gt; &gt;=C2=A0 &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMEND=
ED&quot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this<br>
&gt; &gt;=C2=A0 document are to be interpreted as described in [RFC2119].<b=
r>
&gt; <br>
&gt; Consider using the boilerplate from RFC 8174.<br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
-----<br>
&gt; <br>
&gt; =C2=A71.3:<br>
&gt; <br>
&gt; &gt;=C2=A0 This document revises and obsoletes the experimental CT 1.0=
 [RFC6962]<br>
&gt; &gt;=C2=A0 protocol, drawing on insights gained from CT 1.0 deployment=
s and on<br>
&gt; &gt;=C2=A0 feedback from the community.<br>
&gt; <br>
&gt; Given that *this* document is also experimental, it seems a bit odd to=
 call out<br>
&gt; RFC 6962 as experimental.<br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
-----<br>
&gt; <br>
&gt; =C2=A72.1.1:<br>
&gt; <br>
&gt; &gt;=C2=A0 We have established a registry of acceptable hash algorithm=
s (see<br>
&gt; <br>
&gt; The use of first person here is awkward. Consider: &quot;This document=
<br>
&gt; establishes...&quot;<br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
-----<br>
&gt; <br>
&gt; =C2=A710.2:<br>
&gt; <br>
&gt; &gt;=C2=A0 | 0x01 - | Unassigned |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Specification=C2=A0 =C2=
=A0 =C2=A0 |<br>
&gt; &gt;=C2=A0 | 0xDF=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 | Required and=C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt; &gt;=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 | Expert Review=C2=A0 =C2=A0 =C2=A0 |<br>
&gt; <br>
&gt; The policy being cited here is confusing. It is unclear whether the in=
tention is<br>
&gt; that values can be registered under both =C2=A74.5 and =C2=A74.6 of RF=
C 8126. I suspect<br>
&gt; the intention here is the policy specified in RFC 8126 =C2=A74.6 only,=
 without<br>
&gt; reference to the policy in =C2=A74.5. If so, please use the formal nam=
e<br>
&gt; &quot;Specification Required.&quot;<br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
-----<br>
&gt; <br>
&gt; =C2=A710.4:<br>
&gt; <br>
&gt; &gt;=C2=A0 | 0x0008 -=C2=A0 =C2=A0 | Unassigned=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0| Specification Required and=C2=A0 =C2=A0|<br>
&gt; &gt;=C2=A0 | 0xDFFF=C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Expert Review=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt; <br>
&gt; Same comment as above.<br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
-----<br>
&gt; <br>
&gt; =C2=A710.5:<br>
&gt; <br>
&gt; &gt;=C2=A0 | 0x0000 -=C2=A0 =C2=A0 =C2=A0 | Unassigned | n/a | Specifi=
cation Required and=C2=A0 =C2=A0 =C2=A0|<br>
&gt; &gt;=C2=A0 | 0xDFFF=C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0| Expert Review=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt; <br>
&gt; Same comment as above.<br>
&gt; <br>
&gt; <br>
<br>
_______________________________________________<br>
Trans mailing list<br>
<a href=3D"mailto:Trans@ietf.org" target=3D"_blank">Trans@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/trans" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/trans</a><br>
</blockquote></div></div>

--0000000000007fad7b0583fadd59--


From nobody Wed Mar 13 07:53:44 2019
Return-Path: <alissa@cooperw.in>
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 583531277D6; Wed, 13 Mar 2019 07:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=cooperw.in header.b=pB/JRXIo; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=1vRrvb43
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 MmdsImqC8VMe; Wed, 13 Mar 2019 07:53:32 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E2521277D2; Wed, 13 Mar 2019 07:53:32 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 7E0122553D; Wed, 13 Mar 2019 10:53:31 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Wed, 13 Mar 2019 10:53:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=z +/RUVzuKxnPW6V0vHCWvwe+E/QEsO+2mo5ANFypf94=; b=pB/JRXIoIzolqKEXV RdvfVtIp90XkQWH8cEBjSi/YAUkIFmXlyAZbSOmucj+VipW+/1Rph9kJqtwq/xrv DXhMv2AYSO5jyX4+++72sn0FgVndxGRShQTd4rwfoYOslZwz0j56RZwpfnj1QuoP ZkwRhYvyxJVwhLtLeKlFZL7DaPKxlRjKNO0ILAIOH8lYAGWQnUdoGwQthCImRv3g 83Mg0R/VyH/KSpQz62ERx741XLtWx9xfzNI71C8qhia+dXnQg2wubAAGxWvt6MFp rWOjWbxVsS0gYMcye/crPwoVoDqILnacOD3gXJjKA5lBJ4fC5la8Ei/xQIUEbRru ZmlCw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=z+/RUVzuKxnPW6V0vHCWvwe+E/QEsO+2mo5ANFypf 94=; b=1vRrvb43O3lTS+0AD3xWU715gSgrM44wEJu07ArDNx5isMOgatbsVdLwE XRB0L/bMGkeU70rV4PPYAu43MD1+mJp81DTXul9tfrsjYFNHr1fvSSKZ4+0fMgy+ me4J2gCmV7CK23/T5s53OnNDF7BEbDNhMv7SbXnS28+IR79afJrjIEkpwOT3KXXl 5JtHHVxdB5dT08596nEMv4PMt9XUkw3URdzyRYDmEBJqbK8xtz4pD4q7Jngz4AnZ RV6njCvkb5TvKpCcNKveBXcJn4KvCusVZU24w99RKlWj9sc5lz2jLrD5YRo1yy9I 6JqEeBX7G5PUeQNBP42+O5Rhz5eQg==
X-ME-Sender: <xms:ahmJXCEctYYC0Jzh8OzK04oxkt-J2o8RHgTxibfI4E3z11ogiBWI6Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrhedtgdeilecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrih hnpehivghtfhdrohhrghenucfkphepudejfedrfeekrdduudejrdeiheenucfrrghrrghm pehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhushhtvg hrufhiiigvpedt
X-ME-Proxy: <xmx:ahmJXK8YhpbZTO0sX_wwI_qxfb9ISwrhCnAo8mAA1paUiSBLu8AUFA> <xmx:ahmJXMXDYipCcvUtPoR1Nf-k5FRb44A3Jj5IYaUZUxRagORj0Cmxlw> <xmx:ahmJXEE-Tn7A-Uhzjma5W1-ig4P7uP-RfjSj3vVdtsDBnUMwVf9qow> <xmx:axmJXOMXeR73q7m0aKeWhbnfI5k1aknsPK7X6MjvQ8A0hLC6xlC2qg>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.65]) by mail.messagingengine.com (Postfix) with ESMTPA id D22BB10345; Wed, 13 Mar 2019 10:53:29 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <7017B332-62F8-47BC-94EE-02ABDB7C1B14@kuehlewind.net>
Date: Wed, 13 Mar 2019 10:53:28 -0400
Cc: Eric Rescorla <ekr@rtfm.com>, trans-chairs@ietf.org, Trans <trans@ietf.org>, Adam Roach via Datatracker <noreply@ietf.org>, draft-ietf-trans-rfc6962-bis@ietf.org, IESG <iesg@ietf.org>, Paul Wouters <paul@nohats.ca>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4D3DEA6C-7526-4045-AA5E-AC7039CA04F4@cooperw.in>
References: <155245900142.5466.15600148045977298644.idtracker@ietfa.amsl.com> <CABcZeBNMt8y7EoFr3PXR84zPgvssp5=B2x7-7sQOb4wM_94RGg@mail.gmail.com> <7017B332-62F8-47BC-94EE-02ABDB7C1B14@kuehlewind.net>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/HLPqGYyxVssWnEccw_d_12WMuJQ>
Subject: Re: [Trans] Adam Roach's Discuss on draft-ietf-trans-rfc6962-bis-31: (with DISCUSS and COMMENT)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Mar 2019 14:53:35 -0000

Hi Mirja,

> On Mar 13, 2019, at 10:19 AM, Mirja Kuehlewind <ietf@kuehlewind.net> =
wrote:
>=20
> HI Ekr,
>=20
> I actually have a related question. As this document is rather =
specifying a new version than =E2=80=9Cjust=E2=80=9D correcting an =
existing spec, it=E2=80=99s not really clear to me if the obsolete tag =
is the right choice here. I know some other protocols do this in a =
similar fashion, but I would rather recommend to only update the =
previous version RFC (in order to create a link to this new spec) or =
declare it historic if usage is not recommended anymore. I think that's =
also something we should discuss on the IESG.

We have a statement that explains our current position: =
https://www.ietf.org/blog/iesg-statement-designating-rfcs-historic/

Alissa

>=20
> Coming back to your original question about how much should be changed =
in a bis document. I think this is a valid question for bis doc that =
correct known errors. However, in case of this document that specifies a =
new version, I think it is the right thing to do to also align such a =
new version with the guidelines we follow at the time of publication.
>=20
> Mirja
>=20
>=20
>> On 13. Mar 2019, at 14:28, Eric Rescorla <ekr@rtfm.com> wrote:
>>=20
>>=20
>>=20
>> On Tue, Mar 12, 2019 at 11:36 PM Adam Roach via Datatracker =
<noreply@ietf..org> wrote:
>> Adam Roach has entered the following ballot position for
>> draft-ietf-trans-rfc6962-bis-31: Discuss
>>=20
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut =
this
>> introductory paragraph, however.)
>>=20
>>=20
>> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> DISCUSS:
>> =
----------------------------------------------------------------------
>>=20
>> Thanks to everyone who worked on updating this protocol to reflect =
experience
>> gathered from the initial CT protocol. I have one blocking comment, =
and a small
>> number of editorial suggestions.
>>=20
>> =
--------------------------------------------------------------------------=
-
>>=20
>> =C2=A75:
>>=20
>>> Clients are configured with a base URL for a log and construct URLs
>>> for requests by appending suffixes to this base URL.  This structure
>>> places some degree of restriction on how log operators can deploy
>>> these services, as noted in [RFC7320].  However, operational
>>> experience with version 1 of this protocol has not indicated that
>>> these restrictions are a problem in practice.
>>=20
>> The synthesis of URLs by a protocol in this fashion is prohibited by =
BCP 190:
>>=20
>>   Scheme definitions define the presence, format, and semantics of a
>>   path component in URIs; all other specifications MUST NOT =
constrain,
>>   or define the structure or the semantics for any path component.
>>=20
>> Unless the intention of this document is to update BCP 190 to change =
this
>> normative requirement, we can't publish it in its current form. Note =
that doing
>> so would require a change of venue, as updates to BCP 190 would not =
be covered
>> by the current TRANS charter.
>>=20
>> Please see BCP 190 section 3 for alternate approaches. All three =
approaches
>> could be made to work for CT, and I would be happy to explain how to =
do so if
>> clarification is desired.
>>=20
>> While I agree that this is forbidden by BCP 190, this structure is =
inherited from
>> RFC 6962, which predated 7320, so making that change seems like it's =
going
>> to be fairly disruptive. This seems like it is falling into our =
discussion the other
>> day about what must be changed in -bis documents.
>>=20
>> -Ekr
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> =C2=A71.1:
>>=20
>>> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>>> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>>> document are to be interpreted as described in [RFC2119].
>>=20
>> Consider using the boilerplate from RFC 8174.
>>=20
>> =
--------------------------------------------------------------------------=
-
>>=20
>> =C2=A71.3:
>>=20
>>> This document revises and obsoletes the experimental CT 1.0 =
[RFC6962]
>>> protocol, drawing on insights gained from CT 1.0 deployments and on
>>> feedback from the community.
>>=20
>> Given that *this* document is also experimental, it seems a bit odd =
to call out
>> RFC 6962 as experimental.
>>=20
>> =
--------------------------------------------------------------------------=
-
>>=20
>> =C2=A72.1.1:
>>=20
>>> We have established a registry of acceptable hash algorithms (see
>>=20
>> The use of first person here is awkward. Consider: "This document
>> establishes..."
>>=20
>> =
--------------------------------------------------------------------------=
-
>>=20
>> =C2=A710.2:
>>=20
>>> | 0x01 - | Unassigned |                        | Specification      =
|
>>> | 0xDF   |            |                        | Required and       =
|
>>> |        |            |                        | Expert Review      =
|
>>=20
>> The policy being cited here is confusing. It is unclear whether the =
intention is
>> that values can be registered under both =C2=A74.5 and =C2=A74.6 of =
RFC 8126. I suspect
>> the intention here is the policy specified in RFC 8126 =C2=A74.6 =
only, without
>> reference to the policy in =C2=A74.5. If so, please use the formal =
name
>> "Specification Required."
>>=20
>> =
--------------------------------------------------------------------------=
-
>>=20
>> =C2=A710.4:
>>=20
>>> | 0x0008 -    | Unassigned           | Specification Required and   =
|
>>> | 0xDFFF      |                      | Expert Review                =
|
>>=20
>> Same comment as above.
>>=20
>> =
--------------------------------------------------------------------------=
-
>>=20
>> =C2=A710.5:
>>=20
>>> | 0x0000 -      | Unassigned | n/a | Specification Required and     =
|
>>> | 0xDFFF        |            |     | Expert Review                  =
|
>>=20
>> Same comment as above.
>>=20
>>=20
>=20


From nobody Wed Mar 13 08:51:43 2019
Return-Path: <ekr@rtfm.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 5B5B5130F1C for <trans@ietfa.amsl.com>; Wed, 13 Mar 2019 08:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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=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 eE0O-2EZvvvT for <trans@ietfa.amsl.com>; Wed, 13 Mar 2019 08:51:33 -0700 (PDT)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 C9EBA130F3C for <trans@ietf.org>; Wed, 13 Mar 2019 08:51:19 -0700 (PDT)
Received: by mail-lf1-x12c.google.com with SMTP id a132so412237lfa.13 for <trans@ietf.org>; Wed, 13 Mar 2019 08:51:19 -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=xIg5l1QTe/0IsXUeTcNcHE/zwo/jhWa2650ER8/ttJA=; b=UVNkk48YPqTN07nN2vcaCb7BMiI9ar/v78IqsKYp5bT1CW+4NBjrc6qXdByvjPkfbs DjAds/3BY19dAc4q1eZbRX5S7TZPbVintvTSs1hbByzWeJOsro7OdTYAq8jKiBGbh0k+ rMXJT4TaAfJfDlx06Smk66T2Wh/IAi2oxCCmegvRdvEOuYpY/PScJVTPOSnlacLnMz5R EWkELokVISc/5YbKFKX/qYw/UB/MngdAj1aaE/MOCS7ZiZMnHH6lGwcYwcu8xP7ukBeW m1DIh72I80NwOZC/JWiHu/0UCwM6HpGBkHvLN5UxyUvGA4bZIAic+8MyXQcumlbY9ijS +IQg==
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=xIg5l1QTe/0IsXUeTcNcHE/zwo/jhWa2650ER8/ttJA=; b=YoZxn2GMTa4kiAM7ZFgSPBeiSjAesfGEly4I/Ua4nyQeF16nifpaXzqDr5UN2U0ghB w1k17T0hVHZVWGIv+mvjfHuNwuHoCxvWsyAu8qvMNHKzptLvIJoKSc93C11QkARVKJpm IdP4Kmih0qIcZT2VSZsq2mioymdKmxpuSMi9cNLPViwx/CmvCCCwuuSsYMSG+gk+Irdz bJsk1XpI8ibt8qn5+GouFJzvQdH2+JZO2NyR8oa1zMk+uYOBwssXSbbXFsrrNk/bm04I LkH2tIkHXrrqNpMJcinKGKt5nSem9s/T0M/PP1BfA0kHDXkHaEyZSHRtt5fUF8q/CrUm OjmA==
X-Gm-Message-State: APjAAAWNfIuipuvPHJacw47iEdwVoVbWD0kzU5wEzV9ruiXhaS0dniow WtBNKwI0eSnif1RPMGCHuedXMQ4jjt5Bdy8j/xzcWA==
X-Google-Smtp-Source: APXvYqwT2J0GadLyNVGk6ExC6vRIWfzPYa35fN0KO5HqPUb5+ZWWrqVYgr2WKSJlX0kmQ1XsiGnJDnx8ikVVmN70TDw=
X-Received: by 2002:a19:7516:: with SMTP id y22mr22172338lfe.106.1552492277431;  Wed, 13 Mar 2019 08:51:17 -0700 (PDT)
MIME-Version: 1.0
References: <155245900142.5466.15600148045977298644.idtracker@ietfa.amsl.com> <CABcZeBNMt8y7EoFr3PXR84zPgvssp5=B2x7-7sQOb4wM_94RGg@mail.gmail.com> <7017B332-62F8-47BC-94EE-02ABDB7C1B14@kuehlewind.net> <4D3DEA6C-7526-4045-AA5E-AC7039CA04F4@cooperw.in>
In-Reply-To: <4D3DEA6C-7526-4045-AA5E-AC7039CA04F4@cooperw.in>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 13 Mar 2019 08:50:40 -0700
Message-ID: <CABcZeBNGzDMCxev=pXg1U67HnXP=qh1go2Xn-0bCiNv53zJ9TA@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>, trans-chairs@ietf.org, Trans <trans@ietf.org>, Adam Roach via Datatracker <noreply@ietf.org>, draft-ietf-trans-rfc6962-bis@ietf.org,  IESG <iesg@ietf.org>, Paul Wouters <paul@nohats.ca>
Content-Type: multipart/alternative; boundary="000000000000b69de40583fbc647"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/JUK7A8V2JAO7685xD0j34oYLy8E>
Subject: Re: [Trans] Adam Roach's Discuss on draft-ietf-trans-rfc6962-bis-31: (with DISCUSS and COMMENT)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Mar 2019 15:51:36 -0000

--000000000000b69de40583fbc647
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks for pointing that out. I had forgotten. This in fact seems to
support use of Obsoletes here.

-Ekr


On Wed, Mar 13, 2019 at 7:53 AM Alissa Cooper <alissa@cooperw.in> wrote:

> Hi Mirja,
>
> > On Mar 13, 2019, at 10:19 AM, Mirja Kuehlewind <ietf@kuehlewind.net>
> wrote:
> >
> > HI Ekr,
> >
> > I actually have a related question. As this document is rather
> specifying a new version than =E2=80=9Cjust=E2=80=9D correcting an existi=
ng spec, it=E2=80=99s not
> really clear to me if the obsolete tag is the right choice here. I know
> some other protocols do this in a similar fashion, but I would rather
> recommend to only update the previous version RFC (in order to create a
> link to this new spec) or declare it historic if usage is not recommended
> anymore. I think that's also something we should discuss on the IESG.
>
> We have a statement that explains our current position:
> https://www.ietf.org/blog/iesg-statement-designating-rfcs-historic/
>
> Alissa
>
> >
> > Coming back to your original question about how much should be changed
> in a bis document. I think this is a valid question for bis doc that
> correct known errors. However, in case of this document that specifies a
> new version, I think it is the right thing to do to also align such a new
> version with the guidelines we follow at the time of publication.
> >
> > Mirja
> >
> >
> >> On 13. Mar 2019, at 14:28, Eric Rescorla <ekr@rtfm.com> wrote:
> >>
> >>
> >>
> >> On Tue, Mar 12, 2019 at 11:36 PM Adam Roach via Datatracker
> <noreply@ietf..org> wrote:
> >> Adam Roach has entered the following ballot position for
> >> draft-ietf-trans-rfc6962-bis-31: Discuss
> >>
> >> When responding, please keep the subject line intact and reply to all
> >> email addresses included in the To and CC lines. (Feel free to cut thi=
s
> >> introductory paragraph, however.)
> >>
> >>
> >> Please refer to
> https://www.ietf.org/iesg/statement/discuss-criteria.html
> >> for more information about IESG DISCUSS and COMMENT positions.
> >>
> >>
> >> The document, along with other ballot positions, can be found here:
> >> https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/
> >>
> >>
> >>
> >> ----------------------------------------------------------------------
> >> DISCUSS:
> >> ----------------------------------------------------------------------
> >>
> >> Thanks to everyone who worked on updating this protocol to reflect
> experience
> >> gathered from the initial CT protocol. I have one blocking comment, an=
d
> a small
> >> number of editorial suggestions.
> >>
> >>
> -------------------------------------------------------------------------=
--
> >>
> >> =C2=A75:
> >>
> >>> Clients are configured with a base URL for a log and construct URLs
> >>> for requests by appending suffixes to this base URL.  This structure
> >>> places some degree of restriction on how log operators can deploy
> >>> these services, as noted in [RFC7320].  However, operational
> >>> experience with version 1 of this protocol has not indicated that
> >>> these restrictions are a problem in practice.
> >>
> >> The synthesis of URLs by a protocol in this fashion is prohibited by
> BCP 190:
> >>
> >>   Scheme definitions define the presence, format, and semantics of a
> >>   path component in URIs; all other specifications MUST NOT constrain,
> >>   or define the structure or the semantics for any path component.
> >>
> >> Unless the intention of this document is to update BCP 190 to change
> this
> >> normative requirement, we can't publish it in its current form. Note
> that doing
> >> so would require a change of venue, as updates to BCP 190 would not be
> covered
> >> by the current TRANS charter.
> >>
> >> Please see BCP 190 section 3 for alternate approaches. All three
> approaches
> >> could be made to work for CT, and I would be happy to explain how to d=
o
> so if
> >> clarification is desired.
> >>
> >> While I agree that this is forbidden by BCP 190, this structure is
> inherited from
> >> RFC 6962, which predated 7320, so making that change seems like it's
> going
> >> to be fairly disruptive. This seems like it is falling into our
> discussion the other
> >> day about what must be changed in -bis documents.
> >>
> >> -Ekr
> >>
> >>
> >>
> >> ----------------------------------------------------------------------
> >> COMMENT:
> >> ----------------------------------------------------------------------
> >>
> >> =C2=A71.1:
> >>
> >>> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> >>> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> >>> document are to be interpreted as described in [RFC2119].
> >>
> >> Consider using the boilerplate from RFC 8174.
> >>
> >>
> -------------------------------------------------------------------------=
--
> >>
> >> =C2=A71.3:
> >>
> >>> This document revises and obsoletes the experimental CT 1.0 [RFC6962]
> >>> protocol, drawing on insights gained from CT 1.0 deployments and on
> >>> feedback from the community.
> >>
> >> Given that *this* document is also experimental, it seems a bit odd to
> call out
> >> RFC 6962 as experimental.
> >>
> >>
> -------------------------------------------------------------------------=
--
> >>
> >> =C2=A72.1.1:
> >>
> >>> We have established a registry of acceptable hash algorithms (see
> >>
> >> The use of first person here is awkward. Consider: "This document
> >> establishes..."
> >>
> >>
> -------------------------------------------------------------------------=
--
> >>
> >> =C2=A710.2:
> >>
> >>> | 0x01 - | Unassigned |                        | Specification      |
> >>> | 0xDF   |            |                        | Required and       |
> >>> |        |            |                        | Expert Review      |
> >>
> >> The policy being cited here is confusing. It is unclear whether the
> intention is
> >> that values can be registered under both =C2=A74.5 and =C2=A74.6 of RF=
C 8126. I
> suspect
> >> the intention here is the policy specified in RFC 8126 =C2=A74.6 only,
> without
> >> reference to the policy in =C2=A74.5. If so, please use the formal nam=
e
> >> "Specification Required."
> >>
> >>
> -------------------------------------------------------------------------=
--
> >>
> >> =C2=A710.4:
> >>
> >>> | 0x0008 -    | Unassigned           | Specification Required and   |
> >>> | 0xDFFF      |                      | Expert Review                |
> >>
> >> Same comment as above.
> >>
> >>
> -------------------------------------------------------------------------=
--
> >>
> >> =C2=A710.5:
> >>
> >>> | 0x0000 -      | Unassigned | n/a | Specification Required and     |
> >>> | 0xDFFF        |            |     | Expert Review                  |
> >>
> >> Same comment as above.
> >>
> >>
> >
>
>

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

<div dir=3D"ltr"><div>Thanks for pointing that out. I had forgotten. This i=
n fact seems to support use of Obsoletes here.<br></div><div><br></div><div=
>-Ekr</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Wed, Mar 13, 2019 at 7:53 AM Alissa Cooper &lt=
;<a href=3D"mailto:alissa@cooperw.in">alissa@cooperw.in</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Mirja,<br>
<br>
&gt; On Mar 13, 2019, at 10:19 AM, Mirja Kuehlewind &lt;<a href=3D"mailto:i=
etf@kuehlewind.net" target=3D"_blank">ietf@kuehlewind.net</a>&gt; wrote:<br=
>
&gt; <br>
&gt; HI Ekr,<br>
&gt; <br>
&gt; I actually have a related question. As this document is rather specify=
ing a new version than =E2=80=9Cjust=E2=80=9D correcting an existing spec, =
it=E2=80=99s not really clear to me if the obsolete tag is the right choice=
 here. I know some other protocols do this in a similar fashion, but I woul=
d rather recommend to only update the previous version RFC (in order to cre=
ate a link to this new spec) or declare it historic if usage is not recomme=
nded anymore. I think that&#39;s also something we should discuss on the IE=
SG.<br>
<br>
We have a statement that explains our current position: <a href=3D"https://=
www.ietf.org/blog/iesg-statement-designating-rfcs-historic/" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/blog/iesg-statement-designating=
-rfcs-historic/</a><br>
<br>
Alissa<br>
<br>
&gt; <br>
&gt; Coming back to your original question about how much should be changed=
 in a bis document. I think this is a valid question for bis doc that corre=
ct known errors. However, in case of this document that specifies a new ver=
sion, I think it is the right thing to do to also align such a new version =
with the guidelines we follow at the time of publication.<br>
&gt; <br>
&gt; Mirja<br>
&gt; <br>
&gt; <br>
&gt;&gt; On 13. Mar 2019, at 14:28, Eric Rescorla &lt;<a href=3D"mailto:ekr=
@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; On Tue, Mar 12, 2019 at 11:36 PM Adam Roach via Datatracker &lt;no=
reply@ietf..org&gt; wrote:<br>
&gt;&gt; Adam Roach has entered the following ballot position for<br>
&gt;&gt; draft-ietf-trans-rfc6962-bis-31: Discuss<br>
&gt;&gt; <br>
&gt;&gt; When responding, please keep the subject line intact and reply to =
all<br>
&gt;&gt; email addresses included in the To and CC lines. (Feel free to cut=
 this<br>
&gt;&gt; introductory paragraph, however.)<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; Please refer to <a href=3D"https://www.ietf.org/iesg/statement/dis=
cuss-criteria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.o=
rg/iesg/statement/discuss-criteria.html</a><br>
&gt;&gt; for more information about IESG DISCUSS and COMMENT positions.<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; The document, along with other ballot positions, can be found here=
:<br>
&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-trans-rfc69=
62-bis/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/=
doc/draft-ietf-trans-rfc6962-bis/</a><br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; ------------------------------------------------------------------=
----<br>
&gt;&gt; DISCUSS:<br>
&gt;&gt; ------------------------------------------------------------------=
----<br>
&gt;&gt; <br>
&gt;&gt; Thanks to everyone who worked on updating this protocol to reflect=
 experience<br>
&gt;&gt; gathered from the initial CT protocol. I have one blocking comment=
, and a small<br>
&gt;&gt; number of editorial suggestions.<br>
&gt;&gt; <br>
&gt;&gt; ------------------------------------------------------------------=
---------<br>
&gt;&gt; <br>
&gt;&gt; =C2=A75:<br>
&gt;&gt; <br>
&gt;&gt;&gt; Clients are configured with a base URL for a log and construct=
 URLs<br>
&gt;&gt;&gt; for requests by appending suffixes to this base URL.=C2=A0 Thi=
s structure<br>
&gt;&gt;&gt; places some degree of restriction on how log operators can dep=
loy<br>
&gt;&gt;&gt; these services, as noted in [RFC7320].=C2=A0 However, operatio=
nal<br>
&gt;&gt;&gt; experience with version 1 of this protocol has not indicated t=
hat<br>
&gt;&gt;&gt; these restrictions are a problem in practice.<br>
&gt;&gt; <br>
&gt;&gt; The synthesis of URLs by a protocol in this fashion is prohibited =
by BCP 190:<br>
&gt;&gt; <br>
&gt;&gt;=C2=A0 =C2=A0Scheme definitions define the presence, format, and se=
mantics of a<br>
&gt;&gt;=C2=A0 =C2=A0path component in URIs; all other specifications MUST =
NOT constrain,<br>
&gt;&gt;=C2=A0 =C2=A0or define the structure or the semantics for any path =
component.<br>
&gt;&gt; <br>
&gt;&gt; Unless the intention of this document is to update BCP 190 to chan=
ge this<br>
&gt;&gt; normative requirement, we can&#39;t publish it in its current form=
. Note that doing<br>
&gt;&gt; so would require a change of venue, as updates to BCP 190 would no=
t be covered<br>
&gt;&gt; by the current TRANS charter.<br>
&gt;&gt; <br>
&gt;&gt; Please see BCP 190 section 3 for alternate approaches. All three a=
pproaches<br>
&gt;&gt; could be made to work for CT, and I would be happy to explain how =
to do so if<br>
&gt;&gt; clarification is desired.<br>
&gt;&gt; <br>
&gt;&gt; While I agree that this is forbidden by BCP 190, this structure is=
 inherited from<br>
&gt;&gt; RFC 6962, which predated 7320, so making that change seems like it=
&#39;s going<br>
&gt;&gt; to be fairly disruptive. This seems like it is falling into our di=
scussion the other<br>
&gt;&gt; day about what must be changed in -bis documents.<br>
&gt;&gt; <br>
&gt;&gt; -Ekr<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; ------------------------------------------------------------------=
----<br>
&gt;&gt; COMMENT:<br>
&gt;&gt; ------------------------------------------------------------------=
----<br>
&gt;&gt; <br>
&gt;&gt; =C2=A71.1:<br>
&gt;&gt; <br>
&gt;&gt;&gt; The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;RE=
QUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,<br>
&gt;&gt;&gt; &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&=
quot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this<br>
&gt;&gt;&gt; document are to be interpreted as described in [RFC2119].<br>
&gt;&gt; <br>
&gt;&gt; Consider using the boilerplate from RFC 8174.<br>
&gt;&gt; <br>
&gt;&gt; ------------------------------------------------------------------=
---------<br>
&gt;&gt; <br>
&gt;&gt; =C2=A71.3:<br>
&gt;&gt; <br>
&gt;&gt;&gt; This document revises and obsoletes the experimental CT 1.0 [R=
FC6962]<br>
&gt;&gt;&gt; protocol, drawing on insights gained from CT 1.0 deployments a=
nd on<br>
&gt;&gt;&gt; feedback from the community.<br>
&gt;&gt; <br>
&gt;&gt; Given that *this* document is also experimental, it seems a bit od=
d to call out<br>
&gt;&gt; RFC 6962 as experimental.<br>
&gt;&gt; <br>
&gt;&gt; ------------------------------------------------------------------=
---------<br>
&gt;&gt; <br>
&gt;&gt; =C2=A72.1.1:<br>
&gt;&gt; <br>
&gt;&gt;&gt; We have established a registry of acceptable hash algorithms (=
see<br>
&gt;&gt; <br>
&gt;&gt; The use of first person here is awkward. Consider: &quot;This docu=
ment<br>
&gt;&gt; establishes...&quot;<br>
&gt;&gt; <br>
&gt;&gt; ------------------------------------------------------------------=
---------<br>
&gt;&gt; <br>
&gt;&gt; =C2=A710.2:<br>
&gt;&gt; <br>
&gt;&gt;&gt; | 0x01 - | Unassigned |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Specification=C2=A0 =C2=A0 =
=C2=A0 |<br>
&gt;&gt;&gt; | 0xDF=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 | Required and=C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;&gt;&gt; |=C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 | Expert Review=C2=A0 =C2=A0 =C2=A0 |<br>
&gt;&gt; <br>
&gt;&gt; The policy being cited here is confusing. It is unclear whether th=
e intention is<br>
&gt;&gt; that values can be registered under both =C2=A74.5 and =C2=A74.6 o=
f RFC 8126. I suspect<br>
&gt;&gt; the intention here is the policy specified in RFC 8126 =C2=A74.6 o=
nly, without<br>
&gt;&gt; reference to the policy in =C2=A74.5. If so, please use the formal=
 name<br>
&gt;&gt; &quot;Specification Required.&quot;<br>
&gt;&gt; <br>
&gt;&gt; ------------------------------------------------------------------=
---------<br>
&gt;&gt; <br>
&gt;&gt; =C2=A710.4:<br>
&gt;&gt; <br>
&gt;&gt;&gt; | 0x0008 -=C2=A0 =C2=A0 | Unassigned=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0| Specification Required and=C2=A0 =C2=A0|<br>
&gt;&gt;&gt; | 0xDFFF=C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Expert Review=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;&gt; <br>
&gt;&gt; Same comment as above.<br>
&gt;&gt; <br>
&gt;&gt; ------------------------------------------------------------------=
---------<br>
&gt;&gt; <br>
&gt;&gt; =C2=A710.5:<br>
&gt;&gt; <br>
&gt;&gt;&gt; | 0x0000 -=C2=A0 =C2=A0 =C2=A0 | Unassigned | n/a | Specificat=
ion Required and=C2=A0 =C2=A0 =C2=A0|<br>
&gt;&gt;&gt; | 0xDFFF=C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0| Expert Review=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;&gt; <br>
&gt;&gt; Same comment as above.<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt; <br>
<br>
</blockquote></div>

--000000000000b69de40583fbc647--


From nobody Wed Mar 13 08:56:13 2019
Return-Path: <ietf@kuehlewind.net>
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 721011310DC; Wed, 13 Mar 2019 08:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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 5m2td66Kq4yE; Wed, 13 Mar 2019 08:55:59 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 6D8D5131071; Wed, 13 Mar 2019 08:55:59 -0700 (PDT)
Received: from [129.192.10.2] (helo=[10.149.2.6]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1h46EV-00008a-8n; Wed, 13 Mar 2019 16:55:55 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <CABcZeBNGzDMCxev=pXg1U67HnXP=qh1go2Xn-0bCiNv53zJ9TA@mail.gmail.com>
Date: Wed, 13 Mar 2019 16:55:54 +0100
Cc: Alissa Cooper <alissa@cooperw.in>, trans-chairs@ietf.org, Trans <trans@ietf.org>, Adam Roach via Datatracker <noreply@ietf.org>, draft-ietf-trans-rfc6962-bis@ietf.org, IESG <iesg@ietf.org>, Paul Wouters <paul@nohats.ca>
Content-Transfer-Encoding: quoted-printable
Message-Id: <001DE1A5-32B4-4D21-B1C1-B9811ED7D94D@kuehlewind.net>
References: <155245900142.5466.15600148045977298644.idtracker@ietfa.amsl.com> <CABcZeBNMt8y7EoFr3PXR84zPgvssp5=B2x7-7sQOb4wM_94RGg@mail.gmail.com> <7017B332-62F8-47BC-94EE-02ABDB7C1B14@kuehlewind.net> <4D3DEA6C-7526-4045-AA5E-AC7039CA04F4@cooperw.in> <CABcZeBNGzDMCxev=pXg1U67HnXP=qh1go2Xn-0bCiNv53zJ9TA@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
X-Mailer: Apple Mail (2.3445.101.1)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1552492559;1b48ead7;
X-HE-SMSGID: 1h46EV-00008a-8n
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/GCxD6C1BDHLrny-YsbUKD9eT53Y>
Subject: Re: [Trans] Adam Roach's Discuss on draft-ietf-trans-rfc6962-bis-31: (with DISCUSS and COMMENT)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Mar 2019 15:56:11 -0000

Hi Ekr,

See below

> On 13. Mar 2019, at 16:50, Eric Rescorla <ekr@rtfm.com> wrote:
>=20
> Thanks for pointing that out. I had forgotten. This in fact seems to =
support use of Obsoletes here.
>=20
> -Ekr
>=20
>=20
> On Wed, Mar 13, 2019 at 7:53 AM Alissa Cooper <alissa@cooperw.in> =
wrote:
> Hi Mirja,
>=20
> > On Mar 13, 2019, at 10:19 AM, Mirja Kuehlewind <ietf@kuehlewind.net> =
wrote:
> >=20
> > HI Ekr,
> >=20
> > I actually have a related question. As this document is rather =
specifying a new version than =E2=80=9Cjust=E2=80=9D correcting an =
existing spec, it=E2=80=99s not really clear to me if the obsolete tag =
is the right choice here. I know some other protocols do this in a =
similar fashion, but I would rather recommend to only update the =
previous version RFC (in order to create a link to this new spec) or =
declare it historic if usage is not recommended anymore. I think that's =
also something we should discuss on the IESG.
>=20
> We have a statement that explains our current position: =
https://www.ietf.org/blog/iesg-statement-designating-rfcs-historic/

Based on the statement you made in the other mail:

 "this is a new version of this protocol and you should stop using the =
old and and start using this one=E2=80=9D

And what=E2=80=99s written in this statement:

"	=E2=80=A2 A document is labelled Historic when what it describes =
is no longer considered current: no longer recommended for use. =E2=80=9C

I would think historic should be used.

Mirja



>=20
> Alissa
>=20
> >=20
> > Coming back to your original question about how much should be =
changed in a bis document. I think this is a valid question for bis doc =
that correct known errors. However, in case of this document that =
specifies a new version, I think it is the right thing to do to also =
align such a new version with the guidelines we follow at the time of =
publication.
> >=20
> > Mirja
> >=20
> >=20
> >> On 13. Mar 2019, at 14:28, Eric Rescorla <ekr@rtfm.com> wrote:
> >>=20
> >>=20
> >>=20
> >> On Tue, Mar 12, 2019 at 11:36 PM Adam Roach via Datatracker =
<noreply@ietf..org> wrote:
> >> Adam Roach has entered the following ballot position for
> >> draft-ietf-trans-rfc6962-bis-31: Discuss
> >>=20
> >> When responding, please keep the subject line intact and reply to =
all
> >> email addresses included in the To and CC lines. (Feel free to cut =
this
> >> introductory paragraph, however.)
> >>=20
> >>=20
> >> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> >> for more information about IESG DISCUSS and COMMENT positions.
> >>=20
> >>=20
> >> The document, along with other ballot positions, can be found here:
> >> https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/
> >>=20
> >>=20
> >>=20
> >> =
----------------------------------------------------------------------
> >> DISCUSS:
> >> =
----------------------------------------------------------------------
> >>=20
> >> Thanks to everyone who worked on updating this protocol to reflect =
experience
> >> gathered from the initial CT protocol. I have one blocking comment, =
and a small
> >> number of editorial suggestions.
> >>=20
> >> =
--------------------------------------------------------------------------=
-
> >>=20
> >> =C2=A75:
> >>=20
> >>> Clients are configured with a base URL for a log and construct =
URLs
> >>> for requests by appending suffixes to this base URL.  This =
structure
> >>> places some degree of restriction on how log operators can deploy
> >>> these services, as noted in [RFC7320].  However, operational
> >>> experience with version 1 of this protocol has not indicated that
> >>> these restrictions are a problem in practice.
> >>=20
> >> The synthesis of URLs by a protocol in this fashion is prohibited =
by BCP 190:
> >>=20
> >>   Scheme definitions define the presence, format, and semantics of =
a
> >>   path component in URIs; all other specifications MUST NOT =
constrain,
> >>   or define the structure or the semantics for any path component.
> >>=20
> >> Unless the intention of this document is to update BCP 190 to =
change this
> >> normative requirement, we can't publish it in its current form. =
Note that doing
> >> so would require a change of venue, as updates to BCP 190 would not =
be covered
> >> by the current TRANS charter.
> >>=20
> >> Please see BCP 190 section 3 for alternate approaches. All three =
approaches
> >> could be made to work for CT, and I would be happy to explain how =
to do so if
> >> clarification is desired.
> >>=20
> >> While I agree that this is forbidden by BCP 190, this structure is =
inherited from
> >> RFC 6962, which predated 7320, so making that change seems like =
it's going
> >> to be fairly disruptive. This seems like it is falling into our =
discussion the other
> >> day about what must be changed in -bis documents.
> >>=20
> >> -Ekr
> >>=20
> >>=20
> >>=20
> >> =
----------------------------------------------------------------------
> >> COMMENT:
> >> =
----------------------------------------------------------------------
> >>=20
> >> =C2=A71.1:
> >>=20
> >>> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL =
NOT",
> >>> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in =
this
> >>> document are to be interpreted as described in [RFC2119].
> >>=20
> >> Consider using the boilerplate from RFC 8174.
> >>=20
> >> =
--------------------------------------------------------------------------=
-
> >>=20
> >> =C2=A71.3:
> >>=20
> >>> This document revises and obsoletes the experimental CT 1.0 =
[RFC6962]
> >>> protocol, drawing on insights gained from CT 1.0 deployments and =
on
> >>> feedback from the community.
> >>=20
> >> Given that *this* document is also experimental, it seems a bit odd =
to call out
> >> RFC 6962 as experimental.
> >>=20
> >> =
--------------------------------------------------------------------------=
-
> >>=20
> >> =C2=A72.1.1:
> >>=20
> >>> We have established a registry of acceptable hash algorithms (see
> >>=20
> >> The use of first person here is awkward. Consider: "This document
> >> establishes..."
> >>=20
> >> =
--------------------------------------------------------------------------=
-
> >>=20
> >> =C2=A710.2:
> >>=20
> >>> | 0x01 - | Unassigned |                        | Specification     =
 |
> >>> | 0xDF   |            |                        | Required and      =
 |
> >>> |        |            |                        | Expert Review     =
 |
> >>=20
> >> The policy being cited here is confusing. It is unclear whether the =
intention is
> >> that values can be registered under both =C2=A74.5 and =C2=A74.6 of =
RFC 8126. I suspect
> >> the intention here is the policy specified in RFC 8126 =C2=A74.6 =
only, without
> >> reference to the policy in =C2=A74.5. If so, please use the formal =
name
> >> "Specification Required."
> >>=20
> >> =
--------------------------------------------------------------------------=
-
> >>=20
> >> =C2=A710.4:
> >>=20
> >>> | 0x0008 -    | Unassigned           | Specification Required and  =
 |
> >>> | 0xDFFF      |                      | Expert Review               =
 |
> >>=20
> >> Same comment as above.
> >>=20
> >> =
--------------------------------------------------------------------------=
-
> >>=20
> >> =C2=A710.5:
> >>=20
> >>> | 0x0000 -      | Unassigned | n/a | Specification Required and    =
 |
> >>> | 0xDFFF        |            |     | Expert Review                 =
 |
> >>=20
> >> Same comment as above.
> >>=20
> >>=20
> >=20
>=20


From nobody Wed Mar 13 09:34:27 2019
Return-Path: <noreply@ietf.org>
X-Original-To: trans@ietf.org
Delivered-To: trans@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF38130F2C; Wed, 13 Mar 2019 09:34:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-trans-rfc6962-bis@ietf.org, Paul Wouters <paul@nohats.ca>, trans-chairs@ietf.org, paul@nohats.ca, trans@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.93.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155249486456.28074.9608101501013163742.idtracker@ietfa.amsl.com>
Date: Wed, 13 Mar 2019 09:34:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/CoDP8uTXny65czyU-KVSgmJFrZc>
Subject: [Trans] Alissa Cooper's Discuss on draft-ietf-trans-rfc6962-bis-31: (with DISCUSS and COMMENT)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Mar 2019 16:34:25 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-trans-rfc6962-bis-31: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Glad to see this revision of the protocol. My comments and questions should be
easy to address.

= Section 10.2, 10.4, 10.5 =

A Specification Required registry policy implies expert review. So a registry
policy of "Specification Required and Expert Review" is duplicative; it should
just say "Specification Required." I know this seems trivial but there has been
so much confusion about this through the years that it is important to be
precise.

= Section 10.3 =

This section needs to state what the registry policy is for the code points not
already registered (presumably Expert Review given 10.3.1, but it needs to be
explicit).

= Section 10.6.1 =

Using the term "Parameters Required" as a capitalized term is confusing. FCFS
registries by definition can require additional information to be provided in
order to get something registered. For avoidance of confusion I think the
assignment policy should be listed as First Come First Served and the
requirement that parameters be included in the application can use a normative
MUST in the last paragraph if there is concern that the parameters won't be
supplied.

However, I also wonder what will be done with the parameters that are supplied.
Is IANA expected to just maintain them privately, or to publish them?

What is expected to appear in the 'Log' column in the registry?


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

In Section 1.1, please use the RFC 8174 boilerplate in lieu of the RFC 2119 boilerplate.



From nobody Wed Mar 13 09:39:21 2019
Return-Path: <alissa@cooperw.in>
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 E63A6130F0D; Wed, 13 Mar 2019 09:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=cooperw.in header.b=bBm7f10C; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=VagcK4OU
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 tg3540Oqz7Qd; Wed, 13 Mar 2019 09:39:17 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA2DD130F02; Wed, 13 Mar 2019 09:39:12 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 9983E24871; Wed, 13 Mar 2019 12:39:11 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 13 Mar 2019 12:39:11 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=A K6SLtslMsLTZhetZViXp6jkyUG7sxuGKLwS85JLfSw=; b=bBm7f10CEMkn4XFai cY0jB9J76m1zw9cVBVznaDB2ik+Z/XP+QTu1qtxXt8NGKa6odkqDWNT9xtO8S3Ho r1C6WglKlOAPzwj2wSnylPCxis0IW3kNe9Hfbvy1fU10khpeQoPs7px/hwdic5Cy K6Ld7L0shBdDUGdafI07nQUQ1vJ2uclxPzRZLxsULVMy9HhLEt3yG+rl4LVIIfri fiUcmzo8mKrSg/A2UUReQJ5y7hOT3S87nPAiFKIfWum7KEgikyLN7AMTSPv3MJ2J MCrv+IKddpvysofAA9fBQqxRZKZD57nH4xdJrbPF3397VUwupipAdME5zRt9F56/ dud9Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=AK6SLtslMsLTZhetZViXp6jkyUG7sxuGKLwS85JLf Sw=; b=VagcK4OUfPhUnc4G3r4ExFkvklzO+bUrpxFr0qi3DZzTuzomWoiaqykUu rQEu9XeYbUicI0iA/N560TWyha/x08iBmJok/bJUD7azuO85NmR5LVFIGTQ8254m LDZ4wj5PRmszxWA3MRTMxZ1IRy9KWtDIs4m5SAS70pZMCzHaT8kPkLNEWJV9V/mS aO4ecJFvrbOd5XOSJZHSHsXVUzzoOwS6LP93YjsqkQpOuH0jV1FVuSJl1dnFmO8e oRznX7l6ek+v/vQJGSCukgpYHf0aDtpmIUbeO9/+p1RacYUN9D6U2OW2yVI2uVXS k72x208B5WE/oii2U/EY+H+7OmJwg==
X-ME-Sender: <xms:LzKJXPLzO95dw5212R3SCzS8XNYzGU4PwcLYk5429vIiSYKiZbKW4Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrhedtgdeltdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurheptggguffhjgffgffkfhfvofesthhqmh dthhdtvdenucfhrhhomheptehlihhsshgrucevohhophgvrhcuoegrlhhishhsrgestgho ohhpvghrfidrihhnqeenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppedujeefrd efkedruddujedrieehnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhishhsrgestgho ohhpvghrfidrihhnnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:LzKJXPjJqnyS1mdSZ3GZr5ktIolZX7SNQM47UKcrvBN5wV2-v1AX0w> <xmx:LzKJXMJfiAk8MlWhn9oe-fQMcwWKeu7Oe4OHrmmjSHd4WBAjnsxflw> <xmx:LzKJXGgmJp8yybeT8Ule9tRRrh2CEJLSnjGbrxBJdGz_1uQwI6Pl8g> <xmx:LzKJXDR1w3bpCbZctuutQaCB0hjG0fTTH5SOGmbPqbOKr4dJx054sg>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.65]) by mail.messagingengine.com (Postfix) with ESMTPA id DD0F4E4360; Wed, 13 Mar 2019 12:39:10 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <155148198458.6254.15247203587880068135@ietfa.amsl.com>
Date: Wed, 13 Mar 2019 12:39:09 -0400
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-trans-rfc6962-bis.all@ietf.org, trans@ietf.org, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C284C13A-5B7F-4844-903D-0A36FD36458B@cooperw.in>
References: <155148198458.6254.15247203587880068135@ietfa.amsl.com>
To: Joel Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/DrlVkjbb2EnxKxcXb9_g3WGk8BQ>
Subject: Re: [Trans] [Gen-art] Genart last call review of draft-ietf-trans-rfc6962-bis-31
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Mar 2019 16:39:19 -0000

Joel, thank you for your review. I entered a DISCUSS ballot to discuss a =
couple of the IANA registries.

Alissa

> On Mar 1, 2019, at 6:13 PM, Joel Halpern <jmh@joelhalpern.com> wrote:
>=20
> Reviewer: Joel Halpern
> Review result: Ready
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-trans-rfc6962-bis-31
> Reviewer: Joel Halpern
> Review Date: 2019-03-01
> IETF LC End Date: 2019-03-14
> IESG Telechat date: 2019-03-14
>=20
> Summary: This document is ready for publication as an Experimental RFC
>=20
> Major issues: N/A
>=20
> Minor issues: N/A
>=20
> Nits/editorial comments: N/A
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Mar 13 10:26:41 2019
Return-Path: <adam@nostrum.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 B94B1130EF7; Wed, 13 Mar 2019 10:26:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level: 
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 Yi_RouXNiWN2; Wed, 13 Mar 2019 10:26:32 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 B5B96130F13; Wed, 13 Mar 2019 10:26:09 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x2DHQ6IU027400 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 13 Mar 2019 12:26:07 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1552497969; bh=9W7woJlGs/vsyVrGXlsP+M9V2bYgzDOomcyyIXPf0V0=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=tiWhFBAG/vS1jNaV0DMhJEYHKPpReaPRbZ2BNXgh8psTsr7aIEwS6BCwVibqyRNzg DrRfBl8s3rR2pNRkndf6ux8VQs0Oq66RzJn4QJ32Z4U9JU32aYLvCSldeqWB+kYjxe 8YSu4EQCOLKlPc810xwIkd8slF6DNPhlt06H3VTc=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: Eric Rescorla <ekr@rtfm.com>, Adam Roach via Datatracker <noreply@ietf.org>
Cc: draft-ietf-trans-rfc6962-bis@ietf.org, Paul Wouters <paul@nohats.ca>, Trans <trans@ietf.org>, The IESG <iesg@ietf.org>, trans-chairs@ietf.org
References: <155245900142.5466.15600148045977298644.idtracker@ietfa.amsl.com> <CABcZeBNMt8y7EoFr3PXR84zPgvssp5=B2x7-7sQOb4wM_94RGg@mail.gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <bd8c65b5-b760-e393-2936-8dfbf6ded1b6@nostrum.com>
Date: Wed, 13 Mar 2019 12:26:01 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <CABcZeBNMt8y7EoFr3PXR84zPgvssp5=B2x7-7sQOb4wM_94RGg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------69EF495B583EFD62848F7D8B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/gtn3ylODr6z7BfYS6EPkyIXVanA>
Subject: Re: [Trans] Adam Roach's Discuss on draft-ietf-trans-rfc6962-bis-31: (with DISCUSS and COMMENT)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Mar 2019 17:26:35 -0000

This is a multi-part message in MIME format.
--------------69EF495B583EFD62848F7D8B
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 3/13/19 8:28 AM, Eric Rescorla wrote:
>
>
> On Tue, Mar 12, 2019 at 11:36 PM Adam Roach via Datatracker 
> <noreply@ietf..org <mailto:noreply@ietf.org>> wrote:
>
>
>
>     ----------------------------------------------------------------------
>     DISCUSS:
>     ----------------------------------------------------------------------
>
>     Thanks to everyone who worked on updating this protocol to reflect
>     experience
>     gathered from the initial CT protocol. I have one blocking
>     comment, and a small
>     number of editorial suggestions.
>
>     ---------------------------------------------------------------------------
>
>     §5:
>
>     >  Clients are configured with a base URL for a log and construct URLs
>     >  for requests by appending suffixes to this base URL. This structure
>     >  places some degree of restriction on how log operators can deploy
>     >  these services, as noted in [RFC7320].  However, operational
>     >  experience with version 1 of this protocol has not indicated that
>     >  these restrictions are a problem in practice.
>
>     The synthesis of URLs by a protocol in this fashion is prohibited
>     by BCP 190:
>
>        Scheme definitions define the presence, format, and semantics of a
>        path component in URIs; all other specifications MUST NOT
>     constrain,
>        or define the structure or the semantics for any path component.
>
>     Unless the intention of this document is to update BCP 190 to
>     change this
>     normative requirement, we can't publish it in its current form.
>     Note that doing
>     so would require a change of venue, as updates to BCP 190 would
>     not be covered
>     by the current TRANS charter.
>
>     Please see BCP 190 section 3 for alternate approaches. All three
>     approaches
>     could be made to work for CT, and I would be happy to explain how
>     to do so if
>     clarification is desired.
>
>
> While I agree that this is forbidden by BCP 190, this structure is 
> inherited from
> RFC 6962, which predated 7320, so making that change seems like it's going
> to be fairly disruptive. This seems like it is falling into our 
> discussion the other
> day about what must be changed in -bis documents.


I think the timing of this document is fortuitous, in that it can help 
inform that conversation. In particular, this situation helps me better 
understand why both you and Benjamin raised objections to the high-level 
proposal that unchanged parts of -bis documents shouldn't be subject to 
DISCUSS positions. The take-away that I plan to bring to that 
conversation is that such a decision needs to be informed by (a) scope 
of changes between a document and its -bis, and (b) scope of changes 
required to satisfy a potential DISCUSS position.

In cases like this one, where a not-even-remotely-backwards-compatible 
suite of protocol changes is being made to a protocol in a document 
update whose diff [1] is basically the entire document, I don't think 
the principle of ignoring existing flaws in a previous document really 
applies. I get that both of those predicates are somewhat subjective 
evaluations, and that drawing a line in a process document might be 
difficult; but I think that any standard, however subjective, that you 
would be willing to sign on to would place this document outside the 
category of "bis versions that are making small, incremental changes to 
existing documents."

If the remedy for the flaw were a major overhaul rather than a 
relatively minor tweak, it would again shift the evaluation a bit; 
however, the naïve band-aid solution of moving CT endpoints to live 
under "/.well-known/ct" is a trivial change, both for this document and 
for implementations (in fact, for implementations, it can generally be 
accomplished with a configuration tweak rather than writing new code). 
To be clear, this is a textbook example of the kind of situation URI 
templates were designed for, but that would require substantially more 
work than simply moving it into the .well-known tree. Either approach 
would address the URI ownership issue.

/a

____
[1] 
https://www.ietf.org/rfcdiff?url1=rfc6962&url2=draft-ietf-trans-rfc6962-bis-31


--------------69EF495B583EFD62848F7D8B
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 3/13/19 8:28 AM, Eric Rescorla
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CABcZeBNMt8y7EoFr3PXR84zPgvssp5=B2x7-7sQOb4wM_94RGg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr"><br>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Tue, Mar 12, 2019 at
            11:36 PM Adam Roach via Datatracker &lt;<a
              href="mailto:noreply@ietf.org" moz-do-not-send="true">noreply@ietf..org</a>&gt;
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex"><br>
            <br>
----------------------------------------------------------------------<br>
            DISCUSS:<br>
----------------------------------------------------------------------<br>
            <br>
            Thanks to everyone who worked on updating this protocol to
            reflect experience<br>
            gathered from the initial CT protocol. I have one blocking
            comment, and a small<br>
            number of editorial suggestions.<br>
            <br>
---------------------------------------------------------------------------<br>
            <br>
            §5:<br>
            <br>
            &gt;  Clients are configured with a base URL for a log and
            construct URLs<br>
            &gt;  for requests by appending suffixes to this base URL. 
            This structure<br>
            &gt;  places some degree of restriction on how log operators
            can deploy<br>
            &gt;  these services, as noted in [RFC7320].  However,
            operational<br>
            &gt;  experience with version 1 of this protocol has not
            indicated that<br>
            &gt;  these restrictions are a problem in practice.<br>
            <br>
            The synthesis of URLs by a protocol in this fashion is
            prohibited by BCP 190:<br>
            <br>
               Scheme definitions define the presence, format, and
            semantics of a<br>
               path component in URIs; all other specifications MUST NOT
            constrain,<br>
               or define the structure or the semantics for any path
            component.<br>
            <br>
            Unless the intention of this document is to update BCP 190
            to change this<br>
            normative requirement, we can't publish it in its current
            form. Note that doing<br>
            so would require a change of venue, as updates to BCP 190
            would not be covered<br>
            by the current TRANS charter.<br>
            <br>
            Please see BCP 190 section 3 for alternate approaches. All
            three approaches<br>
            could be made to work for CT, and I would be happy to
            explain how to do so if<br>
            clarification is desired.<br>
          </blockquote>
          <div><br>
          </div>
          <div>While I agree that this is forbidden by BCP 190, this
            structure is inherited from</div>
          <div>RFC 6962, which predated 7320, so making that change
            seems like it's going</div>
          <div>to be fairly disruptive. This seems like it is falling
            into our discussion the other</div>
          <div>day about what must be changed in -bis documents.<br>
          </div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>I think the timing of this document is fortuitous, in that it can
      help inform that conversation. In particular, this situation helps
      me better understand why both you and Benjamin raised objections
      to the high-level proposal that unchanged parts of -bis documents
      shouldn't be subject to DISCUSS positions. The take-away that I
      plan to bring to that conversation is that such a decision needs
      to be informed by (a) scope of changes between a document and its
      -bis, and (b) scope of changes required to satisfy a potential
      DISCUSS position.<br>
    </p>
    <p>In cases like this one, where a
      not-even-remotely-backwards-compatible suite of protocol changes
      is being made to a protocol in a document update whose diff [1] is
      basically the entire document, I don't think the principle of
      ignoring existing flaws in a previous document really applies. I
      get that both of those predicates are somewhat subjective
      evaluations, and that drawing a line in a process document might
      be difficult; but I think that any standard, however subjective,
      that you would be willing to sign on to would place this document
      outside the category of "bis versions that are making small,
      incremental changes to existing documents."</p>
    <p>If the remedy for the flaw were a major overhaul rather than a
      relatively minor tweak, it would again shift the evaluation a bit;
      however, the naïve band-aid solution of moving CT endpoints to
      live under "/.well-known/ct" is a trivial change, both for this
      document and for implementations (in fact, for implementations, it
      can generally be accomplished with a configuration tweak rather
      than writing new code). To be clear, this is a textbook example of
      the kind of situation URI templates were designed for, but that
      would require substantially more work than simply moving it into
      the .well-known tree. Either approach would address the URI
      ownership issue.<br>
    </p>
    <p>/a<br>
    </p>
    <p>____<br>
      [1]
<a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url1=rfc6962&amp;url2=draft-ietf-trans-rfc6962-bis-31">https://www.ietf.org/rfcdiff?url1=rfc6962&amp;url2=draft-ietf-trans-rfc6962-bis-31</a><br>
    </p>
  </body>
</html>

--------------69EF495B583EFD62848F7D8B--


From nobody Wed Mar 13 13:53:10 2019
Return-Path: <aamelnikov@fastmail.fm>
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 C32C81311BD; Wed, 13 Mar 2019 13:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.981
X-Spam-Level: 
X-Spam-Status: No, score=-1.981 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, MIME_HEADER_CTYPE_ONLY=0.717, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=SlOn/q7e; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=npE9fk/x
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 9dLVoODmuzJ4; Wed, 13 Mar 2019 13:53:07 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DC461311B2; Wed, 13 Mar 2019 13:53:07 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id B784821FFD; Wed, 13 Mar 2019 16:53:06 -0400 (EDT)
Received: from imap1 ([10.202.2.51]) by compute7.internal (MEProxy); Wed, 13 Mar 2019 16:53:06 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= message-id:in-reply-to:references:date:from:to:cc:subject :content-type; s=fm2; bh=/kcGBwyWw1MXfZqueG0qDO5NrU7AHhRzspfFZ3x e/q4=; b=SlOn/q7eZpN2H07fiVjN8g3iNJxsi99KzpoDVXE2jjAu4wmeLmRL0A9 8dST/6xA1KxaA9nDgJavwBvJ10EZgwbIVVJB+9eU6oSGT2GJI1FJOO8EDPmEa5tA Xz24jecMrGDuJMPllMx+oCd1tXkvuIcUYDeg2QK9Jai1vmnccAAMdBDESgwux4BE eBp5r9wAvyhnEBPc9Qt85tD6K3MVj/e3psBp3ad1ozj5IFJTAVXxkw49yUAiv4dq 4xZ6Ii+lhyGzOt7yp/lC3yYJgzwY8oUq7D5xiuGi6REoKTyQhsnbSkbq0wuksOvT 6SfyQdxijzvCwoz6FTINQDdrlcNDP4Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:references:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=/kcGBwyWw1MXfZque G0qDO5NrU7AHhRzspfFZ3xe/q4=; b=npE9fk/xHpCuGOrxKVwRcTRbuMAtj9wdF HtbvkDRfHl1pn/rDcufcaso2oHjHYZBPvablJCEDHgWZYFie2XeuP1NsGMVNhHHr r+n1ILLVaNrN6Qmj0ctGRc46APBcWWIz+JzdxzfXETkdrFSqyuSCdmbE5pkDSzx6 QDy3INDKeLMJv1jPsFPbhWvAXACqEVAnm47w7rK8PKmmxiGowXfpZriVrPDuUn98 KWmehOdhjMOpSWvjW39IWxCMQRGrCFT02Yhpt4bA9QR91Bl/1WvSt0Yh/DDNduwb 9Od6SXCW6N5yoYkLOxb4LFcf7YkSIwe316lHO/U1IFZpAyXQkHe7g==
X-ME-Sender: <xms:sW2JXA9VlFjfdV0x7pHYN3PtUtDucM4GDmboeftWUBxBJ5GyMpYx3Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrhedtgddugeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfkfgjfhffhffvufgtsegrtderreerreejnecuhfhrohhmpedftehlvgig vgihucfovghlnhhikhhovhdfuceorggrmhgvlhhnihhkohhvsehfrghsthhmrghilhdrfh hmqeenucfrrghrrghmpehmrghilhhfrhhomheprggrmhgvlhhnihhkohhvsehfrghsthhm rghilhdrfhhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:sW2JXJcPPmL0JpGgamSbAxaaV1pWkZ0eNO5o8jIE0O5DID5dtTkpMw> <xmx:sW2JXJ2Ml3sCp5cqdDIxjB0Iv8NzPsGzr3AwpPtK_QNjiLDjVc_LuQ> <xmx:sW2JXCCbseiAstahm4A2TgBzSZ_HErFWnPpPCFgZLb3UKltzeqd8_g> <xmx:sm2JXIAYwrDGKF_5UitPd34hXHmQD4FaKn0C7OecL3za9ARY7dNaiw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9995DD4814; Wed, 13 Mar 2019 16:53:05 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.5-925-g644bf8c-fmstable-20190228v5
X-Me-Personality: 21611513
Message-Id: <cb8b1664-6176-4c62-9651-5922f7d0ae2e@www.fastmail.com>
In-Reply-To: <bd8c65b5-b760-e393-2936-8dfbf6ded1b6@nostrum.com>
References: <155245900142.5466.15600148045977298644.idtracker@ietfa.amsl.com> <CABcZeBNMt8y7EoFr3PXR84zPgvssp5=B2x7-7sQOb4wM_94RGg@mail.gmail.com> <bd8c65b5-b760-e393-2936-8dfbf6ded1b6@nostrum.com>
Date: Wed, 13 Mar 2019 16:52:50 -0400
From: "Alexey Melnikov" <aamelnikov@fastmail.fm>
To: "Adam Roach" <adam@nostrum.com>, "Eric Rescorla" <ekr@rtfm.com>
Cc: draft-ietf-trans-rfc6962-bis@ietf.org, "Paul Wouters" <paul@nohats.ca>, Trans <trans@ietf.org>, "The IESG" <iesg@ietf.org>, trans-chairs@ietf.org
Content-Type: multipart/alternative; boundary=6462d9b790f348a8ad377b6a8f2ec418
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/Se-xNnHrS6CcbHzCI7moCV4xiBw>
Subject: Re: [Trans]  =?utf-8?q?Adam_Roach=27s_Discuss_on_draft-ietf-trans-rfc?= =?utf-8?q?6962-bis-31=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Mar 2019 20:53:09 -0000

--6462d9b790f348a8ad377b6a8f2ec418
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 13, 2019, at 5:26 PM, Adam Roach wrote:
> On 3/13/19 8:28 AM, Eric Rescorla wrote:
>>=20
>> On Tue, Mar 12, 2019 at 11:36 PM Adam Roach via Datatracker <noreply@=
ietf..org <mailto:noreply@ietf.org>> wrote:
>>>=20
>>> --------------------------------------------------------------------=
--
>>>  DISCUSS:
>>>  -------------------------------------------------------------------=
---
>>>=20
>>>  Thanks to everyone who worked on updating this protocol to reflect =
experience
>>>  gathered from the initial CT protocol. I have one blocking comment,=
 and a small
>>>  number of editorial suggestions.
>>>=20
>>>  -------------------------------------------------------------------=
--------
>>>=20
>>>  =C2=A75:
>>>=20
>>>  > Clients are configured with a base URL for a log and construct UR=
Ls
>>>  > for requests by appending suffixes to this base URL. This structu=
re
>>>  > places some degree of restriction on how log operators can deploy=

>>>  > these services, as noted in [RFC7320]. However, operational
>>>  > experience with version 1 of this protocol has not indicated that=

>>>  > these restrictions are a problem in practice.
>>>=20
>>>  The synthesis of URLs by a protocol in this fashion is prohibited b=
y BCP 190:
>>>=20
>>>  Scheme definitions define the presence, format, and semantics of a
>>>  path component in URIs; all other specifications MUST NOT constrain=
,
>>>  or define the structure or the semantics for any path component.
>>>=20
>>>  Unless the intention of this document is to update BCP 190 to chang=
e this
>>>  normative requirement, we can't publish it in its current form. Not=
e that doing
>>>  so would require a change of venue, as updates to BCP 190 would not=
 be covered
>>>  by the current TRANS charter.
>>>=20
>>>  Please see BCP 190 section 3 for alternate approaches. All three ap=
proaches
>>>  could be made to work for CT, and I would be happy to explain how t=
o do so if
>>>  clarification is desired.
>>=20
>> While I agree that this is forbidden by BCP 190, this structure is in=
herited from
>> RFC 6962, which predated 7320, so making that change seems like it's =
going
>> to be fairly disruptive. This seems like it is falling into our discu=
ssion the other
>> day about what must be changed in -bis documents.
> I think the timing of this document is fortuitous, in that it can help=
 inform that conversation. In particular, this situation helps me better=
 understand why both you and Benjamin raised objections to the high-leve=
l proposal that unchanged parts of -bis documents shouldn't be subject t=
o DISCUSS positions. The take-away that I plan to bring to that conversa=
tion is that such a decision needs to be informed by (a) scope of change=
s between a document and its -bis, and (b) scope of changes required to =
satisfy a potential DISCUSS position.

> In cases like this one, where a not-even-remotely-backwards-compatible=
 suite of protocol changes is being made to a protocol in a document upd=
ate whose diff [1] is basically the entire document, I don't think the p=
rinciple of ignoring existing flaws in a previous document really applie=
s. I get that both of those predicates are somewhat subjective evaluatio=
ns, and that drawing a line in a process document might be difficult; bu=
t I think that any standard, however subjective, that you would be willi=
ng to sign on to would place this document outside the category of "bis =
versions that are making small, incremental changes to existing document=
s."

> If the remedy for the flaw were a major overhaul rather than a relativ=
ely minor tweak, it would again shift the evaluation a bit; however, the=
 na=C3=AFve band-aid solution of moving CT endpoints to live under "/.we=
ll-known/ct" is a trivial change, both for this document and for impleme=
ntations (in fact, for implementations, it can generally be accomplished=
 with a configuration tweak rather than writing new code). To be clear, =
this is a textbook example of the kind of situation URI templates were d=
esigned for, but that would require substantially more work than simply =
moving it into the .well-known tree. Either approach would address the U=
RI ownership issue.

I am in full agreement with this.

--6462d9b790f348a8ad377b6a8f2ec418
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Wed, Mar 13,=
 2019, at 5:26 PM, Adam Roach wrote:<br></div><blockquote type=3D"cite" =
id=3D"fastmail-quoted"><div class=3D"fastmail-quoted-moz-cite-prefix">On=
 3/13/19 8:28 AM, Eric Rescorla
      wrote:<br></div><blockquote cite=3D"mid:CABcZeBNMt8y7EoFr3PXR84zPg=
vssp5=3DB2x7-7sQOb4wM_94RGg@mail.gmail.com" type=3D"cite"><div dir=3D"lt=
r"><div dir=3D"ltr"><br></div><div class=3D"fastmail-quoted-gmail_quote"=
><div class=3D"fastmail-quoted-gmail_attr" dir=3D"ltr">On Tue, Mar 12, 2=
019 at
            11:36 PM Adam Roach via Datatracker &lt;<a href=3D"mailto:no=
reply@ietf.org">noreply@ietf..org</a>&gt;
            wrote:<br></div><blockquote style=3D"margin-top:0px;margin-r=
ight:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;borde=
r-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex=
;" class=3D"fastmail-quoted-gmail_quote"><div><br></div><div>-----------=
-----------------------------------------------------------<br></div><di=
v> DISCUSS:<br></div><div> ---------------------------------------------=
-------------------------<br></div><div> <br></div><div> Thanks to every=
one who worked on updating this protocol to
            reflect experience<br></div><div> gathered from the initial =
CT protocol. I have one blocking
            comment, and a small<br></div><div> number of editorial sugg=
estions.<br></div><div> <br></div><div> --------------------------------=
-------------------------------------------<br></div><div> <br></div><di=
v> =C2=A75:<br></div><div> <br></div><div> &gt;&nbsp; Clients are config=
ured with a base URL for a log and
            construct URLs<br></div><div> &gt;&nbsp; for requests by app=
ending suffixes to this base URL.&nbsp;
            This structure<br></div><div> &gt;&nbsp; places some degree =
of restriction on how log operators
            can deploy<br></div><div> &gt;&nbsp; these services, as note=
d in [RFC7320].&nbsp; However,
            operational<br></div><div> &gt;&nbsp; experience with versio=
n 1 of this protocol has not
            indicated that<br></div><div> &gt;&nbsp; these restrictions =
are a problem in practice.<br></div><div> <br></div><div> The synthesis =
of URLs by a protocol in this fashion is
            prohibited by BCP 190:<br></div><div> <br></div><div> &nbsp;=
 &nbsp;Scheme definitions define the presence, format, and
            semantics of a<br></div><div> &nbsp; &nbsp;path component in=
 URIs; all other specifications MUST NOT
            constrain,<br></div><div> &nbsp; &nbsp;or define the structu=
re or the semantics for any path
            component.<br></div><div> <br></div><div> Unless the intenti=
on of this document is to update BCP 190
            to change this<br></div><div> normative requirement, we can'=
t publish it in its current
            form. Note that doing<br></div><div> so would require a chan=
ge of venue, as updates to BCP 190
            would not be covered<br></div><div> by the current TRANS cha=
rter.<br></div><div> <br></div><div> Please see BCP 190 section 3 for al=
ternate approaches. All
            three approaches<br></div><div> could be made to work for CT=
, and I would be happy to
            explain how to do so if<br></div><div> clarification is desi=
red.<br></div></blockquote><div><br></div><div>While I agree that this i=
s forbidden by BCP 190, this
            structure is inherited from<br></div><div>RFC 6962, which pr=
edated 7320, so making that change
            seems like it's going<br></div><div>to be fairly disruptive.=
 This seems like it is falling
            into our discussion the other<br></div><div>day about what m=
ust be changed in -bis documents.<br></div></div></div></blockquote><p>I=
 think the timing of this document is fortuitous, in that it can
      help inform that conversation. In particular, this situation helps=

      me better understand why both you and Benjamin raised objections
      to the high-level proposal that unchanged parts of -bis documents
      shouldn't be subject to DISCUSS positions. The take-away that I
      plan to bring to that conversation is that such a decision needs
      to be informed by (a) scope of changes between a document and its
      -bis, and (b) scope of changes required to satisfy a potential
      DISCUSS position.<br></p><p>In cases like this one, where a
      not-even-remotely-backwards-compatible suite of protocol changes
      is being made to a protocol in a document update whose diff [1] is=

      basically the entire document, I don't think the principle of
      ignoring existing flaws in a previous document really applies. I
      get that both of those predicates are somewhat subjective
      evaluations, and that drawing a line in a process document might
      be difficult; but I think that any standard, however subjective,
      that you would be willing to sign on to would place this document
      outside the category of "bis versions that are making small,
      incremental changes to existing documents."<br></p><p>If the remed=
y for the flaw were a major overhaul rather than a
      relatively minor tweak, it would again shift the evaluation a bit;=

      however, the na=C3=AFve band-aid solution of moving CT endpoints t=
o
      live under "/.well-known/ct" is a trivial change, both for this
      document and for implementations (in fact, for implementations, it=

      can generally be accomplished with a configuration tweak rather
      than writing new code). To be clear, this is a textbook example of=

      the kind of situation URI templates were designed for, but that
      would require substantially more work than simply moving it into
      the .well-known tree. Either approach would address the URI
      ownership issue.<br></p></blockquote><div>I am in full agreement w=
ith this.<br></div><div><br></div></body></html>
--6462d9b790f348a8ad377b6a8f2ec418--


From nobody Wed Mar 13 17:10:41 2019
Return-Path: <noreply@ietf.org>
X-Original-To: trans@ietf.org
Delivered-To: trans@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 28001131110; Wed, 13 Mar 2019 17:10:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jana Iyengar via Datatracker <noreply@ietf.org>
To: <tsv-art@ietf.org>
Cc: draft-ietf-trans-rfc6962-bis.all@ietf.org, trans@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Jana Iyengar <jri.ietf@gmail.com>
Message-ID: <155252223906.24967.13703742248115518247@ietfa.amsl.com>
Date: Wed, 13 Mar 2019 17:10:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/cRqcZi0i0ZUBTMt8GY2UGROHymQ>
Subject: [Trans] Tsvart last call review of draft-ietf-trans-rfc6962-bis-31
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 14 Mar 2019 00:10:39 -0000

Reviewer: Jana Iyengar
Review result: Ready

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

This document is very clearly written and explains the goals of Certificate
Transparency, the mechanisms by which the goals are accomplished, and details
for implementing various CT components.

My comments below are perhaps worth addressing in the draft, but they aren't
critical.

1/ Section 4 discusses log format and operation, but it is predominantly about
format.  Section 4.13 is entirely an operational consideration, and it sticks
out a bit. It left me thinking if it made sense to separate it out into an "Log
Operational Considerations" section. It might be an overkill to have a separate
section, but see below for more.

2/ Are there other operational considerations worth talking about?  Are there,
for instance, DoS vectors that a Log operator needs to be aware of that might
be specific to running a Log?

3/ How many logs should a submitter submit a newly issued certificate to? What
are the considerations here? I did not see any recommendations for submitters.
Is this worth discussing in the document?

4/ I was wondering what might happen if cert lifetimes were too small. What are
the consequences? Is there value in discussing this?


From nobody Thu Mar 14 06:09:22 2019
Return-Path: <noreply@ietf.org>
X-Original-To: trans@ietf.org
Delivered-To: trans@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C02B1130DC4; Thu, 14 Mar 2019 06:09:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-trans-rfc6962-bis@ietf.org, Paul Wouters <paul@nohats.ca>, trans-chairs@ietf.org, paul@nohats.ca, trans@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <155256895272.2621.1849917214823286530.idtracker@ietfa.amsl.com>
Date: Thu, 14 Mar 2019 06:09:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/qiURoDHiWrP1l7X3WY9RRvYrWFg>
Subject: [Trans] Alexey Melnikov's Discuss on draft-ietf-trans-rfc6962-bis-31: (with DISCUSS and COMMENT)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 14 Mar 2019 13:09:13 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-trans-rfc6962-bis-31: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

I think this is an important document and I am looking forward to seeing it as
a Proposed Standard in the future. However, it has a good number of editorial
issues that make the document hard to read and implement.

5.  Log Client Messages

   type:  A URN reference identifying the problem.  To facilitate
      automated response to errors, this document defines a set of
      standard tokens for use in the "type" field, within the URN
      namespace of: "urn:ietf:params:trans:error:".

I think you need to register this in
<https://www.iana.org/assignments/params/params.xhtml#params-1>

Also, can you clarify whether error need an IANA registry?


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

General:

STH is only defined in the table of Content! Please define it early in the
document (before the "Changes since v1" section), so that it would be easier to
understand for somebody who is new to this.

"LSB" is never defined.

It might be just me, but I don't know what is the meaning of the ":" operation
for an expression "A : B" outside of an index.

DER encoding needs a Normative Reference.

TLS 1.2 needs at least an Informative Reference.

In 4.1: URL needs a reference.

In 4.1:
 What is the typical resolution for Maximum Merge Delay? 10 seconds? 20 minutes?

In 4.3:

   This prevents the CA from avoiding blame by logging a partial or empty chain.

"prevents the CA from avoiding blame" reads very awkwardly, maybe rephrase?

4.4.  Log ID

   Each log is identified by an OID, which is one of the log's
   parameters (see Section 4.1) and which MUST NOT be used to identify
   any other log.  A log's operator MUST either allocate the OID
   themselves or request an OID from the Log ID Registry (see
   Section 10.6.1).  Various data structures include the DER encoding of
   this OID, excluding the ASN.1 tag and length bytes,

OID encoding in DER really needs a normative reference.

5.  Log Client Messages

   Messages are sent as HTTPS GET or POST requests.  Parameters for
   POSTs and all responses are encoded as JavaScript Object Notation
   (JSON) objects [RFC8259].  Parameters for GETs are encoded as order-
   independent key/value URL parameters, using the "application/x-www-
   form-urlencoded" format described in the "HTML 4.01 Specification"
   [HTML401].  Binary data is base64 encoded [RFC4648] as specified in

Please clarify whether you are using Section 4 or Section 5 version of base64.
Also, are the trailing "=" expected in values?

   the individual messages.

   Note that JSON objects and URL parameters may contain fields not
   specified here.  These extra fields SHOULD be ignored.

Why not "MUST be ignored"? This is important for forward compatibility.

8.1.6.  Evaluating compliance

   A TLS client can only evaluate compliance if it has given the TLS
   server the opportunity to send SCTs and inclusion proofs by any of
   the three mechanisms that are mandatory to implement for CT-using TLS
   clients (see Section 8.1.1).  Therefore, a TLS client MUST NOT
   evaluate compliance if it did not include both the

Maybe "evaluate" above is a wrong verb, I think "enforce" would be better here.

   "transparency_info" and "status_request" TLS extensions in the
   ClientHello.

8.2.  Monitor

   1.  Fetch the current STH (Section 5.2).  Repeat until the STH
       changes.

I think the above text should recommend how often the client should poll for
this.



From nobody Thu Mar 14 06:50:12 2019
Return-Path: <noreply@ietf.org>
X-Original-To: trans@ietf.org
Delivered-To: trans@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 57829129B88; Thu, 14 Mar 2019 06:50:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-trans-rfc6962-bis@ietf.org, Paul Wouters <paul@nohats.ca>, trans-chairs@ietf.org, paul@nohats.ca, trans@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
Message-ID: <155257141035.2645.11460081509986673853.idtracker@ietfa.amsl.com>
Date: Thu, 14 Mar 2019 06:50:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/0R9dKzZ4h2bLQX4pyHqwdA4uVdo>
Subject: [Trans] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-ietf?= =?utf-8?q?-trans-rfc6962-bis-31=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 14 Mar 2019 13:50:10 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-trans-rfc6962-bis-31: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

There was a presentation at maprg IETF 103 about the question if CT helps
attackers to find new domains. I think this risk should at least be mentioned
in the security considerations section.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

 1) I found section 2 a bit hard to follow. Would it maybe be possible to
 provide more textual explanation of the algorithms instead of just describing
 the steps of the algorithms? Also I was wondering how much much these
 algorithms are actually „part“ of the protocol spec…? Are could these be
 rather seen as example algorithms? Maybe that could be further clarified

 2) Please expand STH on first occurrence (in sec 4.1)

 3) Sec 4.4: „A log's operator MUST either allocate the OID
    themselves or request an OID from the Log ID Registry (see
    Section 10.6.1).“
Isn't there an obligation to register?

 4) sec 4.8: „If an
   implementation sees an extension that it does not understand, it
   SHOULD ignore that extension.“
Maybe it’s just me because I may have missed some context but does „ignore“
mean here that it should log it or not?

 5) sec 5: „MAY retry the same
   request without modification at a later date.“
Would it be possible to provide a recommendation how long the client should
wait?

 6) sec 5.6: „Logs MAY restrict the number of entries that can be retrieved per
   "get-entries" request.“
Should this be added to sec 4.1?

 7) sec 10.3: Couldn’t you use the TLS  SignatureScheme Registry directly
 (instead of forming an own registry)?

 8) sec 10.4: i Wonder if an RFC-required policy wouldn’t be more appropriate
 for the VersionedTransTypes registry?

 9) sec 10.6.1:I guess  the registration policy is FCFS? RFC 8126 recommend to
 always (clearly) name the registry.

And finally one higher level question mainly out of curiosity: was it
considered to e.g. use json for all data structures? Is there a performance
reason to not do that or wasn’t that even discussed?



From nobody Thu Mar 14 07:09:37 2019
Return-Path: <noreply@ietf.org>
X-Original-To: trans@ietf.org
Delivered-To: trans@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5617A130E5B; Thu, 14 Mar 2019 07:09:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-trans-rfc6962-bis@ietf.org, Paul Wouters <paul@nohats.ca>, trans-chairs@ietf.org, paul@nohats.ca, trans@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <155257256734.2691.16242192957909565560.idtracker@ietfa.amsl.com>
Date: Thu, 14 Mar 2019 07:09:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/2Sc26GMFwQnTRl5DEEk_-51ABFU>
Subject: [Trans] Benjamin Kaduk's Discuss on draft-ietf-trans-rfc6962-bis-31: (with DISCUSS and COMMENT)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 14 Mar 2019 14:09:28 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-trans-rfc6962-bis-31: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

First off, thanks for this well-written document!  I intend to ballot Yes,
but there are a few issues that need to be resolved first.

Sections 4.11 and 4.12 have arrays of NodeHash to carry consistency and
inclusion proofs, respectively, with minimum array size of 1.  However,
Sections 2.1.4.1 and 2.1.3.1 (respectively) seem to admit the
possibility of zero-length proofs in degenerate cases, which the
aforementioned protocol description language forbids the conveyance of.
(Section 5.3 explicitly requires the use of an empty consistency proof.)
Do those minimum array sizes need to be (implicit) zero?
(If they do not, it seems that a minimum size of 32 would have the same
effect as that of one, since a NodeHash has minimum size 32.)

I support Alexey's Discuss regarding the registration of a
"urn:ietf:params:trans:error" URN namespace.

In Section 6:

   o  An Online Certificate Status Protocol (OCSP) [RFC6960] response
      extension (see Section 7.1.1), where the OCSP response is provided
      in the "CertificateStatus" message, provided that the TLS client
      included the "status_request" extension in the (extended)
      "ClientHello" (Section 8 of [RFC6066]).  [...]

This is not quite a TLS 1.3-compliant formulation -- TLS 1.3 does not
use the "CertificateStatus message", but rather uses the encoding of
that structure in a status_request extension in the CertificateEntry.

I also think we need greater clarity on the (non-)usage of CT for TLS
client certificates; see COMMENT

I also support Alissa's Discuss.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Since the 64-bit timestamp format (milliseconds since epoch) is used in
multiple places, there is perhaps room for consolidation into a single
definition.

Section 1

Do we need to provide a definition or reference for "public
certification authority"?

   It is necessary to treat each log as a trusted third party, because
   the log auditing mechanisms described in this document can be
   circumvented by a misbehaving log that shows different, inconsistent
   views of itself to different clients.  Whilst it is anticipated that
   additional mechanisms could be developed to address these
   shortcomings and thereby avoid the need to blindly trust logs, such
   mechanisms are outside the scope of this document.

Doesn't Section 11.3 discuss/link to some (partial) mechanisms to detect
misbehaving logs?  It's not clear that "anticipated" is quite the right
terminology to use here, then...

Section 2.1.1

   We have established a registry of acceptable hash algorithms (see
   Section 10.2).  [...]

It's not clear that we need to use the first person here.

Section 2.1.2

   When a client has a complete list of n input "entries" from "0" up to
   "tree_size - 1" and wishes to verify this list against a tree head
   "root_hash" returned by the log for the same "tree_size", the
   following algorithm may be used:

This seems to imply that n equals "tree_size"; do we want to normalize
to one name or the other?

   3.  If there is more than one element in the "stack", repeat the same
       merge procedure (Step 2.3 above) until only a single element
       remains.

nit: we just want the sub-sub-bullets of 2.3, and not the "repeat
merge_count times" part, since "merge_count" is not defined in this
scope?

Section 2.1.3.2

IMPORTANT: We need to define/specify what "leaf_index" is.

Section 2.1.4.1

   SUBPROOF(m, D[m], true) = {}

I don't remember seeing the "D[m]" notation defined; is this a typo for
something else?

   If m <= k, the right subtree entries D[k:n] only exist in the current
   tree.  We prove that the left subtree entries D[0:k] are consistent
   and add a commitment to D[k:n]:

   SUBPROOF(m, D_n, b) = SUBPROOF(m, D[0:k], b) : MTH(D[k:n])

This 'b' is always 'false', right?

Section 2.2

   Various data structures Section 1.2 are signed.  A log MUST use one
   of the signature algorithms defined in Section 10.3.

A literal reading of this forbids any algorithms registered in the
future but not listed in this document; we probably want to say "listed
in the registry defined in".

Section 3.2

   o  "SignedData.digestAlgorithms" MUST only include the
      "SignerInfo.digestAlgorithm" OID value (see below).

nit: this could be misread as saying that there is a single
distinguished OID that has symbolic name "SingerInfo.digestAlgorithm";
we just want this one to match the one in the SignerInfo in the
SignedData.signerInfos, so maybe something about "same as" would avoid
the ambiguity.

Section 4.1

   Maximum Chain Length:  The longest chain submission the log is
      willing to accept, if the log imposes any limit.

Is the absence of a limit indicated by the absence of the parameter or a
distinguished sentinel value?

   Final STH:  If a log has been closed down (i.e., no longer accepts
      new entries), existing entries may still be valid.  In this case,
      the client should know the final valid STH in the log to ensure no
      new entries can be added without detection.  The final STH should
      be provided in the form of a TransItem of type
      "signed_tree_head_v2".

Is this a lowercase "should" or a "SHOULD" or a "MUST"?  (How else would
it be provided?)

Do we need to say that the Final STH is not provided for a log that is
still accepting submissions?

Section 4.4

   Note that the ASN.1 length and the opaque vector length are identical
   in size (1 byte) and value, so the DER encoding of the OID can be
   reproduced simply by prepending an OBJECT IDENTIFIER tag (0x06) to
   the opaque vector length and contents.

nit: maybe "full DER encoding (including tag and length)" to contrast
with the previous paragraph?

   OIDs used to identify logs are limited such that the DER encoding of
   their value is less than or equal to 127 octets.

This seems to be a new requirement to this spec, in which case RFC 2119
language would be appropriate?

Section 4.7

   "sct_extensions" matches the SCT extensions of the corresponding SCT.

Is this supposed to imply the ordering and non-duplication requirements?
(If it does not, then recreating the log entry from the SCT for
signature validation could prove difficult.)

Sections 4.9, 4.10

Do we really want to allow for zero-length signatures in the structure
definition?

Section 4.11

   "consistency_path" is a vector of Merkle Tree nodes proving the
   consistency of two STHs.

A backreference to Section 2.1.4 might be helpful.

Section 4.12

   "inclusion_path" is a vector of Merkle Tree nodes proving the
   inclusion of the chosen certificate or precertificate.

A backreference to Section 2.1.3 might be helpful.

Section 5

Sometimes documents using base64 note explicitly that the padding
characters are (or aren't) included; 4648 is fairly clear that the
default is to include the padding characters, so there isn't necessarily
any change needed here.

Section 5.1

      chain:  An array of zero or more base64 encoded CA certificates.
         The first element is the certifier of the "submission"; the
         second certifies the first; etc.  The last element of "chain"
         (or, if "chain" is an empty array, the "submission") is
         certified by an accepted trust anchor.

I'm reading this to be a JSON array of strings; is that correct, and do
we want to be more explicit about it ("no" may well be fine)?

   If "submission" is an accepted trust anchor whose certifier is
   neither an accepted trust anchor nor the first element of "chain",
   then the log MUST return the "unknown anchor" error.  A log cannot
   generate an SCT for a submission if it does not have access to the
   issuer's public key.

Is this a descriptive "cannot" or a normative "MUST NOT"?

   If the returned "sct" is intended to be provided to TLS clients, then
   "sth" and "inclusion" (if returned) SHOULD also be provided to TLS
   clients (e.g., if "type" was 2 (for "precert_sct_v2") then all three
   "TransItem"s could be embedded in the certificate).

nit: the grammar is a bit weird around the second "then", maybe ", so
that" is easier to read?

Section 5.4

IMPORTANT: The input to get-proof-by-hash has a "tree_size" but the
processing discussion refers to a single "requested STH".  It does not
seem like the one uniquely determines the other, since there could be
multiple valid STHs for a given tree size (e.g., if there are no
submissions for more than the MMD).  Is the intent to supply an STH as
input, or is there otherwise need for further clarity here?

      inclusion:  A base64 encoded "TransItem" of type
         "inclusion_proof_v2" whose "inclusion_path" array of Merkle
         Tree nodes proves the inclusion of the chosen certificate in
         the selected STH.

We don't seem to define "chosen certificate"; do we just want to refer
to the (input) leaf hash?

Section 5.5

[similar note about tree_size/STH mapping]

Similarly, we talk about "index of requested hash", which is at least
unambiguous (IIUC), but we don't give a description of how the server
could/should determine.

[same comment about "chosen certificate"]

Section 5.6

         submitted_entry:  JSON object representing the inputs that were
            submitted to "submit-entry", with the addition of the trust

What does "representing" mean?  (In particular, does it use the same
JSON structure?)

Section 5.7

There is not a note here about how no signature is required on the
results, and in fact this data does seem to only be authenticated by the
surrounding TLS connection.  Perhaps it's worth making a note of that.

Section 6

   CT-using TLS servers MUST use at least one of the three mechanisms
   listed below to present one or more SCTs from one or more logs to
   each TLS client during full TLS handshakes, where each SCT

This MUST may need some caveats, given that the server can't use TLS
extensions not offered first by the client.  So maybe it has to be
"each CT-using TLS client".

Section 6.1

   o  One or more logs may not have become acceptable to all CT-using
      TLS clients.

nit: are we concerned about (new?) logs potentially becoming acceptable
to clients, or logs acceptable to clients becoming no longer accepted
(or both)?

Section 6.3

   In each "TransItemList" that is sent to a client during a TLS

nit: I don't know that "to a client" is needed; the server can just as
well use CT for client certificates, right?

   o  The TLS server MUST construct a "TransItemList" of relevant
      "TransItem"s (see Section 6.3), which SHOULD omit any "TransItem"s
      that are already embedded in the server certificate or the stapled
      OCSP response (see Section 7.1).  If the constructed
      "TransItemList" is not empty, then the TLS server MUST include the
      "transparency_info" extension with the "extension_data" set to
      this "TransItemList".

Am I allowed to send an empty "transparency_info" extension if the
TransItemList is empty?

   TLS servers MUST only include this extension in the following
   messages:

   o  the ServerHello message (for TLS 1.2 or earlier).

   o  the Certificate or CertificateRequest message (for TLS 1.3).

Servers sending it in CR implies that clients can send it in Certificate
(heh, the normal "CT" abbreviation is not really usable in this
context), but we don't explicitly say that.

Section 10.3

I'm confused by this registry.  Is the SignatureScheme value required to
come from/match the TLS SignatureScheme registry?  Is anything going to
key off that value or otherwise use the value in a protocol data
structure?  (Why are there two entries for 0x0403?)

Section 10.5

   All OIDs in the range from 1.3.101.8192 to 1.3.101.16383 have been
   reserved.  This is a limited resource of 8,192 OIDs, each of which
   has an encoded length of 4 octets.

The table says "Unassigned"; which is it?

Section 11.1

This seems to be making some unstated assumptions, including perhaps
that someone has actually submitted the misissued certificate in
question to a log (in order to support the claim that the maximum time
it can be used without audit is twice the MMD).

Section 11.3

We may want to note the potential privacy concerns relating to gossip
and similar mechanisms, at least in passing.  I do see Section 11.4,
though there's not a terribly tight linkage in the text, and 11.4 may
not have comprehensive coverage of all privacy considerations.

Section 13.2

I think that RFCs 6234 and 6979 may need to be normative, since they're
needed for the signature/hash algorithms that are specified for use.



From nobody Thu Mar 21 03:47:36 2019
Return-Path: <xramtsov@gmail.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 CE459130EC7 for <trans@ietfa.amsl.com>; Thu, 21 Mar 2019 03:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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=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 f8mZYqTa9B8h for <trans@ietfa.amsl.com>; Thu, 21 Mar 2019 03:47:33 -0700 (PDT)
Received: from mail-yw1-xc31.google.com (mail-yw1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) (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 41D4B1274A1 for <trans@ietf.org>; Thu, 21 Mar 2019 03:47:33 -0700 (PDT)
Received: by mail-yw1-xc31.google.com with SMTP id u197so539142ywf.3 for <trans@ietf.org>; Thu, 21 Mar 2019 03:47:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=date:from:subject:to:message-id:mime-version; bh=mqVN9FaC76X0GcMdmju4jyQy76qCxLAUbeEr2Y6dBqE=; b=BSgy0vTYDNR3wvZOZVOpDXIMZ6nfZcFStj4NnjIH4WZga+HGWhTxAUHMphGI842u+V 1Vt8njpwEJe+m4iuoHRbQPIsHCciX+aFgmJZhuXJ7RXRJmK1jtG3FlnhG/lrBP+on3HX 1TUpnVOINkmrIJdwhrk6fb8CSDUZ5iVNoMBSgM99shXKeEpoapqxKma9aVNbt0/u1OWJ 06IlVVyuaTEIt6sLty50IuuFRT1fDDGtLPmNxSQbpFRWhuf84SdcOkWt6WD4/Tjnbv4c ktSzS8/RLmDRfKLGMYGoG0Xvw7H7+EPZN4EwXgfLagtHryKt+NT2+VpXFEmvKMY3lt5Q 75aA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:message-id:mime-version; bh=mqVN9FaC76X0GcMdmju4jyQy76qCxLAUbeEr2Y6dBqE=; b=sTLcvWDJRexV8r6AxD1iL7387iUu0tuNBu7IRF5GWDGIzbjmDq8/leBPfItcrxIyFG McLtH038JgEw7HXZ6Tqw6G2nvD6/6m0JecXTf0QJgE3MqzpVZrK6LGl0u5Gk6aR03Kc3 LVzFCvrlG4ZPpuazkUs/5gJ5xNvU1Ek95He3kMJ8qwMvKJj8G4lZtOWB9YnxwNX60VGX 54ZYVw5rUsLthPnXTiNqf6qQqIBjvKDQe7y8x0Gb6+cCd1/ZBkdUl8Tw1yBjiyn+ALlo cut3jKI/kWL6mbVfR/qkwznxeqEL+K+eEfdzHmSJV/ikhkxWS6PBRkcKwd2ESOb4GQUE EJ+Q==
X-Gm-Message-State: APjAAAWrdLlu4TLD0dVFQPLzSAx0jgVWoSKQyNWJ94wWNTQeQBYw1GzN 6eCg27WTJ1bLaB1wr6gJOQamDqyK
X-Google-Smtp-Source: APXvYqx1yU3w/R1eX6y/0dn1CEU/bQbiZolqfBgNop8jgsvCB1ollJbzwTeEvjRtlcrP1xwv1IeACA==
X-Received: by 2002:a25:b1a1:: with SMTP id h33mr2192317ybj.270.1553165252269;  Thu, 21 Mar 2019 03:47:32 -0700 (PDT)
Received: from [192.168.1.102] ([185.155.18.125]) by smtp.gmail.com with ESMTPSA id q9sm2288420ywq.88.2019.03.21.03.47.30 for <trans@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 21 Mar 2019 03:47:31 -0700 (PDT)
Date: Thu, 21 Mar 2019 13:47:28 +0300
From: Evgeny <xramtsov@gmail.com>
To: trans@ietf.org
Message-Id: <1553165248.1179.0@smtp.gmail.com>
X-Mailer: geary/0.12.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/a8KIReZTGySvgt2OLB00s5VUPIU>
Subject: [Trans] Long Poll
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 21 Mar 2019 10:47:35 -0000

I briefly read the rfc6962-bis I-D and didn't find whether it is 
possible to continuosly receive new entries. In Section 5.2 there is 
"/ct/v2/get-entries" request, but seems like it instantly returns 
entries or just an empty result. Is it possible to retrieve new entries 
via "long poll"? If not, is it planned to add this functionality to the 
spec? I find it weird to constantly issue GET requests in a loop.


From nobody Thu Mar 21 09:04:38 2019
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 25D34131450 for <trans@ietfa.amsl.com>; Thu, 21 Mar 2019 09:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level: 
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] 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 6WWyo-BNUBur for <trans@ietfa.amsl.com>; Thu, 21 Mar 2019 09:04:27 -0700 (PDT)
Received: from mail-yw1-xc2e.google.com (mail-yw1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) (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 17952131368 for <trans@ietf.org>; Thu, 21 Mar 2019 09:04:10 -0700 (PDT)
Received: by mail-yw1-xc2e.google.com with SMTP id v127so5125552ywe.13 for <trans@ietf.org>; Thu, 21 Mar 2019 09:04:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PllxSdX5ZSSgJhkGOv8PzXcWR1uNXoXSOlpJ2WmpiSQ=; b=Mm8nGiiSjNbgTot5shfFo4T7iJ2qWcTFok7X1bZnL4mzgbdC/+ZrmipCNPvneCiASZ az81zOJiEcOo8jg5qbKHF8widSvcFXjagtr4ppJjfH3wXP2Sq2MPlWqHgrpB3GsOWnOk s+WaQ3Ub64Fg5t0eL35T14k89a+29vsQ/yJIa87cIWnaLNBWPIjLnRRzEfyZXfa5x0SX yfqkK6OngRChGAVQC1eEE20w8CCPW8xfyRvMqGWLxwpwXiNSIum9BaXmi+SUxUK2k4MK RXp96L1YDDFO9UWib+cremZkxQpHlA1I3S57iNtDDxDzbEcnlbhrVVqv2/i7/T10wumh p7bg==
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=PllxSdX5ZSSgJhkGOv8PzXcWR1uNXoXSOlpJ2WmpiSQ=; b=Y3ld0JUs1/WDoyBAp6qgkSAovUeIbvtWdIQbNDuBDLRRy49wq/irS8C5QPPb55t7dO CDlPI0uOyTMDv/Drwtvo/Fb92khKOs9BbWChODz8Q7aQy3c0L0wq+4sJXY6Gs2QybaXk tRjrXMhtZOwt2xZAKlIGmFBTb8eVKJgrURSjJmd6vkgw1NDLZoK3V4yHJXcyJaR+MZbC r90UH4QuaKSMjI877oKKSGbsOyGXwgYzLdPHQT0bOPwOKqSdRoiMkfcDeFZedRrVlmOt GgL5eq86UkbSdkpzDo3abMKdv1wrzbq8dBx7IaatvApNRJm1hp0oAUnGNvXyEUufc7u+ eV3g==
X-Gm-Message-State: APjAAAUWbkP1sTUpFRDPsK5fJwn+eA/PkQbGugmGFwtEzj+DlECIsolo Q6CpPHRNtJgcOAvyZCw6+S77rzQxWSxyNkW1BkEKBQ==
X-Google-Smtp-Source: APXvYqy32CLT+3ij3OpKBqbGHuAIcch8OTkS9zqjx3GzN/D+FdatWWN32RA0lfcP/QENifK56KeXScGCLKbOPXS42Jo=
X-Received: by 2002:a81:9484:: with SMTP id l126mr3583698ywg.209.1553184248942;  Thu, 21 Mar 2019 09:04:08 -0700 (PDT)
MIME-Version: 1.0
References: <1553165248.1179.0@smtp.gmail.com>
In-Reply-To: <1553165248.1179.0@smtp.gmail.com>
From: Eran Messeri <eranm@google.com>
Date: Thu, 21 Mar 2019 16:03:44 +0000
Message-ID: <CALzYgEfEgO2R_SwsAE-UtqV0rPAX9trcREt2jCTw_i1OHsXQFg@mail.gmail.com>
To: Evgeny <xramtsov@gmail.com>
Cc: "trans@ietf.org" <trans@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006e386205849ce313"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/mUoPNoDdlML8sTHRAG-__5kCnL0>
Subject: Re: [Trans] Long Poll
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 21 Mar 2019 16:04:36 -0000

--0000000000006e386205849ce313
Content-Type: text/plain; charset="UTF-8"

To put simply, the answer is no, there's no "long poll" endpoint and no
plan to add it to the spec.

The reason is it doesn't make sense to ask for new entries unless you know
they're there - by first calling get-sth to learn of a new tree head.

Generally the protocol is designed for auditing for tree consistency by a
client/monitor that observes STHs, fetches entries for the tree at the
specified size and validates the root hash published matches the one
calculated from the entries.

IIRC there are monitors that offer a polling service.

On Thu, Mar 21, 2019 at 10:47 AM Evgeny <xramtsov@gmail.com> wrote:

> I briefly read the rfc6962-bis I-D and didn't find whether it is
> possible to continuosly receive new entries. In Section 5.2 there is
> "/ct/v2/get-entries" request, but seems like it instantly returns
> entries or just an empty result. Is it possible to retrieve new entries
> via "long poll"? If not, is it planned to add this functionality to the
> spec? I find it weird to constantly issue GET requests in a loop.
>
> _______________________________________________
> Trans mailing list
> Trans@ietf.org
> https://www.ietf.org/mailman/listinfo/trans
>

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

<div dir=3D"ltr">To put simply, the answer is no, there&#39;s no &quot;long=
 poll&quot; endpoint and no plan to add it to the spec.<div><br></div><div>=
The reason is it doesn&#39;t make sense to ask for new entries unless you k=
now they&#39;re there - by first calling get-sth to learn of a new tree hea=
d.</div><div><br></div><div>Generally the protocol is designed for auditing=
 for tree consistency by a client/monitor that observes STHs, fetches entri=
es for the tree at the specified size and validates the root hash published=
 matches the one calculated from the entries.</div><div><br></div><div>IIRC=
 there are monitors that offer a polling service.=C2=A0</div></div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Mar 21=
, 2019 at 10:47 AM Evgeny &lt;<a href=3D"mailto:xramtsov@gmail.com">xramtso=
v@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">I briefly read the rfc6962-bis I-D and didn&#39;t find whether i=
t is <br>
possible to continuosly receive new entries. In Section 5.2 there is <br>
&quot;/ct/v2/get-entries&quot; request, but seems like it instantly returns=
 <br>
entries or just an empty result. Is it possible to retrieve new entries <br=
>
via &quot;long poll&quot;? If not, is it planned to add this functionality =
to the <br>
spec? I find it weird to constantly issue GET requests in a loop.<br>
<br>
_______________________________________________<br>
Trans mailing list<br>
<a href=3D"mailto:Trans@ietf.org" target=3D"_blank">Trans@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/trans" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/trans</a><br>
</blockquote></div>

--0000000000006e386205849ce313--


From nobody Thu Mar 21 09:41:54 2019
Return-Path: <xramtsov@gmail.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 2F6FA1313CE for <trans@ietfa.amsl.com>; Thu, 21 Mar 2019 09:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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=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 ymFV8PMfCaWJ for <trans@ietfa.amsl.com>; Thu, 21 Mar 2019 09:41:49 -0700 (PDT)
Received: from mail-yw1-xc34.google.com (mail-yw1-xc34.google.com [IPv6:2607:f8b0:4864:20::c34]) (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 6765E1313CB for <trans@ietf.org>; Thu, 21 Mar 2019 09:41:45 -0700 (PDT)
Received: by mail-yw1-xc34.google.com with SMTP id w66so5265631ywd.4 for <trans@ietf.org>; Thu, 21 Mar 2019 09:41:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=date:from:subject:to:message-id:in-reply-to:references:mime-version;  bh=0dPv5P6W3fvzAWCK4miGNpuh7cjeXPD0Pvdhqt+c/EQ=; b=kEK9ufEXQY7s39+2aKDigdh4wx489J6ecBFhTv6G0ToJDjEEZkuZZ2B03KcUWXsIGN EPGFPj+g6srXr4uFrNzbPazMirh0NTqgo+Qixl763wExa9Ha5yMqnQR7DWp3wGqu1crO Q+6rJXmGwCWrmDYNHH1VC+bh971wL5DmbuYMVJx8t9N8aaAr7Fi/ayVHhrq6TPmaRw0q z3V2G+r/r0/mSEW0jOgc2E9XgkQhcUOdU1LECYFfRy/S7SmvJBMi8Xh3+WOi/RZM5/SL lwpo2lClsvTyfP/frmV2bmBMZucPvDJG+Tlf0uEmRBibY1IjRvJH7vdBHA2LhxVjEGMy 5Clw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:message-id:in-reply-to :references:mime-version; bh=0dPv5P6W3fvzAWCK4miGNpuh7cjeXPD0Pvdhqt+c/EQ=; b=k6wogSNxy3XbkB1o7tPCmh0NHnXthzHdaa3JwclWgHccRuZRKxnMF8DmOT3uqMrbNX t73YpFM5cwhG4cPfkbWs+UEGsBbq2vd9uy2Aprli4e+pQtXyssq/YtYnO65IA5m9vfQc TqcsJPVJKfWWD8VZPIfUSw2cIRC1ptYh3tFv7yek08GP2se6/md3epBQ5LdbREDb6P8p +n2g89QoEd7Zmi1p4w34htgG3OmxKdrADQBZTkY6x2/OxFe19MYu/YxboEKajLCCamJ3 yJG5eRwGsUjk2PSezgYTeI7kslO7cVcslinxUBy14enuH1C0u6/DWxTmeGoALMMviuC9 1k2A==
X-Gm-Message-State: APjAAAUaDue5t0fo37A0ozXo18vj+F3YTQ0CWP274G7R3MRav9XUmCbo eCQjdaxVDXY0n0nb6/I7XUEYDG1P
X-Google-Smtp-Source: APXvYqzSX4zmd5IZQqtcruIiT5NScjD7cv/r05ZDwTQIjxo8H6xRZ1xh8IVcNgGZGtq58Giweu6CMg==
X-Received: by 2002:a81:1155:: with SMTP id 82mr3857826ywr.92.1553186504428; Thu, 21 Mar 2019 09:41:44 -0700 (PDT)
Received: from [192.168.1.102] ([185.155.18.125]) by smtp.gmail.com with ESMTPSA id h184sm1864401ywb.23.2019.03.21.09.41.42 for <trans@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 21 Mar 2019 09:41:43 -0700 (PDT)
Date: Thu, 21 Mar 2019 19:41:40 +0300
From: Evgeny <xramtsov@gmail.com>
To: trans@ietf.org
Message-Id: <1553186500.1179.1@smtp.gmail.com>
In-Reply-To: <CALzYgEfEgO2R_SwsAE-UtqV0rPAX9trcREt2jCTw_i1OHsXQFg@mail.gmail.com>
References: <1553165248.1179.0@smtp.gmail.com> <CALzYgEfEgO2R_SwsAE-UtqV0rPAX9trcREt2jCTw_i1OHsXQFg@mail.gmail.com>
X-Mailer: geary/0.12.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/B13z0Ge6W4DOzfEzbAdfXz9XnbQ>
Subject: Re: [Trans] Long Poll
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 21 Mar 2019 16:41:53 -0000

On Thu, Mar 21, 2019 at 7:03 PM, Eran Messeri <eranm@google.com> wrote:
> The reason is it doesn't make sense to ask for new entries unless you 
> know they're there - by first calling get-sth to learn of a new tree 
> head.

In this case I can poll for get-sth, no? From section 8.2:

 > Fetch the current STH (Section 5.2).  Repeat until the STH changes.

How this "repeat" will look in practice? Like while(0) {... sleep(1)}?


From nobody Thu Mar 21 12:15:06 2019
Return-Path: <xramtsov@gmail.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 BEB8C130DE9 for <trans@ietfa.amsl.com>; Thu, 21 Mar 2019 12:15:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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=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 I_hdLOtzWTDP for <trans@ietfa.amsl.com>; Thu, 21 Mar 2019 12:15:03 -0700 (PDT)
Received: from mail-yw1-xc2a.google.com (mail-yw1-xc2a.google.com [IPv6:2607:f8b0:4864:20::c2a]) (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 0DBA112AF7F for <trans@ietf.org>; Thu, 21 Mar 2019 12:15:03 -0700 (PDT)
Received: by mail-yw1-xc2a.google.com with SMTP id a199so2475ywa.0 for <trans@ietf.org>; Thu, 21 Mar 2019 12:15:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=date:from:subject:to:message-id:in-reply-to:references:mime-version;  bh=sX6w0H19hJaWTr+7OB0OUdVABQmZegZCYCf9Ky1gjec=; b=Ps/+vDCzgb+3aWCzQoq8iJBjtyQX4rdEh0M/8SP1LD25bWKDV32Jcg1NSMTJxB3M+w JQs2mKYWjYikmfD8ljfi6EXxvUCHeltiMliJ6BOll2tsGriAEFvihTgvWirmvqvwoiKN x2tLlP2cqg8Wn1fIl+1vqkqpa5LsCL0lEZcvlyU4Sj2WK/miJosfW5wRaamhhgw+W8ow qV0CvGcfjhZgKZVWz1ZXksF8q3nUPn/fCf53IF3t+NkRKWAvPVBEAcKC5weUPgr5qO4H IigxxTz5fpVZd4p9V4tow7dIlSv8UCcZJENIT3kXA+oDXSf2UELaW2H+w35TcO9+J3ya ktGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:message-id:in-reply-to :references:mime-version; bh=sX6w0H19hJaWTr+7OB0OUdVABQmZegZCYCf9Ky1gjec=; b=P4FCKUyN5TWHvn+G8uo4cCQQN4lV1FfJv/zTx1lIROBO8mkUzTMqFqfTHeJYkSWgqs sCEqnF+Swlv7eeXjYTtNKrMGHDlvYzmbXDGjRVpQ0L1piJEeNUYqp8xqdAUm+t4gvqoI 0uXrE/cgnWAaAP0kREh1o/bM+VU2ZffPuX9jMe97yz5/JHYhqbJmVGAe5ZULCrGkTjLG RcO+0eXqZ1zm/wLAGcpaFtjhVkSRYEmQFw+4BsmjCat1yw/0/1MQOXhkMLZNnLZCwCkw icMRKJRABVraCpYQ0DvHYz3lau1vZnRMU9OxgEo/ZF/WmhccxZq9GnRSgbU4K9mhN8xI HfiA==
X-Gm-Message-State: APjAAAUqMUTXRSzEuFfxG16TgWyxl3l2gdWN4j16RwhmKYwXRZkmlzyR uSynYbIIkXm2wB32nKxxFADevATv
X-Google-Smtp-Source: APXvYqwoXRf2Rvd9PA1rqL0oAs5lYlWBLIB1wytgapxYZAUgaBpMm3T6V+tYhEJUK4k1W06bbkK1ow==
X-Received: by 2002:a25:4054:: with SMTP id n81mr4593644yba.346.1553195702132;  Thu, 21 Mar 2019 12:15:02 -0700 (PDT)
Received: from [192.168.1.102] ([185.155.18.125]) by smtp.gmail.com with ESMTPSA id h5sm3218341ywh.3.2019.03.21.12.15.00 for <trans@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 21 Mar 2019 12:15:01 -0700 (PDT)
Date: Thu, 21 Mar 2019 22:14:58 +0300
From: Evgeny <xramtsov@gmail.com>
To: trans@ietf.org
Message-Id: <1553195698.1179.2@smtp.gmail.com>
In-Reply-To: <1553186500.1179.1@smtp.gmail.com>
References: <1553165248.1179.0@smtp.gmail.com> <CALzYgEfEgO2R_SwsAE-UtqV0rPAX9trcREt2jCTw_i1OHsXQFg@mail.gmail.com> <1553186500.1179.1@smtp.gmail.com>
X-Mailer: geary/0.12.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/zaVE3hsVRXImGhOAJdfB7IArEZs>
Subject: Re: [Trans] Long Poll
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 21 Mar 2019 19:15:05 -0000

On Thu, Mar 21, 2019 at 7:41 PM, Evgeny <xramtsov@gmail.com> wrote:
> Like while(0) {... sleep(1)}?

Oops, it should have been while(1) of course :)


From nobody Fri Mar 22 09:48:27 2019
Return-Path: <rasmus.dahlberg@kau.se>
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 3A1C213129F for <trans@ietfa.amsl.com>; Fri, 22 Mar 2019 09:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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=kau.se
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 yFGIRwGUh2Us for <trans@ietfa.amsl.com>; Fri, 22 Mar 2019 09:48:22 -0700 (PDT)
Received: from smtp1.kau.se (smtp1.kau.se [130.243.21.250]) by ietfa.amsl.com (Postfix) with ESMTP id EB893131290 for <trans@ietf.org>; Fri, 22 Mar 2019 09:48:21 -0700 (PDT)
Received: from e-mailfilter02.sunet.se (e-mailfilter02.sunet.se [192.36.171.202]) by smtp1.kau.se (Postfix) with ESMTP id 146591847DBF; Fri, 22 Mar 2019 17:48:20 +0100 (CET)
Received: from Exch-A1.personal.kau (exch-a1.kau.se [130.243.19.82]) by e-mailfilter02.sunet.se (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id x2MGmIxU193437 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Fri, 22 Mar 2019 17:48:19 +0100
Received: from work (130.243.27.149) by Exch-A1.personal.kau (130.243.19.82) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1591.10; Fri, 22 Mar 2019 17:48:18 +0100
Date: Fri, 22 Mar 2019 17:48:12 +0100
From: Rasmus Dahlberg <rasmus.dahlberg@kau.se>
To: Evgeny <xramtsov@gmail.com>
CC: <trans@ietf.org>, <eranm@google.com>
Message-ID: <20190322164812.jajis3kx6qbxn25f@work>
References: <1553165248.1179.0@smtp.gmail.com> <CALzYgEfEgO2R_SwsAE-UtqV0rPAX9trcREt2jCTw_i1OHsXQFg@mail.gmail.com> <1553186500.1179.1@smtp.gmail.com> <1553195698.1179.2@smtp.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <1553195698.1179.2@smtp.gmail.com>
User-Agent: NeoMutt/20171215
X-Originating-IP: [130.243.27.149]
X-ClientProxiedBy: Exch-A1.personal.kau (130.243.19.82) To Exch-A1.personal.kau (130.243.19.82)
X-Bayes-Prob: 0.9999 (Score 5, tokens from: outbound, outbound-kau-se:default,  kau-se:default, base:default, @@RPTN)
X-p0f-Info: os=Windows 7 or 8, link=Ethernet or modem
X-CanIt-Geo: ip=130.243.27.149; country=SE; latitude=59.3247; longitude=18.0560; http://maps.google.com/maps?q=59.3247,18.0560&z=6
X-CanItPRO-Stream: outbound-kau-se:outbound (inherits from outbound-kau-se:default, kau-se:default, base:default)
X-Canit-Stats-ID: 0aXP4MjtD - 55b997887d4b - 20190322
X-Antispam-Training-Forget: https://mailfilter.sunet.se/canit/b.php?c=f&i=0aXP4MjtD&m=55b997887d4b&rlm=outbound-kau-se&t=20190322
X-Antispam-Training-Nonspam: https://mailfilter.sunet.se/canit/b.php?c=n&i=0aXP4MjtD&m=55b997887d4b&rlm=outbound-kau-se&t=20190322
X-Antispam-Training-Phish: https://mailfilter.sunet.se/canit/b.php?c=p&i=0aXP4MjtD&m=55b997887d4b&rlm=outbound-kau-se&t=20190322
X-Antispam-Training-Spam: https://mailfilter.sunet.se/canit/b.php?c=s&i=0aXP4MjtD&m=55b997887d4b&rlm=outbound-kau-se&t=20190322
X-CanIt-Archive-Cluster: PfMRe/vJWMiXwM2YIH5BVExnUnw
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=kau.se; h=date:from:to :cc:subject:message-id:references:mime-version:content-type :in-reply-to; s=canit; bh=OOnDOjMSajRfxe7QDOHbuqn6cxkOA3Kvt5wrI2 7S2AE=; b=OmCTksQGsqnHi54R0M3dnVkXSrTFb0ulHJk03adz3HrLiXcPi8oTiN Z4a/zbCh/64LWva+cjhPoq+Zcr9Z84IhZFtyD8s4j+5K8a+KUCCaWR1QhqjjVn/H C6c7+8aTEuFeqJ/HgPWlFJXriisTDvL34zXFvF8AGOzDvrEydr9hNwVCVPaC317J ZN2UQoYRorE+qMDKioavo4PQssJK5KinZqrvwKEeH6gmQPNWpQq4/4htQ1e3qwl9 +Kc8sLGoiKxuSotct9GLoTwX3PGtbd/GcjxH88DBFJdMEvYrxD8Awc9aYc3vx+V0 Zs1ziuXuW9ZM17X+75MErUPm52kR2VeQ==
X-Scanned-By: CanIt (www . roaringpenguin . com)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/M0TPSk7Qk438neZRlMb8cL8f8Rk>
Subject: Re: [Trans] Long Poll
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 22 Mar 2019 16:48:25 -0000

Hi,

You could fetch the latest STH periodically based on how often a log can produce
it: see MMD and STH frequency in Section 4.1.  For example, checking once per
hour makes sense if a log's MMD is 24 hours and its STH frequency is 24.  If you
are looking to fetch STHs today, i.e., from a log that is not CT/bis compliant,
you could learn how often STHs are normally produced by some initial polling
tests. Another option is to simply pick an interval that suits your needs,
preferably without being to aggressive based on how often STHs are produced.

On the topic of STH frequency, have anyone else noticed that Google's Icarus,
Pilot, Rocketeer and Skydiver logs switched from one hour STH interarrival times
to nearly instant updates somewhere around November 2018?  Try fetching one
hundred STHs back-to-back: most tree sizes will be unique.

If anyone knows what motivated this change I would happily be pointed in the
right direction. As many of you know, such high STH frequencies can cause a lot
of friction while experimenting and deploying various forms of gossip/auditing.

/R

On Thu, Mar 21, 2019 at 10:14:58PM +0300, Evgeny wrote:
> On Thu, Mar 21, 2019 at 7:41 PM, Evgeny <xramtsov@gmail.com> wrote:
> > Like while(0) {... sleep(1)}?
> 
> Oops, it should have been while(1) of course :)
> 
> _______________________________________________
> Trans mailing list
> Trans@ietf.org
> https://www.ietf.org/mailman/listinfo/trans


From nobody Fri Mar 22 10:24:39 2019
Return-Path: <xramtsov@gmail.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 9904313133F for <trans@ietfa.amsl.com>; Fri, 22 Mar 2019 10:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, 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 2Mq2USM7gZGy for <trans@ietfa.amsl.com>; Fri, 22 Mar 2019 10:24:35 -0700 (PDT)
Received: from mail-yw1-xc2a.google.com (mail-yw1-xc2a.google.com [IPv6:2607:f8b0:4864:20::c2a]) (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 B6E1B13133D for <trans@ietf.org>; Fri, 22 Mar 2019 10:24:35 -0700 (PDT)
Received: by mail-yw1-xc2a.google.com with SMTP id d132so2355238ywa.2 for <trans@ietf.org>; Fri, 22 Mar 2019 10:24:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=date:from:subject:to:message-id:in-reply-to:references:mime-version;  bh=FPx1iS5L0C8385NjsxgxDxjtGva0JbClbxe5MJwTHXI=; b=nwgj/LjQkcPi/vizMVBjC3jKWeThhSP9MOUFMf3VAd0PQ7j6zT9eV5udymf8A1qBJ9 QtrMd4oUrsu0ZQpxnFS2fp3bc0Jhc90U89Ek6HmvOmEF6qT9aIX0U/pHnZ1ZPd60JYhq FlOFo8N8Kl9TK12ge8x6XFMPDgcLPlsBJD9bk6He5uLnb1Mw/+oyVOziyjrUh1RxyCc1 kk0lSLs+hjTnwmNLTLKY7q+++eIYJ/K/aR6bvDgGpvsnnLo+qjGyfD5UALoFHixQPssC ISzXqFppE4B1PbxTIZHb3FiTqNdMVntC+V/w5G/GA9Uf+6rhXRoObpV5abr9c14Boljs oBjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:message-id:in-reply-to :references:mime-version; bh=FPx1iS5L0C8385NjsxgxDxjtGva0JbClbxe5MJwTHXI=; b=oPo7s1Nm9UFN1TF85hmyIZSRT+dAMrCgBADvvX1vYIqgkOABJWdP3BK99nYlQkmO7C QDY5ao+cKNmPoQSjAr7oM6wBaI/6Wtcmw40nVSG7x08rZ0AvnQJQF+pvXfqbJuDvhabJ 0tgXewU4q9CLsonZdZydUv969q4BJ0T0x4sPK9H6G/uefNgjp+T1xtaaqcNkFu9OuILm nqO6B6I+F5YapMc5VgkmcryDN8cz7E3sdeIWdjlj1QkFNucugBxbBjHkqWqUDOMKLOGV Q17CtPHcHZjMa9/HAjHxR8Vxa4n3sqPEI/dibtFB+5EH3m+UERQoJkvyba3khmbz9U+8 33ig==
X-Gm-Message-State: APjAAAWrq5MwUvasC2QAx4RdUYEUm0FDF5mYP4P8yakDclnfCeqVwsWM YqW6WjbNM8ZD9+iblUdtoseaTKow
X-Google-Smtp-Source: APXvYqxS4c9m9wywzGGgUPaBQ8wCyJD+6sFJkv9QLiU0HC0Rfot1wVdCQyw68cRpC7P3AJ0of7CA6Q==
X-Received: by 2002:a81:4506:: with SMTP id s6mr9292847ywa.500.1553275474605;  Fri, 22 Mar 2019 10:24:34 -0700 (PDT)
Received: from [192.168.1.102] ([185.155.18.125]) by smtp.gmail.com with ESMTPSA id f190sm9047303ywb.98.2019.03.22.10.24.32 for <trans@ietf.org> (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 22 Mar 2019 10:24:33 -0700 (PDT)
Date: Fri, 22 Mar 2019 20:24:30 +0300
From: Evgeny <xramtsov@gmail.com>
To: trans@ietf.org
Message-Id: <1553275470.1281.2@smtp.gmail.com>
In-Reply-To: <20190322164812.jajis3kx6qbxn25f@work>
References: <1553165248.1179.0@smtp.gmail.com> <CALzYgEfEgO2R_SwsAE-UtqV0rPAX9trcREt2jCTw_i1OHsXQFg@mail.gmail.com> <1553186500.1179.1@smtp.gmail.com> <1553195698.1179.2@smtp.gmail.com> <20190322164812.jajis3kx6qbxn25f@work>
X-Mailer: geary/0.12.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/tnR_NjcuZPUyq0Vz8GO1RDB2zUk>
Subject: Re: [Trans] Long Poll
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 22 Mar 2019 17:24:38 -0000

On Fri, Mar 22, 2019 at 7:48 PM, Rasmus Dahlberg 
<rasmus.dahlberg@kau.se> wrote:
> You could fetch the latest STH periodically based on how often a log 
> can produce
> it: see MMD and STH frequency in Section 4.1.  For example, checking 
> once per
> hour makes sense if a log's MMD is 24 hours and its STH frequency is 
> 24.  If you
> are looking to fetch STHs today, i.e., from a log that is not CT/bis 
> compliant,
> you could learn how often STHs are normally produced by some initial 
> polling
> tests. Another option is to simply pick an interval that suits your 
> needs,
> preferably without being to aggressive based on how often STHs are 
> produced.

Well, yes, I understand all this. Even if long polling is suboptimal in 
some sceanrios, what stops the authors from introducing long-polling 
API request for STH, it can be even optional. Because in my use case 
(that's a long story) I find long polling a better fit.


From nobody Fri Mar 22 12:38:54 2019
Return-Path: <devon.obrien@gmail.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 E5FAA1311E9 for <trans@ietfa.amsl.com>; Fri, 22 Mar 2019 12:38:51 -0700 (PDT)
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 TIaIOYN3LKa0 for <trans@ietfa.amsl.com>; Fri, 22 Mar 2019 12:38:49 -0700 (PDT)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 329DD130E2F for <trans@ietf.org>; Fri, 22 Mar 2019 12:38:49 -0700 (PDT)
Received: by mail-wr1-x435.google.com with SMTP id p1so3566261wrs.8 for <trans@ietf.org>; Fri, 22 Mar 2019 12:38:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LB4VOCxgA4xk319FnmQvwQJcbKtu9XG3d2pRX0GiJC0=; b=tWpbdlVEMbuTJ9cGfpfCon+MqAgCdQC9lbYz6I4nMbOpjWbP1Z7EoJCm/qFrSC3Vcv IK36xn5K+ooTWHKM9AXgOKe64bre4SejAGXL3H6lXRBu/VpwD8Nnd7OT8K5jxyQ843f/ jelEM7sTGTTCEq5k2OwsoHnjHPWsFzjD8/rIaxVp1gapADjW0t6ZVQtZ1Tm1j9qeZpHC ihOVnhg+9pCH7e2lofLhDp0UD4wTJb1mB2c96xFw7WVHzoVCkSJ1cU9nRGm016XI4qkm WTE4Smq6eDZMTS++1nui2S4L9nGO1p+hCnGkznFEvkh2ahxBeOEASx+wUfQBjTCtE3At F1+A==
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=LB4VOCxgA4xk319FnmQvwQJcbKtu9XG3d2pRX0GiJC0=; b=KXm6v+MhAUnRFZKeqFBkiiXs8Hb3hnzlk9nOdJcxxJawMd7mU8yAZnNRDMGLW/vvul ZFtWoGMsAh6U7wCsZJI0CU9yjOpFXhumx9ET1WUIX2lvTUF4J6QfWn88HEw5dlUAQnrD YAT5hOlUZQcfadzUw8oNftSmpjri77LfgqPqOOGCohdzg9M00ePEmejZ55HgkgoQMWPF YjApjDXehthKytVw3HdBVj8pesZ8fZsQ4Gxo4omb8wsjHxnubzNyZvx0t0x8OwpYouAb 3cPWZSDKQX9Nl4SYBfe2rviN+Qz9KLblM9T9ahRUKLo1LGgqVG+azk4BqAVrKNi5qLf9 DnbA==
X-Gm-Message-State: APjAAAUyCV1Wvce77fZEet0Riiwm0bFUcZ81BKA1GE1cg9XLjW+Hvj/b t+oCAh9bjX/Zmho2CmjKRXZFvaItycn2m6D9/h4=
X-Google-Smtp-Source: APXvYqyyR5vLFwH2vRbOxRPt0vVpT7MXnX+osbe9NSR/c3RBgb4v3KPSX8blqG7vBnXzj9of1ug3v9Z+m8nQAEpOvPM=
X-Received: by 2002:adf:f64d:: with SMTP id x13mr8003617wrp.298.1553283527625;  Fri, 22 Mar 2019 12:38:47 -0700 (PDT)
MIME-Version: 1.0
References: <1553165248.1179.0@smtp.gmail.com> <CALzYgEfEgO2R_SwsAE-UtqV0rPAX9trcREt2jCTw_i1OHsXQFg@mail.gmail.com> <1553186500.1179.1@smtp.gmail.com> <1553195698.1179.2@smtp.gmail.com> <20190322164812.jajis3kx6qbxn25f@work>
In-Reply-To: <20190322164812.jajis3kx6qbxn25f@work>
From: "Devon O'Brien" <devon.obrien@gmail.com>
Date: Fri, 22 Mar 2019 12:38:36 -0700
Message-ID: <CAPpiK7WEHsFnt2iy64k==7q58ok8A4rYMgWRrfwJ6O-20MJdzQ@mail.gmail.com>
To: Rasmus Dahlberg <rasmus.dahlberg@kau.se>
Cc: Evgeny <xramtsov@gmail.com>, eranm@google.com, trans@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e653900584b4009b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/Gra1qcuAqS4rhz0E6yE0pEpve98>
Subject: Re: [Trans] Long Poll
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 22 Mar 2019 19:38:52 -0000

--000000000000e653900584b4009b
Content-Type: text/plain; charset="UTF-8"

The capability to incorporate certificate logging requests, and therefore
mint substantially more frequent STHs is an artifact of the new codebase
that these CT Logs are running on. The migration was performed in November
[1] as you have observed, and was undertaken to increase reliability and
availability of these CT Logs. Frequent STHs are compliant with both RFC
6962 and the relevant CT-enforcing user agent policies, but if this
behavior is actively harmful, discussion on ct-policy@chromium.org is
probably the most reliable venue for discussing changes that are outside
the scope of RFC 6962, as this will be visible to Log Operators, CAs, and
Browsers/UAs.

[1]
https://groups.google.com/a/chromium.org/d/msg/ct-policy/-AGqeW5r7ck/4M6BB9CEAQAJ

On Fri, Mar 22, 2019 at 9:48 AM Rasmus Dahlberg <rasmus.dahlberg@kau.se>
wrote:

> Hi,
>
> You could fetch the latest STH periodically based on how often a log can
> produce
> it: see MMD and STH frequency in Section 4.1.  For example, checking once
> per
> hour makes sense if a log's MMD is 24 hours and its STH frequency is 24.
> If you
> are looking to fetch STHs today, i.e., from a log that is not CT/bis
> compliant,
> you could learn how often STHs are normally produced by some initial
> polling
> tests. Another option is to simply pick an interval that suits your needs,
> preferably without being to aggressive based on how often STHs are
> produced.
>
> On the topic of STH frequency, have anyone else noticed that Google's
> Icarus,
> Pilot, Rocketeer and Skydiver logs switched from one hour STH interarrival
> times
> to nearly instant updates somewhere around November 2018?  Try fetching one
> hundred STHs back-to-back: most tree sizes will be unique.
>
> If anyone knows what motivated this change I would happily be pointed in
> the
> right direction. As many of you know, such high STH frequencies can cause
> a lot
> of friction while experimenting and deploying various forms of
> gossip/auditing.
>
> /R
>
> On Thu, Mar 21, 2019 at 10:14:58PM +0300, Evgeny wrote:
> > On Thu, Mar 21, 2019 at 7:41 PM, Evgeny <xramtsov@gmail.com> wrote:
> > > Like while(0) {... sleep(1)}?
> >
> > Oops, it should have been while(1) of course :)
> >
> > _______________________________________________
> > Trans mailing list
> > Trans@ietf.org
> > https://www.ietf.org/mailman/listinfo/trans
>
> _______________________________________________
> Trans mailing list
> Trans@ietf.org
> https://www.ietf.org/mailman/listinfo/trans
>

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

<div dir=3D"ltr"><div dir=3D"ltr">The capability to incorporate certificate=
 logging requests, and therefore mint substantially more frequent STHs is a=
n artifact of the new codebase that these CT Logs are running on. The migra=
tion was performed in November [1] as you have observed, and was undertaken=
 to increase reliability and availability of these CT Logs. Frequent STHs a=
re compliant with both RFC 6962 and the relevant CT-enforcing user agent po=
licies, but if this behavior is actively harmful, discussion on <a href=3D"=
mailto:ct-policy@chromium.org">ct-policy@chromium.org</a> is probably the m=
ost reliable venue for discussing changes that are outside the scope of RFC=
 6962, as this will be visible to Log Operators, CAs, and Browsers/UAs.<div=
><br></div><div>[1]=C2=A0<a href=3D"https://groups.google.com/a/chromium.or=
g/d/msg/ct-policy/-AGqeW5r7ck/4M6BB9CEAQAJ">https://groups.google.com/a/chr=
omium.org/d/msg/ct-policy/-AGqeW5r7ck/4M6BB9CEAQAJ</a></div></div></div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, M=
ar 22, 2019 at 9:48 AM Rasmus Dahlberg &lt;<a href=3D"mailto:rasmus.dahlber=
g@kau.se">rasmus.dahlberg@kau.se</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">=
Hi,<br>
<br>
You could fetch the latest STH periodically based on how often a log can pr=
oduce<br>
it: see MMD and STH frequency in Section 4.1.=C2=A0 For example, checking o=
nce per<br>
hour makes sense if a log&#39;s MMD is 24 hours and its STH frequency is 24=
.=C2=A0 If you<br>
are looking to fetch STHs today, i.e., from a log that is not CT/bis compli=
ant,<br>
you could learn how often STHs are normally produced by some initial pollin=
g<br>
tests. Another option is to simply pick an interval that suits your needs,<=
br>
preferably without being to aggressive based on how often STHs are produced=
.<br>
<br>
On the topic of STH frequency, have anyone else noticed that Google&#39;s I=
carus,<br>
Pilot, Rocketeer and Skydiver logs switched from one hour STH interarrival =
times<br>
to nearly instant updates somewhere around November 2018?=C2=A0 Try fetchin=
g one<br>
hundred STHs back-to-back: most tree sizes will be unique.<br>
<br>
If anyone knows what motivated this change I would happily be pointed in th=
e<br>
right direction. As many of you know, such high STH frequencies can cause a=
 lot<br>
of friction while experimenting and deploying various forms of gossip/audit=
ing.<br>
<br>
/R<br>
<br>
On Thu, Mar 21, 2019 at 10:14:58PM +0300, Evgeny wrote:<br>
&gt; On Thu, Mar 21, 2019 at 7:41 PM, Evgeny &lt;<a href=3D"mailto:xramtsov=
@gmail.com" target=3D"_blank">xramtsov@gmail.com</a>&gt; wrote:<br>
&gt; &gt; Like while(0) {... sleep(1)}?<br>
&gt; <br>
&gt; Oops, it should have been while(1) of course :)<br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; Trans mailing list<br>
&gt; <a href=3D"mailto:Trans@ietf.org" target=3D"_blank">Trans@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/trans" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/trans</a><br>
<br>
_______________________________________________<br>
Trans mailing list<br>
<a href=3D"mailto:Trans@ietf.org" target=3D"_blank">Trans@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/trans" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/trans</a><br>
</blockquote></div>

--000000000000e653900584b4009b--


From nobody Fri Mar 22 13:31:03 2019
Return-Path: <rasmus.dahlberg@kau.se>
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 1D149131226 for <trans@ietfa.amsl.com>; Fri, 22 Mar 2019 13:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level: 
X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=kau.se
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 S1F7yUtIr-r3 for <trans@ietfa.amsl.com>; Fri, 22 Mar 2019 13:30:59 -0700 (PDT)
Received: from smtp1.kau.se (smtp1.kau.se [130.243.21.250]) by ietfa.amsl.com (Postfix) with ESMTP id 88B7812AF7A for <trans@ietf.org>; Fri, 22 Mar 2019 13:30:58 -0700 (PDT)
Received: from e-mailfilter02.sunet.se (e-mailfilter02.sunet.se [192.36.171.202]) by smtp1.kau.se (Postfix) with ESMTP id BC76A1802534; Fri, 22 Mar 2019 21:30:46 +0100 (CET)
Received: from Exch-A1.personal.kau (exch-a1.kau.se [130.243.19.82]) by e-mailfilter02.sunet.se (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id x2MKUjYu077628 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Fri, 22 Mar 2019 21:30:45 +0100
Received: from home (130.243.27.149) by Exch-A1.personal.kau (130.243.19.82) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1591.10; Fri, 22 Mar 2019 21:30:45 +0100
Date: Fri, 22 Mar 2019 21:30:38 +0100
From: Rasmus Dahlberg <rasmus.dahlberg@kau.se>
To: "Devon O'Brien" <devon.obrien@gmail.com>
CC: Evgeny <xramtsov@gmail.com>, <eranm@google.com>, <trans@ietf.org>
Message-ID: <20190322203038.pvirayepwbgrvkwz@home>
References: <1553165248.1179.0@smtp.gmail.com> <CALzYgEfEgO2R_SwsAE-UtqV0rPAX9trcREt2jCTw_i1OHsXQFg@mail.gmail.com> <1553186500.1179.1@smtp.gmail.com> <1553195698.1179.2@smtp.gmail.com> <20190322164812.jajis3kx6qbxn25f@work> <CAPpiK7WEHsFnt2iy64k==7q58ok8A4rYMgWRrfwJ6O-20MJdzQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <CAPpiK7WEHsFnt2iy64k==7q58ok8A4rYMgWRrfwJ6O-20MJdzQ@mail.gmail.com>
User-Agent: NeoMutt/20171215
X-Originating-IP: [130.243.27.149]
X-ClientProxiedBy: Exch-A3.personal.kau (130.243.19.84) To Exch-A1.personal.kau (130.243.19.82)
X-Bayes-Prob: 0.9999 (Score 5, tokens from: outbound, outbound-kau-se:default,  kau-se:default, base:default, @@RPTN)
X-p0f-Info: os=Windows 7 or 8, link=Ethernet or modem
X-CanIt-Geo: ip=130.243.27.149; country=SE; latitude=59.3247; longitude=18.0560; http://maps.google.com/maps?q=59.3247,18.0560&z=6
X-CanItPRO-Stream: outbound-kau-se:outbound (inherits from outbound-kau-se:default, kau-se:default, base:default)
X-Canit-Stats-ID: 0aXP8uJst - 2e6a9ccc722d - 20190322
X-Antispam-Training-Forget: https://mailfilter.sunet.se/canit/b.php?c=f&i=0aXP8uJst&m=2e6a9ccc722d&rlm=outbound-kau-se&t=20190322
X-Antispam-Training-Nonspam: https://mailfilter.sunet.se/canit/b.php?c=n&i=0aXP8uJst&m=2e6a9ccc722d&rlm=outbound-kau-se&t=20190322
X-Antispam-Training-Phish: https://mailfilter.sunet.se/canit/b.php?c=p&i=0aXP8uJst&m=2e6a9ccc722d&rlm=outbound-kau-se&t=20190322
X-Antispam-Training-Spam: https://mailfilter.sunet.se/canit/b.php?c=s&i=0aXP8uJst&m=2e6a9ccc722d&rlm=outbound-kau-se&t=20190322
X-CanIt-Archive-Cluster: PfMRe/vJWMiXwM2YIH5BVExnUnw
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=kau.se; h=date:from:to :cc:subject:message-id:references:mime-version:content-type :in-reply-to; s=canit; bh=JsDFy4Bt60y7k9r8192pm7Q9fmw8y+9Cs8BeTV dFujw=; b=Qb+9vFgmEv+b3vRhEJSWRBeEJ/D13KvA45ndnreDVnj5ttxFiY3wLp zlCIVvy+ne+sbJI4svdzVOS3ag4rxrwAOAVhM0X+8qJWpCje/x8AYVTTjT6HTaEN WDTqWDfq2+chp2ZX9d9saTd7lm2CiJotXbTym7HqTh8WnuXVMJ42EN0WIhDnmh7S N6fBliE5YoGGnLqvqgGdOxoqGQv2EZk3uyFprUWyBRqI+oYwgdGxPbFmzad9Bfcd UACpSwThQZHddaP5z8VjEolYY37icItptLM3UDAcg6hCuP4qhfcIE5rQNqa/OcKR wZO7izMegj9YJ6YPzwjgQSlSpKDdFjJQ==
X-Scanned-By: CanIt (www . roaringpenguin . com)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/H2h-ImGXheoDkSGRmRkNdkdNmws>
Subject: Re: [Trans] Long Poll
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 22 Mar 2019 20:31:02 -0000

Thanks, both for the link and your suggestion to bring this to Chrome's
CT policy mailing list. One of the reasons why I thought it was relevant to
bring up here is the fact that the draft developed by Nordberg, Gillmor
and Ritter depends on a sound STH frequency to preserve privacy [2].

2: https://datatracker.ietf.org/doc/draft-ietf-trans-gossip/

/R

On Fri, Mar 22, 2019 at 12:38:36PM -0700, Devon O'Brien wrote:
> The capability to incorporate certificate logging requests, and therefore
> mint substantially more frequent STHs is an artifact of the new codebase
> that these CT Logs are running on. The migration was performed in November
> [1] as you have observed, and was undertaken to increase reliability and
> availability of these CT Logs. Frequent STHs are compliant with both RFC
> 6962 and the relevant CT-enforcing user agent policies, but if this
> behavior is actively harmful, discussion on ct-policy@chromium.org is
> probably the most reliable venue for discussing changes that are outside
> the scope of RFC 6962, as this will be visible to Log Operators, CAs, and
> Browsers/UAs.
> 
> [1]
> https://groups.google.com/a/chromium.org/d/msg/ct-policy/-AGqeW5r7ck/4M6BB9CEAQAJ
> 
> On Fri, Mar 22, 2019 at 9:48 AM Rasmus Dahlberg <rasmus.dahlberg@kau.se>
> wrote:
> 
> > Hi,
> >
> > You could fetch the latest STH periodically based on how often a log can
> > produce
> > it: see MMD and STH frequency in Section 4.1.  For example, checking once
> > per
> > hour makes sense if a log's MMD is 24 hours and its STH frequency is 24.
> > If you
> > are looking to fetch STHs today, i.e., from a log that is not CT/bis
> > compliant,
> > you could learn how often STHs are normally produced by some initial
> > polling
> > tests. Another option is to simply pick an interval that suits your needs,
> > preferably without being to aggressive based on how often STHs are
> > produced.
> >
> > On the topic of STH frequency, have anyone else noticed that Google's
> > Icarus,
> > Pilot, Rocketeer and Skydiver logs switched from one hour STH interarrival
> > times
> > to nearly instant updates somewhere around November 2018?  Try fetching one
> > hundred STHs back-to-back: most tree sizes will be unique.
> >
> > If anyone knows what motivated this change I would happily be pointed in
> > the
> > right direction. As many of you know, such high STH frequencies can cause
> > a lot
> > of friction while experimenting and deploying various forms of
> > gossip/auditing.
> >
> > /R
> >
> > On Thu, Mar 21, 2019 at 10:14:58PM +0300, Evgeny wrote:
> > > On Thu, Mar 21, 2019 at 7:41 PM, Evgeny <xramtsov@gmail.com> wrote:
> > > > Like while(0) {... sleep(1)}?
> > >
> > > Oops, it should have been while(1) of course :)
> > >
> > > _______________________________________________
> > > Trans mailing list
> > > Trans@ietf.org
> > > https://www.ietf.org/mailman/listinfo/trans
> >
> > _______________________________________________
> > Trans mailing list
> > Trans@ietf.org
> > https://www.ietf.org/mailman/listinfo/trans
> >


From nobody Tue Mar 26 08:58:05 2019
Return-Path: <rob@sectigo.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 085AB120500 for <trans@ietfa.amsl.com>; Tue, 26 Mar 2019 08:58:03 -0700 (PDT)
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, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 (1024-bit key) header.d=comodoca.onmicrosoft.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 6JipbeB8csYZ for <trans@ietfa.amsl.com>; Tue, 26 Mar 2019 08:58:00 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-eopbgr810084.outbound.protection.outlook.com [40.107.81.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3740120449 for <trans@ietf.org>; Tue, 26 Mar 2019 08:57:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comodoca.onmicrosoft.com; s=selector1-sectigo-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MU1yrYBoYOZFw4kBoFQNyCslCVONFck9xr2R8NIislo=; b=qHGq62SWs09Cw7ljxXPgpGFVAPLskjvYlgHyXtJCPyMzBzopDYDb0mznW5kZSwgPhPQCixteI/DxYL5wxKQJFqb3RmOLl+6z2Jssqzyj7qny2xpD8KABZo8OHK4yL8NzqQNfV1yatvc8H1zmBRhl/EiLLa7CrxzgsEHpWuTqn74=
Received: from DM6PR17MB2251.namprd17.prod.outlook.com (20.176.92.149) by DM6PR17MB3228.namprd17.prod.outlook.com (20.176.125.209) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.15; Tue, 26 Mar 2019 15:57:57 +0000
Received: from DM6PR17MB2251.namprd17.prod.outlook.com ([fe80::6123:f96c:b0e3:72d9]) by DM6PR17MB2251.namprd17.prod.outlook.com ([fe80::6123:f96c:b0e3:72d9%5]) with mapi id 15.20.1730.019; Tue, 26 Mar 2019 15:57:57 +0000
From: Rob Stradling <rob@sectigo.com>
To: "trans@ietf.org" <trans@ietf.org>
Thread-Topic: 6962-bis: Explicitly define the colon operator
Thread-Index: AQHU4+yu2TznME+Erk+/ur+oMHDs3g==
Date: Tue, 26 Mar 2019 15:57:57 +0000
Message-ID: <724fd173-64c1-c9f3-0bf2-5eed829da3fe@sectigo.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-clientproxiedby: LO2P265CA0161.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9::29) To DM6PR17MB2251.namprd17.prod.outlook.com (2603:10b6:5:b9::21)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rob@sectigo.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [91.212.12.2]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d85c8c34-d712-48ed-87ef-08d6b203d080
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:DM6PR17MB3228; 
x-ms-traffictypediagnostic: DM6PR17MB3228:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <DM6PR17MB3228EA89D4D32AD0D7226740AA5F0@DM6PR17MB3228.namprd17.prod.outlook.com>
x-forefront-prvs: 09888BC01D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(396003)(346002)(366004)(376002)(39840400004)(189003)(199004)(86362001)(106356001)(99286004)(105586002)(2351001)(316002)(6436002)(68736007)(256004)(31686004)(53936002)(6486002)(476003)(31696002)(5660300002)(486006)(2616005)(14454004)(8936002)(81166006)(81156014)(66066001)(478600001)(5640700003)(8676002)(1730700003)(7736002)(305945005)(966005)(71190400001)(36756003)(97736004)(71200400001)(2501003)(6916009)(3846002)(386003)(6506007)(6116002)(25786009)(102836004)(186003)(4744005)(26005)(6512007)(6306002)(2906002)(52116002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR17MB3228; H:DM6PR17MB2251.namprd17.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: sectigo.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: eKx1eowrs2d00x4wLwPE7zAAf4glm2NnEjAwX0KzrolevX9aW55iLqa+dvEn0nOYTEo6CBuh29M/ON3dkp3xxnHNNbE/tOKE+FDy3jofqUJZa4yQpnT/sAJZREA8S5KgsKbI+xgKm/GF+sPSRveaxSv3jLKKIiovai5p7s+ZIiNbiiNdk5hMmH3roOVy/n6/M9kdvKHI/tGnaV0GPvd4sqUTHehfRjH3DQxzch4xFKR1/s1Sj0+Xrfqv+K7GCujk7eGsMQXhhm74ZdkJkToWXWarxnDfnRcq3/jrXW1z5MaRD/N15Y2Y8D7ypFw1+FRUb21ySmdbAOikdvOiImQ+bcg9V9o+7m+i3O23IuBsMEOYc/CL3mjY9xVCZNc4BjPCYZXRK/NQWwsJNycM0wErTIUzL4wtzg5JmH+TtyEeBC0=
Content-Type: text/plain; charset="utf-8"
Content-ID: <18EEE78D74F6E14BB262EB898C3AAF18@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: sectigo.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d85c8c34-d712-48ed-87ef-08d6b203d080
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Mar 2019 15:57:57.8508 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0e9c4894-6caa-465d-9660-4b6968b49fb7
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR17MB3228
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/0pC2vgpaD-Lsx1aEyoQhJRuiFn0>
Subject: [Trans] 6962-bis: Explicitly define the colon operator
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 26 Mar 2019 15:58:03 -0000

VGhlIC1iaXMgYXV0aG9ycyByZWNlaXZlZCB0aGlzIGNvbW1lbnQgYSBmZXcgZGF5cyBhZ286DQoN
CiJJbiBwYWdlIDkgb2YgDQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi10
cmFucy1yZmM2OTYyLWJpcy0zMSBpbiBzZWN0aW9uIA0KaW4gc2VjdGlvbiAyLjEuMy4xLiB3ZSBm
aW5kDQoNClRoZSA6IG9wZXJhdG9yIGFuZCBEW2sxOmsyXSBhcmUgZGVmaW5lZCB0aGUgc2FtZSBh
cyBpbiBTZWN0aW9uIDIuMS4xLg0KDQpIb3dldmVyLCBpbiBzZWN0aW9uIDIuMS4xLiB0aGUgb3Bl
cmF0b3IgOiBpcyBub3QgZm91bmQuIFRoZXJlIGlzIG5vIA0KZGVmaW5pdGlvbiBvZiB0aGlzIG9w
ZXJhdG9yLiINCg0KDQpUaGUgSUVTRyBoYXMgZXZhbHVhdGVkIHZlcnNpb24gLTMxLCBhbmQgd2Ug
KHRoZSBhdXRob3JzKSBub3cgaGF2ZSBhIA0KYnVuY2ggb2YgRElTQ1VTUyBjb21tZW50cyB0byBh
ZGRyZXNzIGJlZm9yZSBDVCB2MiB3aWxsIChmaW5hbGx5ISkgYmVjb21lIA0KYW4gUkZDLiAgQWx0
aG91Z2ggaXQncyBleHRyZW1lbHkgbGF0ZSBpbiB0aGUgcHJvY2VzcyB0byBiZSBtYWtpbmcgYW55
IA0KY2hhbmdlcyB0byB0aGUgZG9jdW1lbnQgKGV4Y2VwdCBmb3IgYWRkcmVzc2luZyB0aGUgRElT
Q1VTUyBjb21tZW50cyksIA0KdGhlIFdHIENoYWlycyBhbmQgQS1EIChFS1IpIGhhdmUgZ2l2ZW4g
dGhlIGdvLWFoZWFkIHRvIGFkZHJlc3MgdGhlIA0KY29uY2VybiBub3RlZCBhYm92ZSwgcHJvdmlk
ZWQgdGhhdCBJIHNlbmQgdGhpcyBtZXNzYWdlIHRvIHRoZSBsaXN0IHRvIA0KZ2l2ZSBmb2xrcyBh
IGNoYW5jZSB0byBvYmplY3QuDQoNCkkndmUgcHJlcGFyZWQgYSBQUjoNCmh0dHBzOi8vZ2l0aHVi
LmNvbS9nb29nbGUvY2VydGlmaWNhdGUtdHJhbnNwYXJlbmN5LXJmY3MvcHVsbC8zMDgNCg0KLS0g
DQpSb2IgU3RyYWRsaW5nDQpTZW5pb3IgUmVzZWFyY2ggJiBEZXZlbG9wbWVudCBTY2llbnRpc3QN
ClNlY3RpZ28gTGltaXRlZA0KDQo=


From nobody Sat Mar 30 01:56:52 2019
Return-Path: <kaduk@mit.edu>
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 549CC120183 for <trans@ietfa.amsl.com>; Sat, 30 Mar 2019 01:56:51 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, 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 rcKxwrb0PI2l for <trans@ietfa.amsl.com>; Sat, 30 Mar 2019 01:56:49 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 5C1B512013D for <trans@ietf.org>; Sat, 30 Mar 2019 01:56:49 -0700 (PDT)
Received: from kduck.mit.edu (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x2U8ujLJ020176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 30 Mar 2019 04:56:47 -0400
Date: Sat, 30 Mar 2019 03:56:45 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Rob Stradling <rob@sectigo.com>
Cc: "trans@ietf.org" <trans@ietf.org>
Message-ID: <20190330085645.GN35679@kduck.mit.edu>
References: <724fd173-64c1-c9f3-0bf2-5eed829da3fe@sectigo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <724fd173-64c1-c9f3-0bf2-5eed829da3fe@sectigo.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/9nKPuLe3gW9Wj5xzMw8hzElSplc>
Subject: Re: [Trans] 6962-bis: Explicitly define the colon operator
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 30 Mar 2019 08:56:51 -0000

On Tue, Mar 26, 2019 at 03:57:57PM +0000, Rob Stradling wrote:
> The -bis authors received this comment a few days ago:
> 
> "In page 9 of 
> https://tools.ietf.org/html/draft-ietf-trans-rfc6962-bis-31 in section 
> in section 2.1.3.1. we find
> 
> The : operator and D[k1:k2] are defined the same as in Section 2.1.1.
> 
> However, in section 2.1.1. the operator : is not found. There is no 
> definition of this operator."
> 
> 
> The IESG has evaluated version -31, and we (the authors) now have a 
> bunch of DISCUSS comments to address before CT v2 will (finally!) become 
> an RFC.  Although it's extremely late in the process to be making any 
> changes to the document (except for addressing the DISCUSS comments), 
> the WG Chairs and A-D (EKR) have given the go-ahead to address the 
> concern noted above, provided that I send this message to the list to 
> give folks a chance to object.
> 
> I've prepared a PR:
> https://github.com/google/certificate-transparency-rfcs/pull/308

Interesting, I guess I mis-parsed what it was supposed to be, when
balloting (in that I mostly only saw the D[k1:k2] notation and asked what
"D[m]" was.  So I guess I should take another look, but maybe I can hold
off on that until there's text to review that resolves my DISCUSS points.

-Ben

