Re: iSCSI: Last call issues for the Naming and Discovery document

[Mark Bakke <mbakke@cisco.com>]

Marjorie-

Thanks for the detailed comments.  I've embedded my responses below.

--
Mark

> "KRUEGER,MARJORIE (HP-Roseville,ex1)" wrote:
> 
> Some cleanup items for the iSCSI Naming and Discovery document:
> 
> 1) Sec.1 p.5 and p. 14 define "iSCSI Address" but contradict each other.  p. 5 defines it as
> simply and IP address [& port] and p. 14 says it's the iSCSI name and IP addr [+port].  Paragraph
> 5 needs to be modified to match p. 14.

How about (page 5):

   iSCSI nodes also have addresses. An iSCSI address specifies a single
   path to an iSCSI node and consists of the iSCSI name, plus a transport
   (TCP) address which uses the following format:

      <domain-name>[:<port>]

   Where <domain-name> is one of:




> 
> 2) Sec. 1 p. 17 says
> 
> In this example, Robert's SSN is like the iSCSI Name, his phone number and addresses are analogous
> to the TCP addresses which make up an iSCSI session, and "Robert Smith" would be a human-friendly
> label for this person.
> The statement that Robert Smith's addresses are like an iSCSI session makes no sense to me.  An
> iSCSI session is a relationship between two separate iSCSI nodes.  Robert's addresses are only one
> end of the relationship.  Perhaps this paragraph means to say his phone number, etc. are like an
> iSCSI nodes TCP addresses?

You're right; that's what I had meant.  I'll fix the wording.

> 
> 3) Sec. 1.1 p. 1 first sentence "iSCSI has given the Organizational naming authority additional
> flexibility by permitting it to hand out local naming authority to
>    subordinate organizations."
> 
> I suggest changing this to "The iSCSI naming scheme was constructed to give an organizational
> naming authority the flexibility to further subdivide the responsibility for name creation to
> subordinate naming authorities."  Use of "capital O" in Organization implies there's some globally
> defined naming authority that this sentence is referring to.
> 
> 4) General comment on section 1.1  To reflect the definition in the iSCSI main draft, sec.
> 2.2.6.3.2,  either the examples need to be changed to show the ":" after the reversed domain name
> in the string, or the text needs to be changed to say that these substrings are sub-domain names.
> 
> 5)sec. 1.1, p 15 - this example is missing the ":" following the reversed domain name.
> 
> 6)sec. 3, p 1 - the last sentence is missing something.  It's "Moreover, iSCSI discovery
> mechanism only deals with target discovery and one still needs to use  the SCSI protocol for LUN
> discovery." and should be "Moreover, the iSCSI discovery  mechanisms listed here only deal with
> target discovery and one still needs to use the SCSI protocol for LUN discovery."
> 
> 7) sec. 3 p 2 - 2nd sentence is missing something. It's "The goal of iSCSI discovery mechanism is
> to provide low overhead support for small iSCSI setups, and scalable discovery solutions for large
> enterprise setups." and should be "The goal of iSCSI discovery  mechanisms are to provide low
> overhead support for small iSCSI setups, and scalable discovery solutions for large enterprise
> setups."
> 
> 8) sec. 3, p 5  the sentence "This mechanism assumes that the IP address and TCP port information
> are already available to the initiator." is missing something, should be "This mechanism assumes
> that the target's IP address and TCP port information are already available to the initiator."
> 
> 9) appendix B.3, I think there's a typo in the first sentence.  "This gateway presents logical
> targets (iSCSI Names) to the initiators, and maps them to real iSCSI targets as it chooses."
> should be "This gateway presents logical targets (iSCSI Names) to the initiators, and maps them to
> SCSI targets as it chooses."
> 
> 10)  appendix B.4 another typo?  "An iSCSI proxy is a SCSI gateway..." should be "An iSCSI proxy
> is an iSCSI gateway.."
> 
> 11) appendix B.5, p 4 refers to a "DMZ"  There is no definition of this term in this document.
> Needs to either be defined or substitute some more descriptive phrase here.
> 
> 
> Regards,
> 
> Marjorie Krueger
> Networked Storage Architecture
> Networked Storage Solutions
> Hewlett-Packard

-- 
Mark A. Bakke
Cisco Systems
mbakke@cisco.com
763.398.1054