Re: [Trans] Compatibility of name redaction and EV

Ben Laurie <benl@google.com> Tue, 19 August 2014 21:02 UTC

Return-Path: <benl@google.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 7216B1A04C5 for <trans@ietfa.amsl.com>; Tue, 19 Aug 2014 14:02:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.047
X-Spam-Level:
X-Spam-Status: No, score=-2.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, RP_MATCHES_RCVD=-0.668, 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 90O7rrAdLsc7 for <trans@ietfa.amsl.com>; Tue, 19 Aug 2014 14:02:44 -0700 (PDT)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A59981A013B for <trans@ietf.org>; Tue, 19 Aug 2014 14:02:44 -0700 (PDT)
Received: by mail-qc0-f174.google.com with SMTP id l6so6849116qcy.33 for <trans@ietf.org>; Tue, 19 Aug 2014 14:02:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4dYvLph/xHoDtT0ngZP6JL5xm2hOffratyMFI5/uuFk=; b=K+213TU83jjBrYZm+MFeBvoA4L0qbQL9Ml49PuZwlX0TEdu4Thq9stzwGhX1efC5oo z36W8z6KRc6V5f/iB8n2IJDHMP/2Qm0tNb1UVKP0RX2Wv6mgmsNZM3MR4ey9DnI4cZFI gtQRSpqb6YW0d9Um6aaydLFn4J8mK6CK57sBXwY0VWJ14rqeT8tECVjk2R5Y6/gicNKC bs9s1j7q53UfvG4k+dg272EuA456bi2XqPGS2lhUyjk9QArQ3zYLRKQiDCn4sqQfT5RE P6ljzRpxq5PEZKF8SZSKVYMpltNdlOE+n2MtIwuwVjswSRwaYl1GVJ++AHbNfkHKyFfa paEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4dYvLph/xHoDtT0ngZP6JL5xm2hOffratyMFI5/uuFk=; b=LLrvQjZTFDxuMNfOM6DRLAeuYoHQ/B7OwX28tFVVpPYHzFW2Iz6vsRUBo3cGiGi9vY fboSAdP+16HL7QXzmYdnoU8CX4aoKY7XzfYJKGCHixMzvAeW5KA37CFrE2A+QMX7Zqef ZW0TFNe2iT1n206DhRzj3Ho5ABi5E+Jl+IPN+S4UpaN3Z496keXmV8kxkTH3iaC3rgHY 4kQ3MVxFowS2AwLJBrOFgPAIA6qTBlg+zh1pUX1L2Sn/fpL5WHW/8q6WVvL2G/orfgmL vcoIdHbkmCEdoRx11zzQsmuNkwlMfzWFDcnUOldL09cj8tD4Mwd5KkbcKU5AVbZ/fjva uIug==
X-Gm-Message-State: ALoCoQnMew59lVmELAhLfIU51hfraGQN9lOPzS1RBN5w6lt1mxCtV2So7/VZUpboWUYMSxovVsOO
MIME-Version: 1.0
X-Received: by 10.224.51.197 with SMTP id e5mr18985817qag.48.1408482162261; Tue, 19 Aug 2014 14:02:42 -0700 (PDT)
Received: by 10.229.40.68 with HTTP; Tue, 19 Aug 2014 14:02:42 -0700 (PDT)
In-Reply-To: <53F3B6C4.2000108@bbn.com>
References: <CABrd9SQ=mW7DoQUkXGv5M=nuoR1fTFG5N1Qc_PyK+mtm6E6s_A@mail.gmail.com> <53F25A33.5020405@bbn.com> <CABrd9SQcYQCV93CC-1DocNwOrKa0aJVqMaOMVRPWJt3pinvuiA@mail.gmail.com> <53F26610.8000608@bbn.com> <CABrd9SQWyNjvHdZXJ_eZCg4iFtdUxrWDQL1uVuAM+xnvdMCdFA@mail.gmail.com> <53F39933.8030706@bbn.com> <CABrd9SRXC+n4D=L9CcxuhXuQBj0Ff=KrW81r_J8ZWAurxUL1xA@mail.gmail.com> <53F3B6C4.2000108@bbn.com>
Date: Tue, 19 Aug 2014 14:02:42 -0700
Message-ID: <CABrd9SSdSW03ZfxAAu378zJYbRjJFRfz44fbp-ioEGokaE05-w@mail.gmail.com>
From: Ben Laurie <benl@google.com>
To: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/59LeKHLR6zB-a6i0Uj5u7m5WDmk
Cc: "trans@ietf.org" <trans@ietf.org>
Subject: Re: [Trans] Compatibility of name redaction and EV
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, 19 Aug 2014 21:02:46 -0000

On 19 August 2014 13:42, Stephen Kent <kent@bbn.com> wrote:
> Ben,
>
>> ...
>>
>>> It's rather unusual for an author of an RFC to publicly state that he
>>> plans
>>> to ignore the RFC if it doesn't match his implementation plans.
>>
>> As you are fond of pointing out, I am not the author, I am one of the
>> editors. I am perhaps overly honest in stating up front that I will
>> not unconditionally follow the consensus decisions of the WG, but
>> surely this is far from being a unique stance.
>
> I don't recall making that observation about your role in generating
> this doc. Can you point to a message from me that made that statement,
> i.e., that you are an editor, not a doc author? I just don't recall.

I thought that was the gist of several of your comments wrt to
consensus in the last WG meeting, but I could be misrepresenting you.
If so, my apologies.

> I agree that it is common to speak of doc editors, especially when the
> content is derived from many sources, e.g., WG list discussions. In this
> case,
> the source for the initial doc material was very narrow, and I believe
> Eran said that you are the one responsible for making edits to address
> issues.
> So, forgive my choice of words to describe your role.
>
> As for a public statement wrt ignoring WG consensus (in an implementation)
> by a doc "editor" it strikes me as very unusual, if not unique, based on
> my 28 years of IETF participation.

But that's not what I'm saying - what I'm saying is I can't say in
advance that this standard is one I want to implement, given that I
don't know what it says yet. I think it would be pretty crazy to say
otherwise.

I am not saying this is a _likely_ outcome, just that its a possible one.

It doesn't seem like a point worth dwelling on.