Hi wg, I see more and more road maps that include implementing Key and Signing Policies, so Jerry and I thought it would be a good idea to standardize the policy model and the behavior of its elements.
Ideally, policies can be used between multiple different software products, and if you do, you expect the same behavior. Here is an initial draft for this, we would appreciate your feedback. Best regards, Matthijs -------- Original Message -------- Subject: New Version Notification for draft-mekking-dnsop-kasp-00.txt Date: Fri, 04 Jul 2014 01:25:01 -0700 From: [email protected] To: W. (Matthijs) Mekking <[email protected]>, "Jerry Lundstroem" <[email protected]>, Jerry Lundstroem <[email protected]>, "Matthijs Mekking" <[email protected]> A new version of I-D, draft-mekking-dnsop-kasp-00.txt has been successfully submitted by W. (Matthijs) Mekking and posted to the IETF repository. Name: draft-mekking-dnsop-kasp Revision: 00 Title: DNSSEC Key and Signing Policies Document date: 2014-07-04 Group: Individual Submission Pages: 16 URL: http://www.ietf.org/internet-drafts/draft-mekking-dnsop-kasp-00.txt Status: https://datatracker.ietf.org/doc/draft-mekking-dnsop-kasp/ Htmlized: http://tools.ietf.org/html/draft-mekking-dnsop-kasp-00 Abstract: This document describes how key policies should look like. 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 _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
