Re: [Trans] [trans] #118 (rfc6962-bis): Monitor function description problem

Stephen Kent <kent@bbn.com> Wed, 16 March 2016 17:50 UTC

Return-Path: <kent@bbn.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 2769A12DA4A for <trans@ietfa.amsl.com>; Wed, 16 Mar 2016 10:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 0SISId9VTsDS for <trans@ietfa.amsl.com>; Wed, 16 Mar 2016 10:50:51 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3E4512D52D for <trans@ietf.org>; Wed, 16 Mar 2016 10:50:51 -0700 (PDT)
Received: from ssh.bbn.com ([192.1.122.15]:48495 helo=COMSEC.fios-router.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1agFas-00090X-Uq for trans@ietf.org; Wed, 16 Mar 2016 13:50:51 -0400
From: Stephen Kent <kent@bbn.com>
To: trans@ietf.org
References: <053.295250cc5a90d6e6c0794fe09149ea46@tools.ietf.org> <068.0779562256ffb55d064ab4f9e5d0a31c@tools.ietf.org>
Message-ID: <56E99CFA.8010601@bbn.com>
Date: Wed, 16 Mar 2016 13:50:50 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <068.0779562256ffb55d064ab4f9e5d0a31c@tools.ietf.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/trans/n63dKlN8RIEkPyUxaXSqxu8jVLg>
Subject: Re: [Trans] [trans] #118 (rfc6962-bis): Monitor function description problem
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.17
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, 16 Mar 2016 17:50:53 -0000

Eran,

> #118: Monitor function description problem
>
> Changes (byeranm@google.com)
>
>   * owner:draft-ietf-trans-rfc6962-bis@tools.ietf.org  =>eranm@google.com
>
>
> Comment:
>
>   Is the problem here that the term 'monitoring' means something different
>   in this context, making the introduction and Section 9.3. inconsistent?
>   I can suggest a few resolutions:
>   (1) Replacing the word 'monitor' in the introduction with 'watch'.
>   (2) Modify the Monitor section to indicate a monitor can either ensure
>   logs behave correctly, watch for certificates of interest or do both.
In most prior versions of 6962-bis, Auditing has focused on detecting
mis-behaving logs. Why not stick with that characterization of the 
function?
Your suggestion #2 above seems to make Monitors overlap with Auditors,
rather than having simple, distinct definitions for them.

Let's   say that a Monitor observes an enumerated set of logs for certs 
of interest,
so that it can inform Subjects if there is evidence that a bogus cert has
been logged (relative to the Subject in question).

An Auditor observes an enumerated set of losg to detect log misbehavior.

These are roughly the ways that draft-kent-trans-monitor-auditor-00.txt
characterizes the two functions.

Steve