Jarno Rajahalme wrote:
> AAA should enable the Starbucks domain to know what you are
> paying for.
Without a standard set of DSCP values what good does that do me?
> But I think somehow the scenario for the diffserv flow label has been
> intra-domain, between operators.
And this is the problem. The operators are finding that making
the DSCP completely random has resulted in a useless technology.
The flow label is an end-to-end field so there is a hope they
can restore what they need, but at the same time these bits
are being made mutable.
> The first hop can be solved by the diffserv
> WG alone by devising a suitable PHB-group.
If they had only done that to begin with.
> The point is, IMO the system doesn't work with the
> intra-domain 5-tuple
> MF-classifiers as specified today.
I was being very careful not to use the 5-tuple
because the src/dst addresses are mutable thanks
to NAT. The only end-to-end consistent bits are
the protocol & port, and the flow label.
> Maybe no-one has tried out setting
> intra-operator SLAs based on protocol fields set by hosts
> (being outside of
> the control of both the operators)?
It works as long as long as there is a trust or
financial relationship which creates feedback.
Tony
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
