Re: [MEXT] draft-larsson-mext-flow-distribution-rules-01.txt comments (was: draft-ietf-mext-flow-binding-00.txt

On Tue, Nov 18, 2008 at 16:26:04 -0500, Stuart W. Card wrote:
> conny.larsson@ericsson.com wrote --
> 
> > And the draft describing how this can be done is
> > http://tools.ietf.org/id/draft-larsson-mext-flow-distribution-rules-01.txt
> 
> I hadn't reviewed the latter draft before.
> Thank you for pointing it out.
> It looks like it may become very useful in my team's work.
> My comments follow.
> 
> From that draft:
> 
> > 5.4.  Conditional Rule-Sets
> >
> >   For some scenarios, it is useful to install or transmit a collection
> >   of rule-sets at the same time, and select which one to use depending
> >   on what PIDs are available.  How the set of available PIDs is
> >   determined is outside the scope of this document.
> 
> and:
> 
> > 5.14.  Round-robin
> >
> >   For load-sharing purposes, round-robin transmission is supported.  To
> >   use round-robin, a list of PIDs is given instead of just one:
> >
> >      udp peer 2001:db8:1c32::/48 port 44100 on 4, 4, 5
> >
> >   Here, UDP traffic from port 44100 at any node in prefix 2001:db8:
> >   1c32::/48 will be sent on PIDs 4 and 5.  Two out of three packets
> >   will go on PID 4, which presumably has twice the bandwidth of PID 5.
> 
> These specs make sense iff:
>  a PID is either available, or not; and
>  coarse granularity in bandwidth allocation is adequate.
> 
> However, a path may be 'available', but currently degraded.
> Or paths may simply have bandwidth that is highly variable.
> Likewise different paths may have slightly different bandwidths.

At the Home Agent, a path can only be "available" or "not available",
as it is determined by if a particular BID is bound or not
(draft-larsson PIDs map directly to MIPv6 BIDs).

If the availability is "fuzzy" (sometimes degraded), that would have
to be handled by some outside party that updates the flow rules at the
HA (and MN) according to the conditions of each path.

BR, Michael
_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www.ietf.org/mailman/listinfo/mext

Re: [MEXT] draft-larsson-mext-flow-distribution-rules-01.txt comments (was: draft-ietf-mext-flow-binding-00.txt - comments)