Re: FCIP WG Last Call comment 57 - TCP simultaneous open

[Ralph Weber <ralphoweber@compuserve.com>]

The following changes are proposed:

Change the response to Comment 57 to "accepted with the following results"

Add a new section, 9.1.4, titled "Simultaneous Connection
Establishment" containing the following text.

"If two FCIP Entities perform simultaneous open operations, then two
TCP Connections are formed and the SF originates at one end on one
connection and at the other end on the other. Connection setup
proceeds as described above on both connections, and the steps
described above properly result in the formation of two FCIP
Links between the same FCIP Entities.

"This is not an error. Fibre Channel is perfectly capable of handling
to approximately equal connections between FC Fabric elements.

"The decision to setup pairs of FCIP Links in this manner is
considered to be a site policy decision that can be covered in
the "shared" database described in section 9.1.1."

Change the response to the last issue in Comment 124 to
"The last issue is resolved as per the response to Comment 57."

Thanks.

.Ralph

Black_David@emc.com wrote:

>
> Comment 57 (see below) references the following text from comment 124:
>
>    If two FCIP Entities perform simultaneous open operations, then two
>    TCP Connections are formed and the SF originates at one end on one
>    connection and at the other end on the other. Connection setup
>    proceeds as described in 9.1... on both connections, and the steps
>    described in 9.1... properly result in the formation of two FCIP
>    Links between the same FCIP Entities.
>
>    This is not an error. Fibre Channel is perfectly capable of handling
>    to approximately equal connections between FC Fabric elements.
>
>    The decision to setup pairs of FCIP Links in this manner is
>    considered to be a site policy decision that can be covered in
>    the "shared" database described in section 9.1.1. Further
>    efforts to prevent this mode of operation are considered
>    adverse to acceptance of FCIP as a protocol.
>
> I'd like to see this discussion (excepting the last sentence) inserted
> into the FCIP draft in some form to indicate that TCP simultaneous open is
> not an error.
>
> Thanks,
> --David
>
> Comment 57 Technical
>
>     -- Section 9.1.3 - Processing Incoming TCP Connect Requests
>
>       Note that the originator of TCP connect requests uses IP Address
>       and TCP Port to identify which TCP Connections belong to which
>       FCIP_LEPs while the recipient of TCP connect requests uses the
>       Source FC Fabric Entity World Wide Name, Source FC/FCIP Entity
>       Identifier fields from the FCIP Special Frame to identify which TCP
>       Connection belong to which FCIP_LEPs. For this reason, an FCIP
>       Entity that both originates and receives TCP connect requests is
>       unable to match the FCIP_LEPs associated with originated TCP
>       connect requests to the FCIP_LEPs associated with received TCP
>       connect requests.
>
>    [T] That's a problem. See comment against Section 9.1.2.1 for
>    one suggestion for how to fix this, but some sort of fix appears
>    necessary to me.
>
>    Rejected see comment 124
>
> ---------------------------------------------------
> David L. Black, Senior Technologist
> EMC Corporation, 42 South St., Hopkinton, MA  01748
> +1 (508) 249-6449 *NEW*      FAX: +1 (508) 497-8500
> black_david@emc.com         Cell: +1 (978) 394-7754
> ---------------------------------------------------