IETF Logo Mail Archive

Re: [pkix] [smime] Key lookup service via draft-bhjl-x509-srv-00

Wei Chuang <weihaw@google.com> Wed, 23 March 2016 21:29 UTC

Return-Path: <weihaw@google.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85EDE12D947 for <pkix@ietfa.amsl.com>; Wed, 23 Mar 2016 14:29:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable 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 VN5tRdQX3_jL for <pkix@ietfa.amsl.com>; Wed, 23 Mar 2016 14:29:15 -0700 (PDT)
Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::233]) (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 0380812D7F0 for <pkix@ietf.org>; Wed, 23 Mar 2016 14:29:14 -0700 (PDT)
Received: by mail-vk0-x233.google.com with SMTP id z68so35753071vkg.3 for <pkix@ietf.org>; Wed, 23 Mar 2016 14:29:13 -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; bh=JPgaUBP5T3a/0tyEEV2nmggFStDKjlRUrG0f3VoF1RY=; b=Rqjt/2gspOALVb0n9eZ/8GS9EOEZyrkQzVwmOGt/zuWn29boWUZ9FsnibZvkXbhIo1 SgrF/sjKQdO/QYBkGIwOJ6FhD1RCx071JmirVkmXMuKp3hvHffpZbpQKCVOBLIPJTcJU uh5p8Sp2vOLFmKHGUiAMkLgHFznMQnSNA7wpTNOn74y0ZOFOzNi+oMP+j6E4sHHcoX+2 rFdcEB9cbdDSmsYjKLD+2SQZR7F2Yc/ab/+75CcL/s6CckoxwiLOl4CcjNCBy1ewz1cQ SoeXg+6IDnRMo+0MtIfG8sGa1LmrYr4D3HaARYxRqlL+ZJmy46NL69SX3VNIdU1vul4+ KG/g==
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; bh=JPgaUBP5T3a/0tyEEV2nmggFStDKjlRUrG0f3VoF1RY=; b=RFgJuDt3SubMjgBKq/0yTAyQEb0QoX0PY/n8PlowqUa+0EQZLG2Max4twVMAakHZOk V3ecavEp+j4rT/rJskpFqxb1PUHLV0ns8fYKXMZBf7ZAai8Vmfhd6ZeM5ucmFDtgPEqD Cgm3ws+2oTT82p5kD3V3pajuNmlDu6++Xy5TBIXBh2xHqCbOSkh4JP4RGept/tc9qRWk ttdOczUDTQpRGMXvyCKYyx07x4BF512oJSfdc4wRZUzSW4AJR6YLiipMRqWSl+D0ZopE qLBQWshKgeQh31UOSJIh1zMRnme0LE2kAW+ZPQ1pDs3EY/qYcq4AHeFP5snO2Lf4TRtF Sw6A==
X-Gm-Message-State: AD7BkJIMCaRFp2A6X/3d+5bsXdXMh37ULkZID/eCQO4Z8HXVAHOGPVBgYFHKdYWEfAPQ5CkRxooFjh7m2JDQc2mC
MIME-Version: 1.0
X-Received: by 10.159.40.168 with SMTP id d37mr2583289uad.83.1458768552896; Wed, 23 Mar 2016 14:29:12 -0700 (PDT)
Received: by 10.159.36.179 with HTTP; Wed, 23 Mar 2016 14:29:12 -0700 (PDT)
In-Reply-To: <FB501B0B-999D-45E4-A739-4D561A25275B@mitre.org>
References: <CAAFsWK3HEXDgqONxBohBCGMKk2qMa230fxcNEaGhoTwQZVYQoQ@mail.gmail.com> <alpine.OSX.2.11.1603221443230.18473@ary.lan> <CAAFsWK2Xbw0eU2oz4edtmPH5PhwJgQkTYWKhFruZnCnD37c_CQ@mail.gmail.com> <alpine.OSX.2.11.1603231431110.4624@ary.lan> <FB501B0B-999D-45E4-A739-4D561A25275B@mitre.org>
Date: Wed, 23 Mar 2016 14:29:12 -0700
Message-ID: <CAAFsWK1p-_HNYwM1B-p8MMo58u2hURW45ytKr_1f3h+XKDS5wA@mail.gmail.com>
From: Wei Chuang <weihaw@google.com>
To: "Miller, Timothy J." <tmiller@mitre.org>
Content-Type: multipart/alternative; boundary="94eb2c1238426811c6052ebe051c"
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/w6dONSCkremDK5BUFW7M0ZxjgvQ>
Cc: PKIX <pkix@ietf.org>, Brian Haberman <brian@innovationslab.net>, John R Levine <johnl@taugh.com>, IETF SMIME <smime@ietf.org>
Subject: Re: [pkix] [smime] Key lookup service via draft-bhjl-x509-srv-00
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2016 21:29:17 -0000

On Wed, Mar 23, 2016 at 1:00 PM, Miller, Timothy J. <tmiller@mitre.org>
wrote:

> On 3/23/16, 1:33 PM, "smime on behalf of John R Levine" <
> smime-bounces@ietf.org on behalf of johnl@taugh.com> wrote:
>
>
>
> >If the WG thinks the domain's key should be authoritative, that'd be fine
> >with me.  We didn't want to make any unilateral changes to the trust model
> >without it being clear that it's a change and that there's consensus
> >behind it.
>
> So an authoritative service makes sense in an Enterprise context, but not
> in a consumer context.  How do you preserve consumer choice if Yahoo! owns
> their email service, but they want to certify keys elsewhere?
>

Could Yahoo! (in this example) not provide a means for their users to
update the key lookup service?  As the user is authenticated through their
UI, he or she could upload the keys they want in a secure way.   (A
realistic deployment caveat might be that Yahoo! puts some restrictions on
e.g. Yahoo! might not support self-signed, weak key sizes etc).  One might
argue Yahoo! wouldn't want to provide a key service, but then that's fine.
Without the SRV RR, things should be defined to fall back to the current
state of things.

-Wei


>
> -- T
>
>

v2.23.0 | Report a Bug | By Email