end users/applications marking themselves a DSCP given/imposed by a provider
for access to a negotiated service is not contrary to diffserv architecture
nor to the current SLS effort
it helps to resolve some well known problems/limitations of routers with
respect to application recognition, ACL performances etc.
it's an old (and certainly resolved now)debate about the difference between
marking (which can be handled by the customer)and policing (responsibility
of the provider)
regards
jeanpierre.garbisu@francetelecom.fr
-----Message d'origine-----
De : Jaroslaw Sydir [mailto:sydir@cplane.com]
Envoyé : jeudi 8 février 2001 18:56
À : sls@ist-tequila.org
Cc : Yves T'Joens; John Schnizlein; demir;
diffserv-interest@external.cisco.com
Objet : Re: [tequila/sls] Re: [Diffserv-interest] A question on the
relationship betweenSLA and service class
I think that the SLS should be specified in a way that is independent of
the underlying technology used to implement the service. So I don't
think
that the SLS should contain PHBIDs or DSCPs. The network should map the
service
described in an SLS into a PDB, which in turn is mapped to a PHB at each
hop.
It seems contrary to the diffserv architecture to have end users specify
the PHB
that should be applied to their flow.
Jerry Sydir
This archive was generated by hypermail 2b29 : Mon Feb 12 2001 - 17:36:49 CET