[x500standard] Re: SV: Re: bindingType of ModifyOperationalBindingArgument
- From: "Jean-Paul LEMAIRE" <jean-paul.lemaire@xxxxxxxxxxxxxxxxxxxxx>
- To: x500standard@xxxxxxxxxxxxx
- Date: Fri, 02 Dec 2011 17:39:52 +0100
Hi Erik,
I agree that the text is not clear and a defect is needed about that.
As binding version can be changed (for example when shadowing options
are changed), bindingID shall be unique for a couple of DSAs to
prevent clashes after modification of the version of an existing
agreement.
I also suggest to have a unique bindindID per couple of DSAs
disregarding the type of binding. And the
modificationOperationalBinding and terminateOperationalBinding have to
rejected if the bindingType is not the same as for
establishOperationalBinding.
Best regards
Jean-Paul.
On Fri, 2 Dec 2011 17:18:26 +0100
"Erik Andersen" <era@xxxxxxx> wrote:
Hi Jean-Paul,
The question is whether the BindingID shall be unique among all
instances of
operational bindings between two DSA or whether it is sufficient
that it
unique within a particular operational binding type. In the latter
case,
both the type and the id is necessary for determining the particular
instance.
Another question is whether it is the identifier component of
OperationalBinding that shall be unique rather than the combination
of
identifier and version.
It is not clear from the current text.
Erik Andersen
Andersen's L-Service
Elsevej 48,
DK-3500 Vaerloese
Denmark
Mobile: +45 2097 1490
e-amail: era@xxxxxxx
Skype: andersen-erik
http://www.x500.eu/
http://www.x500standard.com/
http://dk.linkedin.com/in/andersenerik
-----Oprindelig meddelelse-----
Fra: x500standard-bounce@xxxxxxxxxxxxx
[mailto:x500standard-bounce@xxxxxxxxxxxxx] På vegne af Jean-Paul
LEMAIRE
Sendt: 30. november 2011 18:53
Til: x500standard@xxxxxxxxxxxxx
Emne: [x500standard] Re: bindingType of
ModifyOperationalBindingArgument
Hi Erik,
The modifyOperationalBinding can modify the parameters of the
binding but
not the binding type. The binding type shall be present in the
sequence
because the parameters depend on it (with a constraint between
components).
It seems that a DSA should reject a modification on existing bindind
with a
different bindingType as the bindingType used in
establishOperationalBinding. A similar rule should applied to
terminateOperationalBinding.
Regards
Jean-Paul.
Am I right when assuming that the bindingType cannot be changed by
the ModifyOperationalArgument?
If I am right, the bindingType shall the one that is associated with
the bindingID. That should be stated clearly.
I am waiting eagerly for an expert answer.
Erik Andersen
Andersen's L-Service
Elsevej 48,
DK-3500 Vaerloese
Denmark
Mobile: +45 2097 1490
e-amail: era@xxxxxxx
Skype: andersen-erik
http://www.x500.eu/
http://www.x500standard.com/
<http://dk.linkedin.com/in/andersenerik>
http://dk.linkedin.com/in/andersenerik
-----
www.x500standard.com: The central source for information on the
X.500
Directory Standard.
-----
www.x500standard.com: The central source for information on the
X.500 Directory Standard.
-----
www.x500standard.com: The central source for information on the X.500 Directory
Standard.
Other related posts:
