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

Dear Max,

The letter that seems the most significant for me is here:
https://groups.google.com/d/msg/mozilla.dev.security.policy/--aa6dYHhrc/xbozEdS2BgAJ

This letter enumerates the lion's share of limitations currently applied by
Mozilla, if I am correct.

On Tue, Sep 12, 2017 at 6:16 PM, Dr. Pala <madwolf@openca.org> wrote:

> 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>
> Date: Tue, Sep 12, 2017 at 3:55 PM
> Subject: New Version Notification for draft-belyavskiy-certificate-l
> imitation-policy-04.txt
> To: Dmitry Belyavskiy <beldmit@gmail.com>
>
>
>
> A new version of I-D, draft-belyavskiy-certificate-l
> imitation-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
> Status:         https://datatracker.ietf.org/
> doc/draft-belyavskiy-certificate-limitation-policy/
> Htmlized:       https://tools.ietf.org/html/d
> raft-belyavskiy-certificate-limitation-policy-04
> Htmlized:       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
>
> 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.
>
> The IETF Secretariat
>
>
>
>
> --
> SY, Dmitry Belyavsky
>
>
> _______________________________________________
> Spasm mailing listSpasm@ietf.orghttps://www.ietf.org/mailman/listinfo/spasm
>
>
>
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm
>
>

-- 
SY, Dmitry Belyavsky