IETF Logo Mail Archive

Re: [websec] DISCUSS positions on draft-ietf-websec-key-pinning

Barry Leiba <barryleiba@computer.org> Sat, 11 October 2014 20:04 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D9641A8789 for <websec@ietfa.amsl.com>; Sat, 11 Oct 2014 13:04:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 sSPaA3uX5HjG for <websec@ietfa.amsl.com>; Sat, 11 Oct 2014 13:03:58 -0700 (PDT)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54A941A877D for <websec@ietf.org>; Sat, 11 Oct 2014 13:03:58 -0700 (PDT)
Received: by mail-ig0-f172.google.com with SMTP id r2so6473814igi.11 for <websec@ietf.org>; Sat, 11 Oct 2014 13:03:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=w3Vgb6aOHsFSkzPvKsMRxDMJV+scIWNq8Ds7PRWxyaM=; b=lauEoDiCjEoCT0Y9cdioPzB+ji/re1GG+Det+t7IFlMGFxB3w+ZexDo24uI59pev/r ltG0used2UPdC4dYRmv94/g6R/w95HomEbDORElrHwnK5y9cSrYExjYZaFKRrVlevVk9 6I+lq5laq6OxJfmFhhSqLPYK+zFxLo3T59ZXgmuowRAYWyIx22Pb9owVKJNuAq6OFyE0 910/y+wGYCUP4UUHkIr0eEFOOp9ZPKpq0emh5iE07bwn/9S2mGsaXFnokuz82V84CwFg sezv1OTmjpSEKu1n0TTQTe4/aBgy88ujyNYrwwh35ShdOD817KZMx99fGYgPaltwaWTZ g0oQ==
MIME-Version: 1.0
X-Received: by 10.50.143.73 with SMTP id sc9mr17420612igb.29.1413057837767; Sat, 11 Oct 2014 13:03:57 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.163.3 with HTTP; Sat, 11 Oct 2014 13:03:57 -0700 (PDT)
In-Reply-To: <CAC4RtVAZabjOPOkZqUU+s4+y3zErMYE6szdAJNxhfU3vftQu-w@mail.gmail.com>
References: <CAC4RtVDiy-QbHNREsm07+iPzjDiZ1q5GjowZCBnP63nw1ezTAw@mail.gmail.com> <CAC4RtVBg6Hx5iteZ+HHz=Lk8qbRUDA00EBbOG3FQp5U4ZjgS9A@mail.gmail.com> <C8AB7FB1-8E0D-4EDE-8735-892FF40B6F4F@nominum.com> <7E8E7D4E-61D0-4C6B-B5CC-FFAE1BF80699@gmail.com> <CAC4RtVAZabjOPOkZqUU+s4+y3zErMYE6szdAJNxhfU3vftQu-w@mail.gmail.com>
Date: Sat, 11 Oct 2014 16:03:57 -0400
X-Google-Sender-Auth: -g8Qf4b63GbsTXoTSegt6nMhUzU
Message-ID: <CAC4RtVCGUSkp0F=FJhdofQ2J47qeYK=pZ2ne83sj0=qQQdej1w@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "draft-ietf-websec-key-pinning.all@tools.ietf.org" <draft-ietf-websec-key-pinning.all@tools.ietf.org>
Content-Type: multipart/alternative; boundary="001a1134cb0e77a3d005052b2a12"
Archived-At: http://mailarchive.ietf.org/arch/msg/websec/3jhWYi-1eV5QO4xNzH6C1MnDrAY
Cc: IETF WebSec WG <websec@ietf.org>
Subject: Re: [websec] DISCUSS positions on draft-ietf-websec-key-pinning
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/websec>, <mailto:websec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/websec/>
List-Post: <mailto:websec@ietf.org>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Oct 2014 20:04:00 -0000

Ryan, thanks for getting the last of the changes done, and all the
DISCUSSes cleared.  I've sent the approval note to the IESG Secretary, and
we should see the announcement on Monday.

The document will now go into the RFC Editor queue, and you'll hear from
them and have to respond when they do the final edits, in AUTH48 state.

Everyone, thanks for the work on this.  The working group will officially
remain open until the RFC is published, after which I'll close it, but will
leave the mailing list open for any continued discussion.

Barry, Applications AD

v2.23.0 | Report a Bug | By Email