Subject: [Secdispatch] Fwd: New Version Notification for draft-belyavskiy-certificate-limitation-policy-07.txt

From: Dmitry Belyavsky <[email-masked]>
Date: Sun, 25 Nov 2018 21:37:35 +0300

Hello,

I've updated the draft draft-belyavskiy-certificate-limitation-policy
considering the discussions during Secdispatch@IETF103.

The updated document contains 2 changes:
1. Limitations are expected to be linked to root and intermediate CAs, not
to leaf certificates.
2. (Finally :) ) the examples of classes of applications expected to use
CLPs are provided.

Any comments are welcome.

---------- Forwarded message ---------
From: <[email-masked]>
Date: Sun, Nov 25, 2018 at 9:30 PM
Subject: New Version Notification for
draft-belyavskiy-certificate-limitation-policy-07.txt
To: Dmitry Belyavskiy <[email-masked]>

A new version of I-D, draft-belyavskiy-certificate-limitation-policy-07.txt
has been successfully submitted by Dmitry Belyavskiy and posted to the
IETF repository.

Name:           draft-belyavskiy-certificate-limitation-policy
Revision:       07
Title:          Certificate Limitation Policy
Document date:  2018-11-25
Group:          Individual Submission
Pages:          9
URL:
https://www.ietf.org/internet-drafts/draft-belyavskiy-certificate-limitation-policy-07.txt
Status:
https://datatracker.ietf.org/doc/draft-belyavskiy-certificate-limitation-policy/
Htmlized:
https://tools.ietf.org/html/draft-belyavskiy-certificate-limitation-policy-07
Htmlized:
https://datatracker.ietf.org/doc/html/draft-belyavskiy-certificate-limitation-policy
Diff:
https://www.ietf.org/rfcdiff?url2=draft-belyavskiy-certificate-limitation-policy-07

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.

-- 
SY, Dmitry Belyavsky