IETF Logo Mail Archive

Re: [lamps] [pkix] Fwd: New Version Notification for draft-belyavskiy-certificate-limitation-policy-04.txt

"Dr. Pala" <madwolf@openca.org> Tue, 12 September 2017 15:16 UTC

Return-Path: <madwolf@openca.org>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8951C13304F for <spasm@ietfa.amsl.com>; Tue, 12 Sep 2017 08:16:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.63
X-Spam-Level:
X-Spam-Status: No, score=-1.63 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, SPF_PASS=-0.001, T_HK_NAME_DR=0.01] 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 YyVpQfMHzPjC for <spasm@ietfa.amsl.com>; Tue, 12 Sep 2017 08:16:14 -0700 (PDT)
Received: from mail.katezarealty.com (mail.katezarealty.com [104.168.158.213]) by ietfa.amsl.com (Postfix) with ESMTP id 7E4F813302A for <spasm@ietf.org>; Tue, 12 Sep 2017 08:16:14 -0700 (PDT)
Received: from maxs-mbp.cablelabs.com (host64-111.cablelabs.com [192.160.73.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.katezarealty.com (Postfix) with ESMTPSA id 167D637404C1 for <spasm@ietf.org>; Tue, 12 Sep 2017 11:16:14 -0400 (EDT)
To: spasm@ietf.org
References: <150522092693.4724.2532571098567577114.idtracker@ietfa.amsl.com> <CADqLbz+OB86s4E-Ntr6eaEow+sBtxscJ703nGN+PAS7zQmJ==Q@mail.gmail.com>
From: "Dr. Pala" <madwolf@openca.org>
Message-ID: <a0956ff8-9125-23d5-b687-1a6cc3b83558@openca.org>
Date: Tue, 12 Sep 2017 09:16:14 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CADqLbz+OB86s4E-Ntr6eaEow+sBtxscJ703nGN+PAS7zQmJ==Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------70CB07465012FF8D6A064047"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/I70ZnXNwLXSC-JNUwisGxG-lUaU>
Subject: Re: [lamps] [pkix] Fwd: New Version Notification for draft-belyavskiy-certificate-limitation-policy-04.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 15:16:16 -0000

Hi Dmitry,

could you please summarize the discussion that happened in the 
mozilla-dev-security?

Cheers,
Max


On 9/12/17 6:59 AM, Dmitry Belyavsky wrote:
> Hello,
>
> Here is the new version of the draft updated according to the 
> discussion on mozilla-dev-security list.
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
> Date: Tue, Sep 12, 2017 at 3:55 PM
> Subject: New Version Notification for 
> draft-belyavskiy-certificate-limitation-policy-04.txt
> To: Dmitry Belyavskiy <beldmit@gmail.com <mailto:beldmit@gmail.com>>
>
>
>
> A new version of I-D, 
> draft-belyavskiy-certificate-limitation-policy-04.txt
> has been successfully submitted by Dmitry Belyavskiy and posted to the
> IETF repository.
>
> Name:           draft-belyavskiy-certificate-limitation-policy
> Revision:       04
> Title:          Certificate Limitation Policy
> Document date:  2017-09-11
> Group:          Individual Submission
> Pages:          7
> URL: 
> https://www.ietf.org/internet-drafts/draft-belyavskiy-certificate-limitation-policy-04.txt 
> <https://www.ietf.org/internet-drafts/draft-belyavskiy-certificate-limitation-policy-04.txt>
> Status: 
> https://datatracker.ietf.org/doc/draft-belyavskiy-certificate-limitation-policy/ 
> <https://datatracker.ietf.org/doc/draft-belyavskiy-certificate-limitation-policy/>
> Htmlized: 
> https://tools.ietf.org/html/draft-belyavskiy-certificate-limitation-policy-04 
> <https://tools.ietf.org/html/draft-belyavskiy-certificate-limitation-policy-04>
> Htmlized: 
> https://datatracker.ietf.org/doc/html/draft-belyavskiy-certificate-limitation-policy-04 
> <https://datatracker.ietf.org/doc/html/draft-belyavskiy-certificate-limitation-policy-04>
> Diff: 
> https://www.ietf.org/rfcdiff?url2=draft-belyavskiy-certificate-limitation-policy-04 
> <https://www.ietf.org/rfcdiff?url2=draft-belyavskiy-certificate-limitation-policy-04>
>
> Abstract:
>    The document provides a specification of the application-level trust
>    model.  Being provided at the application level, the limitations of
>    trust can be distributed separately using cryptographically protected
>    format instead of hardcoding the checks into the application itself.
>
>
>
>
> Please note that it may take a couple of minutes from the time of 
> submission
> until the htmlized version and diff are available at tools.ietf.org 
> <http://tools.ietf.org>.
>
> The IETF Secretariat
>
>
>
>
> -- 
> SY, Dmitry Belyavsky
>
>
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm

v2.23.0 | Report a Bug | By Email