Re: [MEXT] Important considerations for directionality of flow bindings

[Hesham Soliman <hesham at elevatemobile.com>]

On 31/05/09 7:52 PM, "Yungui Wang" <w52006 at huawei.com> wrote:

> Hello
> 
>> 
>> => Part of accepting requirements is to understand what makes
>> sense. This is
>> a normal discussion for a requirements process. It's not like
>> we're placing
>> requirements on something new that we've never worked with
>> before, this is a
>> well-established technology and is well understood.
> 
> I think, what I decide to buy a watch is that I want to check time,
> not the watch is hard/easily made.
> 
> However, I am attemping to solve your implementation issues
> 1/2/3 respectively mentioned before.
> 1. during MCoA registeration, 'access technology type' mobility
> option which could be re-used from PMIP or re-defined is binding
> to each BID for flow binding.  Then, HA can locally translate
> "forward port 80 traffic on a wifi link"(a policy) into "forward port
> 80 traffic using CoA 3ffe::1" (a rule).

=> But I already mentioned that option in my email and showed why it's not
enough due to changes in radio and due to the fact that "port 80" tells you
nothing about the application running on that port other than it's using
HTTP.

> 2. HA just tracks BID (tieing to ATT) here, not CoA. Then, your
> issue2 doesn't exist.
=> Yes it does exist see above and my earlier email.

> 3. MN, of course, should be able to initiate flow handover due to
> link/interface down or something else. I don't think it is an issue.

=> Then it's completely redundant for the HA to send such rules. Again see
my email. 

> 
>>> For your information, the polcies information could be PCC rules
>>> downloaded from PCRF which is defined in 3GPP TS23.203
>>> and TS23.402, etc.
>> 
>> => I've already said many times that this is not about policies.
>> 
> 
> In context of discussion, I thought you asked information is 'policies or
> link 
> overload indication, etc' of my previous mail. Maybe I misunderstood you.
> May I know what's the information which you stated in your question 'How
> does the HA know this information'?

=> The HA knows nothing about the app running on any port, knows nothing
about changes in the link, nothing about user preferences, nothing about
interface failure....etc. That's the information.

Hesham

> 
> B.R.
> Yungui
>