Hi Benjamin,
on 2007-02-16 04:05 Benjamin Lim said the following:
> Hi,
>
> Since Jari brought up this discussion, I would like to put forth an issue
> about interworking Monami6 with NEMO. In Monami6, a mobile node knows the
> traffic condition over its multiple links. Thus, the mobile node is able to
> inform its home agent how to route the flow to the mobile node (through the
> various filter rules setting methods proposed in the WG).
>
> The mobile node now associates with a mobile router with multiple egress
> paths (roaming into NEMO). However, the mobile node has no way of knowing
> the existence of multiple paths (and their network characteristics) to
> continue on with flow filtering. On the other hand, the mobile router cannot
> perform efficient flow filtering since the mobile router has no way to know
> the traffic requirements of the mobile node's flow.
>
> The fact is that the tunnel ends at the mobile router whereas the traffic
> ends at mobile node cause such a problem with flow filtering.
>
> Any thoughts on how such issue can be solved?
While the proposals discussed in monami6 so far has been geared to transfer
of filter rules, this seems to call for transfer not of filter rules, but
of a subset of policy declarations (some sort of preferences for quality
and cost of service) between the Mobile Router and the Node attaching to the
Mobile Network (the MNN).
I think that as a general problem, this may be less well understood, and
possibly more complex, than expressing filter rules. The filter rules I
see needed by for instance monami6 appear to be a subset of filter rules
that can be expressed for firewalls today, using well-defined languages; but
I'm not aware of mature languages for expressing cost/latency/bandwidth/
/reliability/security/etc. preferences, and how to weigh them against each
other.
I know that some work has been done in SHIM6 on expressing and communicating
policy, but don't know that work well enough to know whether it would be
applicable to this case.
Henrik
_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area
