Hi Geoff, As I listened to the recorded version of the session in Beijing, looks like there some level of consensus that it may be a good idea to add an additional "error_response" code value for "algorithm suite not supported". I believe that will help the algorithm migration process as we can write the exact process in the draft.
You could always use the code 1203, but that is a generic response to a malformed message. Regards, Roque On Nov 11, 2010, at 4:22 AM, Geoff Huston wrote: > Hi, > > I've revised this draft as per the feedback from the WG in today's SIDR > meeting regarding text in the Security Considerations that notes that the > protocol itself does not describe how a client and a server can "reset" the > CMS signing time attribute value > > Given that this addresses the WG comments from today's session. I'd like to > request the chairs to conduct a WG Last Call for this draft. > > thanks > > Geoff & Byron > > > Begin forwarded message: > >> From: IETF I-D Submission Tool <[email protected]> >> Date: 11 November 2010 2:16:44 PM AEDT >> To: [email protected] >> Cc: [email protected],[email protected],[email protected] >> Subject: New Version Notification for >> draft-ietf-sidr-rescerts-provisioning-09 >> >> >> A new version of I-D, draft-ietf-sidr-rescerts-provisioning-09.txt has been >> successfully submitted by Geoff Huston and posted to the IETF repository. >> >> Filename: draft-ietf-sidr-rescerts-provisioning >> Revision: 09 >> Title: A Protocol for Provisioning Resource Certificates >> Creation_date: 2010-11-11 >> WG ID: sidr >> Number_of_pages: 31 >> >> Abstract: >> This document defines a framework for certificate management >> interactions between a resource issuer ("Issuer") and a resource >> recipient ("Subject") through the specification of a protocol for >> interaction between the two parties. The protocol supports the >> transmission of requests from the Subject, and corresponding >> responses from the Issuer encompassing the actions of certificate >> issuance, certificate revocation and certificate status information >> reports. This protocol is intended to be limited to the application >> of resource certificate management and is not intended to be used as >> part of a more general certificate management framework. >> >> >> >> The IETF Secretariat. >> >> > > -- > > Geoff Huston > Chief Scientist, APNIC > > +61 7 3858 3100 > [email protected] > > > > > _______________________________________________ > sidr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/sidr
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
