Hello,

Here is the new version of the draft updated according to the discussion on
mozilla-dev-security list.

---------- Forwarded message ----------
From: <[email protected]>
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 <[email protected]>



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-certif
icate-limitation-policy-04.txt
Status:         https://datatracker.ietf.org/doc/draft-belyavskiy-certifica
te-limitation-policy/
Htmlized:       https://tools.ietf.org/html/draft-belyavskiy-certificate-li
mitation-policy-04
Htmlized:       https://datatracker.ietf.org/doc/html/draft-belyavskiy-cert
ificate-limitation-policy-04
Diff:           https://www.ietf.org/rfcdiff?url2=draft-belyavskiy-certific
ate-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
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy

Reply via email to