[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [NSIS] RE: I-D ACTION:draft-ash-nsis-nslp-qspec-00.txt
> All,
>
> FYI. Please review and comment.
>
> Thanks,
> Jerry, Attila, Cornelia
> Co-Editors
>
>
> -----Original Message-----
> From: i-d-announce-bounces at ietf.org
> [mailto:i-d-announce-bounces at ietf.org]On Behalf Of
> Internet-Drafts at ietf.org
> Sent: Friday, May 28, 2004 3:43 PM
> To: i-d-announce at ietf.org
> Subject: I-D ACTION:draft-ash-nsis-nslp-qspec-00.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
> Title : QoS-NSLP QSpec Template
> Author(s) : J. Ash, et al.
> Filename : draft-ash-nsis-nslp-qspec-00.txt
> Pages : 17
> Date : 2004-5-28
>
> This draft describes a QSpec template for the QoS NSIS Signaling
> Layer Protocol (QoS NSLP) for signaling QoS reservations in the
> Internet. A QSpec is transported in QoS-NSLP messages and is opaque
> to QoS NSLP. It contains the QoS Signaling Model (QSM) control
> information and QoS description parameters. Control information is,
> for example, a flag that a particular QSM was not understood by one
> QoS NSLP entity. QoS description parameters are primary input and
> output parameters of the Resource Management Function. They include
> immutable descriptions of the traffic for which resources are to be
> reserved and of the desired QoS. QoS description parameters can also
> be used for collecting information about resource availability along
> the path. The QSpec template defines generic parameters that are
> common to many QSMs. They should be used by all QSMs if applicable.
> By identifying the generic parameters we aim to ensure
> interoperability between different QSMs.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ash-nsis-nslp-qspec-00.txt
>
> _______________________________________________
> nsis mailing list
> nsis at ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
>
Hi All
Here some comments and some questions about the QoS-NSLP Qspec Template
draft.
In the introduction of the draft the Service Schedule is mentioned as a
QoS Description parameter, after in section 3.4 it is mentioned as a QSM
Specific Control Information and finally in section 3.5 it is placed in
the table of QoS description parameter as a QoS Desired and not detailed
in the remaining of the section like the other parameters : I want to know
if Service Schedule is at the same time QSM Control Information and a QoS
Description, in that case how it will be interpreted in the QNE?
My second question concenrs the function or the entity wich specifies the
parameters of Qspec in the QNI : Once an application triggers the QoS NSLP
to make a resource reservation, how the Qspec, wich is opaque to the
QoS-NSLP, is initially determinated in the QNI (by wich function in the
QNE is it made and fixed) so that it's QoS description parameters will be
interpreted by the RMF and the QSM control information parameters by the
QSM specific NSLP processing.
Best regards
nader
_______________________________________________
nsis mailing list
nsis at ietf.org
https://www1.ietf.org/mailman/listinfo/nsis