IETF Logo Mail Archive

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

Eran Messeri <eranm@google.com> Fri, 07 April 2017 09:06 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 AD7B3126C22 for <trans@ietfa.amsl.com>; Fri, 7 Apr 2017 02:06:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, 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=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 DE8WTv0tGrVq for <trans@ietfa.amsl.com>; Fri, 7 Apr 2017 02:06:07 -0700 (PDT)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::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 75D01124281 for <trans@ietf.org>; Fri, 7 Apr 2017 02:06:07 -0700 (PDT)
Received: by mail-io0-x22a.google.com with SMTP id z13so45860546iof.2 for <trans@ietf.org>; Fri, 07 Apr 2017 02:06:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7lT8ppOqlhC+TFRL+Yq9RuM5fP8tjXjdvRxNCD5aoAY=; b=Hm6Olo0Ji/mWXJFlS8VJz7JP8HUJrc6YnQTR/gJIVYwH/gzS3cj7QUst1lclmzlu+f J7ECHWrkAzftucsA8/58OR66O/56NoRKiOJOqanftcTVvVsoLnHi4ARAbc0Z4PyOciTc SbDCQRyCrN1iG5cGruVUL2f7sao0kpJxtMP8Vu5akqIDLLNuo7qGaUqOD8NAIF1RP2uV Yf8IYny46r5W5WPD15QcPjSuI0o5Hcz6mkWLXFr7CQMT5ALhwbkagiW6QzFcAxYLDHrM pvtfh8Fclo2k9ICmIivW/knBUVMArGpLNC2iEJLTabDfmj2lG91ZhjSST34c3PfV6zQL WQwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7lT8ppOqlhC+TFRL+Yq9RuM5fP8tjXjdvRxNCD5aoAY=; b=hlGCY8xVKCivSMSxgiwKR5jYc7vZKWFT5MqgyqoOTOZxh8PQ1vPGjMdaIcQq4p0xS5 lAmZ+FZ5cOsrQ8bp3vmMZ1Si8FiTjJW/wTRtYSPnxuKE92gcg7SoJI7toLwPVK4dAcTQ R9gLpxGQio0xARllhJX2FqdJ8cHg9bMsvhPdSE7f6jJUExj2hIQO2sN9CSh7wAeZHt2L 6c5Sq8AJ8C3T5JRznbDDd9AoEfcnypPTqAyHd7CLe/CMsT1GA51/HTa3U9g/9eKhv4Ix uL3NiWacdaBVI/alPmfB+txxlBurMIL+28ERVxF6MW9n2KSv8UEMBUzS8HxurvmjkADN et2w==
X-Gm-Message-State: AFeK/H2DjFVK3RoOItFx7s4MMArfGVTS/b8I6imFyqM31EL7MNPIz1Wc+0QXdRKzerCchI81eiTdsSeX3MkI7c1B
X-Received: by 10.107.85.2 with SMTP id j2mr43395695iob.165.1491555966653; Fri, 07 Apr 2017 02:06:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.164.200 with HTTP; Fri, 7 Apr 2017 02:05:36 -0700 (PDT)
In-Reply-To: <CALzYgEdiin67qaUFz6vnjz=kv-igyV_Ld-RN1SnnKnrmTJvk_g@mail.gmail.com>
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>
From: Eran Messeri <eranm@google.com>
Date: Fri, 07 Apr 2017 10:05:36 +0100
Message-ID: <CALzYgEeiOV9q0sk3ooPGBUW1cQGtOVdgPAy8biVMsU6_uOqg0A@mail.gmail.com>
To: "trans@ietf.org" <trans@ietf.org>
Cc: Melinda Shore <melinda.shore@gmail.com>, martin.thomson@gmail.com
Content-Type: multipart/alternative; boundary="94eb2c1c5f808e7c57054c8fef07"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/VkeUKdgoGv0qVKUFycqvwQ66S3I>
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: Fri, 07 Apr 2017 09:06:10 -0000

>From discussing in-person with Richard Barnes, and the trans wg meeting, it
seems there's consensus on not having a 'directory' endpoint for dynamic
discovery of all the methods the log exposes.

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.

On Mon, Mar 20, 2017 at 2:50 PM, Eran Messeri <eranm@google.com> wrote:

> FYI this has been documented in https://trac.ietf.org/trac/
> trans/ticket/185.
>
> On Wed, Mar 15, 2017 at 8:46 PM, Melinda Shore <melinda.shore@gmail.com>
> wrote:
>
>> On 3/15/17 12:29 PM, Martin Thomson wrote:
>> > I am not following this work, but this and the original RFC 6962 both
>> > run afoul of the (good) guidance in RFC 7320.
>> >
>> > Has the working group solicited feedback from the HTTP community on
>> > the use of HTTP in this protocol?
>>
>> No, we haven't.
>>
>> For what it's worth, 6962 reflects implementation and
>> deployment prior to CT having been brought to the IETF
>> for standardization, so any concerns regarding URL
>> syntax or HTTP transport in the work being done by this
>> working group are necessarily limited to the -bis and
>> related documents.
>>
>> To be honest, I'm personally not convinced of the applicability
>> of 7320 in this case but if there's a specific problem it does
>> need to be discussed.
>>
>> Melinda
>>
>>
>> _______________________________________________
>> Trans mailing list
>> Trans@ietf.org
>> https://www.ietf.org/mailman/listinfo/trans
>>
>>
>

v2.46.0 | Report a Bug | By Email | System Status