IETF Logo Mail Archive

[NSIS] Point 3: QSPEC template draft dictates which QOS-NSLP signaling ....

<john.loughney@nokia.com> Fri, 05 January 2007 13:01 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H2ohA-0007GD-Nf; Fri, 05 Jan 2007 08:01:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H2oh9-0007G4-Gw for nsis@ietf.org; Fri, 05 Jan 2007 08:01:15 -0500
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2oh8-00087D-1U for nsis@ietf.org; Fri, 05 Jan 2007 08:01:15 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l05Cx1LY006323; Fri, 5 Jan 2007 14:59:32 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 5 Jan 2007 15:01:01 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 5 Jan 2007 15:01:01 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 05 Jan 2007 15:01:01 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC01B491AB@esebe199.NOE.Nokia.com>
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC8091@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Point 3: QSPEC template draft dictates which QOS-NSLP signaling ....
Thread-Index: AccnNAmV02JEI4mYSJ2rqx7HFPHiiwIEzvwgADBavYAAMBu0MA==
From: john.loughney@nokia.com
To: gash@att.com, nsis@ietf.org
X-OriginalArrivalTime: 05 Jan 2007 13:01:01.0530 (UTC) FILETIME=[8CFD03A0:01C730C9]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070105145932-1829DBB0-0721E24A/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc:
Subject: [NSIS] Point 3: QSPEC template draft dictates which QOS-NSLP signaling ....
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

>> Point_3: QSPEC template draft dictates which QOS-NSLP signaling 
>> features should be used by QOS models.
>> 
>> We have never discussed an agreed that the QSPEC template draft 
>> defines how the QOS-NSLP functionality should be used by QoS models.
>> This should be defined by the QOS-NSLP draft.
>> Therefore, regarding this issue  the QSPEC template draft should
refer 
>> to Section "3.1.2.  QoS Models and QoS Specifications"" of:
>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qos-nslp-12.txt
>> 
>> Therefore the QSPEC template draft should adapt the definition of the

>> QoS models according to what Section 3.1.2 of the QOS-NSLP draft is 
>> saying and refer to Section 3.1.2 of the QOS-NSLP draft.
>
>I'm not sure I fully understand Georgios' phrasing here.  I 
>agree that signaling functionality should only be defined by 
>the QoS NSLP draft and that the QSPEC draft should not specify 
>'how the QoS NSLP functionality should be used by QoS models'. 
> If that is the point, we're in agreement here also.

I agree with Jerry's view on this.

John

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

v2.23.0 | Report a Bug | By Email