From owner-ietf-ldup@imc.org  Wed Nov  3 20:37:07 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05333
	for <ldup-archive@odin.ietf.org>; Wed, 3 Nov 1999 20:37:00 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id RAA18554
	for ietf-ldup-bks; Wed, 3 Nov 1999 17:04:34 -0800 (PST)
Received: from mail.zj.js.cn ([202.102.4.144])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id RAA18539;
	Wed, 3 Nov 1999 17:04:09 -0800 (PST)
Received: from pub.zj.jsinfo.net ([210.77.40.3]) by
          mail.zj.js.cn (Netscape Messaging Server 4.05) with SMTP id
          FKNERE06.90F; Thu, 4 Nov 1999 08:59:38 +0800 
From: service@huali-cn.com (华立服务速递)
Reply-to: service@huali-cn.com (华立服务速递)
To: service@huali-cn.com (商业客户)
Subject: 华立服务
X-Mailer: Spring Sun Immensity Perl SendMail Version 1.00
X-URL: http://www.liyangman.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="-SpringSun-attach-boundary-941677468---"
Date: Thu, 4 Nov 1999 08:59:38 +0800
Message-ID: <FKNERE06.90F@mail.zj.js.cn>
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

---SpringSun-attach-boundary-941677468---
Content-type: text/plain

欢迎使用  五邑五线
============================
http://www.wyol.huali-cn.com
============================
   五邑在线是广东省江门五邑侨乡地区的一个商业性
搜索引擎，收录了江门五邑地区的几百家商业企业网站，
并有众多的商业合作项目、商业快讯，是您事业成功的
第一步！

   把握机遇、再创辉煌！

欢迎使用  五邑五线
============================
http://www.wyol.huali-cn.com
============================



感谢您订阅《华立服务》，您可以点击以下地址订阅或退订《华立服务》
http://www.shangshang.com/cgi-bin/emailer.pl?do=suborunsub&user=huali






本邮件采用无限邮件列表发送，但所有言论不代表溧阳人信息网任何观点
================================================================
 欢迎使用溧阳人信息网（溧阳无限网络工作室）开发的网络五虎将系统
                  http://www.liyangman.com/
----------------------------------------------------------------
免费邮件列表、邮件使者、文件传送专家、网站镜像专家、网站上传专家

---SpringSun-attach-boundary-941677468-----


From owner-ietf-ldup@imc.org  Tue Nov  9 17:26:22 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28173
	for <ldup-archive@odin.ietf.org>; Tue, 9 Nov 1999 17:26:21 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id NAA22818
	for ietf-ldup-bks; Tue, 9 Nov 1999 13:48:03 -0800 (PST)
Received: from highroad.ds.ietf.innovationslab.net (IDENT:root@highroad.noc.ietf.innovationslab.net [130.128.8.8])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id NAA22814
	for <ietf-ldup@imc.org>; Tue, 9 Nov 1999 13:48:01 -0800 (PST)
From: max@milian.de
Received: from milian.de (d1-3.dt.ietf.innovationslab.net [130.128.34.13])
	by highroad.ds.ietf.innovationslab.net (8.9.3/8.9.3) with ESMTP id QAA01802;
	Tue, 9 Nov 1999 16:55:17 -0500
Message-ID: <38287B6D.CADAB4EB@milian.de>
Date: Tue, 09 Nov 1999 14:52:14 -0500
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-ldup@imc.org
Subject: LDUP Eng Team Meeting
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

WED    11/10/1999    1 PM - 3 PM

Cabinet Room; West Conference Center

Meeting notice will be posted on the IETF Message Board.

Chris.



From owner-ietf-ldup@imc.org  Thu Nov 11 15:32:50 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17698
	for <ldup-archive@odin.ietf.org>; Thu, 11 Nov 1999 15:32:36 -0500 (EST)
Received: (from majordomo@localhost)
	by ns.secondary.com (8.9.3/8.9.3) id LAA01065
	for ietf-ldup-bks; Thu, 11 Nov 1999 11:31:50 -0800 (PST)
Received: from mail.oncalldba.com (reed.oncalldba.com [166.70.104.61])
	by ns.secondary.com (8.9.3/8.9.3) with SMTP id LAA01060
	for <ietf-ldup@imc.org>; Thu, 11 Nov 1999 11:31:48 -0800 (PST)
Received: from RMINC_DOM-Message_Server by mail.oncalldba.com
	with Novell_GroupWise; Thu, 11 Nov 1999 12:22:16 -0700
Message-Id: <s82ab4f8.004@mail.oncalldba.com>
X-Mailer: Novell GroupWise 5.5
Date: Thu, 11 Nov 1999 08:52:37 -0700
From: "Ed Reed" <eer@OnCallDBA.COM>
To: <stokes@austin.ibm.com>, <ggood@netscape.com>
Cc: <ietf-ldup@imc.org>
Subject: replica id lookup table words
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=_144D0A78.CFAEC2A8"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_144D0A78.CFAEC2A8
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

 Gordon - here are the words I'd put into the Info Model draft describing =
the ReplicaIDLookupTable, which
we decided in Washington to document in the protocol spec, instead.  Use =
any or none of these words that make sense to you to use.

Ed

1.1.1     ReplicaIDLookupTable
In order to reduce the amount of redundant data associated with the string =
representation of replicaIDs in the ldapChangeSequenceNumber data =
structure (see below), a lookup table MUST be provided by the supplier of =
CSNs, mapping a numeric value to each Replica whose identity is to be used =
in a CSN.
ReplicaIDLookupTable =3D length "#" replicaTuple *
length =3D INTEGER
replicaTuple =3D "(" replicaNumber "#" replicaRDN ")"
replicaNumber =3D INTEGER
An explicit pairing of replicaNumber with replicaRDN is used so that a =
specific ordering is not required. =20
An explicit length, or number of replicaTuples to be sent, is used as a =
convenience to the consumer, or receiver, of subsequent CSNs, and as an =
indicator of an empty list.=20
All instances of replicaNumber MUST be fixed length, having the same =
number of digits, with leading zeros, using base 10 numbering.  If, for =
instance, the length of the replicaLookupTable is 9 entries, a single =
digit would suffice for each replicaNumber.  On the other hand, if the =
length of the repliaLookupTable is 11 entries, then ALL replicaNumbers in =
the table MUST be exactly two digits long, with the left most digit being =
"0" for all of the entries whose replicaNumbers are less than 10.  This =
kludge is so no special syntax matching rules need be supported in =
servers.
Each ReplicaTuple begins with an open parenthisis character "(", and ends =
with a close parenthisis character ")".
There may be zero or more replicaTuples in the lookup table.  An empty =
lookup table, with a length of zero and no replicaTuples, MUST be =
interpreted to mean that the RDN of the replica (left justified, fixed =
length with spaces padding to the right before the sharp "#" field =
separator) is used in lieu of an integer in the ldapChangeSequenceNumber =
(CSN) values that follow.

--=_144D0A78.CFAEC2A8
Content-Type: text/plain
Content-Disposition: attachment; filename="TEXT.htm"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.2614.3500" name=GENERATOR></HEAD>
<BODY bgColor=#ffffff 
style="FONT: 10pt Arial; MARGIN-LEFT: 2px; MARGIN-TOP: 2px">
<DIV>&nbsp;Gordon - here are the words I'd put into the Info Model draft 
describing the ReplicaIDLookupTable, which</DIV>
<DIV>we decided in Washington to document in the protocol spec, instead.&nbsp; 
Use any or none of these words that make sense to you to use.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Ed</DIV>
<DIV>&nbsp;</DIV>
<DIV><A name=_Toc465163586><SPAN style="FONT-FAMILY: 'Courier New'">1.1.1<SPAN 
style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN><SPAN 
style="FONT-FAMILY: 'Courier New'">ReplicaIDLookupTable</SPAN></A><SPAN 
style="FONT-FAMILY: 'Courier New'"><?xml:namespace prefix = o ns = 
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></DIV>
<P class=MsoBodyText><SPAN style="mso-bidi-font-family: 'Courier New'">In order 
to reduce the amount of redundant data associated with the string representation 
of replicaIDs in the ldapChangeSequenceNumber data structure (see below), a 
lookup table MUST be provided by the supplier of CSNs, mapping a numeric value 
to each Replica whose identity is to be used in a CSN.<o:p></o:p></SPAN></P>
<P class=MsoBodyText><SPAN 
style="mso-bidi-font-family: 'Courier New'">ReplicaIDLookupTable = length "#" 
replicaTuple *<o:p></o:p></SPAN></P>
<P class=MsoBodyText><SPAN style="mso-bidi-font-family: 'Courier New'">length = 
INTEGER<o:p></o:p></SPAN></P>
<P class=MsoBodyText><SPAN 
style="mso-bidi-font-family: 'Courier New'">replicaTuple = "(" replicaNumber "#" 
replicaRDN ")"<o:p></o:p></SPAN></P>
<P class=MsoBodyText><SPAN 
style="mso-bidi-font-family: 'Courier New'">replicaNumber = 
INTEGER<o:p></o:p></SPAN></P>
<P class=MsoBodyText><SPAN style="mso-bidi-font-family: 'Courier New'">An 
explicit pairing of replicaNumber with replicaRDN is used so that a specific 
ordering is not required.<SPAN style="mso-spacerun: yes">&nbsp; 
</SPAN><o:p></o:p></SPAN></P>
<P class=MsoBodyText><SPAN style="mso-bidi-font-family: 'Courier New'">An 
explicit length, or number of replicaTuples to be sent, is used as a convenience 
to the consumer, or receiver, of subsequent CSNs, and as an indicator of an 
empty list. <o:p></o:p></SPAN></P>
<P class=MsoBodyText><SPAN style="mso-bidi-font-family: 'Courier New'">All 
instances of replicaNumber MUST be fixed length, having the same number of 
digits, with leading zeros, using base 10 numbering.<SPAN 
style="mso-spacerun: yes">&nbsp; </SPAN>If, for instance, the length of the 
replicaLookupTable is 9 entries, a single digit would suffice for each 
replicaNumber.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>On the other hand, 
if the length of the repliaLookupTable is 11 entries, then ALL replicaNumbers in 
the table MUST be exactly two digits long, with the left most digit being "0" 
for all of the entries whose replicaNumbers are less than 10.<SPAN 
style="mso-spacerun: yes">&nbsp; </SPAN>This kludge is so no special syntax 
matching rules need be supported in servers.<o:p></o:p></SPAN></P>
<P class=MsoBodyText><SPAN style="mso-bidi-font-family: 'Courier New'">Each 
ReplicaTuple begins with an open parenthisis character "(", and ends with a 
close parenthisis character ")".<o:p></o:p></SPAN></P>
<P class=MsoBodyText><SPAN style="mso-bidi-font-family: 'Courier New'">There may 
be zero or more replicaTuples in the lookup table.<SPAN 
style="mso-spacerun: yes">&nbsp; </SPAN>An empty lookup table, with a length of 
zero and no replicaTuples, MUST be interpreted to mean that the RDN of the 
replica (left justified, fixed length with spaces padding to the right before 
the sharp "#" field separator) is used in lieu of an integer in the 
ldapChangeSequenceNumber (CSN) values that 
follow.<o:p></o:p></SPAN></P></BODY></HTML>

--=_144D0A78.CFAEC2A8--


From owner-ietf-ldup@imc.org  Mon Nov 15 11:59:54 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05010
	for <ldup-archive@odin.ietf.org>; Mon, 15 Nov 1999 11:59:50 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id IAA17262
	for ietf-ldup-bks; Mon, 15 Nov 1999 08:18:04 -0800 (PST)
Received: from mailgate.rdg.opengroup.org (mailgate.rdg.opengroup.org [192.153.166.4])
	by ns.secondary.com (8.9.3/8.9.3) with SMTP id IAA17255
	for <ietf-ldup@imc.org>; Mon, 15 Nov 1999 08:18:02 -0800 (PST)
Received: by mailgate.rdg.opengroup.org; id AA26635; Mon, 15 Nov 1999 16:23:45 GMT
Received: from slip139-92-195-252.war.uk.ibm.net [139.92.195.252] by mailgate.rdg.opengroup.org via smtpd  V1.32 (99/03/30 12:28:06) for <ietf-ldup@imc.org> ; Mon Nov 15 16:23 GMT 1999
Message-Id: <3.0.3.32.19991115161413.006c6d30@mailhome.rdg.opengroup.org>
X-Sender: cjh@mailhome.rdg.opengroup.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Mon, 15 Nov 1999 16:14:13 +0000
To: ietf-ldup@imc.org
From: Chris Harding <c.harding@opengroup.org>
Subject: UUID Ref.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

Hi -

As promised in Friday's meeting, here is the reference to the UUID
specification.

The document concerned is Open Group Document C706 - DCE 1.1: Remote
Procedure Call. This is freely available over the web. To get into the
whole document via its TOC, go to
http://www.opengroup.org/publications/catalog/c706.htm   Appendix A is at
http://www.opengroup.org/onlinepubs/009629399/apdxa.htm - in the current
version, this appears to be a specification of the UUID format rather than
a sample implementation description.



Regards,

Chris
+++++

-------------------------------------------------------------------------
           Chris Harding
  T H E    Development Manager
 O P E N   Apex Plaza, Forbury Road, Reading RG1 1AX, UK
G R O U P  Mailto:c.harding@opengroup.org   Ph: +44 118 950 8311 x2262
           WWW: http://www.opengroup.org    Fx: +44 118 950 0110  

OSF/1, Motif, UNIX and the "X" device are registered trademarks in
the US and other countries, and IT DialTone and The Open Group are
trademarks of The Open Group.
-------------------------------------------------------------------------


From owner-ietf-ldup@imc.org  Mon Nov 15 12:52:35 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01494
	for <ldup-archive@odin.ietf.org>; Mon, 15 Nov 1999 12:52:34 -0500 (EST)
Received: (from majordomo@localhost)
	by ns.secondary.com (8.9.3/8.9.3) id JAA18204
	for ietf-ldup-bks; Mon, 15 Nov 1999 09:15:47 -0800 (PST)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA18200
	for <ietf-ldup@imc.org>; Mon, 15 Nov 1999 09:15:46 -0800 (PST)
Received: by dfssl with Internet Mail Service (5.5.2650.21)
	id <W8XXKR49>; Mon, 15 Nov 1999 09:15:58 -0800
Message-ID: <19398D273324D3118A2B0008C7E9A569051BEA88@SIT.platinum.corp.microsoft.com>
From: "Paul Leach (Exchange)" <paulle@Exchange.MICROSOFT.com>
To: "'Chris Harding'" <c.harding@opengroup.org>, ietf-ldup@imc.org
Subject: RE: UUID Ref.
Date: Mon, 15 Nov 1999 09:15:51 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BF2F8D.14EAF560"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BF2F8D.14EAF560
Content-Type: text/plain

The DCE RPC spec, and hence the UUID specification, was later incoroporated
into an ISO RPC standard. Do you have a citation for that?

> -----Original Message-----
> From: Chris Harding [mailto:c.harding@opengroup.org]
> Sent: Monday, November 15, 1999 8:14 AM
> To: ietf-ldup@imc.org
> Subject: UUID Ref.
> 
> 
> Hi -
> 
> As promised in Friday's meeting, here is the reference to the UUID
> specification.
> 
> The document concerned is Open Group Document C706 - DCE 1.1: Remote
> Procedure Call. This is freely available over the web. To get into the
> whole document via its TOC, go to
> http://www.opengroup.org/publications/catalog/c706.htm   
> Appendix A is at
> http://www.opengroup.org/onlinepubs/009629399/apdxa.htm - in 
> the current
> version, this appears to be a specification of the UUID 
> format rather than
> a sample implementation description.
> 
> 
> 
> Regards,
> 
> Chris
> +++++
> 
> --------------------------------------------------------------
> -----------
>            Chris Harding
>   T H E    Development Manager
>  O P E N   Apex Plaza, Forbury Road, Reading RG1 1AX, UK
> G R O U P  Mailto:c.harding@opengroup.org   Ph: +44 118 950 8311 x2262
>            WWW: http://www.opengroup.org    Fx: +44 118 950 0110  
> 
> OSF/1, Motif, UNIX and the "X" device are registered trademarks in
> the US and other countries, and IT DialTone and The Open Group are
> trademarks of The Open Group.
> --------------------------------------------------------------
> -----------
> 

------_=_NextPart_001_01BF2F8D.14EAF560
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: UUID Ref.</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>The DCE RPC spec, and hence the UUID specification, =
was later incoroporated into an ISO RPC standard. Do you have a =
citation for that?</FONT></P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Chris Harding [<A =
HREF=3D"mailto:c.harding@opengroup.org">mailto:c.harding@opengroup.org</=
A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Monday, November 15, 1999 8:14 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: ietf-ldup@imc.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: UUID Ref.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi -</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; As promised in Friday's meeting, here is the =
reference to the UUID</FONT>
<BR><FONT SIZE=3D2>&gt; specification.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The document concerned is Open Group Document =
C706 - DCE 1.1: Remote</FONT>
<BR><FONT SIZE=3D2>&gt; Procedure Call. This is freely available over =
the web. To get into the</FONT>
<BR><FONT SIZE=3D2>&gt; whole document via its TOC, go to</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.opengroup.org/publications/catalog/c706.htm" =
TARGET=3D"_blank">http://www.opengroup.org/publications/catalog/c706.htm=
</A>&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; Appendix A is at</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.opengroup.org/onlinepubs/009629399/apdxa.htm" =
TARGET=3D"_blank">http://www.opengroup.org/onlinepubs/009629399/apdxa.ht=
m</A> - in </FONT>
<BR><FONT SIZE=3D2>&gt; the current</FONT>
<BR><FONT SIZE=3D2>&gt; version, this appears to be a specification of =
the UUID </FONT>
<BR><FONT SIZE=3D2>&gt; format rather than</FONT>
<BR><FONT SIZE=3D2>&gt; a sample implementation description.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Regards,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Chris</FONT>
<BR><FONT SIZE=3D2>&gt; +++++</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
--------------------------------------------------------------</FONT>
<BR><FONT SIZE=3D2>&gt; -----------</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; Chris Harding</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; T H E&nbsp;&nbsp;&nbsp; Development =
Manager</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; O P E N&nbsp;&nbsp; Apex Plaza, Forbury =
Road, Reading RG1 1AX, UK</FONT>
<BR><FONT SIZE=3D2>&gt; G R O U P&nbsp; <A =
HREF=3D"Mailto:c.harding@opengroup.org">Mailto:c.harding@opengroup.org</=
A>&nbsp;&nbsp; Ph: +44 118 950 8311 x2262</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; WWW: <A HREF=3D"http://www.opengroup.org" =
TARGET=3D"_blank">http://www.opengroup.org</A>&nbsp;&nbsp;&nbsp; Fx: =
+44 118 950 0110&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; OSF/1, Motif, UNIX and the &quot;X&quot; device =
are registered trademarks in</FONT>
<BR><FONT SIZE=3D2>&gt; the US and other countries, and IT DialTone and =
The Open Group are</FONT>
<BR><FONT SIZE=3D2>&gt; trademarks of The Open Group.</FONT>
<BR><FONT SIZE=3D2>&gt; =
--------------------------------------------------------------</FONT>
<BR><FONT SIZE=3D2>&gt; -----------</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BF2F8D.14EAF560--


From owner-ietf-ldup@imc.org  Mon Nov 15 14:54:57 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04089
	for <ldup-archive@odin.ietf.org>; Mon, 15 Nov 1999 14:54:56 -0500 (EST)
Received: (from majordomo@localhost)
	by ns.secondary.com (8.9.3/8.9.3) id LAA19408
	for ietf-ldup-bks; Mon, 15 Nov 1999 11:12:02 -0800 (PST)
Received: from mailgate.rdg.opengroup.org (mailgate.rdg.opengroup.org [192.153.166.4])
	by ns.secondary.com (8.9.3/8.9.3) with SMTP id LAA19399
	for <ietf-ldup@imc.org>; Mon, 15 Nov 1999 11:11:59 -0800 (PST)
Received: by mailgate.rdg.opengroup.org; id AA26038; Mon, 15 Nov 1999 19:17:41 GMT
Received: from slip139-92-25-84.wak.uk.ibm.net [139.92.25.84] by mailgate.rdg.opengroup.org via smtpd  V1.32 (99/03/30 12:28:06) for <d.may@opengroup.org> ; Mon Nov 15 19:17 GMT 1999
Message-Id: <3.0.3.32.19991115191112.006c4994@mailhome.rdg.opengroup.org>
X-Sender: cjh@mailhome.rdg.opengroup.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Mon, 15 Nov 1999 19:11:12 +0000
To: "Paul Leach (Exchange)" <paulle@Exchange.MICROSOFT.com>, ietf-ldup@imc.org
From: Chris Harding <c.harding@opengroup.org>
Subject: RE: UUID Ref.
Cc: d.may@opengroup.org
In-Reply-To: <19398D273324D3118A2B0008C7E9A569051BEA88@SIT.platinum.corp
 .microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

Hi -

Deborah May writes:

>>>>
Just one comment to add to Chris' response - the draft you are
referring to is on the web at:
www.opengroup.org/dce/info/draft-leach-uuids-guids-01.txt
It did expire, however this page points you to two references for
UUID/GUID definitions, one of which is the DCE RPC Specification
Chris provided a pointer to.


<<<<

The second reference on that page is to:

                ISO/IEC 11578:1996
                Information technology --
                Open Systems Interconnection -- Remote Procedure Call
                http://www.iso.ch/cate/d2229.html 

which I think answers Paul's question.

Thanks, Deborah!

>>>>

The DCE RPC spec, and hence the UUID specification, was later incoroporated
into an ISO RPC standard. Do you have a citation for that?

> -----Original Message----- 
> From: Chris Harding
[<mailto:c.harding@opengroup.org>mailto:c.harding@opengroup.org] 
> Sent: Monday, November 15, 1999 8:14 AM 
> To: ietf-ldup@imc.org 
> Subject: UUID Ref. 
>  
>  
> Hi - 
>  
> As promised in Friday's meeting, here is the reference to the UUID 
> specification. 
>  
> The document concerned is Open Group Document C706 - DCE 1.1: Remote 
> Procedure Call. This is freely available over the web. To get into the 
> whole document via its TOC, go to 
>
<http://www.opengroup.org/publications/catalog/c706.htm>http://www.opengroup
.org/publications/catalog/c706.htm    
> Appendix A is at 
>
<http://www.opengroup.org/onlinepubs/009629399/apdxa.htm>http://www.opengrou
p.org/onlinepubs/009629399/apdxa.htm - in  
> the current 
> version, this appears to be a specification of the UUID  
> format rather than 
> a sample implementation description. 
>  
>  
>  
> Regards, 
>  
> Chris 
> +++++ 
>  
> -------------------------------------------------------------- 
> ----------- 
>            Chris Harding 
>   T H E    Development Manager 
>  O P E N   Apex Plaza, Forbury Road, Reading RG1 1AX, UK 
> G R O U P  <Mailto:c.harding@opengroup.org>Mailto:c.harding@opengroup.org
  Ph: +44 118 950 8311 x2262 
>            WWW: <http://www.opengroup.org>http://www.opengroup.org    Fx:
+44 118 950 0110   
>  
> OSF/1, Motif, UNIX and the "X" device are registered trademarks in 
> the US and other countries, and IT DialTone and The Open Group are 
> trademarks of The Open Group. 
> -------------------------------------------------------------- 
> ----------- 
>  

<<<<



Regards,

Chris
+++++

-------------------------------------------------------------------------
           Chris Harding
  T H E    Development Manager
 O P E N   Apex Plaza, Forbury Road, Reading RG1 1AX, UK
G R O U P  Mailto:c.harding@opengroup.org   Ph: +44 118 950 8311 x2262
           WWW: http://www.opengroup.org    Fx: +44 118 950 0110  

OSF/1, Motif, UNIX and the "X" device are registered trademarks in
the US and other countries, and IT DialTone and The Open Group are
trademarks of The Open Group.
-------------------------------------------------------------------------


From owner-ietf-ldup@imc.org  Mon Nov 15 15:47:52 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00053
	for <ldup-archive@odin.ietf.org>; Mon, 15 Nov 1999 15:47:48 -0500 (EST)
Received: (from majordomo@localhost)
	by ns.secondary.com (8.9.3/8.9.3) id LAA19876
	for ietf-ldup-bks; Mon, 15 Nov 1999 11:50:08 -0800 (PST)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id LAA19872
	for <ietf-ldup@imc.org>; Mon, 15 Nov 1999 11:50:07 -0800 (PST)
Received: by dfssl with Internet Mail Service (5.5.2650.21)
	id <W8XXKYCF>; Mon, 15 Nov 1999 11:50:33 -0800
Message-ID: <19398D273324D3118A2B0008C7E9A569051BEA94@SIT.platinum.corp.microsoft.com>
From: "Paul Leach (Exchange)" <paulle@Exchange.MICROSOFT.com>
To: "'Chris Harding'" <c.harding@opengroup.org>,
        "Paul Leach (Exchange)"
	 <paulle@Exchange.MICROSOFT.com>,
        ietf-ldup@imc.org
Cc: d.may@opengroup.org
Subject: RE: UUID Ref.
Date: Mon, 15 Nov 1999 11:50:27 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BF2FA2.AD78DD50"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BF2FA2.AD78DD50
Content-Type: text/plain

The draft to which you refer was written by Rich Salz (formerly of the
OSF/OpenGroup) and me.

It included a sample implementation, and some detailed implementation
requirements, which may permit more implementation flexibility than the
DCE/ISO spec (which was very procedural).

It also added code points for UUIDs created from psuedo-random number
generators (including hash functions over string constants). The additional
code points had OSF approval (via Rich), but when the reality of the
existence of the ISO standard hit home, we realized that IETF didn't have
change control. So the spec has sat in limbo. Post-Win2000 ship, I'm
thinking I could re-release the spec as informational if there is demand for
it, as I believe the sample implementation has value, as does the expanded
implementation requirements section.

> -----Original Message-----
> From: Chris Harding [mailto:c.harding@opengroup.org]
> Sent: Monday, November 15, 1999 11:11 AM
> To: Paul Leach (Exchange); ietf-ldup@imc.org
> Cc: d.may@opengroup.org
> Subject: RE: UUID Ref.
> 
> 
> Hi -
> 
> Deborah May writes:
> 
> >>>>
> Just one comment to add to Chris' response - the draft you are
> referring to is on the web at:
> www.opengroup.org/dce/info/draft-leach-uuids-guids-01.txt
> It did expire, however this page points you to two references for
> UUID/GUID definitions, one of which is the DCE RPC Specification
> Chris provided a pointer to.
> 
> 
> <<<<
> 
> The second reference on that page is to:
> 
>                 ISO/IEC 11578:1996
>                 Information technology --
>                 Open Systems Interconnection -- Remote Procedure Call
>                 http://www.iso.ch/cate/d2229.html 
> 
> which I think answers Paul's question.
> 
> Thanks, Deborah!
> 
> >>>>
> 
> The DCE RPC spec, and hence the UUID specification, was later 
> incoroporated
> into an ISO RPC standard. Do you have a citation for that?
> 
> > -----Original Message----- 
> > From: Chris Harding
> [<mailto:c.harding@opengroup.org>mailto:c.harding@opengroup.org] 
> > Sent: Monday, November 15, 1999 8:14 AM 
> > To: ietf-ldup@imc.org 
> > Subject: UUID Ref. 
> >  
> >  
> > Hi - 
> >  
> > As promised in Friday's meeting, here is the reference to the UUID 
> > specification. 
> >  
> > The document concerned is Open Group Document C706 - DCE 
> 1.1: Remote 
> > Procedure Call. This is freely available over the web. To 
> get into the 
> > whole document via its TOC, go to 
> >
> <http://www.opengroup.org/publications/catalog/c706.htm>http:/
> /www.opengroup
> .org/publications/catalog/c706.htm    
> > Appendix A is at 
> >
> <http://www.opengroup.org/onlinepubs/009629399/apdxa.htm>http:
> //www.opengrou
> p.org/onlinepubs/009629399/apdxa.htm - in  
> > the current 
> > version, this appears to be a specification of the UUID  
> > format rather than 
> > a sample implementation description. 
> >  
> >  
> >  
> > Regards, 
> >  
> > Chris 
> > +++++ 
> >  
> > -------------------------------------------------------------- 
> > ----------- 
> >            Chris Harding 
> >   T H E    Development Manager 
> >  O P E N   Apex Plaza, Forbury Road, Reading RG1 1AX, UK 
> > G R O U P  
> <Mailto:c.harding@opengroup.org>Mailto:c.harding@opengroup.org
>   Ph: +44 118 950 8311 x2262 
> >            WWW: 
> <http://www.opengroup.org>http://www.opengroup.org    Fx:
> +44 118 950 0110   
> >  
> > OSF/1, Motif, UNIX and the "X" device are registered trademarks in 
> > the US and other countries, and IT DialTone and The Open Group are 
> > trademarks of The Open Group. 
> > -------------------------------------------------------------- 
> > ----------- 
> >  
> 
> <<<<
> 
> 
> 
> Regards,
> 
> Chris
> +++++
> 
> --------------------------------------------------------------
> -----------
>            Chris Harding
>   T H E    Development Manager
>  O P E N   Apex Plaza, Forbury Road, Reading RG1 1AX, UK
> G R O U P  Mailto:c.harding@opengroup.org   Ph: +44 118 950 8311 x2262
>            WWW: http://www.opengroup.org    Fx: +44 118 950 0110  
> 
> OSF/1, Motif, UNIX and the "X" device are registered trademarks in
> the US and other countries, and IT DialTone and The Open Group are
> trademarks of The Open Group.
> --------------------------------------------------------------
> -----------
> 

------_=_NextPart_001_01BF2FA2.AD78DD50
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: UUID Ref.</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>The draft to which you refer was written by Rich Salz =
(formerly of the OSF/OpenGroup) and me.</FONT>
</P>

<P><FONT SIZE=3D2>It included a sample implementation, and some =
detailed implementation requirements, which may permit more =
implementation flexibility than the DCE/ISO spec (which was very =
procedural).</FONT></P>

<P><FONT SIZE=3D2>It also added code points for UUIDs created from =
psuedo-random number generators (including hash functions over string =
constants). The additional code points had OSF approval (via Rich), but =
when the reality of the existence of the ISO standard hit home, we =
realized that IETF didn't have change control. So the spec has sat in =
limbo. Post-Win2000 ship, I'm thinking I could re-release the spec as =
informational if there is demand for it, as I believe the sample =
implementation has value, as does the expanded implementation =
requirements section.</FONT></P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Chris Harding [<A =
HREF=3D"mailto:c.harding@opengroup.org">mailto:c.harding@opengroup.org</=
A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Monday, November 15, 1999 11:11 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Paul Leach (Exchange); =
ietf-ldup@imc.org</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: d.may@opengroup.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: UUID Ref.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi -</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Deborah May writes:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Just one comment to add to Chris' response - =
the draft you are</FONT>
<BR><FONT SIZE=3D2>&gt; referring to is on the web at:</FONT>
<BR><FONT SIZE=3D2>&gt; =
www.opengroup.org/dce/info/draft-leach-uuids-guids-01.txt</FONT>
<BR><FONT SIZE=3D2>&gt; It did expire, however this page points you to =
two references for</FONT>
<BR><FONT SIZE=3D2>&gt; UUID/GUID definitions, one of which is the DCE =
RPC Specification</FONT>
<BR><FONT SIZE=3D2>&gt; Chris provided a pointer to.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;&lt;&lt;&lt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The second reference on that page is to:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ISO/IEC 11578:1996</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Information technology --</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Open Systems Interconnection -- =
Remote Procedure Call</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.iso.ch/cate/d2229.html" =
TARGET=3D"_blank">http://www.iso.ch/cate/d2229.html</A> </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; which I think answers Paul's question.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thanks, Deborah!</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The DCE RPC spec, and hence the UUID =
specification, was later </FONT>
<BR><FONT SIZE=3D2>&gt; incoroporated</FONT>
<BR><FONT SIZE=3D2>&gt; into an ISO RPC standard. Do you have a =
citation for that?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message----- </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Chris Harding</FONT>
<BR><FONT SIZE=3D2>&gt; [&lt;<A =
HREF=3D"mailto:c.harding@opengroup.org">mailto:c.harding@opengroup.org</=
A>&gt;<A =
HREF=3D"mailto:c.harding@opengroup.org">mailto:c.harding@opengroup.org</=
A>] </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Monday, November 15, 1999 8:14 AM =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: ietf-ldup@imc.org </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: UUID Ref. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Hi - </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; As promised in Friday's meeting, here is =
the reference to the UUID </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; specification. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The document concerned is Open Group =
Document C706 - DCE </FONT>
<BR><FONT SIZE=3D2>&gt; 1.1: Remote </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Procedure Call. This is freely available =
over the web. To </FONT>
<BR><FONT SIZE=3D2>&gt; get into the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; whole document via its TOC, go to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &lt;<A =
HREF=3D"http://www.opengroup.org/publications/catalog/c706.htm" =
TARGET=3D"_blank">http://www.opengroup.org/publications/catalog/c706.htm=
</A>&gt;<A HREF=3D"http:/" TARGET=3D"_blank">http:/</A></FONT>
<BR><FONT SIZE=3D2>&gt; /www.opengroup</FONT>
<BR><FONT SIZE=3D2>&gt; =
.org/publications/catalog/c706.htm&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Appendix A is at </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &lt;<A =
HREF=3D"http://www.opengroup.org/onlinepubs/009629399/apdxa.htm" =
TARGET=3D"_blank">http://www.opengroup.org/onlinepubs/009629399/apdxa.ht=
m</A>&gt;http:</FONT>
<BR><FONT SIZE=3D2>&gt; //www.opengrou</FONT>
<BR><FONT SIZE=3D2>&gt; p.org/onlinepubs/009629399/apdxa.htm - in&nbsp; =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the current </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; version, this appears to be a =
specification of the UUID&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; format rather than </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; a sample implementation description. =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Regards, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Chris </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; +++++ </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
-------------------------------------------------------------- </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ----------- </FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Chris Harding </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; T H E&nbsp;&nbsp;&nbsp; =
Development Manager </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; O P E N&nbsp;&nbsp; Apex Plaza, =
Forbury Road, Reading RG1 1AX, UK </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; G R O U P&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;<A =
HREF=3D"Mailto:c.harding@opengroup.org">Mailto:c.harding@opengroup.org</=
A>&gt;<A =
HREF=3D"Mailto:c.harding@opengroup.org">Mailto:c.harding@opengroup.org</=
A></FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; Ph: +44 118 950 8311 x2262 </FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
WWW: </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;<A HREF=3D"http://www.opengroup.org" =
TARGET=3D"_blank">http://www.opengroup.org</A>&gt;<A =
HREF=3D"http://www.opengroup.org" =
TARGET=3D"_blank">http://www.opengroup.org</A>&nbsp;&nbsp;&nbsp; =
Fx:</FONT>
<BR><FONT SIZE=3D2>&gt; +44 118 950 0110&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; OSF/1, Motif, UNIX and the &quot;X&quot; =
device are registered trademarks in </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the US and other countries, and IT =
DialTone and The Open Group are </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; trademarks of The Open Group. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
-------------------------------------------------------------- </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ----------- </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;&lt;&lt;&lt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Regards,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Chris</FONT>
<BR><FONT SIZE=3D2>&gt; +++++</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
--------------------------------------------------------------</FONT>
<BR><FONT SIZE=3D2>&gt; -----------</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; Chris Harding</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; T H E&nbsp;&nbsp;&nbsp; Development =
Manager</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; O P E N&nbsp;&nbsp; Apex Plaza, Forbury =
Road, Reading RG1 1AX, UK</FONT>
<BR><FONT SIZE=3D2>&gt; G R O U P&nbsp; <A =
HREF=3D"Mailto:c.harding@opengroup.org">Mailto:c.harding@opengroup.org</=
A>&nbsp;&nbsp; Ph: +44 118 950 8311 x2262</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; WWW: <A HREF=3D"http://www.opengroup.org" =
TARGET=3D"_blank">http://www.opengroup.org</A>&nbsp;&nbsp;&nbsp; Fx: =
+44 118 950 0110&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; OSF/1, Motif, UNIX and the &quot;X&quot; device =
are registered trademarks in</FONT>
<BR><FONT SIZE=3D2>&gt; the US and other countries, and IT DialTone and =
The Open Group are</FONT>
<BR><FONT SIZE=3D2>&gt; trademarks of The Open Group.</FONT>
<BR><FONT SIZE=3D2>&gt; =
--------------------------------------------------------------</FONT>
<BR><FONT SIZE=3D2>&gt; -----------</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BF2FA2.AD78DD50--


From owner-ietf-ldup@imc.org  Tue Nov 16 06:10:42 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19534
	for <ldup-archive@odin.ietf.org>; Tue, 16 Nov 1999 06:10:42 -0500 (EST)
Received: (from majordomo@localhost)
	by ns.secondary.com (8.9.3/8.9.3) id CAA21718
	for ietf-ldup-bks; Tue, 16 Nov 1999 02:36:36 -0800 (PST)
Received: from mailgate.rdg.opengroup.org (mailgate.rdg.opengroup.org [192.153.166.4])
	by ns.secondary.com (8.9.3/8.9.3) with SMTP id CAA21714
	for <ietf-ldup@imc.org>; Tue, 16 Nov 1999 02:36:34 -0800 (PST)
Received: by mailgate.rdg.opengroup.org; id AA12276; Tue, 16 Nov 1999 10:42:15 GMT
Received: from slip139-92-24-14.por.uk.ibm.net [139.92.24.14] by mailgate.rdg.opengroup.org via smtpd  V1.32 (99/03/30 12:28:06) for <d.may@opengroup.org> ; Tue Nov 16 10:42 GMT 1999
Message-Id: <3.0.3.32.19991116103536.006ce1b4@mailhome.rdg.opengroup.org>
X-Sender: cjh@mailhome.rdg.opengroup.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Tue, 16 Nov 1999 10:35:36 +0000
To: "Paul Leach (Exchange)" <paulle@Exchange.MICROSOFT.com>,
        "Paul Leach (Exchange)" <paulle@Exchange.MICROSOFT.com>,
        ietf-ldup@imc.org
From: Chris Harding <c.harding@opengroup.org>
Subject: Re: (c.harding 35704) RE: UUID Ref.
Cc: d.may@opengroup.org
In-Reply-To: <19398D273324D3118A2B0008C7E9A569051BEA94@SIT.platinum.corp
 .microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

Dear Paul,

From what you write, it sounds as though a possible course would be to
leave the ISO standard as an authoritative point of reference and add to it:

   - an implementation guide giving the detailed implementation requirements

   - a specification of the additional code-points.

These could be informational RFCs (or perhaps the second could be standards
track).

The information would not all be in the same document, but this is not such
a problem as it used to be, now that we can access documents over the web
(if the ISO document is not publicly available, the RFCs could have links
to the DCE spec.)

>>>>

The draft to which you refer was written by Rich Salz (formerly of the
OSF/OpenGroup) and me. 

It included a sample implementation, and some detailed implementation
requirements, which may permit more implementation flexibility than the
DCE/ISO spec (which was very procedural).

It also added code points for UUIDs created from psuedo-random number
generators (including hash functions over string constants). The additional
code points had OSF approval (via Rich), but when the reality of the
existence of the ISO standard hit home, we realized that IETF didn't have
change control. So the spec has sat in limbo. Post-Win2000 ship, I'm
thinking I could re-release the spec as informational if there is demand
for it, as I believe the sample implementation has value, as does the
expanded implementation requirements section.

> -----Original Message----- 
> From: Chris Harding
[<mailto:c.harding@opengroup.org>mailto:c.harding@opengroup.org] 
> Sent: Monday, November 15, 1999 11:11 AM 
> To: Paul Leach (Exchange); ietf-ldup@imc.org 
> Cc: d.may@opengroup.org 
> Subject: RE: UUID Ref. 
>  
>  
> Hi - 
>  
> Deborah May writes: 
>  
> >>>> 
> Just one comment to add to Chris' response - the draft you are 
> referring to is on the web at: 
> www.opengroup.org/dce/info/draft-leach-uuids-guids-01.txt 
> It did expire, however this page points you to two references for 
> UUID/GUID definitions, one of which is the DCE RPC Specification 
> Chris provided a pointer to. 
>  
>  
> <<<< 
>  
> The second reference on that page is to: 
>  
>                 ISO/IEC 11578:1996 
>                 Information technology -- 
>                 Open Systems Interconnection -- Remote Procedure Call 
>
<http://www.iso.ch/cate/d2229.html>http://www.iso.ch/cate/d2229.html  
>  
> which I think answers Paul's question. 
>  
> Thanks, Deborah! 
>  
> >>>> 
>  
> The DCE RPC spec, and hence the UUID specification, was later  
> incoroporated 
> into an ISO RPC standard. Do you have a citation for that? 
>  
> > -----Original Message-----  
> > From: Chris Harding 
>
[<<mailto:c.harding@opengroup.org>mailto:c.harding@opengroup.org><mailto:c.h
arding@opengroup.org>mailto:c.harding@opengroup.org]  
> > Sent: Monday, November 15, 1999 8:14 AM  
> > To: ietf-ldup@imc.org  
> > Subject: UUID Ref.  
> >   
> >   
> > Hi -  
> >   
> > As promised in Friday's meeting, here is the reference to the UUID  
> > specification.  
> >   
> > The document concerned is Open Group Document C706 - DCE  
> 1.1: Remote  
> > Procedure Call. This is freely available over the web. To  
> get into the  
> > whole document via its TOC, go to  
> > 
>
<<http://www.opengroup.org/publications/catalog/c706.htm>http://www.opengrou
p.org/publications/catalog/c706.htm><http:/>http:/ 
> /www.opengroup 
> .org/publications/catalog/c706.htm     
> > Appendix A is at  
> > 
>
<<http://www.opengroup.org/onlinepubs/009629399/apdxa.htm>http://www.opengro
up.org/onlinepubs/009629399/apdxa.htm>http: 
> //www.opengrou 
> p.org/onlinepubs/009629399/apdxa.htm - in   
> > the current  
> > version, this appears to be a specification of the UUID   
> > format rather than  
> > a sample implementation description.  
> >   
> >   
> >   
> > Regards,  
> >   
> > Chris  
> > +++++  
> >   
> > --------------------------------------------------------------  
> > -----------  
> >            Chris Harding  
> >   T H E    Development Manager  
> >  O P E N   Apex Plaza, Forbury Road, Reading RG1 1AX, UK  
> > G R O U P   
>
<<Mailto:c.harding@opengroup.org>Mailto:c.harding@opengroup.org><Mailto:c.ha
rding@opengroup.org>Mailto:c.harding@opengroup.org 
>   Ph: +44 118 950 8311 x2262  
> >            WWW:  
>
<<http://www.opengroup.org>http://www.opengroup.org><http://www.opengroup.or
g>http://www.opengroup.org    Fx: 
> +44 118 950 0110    
> >   
> > OSF/1, Motif, UNIX and the "X" device are registered trademarks in  
> > the US and other countries, and IT DialTone and The Open Group are  
> > trademarks of The Open Group.  
> > --------------------------------------------------------------  
> > -----------  
> >   
>  
> <<<< 
>  
>  
>  
> Regards, 
>  
> Chris 
> +++++ 
>  
> -------------------------------------------------------------- 
> ----------- 
>            Chris Harding 
>   T H E    Development Manager 
>  O P E N   Apex Plaza, Forbury Road, Reading RG1 1AX, UK 
> G R O U P  <Mailto:c.harding@opengroup.org>Mailto:c.harding@opengroup.org
  Ph: +44 118 950 8311 x2262 
>            WWW: <http://www.opengroup.org>http://www.opengroup.org    Fx:
+44 118 950 0110   
>  
> OSF/1, Motif, UNIX and the "X" device are registered trademarks in 
> the US and other countries, and IT DialTone and The Open Group are 
> trademarks of The Open Group. 
> -------------------------------------------------------------- 
> ----------- 
>  

<<<<



Regards,

Chris
+++++

-------------------------------------------------------------------------
           Chris Harding
  T H E    Development Manager
 O P E N   Apex Plaza, Forbury Road, Reading RG1 1AX, UK
G R O U P  Mailto:c.harding@opengroup.org   Ph: +44 118 950 8311 x2262
           WWW: http://www.opengroup.org    Fx: +44 118 950 0110  

OSF/1, Motif, UNIX and the "X" device are registered trademarks in
the US and other countries, and IT DialTone and The Open Group are
trademarks of The Open Group.
-------------------------------------------------------------------------


From owner-ietf-ldup@imc.org  Thu Nov 18 13:27:55 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16374
	for <ldup-archive@odin.ietf.org>; Thu, 18 Nov 1999 13:27:54 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id JAA01495
	for ietf-ldup-bks; Thu, 18 Nov 1999 09:42:30 -0800 (PST)
Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA01489
	for <ietf-ldup@imc.org>; Thu, 18 Nov 1999 09:42:28 -0800 (PST)
Received: from gypsy (localhost [127.0.0.1])
	by cantor.boolean.net (8.9.3/8.9.3) with SMTP id RAA80785
	for <ietf-ldup@imc.org>; Thu, 18 Nov 1999 17:43:56 GMT
	(envelope-from Kurt@OpenLDAP.Org)
Message-Id: <3.0.5.32.19991118094206.00941b30@localhost>
X-Sender: guru@localhost (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Thu, 18 Nov 1999 09:42:06 -0800
To: ietf-ldup@imc.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>
Subject: LDAPsubentry
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

Forwarded to owning WG...

>To: Ed_Reed@Novell.com
>From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>
>Cc: ietf-ldapext@netscape.com
>
>I would like to see LDAP subentry be an abstract object class
>to which is then subclassed as necessary to provide structure
>(including naming attributes).
>
>As defined, LDAP subentry requires cn.  This may not be appropriate
>for LDAP subentries.   I suggest:
>
>( ldapSubEntryOID NAME 'ldapSubEntry'
>   DESC 'LDAP Subentry abstract class, version 1'
>     SUP top ABSTRACT )
>
>( cnSubEntryOID NAME 'cnSubEntry'
>   DESC 'CN LDAP Subentry class, version 1'
>     SUP ldapSubEntry STRUCTURAL
>     MUST ( cn ) )
>
>Your schema definition would then be split as appropriate between
>the abstract class and the structural class.
>
>Regards, Kurt
>
>
>


From owner-ietf-ldup@imc.org  Thu Nov 18 23:57:07 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15712
	for <ldup-archive@odin.ietf.org>; Thu, 18 Nov 1999 23:57:06 -0500 (EST)
Received: (from majordomo@localhost)
	by ns.secondary.com (8.9.3/8.9.3) id UAA24485
	for ietf-ldup-bks; Thu, 18 Nov 1999 20:23:04 -0800 (PST)
Received: from mail.oncalldba.com (reed.oncalldba.com [166.70.104.61])
	by ns.secondary.com (8.9.3/8.9.3) with SMTP id UAA24474
	for <ietf-ldup@imc.org>; Thu, 18 Nov 1999 20:23:00 -0800 (PST)
Received: from RMINC_DOM-Message_Server by mail.oncalldba.com
	with Novell_GroupWise; Thu, 18 Nov 1999 21:13:31 -0700
Message-Id: <s8346bfb.054@mail.oncalldba.com>
X-Mailer: Novell GroupWise 5.5
Date: Thu, 18 Nov 1999 21:13:16 -0700
From: "Ed Reed" <eer@OnCallDBA.COM>
To: <osidirectory@az05.bull.com>, <ietf-ldup@imc.org>,
        <ietf-ldapext@netscape.com>, <Kurt@OpenLDAP.Org>
Subject: Re: LDAPsubentry
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=_D188D07B.87E68AFD"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_D188D07B.87E68AFD
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hmmm...I made it structural, because that's how the X.500 subentry
is defined...I can see doing it either way.

Any reaction from the X.500 community?  Does it matter to you,
one way or the other?  To be clear, the draft specifies ldapSubEntry
to be STRUCTURAL, and Kurt's proposal is to make it ABSTRACT,
instead.

Ed

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Ed Reed
Reed-Matthews, Inc.
+1 801 785 0315
http://www.OnCallDBA.COM

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org> 11/18/99 10:42AM >>>
Forwarded to owning WG...

>To: Ed_Reed@Novell.com
>From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>
>Cc: ietf-ldapext@netscape.com
>
>I would like to see LDAP subentry be an abstract object class
>to which is then subclassed as necessary to provide structure
>(including naming attributes).
>
>As defined, LDAP subentry requires cn.  This may not be appropriate
>for LDAP subentries.   I suggest:
>
>( ldapSubEntryOID NAME 'ldapSubEntry'
>   DESC 'LDAP Subentry abstract class, version 1'
>     SUP top ABSTRACT )
>
>( cnSubEntryOID NAME 'cnSubEntry'
>   DESC 'CN LDAP Subentry class, version 1'
>     SUP ldapSubEntry STRUCTURAL
>     MUST ( cn ) )
>
>Your schema definition would then be split as appropriate between
>the abstract class and the structural class.
>
>Regards, Kurt
>
>
>

--=_D188D07B.87E68AFD
Content-Type: text/plain
Content-Disposition: attachment; filename="TEXT.htm"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.2614.3500" name=GENERATOR></HEAD>
<BODY bgColor=#ffffff 
style="FONT: 10pt Arial; MARGIN-LEFT: 2px; MARGIN-TOP: 2px">
<DIV>Hmmm...I made it structural, because that's how the X.500 subentry</DIV>
<DIV>is defined...I can see doing it either way.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Any reaction from the X.500 community?&nbsp; Does it matter to you,</DIV>
<DIV>one way or the other?&nbsp; To be clear, the draft specifies 
ldapSubEntry</DIV>
<DIV>to be STRUCTURAL, and Kurt's proposal is to make it ABSTRACT,</DIV>
<DIV>instead.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Ed</DIV>
<DIV>&nbsp;</DIV>
<DIV>=================<BR>Ed Reed<BR>Reed-Matthews, Inc.<BR>+1 801 785 
0315<BR><A 
href="http://www.OnCallDBA.COM">http://www.OnCallDBA.COM</A><BR><BR>&gt;&gt;&gt; 
"Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.Org&gt; 11/18/99 10:42AM 
&gt;&gt;&gt;<BR>Forwarded to owning WG...<BR><BR>&gt;To: 
Ed_Reed@Novell.com<BR>&gt;From: "Kurt D. Zeilenga" 
&lt;Kurt@OpenLDAP.Org&gt;<BR>&gt;Cc: ietf-ldapext@netscape.com<BR>&gt;<BR>&gt;I 
would like to see LDAP subentry be an abstract object class<BR>&gt;to which is 
then subclassed as necessary to provide structure<BR>&gt;(including naming 
attributes).<BR>&gt;<BR>&gt;As defined, LDAP subentry requires cn.&nbsp; This 
may not be appropriate<BR>&gt;for LDAP subentries.&nbsp;&nbsp; I 
suggest:<BR>&gt;<BR>&gt;( ldapSubEntryOID NAME 
'ldapSubEntry'<BR>&gt;&nbsp;&nbsp; DESC 'LDAP Subentry abstract class, version 
1'<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; SUP top ABSTRACT )<BR>&gt;<BR>&gt;( 
cnSubEntryOID NAME 'cnSubEntry'<BR>&gt;&nbsp;&nbsp; DESC 'CN LDAP Subentry 
class, version 1'<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; SUP ldapSubEntry 
STRUCTURAL<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MUST ( cn ) )<BR>&gt;<BR>&gt;Your 
schema definition would then be split as appropriate between<BR>&gt;the abstract 
class and the structural class.<BR>&gt;<BR>&gt;Regards, 
Kurt<BR>&gt;<BR>&gt;<BR>&gt;<BR></DIV></BODY></HTML>

--=_D188D07B.87E68AFD--


From owner-ietf-ldup@imc.org  Fri Nov 19 00:01:03 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17565
	for <ldup-archive@odin.ietf.org>; Fri, 19 Nov 1999 00:00:52 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id UAA25247
	for ietf-ldup-bks; Thu, 18 Nov 1999 20:34:30 -0800 (PST)
Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id UAA25241
	for <ietf-ldup@imc.org>; Thu, 18 Nov 1999 20:34:29 -0800 (PST)
Received: from gypsy (localhost [127.0.0.1])
	by cantor.boolean.net (8.9.3/8.9.3) with SMTP id EAA90719;
	Fri, 19 Nov 1999 04:35:35 GMT
	(envelope-from kurt@boolean.net)
Message-Id: <3.0.5.32.19991118203342.00a0f100@localhost>
X-Sender: guru@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Thu, 18 Nov 1999 20:33:42 -0800
To: "Ed Reed" <eer@OnCallDBA.COM>
From: "Kurt D. Zeilenga" <kurt@boolean.net>
Subject: Re: LDAPsubentry
Cc: <osidirectory@az05.bull.com>, <ietf-ldup@imc.org>,
        <ietf-ldapext@netscape.com>, <Kurt@OpenLDAP.Org>
In-Reply-To: <s8346bfb.056@mail.oncalldba.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

At 09:13 PM 11/18/99 -0700, Ed Reed wrote:
>Hmmm...I made it structural, because that's how the X.500 subentry
>is defined...I can see doing it either way.
>
>Any reaction from the X.500 community?  Does it matter to you,
>one way or the other?  To be clear, the draft specifies ldapSubEntry
>to be STRUCTURAL, and Kurt's proposal is to make it ABSTRACT,
>instead.

I should note that my primary reason for desiring this change
is reuse.  I need such a beast but don't want to get stuck with
MUST cn.

Kurt

----
Kurt D. Zeilenga		<kurt@boolean.net>
Net Boolean Incorporated	<http://www.boolean.net/>


From owner-ietf-ldup@imc.org  Fri Nov 19 05:42:13 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10006
	for <ldup-archive@odin.ietf.org>; Fri, 19 Nov 1999 05:42:11 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id CAA07966
	for ietf-ldup-bks; Fri, 19 Nov 1999 02:06:50 -0800 (PST)
Received: from davisson.uni2.net (davisson.uni2.net [129.142.7.104])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id CAA07962
	for <ietf-ldup@imc.org>; Fri, 19 Nov 1999 02:06:47 -0800 (PST)
Received: from s-150943 (p426-050.ppp.get2net.dk [195.47.141.50])
	by davisson.uni2.net (8.9.3/8.9.1) with SMTP id LAA21669;
	Fri, 19 Nov 1999 11:07:59 +0100
Received: by localhost with Microsoft MAPI; Fri, 19 Nov 1999 11:07:40 +0100
Message-ID: <01BF327E.4BC91280.era.als@get2net.dk>
From: Erik Andersen <era.als@get2net.dk>
To: "'Ed Reed'" <eer@OnCallDBA.COM>,
        "osidirectory@az05.bull.com"
	 <osidirectory@az05.bull.com>,
        "ietf-ldup@imc.org"
	 <ietf-ldup@imc.org>,
        "ietf-ldapext@netscape.com"
	 <ietf-ldapext@netscape.com>,
        "Kurt@OpenLDAP.Org"
	 <Kurt@OpenLDAP.Org>
Subject: RE: LDAPsubentry
Date: Fri, 19 Nov 1999 11:06:29 +0100
Organization: Andersen's L-Service
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

The consequence of making it an abstract object class would be that the 
different types of subentries each should have a structural object class 
defined instead of an auxiliary object class (as we have it X.500). A naming 
attribute would have to be defined for each of those. This naming attribute 
could then be different for each type of subentry. What would the advantage be 
of that? The type of subentry is clearly indicated in the objectClass 
attribute.

As the same clients will access X.500 systems and LDAP servers, it must be an 
advantage for implementers not to have unnecessary differences.

Hope that helps.

Erik Andersen
CEN/ISSS/WS-DIR Chairman
Mobile: +45 20 97 14 90
E-mail;  era.als@get2net.dk
Internet: http://www.cenorm.be/isss/Workshop/DIR/Default.htm


-----Original Message-----
From:	Ed Reed [SMTP:eer@OnCallDBA.COM]
Sent:	19. november 1999 05:13
To:	osidirectory@az05.bull.com; ietf-ldup@imc.org; ietf-ldapext@netscape.com; 
Kurt@OpenLDAP.Org
Subject:	Re: LDAPsubentry

 << File: TEXT.htm >> Hmmm...I made it structural, because that's how the X.500 
subentry
is defined...I can see doing it either way.

Any reaction from the X.500 community?  Does it matter to you,
one way or the other?  To be clear, the draft specifies ldapSubEntry
to be STRUCTURAL, and Kurt's proposal is to make it ABSTRACT,
instead.

Ed

=================
Ed Reed
Reed-Matthews, Inc.
+1 801 785 0315
http://www.OnCallDBA.COM

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org> 11/18/99 10:42AM >>>
Forwarded to owning WG...

>To: Ed_Reed@Novell.com
>From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>
>Cc: ietf-ldapext@netscape.com
>
>I would like to see LDAP subentry be an abstract object class
>to which is then subclassed as necessary to provide structure
>(including naming attributes).
>
>As defined, LDAP subentry requires cn.  This may not be appropriate
>for LDAP subentries.   I suggest:
>
>( ldapSubEntryOID NAME 'ldapSubEntry'
>   DESC 'LDAP Subentry abstract class, version 1'
>     SUP top ABSTRACT )
>
>( cnSubEntryOID NAME 'cnSubEntry'
>   DESC 'CN LDAP Subentry class, version 1'
>     SUP ldapSubEntry STRUCTURAL
>     MUST ( cn ) )
>
>Your schema definition would then be split as appropriate between
>the abstract class and the structural class.
>
>Regards, Kurt
>
>
>



From owner-ietf-ldup@imc.org  Fri Nov 19 08:20:37 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26796
	for <ldup-archive@odin.ietf.org>; Fri, 19 Nov 1999 08:20:37 -0500 (EST)
Received: (from majordomo@localhost)
	by ns.secondary.com (8.9.3/8.9.3) id EAA12230
	for ietf-ldup-bks; Fri, 19 Nov 1999 04:43:58 -0800 (PST)
Received: from thoth.mch.sni.de (thoth.mch.sni.de [192.35.17.2])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id EAA12226
	for <ietf-ldup@imc.org>; Fri, 19 Nov 1999 04:43:55 -0800 (PST)
X-Envelope-Sender-Is: helmut.volpers@icn.siemens.de (at relayer thoth.mch.sni.de)
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by thoth.mch.sni.de (8.9.3/8.9.3) with ESMTP id NAA12667;
	Fri, 19 Nov 1999 13:44:33 +0100 (MET)
Received: from pinguin.mch.sni.de (pinguin.mch.sni.de [192.103.27.50])
	by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id NAA26428;
	Fri, 19 Nov 1999 13:44:33 +0100 (MET)
Received: from icn.siemens.de (x500-helmut-nt.mch.sni.de [139.23.80.134])
	by pinguin.mch.sni.de (8.8.8/8.8.8) with ESMTP id NAA05321;
	Fri, 19 Nov 1999 13:44:32 +0100
Message-ID: <3835462F.6E972FF5@icn.siemens.de>
Date: Fri, 19 Nov 1999 13:44:31 +0100
From: Helmut Volpers <helmut.volpers@icn.siemens.de>
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Ed Reed <eer@OnCallDBA.COM>
CC: osidirectory@az05.bull.com, ietf-ldup@imc.org, ietf-ldapext@netscape.com,
        Kurt@OpenLDAP.Org
Subject: Re: LDAPsubentry
References: <s8346bfb.055@mail.oncalldba.com>
Content-Type: multipart/mixed;
 boundary="------------0B3F684BBC150CBCA36D78F0"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

This is a multi-part message in MIME format.
--------------0B3F684BBC150CBCA36D78F0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Ed Reed wrote:
> 
> Hmmm...I made it structural, because that's how the X.500 subentry
> is defined...I can see doing it either way.
> 
> Any reaction from the X.500 community?  Does it matter to you,
> one way or the other?  To be clear, the draft specifies ldapSubEntry
> to be STRUCTURAL, and Kurt's proposal is to make it ABSTRACT,
> instead.

The reason why it should be structural is because ObjectClasses
like subSchema, collectiveAttributeSubentry or AccessControlSubentry
are auxiliary and every entry should have a structural ObjectClass,
that means if the Subentry ObjectClass is abstract I need another
structural ObjClass for the subentries.
I also didn't understand the real reason why it should be abstract ?

Helmut

> 
> Ed
> 
> =================
> Ed Reed
> Reed-Matthews, Inc.
> +1 801 785 0315
> http://www.OnCallDBA.COM
> 
> >>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org> 11/18/99 10:42AM >>>
> Forwarded to owning WG...
> 
> >To: Ed_Reed@Novell.com
> >From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>
> >Cc: ietf-ldapext@netscape.com
> >
> >I would like to see LDAP subentry be an abstract object class
> >to which is then subclassed as necessary to provide structure
> >(including naming attributes).
> >
> >As defined, LDAP subentry requires cn.  This may not be appropriate
> >for LDAP subentries.   I suggest:
> >
> >( ldapSubEntryOID NAME 'ldapSubEntry'
> >   DESC 'LDAP Subentry abstract class, version 1'
> >     SUP top ABSTRACT )
> >
> >( cnSubEntryOID NAME 'cnSubEntry'
> >   DESC 'CN LDAP Subentry class, version 1'
> >     SUP ldapSubEntry STRUCTURAL
> >     MUST ( cn ) )
> >
> >Your schema definition would then be split as appropriate between
> >the abstract class and the structural class.
> >
> >Regards, Kurt
> >
> >
> >
> 
>   ------------------------------------------------------------------------
> 
>    TEXT.htmName: TEXT.htm
>            Type: Plain Text (text/plain)
--------------0B3F684BBC150CBCA36D78F0
Content-Type: text/x-vcard; charset=us-ascii;
 name="helmut.volpers.vcf"
Content-Description: Card for Helmut  Volpers
Content-Disposition: attachment;
 filename="helmut.volpers.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Volpers;Helmut 
tel;fax:+49-89-63645860
tel;home:+49-89-1576588
tel;work:+49-89-63646713
x-mozilla-html:FALSE
url:http://www.siemens.com/bus-com/
adr:;;Otto-Hahn-Ring 6;Munich;;81730;Germany
version:2.1
email;internet:Helmut.Volpers@icn.siemens.de
title:Directory Server Architect
x-mozilla-cpt:;30160
fn:Volpers, Helmut 
end:vcard

--------------0B3F684BBC150CBCA36D78F0--



From owner-ietf-ldup@imc.org  Fri Nov 19 11:11:54 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11767
	for <ldup-archive@odin.ietf.org>; Fri, 19 Nov 1999 11:11:52 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id HAA15474
	for ietf-ldup-bks; Fri, 19 Nov 1999 07:31:04 -0800 (PST)
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id HAA15470
	for <ietf-ldup@imc.org>; Fri, 19 Nov 1999 07:30:58 -0800 (PST)
Received: from tintin.mcom.com (tintin.mcom.com [205.217.233.42])
	by netscape.com (8.8.5/8.8.5) with ESMTP id HAA01256
	for <ietf-ldup@imc.org>; Fri, 19 Nov 1999 07:31:47 -0800 (PST)
Received: from netscape.com ([205.217.243.75]) by
          tintin.mcom.com (Netscape Messaging Server 4.1) with ESMTP id
          FLGB5B00.9IE; Fri, 19 Nov 1999 07:31:59 -0800 
Message-ID: <38356D6C.7B0CB90D@netscape.com>
Date: Fri, 19 Nov 1999 10:31:56 -0500
From: Mark Smith <mcs@netscape.com>
Organization: Netscape Communications
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <kurt@boolean.net>
CC: Ed Reed <eer@OnCallDBA.COM>, osidirectory@az05.bull.com, ietf-ldup@imc.org,
        ietf-ldapext@netscape.com, Kurt@OpenLDAP.Org
Subject: Re: LDAPsubentry
References: <3.0.5.32.19991118203342.00a0f100@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

"Kurt D. Zeilenga" wrote:
> 
> At 09:13 PM 11/18/99 -0700, Ed Reed wrote:
> >Hmmm...I made it structural, because that's how the X.500 subentry
> >is defined...I can see doing it either way.
> >
> >Any reaction from the X.500 community?  Does it matter to you,
> >one way or the other?  To be clear, the draft specifies ldapSubEntry
> >to be STRUCTURAL, and Kurt's proposal is to make it ABSTRACT,
> >instead.
> 
> I should note that my primary reason for desiring this change
> is reuse.  I need such a beast but don't want to get stuck with
> MUST cn.

A simpler alternative would be to make cn a MAY (which allows for
subclasses that use a different naming attribute).  Kurt, can you
provide an example where cn won't meet your needs?

-- 
Mark Smith
iPlanet Directory Architect / Sun-Netscape Alliance
My words are my own, not my employer's.   Got LDAP?


From owner-ietf-ldup@imc.org  Fri Nov 19 11:13:20 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12227
	for <ldup-archive@odin.ietf.org>; Fri, 19 Nov 1999 11:13:17 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id HAA15505
	for ietf-ldup-bks; Fri, 19 Nov 1999 07:32:43 -0800 (PST)
Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id HAA15501
	for <ietf-ldup@imc.org>; Fri, 19 Nov 1999 07:32:43 -0800 (PST)
Received: from gypsy (localhost [127.0.0.1])
	by cantor.boolean.net (8.9.3/8.9.3) with SMTP id PAA01963;
	Fri, 19 Nov 1999 15:33:21 GMT
	(envelope-from Kurt@OpenLDAP.Org)
Message-Id: <3.0.5.32.19991119073124.00a21780@localhost>
X-Sender: guru@localhost (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Fri, 19 Nov 1999 07:31:24 -0800
To: Erik Andersen <era.als@get2net.dk>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>
Subject: RE: LDAPsubentry
Cc: "'Ed Reed'" <eer@OnCallDBA.COM>,
        "osidirectory@az05.bull.com" <osidirectory@az05.bull.com>,
        "ietf-ldup@imc.org" <ietf-ldup@imc.org>,
        "ietf-ldapext@netscape.com" <ietf-ldapext@netscape.com>
In-Reply-To: <01BF327E.4BC91280.era.als@get2net.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

At 11:06 AM 11/19/99 +0100, Erik Andersen wrote:
>The consequence of making it an abstract object class would be that the 
>different types of subentries each should have a structural object class 
>defined instead of an auxiliary object class (as we have it X.500).

No.  They could share a structural class subclassed from the
abstract class to provide cn naming.

Note: the intention of the LDAP subentry was for other subentries
to subclass ldapSubentry.  Your statement implies that the author
may want to rework the draft to indicate that implementors should
mix in auxiliary object classes to extend ldapSubentry for
specific uses.

>A naming attribute would have to be defined for each of those.

Yes.  But they MAY also share one structural object class.  However,
they would be also allowed to separately subclass the abstract class
if more appropriate for their application.

>This naming attribute 
>could then be different for each type of subentry. What would the advantage be 
>of that?

Some subentries can consume a huge amount of namespace.  If they
are forced to share 'cn' naming with other subentries, name space
conflicts will arise.  Such subentry need to use a naming attribute
which is not used otherwise to ensure no conflicts arise.

The benefit of defining both an abstract AND a structural
object class is that it offers flexibility at no significant cost.

MUST 'cn' will force those who cannot provide a cn attribute
to define other objectclasses for subentries which are not
subclasses of LDAPsubentry.  This would be bad.

>As the same clients will access X.500 systems and LDAP servers, it must be an 
>advantage for implementers not to have unnecessary differences.

I think LDAPsubentry differs enough already that X.500 clients are
likely to be quite lost already.  Dividing the class into two
(an abstract and a structural) object class would likely not
cause additional heartburn.


From owner-ietf-ldup@imc.org  Fri Nov 19 12:13:18 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07431
	for <ldup-archive@odin.ietf.org>; Fri, 19 Nov 1999 12:13:17 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id IAA16205
	for ietf-ldup-bks; Fri, 19 Nov 1999 08:15:40 -0800 (PST)
Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA16201
	for <ietf-ldup@imc.org>; Fri, 19 Nov 1999 08:15:39 -0800 (PST)
Received: from gypsy (localhost [127.0.0.1])
	by cantor.boolean.net (8.9.3/8.9.3) with SMTP id QAA03545;
	Fri, 19 Nov 1999 16:16:45 GMT
	(envelope-from Kurt@OpenLDAP.Org)
Message-Id: <3.0.5.32.19991119081447.00a5a6f0@localhost>
X-Sender: guru@localhost (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Fri, 19 Nov 1999 08:14:47 -0800
To: Mark Smith <mcs@netscape.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>
Subject: Re: LDAPsubentry
Cc: "Kurt D. Zeilenga" <kurt@boolean.net>, Ed Reed <eer@OnCallDBA.COM>,
        osidirectory@az05.bull.com, ietf-ldup@imc.org,
        ietf-ldapext@netscape.com
In-Reply-To: <38356D6C.7B0CB90D@netscape.com>
References: <3.0.5.32.19991118203342.00a0f100@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

At 10:31 AM 11/19/99 -0500, Mark Smith wrote:
>"Kurt D. Zeilenga" wrote:
>> 
>> At 09:13 PM 11/18/99 -0700, Ed Reed wrote:
>> >Hmmm...I made it structural, because that's how the X.500 subentry
>> >is defined...I can see doing it either way.
>> >
>> >Any reaction from the X.500 community?  Does it matter to you,
>> >one way or the other?  To be clear, the draft specifies ldapSubEntry
>> >to be STRUCTURAL, and Kurt's proposal is to make it ABSTRACT,
>> >instead.

Kurt's proposal is to make it abstract AND provide a structural
objectclass with CN naming.

This allows addition of new structural subentry objectclasses which
don't require CN naming to share semantics of the abstract subentry
class YET continues to allow mixin of auxiliary subentry
objectclasses with defined structural subentry objectclasses. 

>> 
>> I should note that my primary reason for desiring this change
>> is reuse.  I need such a beast but don't want to get stuck with
>> MUST cn.
>
>A simpler alternative would be to make cn a MAY (which allows for
>subclasses that use a different naming attribute).

MAY 'cn' would work for me.

>Kurt, can you provide an example where cn won't meet your needs?

Yes.

I am creating subentries associated with each authorization identity
which has access to a particular naming context (or Root DSE).  The
entries have one single value attribute which contains an octetString
representation of the authorization identity.  As this is the ONLY
value, it must be used for naming purposes.  As it's arbirtary, it
consumes the complete name space under the naming attribute within
that RDN.  If I am required to use CN naming, the name space consumed
by these subentries will colide with the namespace of other subentries.

I could use an auxiliary object class that mixed in a new naming
attribute to resolve name space issues, but MUST cn would require
I stuff something into CN.  I hestate stuff the authorization
identities as the matching rules associated with CN are not
appropripriate.  I could stuff an empty string into CN, but this
seems rather pointless.

Right now, I've defined my own structural objectclass for these
subentries which use a different naming attribute than cn.  I'd
like to have a common abstract object class which provides subentry
semantics to which multiple subentry structural objectclasses
can share.  For most implementations, there would likely only
be one such structural objectclasses (with cn naming), but others
could be defines as needed.

Kurt


From owner-ietf-ldup@imc.org  Fri Nov 19 14:17:17 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02613
	for <ldup-archive@odin.ietf.org>; Fri, 19 Nov 1999 14:17:16 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id KAA18086
	for ietf-ldup-bks; Fri, 19 Nov 1999 10:28:25 -0800 (PST)
Received: from tor-smtp2.netcom.ca (tor-smtp2.netcom.ca [207.181.101.101])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA18081
	for <ietf-ldup@imc.org>; Fri, 19 Nov 1999 10:28:24 -0800 (PST)
Received: from erikskov (van-bc7-28.netcom.ca [207.181.73.28])
	by tor-smtp2.netcom.ca (8.8.7-s-4/8.8.7) with SMTP id NAA20036;
	Fri, 19 Nov 1999 13:22:10 -0500 (EST)
Message-Id: <3.0.4.32.19991119101125.0073da74@popd.netcom.ca>
X-Sender: erikskov@popd.netcom.ca
X-Mailer: QUALCOMM Windows Eudora Light Plus Version 3.0.4 (32) with Spelling Checker
Date: Fri, 19 Nov 1999 10:11:25 -0800
To: "Ed Reed" <eer@OnCallDBA.COM>, <osidirectory@az05.bull.com>,
        <ietf-ldup@imc.org>, <ietf-ldapext@netscape.com>, <Kurt@openldap.org>
From: Erik Skovgaard <eskovgaard@geotrain.com>
Subject: Re: LDAPsubentry
In-Reply-To: <s8346bfb.055@mail.oncalldba.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

Ed,

STRUCTURAL sounds good to me.  In fact, it has to be. An ABSTRACT Object
Class cannot be instantiated.  It is merely used to create other Object
Classes through inheritance.

Cheers,                  ....Erik.
--------------------------------------
Erik Skovgaard
GeoTrain/Global Knowledge Network
Enterprise Directory Engineering
http://www.geotrain.com
Telephone: +1 604 244-9131

At 21:13 99/11/18 -0700, Ed Reed wrote:
>Hmmm...I made it structural, because that's how the X.500 subentry
>is defined...I can see doing it either way.
>
>Any reaction from the X.500 community?  Does it matter to you,
>one way or the other?  To be clear, the draft specifies ldapSubEntry
>to be STRUCTURAL, and Kurt's proposal is to make it ABSTRACT,
>instead.
>
>Ed
>
>=================
>Ed Reed
>Reed-Matthews, Inc.
>+1 801 785 0315
>http://www.OnCallDBA.COM
>
>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org> 11/18/99 10:42AM >>>
>Forwarded to owning WG...
>
>>To: Ed_Reed@Novell.com
>>From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>
>>Cc: ietf-ldapext@netscape.com
>>
>>I would like to see LDAP subentry be an abstract object class
>>to which is then subclassed as necessary to provide structure
>>(including naming attributes).
>>
>>As defined, LDAP subentry requires cn.  This may not be appropriate
>>for LDAP subentries.   I suggest:
>>
>>( ldapSubEntryOID NAME 'ldapSubEntry'
>>   DESC 'LDAP Subentry abstract class, version 1'
>>     SUP top ABSTRACT )
>>
>>( cnSubEntryOID NAME 'cnSubEntry'
>>   DESC 'CN LDAP Subentry class, version 1'
>>     SUP ldapSubEntry STRUCTURAL
>>     MUST ( cn ) )
>>
>>Your schema definition would then be split as appropriate between
>>the abstract class and the structural class.
>>
>>Regards, Kurt
>>
>>
>>
>
>Attachment Converted: "d:\Program Files\Eudora\Attach\TEXT2.htm"
>


From owner-ietf-ldup@imc.org  Mon Nov 22 13:54:41 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22818
	for <ldup-archive@odin.ietf.org>; Mon, 22 Nov 1999 13:54:40 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id KAA21424
	for ietf-ldup-bks; Mon, 22 Nov 1999 10:09:59 -0800 (PST)
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA21420
	for <ietf-ldup@imc.org>; Mon, 22 Nov 1999 10:09:58 -0800 (PST)
Received: from tintin.mcom.com (tintin.mcom.com [205.217.233.42])
	by netscape.com (8.8.5/8.8.5) with ESMTP id KAA06459
	for <ietf-ldup@imc.org>; Mon, 22 Nov 1999 10:11:00 -0800 (PST)
Received: from netscape.com ([208.12.63.197]) by tintin.mcom.com
          (Netscape Messaging Server 4.1) with ESMTP id FLM2IS00.CQ7; Mon,
          22 Nov 1999 10:11:16 -0800 
Message-ID: <38398689.128545F9@netscape.com>
Date: Mon, 22 Nov 1999 10:08:09 -0800
From: merrells@netscape.com (John Merrells)
Organization: Netscape Communications
X-Mailer: Mozilla 4.6 [en]C-NSCP  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-ldapext@netscape.com, ietf-lcup@netscape.com,
        LDUP <ietf-ldup@imc.org>
Subject: LDAP Client Update Protocol
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


At the end of the LDUP meeting in Washington I introduced a new
topic for discussion: An LDAP Client Update Protocol. This new
protocol is intended to address the following client needs.

1 -  Mobile clients that maintain a local copy of directory data. 
     While off-line, the client uses the local copy of the data. 
     When the client connects to the network, it synchronizes with 
     the current directory content and can be optionally notified
     about the changes that occur while it is on-line. For example,
     a mail client can maintain a local copy of the corporate address
     book which it synchronizes with the master copy whenever the client
     gets connected to the corporate network. 

2 -  Applications intending to synchronize heterogeneous data stores.
     A meta directory application, for instance, would periodically
     retrieve a list of modified entries from the directory, construct 
     the changes and apply them to a foreign data store. 

3 -  Clients that need to take certain actions when a directory entry 
     is modified. For instance, an electronic mail repository may want
     to perform a "create mailbox" task when a new person entry is added
     to an LDAP directory and a "delete mailbox" task when a person entry
     is removed. 

This work will draw experience from the LDUP working group, and will
be predominently based upon the DirSync, PSearch, and TSearch drafts.

Since this work is suffiently distinct from LDUP and LDAPext I have
created a new mailing list for discussions on this topic. To subscribe
send a plain text message to ietf-lcup-request@netscape.com with the
word 'subscribe' in the body.

John


[PSEARCH] M. Smith "A Simple LDAP Change Notification Mechanism", INTERNET-DRAFT
<draft-ietf-ldapext-psearch-01.txt>, August 1998. 

[TSEARCH] M.Whal "LDAPv3 Triggered Search Control", INTERNET-DRAFT
<draft-ietf-ldapext-trigger-01.txt>,  August 1998. 

[DIRSYNC] M. Armijo "Microsoft LDAP Control for Directory Synchronization",
INTERNET-DRAFT
<draft-armijo-ldap-dirsync-00.txt>, August 1999.


From owner-ietf-ldup@imc.org  Tue Nov 23 21:08:25 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13046
	for <ldup-archive@odin.ietf.org>; Tue, 23 Nov 1999 21:08:24 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id RAA17111
	for ietf-ldup-bks; Tue, 23 Nov 1999 17:38:11 -0800 (PST)
Received: from dir1.control.att.com ([135.207.251.15])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id RAA17107
	for <ietf-ldup@imc.org>; Tue, 23 Nov 1999 17:38:10 -0800 (PST)
Received: from att.com (pest.control.att.com [135.207.251.76])
	by dir1.control.att.com (Postfix) with ESMTP
	id 7B5E771F6; Tue, 23 Nov 1999 20:40:03 -0500 (EST)
Message-ID: <383B4277.DFA787E8@att.com>
Date: Tue, 23 Nov 1999 20:42:15 -0500
From: Chris Apple <capple@att.com>
Organization: AT&T Labs
X-Mailer: Mozilla 4.51 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: John Merrells <merrells@netscape.com>
Cc: ietf-ldapext@netscape.com, ietf-lcup@netscape.com, ietf-ldup@imc.org
Subject: Re: LDAP Client Update Protocol
References: <38398689.128545F9@netscape.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

John Merrells wrote:
> 
> At the end of the LDUP meeting in Washington I introduced a new
> topic for discussion: An LDAP Client Update Protocol. This new
> protocol is intended to address the following client needs.
> 
> 1 -  Mobile clients that maintain a local copy of directory data.
>      While off-line, the client uses the local copy of the data.
>      When the client connects to the network, it synchronizes with
>      the current directory content and can be optionally notified
>      about the changes that occur while it is on-line. For example,
>      a mail client can maintain a local copy of the corporate address
>      book which it synchronizes with the master copy whenever the client
>      gets connected to the corporate network.

Is it your intent that 1 addresses the need of read-only clients?

Or can you make modifications to the local copy that are subsequently
synchronized to the server in addition to supporting the propagation
of updates from server to local copy?

> 
> 2 -  Applications intending to synchronize heterogeneous data stores.
>      A meta directory application, for instance, would periodically
>      retrieve a list of modified entries from the directory, construct
>      the changes and apply them to a foreign data store.
> 
> 3 -  Clients that need to take certain actions when a directory entry
>      is modified. For instance, an electronic mail repository may want
>      to perform a "create mailbox" task when a new person entry is added
>      to an LDAP directory and a "delete mailbox" task when a person entry
>      is removed.
> 
> This work will draw experience from the LDUP working group, and will
> be predominently based upon the DirSync, PSearch, and TSearch drafts.
> 
> Since this work is suffiently distinct from LDUP and LDAPext I have
> created a new mailing list for discussions on this topic. To subscribe
> send a plain text message to ietf-lcup-request@netscape.com with the
> word 'subscribe' in the body.
> 
> John
> 
> [PSEARCH] M. Smith "A Simple LDAP Change Notification Mechanism", INTERNET-DRAFT
> <draft-ietf-ldapext-psearch-01.txt>, August 1998.
> 
> [TSEARCH] M.Whal "LDAPv3 Triggered Search Control", INTERNET-DRAFT
> <draft-ietf-ldapext-trigger-01.txt>,  August 1998.
> 
> [DIRSYNC] M. Armijo "Microsoft LDAP Control for Directory Synchronization",
> INTERNET-DRAFT
> <draft-armijo-ldap-dirsync-00.txt>, August 1999.

-- 
------------------------------------------------------------------------
Chris Apple                     Business Site: AnyWho Directory Service
Internet Directory Group                       http://www.anywho.com
AT&T Labs
capple@control.att.com
+1 973 236 6470                 Tired of slow directories?  Try AnyWho.
------------------------------------------------------------------------


From owner-ietf-ldup@imc.org  Tue Nov 23 21:20:42 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19272
	for <ldup-archive@odin.ietf.org>; Tue, 23 Nov 1999 21:20:41 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id RAA17211
	for ietf-ldup-bks; Tue, 23 Nov 1999 17:45:41 -0800 (PST)
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id RAA17207
	for <ietf-ldup@imc.org>; Tue, 23 Nov 1999 17:45:40 -0800 (PST)
Received: from tintin.mcom.com (tintin.mcom.com [205.217.233.42])
	by netscape.com (8.8.5/8.8.5) with ESMTP id RAA08571
	for <ietf-ldup@imc.org>; Tue, 23 Nov 1999 17:46:46 -0800 (PST)
Received: from netscape.com ([208.12.63.197]) by tintin.mcom.com
          (Netscape Messaging Server 4.1) with ESMTP id FLOIAH00.827; Tue,
          23 Nov 1999 17:47:05 -0800 
Message-ID: <383B42D8.89569E2C@netscape.com>
Date: Tue, 23 Nov 1999 17:43:52 -0800
From: merrells@netscape.com (John Merrells)
Organization: Netscape Communications
X-Mailer: Mozilla 4.7 [en]C-NSCP  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Chris Apple <capple@att.com>
CC: ietf-ldapext@netscape.com, ietf-lcup@netscape.com, ietf-ldup@imc.org
Subject: Re: LDAP Client Update Protocol
References: <38398689.128545F9@netscape.com> <383B4277.DFA787E8@att.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Chris Apple wrote:
> 
> John Merrells wrote:
> >
> > At the end of the LDUP meeting in Washington I introduced a new
> > topic for discussion: An LDAP Client Update Protocol. This new
> > protocol is intended to address the following client needs.
> >
> > 1 -  Mobile clients that maintain a local copy of directory data.
> >      While off-line, the client uses the local copy of the data.
> >      When the client connects to the network, it synchronizes with
> >      the current directory content and can be optionally notified
> >      about the changes that occur while it is on-line. For example,
> >      a mail client can maintain a local copy of the corporate address
> >      book which it synchronizes with the master copy whenever the client
> >      gets connected to the corporate network.
> 
> Is it your intent that 1 addresses the need of read-only clients?
> 
> Or can you make modifications to the local copy that are subsequently
> synchronized to the server in addition to supporting the propagation
> of updates from server to local copy?

My intention, is that this protocol is for a one way update from the
server to the client.  If the client wants to send updates to the
server then it should use the regular LDAP Update Operations to do
this.

If anyone replies to this message please restrict the recipient list
to ietf-lcup to save noise on ietf-ldapext and ietf-ldup.

John


From owner-ietf-ldup@imc.org  Thu Nov 25 21:19:02 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25743
	for <ldup-archive@odin.ietf.org>; Thu, 25 Nov 1999 21:19:01 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id RAA19300
	for ietf-ldup-bks; Thu, 25 Nov 1999 17:45:22 -0800 (PST)
Received: from royou ([202.104.205.6])
	by ns.secondary.com (8.9.3/8.9.3) with SMTP id RAA19286
	for <ietf-ldup@imc.org>; Thu, 25 Nov 1999 17:45:16 -0800 (PST)
Message-Id: <199911260145.RAA19286@ns.secondary.com>
From: "华立服务" <hualicn@cmmail.com>
To: <ietf-ldup@imc.org>
Subject: 你离不开“乔登”
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Mon, 22 Nov 1999 09:42:02
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

    乔登卫浴为台湾世引国际有限公司所生产的一系列产品, 主要生产
卫生间及厨房用各式龙头及配件，其中包括一百余种按縻缸专用高级龙头，
广泛为全世界高级旅馆采用。
    乔登卫浴款式多、标准高、价格大众化，在全国设有40家特约经销商，
为客户提供最完善的售后服务，并为消费者提供了长达五年的产品质量保
证。
     欢迎使用乔登卫浴。
     大陆工厂:宝坚(江门)水暖器材有限公司
     网址:http://www.joden.com.cn/ 
—————　The message was sent by Super Mass Mail　—————
   Download from The Worldfax Network.　http://www.worldfax.net
   Start send worldwide free fax and(or) get free website advertising now!


