Re: New Version Notification for draft-belyavskiy-certificate-limitation-policy-04.txt

Peter Bowen <[email protected]>
Newsgroups gmane.ietf.saag,gmane.ietf.x509,gmane.comp.mozilla.devel.security.policy
Message-ID <CAK6vND90Fryurf4QZYnjaw8iMmhn7=pE4YgW+5R2i5ertMGWsg@mail.gmail.com> 
On Tue, Sep 12, 2017 at 5:59 AM, Dmitry Belyavsky via
dev-security-policy <[email protected]> wrote:
> Here is the new version of the draft updated according to the discussion on
> mozilla-dev-security list.

Given that RFC 5914 already defines a TrustAnchorList and
TrustAnchorInfo object and that the Trust Anchor List object is
explicitly contemplated as being included in a signed CMS message,
would it not make more sense to start from 5914 and define new
extensions encode constraints not currently defined?

Thanks,
Peter
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.