LDAP and XML

[Black_David@emc.com]

Doug,

With my WG co-chair hat on ... this thread needs to
stop, because Marjorie's offer to include LDAP in
addition to XML as an example is reasonable, and is
all that needs to be done for the iSCSI requirements
draft.  Among the examples of the use of XML for
management software is the XML dialect of CIM used
by both DMTF and SNIA, and CIM can clearly be extended
to include iSCSI.  Hence the suggestion that XML be
removed as an inappropriate example is hereby
rejected.  The inclusion of XML as an example
does not obligate the WG to develop an XML schema
any more than inclusion of LDAP would obligate
the WG to develop an LDAP schema.  FWIW, use of
XML does not require a "database" - e.g., some
of the data retrieved by SNMP from the MIB could
also be encoded in XML for retrieval via HTTP.

Comments from others who feel this topic is important
are welcome, but Doug's well-known opinion on LDAP is
noted and should not be repeated on the list in
discussion of the iSCSI requirements draft prior to
the interim meeting.

Thanks,
--David

---------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 42 South St., Hopkinton, MA  01748
+1 (508) 435-1000 x75140     FAX: +1 (508) 497-8500
black_david@emc.com       Mobile: +1 (978) 394-7754
---------------------------------------------------

> -----Original Message-----
> From:	Douglas Otis [SMTP:dotis@sanlight.net]
> Sent:	Wednesday, April 11, 2001 9:33 PM
> To:	KRUEGER,MARJORIE (HP-Roseville,ex1); ips@ece.cmu.edu
> Subject:	RE: iSCSI Naming: WWUIs, URNs, and namespaces
> 
> Marjorie,
> 
> Although there is nothing within requirements documentation regarding how
> an
> XML database scheme is used within an iSCSI architecture, there must be
> some
> relationship either directly or indirectly or it does not belong.  The
> aspect of using this database is unclear, so your views in this area are
> welcome in relating the function you understand this database fulfilling.
> I
> simply said there must be some way to find this service with a substratum
> of
> XML in whatever form it takes.  This service should be comprehensive and
> provide SCSI related items to allow a client, directly or indirectly, the
> means for successful communication using iSCSI.  I did not indicate this
> would be used as a discovery tool, but rather there would need to be such
> a
> means in place to allow its use.  Centralized data removes the abstraction
> server concept that has been found objectionable.  I was attempting to
> view
> such data in that light.
> 
> Doug
> 
> > > There is a need to obtain iSCSI configuration information in
> > > a generalized
> > > way.  This information should allow the client to find the
> > > server using
> > > existing IP namespace information.
> > ..snip..
> >
> > >
> > > Marjorie had mentioned that some are considering XML to support this
> > > function.  You will need some way to find this service.
> >
> > You misread that paragraph in the iSCSI Requirements document.  There
> has
> > been no assertion that storage devices will use XML to discover
> > each other!
> > To quote the requirements document:
> >
> > "... Development of specifications for iSCSI device management as
> > MIBs, XML
> > schemas, etc"
> >
> > Device management is much different (and entirely separate) from service
> > discovery and authentication.  Naming is an a construct for
> > identity, which
> > is necessary for authentication.
> >
> > Marj
> >