W3C home > Mailing lists > Public > public-webcrypto@w3.org > August 2012

Closing ISSUE-16

From: Ryan Sleevi <sleevi@google.com>
Date: Thu, 30 Aug 2012 16:29:48 -0700
Message-ID: <CACvaWvYbH6hbU4VSOZC-73-8BqJ3Gm044G7kNkA6CNASYoDYEA@mail.gmail.com>
To: public-webcrypto@w3.org
During the mailing list discussions, I feel like we reached some degree of
consensus that key expiration was something that would be left to
individual applications to implement, and not an inherent feature of the
API. Vijay captured a variety of situations where "removing" or "preventing
use of" (including raising JavaScript errors) would be the undesirable
behaviour.

Are there any objections to closing ISSUE-16 by:
- Removing startData/endDate from "first class" attributes on the object,
leaving them to be implemented within KeyAttributes instead
- Closing ISSUE-16
Received on Thursday, 30 August 2012 23:30:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 30 August 2012 23:30:16 GMT