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

Also, RFC 5937 defines how to process the constraints from the 5914
structure.

On 10/7/17, 11:31 PM, "pkix on behalf of Peter Bowen"
<[email protected] on behalf of [email protected]> wrote:

>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
>
>_______________________________________________
>pkix mailing list
>[email protected]
>https://www.ietf.org/mailman/listinfo/pkix