Re: [Trans] Starting to think about IETF 90

Dmitry Belyavsky <beldmit@gmail.com> Tue, 03 June 2014 11:36 UTC

Return-Path: <beldmit@gmail.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B0101A01C4 for <trans@ietfa.amsl.com>; Tue, 3 Jun 2014 04:36:19 -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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 DVzXuhUX2mtp for <trans@ietfa.amsl.com>; Tue, 3 Jun 2014 04:36:17 -0700 (PDT)
Received: from mail-yh0-x232.google.com (mail-yh0-x232.google.com [IPv6:2607:f8b0:4002:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 091711A0190 for <trans@ietf.org>; Tue, 3 Jun 2014 04:36:16 -0700 (PDT)
Received: by mail-yh0-f50.google.com with SMTP id 29so4944216yhl.37 for <trans@ietf.org>; Tue, 03 Jun 2014 04:36:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=w9MPxzGEyqKAtvT5fjd08PXV0WMYsFsU7Xyri/3ArXo=; b=b7T4yIZsOcYhBbonEPxrxPLKRT147FGd4VA2ZVtHBH34y0k5uQol1RRrpSObn/U7nM Diwwa1x1EaYnMjxYxTMOu0q46ZohVoX7KqH0gSt6+qmKmtajEqpO7zcjg5Rw2GA+puXm xk82BauOPkljGsVcd1vIfkjgRsd5/dARdA73hmeqr7gXgeMFxwrD+V18GfBrWQ1ouhko ehFsXjoYLO3dhPaEcCAUjBfphzSaEq07V/5czQPK0A+rPgQ+ercPV+VydeGaHKcXOCd9 PR8gFB8pKQOBxPinsFJt3aM7BbkruFT/SBkd4M+Bbrayy1yy3TAF1oHiCsUatBmAXv0u 0FdA==
MIME-Version: 1.0
X-Received: by 10.236.46.5 with SMTP id q5mr61410431yhb.21.1401795370983; Tue, 03 Jun 2014 04:36:10 -0700 (PDT)
Received: by 10.170.91.85 with HTTP; Tue, 3 Jun 2014 04:36:10 -0700 (PDT)
In-Reply-To: <538CE2F1.8020905@gmail.com>
References: <538CE2F1.8020905@gmail.com>
Date: Tue, 03 Jun 2014 15:36:10 +0400
Message-ID: <CADqLbz+oQSSsGv0nKTDR6WZE3HOar_bYe9ZzcRzhptDjqzyydg@mail.gmail.com>
From: Dmitry Belyavsky <beldmit@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary="047d7b5d839122a75e04faeceb98"
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/N3UgvbbfZTroMpyasd1xtqm9U2Y
Cc: "trans@ietf.org" <trans@ietf.org>
Subject: Re: [Trans] Starting to think about IETF 90
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 03 Jun 2014 11:36:19 -0000

Hello Melinda,


On Tue, Jun 3, 2014 at 12:47 AM, Melinda Shore <melinda.shore@gmail.com>
wrote:

>
> So, if you've got a document that you're trying to progress,
> now's a very good time to post to the mailing list with a
> pointer to the document, a quick summary of what you're
> trying to do, and what you think the open issues are or
> areas that need discussion.
>

Unfortunately, I will not be present in Toronto.
So I think there are the following problems that are the subject to solve
for putting the CT into real world.

1. The behaviour of CT-supporting clients is underspecified. There are a
lot of corner cases that should be a subject for clarification. I have sent
the draft of my vision mixed with mostly Ben’s answers about the client
behaviour to the Trans list some time ago. As there is no objections or
agreements, I think that my suggestions should be either ignored and
replaced by a specification written from scratch or adopted as a part of
RFC after discussion.
Also the absence of the gossip protocol description disturbs me too.

2. There is a lack of understanding of infrastructure which is necessary
for the deployment of CT. If we get a hundred of logs, it is not better
than a hundred of CAs we have now. If we found a misbehaviour of log or of
a CA, it should be reported to - where? As far as I understand, this is out
of scope for IETF, but who will establish the rules here?

The adoption of the CT to operate together with DNSSec seems to be a
separate topic and I think, there should be a separate document covering it.


Thank you!
-- 
SY, Dmitry Belyavsky