WARNING: This server is unstable and will be retired in the next days. If you want to keep this forum available, please request immediately a migration on the Nabble Support forum. Forums that don't receive any migration request will be deleted forever.

 « Return to Thread: no DHCP-assigned InitiatorName

Re: no DHCP-assigned InitiatorName: Procedural notes

by Michael Howard-3 :: Rate this Message:

| View in Thread

Black_David@... wrote:
> A couple of procedural notes:
>
>> I am writing this memo to the IETF IP Storage Working Group to voice
>> my concern over the apparent lack of IETF or industry standard for
>> having a DHCP server pass an InitiatorName to an iSCSI boot client.
>
> The IP Storage WG has been closed, BUT this list is still a fine place
> to discuss this sort of topic, and it can be addressed via an individual
> Internet-Draft (a WG is not required to do work).

Understood.

>> This issue may be something that you are already aware of, and may be
>> something that you are already working to address.
>>
>> (I am going to ignore the related issues of CHAP username and secret)
>
> Considering that DHCP has no real security, one cannot pass the CHAP
> secret in the clear via DHCP.  The CHAP username should not cause a
> problem.

I agree.


Michael
_______________________________________________
Ips mailing list
Ips@...
https://www.ietf.org/mailman/listinfo/ips

 « Return to Thread: no DHCP-assigned InitiatorName