[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [NSIS] QSPEC document

The basic problem is that end-2-end QoS-model is a separate problem space. Everyone has tried to define their favourite QoS-solution during the years and everyone of the has failed.
Overprovisioning is the only commenrcial successfull end-2-end Qos Model.

In the development of RSVP IETf had one group discussing QoS-parameters denoted Int.serv. If someone would like work with this, it should be done in a separate working group rather than be a part of the basic protocol specification.
All experience in from Int.serv working group has shown the difficulties to define such models.
I suggest that we standard track document  end-2-end QoS-model  so we can have a separate discussion from developping the template.

regards Lasse

Roy, Radhika R. wrote:

John:

 

You are right that QOS models must NOT introduce any changes to the basic operation of the end-to-end QSPEC template that is used by NSIS QOS signaling protocol.

 

This is our concern too.

 

Best regards,

Radhika

 

From: nsis-bounces at ietf.org [mailto:nsis-bounces at ietf.org] On Behalf Of john.loughney at nokia.com
Sent: Tuesday, January 23, 2007 3:31 AM
To: Lars.westberg at ericsson.com
Cc: gash at att.com; nsis at ietf.org; attila.bader at ericsson.com
Subject: RE: [NSIS] QSPEC document

 

Hi Lars,


I think we are approaching agreement on this issue, so I'll give people a chance to comment and then see if we can get text.

 

I have been concerned about different QoS Models introducing too many changes to the basic operation that it becomes hard to deploy end-to-end, or that implementations would have to be customized quite heavily for each QoS Model.

 

But I think we are getting close to resolving this.

 

thanks,

John

_______________________________________________
nsis mailing list
nsis at ietf.org
https://www1.ietf.org/mailman/listinfo/nsis