Re: [Trans] overview of remaining(?) DISCUSS items for draft-ietf-trans-rfc6962-bis-33

Eran Messeri <eranm@google.com> Wed, 25 September 2019 16:12 UTC

Return-Path: <eranm@google.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20EE71200D7 for <trans@ietfa.amsl.com>; Wed, 25 Sep 2019 09:12:29 -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_HELO_NONE=0.001, SPF_PASS=-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 cOf5mp2QczLd for <trans@ietfa.amsl.com>; Wed, 25 Sep 2019 09:12:26 -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 6F7381200C7 for <trans@ietf.org>; Wed, 25 Sep 2019 09:12:26 -0700 (PDT)
Received: by mail-yw1-xc2c.google.com with SMTP id x64so2253527ywg.3 for <trans@ietf.org>; Wed, 25 Sep 2019 09:12:26 -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=Q4wOUWuOTls1HVdIr9H6Kl+Pr/9jSqgkE4aVxoWp9ck=; b=EPg2o/Zb9nb5jB1bHizgfLfQ4KJ85wJr+6K8V45/rpsdBuQb7jKtmB5tae5OdxYMY7 L9JbK5sN/k2I2VN/VFDYtI2pWC89zXHJCXcEtCRopMDSxWLUldqLpqALGYVOuV/QG46U vtxmufzDmrOdbf7sAA7p7RbZFN4+5A2DfACDwzBqdU8jtkI3DgZJyFNhatDpwOIxpNV4 IGTiK6Cb1zO1q8H6Mc4RHndai6NV2wC0Xah26+RzPTGoYCPYUMks0RioljgZ2PSihHYt 2ul8ix/5/gjZKt/QaIodtH7V4mVyxnxAuJUoyVzI5kySDn57UemdvGbAB62pz5/x7Yk9 TOow==
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=Q4wOUWuOTls1HVdIr9H6Kl+Pr/9jSqgkE4aVxoWp9ck=; b=a0UOJ1Cs8Br4eu5yWVgzUFVce5lWjqZt8x66+tKdYxm7/ol2fv1AD5BhrYb2FpH2Pj nQEIp3wfsoXpw+yuQTJu++E9/6IU/d/i8ziMzYjO53wQxaoYbwpttHXwsGrkEQptn0KM 7BUsixPaZwTxZzKDmtxge539wiSALtHWtH21Q+n3LzjQJKNGxEbuL6xZlGa3WtzMGF93 lJHKbNvf1ZVCRU0jeaZ6drAyAeoIoSrRAQziruqoJvI1yAzrv5DBq7gDC4mIq3JksS6r dVBZkcpby7yZJ7zYHgPcaxLX+tjxFFR1ZuHt+10gXm35NuoeRN7mivrdKE3OlwlMnJKm ZEzA==
X-Gm-Message-State: APjAAAXKhRm09xI6CQ/qoD03OEh0+swWP0aV8UuNq/gCbunZRfh3mG1k TeD2M7l8uQ2PkQWUKakedjqBE99EwAYqdBCgTB925lLrNSc=
X-Google-Smtp-Source: APXvYqyN3MiukpoSO9uWZk6mft+3uE4cU4yCok67Dx8g5wPdi8iH1QOEeaMVPdVvPmCjwSD69bcbRPlwd+yFxzWYKMw=
X-Received: by 2002:a81:9bd7:: with SMTP id s206mr6919315ywg.193.1569427945139; Wed, 25 Sep 2019 09:12:25 -0700 (PDT)
MIME-Version: 1.0
References: <alpine.LRH.2.21.1909181506160.11898@bofh.nohats.ca> <b6ec6a38-a4c2-64b4-0584-d13deead2605@sectigo.com> <alpine.LRH.2.21.1909191211080.29314@bofh.nohats.ca> <4632c221-c207-72c4-83c3-ecc8dcbf2ba7@sectigo.com> <alpine.LRH.2.21.1909231733480.23118@bofh.nohats.ca> <20190924075519.6a9daab1def6475bd26e5370@andrewayer.name> <alpine.LRH.2.21.1909241335180.9491@bofh.nohats.ca> <2fa45a40-c12c-4d85-a0ab-17c83fdd2443@sectigo.com>
In-Reply-To: <2fa45a40-c12c-4d85-a0ab-17c83fdd2443@sectigo.com>
From: Eran Messeri <eranm@google.com>
Date: Wed, 25 Sep 2019 17:11:58 +0100
Message-ID: <CALzYgEfJkodKf=H-WeE0KNjfcd1csJp3fU8OXLbN0ZjYPyo6yw@mail.gmail.com>
To: Rob Stradling <rob@sectigo.com>
Cc: Paul Wouters <paul@nohats.ca>, Andrew Ayer <agwa@andrewayer.name>, Trans <trans@ietf.org>, Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary="0000000000002c0dc9059362eb2d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/DEFcZg8UrVLHBDDNWEa3-JMBoRs>
Subject: Re: [Trans] overview of remaining(?) DISCUSS items for draft-ietf-trans-rfc6962-bis-33
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, 25 Sep 2019 16:12:29 -0000

On Wed, Sep 25, 2019 at 12:16 PM Rob Stradling <rob@sectigo.com> wrote:

> On 24/09/2019 18:38, Paul Wouters wrote:
> > On Tue, 24 Sep 2019, Andrew Ayer wrote:
> >
> >>> While I agree with you, I am just a WG chair. So we need to hear a few
> >>> more opinions of people and then if there is a consensus, we can go
> >>> ahead and make this change.
> >>
> >> I'm also not sure what "this change" would be, but I agree with the
> >> other comments here that CT shouldn't provide a mechanism for logs to
> >> change URL.
> >
> > I meant the clarification text of Base URL change (verus a potential
> > other consensus of text that would allow updating the base url)
> >
> > I'm not sure what the policy is for declaring a registry append only.
> > Maybe leave a comment in for IANA whether or not that needs text?
>
> In -33, section 10.6.1 says:
>    "Each application for the allocation of a Log ID MUST be accompanied
>     by:
>       - the Log's Base URL (see Section 4.1).
>       - a Contact (including contact information), from whom further
>         information can be obtained.
>       - an Owner (including contact information), who is authorized to
>         change this Log ID allocation."
>
> I think we should fold "Owner" and "Contact" into just one field named
> "Log Operator", and clarify that the only part of a Log ID Registry
> entry that can be updated is the log operator's contact information.
>
> Also, given that log operators are permitted to allocate Log IDs from
> other OID arcs (see section 4.4), ISTM that we also need to update
> section 4.1 to say that a log's Base URL is immutable.
>
> Furthermore, ISTM that it would help to be explicit about the
> immutability of each and every log parameter.
>
> Here's a PR that attempts to resolve all of the above:
> https://github.com/google/certificate-transparency-rfcs/pull/314

I agree with Rob and Ryan's stance - as demonstrated with 6962 deployment,
client agility would address the issue of logs wanting to change their URLs
(and I do not recall an occasion where having the ability to change just
the log URL would have been helpful).


>
>
> > Or alternatively, in the text for the Expert Review, mention the
> > registry is strictly append-only ?
>
> There is no Expert Review text relating to the Log ID Registry.
>
> --
> Rob Stradling
> Senior Research & Development Scientist
> Sectigo Limited
>
> _______________________________________________
> Trans mailing list
> Trans@ietf.org
> https://www.ietf.org/mailman/listinfo/trans
>