Re: [therightkey] Comments on -> Re: WG Review: Public Notary, Transparency (trans)
=JeffH <Jeff.Hodges@KingsMountain.com> Fri, 24 January 2014 18:55 UTC
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: therightkey@ietfa.amsl.com
Delivered-To: therightkey@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com
(Postfix) with ESMTP id 6F5681A0100 for <therightkey@ietfa.amsl.com>;
Fri, 24 Jan 2014 10:55:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.897
X-Spam-Level:
X-Spam-Status: No,
score=-0.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334,
RCVD_IN_SORBS_WEB=0.77, SPF_PASS=-0.001] autolearn=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 LUhWgdP2mfSO for
<therightkey@ietfa.amsl.com>; Fri, 24 Jan 2014 10:55:06 -0800 (PST)
Received: from oproxy6-pub.mail.unifiedlayer.com
(oproxy6-pub.mail.unifiedlayer.com [67.222.54.6]) by ietfa.amsl.com (Postfix)
with SMTP id A14551A0046 for <therightkey@ietf.org>;
Fri, 24 Jan 2014 10:55:06 -0800 (PST)
Received: (qmail 19887 invoked by uid 0); 25 Jan 2014 01:55:03 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by
oproxy6.mail.unifiedlayer.com with SMTP; 25 Jan 2014 01:55:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=kingsmountain.com; s=default;
h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID;
bh=Fur4AJVDtjdMKK+25pZiPlG2FOX0uu6k8JhDyXxzu+o=;
b=0grRFI2bqbWwz9TlM/R4Hq19UW3jC63zPX9n2CaDFw2wOWATz1V0s161BA9dDmt25Mo4zc9za2RichkC3CUvUPhW84P36/F5LnsT9AgltmNu6QFX3YtqSwJzdhYWpooq;
Received: from [216.113.168.128] (port=26063 helo=[10.244.137.220]) by
box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.80)
(envelope-from <Jeff.Hodges@KingsMountain.com>) id 1W6luD-0004vt-70;
Fri, 24 Jan 2014 11:55:05 -0700
Message-ID: <52E2B706.8040301@KingsMountain.com>
Date: Fri, 24 Jan 2014 10:55:02 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:17.0) Gecko/20130330 Thunderbird/17.0.5
MIME-Version: 1.0
To: IETF PKI next gen discussion list <therightkey@ietf.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com}
{sentby:smtp auth 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Cc: The IESG <iesg@ietf.org>
Subject: Re: [therightkey] Comments on -> Re: WG Review: Public Notary,
Transparency (trans)
X-BeenThere: therightkey@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <therightkey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/therightkey>,
<mailto:therightkey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/therightkey/>
List-Post: <mailto:therightkey@ietf.org>
List-Help: <mailto:therightkey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/therightkey>,
<mailto:therightkey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 18:55:07 -0000
> On 24 January 2014 18:29, Paul Lambert <paul@marvell.com> wrote: >> >> Comments on draft Public Notary Transparency: >> >> - ŒTransparent Public Notary¹ would be better for a group name >> and match the new charter more closely (versus original charter >> was making an existing service Transparent) >> >> - charter is too public key focused. A Merkle Hash Tree can support >> a notary-like facility for any information that can be hashed >> Suggest changing paragraph two to use current examples but >> add a non-public key example and down-play public keys as just an >> example >> >> - Is ŒPublic¹ necessary in the title and as a goal? >> A ŒTransparent Notary¹ could be public or private. Enterprise or >> private >> applications could readily benefit from notary functions. >> suggest removing public from title and add a sentence in scope >> describing public an private applications. > > The focus on public keys is deliberate. As the second work item says, > WG would re-charter for transparency of other things. This is because > it turns out that whilst there's clearly a general mechanism, there's > a lot of details that may change depending on what exactly is being > logged. +1 > >> >> - word-smithing for readability would be beneficial. Especially >> the introduction to better capture the groups new focus. >> >> Paul >> >> >>