RE: AW: [nemo] WG: new I-D on HA filtering

 > > I personally think there is nothing we should deal with at IETF.
 > > 
 > > Static Configuration:
 > > MN always wants to receives VoIP packets from 802.11b, MN 
 > can ask HA to
 > > configures this filter statically. 

=> How does the HA know if the packet contains VoIP?
The only concrete way of doing this today is to parse
the entire packet and check for RTP/UDP ...etc.
Needless to say that this is not possible if the packet
is encrypted. So I don't think that this is a general
solution.

 > > example: MN and HA shared meaning of IFID.  HA knows IFID1 
 > is assigned
 > > to GPRS and IFID2 is for 802.11b. so administrator of HA just
 > > configure VoIP and IFID2 as a filter.

=> Assuming that the HA knows which packet is VoIP and 
assuming that IFID1 does not chnge to mean WLAN or fixed LAN.

 > > 
 > > Policy Daemon (filter daemon):
 > > Policy daemon is run on HA and MN/MR. MN's daemon exchanges
 > > information of filters which associate IFID and flow type with HA's
 > > daemon. 

=> So this daemon knows MIP right? It knows the HA, home 
address(es) and Care-of addresses somehow. Why do we 
need a new daemon when we can already use MIP? 

Hesham