Jim said: >> I do not have a current use case in terms of a specific application. I >> just note that having a time that things are signed is common practice >> in many documents that are used today. As such I believe it will be a >> common attribute on signatures that will be needed in the future.
Anthony responded: > Really think we should not be adding things w/o the proper use case, as > we have a ton of nice to have things but we also have no use cases so > we have not burdened the group with these It will be much much harder to define & deploy something like signing time in the future as it will break all existing clients (as they will see a field they don't understand and reject the message). If we want to postpone lots of nice-to-have features to later, then we need to change the MUST-understand-everything rule so there is not such a high penalty for postponing. -- James Manger >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On Behalf >> Of Jim Schaad >> Sent: Tuesday, October 9, 2012 11:34 AM >> To: [email protected] >> Subject: [jose] Proposal - Create a SignTime Header >> >> I propose that we create a header entry that is optional and contains >> a time that the signer claims that they signed at. ... _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
