[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NetConf should fully exploit BEEP's rich features


A few remarks:
- can you send (or point me to) the RFC-Editor note about that?

Please see below.

- pls realize that we talk about "transport" in our WG charter as well.

Yes, this is what Bob might call "pollution". Again, see below.

- Maybe it should be: Application Requirements on the Transport Protocol

The point is that we are really not discussing a transport protocol, per se. We're discussing requirements for the protocol that runs on top of the transport protocol. Some people call that the application protocol. Layering is a pain, sometimes.


In any event, the doc talks a lot about pure thansport issues, does it not?

Yes, and it will probably need a clean up, if you agree that this is an issue. And it's clearly caused someone other than Bob confusion, so his comment below might well be applicable.


Bert


Eliot


From: Bob Braden <braden@ISI.EDU>
Date: Tue, 11 Feb 2003 23:48:12 GMT
Message-Id: <200302112348.XAA03474@gra.isi.edu>
To: sob@harvard.edu, mankin@psg.com
Subject: Re: Protocol Action: iSCSI to Proposed Standard
Cc: ips@ece.cmu.edu, ietf@ietf.org

*> *> The IESG has approved publishing the following Internet-Draft
*> as a Proposed Standard:
*> *> o iSCSI <draft-ietf-ips-iscsi-20.txt>
*> *> This document is the product of the IP Storage Working Group.
*> *> The IESG contact persons are Allison Mankin and Scott Bradner.
*> *> *> Technical Summary
*> *> The Small Computer Systems Interface (SCSI) is a family of
*> protocols for communicating with I/O devices, especially storage
*> devices. SCSI is a client-server architecture. The SCSI protocol
*> has been mapped over various transports, including Parallel SCSI,

Transports?

The Webster's New Collegiate Dictionary defines the noun "transport" as
"strong and often intensely pleasurable emotion".  ;-)

All the Internet documentation with which I am familiar, as well as the
OSI reference model, define a "transport layer", but I don't think you
are suggesting SCSI over IP, etc.

Can't we please resist terminology pollution?  In the IETF we call these
[data] link layers.

Bob Braden

*> IPI, IEEE-1394 (firewire) and Fibre Channel. These transports are
*> I/O specific and have limited distance capabilities. The iSCSI
*> protocol defined in draft-ietf-ips-iscsi describes a means of
*> transporting of the SCSI packets over TCP/IP, providing for an
*> interoperable solution which can take advantage of existing
*> Internet infrastructure, Internet management facilities and
*> address distance limitations. Mapping over TCP ensures that the
*> high volume storage transfers use congestion control.
*> *> 




--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>