Re: Request new DLT value for raw fibre channel

[kahou lei <kahou82 () gmail com>]

It is not base on RFC 3643. We are following the standard from
http://www.t11.org .

You can find the draft in Fibre Channel (FC) -> FC-FS-3 Fibre Channel -
Framing and Signaling - 3INCITS Project 1861-D.

Basically, we are following Table 4 Valid Data Characters (Section 5.14) and
Table 7 Frame Delimiters (Section 5.2).

We are currently supporting:

SOFi2 - BCB55555
SOFn2 - BCB53535**
SOFi3 - BCB55656
SOFn3 - BCB53636
SOFf - BCB55858
EOFt RD- -BC957575
EOFt RD+ - BCB57575
EOFa RD- -BC95F5F5
EOFa RD+ -BCB5F5F5
EOFn RD- -BC95D5D5
EOFn RD+ -BCB5D5D5
EOFni RD- -BC8AD5D5
EOFni RD+ -BCAAD5D5

The content of the packet header is based on Section 8.2 General Frame
Format.

Thanks,
Kahou

On Wed, Jul 22, 2009 at 12:38 PM, Guy Harris <guy () alum mit edu> wrote:

> On Jul 22, 2009, at 12:21 PM, Guy Harris wrote:
>
>
> > On Jul 22, 2009, at 11:17 AM, kahou lei wrote:
> >
> >  In this case, can you assign me one more value for FC with SOF? The
> > > reason
> > > is that our module can send out two type of packets: One with SOF, one
> > > without SOF.
> >
> > So what are the contents of the 4 bytes of SOF?
>
> In particular, is it the
>
> 5.3.  FC SOF and EOF
>
>
>   As described in section 5.1, representation of FC SOF and EOF in an
>   IP Network byte stream requires special formatting and 8-bit code
>   definitions.  Therefore, the encapsulated FC frame SHALL have the
>   format shown in Figure 5.  The redundancy of the SOF/EOF
>   representation in the encapsulation format results from concerns that
>   the information be protected from transmission errors.
>
>   W|------------------------------Bit------------------------------|
>   o|                                                               |
>   r|                    1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3|
>   d|0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1|
>    +---------------+---------------+-------------------------------+
>   0|      SOF      |      SOF      |     -SOF      |     -SOF      |
>    +---------------+---------------+-------------------------------+
>   1|                                                               |
>    +-----                   FC frame content                  -----+
>    |                                                               |
>    +---------------+---------------+-------------------------------+
>   n|      EOF      |      EOF      |     -EOF      |     -EOF      |
>    +---------------+---------------+-------------------------------+
>
>    Figure 5 -  FC Frame Encapsulation Format
>
>   Note: The number of 8-bit bytes in the FC frame content is always a
>   multiple of four.
>
>   SOF: The SOF fields contain the encoded SOF value selected from table
>   2.
>
>   +-------+------+-------+    +-------+------+-------+
>   |  FC   | SOF  |       |    |  FC   | SOF  |       |
>   |  SOF  | Code | Class |    |  SOF  | Code | Class |
>   +-------+------+-------+    +-------+------+-------+
>   | SOFf  | 0x28 |   F   |    | SOFi4 | 0x29 |   4   |
>   | SOFi2 | 0x2D |   2   |    | SOFn4 | 0x31 |   4   |
>   | SOFn2 | 0x35 |   2   |    | SOFc4 | 0x39 |   4   |
>   | SOFi3 | 0x2E |   3   |    +-------+------+-------+
>   | SOFn3 | 0x36 |   3   |
>   +-------+------+-------+
>
>   Table 2  Translation of FC SOF values to SOF field contents
>
>   -SOF: The -SOF fields contain the one's complement of the value in
>      the SOF fields.  Encapsulation receivers SHOULD validate the SOF
>      field according to a policy defined by the encapsulating protocol.
>
>                ...
>
>   Note: FC-BB-2 [6] lists SOF and EOF codes not shown in table 2 and
>   table 3 (e.g., SOFi1 and SOFn1).  However, FC-MI [8] identifies these
>   codes as not interoperable, so they are not listed in this
>   specification.
>
> representation from RFC 3643:
>
>        http://tools.ietf.org/html/rfc3643
>
> or is it something else?
>
> -
> This is the tcpdump-workers list.
> Visit https://cod.sandelman.ca/ to unsubscribe.
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.