Re: [Monami6] MCoA vs Flow Bindings: Solving same problem?

Hi Hesham,

On Thursday 29 June 2006 16:08, Soliman, Hesham wrote:
> 
>  > According to section "6.2.  Receiving Binding Update" of
>  > draft-wakikawa-mobileip-multiplecoa-05, it is allowed to have such
>  > a BC:
>  > HoA1 -> CoA1, BID=1
>  > HoA1 -> CoA2, BID=2
>  > HoA1 -> CoA2, BID=3
> 
> => I'm not sure how this helps in the flow binding case. I think 
> there is a simple point and people seem to be talking past it: 
> In the flow binding case we are binding *flows* therefore we need 
> to identify *flows* therefore we have a flow id in the flow id 
> option; exactly where it belongs. The MCoA draft binds *addresses* 
> to each other, therefore their bindings identify *addresses* and 
> that's what the BID does.       
> In other words we bind flows to a CoA. In doing that, we can't 
> help but bind the CoA to the HoA because that's the nature of 
> the BU. But we don't need a BID on the address level, because we 
> don't care about that. The MCoA draft binds CoAs to HoAs. How 
> are you suggesting we use that? And please be specific: what is 
> the use of the BID in the BU sent in the flow binding draft?      
> 
OK, thanks! I see your point. So you did not want to build on MCoA
because it would have made the design less efficient?

Regards,
Gabor

PS: Anyway, just to answer your question...

The BID can be used for the same purpose as the FID.
There is issue only if you allow multiple Flow Identification
options carried in the same BU.
The flow-binding draft currently handles this case by registering multiple
BC entries resulting in:

HoA1 -> CoA1, FID=1, default
HoA1 -> CoA2, FID=2, port 22
HoA1 -> CoA2, FID=3, port 443

Please, correct me if I am wrong!

But if it built on top of MCoA then it could associate each Flow
Identification option to the BID in the BU,
and therefore to the same BC/BUL entry. So you would end up with:

HoA1 -> CoA1, BID=1, default
HoA1 -> CoA2, BID=2, FlowOpt(port 22) or FlowOpt(port 443)

And here is where I see your point. Managing the Flow Identification
options (remove/update) independently is tricky this way if you don't
have separate IDs for each Flow Id option.

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6