[Ips] RE: iSCSI boot - root path DHCP option
Black_David@emc.com Mon, 30 July 2007 02:14 UTC
Return-path: <ips-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFKm3-0004MY-TE; Sun, 29 Jul 2007 22:14:19 -0400
Received: from ips by megatron.ietf.org with local (Exim 4.43) id 1IFKm2-0004MT-4M for ips-confirm+ok@megatron.ietf.org; Sun, 29 Jul 2007 22:14:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFKm1-0004ML-Qw for ips@ietf.org; Sun, 29 Jul 2007 22:14:17 -0400
Received: from mexforward.lss.emc.com ([128.222.32.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFKm0-00045b-G9 for ips@ietf.org; Sun, 29 Jul 2007 22:14:17 -0400
Received: from mailhub.lss.emc.com (uraeus.lss.emc.com [10.254.144.14]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id l6U2EEn6024718; Sun, 29 Jul 2007 22:14:15 -0400 (EDT)
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id l6U2DYHs006376; Sun, 29 Jul 2007 22:14:10 -0400 (EDT)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.12]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 29 Jul 2007 22:14:06 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 29 Jul 2007 22:14:05 -0400
Message-ID: <F222151D3323874393F83102D614E0550A4D23F3@CORPUSMX20A.corp.emc.com>
In-Reply-To: <D2E118A1E7268F449C469EA2F301D9296533E8@exil.voltaire.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: iSCSI boot - root path DHCP option
Thread-Index: AcfPd7h8p2QiRcAeTW+A4vzoaFWfvwC1vhmg
References: <D2E118A1E7268F449C469EA2F301D9296533E8@exil.voltaire.com>
To: yaronh@voltaire.com, ips@ietf.org
X-OriginalArrivalTime: 30 Jul 2007 02:14:06.0013 (UTC) FILETIME=[4E3BA6D0:01C7D24F]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.7.6.21134
X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -3, HTML_70_90 0.1, NO_REAL_NAME 0, __C230066_P5 0, __CP_URI_IN_BODY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __HTML_FONT_BLUE 0, __IMS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_HTML 0'
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 9f79b8e383fd3af2b1b5b1d0910f6094
Cc:
Subject: [Ips] RE: iSCSI boot - root path DHCP option
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1571789957=="
Errors-To: ips-bounces@ietf.org
Yaron, RFC 4173 essentially specifies the format of the root path option when the path string begins with "iscsi:". The implementation you refer to has chosen to do something else - the result is likely to be implementation-specific and have interoperability issues. If there's interest in updating RFC 4173 to address additional issues and/or standardize this format, please submit an Internet-Draft. It is not necessary to replace RFC 4173 in its entirety - a description of what is new and/or changed will suffice. Thanks, --David (ips WG chair) ---------------------------------------------------- David L. Black, Senior Technologist EMC Corporation, 176 South St., Hopkinton, MA 01748 +1 (508) 293-7953 FAX: +1 (508) 293-7786 black_david@emc.com Mobile: +1 (978) 394-7754 ---------------------------------------------------- ________________________________ From: Yaron Haviv [mailto:yaronh@voltaire.com] Sent: Thursday, July 26, 2007 7:26 AM To: Black, David; ips@ietf.org Subject: iSCSI boot - root path DHCP option Guys, I'm trying to figure out something relating to the iSCSI root-path DHCP option The iSCSI boot spec (RFC4173) seem to indicate that the iSCSI root path option in the DHCP server should look like: "iscsi:"<servername>":"<protocol>":"<port>":"<LUN>":"<targetname> While I saw an implementation that uses: (http://iscsi-init.sourceforge.net/README.html) option root-path "[if_name1:]<target_ip1>[,[if_name2:]<target_ip2>]:/<target_name>[/<init iator_name>[/<lun_number>]]"; the RFC doesn't seem to address key issues which are enabled through the 2nd alternative such as specifying an alternate IP address of a target (pretty important for HA) and specifying the initiator Iqn (after all the LUN masking is done on the target based on the initiator iqn) Any idea if the RFC taken those into considerations, or has changed recently ? Thanks, Yaron
_______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips
- [Ips] iSCSI boot - root path DHCP option Yaron Haviv
- [Ips] RE: iSCSI boot - root path DHCP option Black_David