Re: FCIP: Comment 120

["Mallikarjun C." <cbm@rose.hp.com>]

Ralph,

Upon further thought, it appears to me that the "Destination FC/FCIP Entity Identifier"
should be sent and received in the FSF.  I can not think of a way currently to build an 
FCIP_LEP with multiple FCIP_DEs - for ex., how would a sender indicate his intention
to add a TCP connection to an FC/FCIP Entity Pair that it's already communicating with?

Thanks.
--
Mallikarjun

Mallikarjun Chadalapaka
Networked Storage Architecture
Network Storage Solutions Organization
Hewlett-Packard MS 5668 
Roseville CA 95747
cbm@rose.hp.com


----- Original Message ----- 
From: "Ralph Weber" <ralphoweber@compuserve.com>
To: <ips@ece.cmu.edu>
Cc: "Mallikarjun C." <cbm@rose.hp.com>
Sent: Monday, May 06, 2002 1:29 PM
Subject: Re: FCIP: Comment 120


> Mallikarjun,
> 
> Oops! This mistake is on me.
> 
> The Source FC Fabric Entity World Wide Name field DOES NOT contain the
> WWN of the FC Entity. Rather, it contains the "Fibre Channel Name_Identifier 
> [FC-FS] for the FC Fabric entity associated with the FC Entity FCIP Entity
> pair."
> 
> Two corrections are needed in the picture that I led you to believe in:
> 
>    1) The "FC Fabric entity" IS NOT the FC Entity, it is the FC product
>       (switch or whatever) that contains one or more FC Entities; and
>    2) There is no 1-to-n relationship between FC Entities and FCIP Entities,
>       in fact, they come in 1-to-1 one matched pairs.
> 
> Note that these corrections further strengthen the argument that the
> 1-to-n discussion belongs in FC-BB-2, since the multiplicity relationship
> really is farther inside FC constructs than I first suggested.
> 
> Hope this helps.
> 
> .Ralph
> 
> "Mallikarjun C." wrote:
> 
> >
> > Ralph,
> >
> > > The requested figure relies on Fibre Channel concepts and thus appears
> > > in a T11 document, FC-BB-2, ftp://ftp.t11.org/t11/pub/fc/bb-2/02-030v1.pdf.
> > > See Figure 23 on PDF page 87, or Figure 26 on PDF page 94.
> >
> > Thanks for the reference, but unfortunately it doesn't help make the point
> > that there is 1-to-n association between FC Entity and FCIP Entity.
> >
> > Given that FCIP is an RFC that defines these Entities and their relationships
> > in its own right, my suggestion would continue to be that the association be depicted
> > in an architectural model diagram.  It could be as simple as showing a shadow ASCII
> > box to the FCIP Entity box.  I will leave it here up to you and Co-Chairs to make
> > the call.
> >
> > Regards.
> > --
> > Mallikarjun
> >
> > Mallikarjun Chadalapaka
> > Networked Storage Architecture
> > Network Storage Solutions Organization
> > Hewlett-Packard MS 5668
> > Roseville CA 95747
> > cbm@rose.hp.com
> >
> > ----- Original Message -----
> > From: "Ralph Weber" <ralphoweber@compuserve.com>
> > To: <ips@ece.cmu.edu>
> > Cc: "Mallikarjun C." <cbm@rose.hp.com>
> > Sent: Monday, May 06, 2002 7:35 AM
> > Subject: Re: FCIP: Comment 120
> >
> > > Mallikarjun,
> > >
> > > > >... the "FC/FCIP Entity Identifier" is unique only within the scope
> > > > >of the given FC Entity's WWN. ... the model allows multiple FCIP
> > > > >Entities to be associated with the FC Fabric Entity WWN.
> > > >
> > > > If that is so, please add an architectural model diagram (similar to
> > > > Figure 3, or perhaps convert Figure 3 into) which clearly shows this
> > > > 1-to-n association.
> > > >
> > > > This is the only hint in the document (at least that I found) which
> > > > suggests the stated possibility.  Figure 3 with 1-to-1 association almost
> > > > seemed like the architectural model, but on careful reading, is only
> > > > an example.
> > >
> > > The fact that the "FC/FCIP Entity Identifier" is unique only within
> > > the scope of a given FC Entity's WWN seems to be clearly stated in the
> > > definition of the field:
> > >
> > >   "The Source FC/FCIP Entity Identifier field SHALL contain a unique
> > >   identifier for the FC Entity FCIP Entity pair that generates (as opposed
> > >   to echoes) the Special Frame. The value is assigned by the FC Fabric
> > >   entity whose world wide name appears in the Source FC Fabric Entity World
> > >   Wide Name field.
> > >
> > >   "Note: The combination of the Source FC Entity World Wide Name and Source
> > >   FCIP Entity Identifier fields uniquely identifies every FC Entity FCIP
> > >   Entity pair in the IP Network."
> > >
> > > The requested figure relies on Fibre Channel concepts and thus appears
> > > in a T11 document, FC-BB-2, ftp://ftp.t11.org/t11/pub/fc/bb-2/02-030v1.pdf.
> > > See Figure 23 on PDF page 87, or Figure 26 on PDF page 94.
> > >
> > > Thanks.
> > >
> > > .Ralph
> > >
> > > "Mallikarjun C." wrote:
> > >
> > > >
> > > > Ralph,
> > > >
> > > > > http://www.ietf.org/internet-drafts/draft-ietf-ips-fcip-wglc-01.pdf
> > > > ....
> > > > > Please review these comments resolutions to ensure that
> > > > > the desired changes are described.
> > > >
> > > > Sorry for the delayed review, I have additional comments on wglc-01
> > > > for Comment 120.
> > > >
> > > > Regards.
> > > > --
> > > > Mallikarjun
> > > >
> > > > Mallikarjun Chadalapaka
> > > > Networked Storage Architecture
> > > > Network Storage Solutions Organization
> > > > Hewlett-Packard MS 5668
> > > > Roseville CA 95747
> > > > cbm@rose.hp.com
> > > >
> > > > >Comment 120
> > > > >> 8. The FCIP Special Frame
> > > > >......
> > > > >> Note: The combination of the Source FC Entity World Wide Name and
> > > > >> Source FCIP Entity Identifier fields uniquely identifies every FC
> > > > >> Entity FCIP Entity pair in the IP Network.
> > > > >....
> > > > >- Also I take it that the "FC/FCIP Entity Identifier" is unique only
> > > > >within the scope of the given FC Entity's WWN. So, does the model
> > > > >allow multiple FCIP Entities to be associated with the FC Fabric
> > > > >Entity WWN?
> > > > >....
> > > > >Response to the second bullet: Yes, the "FC/FCIP Entity Identifier"
> > > > >is unique only within the scope of the given FC Entity's WWN. Yes,
> > > > >the model allows multiple FCIP Entities to be associated with the FC
> > > > >Fabric Entity WWN.
> > > > >
> > > >
> > > > If that is so, please add an architectural model diagram (similar to
> > > > Figure 3, or perhaps convert Figure 3 into) which clearly shows this
> > > > 1-to-n association.
> > > >
> > > > This is the only hint in the document (at least that I found) which
> > > > suggests the stated possibility.  Figure 3 with 1-to-1 association almost
> > > > seemed like the architectural model, but on careful reading, is only
> > > > an example.
> > >
> > >
>