Re: iSCSI: More on naming and discovery

[csapuntz@cisco.com]

> -- CONNECT and target naming
> 
> One thing to keep in mind is that there are traffic
> analysis tools and both current and forthcoming
> implementations of QoS that understand TCP ports.
> If every iSCSI target has its own <IP address, TCP
> port>, these tools work and can differentiate the
> iSCSI targets without any further enhancements.
> If multiple iSCSI targets are behind a common
> <IP address, TCP port> pair, these tools will
> not be able to separate out traffic to the 
> targets for different analysis or QoS treatment
> without iSCSI-specific enhancements, although
> they can do so based on different source addresses.  

David,

I think we can address this QoS concern by adding an optional port
number to the target name. For example,

10.3.4.2:7032/db1

or

oracle:7032/db1

where 7032 is the port.

We have to be careful about the choice of delimiter. The :
is used by IPv6.

-Costa