[EMAIL PROTECTED] wrote:
...
> A PHB-ID in the flow label is NOT the semantics, but a pointer to the
> semantics. The actual semantics are found from the respective specification,
> and since all the possible (future) PHB-ID pointed semantics cannot be
> hard-coded into the router, they need to be delivered to the router by some
> out-of-band mechanism.
Of course. Diffserv routers have to be configured by a QOS policy system.
See the POLICY, RAP and SNMPCONF WGs and the diffserv MIB and PIB.
> This out-of-band mechanism will indeed establish
> state at the router, not source specific state, but behavior aggregate flow
> specific state. One could even imagine establishing this state with an
> end-to-end signaling mechanism, which would result in a kind of host-to-host
> specific behavior aggregate flow
That's what the bandwidth broker and SLS-signalling people are up to,
though none of that work is in the IETF yet.
Brian
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
