RE: draft-ietf-ips-iscsi-boot-00.txt

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

Prasenjit,

TFTP should be a good starting point.  Other protocols can model from the
TFTP sequence and defined fields.

Doug

> Doug and Costa,
>
> You are both right - however, we may have to include protocols other than
> tftp
> since there are a substantial number of boot ROMs that do not
> support tftp.
>
> Also, under the current draft, you can tftp a iscsi initiator capable boot
> image
> and then do a real boot off some iscsi target - the only catch is that the
> iscsi boot client has to qualify what it wants to boot and this is
> certainly
> possible.
>
> Prasenjit
>
>
> csapuntz@cisco.com@ece.cmu.edu on 11/22/2000 11:48:39 AM
>
> Sent by:  owner-ips@ece.cmu.edu
>
>
> To:   "Douglas Otis" <dotis@sanlight.net>
> cc:   "Ips" <ips@ece.cmu.edu>, csapuntz@cisco.com
> Subject:  Re: draft-ietf-ips-iscsi-boot-00.txt
>
>
>
>
> Doug,
>
> You make a good point that we ignored today's boot ROMs.
>
> The boot team will go back and look at how to accomodate both TFTP-boot
> and iSCSI information in the DHCP/BOOTP info.
>
> Thanks,
> -Costa
>
>
> "Douglas Otis" <dotis@sanlight.net> writes:
>
> > WG,
> >
> > An immediate solution, rather than modification of network booting ROMs,
> > would be useful.  Despite eventual success iSCSI may enjoy, it would be
> > unwise to endorse this proposal as a recommendation of ROMing iSCSI.  Is
> it
> > possible to modify this proposal into utilizing existing ROMs?
> >
> > Doug
>
>
>
>