kmip message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [kmip] Groups - v0.2KMIPRevokeUpdate.docx uploaded
- From: "Bruce Rich" <brich@us.ibm.com>
- To: Judith Furlong <Judith.Furlong@emc.com>
- Date: Thu, 22 Oct 2015 14:52:09 -0500
I like Option 1, except that we've now
added another "if" before the last "otherwise". To
clarify the "otherwise", I would suggest substituting the following
phrase to replace "Otherwise"
...If the revocation reason is neither “key
compromise” nor “CA compromise”...
so the sentence would now read
If the revocation reason is neither
“key compromise” nor “CA compromise”,
the object is placed into the “deactivated” state, and the Deactivation
Date attribute is set to the current date and time.
Bruce A Rich
brich at-sign us dot ibm dot com
From:
Judith Furlong <Judith.Furlong@emc.com>
To:
kmip@lists.oasis-open.org
Date:
10/22/2015 10:06 AM
Subject:
[kmip] Groups
- v0.2KMIPRevokeUpdate.docx uploaded
Sent by:
<kmip@lists.oasis-open.org>
Document
Name: v0.2KMIPRevokeUpdate.docx
Description A proposal outlining two options for changing the description of the Revoke operation (section 4.20 of KMIP Spec) to be clearer and consistent. Download
Latest Revision Public
Download Link
Submitter: Ms. Judith Furlong Group: OASIS Key Management Interoperability Protocol (KMIP) TC Folder: Drafts Date submitted: 2015-10-22 08:05:32
|
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]