Tony Hain wrote:
>
> Jarno Rajahalme wrote:
>
> > I might be wrong, but it seems that unless there is a case
> > where a locally
> > used DSCP value for a PHB cannot be mapped back to a standardized, PHB
> > definition recommended DSCP value at the domain egress, there
> > is no need for
> > additional support from the flow label.
>
> Thank you for making this point, because you have done it
> better than I have been able to. If the DSCP is consistent
> from end-to-end, each domain can make its own decisions.
> I really don't care what they do with the bits in the middle,
> as long as they exit the domain like they entered it. We don't
> need to redefine the flow label if the diffserv WG will
> simply define a set of standard DSCP values for interdomain
> use.
It's been done, by RFC 2474, 2597, and 2598 (soon to be revised,
but the DSCP value doesn't change). What we can't do is force ISPs
to use them. In particular, we can't force ISPs that don't support
diffserv to use them. Like it or not, there *will* be scenarios
where an ISP can't rely on the arriving DSCP value.
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]
--------------------------------------------------------------------
