RE: I-D ACTION:draft-ietf-ips-iscsi-boot-00.txt

["Douglas Otis" <dotis@sanlight.net>]

Prasenjit,

As LDAP often supports DHCP services, simpler and more secure Internet
address conveyance should be supported if not recommended to that of using
names and name servers within the boot process.

Doug

> Hi Pankaj,
>
> I personally think that the use of DHCP and SLP is more complementary.
> We cannot expect all iSCSI initiators and targets to be SLP capable.
>
> In the case an iSCSI boot client is not SLP-capable, then you would need
> DHCP to figure out the location of the SLP agent.
>
> In this case, we are using DHCP to directly figure out the iSCSI boot
> server
> (if possible) while configuring the iSCSI boot client.
>
> In this context, you should think of SLP as a potential discovery server -
> that discussion is being the aegis of the iSCSI naming and discovery
> service
> team.
>
> Regards,
> Prasenjit
>
>    Prasenjit Sarkar
>    Research Staff Member
>    IBM Almaden Research
>    San Jose
>
>
> "Mehra, Pankaj" <pankaj.mehra@compaq.com>@ece.cmu.edu on 11/22/2000
> 10:02:16 AM
>
> Sent by:  owner-ips@ece.cmu.edu
>
>
> To:   ips@ece.cmu.edu
> cc:
> Subject:  RE: I-D ACTION:draft-ietf-ips-iscsi-boot-00.txt
>
>
>
> The draft draft-ietf-ips-iscsi-boot-00.txt refers to the much older RLP
> (which dates back to 1983) rather than the more up-to-date (ca. 1999)
> service location protocol version 2 (SLPv2). This is relevant because the
> format of the "file" field in the DHCPv4/BOOTP headers fits nicely within
> the framework of service URLs.
>
> In fact, if the booting host were to simply behave like an SLP UA looking
> for "iscsi:*" URLs, then it would not need to do anything special to
> satisfy
> all of the requirements set forth for this draft.
>
> The SLP drafts are standards track so it does not make sense to keep
> reinventing the service location infrastructure.
>
> Pankaj Mehra, Compaq Tandem Labs,
> 19333 Vallco Parkway, CAC 1-27, Cupertino, CA 95014
> (408)285-1823 (voice)           (408)285-1819 (FAX)
>
>
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Wednesday, 22 November, 2000 3:04 AM
> Cc: ips@ece.cmu.edu
> Subject: I-D ACTION:draft-ietf-ips-iscsi-boot-00.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the IP Storage Working Group of the IETF.
>
>      Title          : A Standard for BootStrapping Clients using the
> iSCSI
>                           Protocol
>      Author(s) : P. Sarkar, D. Missimer, C. Sapuntzakis
>      Filename  : draft-ietf-ips-iscsi-boot-00.txt
>      Pages          : 7
>      Date      : 21-Nov-00
>
> The Small Computer Systems Interface (SCSI) is a popular family of
> protocols for communicating with I/O devices, especially storage
> devices.  iSCSI is a proposed transport protocol for SCSI that
> operates on top of TCP[12].  This memo describes a standard mechanism
> to enable clients to bootstrap themselves using the iSCSI protocol.
> The goal of this standard is to enable clients to obtain the
> information to open an iSCSI session with the iSCSI bootstrpping
> server, assuming this information is not available.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ips-iscsi-boot-00.txt
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>      "get draft-ietf-ips-iscsi-boot-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
>      mailserv@ietf.org.
> In the body type:
>      "FILE /internet-drafts/draft-ietf-ips-iscsi-boot-00.txt".
>
> NOTE:     The mail server at ietf.org can return the document in
>      MIME-encoded form by using the "mpack" utility.  To use this
>      feature, insert the command "ENCODING mime" before the "FILE"
>      command.  To decode the response(s), you will need "munpack" or
>      a MIME-compliant mail reader.  Different MIME-compliant mail readers
>      exhibit different behavior, especially when dealing with
>      "multipart" MIME messages (i.e. documents which have been split
>      up into multiple messages), so check your local documentation on
>      how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
>
>