[EMAIL PROTECTED] wrote:
> 
> Brian,
> 
> In the scenario you provided (multiple instances of the standard PHBs, each
> mapped to separate DSCP value), the mapping is reversible: the egress router
> of that domain should be able to map back to the single instance of the
> recommended DSCP value for the PHB in question. Therefore usage of the
> recommended DSCPs intra-domain would seem to be sufficient.
> 
> 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.

If you accept that ESP traffic will get QOS treatment only if there is
a suitable SLA at every domain boundary on its path. (Incidentally, the
same is true of intserv - if there is no SLA, there is no reason why
intserv would work across a domain boundary.)

> 
> Also, mutability and standardized semantics would seem to be orthogonal
> issues.

Yes, I think so. As I've been trying to communicate, there is nothing to stop
ISPs using the standardised DSCP values across domain boundaries today,
if they have an SLA in place. 

   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]
--------------------------------------------------------------------

Reply via email to