[EMAIL PROTECTED] wrote:
>
> Robert,
>
> Very well put! Just some additional thoughts:
>
> - If diffserv WG so wants, it can even define a specific (standard) DSCP
> value to be used between domains to signify that the flow label in the same
> IP header has "diffserv semantics". This way the classification could be
> done the same for all source addresses (otherwise ingress router would need
> to know which source addresses use diffserv semantics for the flow label?).
That's an interesting thought, but I think it doesn't work. The egress router
has to *know* that the flow label is in diffserv format, and I think that
requires some magic.
>
> - If there is a diffserv relationship between a client and an ISP, the
> client could still use intserv for select flows by doing intserv signaling,
> which would explicitly tell the ISP that the associated flow label does not
> have any diffserv semantics.
Only for unencrypted traffic I think? The problem case is encrypted traffic,
where all you can "see" are the IP addresses and the flow label. I think the
intserv flow spec will be insufficient in that case.
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]
--------------------------------------------------------------------
