|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: FCIP SOF and EOF CodesSrini, FCIP is used to connect SAN islands through the IP network. The connection points of FCIP devices to the SAN islands are at a type of FC fabric port called B-port. B-port is specified in the FC-BB document. B ports send and receive byte encoded SOF and EOF and not the 4-byte ordered sets that are present on the FC links. Vi > -----Original Message----- > From: Srini V.Raman [mailto:sraman@platys.com] > Sent: Tuesday, December 12, 2000 10:25 AM > To: ips@ece.cmu.edu > Subject: FCIP SOF and EOF Codes > > > > For an FCIP device encapsulating the FC-Frames over TCP/IP > ,why should we > convert the SOF and EOF Codes ? Can't we send them AS IS ? > > This avoids mapping and reverse mapping of all SOF, EOF codes. > > True, We have no way to represent a comma character in the > byte-encoded > format, but the FC-1 Layer will guarentee that a K28.5 will > be a BC in the > byte encoded form. > > For example: > > If an FCIP device receives SOFn2 (K28.5 D21.5 D21.1 D21.1 ), > the FC-1 layer > will have to deliver it as BC_B5_35_35 in byte-encoded form > (according to table -22) . (As per FCPH , p-g : 67-70) > > Since we are using a Length field for FC-Frame boundaries, > the byte encoded > format will be distinguished as either special or data groups. > > Let us say if we choose to use a chip from vitesse > http://www.vitesse.com/pdfs/vsc7216.pdf > > We will be dealing with byte encoded formats like the one > mentioned in FC-PH > spec. Hence why this mapping and reverse mapping ? > > Any Comments ? > > -- srini > > >
Home Last updated: Tue Sep 04 01:06:05 2001 6315 messages in chronological order |