From ips-bounces@ietf.org Fri Apr 1 15:36:29 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08902 for ; Fri, 1 Apr 2005 15:36:29 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHSzz-0002hJ-Ih for ips-web-archive@ietf.org; Fri, 01 Apr 2005 15:44:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHSi7-0002kN-1H; Fri, 01 Apr 2005 15:25:43 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHSi3-0002jq-19; Fri, 01 Apr 2005 15:25:39 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06053; Fri, 1 Apr 2005 15:25:35 -0500 (EST) Message-Id: <200504012025.PAA06053@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Fri, 01 Apr 2005 15:25:35 -0500 Cc: ips@ietf.org Subject: [Ips] I-D ACTION:draft-ietf-ips-iser-03.txt X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db --NextPart 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 : iSCSI Extensions for RDMA Specification Author(s) : M. Ko, et al. Filename : draft-ietf-ips-iser-03.txt Pages : 87 Date : 2005-4-1 iSCSI Extensions for RDMA provides the RDMA data transfer capability to iSCSI [iSCSI] by layering iSCSI on top of the Remote Direct Memory Access Protocol (RDMAP). The iWARP protocol suite provides RDMA Read and Write services, which enable data to be transferred directly into SCSI I/O Buffers without intermediate data copies. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ips-iser-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-iser-03.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-iser-03.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-4-1155059.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ips-iser-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ips-iser-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-4-1155059.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips --NextPart-- From ips-bounces@ietf.org Fri Apr 1 16:39:10 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24332 for ; Fri, 1 Apr 2005 16:39:10 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHTyc-0000Jm-To for ips-web-archive@ietf.org; Fri, 01 Apr 2005 16:46:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHTla-0008Rk-My; Fri, 01 Apr 2005 16:33:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DHTlZ-0008Rf-Hk for ips@megatron.ietf.org; Fri, 01 Apr 2005 16:33:21 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23392 for ; Fri, 1 Apr 2005 16:33:19 -0500 (EST) Received: from e3.ny.us.ibm.com ([32.97.182.143]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHTsy-0008OZ-D6 for ips@ietf.org; Fri, 01 Apr 2005 16:41:00 -0500 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e3.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j31LXCpK004157 for ; Fri, 1 Apr 2005 16:33:12 -0500 Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay04.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j31LX6k4218104 for ; Fri, 1 Apr 2005 16:33:06 -0500 Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j31LX65x020825 for ; Fri, 1 Apr 2005 16:33:06 -0500 Received: from d01ml604.pok.ibm.com (d01ml604.pok.ibm.com [9.56.227.90]) by d01av04.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j31LX650020666 for ; Fri, 1 Apr 2005 16:33:06 -0500 In-Reply-To: <200504012025.PAA06053@ietf.org> Importance: Normal MIME-Version: 1.0 To: ips@ietf.org Subject: Re: [Ips] I-D ACTION:draft-ietf-ips-iser-03.txt X-Mailer: Lotus Notes Release 6.5.2 June 01, 2004 Message-ID: From: Mike Ko Date: Fri, 1 Apr 2005 13:32:59 -0800 X-MIMETrack: Serialize by Router on D01ML604/01/M/IBM(Build V70_M4_01112005 Beta 3|January 11, 2005) at 04/01/2005 16:33:05, Serialize complete at 04/01/2005 16:33:05 Content-Type: text/plain; charset="US-ASCII" X-Spam-Score: 0.0 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db Version -03 of the iSER draft is now available. Here are the significant changes in this version: Sec.3: Added a new paragraph to state that qualifiers are required to support Operational Primitives but how they are realized are up to implementation. With this clarification, the MUST directives in the draft associated with qualifiers have been retained. Sec.8.3: Updated the way unidirectional NOP-outs are retired to account for the NOP-out in-flight problem as discussed in the Minneapolis meeting. Sec.8.4: No changes are required for NOP-ins since StatSN is maintained on a per connection basis Sec. 10.1.3.4: Added the protocol error handling for an iSER node that acts in a manner not permitted by the negotiated or declared value of keys as decribed in sec. 6. This was largely the text originally in sec. 6.7. Mike Sent by: ips-bounces@ietf.org To: i-d-announce@ietf.org cc: ips@ietf.org Subject: [Ips] I-D ACTION:draft-ietf-ips-iser-03.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 : iSCSI Extensions for RDMA Specification Author(s) : M. Ko, et al. Filename : draft-ietf-ips-iser-03.txt Pages : 87 Date : 2005-4-1 iSCSI Extensions for RDMA provides the RDMA data transfer capability to iSCSI [iSCSI] by layering iSCSI on top of the Remote Direct Memory Access Protocol (RDMAP). The iWARP protocol suite provides RDMA Read and Write services, which enable data to be transferred directly into SCSI I/O Buffers without intermediate data copies. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ips-iser-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-iser-03.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-iser-03.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. ftp://ftp.ietf.org/internet-drafts/draft-ietf-ips-iser-03.txt _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Tue Apr 12 13:44:57 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19642 for ; Tue, 12 Apr 2005 13:44:56 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLPbF-00005i-Bc for ips-web-archive@ietf.org; Tue, 12 Apr 2005 13:54:57 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLPJY-0008Sn-43; Tue, 12 Apr 2005 13:36:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKvCh-00024J-Su for ips@megatron.ietf.org; Mon, 11 Apr 2005 05:27:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21935 for ; Mon, 11 Apr 2005 04:36:50 -0400 (EDT) Received: from [202.54.64.17] (helo=hclnpd.hclt-ntl.co.in) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKuYx-0000hX-PD for ips@ietf.org; Mon, 11 Apr 2005 04:46:32 -0400 Received: from npd-disclaim.hclt-ntl.co.in (10.105.1.115 [10.105.1.115]) by hclnpd.hclt-ntl.co.in with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id GVHCKGZ0; Mon, 11 Apr 2005 14:06:40 +0530 thread-index: AcU+cZIIOCjQjiZBShumgF42ZUvu2Q== X-MessageTextProcessor: DisclaimIt (2.50.252) [HCL Technologies Ltd., Chennai, India] Received: from npd-mail.hclt-ntl.co.in ([10.105.1.104]) by npd-disclaim.hclt-ntl.co.in with Microsoft SMTPSVC(6.0.2600.2180); Mon, 11 Apr 2005 14:06:35 +0530 Received: by npd-mail.hclt-ntl.co.in with Internet Mail Service (5.5.2657.72) id <2RA3KL47>; Mon, 11 Apr 2005 14:06:35 +0530 Message-ID: <4B1D6623CCBD79489DE28D1CA062A47ED0753F@npd-mail.hclt-ntl.co.in> From: "Prashanth C - NPD, Chennai" To: Content-Transfer-Encoding: 7bit Date: Mon, 11 Apr 2005 14:06:35 +0530 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Content-Class: urn:content-classes:message Importance: normal Priority: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-OriginalArrivalTime: 11 Apr 2005 08:36:35.0154 (UTC) FILETIME=[91FEAB20:01C53E71] X-Spam-Score: 0.3 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 12 Apr 2005 13:36:37 -0400 Subject: [Ips] unh_iscsi.1.5.04 IOL iSCSI target - not responding for the logout request X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Content-Transfer-Encoding: 7bit Hi All, I have downloaded IOL iscsi Target from the www.souceforge.com and the version is 1.5.04, we have HCL iscsi initiator , where i want to do the login phase, during the execution of the login command, ie, i send the login request with security phase and response is fine, i send the login request with operational stage and response is fine, i send the logout request where it is not responding for that logout request. can anyone help on this and i will also contact IOL people. thanks prashanth Disclaimer: This message and any attachment(s) contained here are information that is confidential, proprietary to HCL Technologies and its customers, privileged or otherwise protected by law. The information is solely intended for the individual or the entity it is addressed to. If you are not the intended recipient of this message, you are not authorized to read, forward, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer. _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Wed Apr 20 06:43:32 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOCg8-0001U9-IX; Wed, 20 Apr 2005 06:43:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOCg7-0001Tx-3n for ips@megatron.ietf.org; Wed, 20 Apr 2005 06:43:31 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25034 for ; Wed, 20 Apr 2005 06:43:28 -0400 (EDT) Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOCrJ-0005zW-MS for ips@ietf.org; Wed, 20 Apr 2005 06:55:06 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j3KAhJsr019804 for ; Wed, 20 Apr 2005 05:43:20 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <26JFPLRQ>; Wed, 20 Apr 2005 12:43:18 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15506AD76F2@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "'ravin@lightsand.com'" Date: Wed, 20 Apr 2005 12:43:18 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 2bf730a014b318fd3efd65b39b48818c Cc: "Ipswg \(E-mail\)" Subject: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org I have done a MIB-Doctor review of this draft. Below are my comments. Some are serious, some are mor nits/admin-related. But it would be good to address them and to spin a new rev. Pls do so quickly. Since my last review (rev 5, early Nov 2004) 5 months have gone by. Pls consider the MIB Review Guidelines as per (now approved as BCP) http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-04.txt See also guidelines for security considerations at http://www.ops.ietf.org/mib-security.html The revision 7 does compile clean. But... some of it is just minor admin things, but quite a few are serious. - Top of page 4 Each FCIP Entity managed by this MIB is referred to as a FCIP Instance. The MIB is broken up as follows: I would change both "MIB" occurences into "MIB module". - Section 4 should probably have a statement that it be removed by the RFC-Editor before publication as RFC. - This statement ::= { mib-2 8889 } -- TO BE ASSIGNED by IANA is NOT ALLOWED. One must do a ::= { mib-2 nnn } -- nnnn TO BE ASSIGNED by IANA - The MODULE DESCRIPTION clause states: DESCRIPTION "The module defines management information specific to FCIP devices." So it is missing the mandatory COPYRIGHT statement. It should read: DESCRIPTION "The module defines management information specific to FCIP devices. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC xxxx; see the RFC itself for full legal notices." - The REVISION description says: DESCRIPTION "Initial version of the FCIP MIB module." It would be much better to say: DESCRIPTION "Initial version of the FCIP MIB module, published as RFC xxxx." - The two Textual Conventions are named: FcDomainId and FcEntityMode. I would prefer them to be named fcipDomainId and FcipEntityMode so that we have a more consistent naming convention within the MIB module itself and less risk for future name clashes in other MIB modules. I can see it is kind of consistent with the FcXxx TCs they import from FC-MGMT-MIB, but that fact also explains why there is a potential risk for future name clashes. Oh well, I guess this is what they have chosen. So... - In the FcDomainId TC they talk about FC entity while they talk about FCIP entity in FcEntityMode TC. Is that intentional or just inconsistent? - I see (in FcDomainIdOrZero ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The Domain Id (of a FC swit has been assigned." SYNTAX Integer32 (0..239) While the FcDomainId in this MIB document is: SYNTAX OCTET STRING (SIZE(1)) That is pretty inconsistent between the two MIB modules. This sort of proves my previous point about inconsistencies and/or name clashes right away. - In the DESCRIPTION clause of the read-write object fcipDynIpConfType I would like to see a statement about expected persistency behaviour. In other words, what happens on a restart? - On page 10 I see: REFERENCE "IETF IPS Working Group - draft-ietf-ips-fcovertcpip-12.txt" That makes that internet-draft normative (I think). Just so you know. - I see: fcipEntityId OBJECT-TYPE SYNTAX OCTET STRING (SIZE(8)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The FCIP entity identifier." REFERENCE "IETF IPS Working Group - draft-ietf-ips-fcovertcpip-12.txt" ::= { fcipEntityInstanceEntry 1 } I think it would be good to add a few words to the description clause to explain what the format of such an FCIP entity identifier look like. In fact, maybe it should be a Textual Convention too. - fcipEntityAddress The decription clasue should state that the format of this object is determined by the value of fcipEntityAddressType, as explained in the RFC4001 in the TC DESCRIPTION for the InetAddress TC. Same for fcipLinkLocalFcipEntityAddress and fcipLinkRemFcipEntityAddress maybe others? - Description clause of fcipEntityStatus MUST describe which columns can or cannor be changed if the row in in active state. Same for fcipLinkStatus... maybe others - I am finding various DESCRIPTION clauses pretty meager, for example fcipLinkCost. fcipLinkLocalFcipEntityMode - I find it strange that fcipEntityId is of SYNTAX OCTET STRING (SIZE(8)) while fcipLinkRemFcipEntityId as a SYNTAX Unsigned32 - I cannot find any details of the persistency behaviour for fcipLinkTable !!?? same for fcipStaticRouteTable... and may be others? same for read-write column in fcipDiscoveryDomainTable - Table fcipLinkErrorsTable contains a lot of Counter32 columns. Each of the DESCRIPTION clauses is supposed to describe if there can be discontinuity situations, and if so, which timer is to be used to detect that. - I think the Security COnsiderations section is weak. It lists sensitive objects, but it does not describe much about why they are sensitive and what kind of damage can happen if improperly changed. The security guidelines on www.ops.ietf.org explains how it should be done in an acceptable manenr - I do not see a IANA COnsiderations section, which is mandatory, and specifically so because a MIB OID needs to be assigned. - $ idnits draft-ietf-ips-fcip-mib-07.txt idnits 1.58 draft-ietf-ips-fcip-mib-07.txt: Checking nits according to http://www.ietf.org/ID-Checklist.html : * The document seems to lack an IANA Considerations section. - !! Bad reference -- !MISSING.] P031 L019: [RFC2012} McCloghrie, K., "SNMPv2 MIB for the Transmission Control !! Missing Reference for citation: [RFC2012] P005 L019: Objects relevant to TCP must be obtained from this group [RFC2012]. That is cause by a accolade instead of a square bracket in the reference sect. Also... RFC2012 has now been obsolted by RFC4022. That is what happens if there are long periods between my comments and a ready for re-review. - !! Missing Reference for citation: [FC-MGMT-MIB] P005 L036: be a regular FC interface. As stated in [FC-MGMT-MIB], a regular That reference is indeed missing. Or maybe it intends to point to this: [FCMGMT] McCloghrie, K., "Fibre Channel Management MIB", , February 2003. Then the citation should be changed to 'FCMGMT] And the cirrent revivion of the fcmgmt-mib is revision 6 as in the RFC-Ed queue. - A NORMATIVE reference is needed for every document from which an IMPORT is done. So that means we are missing normative references (and citations somehwere in the text) to: INET-ADDRESS-MIB ... RFC4022 Oh well.... Bert _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Wed Apr 20 10:02:58 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOFn8-0004Ln-Qa; Wed, 20 Apr 2005 10:02:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOFn6-0004LZ-Tx for ips@megatron.ietf.org; Wed, 20 Apr 2005 10:02:57 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10568 for ; Wed, 20 Apr 2005 10:02:55 -0400 (EDT) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOFyL-0003aw-Cf for ips@ietf.org; Wed, 20 Apr 2005 10:14:33 -0400 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 20 Apr 2005 07:02:35 -0700 X-IronPort-AV: i="3.92,116,1112598000"; d="scan'208"; a="252206171:sNHT1205404430" Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j3KE2Whu004923; Wed, 20 Apr 2005 07:02:33 -0700 (PDT) Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id HAA07403; Wed, 20 Apr 2005 07:02:32 -0700 (PDT) From: Keith McCloghrie Message-Id: <200504201402.HAA07403@cisco.com> Subject: Re: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt To: bwijnen@lucent.com ("Wijnen, Bert (Bert)") Date: Wed, 20 Apr 2005 07:02:32 -0700 (PDT) In-Reply-To: from "Wijnen, Bert (Bert)" at Apr 20, 2005 12:43:18 PM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Content-Transfer-Encoding: 7bit Cc: "\"Ipswg \(E-mail\)\"" , "'ravin@lightsand.com'" X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org Hi Bert, > I have done a MIB-Doctor review of this draft. > > Below are my comments. Some are serious, some are > more nits/admin-related. All the nits/admin-related you found appear to be valid. I can respond to a few of the others. > ... > > - In the FcDomainId TC they talk about FC entity while they talk > about FCIP entity in FcEntityMode TC. Is that intentional > or just inconsistent? I think it's intentional. > - I see (in > FcDomainIdOrZero ::= TEXTUAL-CONVENTION > STATUS current > DESCRIPTION > "The Domain Id (of a FC swit > has been assigned." > SYNTAX Integer32 (0..239) > > While the FcDomainId in this MIB document is: > SYNTAX OCTET STRING (SIZE(1)) > That is pretty inconsistent between the two MIB modules. > This sort of proves my previous point about inconsistencies > and/or name clashes right away. While it seems like an "inconsistency", it originates in the Fibre Channel specifications which seem to define a Domain_ID as an integer value stored in a 1-byte field. E.g., in a header for the FSPF (routing) protocol, there is a 4-byte field defined as: Recipient Domain_ID: This field shall specify the Domain_ID of the neighbor Switch. If the neighbor Domain_ID is known, then the Recipient Domain_ID value shall be set to 000000h||Domain_ID. If the neighbor Domain_ID is unknown, then the Recipient Domain_ID value shall be FFFFFFFFh. Valid values for the Domain_ID are: 01h-EFh. The usage of concatenation (000000h||Domain_ID) requires it to be an octet string; having a *range* of values (01h-EFh) requires it to be an integer. So, it's both !! > - On page 10 I see: > REFERENCE > "IETF IPS Working Group - draft-ietf-ips-fcovertcpip-12.txt" > That makes that internet-draft normative (I think). Just so you know. This is now RFC 3821. Keith. _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Wed Apr 20 11:42:56 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOHLs-0001UB-L7; Wed, 20 Apr 2005 11:42:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOHLq-0001RM-Uj for ips@megatron.ietf.org; Wed, 20 Apr 2005 11:42:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21020 for ; Wed, 20 Apr 2005 11:42:52 -0400 (EDT) Received: from hoemail1.lucent.com ([192.11.226.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOHX3-0006w2-9N for ips@ietf.org; Wed, 20 Apr 2005 11:54:32 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j3KFgkZY018862 for ; Wed, 20 Apr 2005 10:42:48 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <26JFP414>; Wed, 20 Apr 2005 17:42:45 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15506AD76FE@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "'Keith McCloghrie'" Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt Date: Wed, 20 Apr 2005 17:42:44 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2 Cc: ips@ietf.org, ravin@lightsand.com X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org Inline > -----Original Message----- > From: Keith McCloghrie [mailto:kzm@cisco.com] > Sent: Wednesday, April 20, 2005 16:03 > To: bwijnen@lucent.com > Cc: ravin@lightsand.com; ips@ietf.org > Subject: Re: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt > > > Hi Bert, > > > I have done a MIB-Doctor review of this draft. > > > > Below are my comments. Some are serious, some are > > more nits/admin-related. > > All the nits/admin-related you found appear to be valid. Good to see that we agree on that. > I can respondto a few of the others. > > > ... > > > > - In the FcDomainId TC they talk about FC entity while they talk > > about FCIP entity in FcEntityMode TC. Is that intentional > > or just inconsistent? > > I think it's intentional. > Mmm... then maybe some additional text in the DESCRIPTION clauses as to what one and the other mean migth be helpfull to readers like myself. > > - I see (in > > FcDomainIdOrZero ::= TEXTUAL-CONVENTION > > STATUS current > > DESCRIPTION > > "The Domain Id (of a FC swit > > has been assigned." > > SYNTAX Integer32 (0..239) > > > > While the FcDomainId in this MIB document is: > > SYNTAX OCTET STRING (SIZE(1)) > > That is pretty inconsistent between the two MIB modules. > > This sort of proves my previous point about inconsistencies > > and/or name clashes right away. > > While it seems like an "inconsistency", it originates in the Fibre > Channel specifications which seem to define a Domain_ID as an integer > value stored in a 1-byte field. E.g., in a header for the > FSPF (routing) > protocol, there is a 4-byte field defined as: > > Recipient Domain_ID: This field shall specify the Domain_ID of the > neighbor Switch. If the neighbor Domain_ID is known, then the > Recipient Domain_ID value shall be set to 000000h||Domain_ID. If > the neighbor Domain_ID is unknown, then the Recipient Domain_ID > value shall be FFFFFFFFh. > > Valid values for the Domain_ID are: 01h-EFh. > > The usage of concatenation (000000h||Domain_ID) requires it > to be an octet > string; having a *range* of values (01h-EFh) requires it to > be an integer. > So, it's both !! > Thanks for the explanation. In such a (intentional case), I would probably the rename the two TCs to FcIntegerDomainIdOrZero and FcStringDomainId or some such. The FcDomainIdOrZero is alread in RFC-Ed queue I believe, so changing that is not easy at this point. Maybe rename the one in this doc to: FcDomainIdInOctetForm ? And add some of the above explanantion to the DESCRIPTION clause? Possibly also add another reference in the REFENCES section for REFERENCE "FC-SW, rev 3.3, 21 October 1997, section 3." I did a quick hunting around on T11 web page, but could not find it yet. I see under FC-SW a cover letter from 1997, but no document. So a (better) ptr to the underlying spec might be very helpfull. > > - On page 10 I see: > > REFERENCE > > "IETF IPS Working Group - draft-ietf-ips-fcovertcpip-12.txt" > > That makes that internet-draft normative (I think). Just > so you know. > > This is now RFC 3821. > OK good, so it can easily be a normative reference then. Would be good to update it with the RFC number. I think that draft name is used at several places! Bert > Keith. > _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Wed Apr 20 12:52:43 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOIRO-0003Op-UK; Wed, 20 Apr 2005 12:52:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOIRM-0003Oh-Ig for ips@megatron.ietf.org; Wed, 20 Apr 2005 12:52:40 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26973 for ; Wed, 20 Apr 2005 12:52:37 -0400 (EDT) Received: from mail98.messagelabs.com ([216.82.244.147]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DOIcc-0000mq-Co for ips@ietf.org; Wed, 20 Apr 2005 13:04:18 -0400 X-VirusChecked: Checked X-Env-Sender: rsnively@Brocade.COM X-Msg-Ref: server-15.tower-98.messagelabs.com!1114015949!14917403!1 X-StarScan-Version: 5.4.11; banners=-,-,- X-Originating-IP: [66.243.153.112] Received: (qmail 25471 invoked from network); 20 Apr 2005 16:52:29 -0000 Received: from f112.brocade.com (HELO discus.brocade.com) (66.243.153.112) by server-15.tower-98.messagelabs.com with SMTP; 20 Apr 2005 16:52:29 -0000 Received: from hq-ex-2.corp.brocade.com (hq-ex-2 [192.168.38.63]) by discus.brocade.com (Postfix) with ESMTP id 56317F326A; Wed, 20 Apr 2005 09:50:24 -0700 (PDT) Received: from hq-ex-6.corp.brocade.com ([192.168.38.36]) by hq-ex-2.corp.brocade.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 20 Apr 2005 09:52:27 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt Date: Wed, 20 Apr 2005 09:52:27 -0700 Message-ID: <66CFE0CA1DDEB54493E63A2C7C52924608D01A@hq-ex-6.brocade.com> Thread-Topic: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt Thread-Index: AcVFv/rd0jP88aYZQrGSZ/xONf2+hwACCJQA From: "Robert Snively" To: "Wijnen, Bert (Bert)" , "Keith McCloghrie" X-OriginalArrivalTime: 20 Apr 2005 16:52:27.0786 (UTC) FILETIME=[55A9C6A0:01C545C9] X-Spam-Score: 0.0 (/) X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c Content-Transfer-Encoding: quoted-printable Cc: ips@ietf.org, ravin@lightsand.com X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org FC-SW, rev 3.3, Oct 1997 is obsolete and has been withdrawn. It was never a standard at that level. It is available from some standards documentation companies. Contact me if you are interested in that particular issue. The present document is INCITS 384:2004, FC-SW-3. By copyright regulations of INCITS, it can be purchased on the INCITS store for $18 per download or $60 for a paper copy. The next revision is FC-SW-4. FC-SW-4 is presently in development and is available in draft form on www.t11.org under the "drafts" button. Robert Snively, Chair INCITS TC T11 Brocade Communications Systems, Inc. 1745 Technology Drive San Jose, CA 95110 +1 408 333 8135 rsnively@brocade.com=20 > -----Original Message----- > From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org]On Behalf Of > Wijnen, Bert (Bert) > Sent: Wednesday, April 20, 2005 8:43 AM > To: 'Keith McCloghrie' > Cc: ips@ietf.org; ravin@lightsand.com > Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt >=20 >=20 > Inline >=20 > > -----Original Message----- > > From: Keith McCloghrie [mailto:kzm@cisco.com] > > Sent: Wednesday, April 20, 2005 16:03 > > To: bwijnen@lucent.com > > Cc: ravin@lightsand.com; ips@ietf.org > > Subject: Re: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt > >=20 > >=20 > > Hi Bert, > >=20 > > > I have done a MIB-Doctor review of this draft. > > >=20 > > > Below are my comments. Some are serious, some are > > > more nits/admin-related. > >=20 > > All the nits/admin-related you found appear to be valid. >=20 > Good to see that we agree on that. >=20 > > I can respondto a few of the others. > >=20 > > > ... > > > > > > - In the FcDomainId TC they talk about FC entity while they talk=20 > > > about FCIP entity in FcEntityMode TC. Is that intentional > > > or just inconsistent? > > =20 > > I think it's intentional. > >=20 > Mmm... then maybe some additional text in the DESCRIPTION clauses as > to what one and the other mean migth be helpfull to readers like=20 > myself. >=20 > > > - I see (in > > > FcDomainIdOrZero ::=3D TEXTUAL-CONVENTION > > > STATUS current > > > DESCRIPTION > > > "The Domain Id (of a FC swit > > > has been assigned." > > > SYNTAX Integer32 (0..239) > > >=20 > > > While the FcDomainId in this MIB document is: > > > SYNTAX OCTET STRING (SIZE(1)) > > > That is pretty inconsistent between the two MIB modules. > > > This sort of proves my previous point about inconsistencies > > > and/or name clashes right away. > > =20 > > While it seems like an "inconsistency", it originates in the Fibre > > Channel specifications which seem to define a Domain_ID as=20 > an integer > > value stored in a 1-byte field. E.g., in a header for the=20 > > FSPF (routing) > > protocol, there is a 4-byte field defined as: > >=20 > > Recipient Domain_ID: This field shall specify the=20 > Domain_ID of the > > neighbor Switch. If the neighbor Domain_ID is known, then the > > Recipient Domain_ID value shall be set to 000000h||Domain_ID. If > > the neighbor Domain_ID is unknown, then the Recipient Domain_ID > > value shall be FFFFFFFFh. > >=20 > > Valid values for the Domain_ID are: 01h-EFh. > >=20 > > The usage of concatenation (000000h||Domain_ID) requires it=20 > > to be an octet > > string; having a *range* of values (01h-EFh) requires it to=20 > > be an integer. > > So, it's both !! =20 > >=20 >=20 > Thanks for the explanation. In such a (intentional case), I would=20 > probably the rename the two TCs to FcIntegerDomainIdOrZero and > FcStringDomainId or some such. The FcDomainIdOrZero is alread > in RFC-Ed queue I believe, so changing that is not easy at this point. > Maybe rename the one in this doc to: FcDomainIdInOctetForm ? > And add some of the above explanantion to the DESCRIPTION clause? > Possibly also add another reference in the REFENCES section for > REFERENCE "FC-SW, rev 3.3, 21 October 1997, section 3." > I did a quick hunting around on T11 web page, but could not find > it yet. I see under FC-SW a cover letter from 1997, but no document. > So a (better) ptr to the underlying spec might be very helpfull. >=20 > > > - On page 10 I see: > > > REFERENCE > > > "IETF IPS Working Group - draft-ietf-ips-fcovertcpip-12.txt" > > > That makes that internet-draft normative (I think). Just=20 > > so you know. > > =20 > > This is now RFC 3821. > >=20 > OK good, so it can easily be a normative reference then. > Would be good to update it with the RFC number. > I think that draft name is used at several places! >=20 > Bert >=20 > > Keith. > >=20 >=20 > _______________________________________________ > Ips mailing list > Ips@ietf.org > https://www1.ietf.org/mailman/listinfo/ips >=20 >=20 _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Wed Apr 20 18:08:15 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DONMl-00032v-H8; Wed, 20 Apr 2005 18:08:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DONMj-00032n-Jh for ips@megatron.ietf.org; Wed, 20 Apr 2005 18:08:13 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27407 for ; Wed, 20 Apr 2005 18:08:11 -0400 (EDT) Received: from ihemail2.lucent.com ([192.11.222.163]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DONY2-0001z6-4P for ips@ietf.org; Wed, 20 Apr 2005 18:19:54 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id j3KM81pX021260 for ; Wed, 20 Apr 2005 17:08:02 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <26JFPZHK>; Thu, 21 Apr 2005 00:08:00 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15506AD7706@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "'Robert Snively'" , "Wijnen, Bert (Bert)" , Keith McCloghrie Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt Date: Thu, 21 Apr 2005 00:07:59 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48 Cc: ips@ietf.org, ravin@lightsand.com X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org Rob, thanks for that information. It raises various questions: - The referenced document (where I supposedly should be able to find underlying explanations of why some objects are defined as they are) is not a current or even a final one. Needs to be fixed I would say - You seem to imply that IETFers who want to review this MIB document and want to understand the underlying technology that they must purchase some other T11 document. Does NOT seem right to me Oh well... something for your WG chairs and Ad to deal with. Bert > -----Original Message----- > From: Robert Snively [mailto:rsnively@Brocade.COM] > Sent: Wednesday, April 20, 2005 18:52 > To: Wijnen, Bert (Bert); Keith McCloghrie > Cc: ips@ietf.org; ravin@lightsand.com > Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt > > > FC-SW, rev 3.3, Oct 1997 is obsolete and has been withdrawn. > It was never a standard at that level. It is available > from some standards documentation companies. Contact me > if you are interested in that particular issue. > > The present document is INCITS 384:2004, FC-SW-3. By > copyright regulations of INCITS, it can be purchased on > the INCITS store for $18 per download or $60 for a paper > copy. The next revision is FC-SW-4. FC-SW-4 is presently > in development and is available in draft form on www.t11.org > under the "drafts" button. > > Robert Snively, Chair INCITS TC T11 > > Brocade Communications Systems, Inc. > 1745 Technology Drive > San Jose, CA 95110 > > +1 408 333 8135 > rsnively@brocade.com > > > > > > -----Original Message----- > > From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org]On Behalf Of > > Wijnen, Bert (Bert) > > Sent: Wednesday, April 20, 2005 8:43 AM > > To: 'Keith McCloghrie' > > Cc: ips@ietf.org; ravin@lightsand.com > > Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt > > > > > > Inline > > > > > -----Original Message----- > > > From: Keith McCloghrie [mailto:kzm@cisco.com] > > > Sent: Wednesday, April 20, 2005 16:03 > > > To: bwijnen@lucent.com > > > Cc: ravin@lightsand.com; ips@ietf.org > > > Subject: Re: [Ips] MIB Doctor review: > draft-ietf-ips-fcip-mib-07.txt > > > > > > > > > Hi Bert, > > > > > > > I have done a MIB-Doctor review of this draft. > > > > > > > > Below are my comments. Some are serious, some are > > > > more nits/admin-related. > > > > > > All the nits/admin-related you found appear to be valid. > > > > Good to see that we agree on that. > > > > > I can respondto a few of the others. > > > > > > > ... > > > > > > > > - In the FcDomainId TC they talk about FC entity while > they talk > > > > about FCIP entity in FcEntityMode TC. Is that intentional > > > > or just inconsistent? > > > > > > I think it's intentional. > > > > > Mmm... then maybe some additional text in the DESCRIPTION clauses as > > to what one and the other mean migth be helpfull to readers like > > myself. > > > > > > - I see (in > > > > FcDomainIdOrZero ::= TEXTUAL-CONVENTION > > > > STATUS current > > > > DESCRIPTION > > > > "The Domain Id (of a FC swit > > > > has been assigned." > > > > SYNTAX Integer32 (0..239) > > > > > > > > While the FcDomainId in this MIB document is: > > > > SYNTAX OCTET STRING (SIZE(1)) > > > > That is pretty inconsistent between the two MIB modules. > > > > This sort of proves my previous point about inconsistencies > > > > and/or name clashes right away. > > > > > > While it seems like an "inconsistency", it originates in the Fibre > > > Channel specifications which seem to define a Domain_ID as > > an integer > > > value stored in a 1-byte field. E.g., in a header for the > > > FSPF (routing) > > > protocol, there is a 4-byte field defined as: > > > > > > Recipient Domain_ID: This field shall specify the > > Domain_ID of the > > > neighbor Switch. If the neighbor Domain_ID is known, then the > > > Recipient Domain_ID value shall be set to > 000000h||Domain_ID. If > > > the neighbor Domain_ID is unknown, then the Recipient > Domain_ID > > > value shall be FFFFFFFFh. > > > > > > Valid values for the Domain_ID are: 01h-EFh. > > > > > > The usage of concatenation (000000h||Domain_ID) requires it > > > to be an octet > > > string; having a *range* of values (01h-EFh) requires it to > > > be an integer. > > > So, it's both !! > > > > > > > Thanks for the explanation. In such a (intentional case), I would > > probably the rename the two TCs to FcIntegerDomainIdOrZero and > > FcStringDomainId or some such. The FcDomainIdOrZero is alread > > in RFC-Ed queue I believe, so changing that is not easy at > this point. > > Maybe rename the one in this doc to: FcDomainIdInOctetForm ? > > And add some of the above explanantion to the DESCRIPTION clause? > > Possibly also add another reference in the REFENCES section for > > REFERENCE "FC-SW, rev 3.3, 21 October 1997, section 3." > > I did a quick hunting around on T11 web page, but could not find > > it yet. I see under FC-SW a cover letter from 1997, but no document. > > So a (better) ptr to the underlying spec might be very helpfull. > > > > > > - On page 10 I see: > > > > REFERENCE > > > > "IETF IPS Working Group - > draft-ietf-ips-fcovertcpip-12.txt" > > > > That makes that internet-draft normative (I think). Just > > > so you know. > > > > > > This is now RFC 3821. > > > > > OK good, so it can easily be a normative reference then. > > Would be good to update it with the RFC number. > > I think that draft name is used at several places! > > > > Bert > > > > > Keith. > > > > > > > _______________________________________________ > > Ips mailing list > > Ips@ietf.org > > https://www1.ietf.org/mailman/listinfo/ips > > > > > _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Fri Apr 22 05:22:25 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOuMi-0005lD-RM; Fri, 22 Apr 2005 05:22:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOuMg-0005l5-Ek for ips@megatron.ietf.org; Fri, 22 Apr 2005 05:22:22 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27834 for ; Fri, 22 Apr 2005 05:22:20 -0400 (EDT) Received: from volter-fw.ser.netvision.net.il ([212.143.107.30] helo=taurus.voltaire.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOuYG-00055V-Uf for ips@ietf.org; Fri, 22 Apr 2005 05:34:22 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Fri, 22 Apr 2005 12:21:33 +0300 Message-ID: Thread-Topic: Negotiating dependent key values Thread-Index: AcVFt4hE2euQAEBNS/OUcfGWU7PmJgBYFScMAAEz+Eo= From: "Erez Zilber" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: quoted-printable Subject: [Ips] Negotiating dependent key values X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org Hi, =20 Some key values that are negotiated in the login phase may be dependent = of other key values. If key value 'A' should be negotiated only if key = value 'B' is negotiated to some value, can they be sent in the same = login message? Should they be sent in different login messages? =20 Thanks =20 Erez Zilber Software Engineer T 972-9-9717689 www.voltaire.com =20 The Grid Interconnect Company _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Fri Apr 22 06:24:11 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOvKV-0005dr-2Y; Fri, 22 Apr 2005 06:24:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOvKT-0005dQ-M3 for ips@megatron.ietf.org; Fri, 22 Apr 2005 06:24:09 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02021 for ; Fri, 22 Apr 2005 06:24:07 -0400 (EDT) Received: from mtagate4.de.ibm.com ([195.212.29.153]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOvW4-0006RI-Bw for ips@ietf.org; Fri, 22 Apr 2005 06:36:09 -0400 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate4.de.ibm.com (8.12.10/8.12.10) with ESMTP id j3MANwWM154562 for ; Fri, 22 Apr 2005 10:23:58 GMT Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com [9.149.165.229]) by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j3MANwYr280522 for ; Fri, 22 Apr 2005 12:23:58 +0200 Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av04.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id j3MANwH4029795 for ; Fri, 22 Apr 2005 12:23:58 +0200 Received: from d12ml102.megacenter.de.ibm.com (d12ml102.megacenter.de.ibm.com [9.149.166.138]) by d12av04.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id j3MANwCi029792; Fri, 22 Apr 2005 12:23:58 +0200 In-Reply-To: To: "Erez Zilber" Subject: Re: [Ips] Negotiating dependent key values MIME-Version: 1.0 X-Mailer: Lotus Notes Build V70_03242005NP March 24, 2005 From: Julian Satran Message-ID: Date: Fri, 22 Apr 2005 13:23:56 +0300 X-MIMETrack: Serialize by Router on D12ML102/12/M/IBM(Release 6.5.1| March 5, 2004) at 22/04/2005 13:23:57, Serialize complete at 22/04/2005 13:23:57 X-Spam-Score: 2.3 (++) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Cc: ips@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1058725307==" Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org --===============1058725307== Content-Type: text/html; charset="US-ASCII"

ips-bounces@ietf.org wrote on 22/04/2005 12:21:33:

> Hi,
>  
> Some key values that are negotiated in the login phase may be
> dependent of other key values. If key value 'A' should be negotiated
> only if key value 'B' is negotiated to some value, can they be sent
> in the same login message? Should they be sent in different login messages?
>  

They can be sent in the same message or in different messages (there is no rule to mandate either form).
Setting the values is meant to be done when everything has been said and there has be no intervening explicit or implicit "reset".

> Thanks
>  
> Erez Zilber
> Software Engineer
> T 972-9-9717689
> www.voltaire.com <http://www.voltaire.com/>
> The Grid Interconnect Company
>
> _______________________________________________
> Ips mailing list
> Ips@ietf.org
> https://www1.ietf.org/mailman/listinfo/ips
 --===============1058725307== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips --===============1058725307==-- From ips-bounces@ietf.org Sun Apr 24 13:35:51 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DPl1L-00013O-2E; Sun, 24 Apr 2005 13:35:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DPl1J-00013D-70 for ips@megatron.ietf.org; Sun, 24 Apr 2005 13:35:49 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06091 for ; Sun, 24 Apr 2005 13:35:46 -0400 (EDT) Message-Id: <200504241735.NAA06091@ietf.org> Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DPlDN-0005Yn-E3 for ips@ietf.org; Sun, 24 Apr 2005 13:48:18 -0400 Received: from localhost ([127.0.0.1] helo=psg.com) by psg.com with esmtp (Exim 4.50 (FreeBSD)) id 1DPl1F-000Lww-Bm; Sun, 24 Apr 2005 17:35:45 +0000 To: "Wijnen, Bert (Bert)" Subject: Re: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt In-Reply-To: Message from "Wijnen, Bert (Bert)" of "Thu, 21 Apr 2005 00:07:59 +0200." <7D5D48D2CAA3D84C813F5B154F43B15506AD7706@nl0006exch001u.nl.lucent.com> Date: Sun, 24 Apr 2005 10:35:44 -0700 From: Allison Mankin X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Cc: ips@ietf.org, Keith McCloghrie , ravin@lightsand.com, 'Robert Snively' X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org Bert, Thanks for calling out several references issue for us, one in an earlier mail. Points 1. The reference to 3821 (FCIP) certainly needs to normative (this is from a different message of yours on the thread). 2. As to the underlying INCITS document being for charge, I think this is something IETF "deals with"? I quickly found my way to RFC 3621, the hubmib WG's Power Ethernet MIB, where IEEE-802.3af is a normative reference, but must be purchased. Same situation, right? 3. We do need Elizabeth as shepherd to manage the sorting out of which INCITS document is to be referenced, and to put in some mention of the fact that work is in progress. Allison > - The referenced document (where I supposedly should be able > to find underlying explanations of why some objects are > defined as they are) is not a current or even a final one. > Needs to be fixed I would say > - You seem to imply that IETFers who want to review this MIB > document and want to understand the underlying technology > that they must purchase some other T11 document. > Does NOT seem right to me > > Oh well... something for your WG chairs and Ad to deal with. _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Sun Apr 24 17:14:33 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DPoQz-0004q3-Kg; Sun, 24 Apr 2005 17:14:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DPoQv-0004pu-SR for ips@megatron.ietf.org; Sun, 24 Apr 2005 17:14:31 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22959 for ; Sun, 24 Apr 2005 17:14:27 -0400 (EDT) Received: from hoemail1.lucent.com ([192.11.226.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DPod2-0007aP-3E for ips@ietf.org; Sun, 24 Apr 2005 17:27:01 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j3OLEP9r010167 for ; Sun, 24 Apr 2005 16:14:26 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <26JFR3X2>; Sun, 24 Apr 2005 23:14:24 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15506AD7745@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "'Allison Mankin'" Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt Date: Sun, 24 Apr 2005 23:14:24 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: ips@ietf.org, Keith McCloghrie , ravin@lightsand.com, 'Robert Snively' X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org W.r.t. > 2. As to the underlying INCITS document being for charge, > I think this is something IETF "deals with"? I quickly > found my way to RFC 3621, the hubmib WG's Power Ethernet MIB, > where IEEE-802.3af is a normative reference, but must be purchased. > Same situation, right? > For most (if not all) IEEE documents that we need to look at during IETF review, the IEEE makes available the underlying document to teh specific WG. Afterwards approval I am not sure if you can still freely get at it. But my concern is that it is often difficult to review if one does not have access to the underlying technology. Specifically if teh DESCRIPTION clauses are not extensive in explaining the exact details but instead a reference to a non-accesible doc is included. > 3. We do need Elizabeth as shepherd to manage the sorting out > of which INCITS document is to be referenced, and to put > in some mention of the fact that work is in progress. > yes please. Bert > Allison > > > - The referenced document (where I supposedly should be able > > to find underlying explanations of why some objects are > > defined as they are) is not a current or even a final one. > > Needs to be fixed I would say > > - You seem to imply that IETFers who want to review this MIB > > document and want to understand the underlying technology > > that they must purchase some other T11 document. > > Does NOT seem right to me > > > > Oh well... something for your WG chairs and Ad to deal with. > _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Sun Apr 24 18:37:56 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DPpjg-0003jE-4l; Sun, 24 Apr 2005 18:37:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DPpje-0003j9-Gc for ips@megatron.ietf.org; Sun, 24 Apr 2005 18:37:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00172 for ; Sun, 24 Apr 2005 18:37:49 -0400 (EDT) Received: from bay106-f35.bay106.hotmail.com ([65.54.161.45] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DPpvh-0002xK-9X for ips@ietf.org; Sun, 24 Apr 2005 18:50:24 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 24 Apr 2005 15:37:39 -0700 Message-ID: Received: from 65.54.161.200 by by106fd.bay106.hotmail.msn.com with HTTP; Sun, 24 Apr 2005 22:37:39 GMT X-Originating-IP: [65.54.161.200] X-Originating-Email: [bernard_aboba@hotmail.com] X-Sender: bernard_aboba@hotmail.com In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B15506AD7745@nl0006exch001u.nl.lucent.com> From: "Bernard Aboba" To: bwijnen@lucent.com, mankin@psg.com Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt Date: Sun, 24 Apr 2005 15:37:39 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 24 Apr 2005 22:37:39.0501 (UTC) FILETIME=[3875ADD0:01C5491E] X-Spam-Score: 0.8 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Cc: ips@ietf.org, kzm@cisco.com, ravin@lightsand.com, rsnively@Brocade.COM X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org >For most (if not all) IEEE documents that we need to look at during IETF >review, the IEEE makes available the underlying document to the specific >WG. Indeed, we have a letter from the chair of IEEE 802 to this effect. >Afterwards approval I am not sure if you can still freely get at it. All IEEE 802 standards more than 12 months old are available for free download on the Web via the "Get IEEE 802 program". _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Mon Apr 25 05:20:12 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DPzlD-0000m5-6X; Mon, 25 Apr 2005 05:20:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DPzl8-0000l6-VW for ips@megatron.ietf.org; Mon, 25 Apr 2005 05:20:09 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27634 for ; Mon, 25 Apr 2005 05:20:04 -0400 (EDT) Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DPzxL-0006hX-FB for ips@ietf.org; Mon, 25 Apr 2005 05:32:44 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j3P9JsPm026098 for ; Mon, 25 Apr 2005 04:19:55 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <26JFRVNV>; Mon, 25 Apr 2005 11:19:53 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15506AD774C@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "'Bernard Aboba'" , mankin@psg.com Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt Date: Mon, 25 Apr 2005 11:19:52 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 1.0 (+) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: ips@ietf.org, kzm@cisco.com, ravin@lightsand.com, rsnively@Brocade.COM X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org > All IEEE 802 standards more than 12 months old are available for free > download on the Web via the "Get IEEE 802 program". > Even better these days, on page http://standards.ieee.org/getieee802/ I now see: The Get IEEE 802R program makes IEEE 802R standards available at no charge in PDF format thanks to the sponsors listed to the right. This program grants public access to view and download current individual IEEE Local and Metropolitan Area Network standards at no charge. - New IEEE 802R standards are included in the program after they have been published in PDF for six months. So already after 6 months! Bert _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Tue Apr 26 09:32:08 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQQAa-0006aG-3x; Tue, 26 Apr 2005 09:32:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQQAY-0006a8-FQ for ips@megatron.ietf.org; Tue, 26 Apr 2005 09:32:06 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07911 for ; Tue, 26 Apr 2005 09:32:05 -0400 (EDT) Received: from [217.29.142.34] (helo=ntserver.Enppi-mail.corp) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQQMx-0004H2-FL for ips@ietf.org; Tue, 26 Apr 2005 09:44:59 -0400 Content-Class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 26 Apr 2005 15:31:47 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Message-ID: Thread-Topic: Virtualied Labs Thread-Index: AcVKY9pVjHHqO/+6SOS3qpub6amtWg== From: "Mohammed Awad" To: X-Spam-Score: 0.1 (/) X-Scan-Signature: 21be852dc93f0971708678c18d38c096 Subject: [Ips] Virtualied Labs X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1330332854==" Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org This is a multi-part message in MIME format. --===============1330332854== Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C54A64.4B8C19A8" This is a multi-part message in MIME format. ------_=_NextPart_001_01C54A64.4B8C19A8 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear All, =20 I'm a new member here. The main reason I'm here is that I intend to select the IP storage as my new PhD subject which I'm preparing nowadays. Unfortunately, in our university we don't have adequately furnished labs. So before I go forth and make the choice, could anybody tell me whether there exists some software or tools that can adequately virtualize networked storage environments so that I can do the experiments and test benchmarks without the need for real labs. =20 Thanks Mohammad Awad. ------_=_NextPart_001_01C54A64.4B8C19A8 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear All,

 

I’m a new member here. The main reason = I’m here is that I intend to select the IP storage as my new PhD subject which = I’m preparing nowadays. Unfortunately, in our university we don’t have = adequately furnished labs. So before I go forth and make the choice, could anybody = tell me whether there exists some software or tools that can adequately virtualize networked storage environments so that = I can do the experiments and test benchmarks without the need for real = labs.

 

Thanks

Mohammad Awad.

=00 ------_=_NextPart_001_01C54A64.4B8C19A8-- --===============1330332854== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips --===============1330332854==-- From ips-bounces@ietf.org Wed Apr 27 14:27:26 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQrFu-0003y7-Ub; Wed, 27 Apr 2005 14:27:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQrFs-0003y2-ND for ips@megatron.ietf.org; Wed, 27 Apr 2005 14:27:25 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09168 for ; Wed, 27 Apr 2005 14:27:23 -0400 (EDT) From: pat_thaler@agilent.com Received: from msgbas1x.cos.agilent.com ([192.25.240.36]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQrSX-0002gh-Dv for ips@ietf.org; Wed, 27 Apr 2005 14:40:32 -0400 Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 7472E2381B for ; Wed, 27 Apr 2005 12:27:09 -0600 (MDT) Received: from wcosvs02.cos.agilent.com (wcosvs02.cos.agilent.com [130.29.152.188]) by relcos1.cos.agilent.com (Postfix) with ESMTP id 522154C5 for ; Wed, 27 Apr 2005 12:27:09 -0600 (MDT) Received: from wcosbh22.cos.agilent.com ([130.29.152.178]) by wcosvs02.cos.agilent.com with InterScan Messaging Security Suite; Wed, 27 Apr 2005 12:27:07 -0600 Received: from wcosmb05.cos.agilent.com ([130.29.152.72]) by wcosbh22.cos.agilent.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 27 Apr 2005 12:27:07 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt Date: Wed, 27 Apr 2005 12:27:06 -0600 Message-ID: <9418406DEC3B8A4BBDB1B87291D851AF0E7681@wcosmb05.cos.agilent.com> Thread-Topic: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt Thread-Index: AcVJHpmeGzZvAeQLQ26GTl+An6w3LgCN2UZA To: , , X-OriginalArrivalTime: 27 Apr 2005 18:27:07.0052 (UTC) FILETIME=[B7A93EC0:01C54B56] X-Spam-Score: 0.3 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Content-Transfer-Encoding: quoted-printable Cc: ips@ietf.org, kzm@cisco.com, ravin@lightsand.com, rsnively@Brocade.COM X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org Actually, the delay for Get IEEE 802 is six months after publication = rather than 12. Pat Thaler -----Original Message----- From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org]On Behalf Of Bernard Aboba Sent: Sunday, 24 April, 2005 3:38 PM To: bwijnen@lucent.com; mankin@psg.com Cc: ips@ietf.org; kzm@cisco.com; ravin@lightsand.com; rsnively@Brocade.COM Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt >For most (if not all) IEEE documents that we need to look at during = IETF >review, the IEEE makes available the underlying document to the = specific >WG. Indeed, we have a letter from the chair of IEEE 802 to this effect. >Afterwards approval I am not sure if you can still freely get at it. All IEEE 802 standards more than 12 months old are available for free=20 download on the Web via the "Get IEEE 802 program". _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Wed Apr 27 15:07:25 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQrsb-00030Z-0C; Wed, 27 Apr 2005 15:07:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQrsZ-00030U-5M for ips@megatron.ietf.org; Wed, 27 Apr 2005 15:07:23 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13416 for ; Wed, 27 Apr 2005 15:07:21 -0400 (EDT) From: pat_thaler@agilent.com Received: from msgbas9x.lvld.agilent.com ([192.25.144.41]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQs5G-0003df-8y for ips@ietf.org; Wed, 27 Apr 2005 15:20:31 -0400 Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas9x.lvld.agilent.com (Postfix) with ESMTP id D11CC2820 for ; Wed, 27 Apr 2005 13:07:10 -0600 (MDT) Received: from wcosvs03.cos.agilent.com (wcosvs03.cos.agilent.com [130.29.152.233]) by relcos1.cos.agilent.com (Postfix) with ESMTP id A44A6130 for ; Wed, 27 Apr 2005 13:07:10 -0600 (MDT) Received: from wcosbh22.cos.agilent.com ([130.29.152.178]) by wcosvs03.cos.agilent.com with InterScan Messaging Security Suite; Wed, 27 Apr 2005 13:07:06 -0600 Received: from wcosmb05.cos.agilent.com ([130.29.152.72]) by wcosbh22.cos.agilent.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 27 Apr 2005 13:07:06 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt Date: Wed, 27 Apr 2005 13:07:06 -0600 Message-ID: <9418406DEC3B8A4BBDB1B87291D851AF0E7682@wcosmb05.cos.agilent.com> Thread-Topic: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt Thread-Index: AcVJHpmeGzZvAeQLQ26GTl+An6w3LgCOoWGg To: , , X-OriginalArrivalTime: 27 Apr 2005 19:07:06.0614 (UTC) FILETIME=[4DE95960:01C54B5C] X-Spam-Score: 0.3 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Content-Transfer-Encoding: quoted-printable Cc: ips@ietf.org, kzm@cisco.com, ravin@lightsand.com, rsnively@Brocade.COM X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org I'm happy we are able to currently make IEEE 802 documents freely = available through the Get IEEE 802 (R) program. However, I don't think = free availability of referenced documents to users of IETF standards is = relevant from the point of view of IETF policy with regard to = referencing documents. At the time the first IEEE 802 related MIB work was done in IETF, Get = IEEE 802 did not exist and the documents had to be bought (perhaps on = paper even - how primitive). The program is currently available through = the sponsorship of IEEE 802, Wi-Fi Alliance and Cisco. As far as I know, = within IEEE, only IEEE 802 standards have such a program. Continued = availability of the program is subject to periodic review.=20 Free document availability of references for reviewers is another = matter. Regards, Pat Thaler IEEE 802 Vice Chair -----Original Message----- From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org]On Behalf Of Bernard Aboba Sent: Sunday, 24 April, 2005 3:38 PM To: bwijnen@lucent.com; mankin@psg.com Cc: ips@ietf.org; kzm@cisco.com; ravin@lightsand.com; rsnively@Brocade.COM Subject: RE: [Ips] MIB Doctor review: draft-ietf-ips-fcip-mib-07.txt >For most (if not all) IEEE documents that we need to look at during = IETF >review, the IEEE makes available the underlying document to the = specific >WG. Indeed, we have a letter from the chair of IEEE 802 to this effect. >Afterwards approval I am not sure if you can still freely get at it. All IEEE 802 standards more than 12 months old are available for free=20 download on the Web via the "Get IEEE 802 program". _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Wed Apr 27 23:43:50 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQzwM-00068F-4n; Wed, 27 Apr 2005 23:43:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQzwK-00068A-Ma for ips@megatron.ietf.org; Wed, 27 Apr 2005 23:43:48 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06821 for ; Wed, 27 Apr 2005 23:43:46 -0400 (EDT) Received: from [217.29.142.34] (helo=ntserver.Enppi-mail.corp) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DR096-0004T9-7l for ips@ietf.org; Wed, 27 Apr 2005 23:57:01 -0400 Content-Class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Ips] Virtualied Labs X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Thu, 28 Apr 2005 05:43:35 +0200 Message-ID: Thread-Topic: [Ips] Virtualied Labs Thread-Index: AcVKY9pVjHHqO/+6SOS3qpub6amtWgAA6UcAACLFMEAADioHIAAd9giR From: "Mohammed Awad" To: "Aggarwal, Vikas (OFT)" X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Cc: ips@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0140443662==" Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org --===============0140443662== Content-Class: urn:content-classes:message Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 RGVhciBWaWthcywNCiANCllvdXIgb2ZmZXIgdG8gaGVscCBpcyB2ZXJ5IGtpbmQgb2YgeW91LiBJ IGZlZWwgdGhhdCB5b3UgYXJlIGdvaW5nIHRvIGJlIG9mIGdyZWF0IGltcG9ydGFuY2UgdG8gbWUg c2luY2UgeW91ciBleHBlcnRpc2UgbGllcyBleGFjdGx5IHdpdGhpbiBteSBzY29wZSBvZiBpbnRl cmVzdC4gSSdsbCBiZSBnbGFkIGlmIHlvdSB5b3UgY291bGQgaGF2ZSB0aGUgdGltZSB0byBhbnN3 ZXIgdGhlc2UgcXVlc3Rpb24gZm9yIG1lOg0KLSBEbyB5b3UgdGhpbmsgdGhhIEZDSVAgd2lsbCB0 YWtlIG92ZXIgaVNDU0kgaW4gdGhlIG5leHQgY291cGxlIG9mIHllYXJzLiBJbiBvdGhlciB3b3Jk cywgZG8geW91IHRoaW5rIHRoYXQgaVNDU0kgaXMgYWJvdXQgdG8gYmUgYW4gb2xkIGZhc2hpb24g YW5kIHRoZXJlZm9yZSBJIGJldHRlciB0cnkgdG8gZG8gbXkgcmVzZWFyY2ggd2l0aCB0aGUgRkNJ UD8NCiANClRoYW5rcywNCk1vaGFtbWFkDQogICANCg0KCS0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t LS0tIA0KCUZyb206IEFnZ2Fyd2FsLCBWaWthcyAoT0ZUKSBbbWFpbHRvOlZpa2FzLkFnZ2Fyd2Fs QG9mdC5zdGF0ZS5ueS51c10gDQoJU2VudDogV2VkIDQvMjcvMjAwNSAzOjE3IFBNIA0KCVRvOiBN b2hhbW1lZCBBd2FkIA0KCUNjOiANCglTdWJqZWN0OiBSRTogW0lwc10gVmlydHVhbGllZCBMYWJz DQoJDQoJDQoNCglJIHd1ZCBiZSBpbnRlcmVzdGVkIGluIG1heSBiZSBoZWxwaW5nIG91dCBvciBs ZWFybmluaW5nIGp1c3QgZm9yIGZ1bi4NCg0KCUFzIEkgYW0gd29ya2luZyBvbiBYRU4gYW5kIHdv cmtlZCBvbiBTdG9yYWdlIGZpYnJlIGNoYW5uZWwgIGFuZCBsaXR0bGUgYml0IG9uIGlzY3NpLWxp bnV4Lg0KDQoJU29tZSBwZW9wbGUgYXJlIGRldmVsb3Bpbmcgb3BlbiBzb3VyY2UgaXNjc2kgZGlz ayBhcnJheSBlbnRlcnByaXNlLg0KDQoJIA0KDQoJLXZpa2FzDQoNCgkgDQoNCgkNCiAgX19fX18g IA0KDQoNCglGcm9tOiBNb2hhbW1lZCBBd2FkIFttYWlsdG86TUF3YWRARW5wcGkuY29tXSANCglT ZW50OiBXZWRuZXNkYXksIEFwcmlsIDI3LCAyMDA1IDI6MzQgQU0NCglUbzogQWdnYXJ3YWwsIFZp a2FzIChPRlQpDQoJU3ViamVjdDogUkU6IFtJcHNdIFZpcnR1YWxpZWQgTGFicw0KDQoJIA0KDQoJ VGhhbmtzIGEgbG90Lg0KDQoJIA0KDQoJUmVnYXJkcywNCg0KCU1vaGFtbWFkDQoNCgkgDQoNCgkt LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KCUZyb206IEFnZ2Fyd2FsLCBWaWthcyAoT0ZUKSBb bWFpbHRvOlZpa2FzLkFnZ2Fyd2FsQG9mdC5zdGF0ZS5ueS51c10gDQoJU2VudDogVHVlc2RheSwg QXByaWwgMjYsIDIwMDUgMzo1NiBQTQ0KCVRvOiBNb2hhbW1lZCBBd2FkDQoJU3ViamVjdDogUkU6 IFtJcHNdIFZpcnR1YWxpZWQgTGFicw0KDQoJIA0KDQoJMS4gICAgICAgVm13YXJlIC4gdSBoYXZl IHRvIHBheSAxNTAkIHBlciBsaWNlbnNlDQoNCgkyLiAgICAgICBmcmVlIHZpcnR1YWxpemF0aW9u IHByb2R1Y3Q6Ojo6ICB3d3cueGVuc291cmNlLmNvbSA8aHR0cDovL3d3dy54ZW5zb3VyY2UuY29t Lz4gIC4gVSBjYW4gZXhwcmVtaWVudCB3aXRoIGxpbnV4IA0KDQoJIA0KDQoJDQogIF9fX19fICAN Cg0KDQoJRnJvbTogaXBzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzppcHMtYm91bmNlc0BpZXRm Lm9yZ10gT24gQmVoYWxmIE9mIE1vaGFtbWVkIEF3YWQNCglTZW50OiBUdWVzZGF5LCBBcHJpbCAy NiwgMjAwNSA5OjMyIEFNDQoJVG86IGlwc0BpZXRmLm9yZw0KCVN1YmplY3Q6IFtJcHNdIFZpcnR1 YWxpZWQgTGFicw0KDQoJIA0KDQoJRGVhciBBbGwsDQoNCgkgDQoNCglJ4oCZbSBhIG5ldyBtZW1i ZXIgaGVyZS4gVGhlIG1haW4gcmVhc29uIEnigJltIGhlcmUgaXMgdGhhdCBJIGludGVuZCB0byBz ZWxlY3QgdGhlIElQIHN0b3JhZ2UgYXMgbXkgbmV3IFBoRCBzdWJqZWN0IHdoaWNoIEnigJltIHBy ZXBhcmluZyBub3dhZGF5cy4gVW5mb3J0dW5hdGVseSwgaW4gb3VyIHVuaXZlcnNpdHkgd2UgZG9u 4oCZdCBoYXZlIGFkZXF1YXRlbHkgZnVybmlzaGVkIGxhYnMuIFNvIGJlZm9yZSBJIGdvIGZvcnRo IGFuZCBtYWtlIHRoZSBjaG9pY2UsIGNvdWxkIGFueWJvZHkgdGVsbCBtZSB3aGV0aGVyIHRoZXJl IGV4aXN0cyBzb21lIHNvZnR3YXJlIG9yIHRvb2xzIHRoYXQgY2FuIGFkZXF1YXRlbHkgdmlydHVh bGl6ZSBuZXR3b3JrZWQgc3RvcmFnZSBlbnZpcm9ubWVudHMgc28gdGhhdCBJIGNhbiBkbyB0aGUg ZXhwZXJpbWVudHMgYW5kIHRlc3QgYmVuY2htYXJrcyB3aXRob3V0IHRoZSBuZWVkIGZvciByZWFs IGxhYnMuDQoNCgkgDQoNCglUaGFua3MNCg0KCU1vaGFtbWFkIEF3YWQuDQoNCg== --===============0140443662== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips --===============0140443662==-- From ips-bounces@ietf.org Thu Apr 28 04:25:44 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DR4L9-00046R-Da; Thu, 28 Apr 2005 04:25:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DR4L3-000464-7c for ips@megatron.ietf.org; Thu, 28 Apr 2005 04:25:37 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23043 for ; Thu, 28 Apr 2005 04:25:35 -0400 (EDT) Received: from mtagate2.de.ibm.com ([195.212.29.151]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DR4Xr-00076R-60 for ips@ietf.org; Thu, 28 Apr 2005 04:38:52 -0400 Received: from d12nrmr1707.megacenter.de.ibm.com (d12nrmr1707.megacenter.de.ibm.com [9.149.167.81]) by mtagate2.de.ibm.com (8.12.10/8.12.10) with ESMTP id j3S8PP5a181564 for ; Thu, 28 Apr 2005 08:25:25 GMT Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228]) by d12nrmr1707.megacenter.de.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j3S8PPRm278206 for ; Thu, 28 Apr 2005 10:25:25 +0200 Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av02.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id j3S8PPan003329 for ; Thu, 28 Apr 2005 10:25:25 +0200 Received: from d12ml102.megacenter.de.ibm.com (d12ml102.megacenter.de.ibm.com [9.149.166.138]) by d12av02.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id j3S8PPl7003323; Thu, 28 Apr 2005 10:25:25 +0200 In-Reply-To: <426FFF52.CABA618F@emc.com> To: ips@ietf.org MIME-Version: 1.0 X-Mailer: Lotus Notes Build V70_04212005NP April 21, 2005 From: Julian Satran Message-ID: Date: Thu, 28 Apr 2005 11:25:23 +0300 X-MIMETrack: Serialize by Router on D12ML102/12/M/IBM(Release 6.5.1| March 5, 2004) at 28/04/2005 11:25:25, Serialize complete at 28/04/2005 11:25:25 X-Spam-Score: 1.8 (+) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Cc: "Conway, Bill" , Sorin Faibish , Black_David@emc.com, "tao, qin" Subject: [Ips] Re: iscsi + REPORT LUNS + overflow question X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1499398055==" Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org --===============1499398055== Content-Type: text/html; charset="US-ASCII"
Dear All,

A question was raised recently regarding (again) the use of the Overrun or Underrun bits in iSCSI.
An iSCSI target is supposed to report an Overrun or Underrun only if there is a mismatch between the Expected-Data-Length and the data length derived by the SCSI target from the data presented in the CDB and the actual data.  In the case of a Report LUNs the Allocated Length is part of the CDB and as long as the Expected-Data-Length matches the Allocated-Data-Length and the target transferred the number of bytes indicated neither Overrun nor Underrun should be set. If target would have transferred less data than the Expected-Data-Length (either because EDL is larger that ADL or because the actual data sent is less than EDL) the Underrun bit must be set (and the value computed). If the target attempts to send more data than EDL (either because EDL is lower than ADL or the target SCSI is bad and attempts to send more than ADL) the Overrun bit must be set (and the overrun value computed).

An ADL lower or higher than the actual list length is not considered an exception according to SCSI (SPC2 and 3).
Note that if EDL is larger than ADL you can have an underrun and an incomplete list and in the case of EDL lower than ADL you can have an overrun and an incomplete list.
A good implementation should set EDL = ADL.

Julo --===============1499398055== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips --===============1499398055==-- From ips-bounces@ietf.org Thu Apr 28 10:04:08 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DR9ce-0003HB-Bd; Thu, 28 Apr 2005 10:04:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DR9cd-0003H6-7I for ips@megatron.ietf.org; Thu, 28 Apr 2005 10:04:07 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17247 for ; Thu, 28 Apr 2005 10:04:05 -0400 (EDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DR9pU-0003ke-Ar for ips@ietf.org; Thu, 28 Apr 2005 10:17:25 -0400 Received: from phys-giza-1 ([129.147.4.102]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id j3SE44i7012761 for ; Thu, 28 Apr 2005 08:04:04 -0600 (MDT) Received: from conversion-daemon.giza-mail1.Central.Sun.COM by giza-mail1.Central.Sun.COM (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0IFN00H01TNV17@giza-mail1.Central.Sun.COM> (original mail from David.Weibel@Sun.COM) for ips@ietf.org; Thu, 28 Apr 2005 08:04:04 -0600 (MDT) Received: from [172.20.56.104] (batara.Central.Sun.COM [172.20.56.104]) by giza-mail1.Central.Sun.COM (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTP id <0IFN00KY5TQGAB@giza-mail1.Central.Sun.COM> for ips@ietf.org; Thu, 28 Apr 2005 08:03:52 -0600 (MDT) Date: Thu, 28 Apr 2005 08:04:05 -0600 From: David Weibel To: ips@ietf.org Message-id: MIME-version: 1.0 (Apple Message framework v622) X-Mailer: Apple Mail (2.622) Content-type: text/plain; charset=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-Spam-Score: 0.0 (/) X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574 Content-Transfer-Encoding: 7BIT Subject: [Ips] iSCSI Targets with 802.3ad support? X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org Are any targets vendors going to support 802.3ad? Please respond directly or on the alias. Thanks -David _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips