Re: [Trans] RFC 7320 and draft-ietf-trans-rfc6962-bis-24

Melinda Shore <melinda.shore@gmail.com> Mon, 10 April 2017 19:15 UTC

Return-Path: <melinda.shore@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 6ED27129AB6 for <trans@ietfa.amsl.com>; Mon, 10 Apr 2017 12:15:23 -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 u1vQtb7yYIJr for <trans@ietfa.amsl.com>; Mon, 10 Apr 2017 12:15:22 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (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 134D9126DED for <trans@ietf.org>; Mon, 10 Apr 2017 12:15:22 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id s16so37614842pfs.0 for <trans@ietf.org>; Mon, 10 Apr 2017 12:15:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=JKQgrr++xEGikWDuWgtldlFFvdGfs0y1jaoxgE10Nn4=; b=F/q3KtoVpZ3oVgGl0dHDkXIzRigo41EOhsmml4vGVzv1mBNMyIBB5KbLhiREJOJNz0 u5ExjymmQDBH+obfQb6NjykIHX2rEUOfTIL6Fpw50THxOSnzZJbag2sWBAnQcf/FWpay 8cukRbVO6ArAg9TLE92CQ8fJqO2ZP8NTI2mLngl5uOGJKRm5JSGcsGldYVvBvvY6JoVZ yjAPiQMfEqwmBVnBj09LkmvR0Zr/2te4OyrjoVYClbDb4ej97F2U1SSHKI5izhJ3H3zm 0PTah1buHNzFh/36R2PUvDVJi2xmg5Mg4z9+Hi1m2/ekfYaBIoSp5enGoB3OP+B7oO5B CRdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=JKQgrr++xEGikWDuWgtldlFFvdGfs0y1jaoxgE10Nn4=; b=RNtRbTJs38rrxQvUtf41vD4VupLCFIq+mDNxwxOadRTQUmLoIx3S46f7nzZAKraQ+0 k+tRE3M37CPbeIsC8E1GlcfcRU+tuvhmJhNtCN9FWYYm+ZRf7LbOCjo6i4IwGn6N7MBL 5HLTuv1qmNUTVPxTFuuC4oKO0WEo+1v+FVw6qdOOEurjyibzcRKxli+BMdjCVPz9DeP8 7C9+jl+kzIT1x8KyAn21GwECiZbssZHvtjO0cVqAGDJN8gHheBsU91hmZNLm67cZUema rQOPOzQWyRLKiDbEtqxUSf6YKRUKOeGnaMGxEtk8goEVKF8+9RWUbUUH505r4aopBF2C mnCw==
X-Gm-Message-State: AFeK/H0CEAohvnKjOvGY1rQAHQUEZ9/x0onwER93g9T7WoXNJDBJyldPpp3OFoSmIudavg==
X-Received: by 10.98.107.194 with SMTP id g185mr57292524pfc.22.1491851721322; Mon, 10 Apr 2017 12:15:21 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (63-140-86-208-radius.dynamic.acsalaska.net. [63.140.86.208]) by smtp.gmail.com with ESMTPSA id f84sm26082281pfa.127.2017.04.10.12.15.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Apr 2017 12:15:20 -0700 (PDT)
To: Eran Messeri <eranm@google.com>, "trans@ietf.org" <trans@ietf.org>
References: <CABkgnnUescLZ-s0a+TGEhpcHH6E1i=1HhGTRhj8mKa=0q9TkHA@mail.gmail.com> <0f1433b8-84a7-754c-6463-ee73808abf9e@gmail.com> <CALzYgEdiin67qaUFz6vnjz=kv-igyV_Ld-RN1SnnKnrmTJvk_g@mail.gmail.com> <CALzYgEeiOV9q0sk3ooPGBUW1cQGtOVdgPAy8biVMsU6_uOqg0A@mail.gmail.com>
Cc: martin.thomson@gmail.com
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <ad3f9f73-5daa-4f9c-1fe1-a5da6c8886a9@gmail.com>
Date: Mon, 10 Apr 2017 11:15:18 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CALzYgEeiOV9q0sk3ooPGBUW1cQGtOVdgPAy8biVMsU6_uOqg0A@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="awSvN47BqoQEFiBM01QmbFB6KjJtNJv4v"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/rK_L6qrwPX88AydrtJ01pJ_erJE>
Subject: Re: [Trans] RFC 7320 and draft-ietf-trans-rfc6962-bis-24
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 19:15:23 -0000

On 4/7/17 1:05 AM, Eran Messeri wrote:
> Instead, we could:
> (1) Clarify why BCP 190 may not apply here (based on experience
> deploying V1 logs)
> (2) Remove the 'ct/v2' portion from all the URIs.
> 
> Any preferences? Mine would be for (2), but it's not a strong preference.

I think that in general, when there's a deviation from a BCP
it's a good idea to document why it's inapplicable - the question
is very likely to come up at some point during the review process.
I don't think that removing the ct/v2 portion would be sufficient to
resolve the conflict with BCP 190, although it may be
desirable for other reasons.

Melinda