Subject: Re: Problems with sequenceNumber
From: [email-masked]
To: [email-masked], Neil Cook <[email-masked]>
Cc: [email-masked], [email-masked], [email-masked]
Date: Mon, 06 Feb 95 17:41:25 pst

Hi Neil,
     
     Has anyone replied yet? Here's my take.
     Replies thusly: KSK>>
     
     Regards,
         Kirpal Khalsa
         Lotus Development Corp.

______________________________ Reply Separator _________________________________
Subject: Problems with sequenceNumber
Author:  Neil Cook <[email-masked]> 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 
to require a proprietary email system to adopt X500 access control when 
exporting directory info. The context prefix was meant to sort of point at an 
access point/subentry but I don't think we ever got around to really working out
the details of how to identify an exporter. There's some wording in the text 
indicating that we didn't plan to handle access control specifics also. 
     
Also I notice a context prefix attribute has been included. We have 
been using an agreement file in parallel with the xapia file, in order 
to have enough information to be able to load the data into a 
directory. Assuming this does not exist, is the dir sync info presumed 
to be loaded directly under the context prefix? 
KSK>> Yep, meant to be loaded right under there.
If not, then where does this information come from?
     
Neil.

Date: Wed, 1 Feb 1995 12:26:39 -0500
From: Ray Freiwirth <[email-masked]>
To: [email-masked]
Subject: Please subscribe

Please subscribe [email-masked]

Please unsubscribe [email-masked]

thanks, ray

From: "Bor, Alexis" <[email-masked]>
To: 'xapia-dirsynch' <[email-masked]>
Subject: Soft Copy of Dir Sync Spec On-Line
Date: Wed, 01 Feb 95 08:37:00 PST
Encoding: 20 TEXT

Draft 0.12 of the Directory Synchronization Specification has been posted   
on nemo.ncsl.nist.gov in the directory oiw/dssig/xapia

I plan to make this available for comments to the EMA Directory Committee   
next week in San Diego.

The files are:

final012.doc -  Word for Windows 6.0
final012.ww2 -  Word for Windows 2.0
final012.rtf -  RTF format

If you need a different format, just send me mail and I will do my best   
to get you a readable copy.

Alexis Bor
Chair
XAPIA Directory Synchronization Technical SubCommittee
[email-masked]