Return-Path: <owner-ips@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips@ece.cmu.edu>
Received: (from majordom@localhost)
	by ece.cmu.edu (8.11.0/8.10.2) id h1E6HqP18026
	for ips-outgoing; Fri, 14 Feb 2003 01:17:52 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from gnat.inet.org (gnat.inet.org [63.108.254.91])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h1DGQYW00642
	for <ips@ece.cmu.edu>; Thu, 13 Feb 2003 11:26:34 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id 6BB4867119; Thu, 13 Feb 2003 11:37:36 -0500 (EST)
Date: Thu, 13 Feb 2003 11:26:06 -0500
Subject: Re: Protocol Action: iSCSI to Proposed Standard
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: "Bob Braden" <braden@ISI.EDU>, <sob@harvard.edu>, <mankin@psg.com>,
   <ips@ece.cmu.edu>, <ietf@ietf.org>
To: "Mallikarjun C." <cbm@rose.hp.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <00e901c2d2cd$d713e890$2cb2e40f@rose.hp.com>
Message-Id: <DA313C24-3F6F-11D7-9068-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Sender: owner-ips@ece.cmu.edu
Precedence: bulk


On Wednesday, Feb 12, 2003, at 13:24 America/Montreal, Mallikarjun C. 
wrote:

>> All the Internet documentation with which I am familiar, as well as 
>> the
>
> I think we have a case of overlapping vocabulary from two different 
> domains.
>
> Per SCSI Architecture Model (SAM-2, SAM-3), iSCSI is very clearly
> a "SCSI transport protocol" (as opposed to a SCSI application layer 
> protocol).
> Parallel SCSI, Fibre Channel etc. are all "SCSI transports" per SCSI 
> conventions.
> That is all the critiqued abstract is trying to describe.

In the context of an *Internet* RFC, it seems sensible to use the normal
Internet terminology -- unless one very very clearly indicates that a
term is being used in some different semantic.  One might postulate that
the document's editors and RFC-Editor could work out a mutually 
agreeable
editorial change here to add clarity.

Ran
