OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

kmip message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [kmip] Can Set Attribute modify an object's Usage Limits Count?

The specification wording there is poor. Basically Usage Limits Count is not allowed to be set at all by the client under any circumstances.
There should be no list of non-permitted operations present there - and that will fix this issue.

The table of Usage Limits Attribute Rules really should be redone into the rules for Usage Limits Count and the rules for Usage Limits Total and Usage Limits Units - or something along those lines.
The set of descriptions there are really indicating that the structure usage there is getting in the way of the handling as it is really three separate attributes rather than one structure - at least in terms of how it is handled.


On Fri, Nov 9, 2018 at 4:46 PM Mark Joseph <mark@p6r.com> wrote:

Looking at section 4.51 Usage Limits it contains details about how Add Attribute or Modify Attribute operations SHALL NOT set or modify the Usage Limit Count.
So what about the Set Attribute operation?


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]