Latest Thales Interop report

From
Jim Flood <>
Date
2012-08-16T14:12:00+00:00
ID
Thread
Latest Thales Interop report
I have also interpreted the answer to be yes, that Locate of any
attribute of the template will find the template regardless of
whether or not the attribute applies to the template object itself,
or to objects created by the template.
Although there is this in section 2.2.6,  None of the
client-settable attributes specified in a Template except the Name
attribute apply to the template object itself, but instead apply to
any object created using the Template,  there is nothing written
about Locate that differentiates. It may be useful to search for
templates by any attribute, and so language could be added to the
Locate operation 4.9 to make the answer explicitly  yes .
For Get on a template, I understand it to return attributes of the
template that are applied to objects created by the template. This
may be what was passed in on the Register, but I don't think it
should be explicitly tied by definition to the Register operation.
Regards,
Jim Flood
On 8/16/2012 6:53 AM, Mathias
Bjoerkqvist1 wrote:
I have interpreted the answer to
be
yes.
I couldn't find any text in the
Locate
section of the spec where we differentiate between attributes
that apply
to the managed object and attributes that apply to managed
objects created
using the managed object (template). Having Locate on template
objects
apply to only the attributes that apply to the template itself
seems to
be of limited value.
Regards,
Mathias
From:
Tim Hudson
<>
To:

<>
Cc:
Karadigudda, Mahadev
<>
Date:
16.08.2012 13:06
Subject:
Re: [kmip-interop-tech]
Draft combined
summary report
Sent
by:
<>
On 16/08/2012 8:53 PM, John Leiseboer wrote:
Strictly, perhaps, the answer should be no, but
maybe
templates are a special case where we should say, yes.
Actually I think the specification is very clear on this -
LOCATE is related
to  attributes  of the managed object - so I don't see
where there
is an avenue to argue that the answer is anything other than no.
If you
can see wriggle room in the text in LOCATE it would be good to
outline
that logic - but that would have to be about LOCATE itself and
not in the
various sections of the specification referring to templates.
What GET on a template returns is underspecified - I still think
it is
clear - in that it should return the template structure exactly
as it was
provided in the REGISTER request and that other interpretations
are stretching
interpretation - however some of the text hints at possible
other interpretations.
We clearly need to document this area (templates) better and to
include
some additional test cases aimed at outlining what is expected
to reduce
the interoperability challenges in the short term.
Tim.