Re: Problems with sequenceNumber
<kirpal_khalsa <at> ccmail.com>
1995-02-06 17:41:25 GMT
Has anyone replied yet? Here's my take.
Replies thusly: KSK>>
Lotus Development Corp.
______________________________ Reply Separator _________________________________
Subject: Problems with sequenceNumber
Author: Neil Cook <n.cook <at> nexor.co.uk> at internet-mail
Date: 1/31/95 2:01 AM
I sent a message to this list a few months ago listing a few problems
with the 0.6 data format specification. Some of them have been fixed
in the new 0.14 spec. However, sequenceNumber is still a
PrintableString with the separator ";" (semicolon). This character is
(still) not allowed in PrintableString, thus we suggest again that the
separator be changed to a : (colon). Has nobody else tried decoding
such a file to discover this problem?
KSK>> No reason not to change this that I can think of.
Also, if you try to load this into a 93 directory, there are access
control issues to worry about. If there is no aci information, then
nobody will be able to read the data. Will the attribute information contain
a relevant access point and related attributes, will the subtree
contain the relevant aci subentries?
KSK>> Security's always been a big hole since day one, primarily because we
decided not to address it for round1 of the spec. It seems highly unreasonable