I think that since the services are supposed to be independent of the
underlying network provisioning technology used then we could think of
a wide range of services including some variations of BE traffic. For
example a user may specify a BE forwarding policy with some
restrictions with regrad to bandwidth, security, etc...
DJamel
On Thu, 2 Nov 2000, Michael Smirnov wrote:
> Hi Jaroslaw,
>
> thanks for your answer,
> On Thu Nov 2 02:51:21 2000 Jaroslaw Sydir wrote:
>
> > Michael,
> >
> > I'm not sure that I understand your question. If the traffic is truely
>
> your answer is just to the point
>
> > best effort then it requires no guarantees and you don't care about it
> > in your traffic engineering. It gets the lowest priority in the network
> > and is dropped in favor of the guaranteed traffic.
>
> and this is exactly what I dislike in the whole story
>
> >
> > If you want to provide a "slightly better than best effort" service,
> > then this implies some level of performance guarantees for some amount
> > of this traffic. In this case you would describe it in terms of
> > individual e2e SLS just like the other types of services.
> >
> > Jerry
> >
> >
> > Michael Smirnov wrote:
> > >
> > > On Wed Nov 1 00:51:41 2000 Jaroslaw Sydir wrote:
> > >
> > > > Jean-Pierre and Pierrick,
> > > >
> > > > A traffic matrix (network wide SLS) can be specified as a set of individual e2e
> > > > SLS/services (represending the trunks that make up the traffic matrix).
> > > <...>
> > >
> > > How you plan to specify best effort traffic?
> > >
> > > cheers
> > >
> > > Michael
> >
>
> regards
>
> Michael
>
This archive was generated by hypermail 2b29 : Thu Nov 02 2000 - 17:42:04 CET