From nsis-bounces@ietf.org Mon Dec 04 00:15:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gr69t-0002KU-PS; Mon, 04 Dec 2006 00:14:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gr69s-0002KP-Ni
	for nsis@ietf.org; Mon, 04 Dec 2006 00:14:28 -0500
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gr69r-0007WS-3O
	for nsis@ietf.org; Mon, 04 Dec 2006 00:14:28 -0500
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/bulls) with ESMTP id
	kB45DvRF018718; Mon, 4 Dec 2006 14:13:57 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx2) with ESMTP id
	kB45DuP16880; Mon, 4 Dec 2006 14:13:56 +0900 (JST)
Received: from localhost (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/redsox) with SMTP id
	kB45Dw815775; Mon, 4 Dec 2006 14:13:58 +0900 (JST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] QoS NSLP: summary object
Date: Mon, 4 Dec 2006 13:12:12 +0800
Message-ID: <5F09D220B62F79418461A978CA0921BD015A43F7@pslexc01.psl.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] QoS NSLP: summary object
Thread-Index: AccEQBQeN3ILSKMHTeGiekKNHXjJCgTJ6maw
From: "Shivanajay Marwaha" <Shivanajay.Marwaha@sg.panasonic.com>
To: "Jukka MJ Manner" <jmanner@cs.Helsinki.FI>, <nsis@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: 
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

Dear Jukka,=20

I have some comment on your email sent sometime ago.=20

Regarding your second point on tearing down several sessions in one NSLP =
tearing RESERVE message (Summary_TEAR), I've some queries regarding:-

- Is the Summary_TEAR only for one hop (hop-by-hop)? Or, is it meant for =
multiple hops over a region (for example a Tunnel) as well?=20

- Secondly, just to be in sync, what is the criteria for Summary_TEAR? =
As I understand, if multiple TEAR are received simultaneously at a QNE, =
they can be combined into a Summary_TEAR (if their next-hop is same). =
Kindly clarify.

- Lastly, does a QNE wait before forwarding a TEAR in order to generate =
a Summary_TEAR? For example, if there exists a delay in arrival of =
multiple TEAR messages propogating on the same path, the Summary_TEAR =
may not be generated, unless the QNE waits.

Thanks and regards,
Shiv =20



> -----Original Message-----
> From: Jukka MJ Manner [mailto:jmanner@cs.Helsinki.FI]=20
> Sent: Friday, November 10, 2006 4:39 AM
> To: nsis@ietf.org
> Subject: [NSIS] QoS NSLP: summary object
>=20
>=20
> Based on John's request, here is recap of the summary object=20
> mentioned today. After Roland's comment on the mic, there are=20
> actually two use
> cases:
>=20
> 1. Allow a QNE to refresh several sessions in one NSLP=20
> refreshing RESERVE message.=20
>=20
> 2. Allow a ANE to tear down several sessions in one NSLP=20
> tearing RESERVE message.
>=20
> Both of these save bytes and processing compared to doing it=20
> independently for each session. They can be implemented=20
> outside GIST by keeping track of the SII_HANDLE provided by=20
> GIST (however, you can only know the handle after you have=20
> received a message from the per, e.g., a RESPONSE). If a QNE=20
> has sessions whose next peer has the same SII_HANDLE, it can=20
> use a new SESSION_LIST where it indicates SID+RSN pairs of=20
> sessions it wants to refresh or tear down. The receiving QNE,=20
> in case of unknown SID, will reply with a RESPONSE carrying=20
> the same object to indicate which session references where=20
> not understood. If a confirmation was requested from the QNR=20
> for a tear, and it must send an individual RESPONSE for each=20
> terminated session, as usual - the summary refresh could hit=20
> a QNR with multiple sessions being terminated.
>=20
> We would like to add this to the NSLP spec. Any comments,=20
> arguments, feedback? I'll wait for a week, then add this=20
> unless I hear arguments against.
>=20
> Jukka
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
>=20


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



From nsis-bounces@ietf.org Mon Dec 04 02:20:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gr87F-0007Kp-Cq; Mon, 04 Dec 2006 02:19:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gr87E-0007Kj-By
	for nsis@ietf.org; Mon, 04 Dec 2006 02:19:52 -0500
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gr87D-0002Yu-2A
	for nsis@ietf.org; Mon, 04 Dec 2006 02:19:52 -0500
Received: from sbz-31.cs.helsinki.fi (sbz-31.cs.helsinki.fi [128.214.9.99])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Mon, 04 Dec 2006 09:19:43 +0200
	id 000AFD7A.4573CC0F.0000320B
Date: Mon, 4 Dec 2006 09:19:43 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Shivanajay Marwaha <Shivanajay.Marwaha@sg.panasonic.com>
Subject: RE: [NSIS] QoS NSLP: summary object
In-Reply-To: <5F09D220B62F79418461A978CA0921BD015A43F7@pslexc01.psl.local>
Message-ID: <Pine.LNX.4.64.0612040913500.3710@sbz-31.cs.Helsinki.FI>
References: <5F09D220B62F79418461A978CA0921BD015A43F7@pslexc01.psl.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: nsis@ietf.org
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


Hi Shiv,

On Mon, 4 Dec 2006, Shivanajay Marwaha wrote:

> Dear Jukka, 
> 
> I have some comment on your email sent sometime ago. 
> 
> Regarding your second point on tearing down several sessions in one NSLP tearing RESERVE message (Summary_TEAR), I've some queries regarding:-
> 
> - Is the Summary_TEAR only for one hop (hop-by-hop)? Or, is it meant for 
>   multiple hops over a region (for example a Tunnel) as well?

Sending a Summary tear is only for one hop, you can't force all nodes to 
send summary tear msgs. A QNE receiving a tear may decide by itself, 
whether to send also a summary tear, or individual tear msgs.

> 
> - Secondly, just to be in sync, what is the criteria for Summary_TEAR? 
>   As I understand, if multiple TEAR are received simultaneously at a 
>   QNE, they can be combined into a Summary_TEAR (if their next-hop is 
>   same). Kindly clarify.

That is a configuration and policy issue. We can't mandate to use some 
heuristics and always send a summary tear. It is a beneficial optimization 
for certain situations.

> 
> - Lastly, does a QNE wait before forwarding a TEAR in order to generate 
>   a Summary_TEAR? For example, if there exists a delay in arrival of 
>   multiple TEAR messages propogating on the same path, the Summary_TEAR 
>   may not be generated, unless the QNE waits.

I don't want to specify how one should implement a QNE and summary tear. 
The spec only allows this functionality.

Jukka

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



From nsis-bounces@ietf.org Mon Dec 04 03:47:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gr9SX-0003ut-4A; Mon, 04 Dec 2006 03:45:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gr9SV-0003ui-Kz
	for nsis@ietf.org; Mon, 04 Dec 2006 03:45:55 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gr9SU-0007IH-6B
	for nsis@ietf.org; Mon, 04 Dec 2006 03:45:55 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kB48jevR009889; Mon, 4 Dec 2006 10:45:41 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 10:45:42 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 10:45:42 +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
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Mon, 4 Dec 2006 10:45:42 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC0176A470@esebe199.NOE.Nokia.com>
In-Reply-To: <Pine.LNX.4.64.0611301109090.22464@sbz-30.cs.Helsinki.FI>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Thread-Index: AccUX3yhnA8EMT2ITp2V7KJgX70DcwDILSXg
From: <john.loughney@nokia.com>
To: <jmanner@cs.Helsinki.FI>
X-OriginalArrivalTime: 04 Dec 2006 08:45:42.0349 (UTC)
	FILETIME=[94D37FD0:01C71780]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061204104541-22F74BB0-44C74AED/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: nsis@ietf.org
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

Jukka,

I could be wrong, but I assumed that the differences between
1) & 2) would be that that in 1) the NSLP would need to pop
the top-most QSPEC and send that to the RMF.  For 2), the
NSLP would just send the entire QSPEC to the RMF, and the
RMF would manipulate what it needed from the QSPEC.

So, I think that there is a difference between 1 & 2.  Are you meaning
that as the QoS NSLP is currently specified, that item 2 could
be managed with no changes to the QoS NSLP?

John

>-----Original Message-----
>From: ext Jukka MJ Manner [mailto:jmanner@cs.Helsinki.FI]=20
>Sent: 30 November, 2006 11:11
>To: Loughney John (Nokia-NRC/Helsinki)
>Cc: nsis@ietf.org
>Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
>
>
>Item 2 does not affect the QoS NSLP in any way. That was the=20
>main point.=20
>It is left to QOSM designers and the RMF. The NSLP doesn't=20
>care what the contents of the QSPEC is, and whether it is=20
>updated in some QNE or not.
>
>Jukka
>
>On Thu, 30 Nov 2006, john.loughney@nokia.com wrote:
>
>> Dave Oran proposed 3 options for supporting domain-local admission=20
>> control operation in NSLP/QSPEC in the following mail:
>> http://www1.ietf.org/mail-archive/web/nsis/current/msg07178.html
>>=20
>> As stated, these are meant as complete solutions:
>>=20
>> 1. Do complete QSPEC stacking, and deal with the issues around what=20
>> constraints have to be met by the stacked QSPEC, whether the QSPEC=20
>> lower in the "stack" is opacified, and what the rules are=20
>for pushing,=20
>> swapping, and popping.
>>=20
>> 2. Allow domain-parameters to be added to a QSPEC on domain entry and

>> removed on exit. In this option one has to describe whether anything=20
>> is opacified and which existing QSPEC parameters get "re-interpreted"

>> if any.
>>=20
>> 3. Recurse at the NSLP level, have a separate domain-private NSLP=20
>> session, and that would contain a domain-private set of paramteres=20
>> instead of the end-to-end QSPEC. I'll note that this approach allows=20
>> (but not requires) the two signaling state machines (end-end=20
>and edge-=20
>> edge through interior nodes) to be decoupled.
>>=20
>> There seems to be consensus that 3 is mandatory, but 2 is still=20
>> desirable.  Does this mean that 2 would be optional in the QoS NSLP?
>>=20
>> John
>>=20
>

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



From nsis-bounces@ietf.org Mon Dec 04 03:47:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gr9Td-0004B9-OX; Mon, 04 Dec 2006 03:47:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gr9Tc-0004AY-Js
	for nsis@ietf.org; Mon, 04 Dec 2006 03:47:04 -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 1Gr9Tb-0007Tj-4D
	for nsis@ietf.org; Mon, 04 Dec 2006 03:47:04 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kB48kUA7009797; Mon, 4 Dec 2006 10:46:50 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 10:46:34 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 10:46:34 +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
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Mon, 4 Dec 2006 10:46:13 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC0176A474@esebe199.NOE.Nokia.com>
In-Reply-To: <000a01c71477$1f8a0070$4c0d5982@dynamic.ewi.utwente.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Thread-Index: AccUX+6MUDt8n0k1QU2/yJu3J3ffkgAFvkbgAMJtbnA=
From: <john.loughney@nokia.com>
To: <karagian@cs.utwente.nl>, <jmanner@cs.Helsinki.FI>
X-OriginalArrivalTime: 04 Dec 2006 08:46:34.0526 (UTC)
	FILETIME=[B3ED13E0:01C71780]
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: nsis@ietf.org
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

So, I assume that you are supporting option 2, correct?

John=20

>-----Original Message-----
>From: ext Georgios Karagiannis [mailto:karagian@cs.utwente.nl]=20
>Sent: 30 November, 2006 14:00
>To: 'Jukka MJ Manner'; Loughney John (Nokia-NRC/Helsinki)
>Cc: nsis@ietf.org
>Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
>
>Hi John
>
>Option 2 will be described in the QSPEC templete draft and in=20
>the QoS models that require to use this feature.
>
>
>Best Regards,
>Georgios
>=20
>
>> -----Original Message-----
>> From: Jukka MJ Manner [mailto:jmanner@cs.Helsinki.FI]=20
>> Sent: donderdag 30 november 2006 10:11
>> To: john.loughney@nokia.com
>> Cc: nsis@ietf.org
>> Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
>>=20
>>=20
>> Item 2 does not affect the QoS NSLP in any way. That was the=20
>> main point.=20
>> It is left to QOSM designers and the RMF. The NSLP doesn't=20
>> care what the contents of the QSPEC is, and whether it is=20
>> updated in some QNE or not.
>>=20
>> Jukka
>>=20
>> On Thu, 30 Nov 2006, john.loughney@nokia.com wrote:
>>=20
>> > Dave Oran proposed 3 options for supporting domain-local admission=20
>> > control operation in NSLP/QSPEC in the following mail:
>> > http://www1.ietf.org/mail-archive/web/nsis/current/msg07178.html
>> >=20
>> > As stated, these are meant as complete solutions:
>> >=20
>> > 1. Do complete QSPEC stacking, and deal with the issues=20
>around what=20
>> > constraints have to be met by the stacked QSPEC, whether the QSPEC=20
>> > lower in the "stack" is opacified, and what the rules are=20
>> for pushing,=20
>> > swapping, and popping.
>> >=20
>> > 2. Allow domain-parameters to be added to a QSPEC on domain=20
>> entry and=20
>> > removed on exit. In this option one has to describe whether=20
>> anything=20
>> > is opacified and which existing QSPEC parameters get=20
>> "re-interpreted"=20
>> > if any.
>> >=20
>> > 3. Recurse at the NSLP level, have a separate domain-private NSLP=20
>> > session, and that would contain a domain-private set of paramteres=20
>> > instead of the end-to-end QSPEC. I'll note that this=20
>> approach allows=20
>> > (but not requires) the two signaling state machines=20
>> (end-end and edge-=20
>> > edge through interior nodes) to be decoupled.
>> >=20
>> > There seems to be consensus that 3 is mandatory, but 2 is still=20
>> > desirable.  Does this mean that 2 would be optional in the=20
>QoS NSLP?
>> >=20
>> > John
>> >=20
>>=20
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>=20
>
>
>

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



From nsis-bounces@ietf.org Mon Dec 04 03:47:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gr9Tf-0004BV-W9; Mon, 04 Dec 2006 03:47:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gr9Te-0004BQ-OS
	for nsis@ietf.org; Mon, 04 Dec 2006 03:47:06 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gr9Td-0007Uf-5F
	for nsis@ietf.org; Mon, 04 Dec 2006 03:47:06 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kB48kkNl010748; Mon, 4 Dec 2006 10:46:50 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 10:46:55 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 10:46:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Mon, 4 Dec 2006 10:46:55 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC0176A475@esebe199.NOE.Nokia.com>
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC7FC8@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Support for local domain information in the QSPEC
Thread-Index: AccUVMjBCgWWu3X5T6KN+j72Q8Re5QAJt/mwAMFC3oA=
From: <john.loughney@nokia.com>
To: <gash@att.com>, <nsis@ietf.org>
X-OriginalArrivalTime: 04 Dec 2006 08:46:55.0853 (UTC)
	FILETIME=[C0A351D0:01C71780]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061204104650-28B9ABB0-46C62DFE/0-0/0-0
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: ce732c7d36989a1bd55104ba259c40a1
Cc: 
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>
Content-Type: multipart/mixed; boundary="===============0595297121=="
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0595297121==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C71780.C0EC60F1"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C71780.C0EC60F1
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Jerry,
=20
Thanks for the feedback.  Does the working agree?
=20
John


________________________________

	From: ext Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]=20
	Sent: 30 November, 2006 14:42
	To: Loughney John (Nokia-NRC/Helsinki); nsis@ietf.org
	Cc: Ash, Gerald R (Jerry), ALABS
	Subject: RE: [NSIS] Support for local domain information in the
QSPEC
=09
=09
	Hi John,
	=20
	My impression was clearly agreement on option 1, which I think
Georgios originally described in his post at=20
	http://www1.ietf.org/mail-archive/web/nsis/current/msg07213.html
	and again at
	http://www1.ietf.org/mail-archive/web/nsis/current/msg07232.html
	=20
	On the thread I think most agreed with Georgios' suggestion, see

	http://www1.ietf.org/mail-archive/web/nsis/current/msg07237.html
	and then
	http://www1.ietf.org/mail-archive/web/nsis/current/msg07238.html
	=20
	Thanks,
	Jerry

________________________________

	From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]=20
	Sent: Thursday, November 30, 2006 2:55 AM
	To: nsis@ietf.org
	Subject: [NSIS] Support for local domain information in the
QSPEC
=09
=09

	I'm trying to tease through all of the mails on this, and so if
my interpretation is incorrect, please suggest corrective text.

	At the previous IETF, Dave Oran proposed that we have a
mathmatically complete description of the traffic source.  I believe we
have consensus on that.=20

	The open question is how to handle QoS model specific
parameters: traffic class, diff serv classes, etc.=20
	1) Include a common set of them as optional parameters in the
QSPEC document and allow QoSM documents define additional parameters via
an IANA registry. =20

	2) Allow QoSM documents to define their own complete QSPECs,
which are used within the QoSM domain, essentially defining an e2e QSPEC
and a local QSPEC.

	I think Georgios summarized these quite well in:=20
	http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html
<http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html> =20

	I believe that more people were favoring #2.  Of course, the
devil is always in the details, as there have been discussions about
what parameters belong where.

	Comments?=20
	John=20


------_=_NextPart_001_01C71780.C0EC60F1
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Support for local domain information in the =
QSPEC</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2995" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D882344608-04122006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Jerry,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D882344608-04122006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D882344608-04122006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thanks for the feedback.&nbsp; Does the working =

agree?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D882344608-04122006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D882344608-04122006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>J</FONT></SPAN><SPAN =
class=3D882344608-04122006><FONT=20
face=3DArial color=3D#0000ff size=3D2>ohn</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ext Ash, Gerald R (Jerry), =
ALABS=20
  [mailto:gash@att.com] <BR><B>Sent:</B> 30 November, 2006 =
14:42<BR><B>To:</B>=20
  Loughney John (Nokia-NRC/Helsinki); nsis@ietf.org<BR><B>Cc:</B> Ash, =
Gerald R=20
  (Jerry), ALABS<BR><B>Subject:</B> RE: [NSIS] Support for local domain=20
  information in the QSPEC<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Hi John,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>My impression was clearly agreement on option =
1, which I=20
  think Georgios originally described in his post at =
</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2><A=20
  =
href=3D"http://www1.ietf.org/mail-archive/web/nsis/current/msg07213.html"=
>http://www1.ietf.org/mail-archive/web/nsis/current/msg07213.html</A></FO=
NT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>and again at</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2><A=20
  =
href=3D"http://www1.ietf.org/mail-archive/web/nsis/current/msg07232.html"=
>http://www1.ietf.org/mail-archive/web/nsis/current/msg07232.html</A></FO=
NT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>On&nbsp;the thread I think most agreed with =
Georgios'=20
  suggestion, see </FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2><A=20
  =
href=3D"http://www1.ietf.org/mail-archive/web/nsis/current/msg07237.html"=
>http://www1.ietf.org/mail-archive/web/nsis/current/msg07237.html</A></FO=
NT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>and then</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2><A=20
  =
href=3D"http://www1.ietf.org/mail-archive/web/nsis/current/msg07238.html"=
>http://www1.ietf.org/mail-archive/web/nsis/current/msg07238.html</A></FO=
NT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Thanks,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Jerry</FONT></SPAN></DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> john.loughney@nokia.com=20
  [mailto:john.loughney@nokia.com] <BR><B>Sent:</B> Thursday, November =
30, 2006=20
  2:55 AM<BR><B>To:</B> nsis@ietf.org<BR><B>Subject:</B> [NSIS] Support =
for=20
  local domain information in the QSPEC<BR></FONT><BR></DIV>
  <DIV></DIV><!-- Converted from text/rtf format -->
  <P><FONT face=3DArial size=3D2>I'm trying to tease through all of the =
mails on=20
  this, and so if my interpretation is incorrect, please suggest =
corrective=20
  text.</FONT></P>
  <P><FONT face=3DArial size=3D2>At the previous IETF, Dave Oran =
proposed that we=20
  have a mathmatically complete description of the traffic source.&nbsp; =
I=20
  believe we have consensus on that. </FONT></P>
  <P><FONT face=3DArial size=3D2>The open question is how to handle QoS =
model=20
  specific parameters: traffic class, diff serv classes, etc.</FONT> =
<BR><FONT=20
  face=3DArial size=3D2>1) Include a common set of them as optional =
parameters in=20
  the QSPEC document and allow QoSM documents define additional =
parameters via=20
  an IANA registry.&nbsp; </FONT></P>
  <P><FONT face=3DArial size=3D2>2) Allow QoSM documents to define their =
own=20
  complete QSPECs, which are used within the QoSM domain, essentially =
defining=20
  an e2e QSPEC and a local QSPEC.</FONT></P>
  <P><FONT face=3DArial size=3D2>I think Georgios summarized these quite =
well=20
  in:</FONT> <BR><A=20
  =
href=3D"http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html"=
><U><FONT=20
  face=3DArial color=3D#0000ff=20
  =
size=3D2>http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html=
</FONT></U></A>=20
  </P>
  <P><FONT face=3DArial size=3D2>I believe that more people were =
favoring #2.&nbsp;=20
  Of course, the devil is always in the details, as there have been =
discussions=20
  about what parameters belong where.</FONT></P>
  <P><FONT face=3DArial size=3D2>Comments?</FONT> <BR><FONT face=3DArial =

  size=3D2>John</FONT> </P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C71780.C0EC60F1--


--===============0595297121==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0595297121==--




From nsis-bounces@ietf.org Mon Dec 04 04:00:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gr9fe-0007Vg-PR; Mon, 04 Dec 2006 03:59:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gr9fe-0007T9-2L
	for nsis@ietf.org; Mon, 04 Dec 2006 03:59:30 -0500
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gr9fc-0000rJ-P9
	for nsis@ietf.org; Mon, 04 Dec 2006 03:59:30 -0500
Received: from [10.1.1.109] (mito.netlab.nec.de [195.37.70.39])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id BC61513CF88
	for <nsis@ietf.org>; Mon,  4 Dec 2006 10:03:40 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v752.2)
References: <455DF1CE.5040004@gmx.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FA6971D3-3A5A-4085-9E8E-94CCEB4B7843@netlab.nec.de>
Content-Transfer-Encoding: 7bit
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Subject: Fwd: [NSIS] Meeting Minutes
Date: Mon, 4 Dec 2006 09:59:25 +0100
To: nsis <nsis@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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

Hi all,

Please check the minutes if they are correct. Deadline for getting  
the minutes fixed is December 7th (Thursday). The final minutes need  
to be uploaded by December 8th.

Thanks,

   Martin

Anfang der weitergeleiteten E-Mail:

> Von: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
> Datum: 17. November 2006 18:30:54 MEZ
> An: nsis <nsis@ietf.org>
> Betreff: [NSIS] Meeting Minutes
>
> Hi all,
>
> here is a first proposal for the meeting minutes.
>
> http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt
>
> Ciao
> Hannes
>
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis


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



From nsis-bounces@ietf.org Mon Dec 04 04:23:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrA1n-000681-5Y; Mon, 04 Dec 2006 04:22:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrA1l-00067w-Fm
	for nsis@ietf.org; Mon, 04 Dec 2006 04:22:21 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrA1k-0004z2-1s
	for nsis@ietf.org; Mon, 04 Dec 2006 04:22:21 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kB49Lplp021067; Mon, 4 Dec 2006 10:22:11 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: <john.loughney@nokia.com>, <jmanner@cs.Helsinki.FI>
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Mon, 4 Dec 2006 10:21:50 +0100
Message-ID: <000601c71785$a47cccc0$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AccUX+6MUDt8n0k1QU2/yJu3J3ffkgAFvkbgAMJtbnAAATE2gA==
In-Reply-To: <BAA65A575825454CBB0103267553FCCC0176A474@esebe199.NOE.Nokia.com>
X-Spam-Score: 0 () 
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Mon, 04 Dec 2006 10:22:11 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: nsis@ietf.org
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

Hi John

>From the three options listed below, option 3 is considered any way. 
Thus in addition to option 3 also option 2 has to be considered.

Best Regards,
Georgios
 

> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com] 
> Sent: maandag 4 december 2006 9:46
> To: karagian@cs.utwente.nl; jmanner@cs.Helsinki.FI
> Cc: nsis@ietf.org
> Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
> 
> So, I assume that you are supporting option 2, correct?
> 
> John 
> 
> >-----Original Message-----
> >From: ext Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> >Sent: 30 November, 2006 14:00
> >To: 'Jukka MJ Manner'; Loughney John (Nokia-NRC/Helsinki)
> >Cc: nsis@ietf.org
> >Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
> >
> >Hi John
> >
> >Option 2 will be described in the QSPEC templete draft and 
> in the QoS 
> >models that require to use this feature.
> >
> >
> >Best Regards,
> >Georgios
> > 
> >
> >> -----Original Message-----
> >> From: Jukka MJ Manner [mailto:jmanner@cs.Helsinki.FI]
> >> Sent: donderdag 30 november 2006 10:11
> >> To: john.loughney@nokia.com
> >> Cc: nsis@ietf.org
> >> Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
> >> 
> >> 
> >> Item 2 does not affect the QoS NSLP in any way. That was the main 
> >> point.
> >> It is left to QOSM designers and the RMF. The NSLP doesn't 
> care what 
> >> the contents of the QSPEC is, and whether it is updated in 
> some QNE 
> >> or not.
> >> 
> >> Jukka
> >> 
> >> On Thu, 30 Nov 2006, john.loughney@nokia.com wrote:
> >> 
> >> > Dave Oran proposed 3 options for supporting domain-local 
> admission 
> >> > control operation in NSLP/QSPEC in the following mail:
> >> > http://www1.ietf.org/mail-archive/web/nsis/current/msg07178.html
> >> > 
> >> > As stated, these are meant as complete solutions:
> >> > 
> >> > 1. Do complete QSPEC stacking, and deal with the issues
> >around what
> >> > constraints have to be met by the stacked QSPEC, whether 
> the QSPEC 
> >> > lower in the "stack" is opacified, and what the rules are
> >> for pushing,
> >> > swapping, and popping.
> >> > 
> >> > 2. Allow domain-parameters to be added to a QSPEC on domain
> >> entry and
> >> > removed on exit. In this option one has to describe whether
> >> anything
> >> > is opacified and which existing QSPEC parameters get
> >> "re-interpreted" 
> >> > if any.
> >> > 
> >> > 3. Recurse at the NSLP level, have a separate 
> domain-private NSLP 
> >> > session, and that would contain a domain-private set of 
> paramteres 
> >> > instead of the end-to-end QSPEC. I'll note that this
> >> approach allows
> >> > (but not requires) the two signaling state machines
> >> (end-end and edge-
> >> > edge through interior nodes) to be decoupled.
> >> > 
> >> > There seems to be consensus that 3 is mandatory, but 2 is still 
> >> > desirable.  Does this mean that 2 would be optional in the
> >QoS NSLP?
> >> > 
> >> > John
> >> > 
> >> 
> >> _______________________________________________
> >> nsis mailing list
> >> nsis@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/nsis
> >> 
> >
> >
> >
> 



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



From nsis-bounces@ietf.org Mon Dec 04 04:35:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrADg-00009A-Eh; Mon, 04 Dec 2006 04:34:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrADf-000093-OY
	for nsis@ietf.org; Mon, 04 Dec 2006 04:34:39 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrADd-0006gr-4f
	for nsis@ietf.org; Mon, 04 Dec 2006 04:34:39 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kB49YQoR021580; Mon, 4 Dec 2006 10:34:32 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: <john.loughney@nokia.com>, <gash@att.com>, <nsis@ietf.org>
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Mon, 4 Dec 2006 10:34:24 +0100
Message-ID: <000d01c71787$6605fa00$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AccUVMjBCgWWu3X5T6KN+j72Q8Re5QAJt/mwAMFC3oAAAaYJwA==
In-Reply-To: <BAA65A575825454CBB0103267553FCCC0176A475@esebe199.NOE.Nokia.com>
X-Spam-Score: 0.817 () FVGT_s_OBFU_Q1,HTML_60_70,HTML_MESSAGE
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Mon, 04 Dec 2006 10:34:33 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e16ce0269ccb2f59707d16700199d13b
Cc: 
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>
Content-Type: multipart/mixed; boundary="===============0949830340=="
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0949830340==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C7178F.C7CA6200"

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01C7178F.C7CA6200
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi John

I have the impression that these two options are different than the ones
that we were discussing in the mailing list.

I think that the consensus that we have had until now is described in:

 <http://www1.ietf.org/mail-archive/web/nsis/current/msg07182.html>
http://www1.ietf.org/mail-archive/web/nsis/current/msg07182.html

Thus if I look to the proposal of Dave Oran I think that we need need 

both otion 3 (parallel session support) and option 2, which is 

Rolands proposal that encapsulates end-to-end QSPEC into a 

local QSPEC and gives the possibility to the QoS model 

to specify which QSPEC parameters can be ignored.

Best Regards,

Georgios


  _____  

From: john.loughney@nokia.com [mailto:john.loughney@nokia.com] 
Sent: maandag 4 december 2006 9:47
To: gash@att.com; nsis@ietf.org
Subject: RE: [NSIS] Support for local domain information in the QSPEC


Hi Jerry,
 
Thanks for the feedback.  Does the working agree?
 
John


  _____  

From: ext Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
Sent: 30 November, 2006 14:42
To: Loughney John (Nokia-NRC/Helsinki); nsis@ietf.org
Cc: Ash, Gerald R (Jerry), ALABS
Subject: RE: [NSIS] Support for local domain information in the QSPEC


Hi John,
 
My impression was clearly agreement on option 1, which I think Georgios
originally described in his post at 
http://www1.ietf.org/mail-archive/web/nsis/current/msg07213.html
and again at
http://www1.ietf.org/mail-archive/web/nsis/current/msg07232.html
 
On the thread I think most agreed with Georgios' suggestion, see 
http://www1.ietf.org/mail-archive/web/nsis/current/msg07237.html
and then
http://www1.ietf.org/mail-archive/web/nsis/current/msg07238.html
 
Thanks,
Jerry

  _____  

From: john.loughney@nokia.com [mailto:john.loughney@nokia.com] 
Sent: Thursday, November 30, 2006 2:55 AM
To: nsis@ietf.org
Subject: [NSIS] Support for local domain information in the QSPEC



I'm trying to tease through all of the mails on this, and so if my
interpretation is incorrect, please suggest corrective text.

At the previous IETF, Dave Oran proposed that we have a mathmatically
complete description of the traffic source.  I believe we have consensus on
that. 

The open question is how to handle QoS model specific parameters: traffic
class, diff serv classes, etc. 
1) Include a common set of them as optional parameters in the QSPEC document
and allow QoSM documents define additional parameters via an IANA registry.


2) Allow QoSM documents to define their own complete QSPECs, which are used
within the QoSM domain, essentially defining an e2e QSPEC and a local QSPEC.

I think Georgios summarized these quite well in: 
 <http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html>
http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html 

I believe that more people were favoring #2.  Of course, the devil is always
in the details, as there have been discussions about what parameters belong
where.

Comments? 
John 


------=_NextPart_000_000E_01C7178F.C7CA6200
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Support for local domain information in the =
QSPEC</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2995" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft>
<P><FONT size=3D2>Hi John</FONT></P>
<P><FONT size=3D2>I have the impression that these two options are =
different than=20
the ones that we were discussing<SPAN class=3D095473309-04122006> in the =
mailing=20
list</SPAN>.</FONT></P>
<P><FONT size=3D2>I think that the consensus that we have had until now =
is=20
described in:</FONT></P>
<P><A=20
href=3D"http://www1.ietf.org/mail-archive/web/nsis/current/msg07182.html"=
><U><FONT=20
color=3D#0000ff=20
size=3D2>http://www1.ietf.org/mail-archive/web/nsis/current/msg07182.html=
</U></FONT></A></P><FONT=20
size=3D2>
<P>Thus if I look to the proposal of Dave Oran I think that we need need =
</P>
<P>both otion 3 (parallel session support) and option 2, which is </P>
<P>Rolands proposal that encapsulates end-to-end QSPEC into a </P>
<P>local QSPEC and gives the possibility to the QoS model </P>
<P>to specify which QSPEC parameters can be ignored.</P>
<P>Best Regards,</P>
<P>Georgios</P></FONT></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> john.loughney@nokia.com=20
  [mailto:john.loughney@nokia.com] <BR><B>Sent:</B> maandag 4 december =
2006=20
  9:47<BR><B>To:</B> gash@att.com; nsis@ietf.org<BR><B>Subject:</B> RE: =
[NSIS]=20
  Support for local domain information in the QSPEC<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D882344608-04122006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Hi Jerry,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D882344608-04122006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D882344608-04122006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Thanks for the feedback.&nbsp; Does the =
working=20
  agree?</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D882344608-04122006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D882344608-04122006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>J</FONT></SPAN><SPAN =
class=3D882344608-04122006><FONT=20
  face=3DArial color=3D#0000ff size=3D2>ohn</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> ext Ash, Gerald R (Jerry), =
ALABS=20
    [mailto:gash@att.com] <BR><B>Sent:</B> 30 November, 2006 =
14:42<BR><B>To:</B>=20
    Loughney John (Nokia-NRC/Helsinki); nsis@ietf.org<BR><B>Cc:</B> Ash, =
Gerald=20
    R (Jerry), ALABS<BR><B>Subject:</B> RE: [NSIS] Support for local =
domain=20
    information in the QSPEC<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>Hi John,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>My impression was clearly agreement on =
option 1, which=20
    I think Georgios originally described in his post at =
</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2><A=20
    =
href=3D"http://www1.ietf.org/mail-archive/web/nsis/current/msg07213.html"=
>http://www1.ietf.org/mail-archive/web/nsis/current/msg07213.html</A></FO=
NT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>and again at</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2><A=20
    =
href=3D"http://www1.ietf.org/mail-archive/web/nsis/current/msg07232.html"=
>http://www1.ietf.org/mail-archive/web/nsis/current/msg07232.html</A></FO=
NT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>On&nbsp;the thread I think most agreed with =
Georgios'=20
    suggestion, see </FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2><A=20
    =
href=3D"http://www1.ietf.org/mail-archive/web/nsis/current/msg07237.html"=
>http://www1.ietf.org/mail-archive/web/nsis/current/msg07237.html</A></FO=
NT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>and then</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2><A=20
    =
href=3D"http://www1.ietf.org/mail-archive/web/nsis/current/msg07238.html"=
>http://www1.ietf.org/mail-archive/web/nsis/current/msg07238.html</A></FO=
NT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>Thanks,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D644543212-30112006><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>Jerry</FONT></SPAN></DIV><BR>
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> john.loughney@nokia.com=20
    [mailto:john.loughney@nokia.com] <BR><B>Sent:</B> Thursday, November =
30,=20
    2006 2:55 AM<BR><B>To:</B> nsis@ietf.org<BR><B>Subject:</B> [NSIS] =
Support=20
    for local domain information in the QSPEC<BR></FONT><BR></DIV>
    <DIV></DIV><!-- Converted from text/rtf format -->
    <P><FONT face=3DArial size=3D2>I'm trying to tease through all of =
the mails on=20
    this, and so if my interpretation is incorrect, please suggest =
corrective=20
    text.</FONT></P>
    <P><FONT face=3DArial size=3D2>At the previous IETF, Dave Oran =
proposed that we=20
    have a mathmatically complete description of the traffic =
source.&nbsp; I=20
    believe we have consensus on that. </FONT></P>
    <P><FONT face=3DArial size=3D2>The open question is how to handle =
QoS model=20
    specific parameters: traffic class, diff serv classes, etc.</FONT> =
<BR><FONT=20
    face=3DArial size=3D2>1) Include a common set of them as optional =
parameters in=20
    the QSPEC document and allow QoSM documents define additional =
parameters via=20
    an IANA registry.&nbsp; </FONT></P>
    <P><FONT face=3DArial size=3D2>2) Allow QoSM documents to define =
their own=20
    complete QSPECs, which are used within the QoSM domain, essentially =
defining=20
    an e2e QSPEC and a local QSPEC.</FONT></P>
    <P><FONT face=3DArial size=3D2>I think Georgios summarized these =
quite well=20
    in:</FONT> <BR><A=20
    =
href=3D"http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html"=
><U><FONT=20
    face=3DArial color=3D#0000ff=20
    =
size=3D2>http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html=
</FONT></U></A>=20
    </P>
    <P><FONT face=3DArial size=3D2>I believe that more people were =
favoring=20
    #2.&nbsp; Of course, the devil is always in the details, as there =
have been=20
    discussions about what parameters belong where.</FONT></P>
    <P><FONT face=3DArial size=3D2>Comments?</FONT> <BR><FONT =
face=3DArial=20
    size=3D2>John</FONT> </P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000E_01C7178F.C7CA6200--




--===============0949830340==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0949830340==--






From nsis-bounces@ietf.org Mon Dec 04 04:50:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrARv-0005wC-85; Mon, 04 Dec 2006 04:49:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrARt-0005w1-Je
	for nsis@ietf.org; Mon, 04 Dec 2006 04:49:21 -0500
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrARq-0000Ff-48
	for nsis@ietf.org; Mon, 04 Dec 2006 04:49:21 -0500
Received: from sbz-31.cs.helsinki.fi (sbz-31.cs.helsinki.fi [128.214.9.99])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Mon, 04 Dec 2006 11:49:15 +0200
	id 000AFDEC.4573EF1B.00004900
Date: Mon, 4 Dec 2006 11:49:12 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: john.loughney@nokia.com
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
In-Reply-To: <BAA65A575825454CBB0103267553FCCC0176A470@esebe199.NOE.Nokia.com>
Message-ID: <Pine.LNX.4.64.0612041143480.3710@sbz-31.cs.Helsinki.FI>
References: <BAA65A575825454CBB0103267553FCCC0176A470@esebe199.NOE.Nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: nsis@ietf.org
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


Hi,

yes, that is what we want.

The point is that item 1 is not really wanted, since it affects the logic 
of the NSLP spec itself, and you need to have different NSLP-deployments 
in nodes. Thus, with item 2 the NSLP is not affect, and therefore the 
better option for NSLP designers - all NSLPs operate the same way with 
regard to the QSPEC. With item 2, what happens inside the RMF is not 
visible to the NSLP, and should stay like that.

Jukka

On Mon, 4 Dec 2006, john.loughney@nokia.com wrote:

> Jukka,
> 
> I could be wrong, but I assumed that the differences between
> 1) & 2) would be that that in 1) the NSLP would need to pop
> the top-most QSPEC and send that to the RMF.  For 2), the
> NSLP would just send the entire QSPEC to the RMF, and the
> RMF would manipulate what it needed from the QSPEC.
> 
> So, I think that there is a difference between 1 & 2.  Are you meaning
> that as the QoS NSLP is currently specified, that item 2 could
> be managed with no changes to the QoS NSLP?
> 
> John
> 
> >-----Original Message-----
> >From: ext Jukka MJ Manner [mailto:jmanner@cs.Helsinki.FI] 
> >Sent: 30 November, 2006 11:11
> >To: Loughney John (Nokia-NRC/Helsinki)
> >Cc: nsis@ietf.org
> >Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
> >
> >
> >Item 2 does not affect the QoS NSLP in any way. That was the 
> >main point. 
> >It is left to QOSM designers and the RMF. The NSLP doesn't 
> >care what the contents of the QSPEC is, and whether it is 
> >updated in some QNE or not.
> >
> >Jukka
> >
> >On Thu, 30 Nov 2006, john.loughney@nokia.com wrote:
> >
> >> Dave Oran proposed 3 options for supporting domain-local admission 
> >> control operation in NSLP/QSPEC in the following mail:
> >> http://www1.ietf.org/mail-archive/web/nsis/current/msg07178.html
> >> 
> >> As stated, these are meant as complete solutions:
> >> 
> >> 1. Do complete QSPEC stacking, and deal with the issues around what 
> >> constraints have to be met by the stacked QSPEC, whether the QSPEC 
> >> lower in the "stack" is opacified, and what the rules are 
> >for pushing, 
> >> swapping, and popping.
> >> 
> >> 2. Allow domain-parameters to be added to a QSPEC on domain entry and
> 
> >> removed on exit. In this option one has to describe whether anything 
> >> is opacified and which existing QSPEC parameters get "re-interpreted"
> 
> >> if any.
> >> 
> >> 3. Recurse at the NSLP level, have a separate domain-private NSLP 
> >> session, and that would contain a domain-private set of paramteres 
> >> instead of the end-to-end QSPEC. I'll note that this approach allows 
> >> (but not requires) the two signaling state machines (end-end 
> >and edge- 
> >> edge through interior nodes) to be decoupled.
> >> 
> >> There seems to be consensus that 3 is mandatory, but 2 is still 
> >> desirable.  Does this mean that 2 would be optional in the QoS NSLP?
> >> 
> >> John
> >> 
> >
> 

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



From nsis-bounces@ietf.org Mon Dec 04 04:50:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrASf-00078x-W0; Mon, 04 Dec 2006 04:50:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrASe-0006zL-88
	for nsis@ietf.org; Mon, 04 Dec 2006 04:50:08 -0500
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrASc-0000IA-QH
	for nsis@ietf.org; Mon, 04 Dec 2006 04:50:08 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1GrASa-0002ZS-Ax; Mon, 04 Dec 2006 10:50:06 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 366AAA994;
	Mon,  4 Dec 2006 10:50:02 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1GrASX-0006yB-Sh; Mon, 04 Dec 2006 10:50:02 +0100
Message-ID: <4573EF49.405@tm.uka.de>
Date: Mon, 04 Dec 2006 10:50:01 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: john.loughney@nokia.com
Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
References: <BAA65A575825454CBB0103267553FCCC01727194@esebe199.NOE.Nokia.com>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC01727194@esebe199.NOE.Nokia.com>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.7 (---)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.7 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: nsis@ietf.org
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

Hi John,

please see below.

john.loughney@nokia.com wrote:
> Dave Oran proposed 3 options for supporting domain-local admission
> control operation in NSLP/QSPEC in the following mail:
> 
> _http://www1.ietf.org/mail-archive/web/nsis/current/msg07178.html_
> 
> As stated, these are meant as complete solutions:
> 
> 1. Do complete QSPEC stacking, and deal with the issues around what
> constraints have to be met by the stacked QSPEC, whether the QSPEC lower
> in the "stack" is opacified, and what the rules are for pushing,
> swapping, and popping.
> 
> 2. Allow domain-parameters to be added to a QSPEC on domain entry and
> removed on exit. In this option one has to describe whether anything is
> opacified and which existing QSPEC parameters get "re-interpreted" if any.
> 
> 3. Recurse at the NSLP level, have a separate domain-private NSLP
> session, and that would contain a domain-private set of paramteres
> instead of the end-to-end QSPEC. I'll note that this approach allows
> (but not requires) the two signaling state machines (end-end and edge-
> edge through interior nodes) to be decoupled.
> 
> There seems to be consensus that 3 is mandatory, but 2 is still
> desirable.  Does this mean that 2 would be optional in the QoS NSLP? 

Option 2 is maybe not covering exactly that what I had in mind, so
please also consider my follow on:
http://www1.ietf.org/mail-archive/web/nsis/current/msg07183.html

Option 2 could be also realized by having one QSPEC type
where parameters are added and removed as needed and I guess
that's different from my proposal.

Regards,
 Roland

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



From nsis-bounces@ietf.org Mon Dec 04 05:02:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrAdg-0003Ky-Fq; Mon, 04 Dec 2006 05:01:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrAde-0003Kp-Es
	for nsis@ietf.org; Mon, 04 Dec 2006 05:01:31 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrAdd-0001ZN-19
	for nsis@ietf.org; Mon, 04 Dec 2006 05:01:30 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kB4A1M5q022768; Mon, 4 Dec 2006 11:01:27 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Roland Bless'" <bless@tm.uka.de>, <john.loughney@nokia.com>
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Mon, 4 Dec 2006 11:01:17 +0100
Message-ID: <003301c7178b$27aed250$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AccXibzeSRBqxbXAQZaS3q4+JEFQsQAAL08w
In-Reply-To: <4573EF49.405@tm.uka.de>
X-Spam-Score: 0 () 
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Mon, 04 Dec 2006 11:01:27 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: nsis@ietf.org
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

Hi John and Roland

I agree with Roland's proposal is different than (2)
that encapsulates end-to-end QSPEC into a 
local QSPEC and gives the possibility to the QoS model 
to specify which QSPEC parameters can be ignored.

In the mailing list there was support on using 
the option proposed by Roland instead of 
using option (1) and (2) proposed by Dave.

Best Regards,
Georgios


> -----Original Message-----
> From: Roland Bless [mailto:bless@tm.uka.de] 
> Sent: maandag 4 december 2006 10:50
> To: john.loughney@nokia.com
> Cc: nsis@ietf.org
> Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
> 
> Hi John,
> 
> please see below.
> 
> john.loughney@nokia.com wrote:
> > Dave Oran proposed 3 options for supporting domain-local admission 
> > control operation in NSLP/QSPEC in the following mail:
> > 
> > _http://www1.ietf.org/mail-archive/web/nsis/current/msg07178.html_
> > 
> > As stated, these are meant as complete solutions:
> > 
> > 1. Do complete QSPEC stacking, and deal with the issues around what 
> > constraints have to be met by the stacked QSPEC, whether the QSPEC 
> > lower in the "stack" is opacified, and what the rules are 
> for pushing, 
> > swapping, and popping.
> > 
> > 2. Allow domain-parameters to be added to a QSPEC on domain 
> entry and 
> > removed on exit. In this option one has to describe whether 
> anything 
> > is opacified and which existing QSPEC parameters get 
> "re-interpreted" if any.
> > 
> > 3. Recurse at the NSLP level, have a separate domain-private NSLP 
> > session, and that would contain a domain-private set of paramteres 
> > instead of the end-to-end QSPEC. I'll note that this 
> approach allows 
> > (but not requires) the two signaling state machines 
> (end-end and edge- 
> > edge through interior nodes) to be decoupled.
> > 
> > There seems to be consensus that 3 is mandatory, but 2 is still 
> > desirable.  Does this mean that 2 would be optional in the QoS NSLP?
> 
> Option 2 is maybe not covering exactly that what I had in 
> mind, so please also consider my follow on:
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07183.html
> 
> Option 2 could be also realized by having one QSPEC type 
> where parameters are added and removed as needed and I guess 
> that's different from my proposal.
> 
> Regards,
>  Roland
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 



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



From nsis-bounces@ietf.org Mon Dec 04 05:17:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrAsv-0004Gz-GC; Mon, 04 Dec 2006 05:17:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrAst-0004Fk-HW
	for nsis@ietf.org; Mon, 04 Dec 2006 05:17:15 -0500
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrAss-0004Nw-3D
	for nsis@ietf.org; Mon, 04 Dec 2006 05:17:15 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1GrAsp-0000nx-3e; Mon, 04 Dec 2006 11:17:13 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id D9D81B5A3;
	Mon,  4 Dec 2006 11:17:10 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1GrAso-0006zu-I0; Mon, 04 Dec 2006 11:17:10 +0100
Message-ID: <4573F5A5.9060501@tm.uka.de>
Date: Mon, 04 Dec 2006 11:17:09 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: john.loughney@nokia.com
Subject: Re: [NSIS] Support for local domain information in the QSPEC
References: <BAA65A575825454CBB0103267553FCCC0172718C@esebe199.NOE.Nokia.com>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC0172718C@esebe199.NOE.Nokia.com>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.7 (---)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.7 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: nsis@ietf.org
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

Hi John and all,

john.loughney@nokia.com wrote:
> I'm trying to tease through all of the mails on this, and so if my
> interpretation is incorrect, please suggest corrective text.

See below.

> At the previous IETF, Dave Oran proposed that we have a mathmatically
> complete description of the traffic source.  I believe we have consensus
> on that.

Yes, no doubt. We need that.

> The open question is how to handle QoS model specific parameters:
> traffic class, diff serv classes, etc.
> 1) Include a common set of them as optional parameters in the QSPEC
> document and allow QoSM documents define additional parameters via an
> IANA registry. 

The problem that I see is that if a QoSM-specific parameter is attached
to the QSPEC, the next domain with a different QoSM cannot interpret
that parameter correctly ("apples and oranges"). Even if both domains
support DiffServ, they may have a totally different set of classes and
PHBs, so signaling the PHB may not be very useful (example: while the
QSPEC's constraints may be supported by some AF class in domain A,
domain B can only use one of it's EF classes for this. So signaling
an AF PHB from domain A to domain B doesn't make much sense IMHO).

More rationale on that is provided here:
http://www1.ietf.org/mail-archive/web/nsis/current/msg07206.html

> 2) Allow QoSM documents to define their own complete QSPECs, which are
> used within the QoSM domain, essentially defining an e2e QSPEC and a
> local QSPEC.

The e2e QSPEC should be defined as generic QSPEC in "the QSPEC
document". Local QSPECs should not define their own e2e QSPEC
rather than how the e2e QSPEC is mapped to their local QSPEC
parameters.
The local QSPEC will usually encapsulate this e2e QSPEC
in its own local QSPEC or have an exact 1:1 mapping so that the
e2e QSPEC is sent to the next domain.
See also
http://www1.ietf.org/mail-archive/web/nsis/current/msg07158.html
for further explanations. Maybe the following picture helps here:
                     RMD                        Y.1541
               +-------------+             +-------------+
    E2E-QSPEC /   RMD-QSPEC   \ E2E-QSPEC /  Y.1541-QSPEC \ E2E-QSPEC
QNI---------->QNE--->QNE--->QNE---------->QNE--->QNE--->QNE---------->QNR
              \               /           \               /
               +-------------+             +-------------+


> I think Georgios summarized these quite well in:
> _http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html_
> 
> I believe that more people were favoring #2.  Of course, the devil is
> always in the details, as there have been discussions about what
> parameters belong where.

Regards,
 Roland

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



From nsis-bounces@ietf.org Mon Dec 04 05:33:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrB7S-0002LL-Ad; Mon, 04 Dec 2006 05:32:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrB7Q-0002Jf-GJ
	for nsis@ietf.org; Mon, 04 Dec 2006 05:32:16 -0500
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrB7P-0006IQ-0z
	for nsis@ietf.org; Mon, 04 Dec 2006 05:32:16 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1GrB7C-00041Q-19; Mon, 04 Dec 2006 11:32:09 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id AF555B5A3;
	Mon,  4 Dec 2006 11:32:01 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1GrB7B-00071E-EB; Mon, 04 Dec 2006 11:32:01 +0100
Message-ID: <4573F920.1010309@tm.uka.de>
Date: Mon, 04 Dec 2006 11:32:00 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: john.loughney@nokia.com
Subject: Re: [NSIS] Support for local domain information in the QSPEC
References: <BAA65A575825454CBB0103267553FCCC0176A475@esebe199.NOE.Nokia.com>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC0176A475@esebe199.NOE.Nokia.com>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.7 (---)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.7 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: gash@att.com, nsis@ietf.org
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

Hi John,

john.loughney@nokia.com wrote:
> Thanks for the feedback.  Does the working agree?

No. I'm actually slightly confused by Jerry's posting
since this discussion about options 1) and 2)
has nothing to do with the mails he quoted.
The quoted mails refer to the fact that the QSPEC
template draft will contain a general description of
QSPECs (as template for QOSM designers that specify their
on local QSPECs) as well as the e2e QSPEC.

My point is: if a DiffServ class parameter is attached,
the QSPEC type should be different from the generic e2e QSPEC.
So instead of having a QOSM ID we should have a QSPEC ID
with 1 being the generic e2e QSPEC which should be understood
by all QOSMs.

Regards,
 Roland

>     ------------------------------------------------------------------------
>     *From:* ext Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>     *Sent:* 30 November, 2006 14:42
>     *To:* Loughney John (Nokia-NRC/Helsinki); nsis@ietf.org
>     *Cc:* Ash, Gerald R (Jerry), ALABS
>     *Subject:* RE: [NSIS] Support for local domain information in the QSPEC
> 
>     Hi John,
>      
>     My impression was clearly agreement on option 1, which I think
>     Georgios originally described in his post at
>     http://www1.ietf.org/mail-archive/web/nsis/current/msg07213.html
>     and again at
>     http://www1.ietf.org/mail-archive/web/nsis/current/msg07232.html
>      
>     On the thread I think most agreed with Georgios' suggestion, see
>     http://www1.ietf.org/mail-archive/web/nsis/current/msg07237.html
>     and then
>     http://www1.ietf.org/mail-archive/web/nsis/current/msg07238.html
>      
>     Thanks,
>     Jerry
> 
>     ------------------------------------------------------------------------
>     *From:* john.loughney@nokia.com [mailto:john.loughney@nokia.com]
>     *Sent:* Thursday, November 30, 2006 2:55 AM
>     *To:* nsis@ietf.org
>     *Subject:* [NSIS] Support for local domain information in the QSPEC
> 
>     I'm trying to tease through all of the mails on this, and so if my
>     interpretation is incorrect, please suggest corrective text.
> 
>     At the previous IETF, Dave Oran proposed that we have a
>     mathmatically complete description of the traffic source.  I believe
>     we have consensus on that.
> 
>     The open question is how to handle QoS model specific parameters:
>     traffic class, diff serv classes, etc.
>     1) Include a common set of them as optional parameters in the QSPEC
>     document and allow QoSM documents define additional parameters via
>     an IANA registry. 
> 
>     2) Allow QoSM documents to define their own complete QSPECs, which
>     are used within the QoSM domain, essentially defining an e2e QSPEC
>     and a local QSPEC.
> 
>     I think Georgios summarized these quite well in:
>     _http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html_
> 
>     I believe that more people were favoring #2.  Of course, the devil
>     is always in the details, as there have been discussions about what
>     parameters belong where.
> 
>     Comments?
>     John


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



From nsis-bounces@ietf.org Mon Dec 04 09:23:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrEiO-000341-Dq; Mon, 04 Dec 2006 09:22:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrEiN-00033n-Kt
	for nsis@ietf.org; Mon, 04 Dec 2006 09:22:39 -0500
Received: from mail146.messagelabs.com ([216.82.245.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GrEiE-0004Yx-GV
	for nsis@ietf.org; Mon, 04 Dec 2006 09:22:39 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-15.tower-146.messagelabs.com!1165242149!439655!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 20418 invoked from network); 4 Dec 2006 14:22:29 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-15.tower-146.messagelabs.com with SMTP;
	4 Dec 2006 14:22:29 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kB4EMSDL027289; 
	Mon, 4 Dec 2006 09:22:29 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id
	kB4EMLf9027231; Mon, 4 Dec 2006 09:22:22 -0500 (EST)
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
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Mon, 4 Dec 2006 08:22:21 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC7FEF@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <4573F920.1010309@tm.uka.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Support for local domain information in the QSPEC
Thread-Index: AccXj30QpC8kVdkVRIOHU0v1M2+BugAGrUiA
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "Roland Bless" <bless@tm.uka.de>, <john.loughney@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, nsis@ietf.org
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

Hi Roland, John, and All,

> -----Original Message-----
> From: Roland Bless [mailto:bless@tm.uka.de]=20
> Sent: Monday, December 04, 2006 5:32 AM
> To: john.loughney@nokia.com
> Cc: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> Subject: Re: [NSIS] Support for local domain information in the QSPEC
>=20
> Hi John,
>=20
> john.loughney@nokia.com wrote:
> > Thanks for the feedback.  Does the working agree?
>=20
> No. I'm actually slightly confused by Jerry's posting
> since this discussion about options 1) and 2)
> has nothing to do with the mails he quoted.
> The quoted mails refer to the fact that the QSPEC
> template draft will contain a general description of
> QSPECs (as template for QOSM designers that specify their
> on local QSPECs) as well as the e2e QSPEC.

I thought the question John posed was related to which parameters should
be described in the QSPEC draft and which should be described in QOSM
specifications.  I think we agree on all except <PHB Class>, <DSTE Class
Type>, and <Y.1541 QoS Class>.  I understood Roland to originally
propose that these parameters be described in QOSM specifications rather
than the QSPEC draft.  I understood Georgios to propose that these be
left in the QSPEC draft:

"Jerry could separate the QSPEC template draft into:
A section/part that describes the Token Bucket + constraints.=20
This part could then emphasize that the described parameters=20
can be used for interoperability purposes.
Another part of the QSPEC template draft will describe=20
the other parameters."

I also understood Roland to later agree with Georgios' proposal in his
post:

"However, it's also ok for me to describe both aspects in one document
as it is probably now too late and too disturbing to make this
separation."

Perhaps I misunderstood these suggestions.  If so, please clarify.
=20
> My point is: if a DiffServ class parameter is attached,
> the QSPEC type should be different from the generic e2e QSPEC.
> So instead of having a QOSM ID we should have a QSPEC ID
> with 1 being the generic e2e QSPEC which should be understood
> by all QOSMs.

I don't think we have a concept of 'generic QSPEC' in the current
proposal.  Only the TMOD-1 parameter must be populated and must be
interpreted by all QNEs.  All other parameters are optional to populate
and optional to interpret by QNEs (unless marked by the M-flag by the
QNI).

Thanks,
Regards,
Jerry

>=20
> Regards,
>  Roland
>=20
> >    =20
> >     --------------------------------------------------------------
> >     ----------
> >     *From:* ext Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> >     *Sent:* 30 November, 2006 14:42
> >     *To:* Loughney John (Nokia-NRC/Helsinki); nsis@ietf.org
> >     *Cc:* Ash, Gerald R (Jerry), ALABS
> >     *Subject:* RE: [NSIS] Support for local domain=20
> >     information in the QSPEC
> >=20
> >     Hi John,
> >     =20
> >     My impression was clearly agreement on option 1, which I think
> >     Georgios originally described in his post at
> >     http://www1.ietf.org/mail-archive/web/nsis/current/msg07213.html
> >     and again at
> >     http://www1.ietf.org/mail-archive/web/nsis/current/msg07232.html
> >     =20
> >     On the thread I think most agreed with Georgios' suggestion, see
> >     http://www1.ietf.org/mail-archive/web/nsis/current/msg07237.html
> >     and then
> >     http://www1.ietf.org/mail-archive/web/nsis/current/msg07238.html
> >     =20
> >     Thanks,
> >     Jerry
> >=20
> >    =20
> >     --------------------------------------------------------------
> >     ----------
> >     *From:* john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> >     *Sent:* Thursday, November 30, 2006 2:55 AM
> >     *To:* nsis@ietf.org
> >     *Subject:* [NSIS] Support for local domain information=20
> >      in the QSPEC
> >=20
> >     I'm trying to tease through all of the mails on this,=20
> >     and so if my
> >     interpretation is incorrect, please suggest corrective text.
> >=20
> >     At the previous IETF, Dave Oran proposed that we have a
> >     mathematically complete description of the traffic=20
> >     source.  I believe
> >     we have consensus on that.
> >=20
> >     The open question is how to handle QoS model specific=20
> >     parameters:
> >     traffic class, diff serv classes, etc.
> >     1) Include a common set of them as optional parameters=20
> >     in the QSPEC
> >     document and allow QoSM documents define additional=20
> >     parameters via
> >     an IANA registry.=20
> >=20
> >     2) Allow QoSM documents to define their own complete=20
> >     QSPECs, which
> >     are used within the QoSM domain, essentially defining=20
> >     an e2e QSPEC
> >     and a local QSPEC.
> >=20
> >     I think Georgios summarized these quite well in:
> >    =20
> >     http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html
> >=20
> >     I believe that more people were favoring #2.  Of=20
> >     course, the devil
> >     is always in the details, as there have been=20
> >     discussions about what
> >     parameters belong where.
> >=20
> >     Comments?
> >     John
>=20
>=20

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



From nsis-bounces@ietf.org Mon Dec 04 10:37:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrFsT-000774-TH; Mon, 04 Dec 2006 10:37:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrFsS-00073y-88
	for nsis@ietf.org; Mon, 04 Dec 2006 10:37:08 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrFsP-0005XA-2f
	for nsis@ietf.org; Mon, 04 Dec 2006 10:37:08 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kB4Fagjo007931; Mon, 4 Dec 2006 16:36:56 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>,
	"'Roland Bless'" <bless@tm.uka.de>, <john.loughney@nokia.com>
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Mon, 4 Dec 2006 16:36:39 +0100
Message-ID: <000001c717ba$03e391b0$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AccXj30QpC8kVdkVRIOHU0v1M2+BugAGrUiAAAOI8ZA=
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC7FEF@KCCLUST06EVS1.ugd.att.com>
X-Spam-Score: 0.3 () FVGT_s_OBFU_Q1
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Mon, 04 Dec 2006 16:36:57 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 963faf56c3a5b6715f0b71b66181e01a
Cc: nsis@ietf.org
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

Hi Jerry

The question of John was related to another issue.
It was related to the e-mails posted by Dave Oran and 
Roland regarding the stacking issue.

I think that the consensus that we have had until now regarding this issue 
is described in:

http://www1.ietf.org/mail-archive/web/nsis/current/msg07182.html


Both option 3 (parallel session support) and option 2, which is 
Rolands proposal that encapsulates end-to-end QSPEC into a 
local QSPEC and gives the possibility to the QoS model 
to specify which QSPEC parameters can be ignored need to be supported

Best Regards,
Georgios
 

> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> Sent: maandag 4 december 2006 15:22
> To: Roland Bless; john.loughney@nokia.com
> Cc: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> Subject: RE: [NSIS] Support for local domain information in the QSPEC
> 
> Hi Roland, John, and All,
> 
> > -----Original Message-----
> > From: Roland Bless [mailto:bless@tm.uka.de]
> > Sent: Monday, December 04, 2006 5:32 AM
> > To: john.loughney@nokia.com
> > Cc: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > Subject: Re: [NSIS] Support for local domain information in 
> the QSPEC
> > 
> > Hi John,
> > 
> > john.loughney@nokia.com wrote:
> > > Thanks for the feedback.  Does the working agree?
> > 
> > No. I'm actually slightly confused by Jerry's posting since this 
> > discussion about options 1) and 2) has nothing to do with 
> the mails he 
> > quoted.
> > The quoted mails refer to the fact that the QSPEC template 
> draft will 
> > contain a general description of QSPECs (as template for QOSM 
> > designers that specify their on local QSPECs) as well as the e2e 
> > QSPEC.
> 
> I thought the question John posed was related to which 
> parameters should be described in the QSPEC draft and which 
> should be described in QOSM specifications.  I think we agree 
> on all except <PHB Class>, <DSTE Class
> Type>, and <Y.1541 QoS Class>.  I understood Roland to originally
> propose that these parameters be described in QOSM 
> specifications rather than the QSPEC draft.  I understood 
> Georgios to propose that these be left in the QSPEC draft:
> 
> "Jerry could separate the QSPEC template draft into:
> A section/part that describes the Token Bucket + constraints. 
> This part could then emphasize that the described parameters 
> can be used for interoperability purposes.
> Another part of the QSPEC template draft will describe the 
> other parameters."
> 
> I also understood Roland to later agree with Georgios' proposal in his
> post:
> 
> "However, it's also ok for me to describe both aspects in one 
> document as it is probably now too late and too disturbing to 
> make this separation."
> 
> Perhaps I misunderstood these suggestions.  If so, please clarify.
>  
> > My point is: if a DiffServ class parameter is attached, the 
> QSPEC type 
> > should be different from the generic e2e QSPEC.
> > So instead of having a QOSM ID we should have a QSPEC ID 
> with 1 being 
> > the generic e2e QSPEC which should be understood by all QOSMs.
> 
> I don't think we have a concept of 'generic QSPEC' in the 
> current proposal.  Only the TMOD-1 parameter must be 
> populated and must be interpreted by all QNEs.  All other 
> parameters are optional to populate and optional to interpret 
> by QNEs (unless marked by the M-flag by the QNI).
> 
> Thanks,
> Regards,
> Jerry
> 
> > 
> > Regards,
> >  Roland
> > 
> > >     
> > >     --------------------------------------------------------------
> > >     ----------
> > >     *From:* ext Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > >     *Sent:* 30 November, 2006 14:42
> > >     *To:* Loughney John (Nokia-NRC/Helsinki); nsis@ietf.org
> > >     *Cc:* Ash, Gerald R (Jerry), ALABS
> > >     *Subject:* RE: [NSIS] Support for local domain 
> > >     information in the QSPEC
> > > 
> > >     Hi John,
> > >      
> > >     My impression was clearly agreement on option 1, which I think
> > >     Georgios originally described in his post at
> > >     
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07213.html
> > >     and again at
> > >     
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07232.html
> > >      
> > >     On the thread I think most agreed with Georgios' 
> suggestion, see
> > >     
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07237.html
> > >     and then
> > >     
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07238.html
> > >      
> > >     Thanks,
> > >     Jerry
> > > 
> > >     
> > >     --------------------------------------------------------------
> > >     ----------
> > >     *From:* john.loughney@nokia.com 
> [mailto:john.loughney@nokia.com]
> > >     *Sent:* Thursday, November 30, 2006 2:55 AM
> > >     *To:* nsis@ietf.org
> > >     *Subject:* [NSIS] Support for local domain information 
> > >      in the QSPEC
> > > 
> > >     I'm trying to tease through all of the mails on this, 
> > >     and so if my
> > >     interpretation is incorrect, please suggest corrective text.
> > > 
> > >     At the previous IETF, Dave Oran proposed that we have a
> > >     mathematically complete description of the traffic 
> > >     source.  I believe
> > >     we have consensus on that.
> > > 
> > >     The open question is how to handle QoS model specific 
> > >     parameters:
> > >     traffic class, diff serv classes, etc.
> > >     1) Include a common set of them as optional parameters 
> > >     in the QSPEC
> > >     document and allow QoSM documents define additional 
> > >     parameters via
> > >     an IANA registry. 
> > > 
> > >     2) Allow QoSM documents to define their own complete 
> > >     QSPECs, which
> > >     are used within the QoSM domain, essentially defining 
> > >     an e2e QSPEC
> > >     and a local QSPEC.
> > > 
> > >     I think Georgios summarized these quite well in:
> > >     
> > >     
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html
> > > 
> > >     I believe that more people were favoring #2.  Of 
> > >     course, the devil
> > >     is always in the details, as there have been 
> > >     discussions about what
> > >     parameters belong where.
> > > 
> > >     Comments?
> > >     John
> > 
> > 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 



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



From nsis-bounces@ietf.org Mon Dec 04 11:39:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrGqI-0004zR-Gv; Mon, 04 Dec 2006 11:38:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrGqH-0004zH-47
	for nsis@ietf.org; Mon, 04 Dec 2006 11:38:57 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrGqF-0006Va-KJ
	for nsis@ietf.org; Mon, 04 Dec 2006 11:38:57 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kB4GcWu8003677; Mon, 4 Dec 2006 18:38:42 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 15:04:56 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 15:04:56 +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
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Mon, 4 Dec 2006 15:04:56 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC0176A962@esebe199.NOE.Nokia.com>
In-Reply-To: <4573F5A5.9060501@tm.uka.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Support for local domain information in the QSPEC
Thread-Index: AccXjYawD+fDpS4YRbKrEnQyEf9yMAAFr3Rw
From: <john.loughney@nokia.com>
To: <bless@tm.uka.de>
X-OriginalArrivalTime: 04 Dec 2006 13:04:56.0478 (UTC)
	FILETIME=[CBCF3BE0:01C717A4]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061204183842-0DFDEBB0-0E495522/0-0/0-0
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: nsis@ietf.org
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

Hi Roland,

>See below.
>
>> At the previous IETF, Dave Oran proposed that we have a mathmatically

>> complete description of the traffic source.  I believe we have=20
>> consensus on that.
>
>Yes, no doubt. We need that.

Agreed.

>> The open question is how to handle QoS model specific parameters:
>> traffic class, diff serv classes, etc.
>> 1) Include a common set of them as optional parameters in the QSPEC=20
>> document and allow QoSM documents define additional=20
>parameters via an=20
>> IANA registry.
>
>The problem that I see is that if a QoSM-specific parameter is=20
>attached to the QSPEC, the next domain with a different QoSM=20
>cannot interpret that parameter correctly ("apples and=20
>oranges"). Even if both domains support DiffServ, they may=20
>have a totally different set of classes and PHBs, so signaling=20
>the PHB may not be very useful (example: while the QSPEC's=20
>constraints may be supported by some AF class in domain A,=20
>domain B can only use one of it's EF classes for this. So=20
>signaling an AF PHB from domain A to domain B doesn't make=20
>much sense IMHO).
>
>More rationale on that is provided here:
>http://www1.ietf.org/mail-archive/web/nsis/current/msg07206.html

I agree, however, see below:

>> 2) Allow QoSM documents to define their own complete QSPECs, which
are=20
>> used within the QoSM domain, essentially defining an e2e QSPEC and a=20
>> local QSPEC.
>
>The e2e QSPEC should be defined as generic QSPEC in "the QSPEC=20
>document". Local QSPECs should not define their own e2e QSPEC=20
>rather than how the e2e QSPEC is mapped to their local QSPEC=20
>parameters.
>The local QSPEC will usually encapsulate this e2e QSPEC in its=20
>own local QSPEC or have an exact 1:1 mapping so that the e2e=20
>QSPEC is sent to the next domain.
>See also
>http://www1.ietf.org/mail-archive/web/nsis/current/msg07158.html
>for further explanations. Maybe the following picture helps here:
>                    RMD                        Y.1541
>              +-------------+             +-------------+
>   E2E-QSPEC /   RMD-QSPEC   \ E2E-QSPEC /  Y.1541-QSPEC \ E2E-QSPEC
>QNI--------->QNE--->QNE--->QNE---------->QNE--->QNE--->QNE--------->QN
>QNI--------->QNE--->QNE--->QNE---------->QNE--->QNE--->QNE--------->R
>             \               /           \               /
>              +-------------+             +-------------+

In the above example, I still worry what the relation is between the
e2e QSPEC, the RMD-QSPEC and the Y.1541-QSPEC.  I think we would need to
ensure that the RMD & Y.1541 QSPECs will sufficiently meet the e2e-QSPEC
needs, correct?  Do we have the protocol mechanism to ensure that, or
are we assuming the network deployments will take care of that?  I think
that we need text somewhere that talks about how the local QSPEC ensures
that the e2e QSPEC is met.

John

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



From nsis-bounces@ietf.org Mon Dec 04 11:40:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrGqm-0005J1-9R; Mon, 04 Dec 2006 11:39:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrGql-0005Iv-4I
	for nsis@ietf.org; Mon, 04 Dec 2006 11:39:27 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrGqj-0006bA-IC
	for nsis@ietf.org; Mon, 04 Dec 2006 11:39:27 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kB4Gcc6x003861; Mon, 4 Dec 2006 18:39:09 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 15:00:33 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 15:00:33 +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
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Mon, 4 Dec 2006 15:00:33 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC0176A949@esebe199.NOE.Nokia.com>
In-Reply-To: <4573F920.1010309@tm.uka.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Support for local domain information in the QSPEC
Thread-Index: AccXj4kNiTSPXLqiSg+YH91QaODapgAFCzVQ
From: <john.loughney@nokia.com>
To: <bless@tm.uka.de>
X-OriginalArrivalTime: 04 Dec 2006 13:00:33.0628 (UTC)
	FILETIME=[2F2381C0:01C717A4]
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: gash@att.com, nsis@ietf.org
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

>From your mail, Georgios's mail and Jerry's mail - I am not sure if we
all have agreed or not on the role(s) of the QSPEC & the QoS NSLP.

If we have an e2e QSPEC and a local QSPEC, then I think the QoS NSLP
will need to manage how to push & pop the local QSPEC, correct?

I think we would need to specify the following behaviors:

1) e2e QSPEC vs. other QSPEC
2) How the QoS NSLP manages the interaction between these two
3) How the e2e QSPEC and the 'other' QSPEC relate to each other,
   which is manditory to support, which is optional, what to do
   if the e2e QSPEC and the other QSPEC contradict each other.

John=20

>-----Original Message-----
>From: ext Roland Bless [mailto:bless@tm.uka.de]=20
>Sent: 04 December, 2006 12:32
>To: Loughney John (Nokia-NRC/Helsinki)
>Cc: gash@att.com; nsis@ietf.org
>Subject: Re: [NSIS] Support for local domain information in the QSPEC
>
>Hi John,
>
>john.loughney@nokia.com wrote:
>> Thanks for the feedback.  Does the working agree?
>
>No. I'm actually slightly confused by Jerry's posting since=20
>this discussion about options 1) and 2) has nothing to do with=20
>the mails he quoted.
>The quoted mails refer to the fact that the QSPEC template=20
>draft will contain a general description of QSPECs (as=20
>template for QOSM designers that specify their on local=20
>QSPECs) as well as the e2e QSPEC.
>
>My point is: if a DiffServ class parameter is attached, the=20
>QSPEC type should be different from the generic e2e QSPEC.
>So instead of having a QOSM ID we should have a QSPEC ID with=20
>1 being the generic e2e QSPEC which should be understood by all QOSMs.
>
>Regards,
> Roland
>
>>    =20
>---------------------------------------------------------------
>---------
>>     *From:* ext Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>>     *Sent:* 30 November, 2006 14:42
>>     *To:* Loughney John (Nokia-NRC/Helsinki); nsis@ietf.org
>>     *Cc:* Ash, Gerald R (Jerry), ALABS
>>     *Subject:* RE: [NSIS] Support for local domain=20
>information in the=20
>> QSPEC
>>=20
>>     Hi John,
>>     =20
>>     My impression was clearly agreement on option 1, which I think
>>     Georgios originally described in his post at
>>     http://www1.ietf.org/mail-archive/web/nsis/current/msg07213.html
>>     and again at
>>     http://www1.ietf.org/mail-archive/web/nsis/current/msg07232.html
>>     =20
>>     On the thread I think most agreed with Georgios' suggestion, see
>>     http://www1.ietf.org/mail-archive/web/nsis/current/msg07237.html
>>     and then
>>     http://www1.ietf.org/mail-archive/web/nsis/current/msg07238.html
>>     =20
>>     Thanks,
>>     Jerry
>>=20
>>    =20
>---------------------------------------------------------------
>---------
>>     *From:* john.loughney@nokia.com [mailto:john.loughney@nokia.com]
>>     *Sent:* Thursday, November 30, 2006 2:55 AM
>>     *To:* nsis@ietf.org
>>     *Subject:* [NSIS] Support for local domain information in the=20
>> QSPEC
>>=20
>>     I'm trying to tease through all of the mails on this,=20
>and so if my
>>     interpretation is incorrect, please suggest corrective text.
>>=20
>>     At the previous IETF, Dave Oran proposed that we have a
>>     mathmatically complete description of the traffic=20
>source.  I believe
>>     we have consensus on that.
>>=20
>>     The open question is how to handle QoS model specific parameters:
>>     traffic class, diff serv classes, etc.
>>     1) Include a common set of them as optional parameters=20
>in the QSPEC
>>     document and allow QoSM documents define additional=20
>parameters via
>>     an IANA registry.=20
>>=20
>>     2) Allow QoSM documents to define their own complete=20
>QSPECs, which
>>     are used within the QoSM domain, essentially defining an=20
>e2e QSPEC
>>     and a local QSPEC.
>>=20
>>     I think Georgios summarized these quite well in:
>>    =20
>_http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html_
>>=20
>>     I believe that more people were favoring #2.  Of course,=20
>the devil
>>     is always in the details, as there have been discussions=20
>about what
>>     parameters belong where.
>>=20
>>     Comments?
>>     John
>
>

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



From nsis-bounces@ietf.org Mon Dec 04 11:59:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrHA0-0003yP-5C; Mon, 04 Dec 2006 11:59:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrH9y-0003yJ-Tj
	for nsis@ietf.org; Mon, 04 Dec 2006 11:59:18 -0500
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrH9u-0001Gb-C1
	for nsis@ietf.org; Mon, 04 Dec 2006 11:59:18 -0500
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1GrH9h-0001ZO-C6; Mon, 04 Dec 2006 17:59:07 +0100
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by irams1.ira.uni-karlsruhe.de with esmtps 
	id 1GrH9h-0000wj-2k; Mon, 04 Dec 2006 17:59:01 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id B03088766;
	Mon,  4 Dec 2006 17:58:59 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1GrH9f-0007PJ-AT; Mon, 04 Dec 2006 17:58:59 +0100
Message-ID: <457453D2.5090600@tm.uka.de>
Date: Mon, 04 Dec 2006 17:58:58 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: john.loughney@nokia.com
Subject: Re: [NSIS] Support for local domain information in the QSPEC
References: <BAA65A575825454CBB0103267553FCCC0176A949@esebe199.NOE.Nokia.com>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC0176A949@esebe199.NOE.Nokia.com>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.8 (---)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.6 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: gash@att.com, nsis@ietf.org
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

Hi John,

john.loughney@nokia.com wrote:
> From your mail, Georgios's mail and Jerry's mail - I am not sure if we
> all have agreed or not on the role(s) of the QSPEC & the QoS NSLP.
> 
> If we have an e2e QSPEC and a local QSPEC, then I think the QoS NSLP
> will need to manage how to push & pop the local QSPEC, correct?

No. This is what can be solved by having only one QSPEC object conveyed
by the QoS NSLP: either it's a local (or QOSM specific) QSPEC or the
e2e QSPEC. One way to add local parameters is to define a local QSPEC
that encapsulates the e2e QSPEC and contains also parameters that are
relevant locally only. The QoSM defines how this is exactly done. What
must be ensured is that the QoSM understands the e2e QSPEC, i.e.
gets an e2e QSPEC as input, may create its local QSPEC (which
encapsulates the e2e QSPEC) and emits an e2e QSPEC at the egress to
the next domain again. By using this approach, each QOSM can define
what to do with the original e2e QSPEC (e.g. ignore in internal
routers etc.). There is also no need for push & pop.

> I think we would need to specify the following behaviors:
> 
> 1) e2e QSPEC vs. other QSPEC

I would allow both, though other QSPECs must maintain the semantics
of the e2e QSPEC (output must be e2e QSPEC at the egress).

> 2) How the QoS NSLP manages the interaction between these two

No, in my proposal the QOS NSLP doesn't deal with any QSPEC,
it simply delivers exactly one QSPEC object to the RMF and
gets exactly one QSPEC object from it (usually the local QSPEC
will encapsulate the e2e QSPEC to fulfill the above requirement)

> 3) How the e2e QSPEC and the 'other' QSPEC relate to each other,
>    which is manditory to support, which is optional, what to do
>    if the e2e QSPEC and the other QSPEC contradict each other.

Each QOSM that needs a local QSPEC should define a mapping
from the e2e QSPEC to its own local parameters, e.g. QoS classes.
The ingress node will create a local QSPEC (if needed at all)
and populate the QoS class parameter, adapt the available QoS
parameters in the e2e QSPEC and encapsulate it in the local QSPEC.
The egress node will terminate the local QSPEC and extract the
encapsulated e2e QSPEC for further forwarding then.

Regards,
 Roland

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



From nsis-bounces@ietf.org Mon Dec 04 12:12:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrHM4-000562-VR; Mon, 04 Dec 2006 12:11:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrHM4-00055u-5I
	for nsis@ietf.org; Mon, 04 Dec 2006 12:11:48 -0500
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrHM0-00039x-4J
	for nsis@ietf.org; Mon, 04 Dec 2006 12:11:48 -0500
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1GrHLx-0004eY-36; Mon, 04 Dec 2006 18:11:43 +0100
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by irams1.ira.uni-karlsruhe.de with esmtps 
	id 1GrHLw-0002xO-Mw; Mon, 04 Dec 2006 18:11:40 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 2444BB5EF;
	Mon,  4 Dec 2006 18:11:39 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1GrHLu-0007Pq-RE; Mon, 04 Dec 2006 18:11:38 +0100
Message-ID: <457456CA.9010604@tm.uka.de>
Date: Mon, 04 Dec 2006 18:11:38 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: john.loughney@nokia.com
Subject: Re: [NSIS] Support for local domain information in the QSPEC
References: <BAA65A575825454CBB0103267553FCCC0176A962@esebe199.NOE.Nokia.com>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC0176A962@esebe199.NOE.Nokia.com>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.8 (---)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.6 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: nsis@ietf.org
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

Hi John.

john.loughney@nokia.com wrote:
>>                    RMD                        Y.1541
>>              +-------------+             +-------------+
>>   E2E-QSPEC /   RMD-QSPEC   \ E2E-QSPEC /  Y.1541-QSPEC \ E2E-QSPEC
>> QNI--------->QNE--->QNE--->QNE---------->QNE--->QNE--->QNE--------->QN
>> QNI--------->QNE--->QNE--->QNE---------->QNE--->QNE--->QNE--------->R
>>             \               /           \               /
>>              +-------------+             +-------------+
> 
> In the above example, I still worry what the relation is between the
> e2e QSPEC, the RMD-QSPEC and the Y.1541-QSPEC.  I think we would need to

The RMD and Y.1541-QoSMs must define how they will map the e2e QSPEC
to their own model. But this must be done anyways, otherwise I don't
see how this will work at all.

> ensure that the RMD & Y.1541 QSPECs will sufficiently meet the e2e-QSPEC
> needs, correct?  Do we have the protocol mechanism to ensure that, or
> are we assuming the network deployments will take care of that?  I think
> that we need text somewhere that talks about how the local QSPEC ensures
> that the e2e QSPEC is met.

Yes, exactly. As already said in other mails:
Each QOSM should specify a mapping from the e2e QSPEC to its own
model, e.g. service classes. Therefore, if an internal QoSM specific
(or "local") QoSM is needed, one should also define what value goes into
the local parameters. However, a QOSM must understand the e2e QSPEC
and decide whether it can fulfill the request or not. It may change
the available QoS section in the e2e QSPEC accordingly. However,
the output must be an e2e QSPEC again. This can be easily achieved
by carrying the e2e QSPEC encapsulated in the local QSPEC.

The idea is that each QoSM only has to specify how the e2e QSPEC
is used for admission control (1:1 mapping) instead of having each QoSM
understand many others (n:1 mapping), which didn't worked out well as we
discussed in the last weeks (because you cannot compare apples and
oranges).

Regards,
 Roland

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



From nsis-bounces@ietf.org Mon Dec 04 12:24:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrHXS-0005Ky-BF; Mon, 04 Dec 2006 12:23:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrHXR-0005Ks-0R
	for nsis@ietf.org; Mon, 04 Dec 2006 12:23:33 -0500
Received: from mail146.messagelabs.com ([216.82.245.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GrHXO-00052D-PB
	for nsis@ietf.org; Mon, 04 Dec 2006 12:23:32 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-7.tower-146.messagelabs.com!1165253009!10574329!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 13262 invoked from network); 4 Dec 2006 17:23:29 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-7.tower-146.messagelabs.com with SMTP;
	4 Dec 2006 17:23:29 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kB4HNTqK011253; 
	Mon, 4 Dec 2006 12:23:29 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id
	kB4HNNjd011172; Mon, 4 Dec 2006 12:23:23 -0500 (EST)
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
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Mon, 4 Dec 2006 11:23:23 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC7FF2@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <457453D2.5090600@tm.uka.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Support for local domain information in the QSPEC
Thread-Index: AccXxZRmdPRgVnyESRiMbg/ZV8F3XAAAPGfQ
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "Roland Bless" <bless@tm.uka.de>, <john.loughney@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, nsis@ietf.org
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

> > 3) How the e2e QSPEC and the 'other' QSPEC relate to each other,
> >    which is mandatory to support, which is optional, what to do
> >    if the e2e QSPEC and the other QSPEC contradict each other.

> Each QOSM that needs a local QSPEC should define a mapping
> from the e2e QSPEC to its own local parameters, e.g. QoS classes.
> The ingress node will create a local QSPEC (if needed at all)
> and populate the QoS class parameter, adapt the available QoS
> parameters in the e2e QSPEC and encapsulate it in the local QSPEC.
> The egress node will terminate the local QSPEC and extract the
> encapsulated e2e QSPEC for further forwarding then.

Recall that in the current proposal, the concept of 'remapping' QSPEC
parameters, e.g., from QSPEC parameter 1 to QSPEC parameter 2, is
eliminated. =20

A local QSPEC may re-define the same QSPEC parameter in the initiator
QSPEC to an equivalent parameter, e.g., RMD may redefine the TMOD
parameter to an equivalent TMOD parameter that specifies only the peak
rate (i.e., set r=3Dp, b/m to default values).=20

Also specified in the current proposal:
- edge nodes must interpret initiator QSPEC parameters
- local QSPEC must be consistent with initiator QSPEC

Thanks,
Regards,
Jerry=20

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



From nsis-bounces@ietf.org Mon Dec 04 12:38:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrHlE-0000br-RK; Mon, 04 Dec 2006 12:37:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrHlD-0000Z1-9S
	for nsis@ietf.org; Mon, 04 Dec 2006 12:37:47 -0500
Received: from mail146.messagelabs.com ([216.82.245.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GrHlC-00071k-16
	for nsis@ietf.org; Mon, 04 Dec 2006 12:37:47 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-6.tower-146.messagelabs.com!1165253865!10437886!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 18729 invoked from network); 4 Dec 2006 17:37:45 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-6.tower-146.messagelabs.com with SMTP;
	4 Dec 2006 17:37:45 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kB4HbiQU019868; 
	Mon, 4 Dec 2006 12:37:45 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id
	kB4HbeSv019832; Mon, 4 Dec 2006 12:37:40 -0500 (EST)
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
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Mon, 4 Dec 2006 11:37:40 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC7FF3@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <457456CA.9010604@tm.uka.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Support for local domain information in the QSPEC
Thread-Index: AccXx2P5djT0weWJQOuq/6aLZqJSBgAAZ3kw
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "Roland Bless" <bless@tm.uka.de>, <john.loughney@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, nsis@ietf.org
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

Roland, John,

See below.

> -----Original Message-----
> From: Roland Bless [mailto:bless@tm.uka.de]=20
> Sent: Monday, December 04, 2006 12:12 PM
> To: john.loughney@nokia.com
> Cc: nsis@ietf.org
> Subject: Re: [NSIS] Support for local domain information in the QSPEC
>=20
> Hi John.
>=20
> john.loughney@nokia.com wrote:
> >>                    RMD                        Y.1541
> >>              +-------------+             +-------------+
> >>   E2E-QSPEC /   RMD-QSPEC   \ E2E-QSPEC /  Y.1541-QSPEC \ E2E-QSPEC
> >>=20
> QNI--------->QNE--->QNE--->QNE---------->QNE--->QNE--->QNE--------->QN
> >>=20
> QNI--------->QNE--->QNE--->QNE---------->QNE--->QNE--->QNE--------->R
> >>             \               /           \               /
> >>              +-------------+             +-------------+
> >=20
> > In the above example, I still worry what the relation is between the
> > e2e QSPEC, the RMD-QSPEC and the Y.1541-QSPEC.  I think we=20
> would need to
>=20
> The RMD and Y.1541-QoSMs must define how they will map the e2e QSPEC
> to their own model. But this must be done anyways, otherwise I don't
> see how this will work at all.
>=20
> > ensure that the RMD & Y.1541 QSPECs will sufficiently meet=20
> > the e2e-QSPEC
> > needs, correct?  Do we have the protocol mechanism to=20
> > ensure that, or
> > are we assuming the network deployments will take care of=20
> > that?  I think
> > that we need text somewhere that talks about how the local=20
> > QSPEC ensures
> > that the e2e QSPEC is met.
>=20
> Yes, exactly. As already said in other mails:
> Each QOSM should specify a mapping from the e2e QSPEC to its own
> model, e.g. service classes. Therefore, if an internal QoSM specific
> (or "local") QoSM is needed, one should also define what=20
> value goes into
> the local parameters. However, a QOSM must understand the e2e QSPEC
> and decide whether it can fulfill the request or not. It may change
> the available QoS section in the e2e QSPEC accordingly. However,
> the output must be an e2e QSPEC again. This can be easily achieved
> by carrying the e2e QSPEC encapsulated in the local QSPEC.
>=20
> The idea is that each QoSM only has to specify how the e2e QSPEC
> is used for admission control (1:1 mapping) instead of having=20
> each QoSM
> understand many others (n:1 mapping), which didn't worked out=20
> well as we
> discussed in the last weeks (because you cannot compare apples and
> oranges).

I'm concerned that we're straying from what I thought we agreed at
IETF-67.  There is no single generic e2e QSPEC, so it isn't possible IMO
for a QOSM to specify 'how the e2e QSPEC is used' as a general rule.

The rules for local QSPECs I thought we agreed on were these:

- edge nodes in local domains must interpret initiator QSPEC parameters
- edge nodes in local domains can either initiate parallel session with
local QSPEC or encapsulates a local QSPEC on initiator QSPEC
- local QSPEC interpreted by local domain QNEs
- local QSPEC must be consistent with initiator QSPEC (e.g. can re-set
TMOD with r=3Dp, b/m to default)

Thanks,
Regards,
Jerry

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



From nsis-bounces@ietf.org Mon Dec 04 15:26:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrKNz-0006qW-AP; Mon, 04 Dec 2006 15:25:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrKNx-0006lx-HJ
	for nsis@ietf.org; Mon, 04 Dec 2006 15:25:57 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrKNw-0008ME-3W
	for nsis@ietf.org; Mon, 04 Dec 2006 15:25:57 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kB4KOkBw001357; Mon, 4 Dec 2006 22:24:49 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 22:24:42 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 22:24:42 +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
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Mon, 4 Dec 2006 22:24:40 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC017BB95F@esebe199.NOE.Nokia.com>
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC7FF2@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Support for local domain information in the QSPEC
Thread-Index: AccXxZRmdPRgVnyESRiMbg/ZV8F3XAAAPGfQAAboBiA=
From: <john.loughney@nokia.com>
To: <gash@att.com>, <bless@tm.uka.de>
X-OriginalArrivalTime: 04 Dec 2006 20:24:42.0144 (UTC)
	FILETIME=[3AE45A00:01C717E2]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061204222449-05208BB0-427C9F61/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: nsis@ietf.org
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

Hi Jerry,

>> > 3) How the e2e QSPEC and the 'other' QSPEC relate to each other,
>> >    which is mandatory to support, which is optional, what to do
>> >    if the e2e QSPEC and the other QSPEC contradict each other.
>
>> Each QOSM that needs a local QSPEC should define a mapping from the=20
>> e2e QSPEC to its own local parameters, e.g. QoS classes.
>> The ingress node will create a local QSPEC (if needed at all) and=20
>> populate the QoS class parameter, adapt the available QoS parameters=20
>> in the e2e QSPEC and encapsulate it in the local QSPEC.
>> The egress node will terminate the local QSPEC and extract the=20
>> encapsulated e2e QSPEC for further forwarding then.
>
>Recall that in the current proposal, the concept of=20
>'remapping' QSPEC parameters, e.g., from QSPEC parameter 1 to=20
>QSPEC parameter 2, is eliminated. =20
>
>A local QSPEC may re-define the same QSPEC parameter in the=20
>initiator QSPEC to an equivalent parameter, e.g., RMD may=20
>redefine the TMOD parameter to an equivalent TMOD parameter=20
>that specifies only the peak rate (i.e., set r=3Dp, b/m to=20
>default values).=20
>
>Also specified in the current proposal:
>- edge nodes must interpret initiator QSPEC parameters
>- local QSPEC must be consistent with initiator QSPEC

Thanks for this, I think these considerations make sense.
Have you drafted text for QSPEC document that covers this?

thanks,
John

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



From nsis-bounces@ietf.org Mon Dec 04 15:38:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrKZg-0006ea-50; Mon, 04 Dec 2006 15:38:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrKZd-0006aT-FB
	for nsis@ietf.org; Mon, 04 Dec 2006 15:38:01 -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 1GrKYb-0001Nm-6Y
	for nsis@ietf.org; Mon, 04 Dec 2006 15:36:59 -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
	kB4KaF3e014827; Mon, 4 Dec 2006 22:36:41 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 22:36:26 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 22:36:26 +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
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Mon, 4 Dec 2006 22:36:24 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC017BB967@esebe199.NOE.Nokia.com>
In-Reply-To: <003301c7178b$27aed250$4c0d5982@dynamic.ewi.utwente.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Thread-Index: AccXibzeSRBqxbXAQZaS3q4+JEFQsQAAL08wABZNdHA=
From: <john.loughney@nokia.com>
To: <karagian@cs.utwente.nl>, <bless@tm.uka.de>
X-OriginalArrivalTime: 04 Dec 2006 20:36:26.0021 (UTC)
	FILETIME=[DE6F7550:01C717E3]
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: nsis@ietf.org
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

Roland,

Could you summize your proposal, making it easier just to verify
that we can come to consensus on this? It looked like there
was some meandering on the email threads about some parts
of your proposal, so it wasn't clear that we had complete
consensus on your initial proposal.

thanks,
John=20

>-----Original Message-----
>From: ext Georgios Karagiannis [mailto:karagian@cs.utwente.nl]=20
>Sent: 04 December, 2006 12:01
>To: 'Roland Bless'; Loughney John (Nokia-NRC/Helsinki)
>Cc: nsis@ietf.org
>Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
>
>Hi John and Roland
>
>I agree with Roland's proposal is different than (2) that=20
>encapsulates end-to-end QSPEC into a local QSPEC and gives the=20
>possibility to the QoS model to specify which QSPEC parameters=20
>can be ignored.
>
>In the mailing list there was support on using the option=20
>proposed by Roland instead of using option (1) and (2)=20
>proposed by Dave.
>
>Best Regards,
>Georgios
>
>
>> -----Original Message-----
>> From: Roland Bless [mailto:bless@tm.uka.de]
>> Sent: maandag 4 december 2006 10:50
>> To: john.loughney@nokia.com
>> Cc: nsis@ietf.org
>> Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
>>=20
>> Hi John,
>>=20
>> please see below.
>>=20
>> john.loughney@nokia.com wrote:
>> > Dave Oran proposed 3 options for supporting domain-local admission=20
>> > control operation in NSLP/QSPEC in the following mail:
>> >=20
>> > _http://www1.ietf.org/mail-archive/web/nsis/current/msg07178.html_
>> >=20
>> > As stated, these are meant as complete solutions:
>> >=20
>> > 1. Do complete QSPEC stacking, and deal with the issues=20
>around what=20
>> > constraints have to be met by the stacked QSPEC, whether the QSPEC=20
>> > lower in the "stack" is opacified, and what the rules are
>> for pushing,
>> > swapping, and popping.
>> >=20
>> > 2. Allow domain-parameters to be added to a QSPEC on domain
>> entry and
>> > removed on exit. In this option one has to describe whether
>> anything
>> > is opacified and which existing QSPEC parameters get
>> "re-interpreted" if any.
>> >=20
>> > 3. Recurse at the NSLP level, have a separate domain-private NSLP=20
>> > session, and that would contain a domain-private set of paramteres=20
>> > instead of the end-to-end QSPEC. I'll note that this
>> approach allows
>> > (but not requires) the two signaling state machines
>> (end-end and edge-
>> > edge through interior nodes) to be decoupled.
>> >=20
>> > There seems to be consensus that 3 is mandatory, but 2 is still=20
>> > desirable.  Does this mean that 2 would be optional in the=20
>QoS NSLP?
>>=20
>> Option 2 is maybe not covering exactly that what I had in mind, so=20
>> please also consider my follow on:
>> http://www1.ietf.org/mail-archive/web/nsis/current/msg07183.html
>>=20
>> Option 2 could be also realized by having one QSPEC type where=20
>> parameters are added and removed as needed and I guess that's=20
>> different from my proposal.
>>=20
>> Regards,
>>  Roland
>>=20
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>=20
>
>
>

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



From nsis-bounces@ietf.org Mon Dec 04 15:38:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrKZj-0006kw-MA; Mon, 04 Dec 2006 15:38:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrKZe-0006Zm-1O
	for nsis@ietf.org; Mon, 04 Dec 2006 15:38:02 -0500
Received: from mail146.messagelabs.com ([216.82.245.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GrKY7-0001LE-N5
	for nsis@ietf.org; Mon, 04 Dec 2006 15:36:28 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-9.tower-146.messagelabs.com!1165264586!10608205!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 15161 invoked from network); 4 Dec 2006 20:36:26 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-9.tower-146.messagelabs.com with SMTP;
	4 Dec 2006 20:36:26 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kB4KaPea017867; 
	Mon, 4 Dec 2006 15:36:26 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id
	kB4KaFVI017763; Mon, 4 Dec 2006 15:36:21 -0500 (EST)
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
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Mon, 4 Dec 2006 14:36:12 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC7FF5@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC017BB95F@esebe199.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Support for local domain information in the QSPEC
Thread-Index: AccXxZRmdPRgVnyESRiMbg/ZV8F3XAAAPGfQAAboBiAAACq5QA==
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: <john.loughney@nokia.com>, <bless@tm.uka.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, nsis@ietf.org
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

Hi John,=20

> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]=20
> Sent: Monday, December 04, 2006 3:25 PM
> To: Ash, Gerald R (Jerry), ALABS; bless@tm.uka.de
> Cc: nsis@ietf.org
> Subject: RE: [NSIS] Support for local domain information in the QSPEC
>=20
> Hi Jerry,
>=20
> >> > 3) How the e2e QSPEC and the 'other' QSPEC relate to each other,
> >> >    which is mandatory to support, which is optional, what to do
> >> >    if the e2e QSPEC and the other QSPEC contradict each other.
> >
> >> Each QOSM that needs a local QSPEC should define a mapping=20
> >> from the=20
> >> e2e QSPEC to its own local parameters, e.g. QoS classes.
> >> The ingress node will create a local QSPEC (if needed at all) and=20
> >> populate the QoS class parameter, adapt the available QoS=20
> >> parameters=20
> >> in the e2e QSPEC and encapsulate it in the local QSPEC.
> >> The egress node will terminate the local QSPEC and extract the=20
> >> encapsulated e2e QSPEC for further forwarding then.
> >
> >Recall that in the current proposal, the concept of=20
> >'remapping' QSPEC parameters, e.g., from QSPEC parameter 1 to=20
> >QSPEC parameter 2, is eliminated. =20
> >
> >A local QSPEC may re-define the same QSPEC parameter in the=20
> >initiator QSPEC to an equivalent parameter, e.g., RMD may=20
> >redefine the TMOD parameter to an equivalent TMOD parameter=20
> >that specifies only the peak rate (i.e., set r=3Dp, b/m to=20
> >default values).=20
> >
> >Also specified in the current proposal:
> >- edge nodes must interpret initiator QSPEC parameters
> >- local QSPEC must be consistent with initiator QSPEC
>=20
> Thanks for this, I think these considerations make sense.
> Have you drafted text for QSPEC document that covers this?

Yes, the updated text reflects the agreements made at IETF-67 and
subsequently on the list.  The updated QSPEC document is currently under
review by the co-editors, and I hope to submit the update to the I-D
editor later this week.

Thanks,
Jerry

>=20
> thanks,
> John
>=20

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



From nsis-bounces@ietf.org Mon Dec 04 15:47:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrKhs-0000qE-B5; Mon, 04 Dec 2006 15:46:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrKhr-0000q9-Bs
	for nsis@ietf.org; Mon, 04 Dec 2006 15:46:31 -0500
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrKhp-0003LC-U4
	for nsis@ietf.org; Mon, 04 Dec 2006 15:46:31 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kB4Kj8uw028536; Mon, 4 Dec 2006 22:45:18 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 22:45:27 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 22:45:26 +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
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Mon, 4 Dec 2006 22:45:26 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC017BB96A@esebe199.NOE.Nokia.com>
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC7FF5@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Support for local domain information in the QSPEC
Thread-Index: AccXxZRmdPRgVnyESRiMbg/ZV8F3XAAAPGfQAAboBiAAACq5QAAAihBg
From: <john.loughney@nokia.com>
To: <gash@att.com>, <bless@tm.uka.de>
X-OriginalArrivalTime: 04 Dec 2006 20:45:26.0605 (UTC)
	FILETIME=[20A607D0:01C717E5]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061204224519-6F770BB0-664A02DA/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: nsis@ietf.org
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

Hi Jerry,

>> Thanks for this, I think these considerations make sense.
>> Have you drafted text for QSPEC document that covers this?
>
>Yes, the updated text reflects the agreements made at IETF-67=20
>and subsequently on the list.  The updated QSPEC document is=20
>currently under review by the co-editors, and I hope to submit=20
>the update to the I-D editor later this week.

Good, having text helps.  Reviewing the email threads was a bit
unclear, because there were some places where it appeared that
people were agreeing to different things, and so forth.
=20
thanks,
John

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



From nsis-bounces@ietf.org Tue Dec 05 10:55:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrcdH-0007tu-1V; Tue, 05 Dec 2006 10:54:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrcdF-0007tp-AW
	for nsis@ietf.org; Tue, 05 Dec 2006 10:54:57 -0500
Received: from mclmx.mail.saic.com ([149.8.64.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrcdD-0006pe-Us
	for nsis@ietf.org; Tue, 05 Dec 2006 10:54:57 -0500
Received: from 0015-its-ieg01.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx.mail.saic.com; Tue, 5 Dec 2006 10:54:47 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
	by 0015-its-ieg01.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006120510544707985 ; Tue, 05 Dec 2006 10:54:47 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service
	(5.5.2657.72) id <XWKQGY04>; Tue, 5 Dec 2006 10:54:47 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426230F04@0591-ITS-EXMP02.us.saic.com>
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: Roland Bless <bless@tm.uka.de>,
    john.loughney@nokia.com
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Tue, 5 Dec 2006 10:54:40 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
content-class: urn:content-classes:message
x-mimeole: Produced By Microsoft Exchange V6.5
x-originalarrivaltime: 05 Dec 2006 15:54:41.0242 (UTC)
	FILETIME=[ACD0A3A0:01C71885]
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: gash@att.com, nsis@ietf.org
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

Hi, John, Roland, and all:

Yes, we agree with Roland's proposal: Only one (generic) QSPEC object
e2e. Nothing else is needed in this "generic" draft.

Each QOSM draft will deal with its own local QSPEC object including
mapping between its own QOSM-specific local QSPEC and the "generic" QOS
object. Each QOSM needs to do a lot of things because they are "apples"
and "oranges." 

For example, so-called QOS-SLAs like Y.1541, DSTE, and 3GPP-Y.1541 will
have to do a lot of things, not limited to, as follows:

1. They have to find the proper signaling messages that need to be used
for NSIS-QOS signaling messages as they do not have their own.

2. They many even need to have some extensions in NSIS QOS signaling
messages here and there. Let them sort out those things.

3. They may need to see how their QOSM signaling messages can be used
with SIP call signaling messages for, say audio codec negotiations, as
they do not have any flexibility for negotiations other than some only
"one" fixed QOS-class that can be used for real-time services like
audio.

4. Item 3 clearly reveals the most important part of those QOS SLAs: a.
Bad Part and b. Good Part. 

4a. The bad part is this: The use of QOS signaling messages for "QOS
negotiations" of QOS-SLAs (Y.1541, DSTE, and 3GPP-Y.1541) is completely
UNECESSARY as there is NOTHING to negotiate because there is only fixed
value (one QOS Class) for QOS SLAs. If they want to create those
signaling messages, those will be wastage of resources for nothing
(i.e., at the end of all audio codec negotiations by SIP signaling
messages, there is only one QOS class).

4b. The good part is this: Like all SLAs, the Y.1541, DSTE, and
3GPP-Y.1541 QOS SLAs also want to AVOID unnecessary NEGOTIATION because
SLA has already been greed upon: Only one fixed value-based QOS class
for say real-time audio service. 

5. The question is this: How do the routers will implement item 4b? The
edge routers that implement the QOS SLA (say Y.1541) will just examine
the "general" QSPEC template and if the values of the QOS parameters
meet the bound of say Y.1541 QOS-SLA (e.g., delay < 50 msecs for audio
real-time services), it will accept the call. Otherwise, it will reject
the call.

6. The interesting question is this: How do the routers in item 5 know
which QOS class of say Y.1541 SLA? There are many solutions available
for this: i. Use OPS protocol that help to do so using VoIP call
signaling messages (SIP, H,323) mapping into IP layer, ii. Mark IP flows
agreed upon by ISPs as a part of SLA, iii. Manipulation of TOS agreed
upon by ISPs as a part of SLA, and iv. Many other schemes.

The key of the above explanations is this: If we use item 4a using some
extensions in the "generic" QSPEC draft (and even may require some other
NSIS QOS signaling messages as well) extending some signaling messages
as QOS-SLAs (Y.1541, DSTE, and 3GPP-Y.1541)do not have own signaling
messages, it is completely UNNECESSARY because their fundamental goal
has been item 4b.

If it is not true, why did these QOS-SLAs (Y.1541, DSTE, and
3GPP-Y.1541) create their own QOS signaling messages like RSVP,
DiffServ, and IntServ QOS Models?

Best regards,
Radhika

-----Original Message-----
From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of
Roland Bless
Sent: Monday, December 04, 2006 11:59 AM
To: john.loughney@nokia.com
Cc: gash@att.com; nsis@ietf.org
Subject: Re: [NSIS] Support for local domain information in the QSPEC

Hi John,

john.loughney@nokia.com wrote:
> From your mail, Georgios's mail and Jerry's mail - I am not sure if we
> all have agreed or not on the role(s) of the QSPEC & the QoS NSLP.
> 
> If we have an e2e QSPEC and a local QSPEC, then I think the QoS NSLP
> will need to manage how to push & pop the local QSPEC, correct?

No. This is what can be solved by having only one QSPEC object conveyed
by the QoS NSLP: either it's a local (or QOSM specific) QSPEC or the
e2e QSPEC. One way to add local parameters is to define a local QSPEC
that encapsulates the e2e QSPEC and contains also parameters that are
relevant locally only. The QoSM defines how this is exactly done. What
must be ensured is that the QoSM understands the e2e QSPEC, i.e.
gets an e2e QSPEC as input, may create its local QSPEC (which
encapsulates the e2e QSPEC) and emits an e2e QSPEC at the egress to
the next domain again. By using this approach, each QOSM can define
what to do with the original e2e QSPEC (e.g. ignore in internal
routers etc.). There is also no need for push & pop.

> I think we would need to specify the following behaviors:
> 
> 1) e2e QSPEC vs. other QSPEC

I would allow both, though other QSPECs must maintain the semantics
of the e2e QSPEC (output must be e2e QSPEC at the egress).

> 2) How the QoS NSLP manages the interaction between these two

No, in my proposal the QOS NSLP doesn't deal with any QSPEC,
it simply delivers exactly one QSPEC object to the RMF and
gets exactly one QSPEC object from it (usually the local QSPEC
will encapsulate the e2e QSPEC to fulfill the above requirement)

> 3) How the e2e QSPEC and the 'other' QSPEC relate to each other,
>    which is manditory to support, which is optional, what to do
>    if the e2e QSPEC and the other QSPEC contradict each other.

Each QOSM that needs a local QSPEC should define a mapping
from the e2e QSPEC to its own local parameters, e.g. QoS classes.
The ingress node will create a local QSPEC (if needed at all)
and populate the QoS class parameter, adapt the available QoS
parameters in the e2e QSPEC and encapsulate it in the local QSPEC.
The egress node will terminate the local QSPEC and extract the
encapsulated e2e QSPEC for further forwarding then.

Regards,
 Roland


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



From nsis-bounces@ietf.org Tue Dec 05 13:34:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Grf7D-0002Fg-AJ; Tue, 05 Dec 2006 13:34:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Grf7C-0002Fb-6l
	for nsis@ietf.org; Tue, 05 Dec 2006 13:34:02 -0500
Received: from mclmx2.mail.saic.com ([149.8.64.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Grf7A-000597-QG
	for nsis@ietf.org; Tue, 05 Dec 2006 13:34:02 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx2.mail.saic.com; Tue, 5 Dec 2006 13:33:55 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006120513335321194 ; Tue, 05 Dec 2006 13:33:54 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service
	(5.5.2657.72) id <XWKQHD7T>; Tue, 5 Dec 2006 13:33:46 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426230F06@0591-ITS-EXMP02.us.saic.com>
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: Roland Bless <bless@tm.uka.de>,
    john.loughney@nokia.com
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Tue, 5 Dec 2006 13:33:37 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
content-class: urn:content-classes:message
x-mimeole: Produced By Microsoft Exchange V6.5
x-originalarrivaltime: 05 Dec 2006 18:33:38.0681 (UTC)
	FILETIME=[E1925690:01C7189B]
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Cc: nsis@ietf.org
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

Roland and all:

Roland is right. I am using Roland's following figure why it is
unnecessary for us to worry about Y.1541 QOS SLA.

                     RMD                        Y.1541
               +-------------+             +-------------+
    E2E-QSPEC /   RMD-QSPEC   \ E2E-QSPEC /  Y.1541-QSPEC \ E2E-QSPEC
QNI---------->QNE--->QNE--->QNE-------->[R1]-QNE--->QNE-->[R2]------>QNR
              \               /           \               /
               +-------------+             +-------------+

Please note that I have used two routers R1 and R2 in the network where
Y.1451 QOS-SLA has been implemented. Please also note that, like all
SLAs, Y.1451 QOS SLA is also non-negotiable as QOS classes are fixed per
application [e.g., voice = class 1 (delay <50ms); video, IM = class 2
(delay < 100ms); non-real-time data = class 3 (delay <500ms)].

All routers including R1 and R2 of SLA (Y.1451) know that they have to
implement Y.1451 SLA. So, they do not need to do anything to negotiate
so far QSPEC is concerned. That is, there is no need for Y.1451-QSPEC
template because the general E2E-QSPEC template is good enough. How?

Let me explain as follows:

1. E2E-QSPEC template will have the QOS parameters (delay, jitter, loss)
and the end system will specify their values. Once the values are known,
Y.1451-aware router R1 will just need to examine the values of those QOS
parameters. Examining those values of QOS parameters, R1 can decide
whether to accept or reject the call because it has nothing to
negotiate.

2. The thing that is needed for Y.1451-aware router R1 in item 1 is to
know which application has requested this. It is very interesting to map
between the application layer and the IP layer. In another email, I have
explained how fixed-value-based SLAs are implemented: OSP protocol
(SIP/H.323 <-> IP), IP TOS-bits, IP-flow-ID, and others. This mapping is
outside the scope of the NSIS WG unless Y.1451-SLA ISPs negotiate among
themselves which path they need to use. NSIS WG will assume somehow
there is a way to do so. Y.1451-QOSM is the right place that Y.1451-QOS
SLA folks will use all those schemes for implementations/mapping.

3. If Y.1451-QOS SLA folks want to create their own QSPEC templates and
want extend the generic QSPEC template, it will be messy. Not only this,
let us ask them one fundamental question: If they avoid to create QOS
signaling messages to avoid negotiations in the first place, why do they
NOW want to create extensions in QSPEC template signaling messages to
carry those "value specific non-negotiable" QOS class? Is it NOT a step
backward in the first place? How does it help them? Why do they not use
one of those "very simplistic" things as identified in item 2?

The bottom line is this:

Let the Y.1451-QOS SLA folks justify why do they want QOS signaling
messages in extending the "generic" QSPEC template for implementation
before doing any further works in this regard in Y.1451-QOSM draft?

Let the Y.1451-QOS SLA folks draw a simple call flow using the following
simplified figure as shown below justifying how Y.1451-QPSEC templates
are helpful instead of using the "generic" QSPEC template:


                   Y.1541
               +-------------+
    E2E-QSPEC /  Y.1541-QSPEC \ E2E-QSPEC
-------->[R1]-QNE--->QNE-->[R2]------>QNR
              \               /           
               +-------------+            

The Y.1451-QOS SLA folks are also being advised to use a SIP call flows
on the top of the network layer NSIS QOS signaling flows. Then they will
gain more insights why they do not need any QSPEC template of their own.

We think that the Y.1451-QOS SLA folks will create their lives miserable
if they use their own QSPEC template if they do NOT use one of the paths
as shown in items 1, 2, and 3.

Best regards,
Radhika

-----Original Message-----
From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of
Roland Bless
Sent: Monday, December 04, 2006 5:17 AM
To: john.loughney@nokia.com
Cc: nsis@ietf.org
Subject: Re: [NSIS] Support for local domain information in the QSPEC

Hi John and all,

john.loughney@nokia.com wrote:
> I'm trying to tease through all of the mails on this, and so if my
> interpretation is incorrect, please suggest corrective text.

See below.

> At the previous IETF, Dave Oran proposed that we have a mathmatically
> complete description of the traffic source.  I believe we have
consensus
> on that.

Yes, no doubt. We need that.

> The open question is how to handle QoS model specific parameters:
> traffic class, diff serv classes, etc.
> 1) Include a common set of them as optional parameters in the QSPEC
> document and allow QoSM documents define additional parameters via an
> IANA registry. 

The problem that I see is that if a QoSM-specific parameter is attached
to the QSPEC, the next domain with a different QoSM cannot interpret
that parameter correctly ("apples and oranges"). Even if both domains
support DiffServ, they may have a totally different set of classes and
PHBs, so signaling the PHB may not be very useful (example: while the
QSPEC's constraints may be supported by some AF class in domain A,
domain B can only use one of it's EF classes for this. So signaling
an AF PHB from domain A to domain B doesn't make much sense IMHO).

More rationale on that is provided here:
http://www1.ietf.org/mail-archive/web/nsis/current/msg07206.html

> 2) Allow QoSM documents to define their own complete QSPECs, which are
> used within the QoSM domain, essentially defining an e2e QSPEC and a
> local QSPEC.

The e2e QSPEC should be defined as generic QSPEC in "the QSPEC
document". Local QSPECs should not define their own e2e QSPEC
rather than how the e2e QSPEC is mapped to their local QSPEC
parameters.
The local QSPEC will usually encapsulate this e2e QSPEC
in its own local QSPEC or have an exact 1:1 mapping so that the
e2e QSPEC is sent to the next domain.
See also
http://www1.ietf.org/mail-archive/web/nsis/current/msg07158.html
for further explanations. Maybe the following picture helps here:
                     RMD                        Y.1541
               +-------------+             +-------------+
    E2E-QSPEC /   RMD-QSPEC   \ E2E-QSPEC /  Y.1541-QSPEC \ E2E-QSPEC
QNI---------->QNE--->QNE--->QNE---------->QNE--->QNE--->QNE---------->QN
R
              \               /           \               /
               +-------------+             +-------------+


> I think Georgios summarized these quite well in:
> _http://www1.ietf.org/mail-archive/web/nsis/current/msg07164.html_
> 
> I believe that more people were favoring #2.  Of course, the devil is
> always in the details, as there have been discussions about what
> parameters belong where.

Regards,
 Roland


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



From nsis-bounces@ietf.org Wed Dec 06 03:18:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Grrxu-0001cn-Oi; Wed, 06 Dec 2006 03:17:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Grrxu-0001cc-5z
	for nsis@ietf.org; Wed, 06 Dec 2006 03:17:18 -0500
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Grrxr-0007Xj-Of
	for nsis@ietf.org; Wed, 06 Dec 2006 03:17:18 -0500
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1Grrxh-0000l3-55; Wed, 06 Dec 2006 09:17:06 +0100
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by irams1.ira.uni-karlsruhe.de with esmtps 
	id 1Grrxg-0003qt-Mn; Wed, 06 Dec 2006 09:17:04 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 1BD9EA829;
	Wed,  6 Dec 2006 09:17:04 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1Grrxf-0001lu-M8; Wed, 06 Dec 2006 09:17:03 +0100
Message-ID: <45767C7F.20509@tm.uka.de>
Date: Wed, 06 Dec 2006 09:17:03 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: john.loughney@nokia.com
Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
References: <BAA65A575825454CBB0103267553FCCC017BB967@esebe199.NOE.Nokia.com>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC017BB967@esebe199.NOE.Nokia.com>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.8 (---)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.6 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, karagian@cs.utwente.nl,
	nsis@ietf.org
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

Hi John,

john.loughney@nokia.com wrote:
> Could you summize your proposal, making it easier just to verify
> that we can come to consensus on this? It looked like there
> was some meandering on the email threads about some parts
> of your proposal, so it wasn't clear that we had complete
> consensus on your initial proposal.

Ok, I'll try once again.

1. each QSPEC has a type (QSPEC-ID) instead of this QOSM-ID
   because I think that some QSPECs are applicable to more
   than one QOSM (e.g., the e2e QSPEC) and some QOSM may understand
   more than one QSPEC type.

2. Instead of supporting stacking QSPEC objects in QoS-NSLP
   I suggest to have only a "single" QSPEC object in a QoS-NSLP.
   If one wants to carry other QSPECs transparently or simply
   add parameters of local meaning etc. one could
   simply define an "encapsulation" for its own QSPEC type
   like this:
----------------------------------
| QSPEC-Type = RMD-QSPEC         |  Common QSPEC header
+================================+\
|  RMD-specific Parameter 1      | \
+--------------------------------+  \
|             ....               |   local QSPEC parameters
+--------------------------------+  /
|  RMD-specific Parameter n      | /
+--------------------------------+/
| +----------------------------+ |
| | QSPEC-Type = E2E QSPEC     | |
| +============================+ |
| |                            | | Encapsulated "external" QSPEC
| |          ....              | |
| +----------------------------+ |
+--------------------------------+

That's essentially the proposal to remove stacking
while achieving the same functionality with encapsulation.

This simplifies QoS NSLP operation and implementation,
because there are less error cases at the interface from
QoS-NSLP to the RMF and not every QoSM requires its own QSPEC
so stacking would be superfluous for them.

Still unclear?

Regards,
 Roland

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



From nsis-bounces@ietf.org Wed Dec 06 05:10:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrtiX-0003Jf-RL; Wed, 06 Dec 2006 05:09:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrtiW-0003J8-H1
	for nsis@ietf.org; Wed, 06 Dec 2006 05:09:32 -0500
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrtiU-00077k-5W
	for nsis@ietf.org; Wed, 06 Dec 2006 05:09:32 -0500
Received: from sbz-31.cs.helsinki.fi (sbz-31.cs.helsinki.fi [128.214.9.99])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Wed, 06 Dec 2006 12:09:25 +0200
	id 000AFD5E.457696D5.00003311
Date: Wed, 6 Dec 2006 12:09:25 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: nsis@ietf.org
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
In-Reply-To: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
Message-ID: <Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
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


Dear all,

I sent the following request for feedback two weeks ago. No comments have 
been raised. I will wait until this Friday, then submit the draft.

Jukka

On Tue, 21 Nov 2006, Jukka MJ Manner wrote:

> 
> Hi all,
> 
> I have done all the edits I had in my list to the QoS NSLP spec, the main 
> points are in recent thread with Roland. From the url below you can find 
> the current draft v. "13-pre1" and a diff to v. 12.
> 
> http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
> 
> A direct link to the diff:
> 
> http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos-nslp-12-from-3-pre1.diff.html
> 
> 
> I would appreciate comments on the changes I did (what is wrong, what I 
> missed, etc.).
> 
> 
> I still have one problem with the spec, namely the way the NSLP suggests 
> to handle mobility and path changes. I think we need to review that 
> statement, because it seems like a "hack" (playing with the RSN value), 
> and not really useful. And the interactions with GIST look partly wrong. 
> The folks working on the mobility draft (me included) could comment. The 
> section I'm talking about is 3.2.10, especially 3.2.10.2, in the v.12 
> draft.
> 
> BR,
> Jukka
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 

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



From nsis-bounces@ietf.org Wed Dec 06 08:21:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Grwi9-0005ut-Ee; Wed, 06 Dec 2006 08:21:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Grwi7-0005u6-Ss
	for nsis@ietf.org; Wed, 06 Dec 2006 08:21:19 -0500
Received: from mo-p00-ob.rzone.de ([81.169.146.162])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Grwi6-0002Ms-GO
	for nsis@ietf.org; Wed, 06 Dec 2006 08:21:19 -0500
Received: from [192.168.178.33]
	(p5484B9E1.dip0.t-ipconnect.de [84.132.185.225])
	by post.webmailer.de (mrclete mo23) (RZmta 3.7)	with ESMTP	id
	iB6DCJ2Q0624aB; Wed, 6 Dec 2006 14:21:10 +0100 (MET)
Date: Wed, 6 Dec 2006 14:21:10 +0100 (MET)
Message-ID: <4576C336.8020406@cs.uni-goettingen.de>
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Xiaoming Fu <fu@cs.uni-goettingen.de>
Subject: Re: [NSIS] Question to the CL QoS Model authors
References: <Pine.LNX.4.64.0610102342390.21326@sbz-31.cs.Helsinki.FI>
	<452C87AD.1080702@cs.uni-goettingen.de>
In-Reply-To: <452C87AD.1080702@cs.uni-goettingen.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RZG-AUTH: gNvC5ZWVA5d1mEPfeXALj6w=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: Jukka MJ Manner <jmanner@cs.Helsinki.FI>, nsis@ietf.org, "Kappler,
	Cornelia" <cornelia.kappler@siemens.com>
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

Hi,

with the proposed e2e QSPEC object remapping is not necessary any more. Since CLS
relies on Token Bucket as the only parameter, no local QSPEC needs to be defined.
I assume QoSClass and Priority is ignored by CLS QOSM from now on. Still interesting
could be two different queues to handle CL and Best Effort traffic.

The interoperation with RSVP is another open issue. The table in section 7 shows
a mapping of objects and parameters between QoS NSLP and RSVP.

A RSVP PATH message contains a Sender TSpec and an ADSpec object. The Sender TSpec
describes the traffic specification while the ADSpec probes for available Bandwidth.
The ADSpec can be mapped to <QoS Available> (Bandwidth) and the Sender TSpec +
FlowSpec to <QoS Desired> and opt. <Minimum QoS> (both Token Bucket).

Compared to the table in section 6.4.2 of the QSPEC Template the <QoS Desired> is
missing in the QUERY and RESERVE message. How does this fit together? The Object
Combination is not optional from my understanding. The CLS-draft mentions that
Sender-TSpec and ADSpec cannot be mapped easily. Does this mean multicast flows
and merged FlowSpecs?

Where is the difference between one-pass, One Pass with Advertising(OPWA) and the
two-pass reservation model? Are there more? When the Sender includes an ADSpec in the
Path message, it's OPWA, without ADSpec it's one-pass. The Receiver-Initiated Reservation
is two-pass?

There are three examples in Appendix B.2 showing how the QSPEC in a QUERY message
can be composed and interpreted.

1.The Sender (QNR) collects information about the available bandwidth with a QUERY
message containing <QoS Available>. The Receiver (QNI) generates a RESERVE message
with <QoS Desired> based on <QoS Available>. The Sender (QNR) sends back a RESPONSE
with <QoS Reserved> which carries information about the performed reservation.
According to the QSPEC Procedures <QoS Available> is missing in the QUERY and RESERVE.

The next two examples are not quite clear to me.
2.  When the QNR composes the <QoS Desired> based on <QoS Available> it uses a Token
Bucket (QNE-readonly). A Resource QUERY can get <QoS Available>. I'm not sure if this
is draft-conform: The QNR could pretend to be a QNI for the QUERY to make then a
Receiver-Initiated Reservation as QNR. From my understanding a QNR can't do a Resource
QUERY along the path to the QNI.

3. Peak-Rate can be mapped to Bandwidth. The Traffic object contains both, Token Bucket
and Bandwidth. Using Bandwidth avoids mapping and interpreting certain fields of TB,
but each QNE along the path should know how to deal with the new <QoS Available>.

Comments?

Bernd






Xiaoming Fu wrote:
> Hi Jukka,
> 
> The CLS draft is actually a remapping of RSVP CLS parameters (and 
> procedures) to NSIS.
> 
In the table in section 7 <QoS Desired> (QUERY and RESERVE) is not mentioned
as in the QSPEC Procedures. The same with <QoS Available> for RESPONSE. Also
in section 5.3 <QoS Desired> is not mentioned. Are these parameter optional? > In the QSPEC-1 parameters specified in [draft-ietf-nsis-qspec], there
> are the following two types:
> 
> - <Excess Treatment> is an optional parameter in QNI, namely it can be 
> included or excluded in the CLS control information. If it is included 
> in a message, then CLS QNE must interpret and populate it.
> 
> - <QoS Desired> and <QoS Reserved> are mandatory for all (QNI QNEs QNR)
> including other QoSMs; <QoS Available> mandatory for receiver-initiated 
> reservation, but optional for sender-initiated reservation.
> 
> however, we didn't discuss how exactly the objects other than Token 
> Bucket(s) inside the QoS Desired etc should be handled. We thought a QNE 
> doesn't need to include (for QNI/QNR) nor interpret any of them.
> 
> Any remarks on this?
> Xiaoming
> 
> Jukka MJ Manner wrote:
> 
>> Hi Xiaoming and Cornelia,
>>
>> I was wondering if you have some ideas on how the CL QoS Model would 
>> handle all the current QSPEC-1 parameters? Your draft lists that as an 
>> open issue.
>>
>> Cheers,
>> Jukka
>>
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
> 
> 


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



From nsis-bounces@ietf.org Wed Dec 06 09:48:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gry43-000636-Dt; Wed, 06 Dec 2006 09:48:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gry42-00060N-A5
	for nsis@ietf.org; Wed, 06 Dec 2006 09:48:02 -0500
Received: from rsys002x.roke.co.uk ([193.118.201.109])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gry3w-0007IA-KX
	for nsis@ietf.org; Wed, 06 Dec 2006 09:48:02 -0500
Received: from rsys005a.comm.ad.roke.co.uk (rsys005a [193.118.193.85])
	by rsys002x.roke.co.uk (8.13.1/8.13.1) with ESMTP id kB6ElR97028814;
	Wed, 6 Dec 2006 14:47:28 GMT
Received: from [193.118.197.186] ([193.118.197.186]) by
	rsys005a.comm.ad.roke.co.uk with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 6 Dec 2006 14:47:27 +0000
Message-ID: <4576D7FF.90203@roke.co.uk>
Date: Wed, 06 Dec 2006 14:47:27 +0000
From: Andrew McDonald <andrew.mcdonald@roke.co.uk>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>, nsis@ietf.org
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
In-Reply-To: <Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Dec 2006 14:47:27.0735 (UTC)
	FILETIME=[73121070:01C71945]
X-MailScanner-roke-co-uk: Found to be clean
X-MailScanner-roke-co-uk-SpamCheck: 
X-MailScanner-From: andrew.mcdonald@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Cc: 
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

Hi,

A few comments (complete with suggested changes).

Jukka: I sent you the first couple directly, and then decided it was 
probably a good idea to send them all to the list.

A minor rewording suggestion in 4.8. I don't think the problem is about 
finding a P-QNE, it is more fundamentally (at a GIST level) about 
finding a next upstream peer (since there could be more than one hop to 
the P-QNE).

Current (13-pre1) text:
-- 
    For incoming data flows, the end host is the QNI, and it sends a
    RESERVE towards the data sender with the PROXY scope flag set. Here
    the end host sets the MRI so that it indicates the end host as the
    receiver of the data, and sets the D-flag.

    Now GIST will seek to route the RESERVE using reverse routing. If
    there is only one P-QNE in the domain, it is trivial for GIST to
    forward the RESERVE to the P-QNE. If there are more than one P-QNEs,
    GIST may be able to find the correct QNE for the reserve route, but
    may also reply with an error indicating destination unreachable,
    e.g., if there are multiple inbound routes and the data flow may
    arrive from either route - GIST does not send the RESERVE to multiple
    P-QNEs. See the GIST spec [I-D.ietf-nsis-ntlp] for more information
    on GIST's ability to do reverse routing.
-- 

Proposed text:
-- 
For incoming data flows, the end host is the QNI, and it sends a RESERVE 
towards the data sender with the PROXY scope flag set. Here the end host 
sets the MRI so that it indicates the end host as the receiver of the 
data, and sets the D-flag.

GIST is able to send messages towards the data sender if there is 
existing message routing state or it is able to use the Upstream Q-mode 
Encapsulation. In some cases GIST will be unable to determine the 
appropriate next hop for the message, and so will indicate a failure to 
deliver it (by sending an error message). This may occur, for example, 
if GIST attempts to determine an upstream next hop and there are 
multiple possible inbound routes that could be used.
-- 

Another minor one on 5.1.1:
13-pre1 text:
--
    The ACK flag is usefull when a QNE wants to make sure the messages
    received by the downstream QNE are truly processed, even when GIST
    continues to work. This is usefull for faster dead peer diagnostics
    on the NSLP layer. Reliable transmission of messages between two QoS
    NSLP peer should be handled by GIST, not the NSLP by itself.
--
I'm not sure what "even when GIST continues to work" means.
(and 'usefull' has only one 'l')

Would the following be clearer?
--
The ACK flag is useful when a QNE wants to make sure the messages 
received by the downstream QNE are truly processed by the QoS NSLP, not 
just delivered by GIST. This is useful for faster dead peer diagnostics 
on the NSLP layer. Reliable transmission of messages between two QoS 
NSLP peer should be handled by GIST, not the NSLP by itself.
--
5.1.2.1 BNF says:
    RESERVE = COMMON_HEADER
              RSN [ RII ] [ REFRESH_PERIOD ] [ *BOUND_SESSION_ID ]
              [ SESSION_ID_LIST ] [ RSN_LIST ]
              [ [ PACKET_CLASSIFIER ] QSPEC ]

(and similarly for RESPONSE)

This says that you can have an RSN_LIST with no SESSION_ID_LIST. That 
doesn't sound right to me. Is the following correct:

    RESERVE = COMMON_HEADER
              RSN [ RII ] [ REFRESH_PERIOD ] [ *BOUND_SESSION_ID ]
              [ SESSION_ID_LIST [ RSN_LIST ] ]
              [ [ PACKET_CLASSIFIER ] QSPEC ]

and for RESPONSE:
  RESPONSE = COMMON_HEADER
               [ RII / RSN ] INFO_SPEC [ SESSION_ID_LIST [ RSN_LIST ] ]
               [ QSPEC ]

i.e. if you include a SESSION_ID_LIST you can also include an RSN_LIST

Could the object formats in 5.1.3.7/5.1.3.8 also be made a bit clearer 
(more detailed), i.e.:

current 13-pre1:
     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                                                               |
    +                                                               +
    |                                                               |
    +                          Session IDs                          +
    |                                                               |
    +                                                               +
    |                                                               |
    /                                                               /
    |                                                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

suggestion:
     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                                                               |
    +                                                               +
    |                                                               |
    +                         Session ID 1                          +
    |                                                               |
    +                                                               +
    |                                                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    :                                                               :
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                                                               |
    +                                                               +
    |                                                               |
    +                         Session ID n                          +
    |                                                               |
    +                                                               +
    |                                                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

(following pattern in some of the GIST formats)

Similarly in RSN_LIST:
13-pre1:
     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                                                               |
    /                  Reservation Sequence Numbers                 /
    |                                                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

I suspect you need the Epoch Identifier (I've only thought about this 
very briefly), not just the 'raw' RSN (the term 'Reservation Sequence 
Numbers' is possibly a little vague here). However, since the Epoch 
Identifier is for the entire QNE, not per-peer, so you only need one.

Suggestion:
     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                       Epoch Identifier                        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |             Reservation Sequence Number 1 (RSN1)              |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    :                                                               :
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |             Reservation Sequence Number n (RSNn)              |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


In a number of places there are some "RNS" typos that should be "RSN"

5.3.6: "uknown" -> "unknown"
5.3.6: "sessiond" -> "Session ID"

regards,
Andrew

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



From nsis-bounces@ietf.org Wed Dec 06 10:50:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Grz1E-0001tx-29; Wed, 06 Dec 2006 10:49:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Grz1C-0001rn-5t
	for nsis@ietf.org; Wed, 06 Dec 2006 10:49:10 -0500
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Grz18-0001tZ-SO
	for nsis@ietf.org; Wed, 06 Dec 2006 10:49:10 -0500
Received: from sbz-31.cs.helsinki.fi (sbz-31.cs.helsinki.fi [128.214.9.99])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Wed, 06 Dec 2006 17:49:05 +0200
	id 000AFD55.4576E671.0000159F
Date: Wed, 6 Dec 2006 17:49:05 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Andrew McDonald <andrew.mcdonald@roke.co.uk>
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
In-Reply-To: <4576D7FF.90203@roke.co.uk>
Message-ID: <Pine.LNX.4.64.0612061748430.6831@sbz-31.cs.Helsinki.FI>
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
	<4576D7FF.90203@roke.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: nsis@ietf.org
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


Thanks, Andrew, will change all.

Jukka

On Wed, 6 Dec 2006, Andrew McDonald wrote:

> Hi,
> 
> A few comments (complete with suggested changes).
> 
> Jukka: I sent you the first couple directly, and then decided it was probably
> a good idea to send them all to the list.
> 
> A minor rewording suggestion in 4.8. I don't think the problem is about
> finding a P-QNE, it is more fundamentally (at a GIST level) about finding a
> next upstream peer (since there could be more than one hop to the P-QNE).
> 
> Current (13-pre1) text:
> 

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



From nsis-bounces@ietf.org Wed Dec 06 17:06:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gs4tb-0005K1-Q1; Wed, 06 Dec 2006 17:05:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gs4ta-0005Hw-Ex
	for nsis@ietf.org; Wed, 06 Dec 2006 17:05:42 -0500
Received: from mo-p00-ob.rzone.de ([81.169.146.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gs4tX-0007Ll-UI
	for nsis@ietf.org; Wed, 06 Dec 2006 17:05:42 -0500
Received: from [192.168.178.33]
	(p5484B9E1.dip0.t-ipconnect.de [84.132.185.225])
	by post.webmailer.de (mrclete mo13) (RZmta 3.8)	with ESMTP	id
	iB6GhfKr00e4fA; Wed, 6 Dec 2006 23:05:37 +0100 (MET)
Date: Wed, 6 Dec 2006 23:05:37 +0100 (MET)
Message-ID: <45773E20.3040000@cs.uni-goettingen.de>
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: nsis@ietf.org
Subject: Re: [NSIS] Question to the CL QoS Model authors
References: <Pine.LNX.4.64.0610102342390.21326@sbz-31.cs.Helsinki.FI>
	<452C87AD.1080702@cs.uni-goettingen.de>
	<4576C336.8020406@cs.uni-goettingen.de>
In-Reply-To: <4576C336.8020406@cs.uni-goettingen.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RZG-AUTH: gNvC5ZWVA5d1mEPfeXALj6w=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: Xiaoming Fu <fu@cs.uni-goettingen.de>,
	Jukka MJ Manner <jmanner@cs.Helsinki.FI>, "Kappler,
	Cornelia" <cornelia.kappler@siemens.com>
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

Hi,

the question about one and two pass was wrong. I'm more interested in which
one is interesting for the QOSM CLS.

Bernd


Bernd Schloer wrote:
> Hi,
> 
> with the proposed e2e QSPEC object remapping is not necessary any more. 
> Since CLS
> relies on Token Bucket as the only parameter, no local QSPEC needs to be 
> defined.
> I assume QoSClass and Priority is ignored by CLS QOSM from now on. Still 
> interesting
> could be two different queues to handle CL and Best Effort traffic.
> 
> The interoperation with RSVP is another open issue. The table in section 
> 7 shows
> a mapping of objects and parameters between QoS NSLP and RSVP.
> 
> A RSVP PATH message contains a Sender TSpec and an ADSpec object. The 
> Sender TSpec
> describes the traffic specification while the ADSpec probes for 
> available Bandwidth.
> The ADSpec can be mapped to <QoS Available> (Bandwidth) and the Sender 
> TSpec +
> FlowSpec to <QoS Desired> and opt. <Minimum QoS> (both Token Bucket).
> 
> Compared to the table in section 6.4.2 of the QSPEC Template the <QoS 
> Desired> is
> missing in the QUERY and RESERVE message. How does this fit together? 
> The Object
> Combination is not optional from my understanding. The CLS-draft 
> mentions that
> Sender-TSpec and ADSpec cannot be mapped easily. Does this mean 
> multicast flows
> and merged FlowSpecs?
> 
> Where is the difference between one-pass, One Pass with 
> Advertising(OPWA) and the
> two-pass reservation model? Are there more? When the Sender includes an 
> ADSpec in the
> Path message, it's OPWA, without ADSpec it's one-pass. The 
> Receiver-Initiated Reservation
> is two-pass?
> 
> There are three examples in Appendix B.2 showing how the QSPEC in a 
> QUERY message
> can be composed and interpreted.
> 
> 1.The Sender (QNR) collects information about the available bandwidth 
> with a QUERY
> message containing <QoS Available>. The Receiver (QNI) generates a 
> RESERVE message
> with <QoS Desired> based on <QoS Available>. The Sender (QNR) sends back 
> a RESPONSE
> with <QoS Reserved> which carries information about the performed 
> reservation.
> According to the QSPEC Procedures <QoS Available> is missing in the 
> QUERY and RESERVE.
> 
> The next two examples are not quite clear to me.
> 2.  When the QNR composes the <QoS Desired> based on <QoS Available> it 
> uses a Token
> Bucket (QNE-readonly). A Resource QUERY can get <QoS Available>. I'm not 
> sure if this
> is draft-conform: The QNR could pretend to be a QNI for the QUERY to 
> make then a
> Receiver-Initiated Reservation as QNR. From my understanding a QNR can't 
> do a Resource
> QUERY along the path to the QNI.
> 
> 3. Peak-Rate can be mapped to Bandwidth. The Traffic object contains 
> both, Token Bucket
> and Bandwidth. Using Bandwidth avoids mapping and interpreting certain 
> fields of TB,
> but each QNE along the path should know how to deal with the new <QoS 
> Available>.
> 
> Comments?
> 
> Bernd
> 
> 
> 
> 
> 
> 
> Xiaoming Fu wrote:
> 
>> Hi Jukka,
>>
>> The CLS draft is actually a remapping of RSVP CLS parameters (and 
>> procedures) to NSIS.
>>
> In the table in section 7 <QoS Desired> (QUERY and RESERVE) is not 
> mentioned
> as in the QSPEC Procedures. The same with <QoS Available> for RESPONSE. 
> Also
> in section 5.3 <QoS Desired> is not mentioned. Are these parameter 
> optional? > In the QSPEC-1 parameters specified in 
> [draft-ietf-nsis-qspec], there
> 
>> are the following two types:
>>
>> - <Excess Treatment> is an optional parameter in QNI, namely it can be 
>> included or excluded in the CLS control information. If it is included 
>> in a message, then CLS QNE must interpret and populate it.
>>
>> - <QoS Desired> and <QoS Reserved> are mandatory for all (QNI QNEs QNR)
>> including other QoSMs; <QoS Available> mandatory for 
>> receiver-initiated reservation, but optional for sender-initiated 
>> reservation.
>>
>> however, we didn't discuss how exactly the objects other than Token 
>> Bucket(s) inside the QoS Desired etc should be handled. We thought a 
>> QNE doesn't need to include (for QNI/QNR) nor interpret any of them.
>>
>> Any remarks on this?
>> Xiaoming
>>
>> Jukka MJ Manner wrote:
>>
>>> Hi Xiaoming and Cornelia,
>>>
>>> I was wondering if you have some ideas on how the CL QoS Model would 
>>> handle all the current QSPEC-1 parameters? Your draft lists that as 
>>> an open issue.
>>>
>>> Cheers,
>>> Jukka
>>>
>>> _______________________________________________
>>> nsis mailing list
>>> nsis@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/nsis
>>
>>
>>
> 
> 

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



From nsis-bounces@ietf.org Thu Dec 07 03:19:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsESo-0008JE-77; Thu, 07 Dec 2006 03:18:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsESn-0008J9-5w
	for nsis@ietf.org; Thu, 07 Dec 2006 03:18:41 -0500
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsESj-0005K0-G0
	for nsis@ietf.org; Thu, 07 Dec 2006 03:18:41 -0500
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1GsESa-0003qN-JP; Thu, 07 Dec 2006 09:18:34 +0100
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by irams1.ira.uni-karlsruhe.de with esmtps 
	id 1GsESa-0004iu-38; Thu, 07 Dec 2006 09:18:28 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 98571B4F3;
	Thu,  7 Dec 2006 09:18:27 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1GsESZ-0003UU-8T; Thu, 07 Dec 2006 09:18:27 +0100
Message-ID: <4577CE52.3090806@tm.uka.de>
Date: Thu, 07 Dec 2006 09:18:26 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: Re: [NSIS] Support for local domain information in the QSPEC
References: <9473683187ADC049A855ED2DA739ABCA0DDC7FF2@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC7FF2@KCCLUST06EVS1.ugd.att.com>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.8 (---)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.6 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: john.loughney@nokia.com, nsis@ietf.org
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

Hi Jerry,

Ash, Gerald R (Jerry), ALABS wrote:
> Recall that in the current proposal, the concept of 'remapping' QSPEC
> parameters, e.g., from QSPEC parameter 1 to QSPEC parameter 2, is
> eliminated.  

I guess that this "Remapping" is different from what I described.
QoS mapping (not remapping) is required at some stage of the admission
control process, i.e. you must decide into which QoS class this
reservation will be put.

> A local QSPEC may re-define the same QSPEC parameter in the initiator
> QSPEC to an equivalent parameter, e.g., RMD may redefine the TMOD
> parameter to an equivalent TMOD parameter that specifies only the peak
> rate (i.e., set r=p, b/m to default values). 

Yes, but it should not alter the original QSPEC parameters
that were specified by the QNE (except in the QoS available
section).

> Also specified in the current proposal:
> - edge nodes must interpret initiator QSPEC parameters
> - local QSPEC must be consistent with initiator QSPEC

Yep. Sounds good at a first glance.
 Roland

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



From nsis-bounces@ietf.org Thu Dec 07 03:28:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsEb9-0004Bv-3f; Thu, 07 Dec 2006 03:27:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsEb8-0004Bq-Ao
	for nsis@ietf.org; Thu, 07 Dec 2006 03:27:18 -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 1GsEb6-0006eX-Te
	for nsis@ietf.org; Thu, 07 Dec 2006 03:27:18 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kB78QeED021445; Thu, 7 Dec 2006 10:26:46 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Dec 2006 10:26:57 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Dec 2006 10:26:44 +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
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Thu, 7 Dec 2006 10:25:27 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC018077C9@esebe199.NOE.Nokia.com>
In-Reply-To: <4577CE52.3090806@tm.uka.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Support for local domain information in the QSPEC
Thread-Index: AccZ2FEmxOGte8OUScK8mhVuXsRJIQAALLJg
From: <john.loughney@nokia.com>
To: <bless@tm.uka.de>, <gash@att.com>
X-OriginalArrivalTime: 07 Dec 2006 08:26:44.0645 (UTC)
	FILETIME=[6DF0E550:01C719D9]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061207102647-5384DBB0-30BC530C/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: nsis@ietf.org
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

Roland,

>Ash, Gerald R (Jerry), ALABS wrote:
>> Recall that in the current proposal, the concept of 'remapping' QSPEC

>> parameters, e.g., from QSPEC parameter 1 to QSPEC parameter 2, is=20
>> eliminated.
>
>I guess that this "Remapping" is different from what I described.
>QoS mapping (not remapping) is required at some stage of the=20
>admission control process, i.e. you must decide into which QoS=20
>class this reservation will be put.
>
>> A local QSPEC may re-define the same QSPEC parameter in the initiator

>> QSPEC to an equivalent parameter, e.g., RMD may redefine the TMOD=20
>> parameter to an equivalent TMOD parameter that specifies only the
peak=20
>> rate (i.e., set r=3Dp, b/m to default values).
>
>Yes, but it should not alter the original QSPEC parameters=20
>that were specified by the QNE (except in the QoS available section).
>
>> Also specified in the current proposal:
>> - edge nodes must interpret initiator QSPEC parameters
>> - local QSPEC must be consistent with initiator QSPEC
>
>Yep. Sounds good at a first glance.

I agree.  If I used 'remapping' then it was a mistake. What I meant
was mapping the expected e2e qos to the local domain qos, for eaxmple
as you mention deciding what local QoS class the reservation should
be put in.

John

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



From nsis-bounces@ietf.org Thu Dec 07 03:28:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsEbG-0004D0-BM; Thu, 07 Dec 2006 03:27:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsEbF-0004Cv-1I
	for nsis@ietf.org; Thu, 07 Dec 2006 03:27:25 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsEbC-0006eo-JI
	for nsis@ietf.org; Thu, 07 Dec 2006 03:27:25 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kB78Qh0B013007; Thu, 7 Dec 2006 10:26:45 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Dec 2006 10:26:55 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Dec 2006 10:26:44 +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
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Thu, 7 Dec 2006 10:26:41 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC018077D2@esebe199.NOE.Nokia.com>
In-Reply-To: <45767C7F.20509@tm.uka.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Thread-Index: AccZDvnJ3Cpc9b4IRquIoetabrDvrQAylngA
From: <john.loughney@nokia.com>
To: <bless@tm.uka.de>
X-OriginalArrivalTime: 07 Dec 2006 08:26:44.0848 (UTC)
	FILETIME=[6E0FDF00:01C719D9]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061207102647-322BBBB0-6D8077BC/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: gash@att.com, karagian@cs.utwente.nl, nsis@ietf.org
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

Hi Roland,

This looks reasonable.  Now I just want to make sure this is what the
WG understands and that we can get closure on this.

So, to the WG - are you in agreement with Roland's proposal here?

John=20

>-----Original Message-----
>From: ext Roland Bless [mailto:bless@tm.uka.de]=20
>Sent: 06 December, 2006 10:17
>To: Loughney John (Nokia-NRC/Helsinki)
>Cc: karagian@cs.utwente.nl; nsis@ietf.org; Ash, Gerald R (Jerry), ALABS
>Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
>
>Hi John,
>
>john.loughney@nokia.com wrote:
>> Could you summize your proposal, making it easier just to=20
>verify that=20
>> we can come to consensus on this? It looked like there was some=20
>> meandering on the email threads about some parts of your=20
>proposal, so=20
>> it wasn't clear that we had complete consensus on your initial=20
>> proposal.
>
>Ok, I'll try once again.
>
>1. each QSPEC has a type (QSPEC-ID) instead of this QOSM-ID
>   because I think that some QSPECs are applicable to more
>   than one QOSM (e.g., the e2e QSPEC) and some QOSM may understand
>   more than one QSPEC type.
>
>2. Instead of supporting stacking QSPEC objects in QoS-NSLP
>   I suggest to have only a "single" QSPEC object in a QoS-NSLP.
>   If one wants to carry other QSPECs transparently or simply
>   add parameters of local meaning etc. one could
>   simply define an "encapsulation" for its own QSPEC type
>   like this:
>----------------------------------
>| QSPEC-Type =3D RMD-QSPEC         |  Common QSPEC header
>+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D+\
>|  RMD-specific Parameter 1      | \
>+--------------------------------+  \
>|             ....               |   local QSPEC parameters
>+--------------------------------+  /
>|  RMD-specific Parameter n      | /
>+--------------------------------+/
>| +----------------------------+ |
>| | QSPEC-Type =3D E2E QSPEC     | |
>| =
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D+ |
>| |                            | | Encapsulated "external" QSPEC
>| |          ....              | |
>| +----------------------------+ |
>+--------------------------------+
>
>That's essentially the proposal to remove stacking while=20
>achieving the same functionality with encapsulation.
>
>This simplifies QoS NSLP operation and implementation, because=20
>there are less error cases at the interface from QoS-NSLP to=20
>the RMF and not every QoSM requires its own QSPEC so stacking=20
>would be superfluous for them.
>
>Still unclear?
>
>Regards,
> Roland
>

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



From nsis-bounces@ietf.org Thu Dec 07 04:06:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsFCU-0006dw-SU; Thu, 07 Dec 2006 04:05:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsFCT-0006db-0s
	for nsis@ietf.org; Thu, 07 Dec 2006 04:05:53 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsFCR-0005MW-GU
	for nsis@ietf.org; Thu, 07 Dec 2006 04:05:52 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kB795ZDn029660; Thu, 7 Dec 2006 10:05:44 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: <john.loughney@nokia.com>, <bless@tm.uka.de>
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Thu, 7 Dec 2006 10:05:30 +0100
Message-ID: <001101c719de$dc8ada70$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AccZDvnJ3Cpc9b4IRquIoetabrDvrQAylngAAAFZhQA=
In-Reply-To: <BAA65A575825454CBB0103267553FCCC018077D2@esebe199.NOE.Nokia.com>
X-Spam-Score: 0 () 
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Thu, 07 Dec 2006 10:05:47 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: gash@att.com, nsis@ietf.org
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

Hi John

I think that during and after the IETF meeting in San Diego 
many people supported the proposal of Roland.

Best Regards,
Georgios
 

> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com] 
> Sent: donderdag 7 december 2006 9:27
> To: bless@tm.uka.de
> Cc: karagian@cs.utwente.nl; nsis@ietf.org; gash@att.com
> Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
> 
> Hi Roland,
> 
> This looks reasonable.  Now I just want to make sure this is 
> what the WG understands and that we can get closure on this.
> 
> So, to the WG - are you in agreement with Roland's proposal here?
> 
> John 
> 
> >-----Original Message-----
> >From: ext Roland Bless [mailto:bless@tm.uka.de]
> >Sent: 06 December, 2006 10:17
> >To: Loughney John (Nokia-NRC/Helsinki)
> >Cc: karagian@cs.utwente.nl; nsis@ietf.org; Ash, Gerald R 
> (Jerry), ALABS
> >Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
> >
> >Hi John,
> >
> >john.loughney@nokia.com wrote:
> >> Could you summize your proposal, making it easier just to
> >verify that
> >> we can come to consensus on this? It looked like there was some 
> >> meandering on the email threads about some parts of your
> >proposal, so
> >> it wasn't clear that we had complete consensus on your initial 
> >> proposal.
> >
> >Ok, I'll try once again.
> >
> >1. each QSPEC has a type (QSPEC-ID) instead of this QOSM-ID
> >   because I think that some QSPECs are applicable to more
> >   than one QOSM (e.g., the e2e QSPEC) and some QOSM may understand
> >   more than one QSPEC type.
> >
> >2. Instead of supporting stacking QSPEC objects in QoS-NSLP
> >   I suggest to have only a "single" QSPEC object in a QoS-NSLP.
> >   If one wants to carry other QSPECs transparently or simply
> >   add parameters of local meaning etc. one could
> >   simply define an "encapsulation" for its own QSPEC type
> >   like this:
> >----------------------------------
> >| QSPEC-Type = RMD-QSPEC         |  Common QSPEC header
> >+================================+\
> >|  RMD-specific Parameter 1      | \
> >+--------------------------------+  \
> >|             ....               |   local QSPEC parameters
> >+--------------------------------+  /
> >|  RMD-specific Parameter n      | /
> >+--------------------------------+/
> >| +----------------------------+ |
> >| | QSPEC-Type = E2E QSPEC     | |
> >| +============================+ |
> >| |                            | | Encapsulated "external" QSPEC
> >| |          ....              | |
> >| +----------------------------+ |
> >+--------------------------------+
> >
> >That's essentially the proposal to remove stacking while 
> achieving the 
> >same functionality with encapsulation.
> >
> >This simplifies QoS NSLP operation and implementation, because there 
> >are less error cases at the interface from QoS-NSLP to the 
> RMF and not 
> >every QoSM requires its own QSPEC so stacking would be 
> superfluous for 
> >them.
> >
> >Still unclear?
> >
> >Regards,
> > Roland
> >
> 



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



From nsis-bounces@ietf.org Thu Dec 07 05:48:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsGmp-0008Au-EU; Thu, 07 Dec 2006 05:47:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsGmn-0008Aa-KY
	for nsis@ietf.org; Thu, 07 Dec 2006 05:47:29 -0500
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsGmh-0000y0-NP
	for nsis@ietf.org; Thu, 07 Dec 2006 05:47:29 -0500
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1GsGmb-0002LF-P4; Thu, 07 Dec 2006 11:47:22 +0100
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by irams1.ira.uni-karlsruhe.de with esmtps 
	id 1GsGmb-0001pV-2e; Thu, 07 Dec 2006 11:47:17 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 7131C8769;
	Thu,  7 Dec 2006 11:47:16 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1GsGmZ-0003au-Sr; Thu, 07 Dec 2006 11:47:16 +0100
Message-ID: <4577F133.1010803@tm.uka.de>
Date: Thu, 07 Dec 2006 11:47:15 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: Re: [NSIS] Support for local domain information in the QSPEC
References: <9473683187ADC049A855ED2DA739ABCA0DDC7FF3@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC7FF3@KCCLUST06EVS1.ugd.att.com>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.8 (---)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.6 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: john.loughney@nokia.com, nsis@ietf.org
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

Hi Jerry,

> I'm concerned that we're straying from what I thought we agreed at
> IETF-67.  There is no single generic e2e QSPEC, so it isn't possible IMO
> for a QOSM to specify 'how the e2e QSPEC is used' as a general rule.

Maybe I can clarify that. What I denote as "e2e QSPEC" is
roughly "our" traffic source description + the constraints:
e2e QSPEC:={
Source traffic Description:
 TMOD-1 (mandatory to include)
 TMOD-2 (optional to include)

Constraints (optional to include):
 Path Latency
 Path Jitter
 Path PLR
 Path PER
 Priority (Preemption, Defending, Admission, RPH Priority)
}

I simply proposed to leave out any QoSM specific parameters
from the specification. So an e2e QSPEC will contain the TMOD-1
and one of the Constraints.

The idea is now that a domain - using a particular QOSM -
can take the e2e QSPEC and decide into which class the request
belongs and whether there are enough resources available there.
This is what I call mapping.
For example, within a DiffServ QOSM of one provider, the
particular constraints can be met by forwarding the flow in the
AF class, whereas another provider applying the same QOSM
may decide that this request belongs into another DS class,
e.g., because the network is engineered differently.
Mapping a T-MOD1 with Latency < 100ms may be easily mapped
to Y.1541 class 0 and then to a concrete DiffServ class.

> The rules for local QSPECs I thought we agreed on were these:
> 
> - edge nodes in local domains must interpret initiator QSPEC parameters
> - edge nodes in local domains can either initiate parallel session with
> local QSPEC or encapsulates a local QSPEC on initiator QSPEC
> - local QSPEC interpreted by local domain QNEs
> - local QSPEC must be consistent with initiator QSPEC (e.g. can re-set
> TMOD with r=p, b/m to default)

That's ok for me.
 Roland

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



From nsis-bounces@ietf.org Thu Dec 07 07:18:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsICX-0002QL-Gg; Thu, 07 Dec 2006 07:18:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsICW-0002Q6-LR
	for nsis@ietf.org; Thu, 07 Dec 2006 07:18:08 -0500
Received: from mail120.messagelabs.com ([216.82.250.83])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GsICV-00072T-9x
	for nsis@ietf.org; Thu, 07 Dec 2006 07:18:08 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-3.tower-120.messagelabs.com!1165493885!17646853!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 26553 invoked from network); 7 Dec 2006 12:18:05 -0000
Received: from unknown (HELO attrh9i.attrh.att.com) (134.24.146.4)
	by server-3.tower-120.messagelabs.com with SMTP;
	7 Dec 2006 12:18:05 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh9i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kB7CAsFJ012747; 
	Thu, 7 Dec 2006 07:10:54 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by attrh9i.attrh.att.com (8.13.7/8.13.7) with ESMTP id
	kB7CAn6f012728; Thu, 7 Dec 2006 07:10:49 -0500 (EST)
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
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Thu, 7 Dec 2006 06:17:59 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC8006@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC018077D2@esebe199.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Thread-Index: AccZDvnJ3Cpc9b4IRquIoetabrDvrQAylngAAAgLNJA=
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: <john.loughney@nokia.com>, <bless@tm.uka.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, karagian@cs.utwente.nl,
	nsis@ietf.org
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

John,

Yes, I'm in agreement with Roland's proposal and given WG agreement will
update the QSPEC draft accordingly.

Thanks,
Jerry=20

-----Original Message-----
From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]=20
Sent: Thursday, December 07, 2006 3:27 AM
To: bless@tm.uka.de
Cc: karagian@cs.utwente.nl; nsis@ietf.org; Ash, Gerald R (Jerry), ALABS
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.

Hi Roland,

This looks reasonable.  Now I just want to make sure this is what the
WG understands and that we can get closure on this.

So, to the WG - are you in agreement with Roland's proposal here?

John=20

>-----Original Message-----
>From: ext Roland Bless [mailto:bless@tm.uka.de]=20
>Sent: 06 December, 2006 10:17
>To: Loughney John (Nokia-NRC/Helsinki)
>Cc: karagian@cs.utwente.nl; nsis@ietf.org; Ash, Gerald R (Jerry), ALABS
>Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
>
>Hi John,
>
>john.loughney@nokia.com wrote:
>> Could you summize your proposal, making it easier just to=20
>verify that=20
>> we can come to consensus on this? It looked like there was some=20
>> meandering on the email threads about some parts of your=20
>proposal, so=20
>> it wasn't clear that we had complete consensus on your initial=20
>> proposal.
>
>Ok, I'll try once again.
>
>1. each QSPEC has a type (QSPEC-ID) instead of this QOSM-ID
>   because I think that some QSPECs are applicable to more
>   than one QOSM (e.g., the e2e QSPEC) and some QOSM may understand
>   more than one QSPEC type.
>
>2. Instead of supporting stacking QSPEC objects in QoS-NSLP
>   I suggest to have only a "single" QSPEC object in a QoS-NSLP.
>   If one wants to carry other QSPECs transparently or simply
>   add parameters of local meaning etc. one could
>   simply define an "encapsulation" for its own QSPEC type
>   like this:
>----------------------------------
>| QSPEC-Type =3D RMD-QSPEC         |  Common QSPEC header
>+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D+\
>|  RMD-specific Parameter 1      | \
>+--------------------------------+  \
>|             ....               |   local QSPEC parameters
>+--------------------------------+  /
>|  RMD-specific Parameter n      | /
>+--------------------------------+/
>| +----------------------------+ |
>| | QSPEC-Type =3D E2E QSPEC     | |
>| =
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D+ |
>| |                            | | Encapsulated "external" QSPEC
>| |          ....              | |
>| +----------------------------+ |
>+--------------------------------+
>
>That's essentially the proposal to remove stacking while=20
>achieving the same functionality with encapsulation.
>
>This simplifies QoS NSLP operation and implementation, because=20
>there are less error cases at the interface from QoS-NSLP to=20
>the RMF and not every QoSM requires its own QSPEC so stacking=20
>would be superfluous for them.
>
>Still unclear?
>
>Regards,
> Roland
>

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



From nsis-bounces@ietf.org Thu Dec 07 07:19:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsICt-0002SL-CI; Thu, 07 Dec 2006 07:18:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsICs-0002S7-Dq
	for nsis@ietf.org; Thu, 07 Dec 2006 07:18:30 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsICq-00075M-2K
	for nsis@ietf.org; Thu, 07 Dec 2006 07:18:30 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kB7CIAZq007918; Thu, 7 Dec 2006 13:18:23 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Roland Bless'" <bless@tm.uka.de>,
	"'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Thu, 7 Dec 2006 13:18:07 +0100
Message-ID: <002601c719f9$c91f6ee0$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AccZ7WGsG/dIxtYUTTecVm7ZAORvnQAC+1ow
In-Reply-To: <4577F133.1010803@tm.uka.de>
X-Spam-Score: 0.3 () FVGT_s_OBFU_Q1
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Thu, 07 Dec 2006 13:18:23 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: john.loughney@nokia.com, nsis@ietf.org
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

Hi all

> 
> > The rules for local QSPECs I thought we agreed on were these:
> > 
> > - edge nodes in local domains must interpret initiator QSPEC 
> > parameters
> > - edge nodes in local domains can either initiate parallel session 
> > with local QSPEC or encapsulates a local QSPEC on initiator QSPEC
> > - local QSPEC interpreted by local domain QNEs
> > - local QSPEC must be consistent with initiator QSPEC (e.g. 
> can re-set 
> > TMOD with r=p, b/m to default)
> 
> That's ok for me.
>  Roland

This is okay for me too. 
Note that in the second case (local QSPEC must be consistent with initiator
QSPEC)
the local QSPEC can use a bandwidth parameter with a value equal to peak
(p).

Best regards,
Georgios



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



From nsis-bounces@ietf.org Thu Dec 07 07:38:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsIVx-00069J-0L; Thu, 07 Dec 2006 07:38:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsIVw-00068P-4h
	for nsis@ietf.org; Thu, 07 Dec 2006 07:38:12 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsIV6-0001ud-Sh
	for nsis@ietf.org; Thu, 07 Dec 2006 07:37:23 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kB7Cb4QW008748; Thu, 7 Dec 2006 13:37:15 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>,
	<john.loughney@nokia.com>, <bless@tm.uka.de>
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Thu, 7 Dec 2006 13:37:00 +0100
Message-ID: <002701c719fc$67974b90$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AccZDvnJ3Cpc9b4IRquIoetabrDvrQAylngAAAgLNJAAALTfsA==
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC8006@KCCLUST06EVS1.ugd.att.com>
X-Spam-Score: 0 () 
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Thu, 07 Dec 2006 13:37:17 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: nsis@ietf.org
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

Hi John and Jerry

I also agree with this proposal!

Best Regards,
Georgios
 

> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> Sent: donderdag 7 december 2006 13:18
> To: john.loughney@nokia.com; bless@tm.uka.de
> Cc: Ash, Gerald R (Jerry), ALABS; karagian@cs.utwente.nl; 
> nsis@ietf.org
> Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
> 
> John,
> 
> Yes, I'm in agreement with Roland's proposal and given WG 
> agreement will update the QSPEC draft accordingly.
> 
> Thanks,
> Jerry 
> 
> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> Sent: Thursday, December 07, 2006 3:27 AM
> To: bless@tm.uka.de
> Cc: karagian@cs.utwente.nl; nsis@ietf.org; Ash, Gerald R 
> (Jerry), ALABS
> Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
> 
> Hi Roland,
> 
> This looks reasonable.  Now I just want to make sure this is 
> what the WG understands and that we can get closure on this.
> 
> So, to the WG - are you in agreement with Roland's proposal here?
> 
> John 
> 
> >-----Original Message-----
> >From: ext Roland Bless [mailto:bless@tm.uka.de]
> >Sent: 06 December, 2006 10:17
> >To: Loughney John (Nokia-NRC/Helsinki)
> >Cc: karagian@cs.utwente.nl; nsis@ietf.org; Ash, Gerald R 
> (Jerry), ALABS
> >Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
> >
> >Hi John,
> >
> >john.loughney@nokia.com wrote:
> >> Could you summize your proposal, making it easier just to
> >verify that
> >> we can come to consensus on this? It looked like there was some 
> >> meandering on the email threads about some parts of your
> >proposal, so
> >> it wasn't clear that we had complete consensus on your initial 
> >> proposal.
> >
> >Ok, I'll try once again.
> >
> >1. each QSPEC has a type (QSPEC-ID) instead of this QOSM-ID
> >   because I think that some QSPECs are applicable to more
> >   than one QOSM (e.g., the e2e QSPEC) and some QOSM may understand
> >   more than one QSPEC type.
> >
> >2. Instead of supporting stacking QSPEC objects in QoS-NSLP
> >   I suggest to have only a "single" QSPEC object in a QoS-NSLP.
> >   If one wants to carry other QSPECs transparently or simply
> >   add parameters of local meaning etc. one could
> >   simply define an "encapsulation" for its own QSPEC type
> >   like this:
> >----------------------------------
> >| QSPEC-Type = RMD-QSPEC         |  Common QSPEC header
> >+================================+\
> >|  RMD-specific Parameter 1      | \
> >+--------------------------------+  \
> >|             ....               |   local QSPEC parameters
> >+--------------------------------+  /
> >|  RMD-specific Parameter n      | /
> >+--------------------------------+/
> >| +----------------------------+ |
> >| | QSPEC-Type = E2E QSPEC     | |
> >| +============================+ |
> >| |                            | | Encapsulated "external" QSPEC
> >| |          ....              | |
> >| +----------------------------+ |
> >+--------------------------------+
> >
> >That's essentially the proposal to remove stacking while 
> achieving the 
> >same functionality with encapsulation.
> >
> >This simplifies QoS NSLP operation and implementation, because there 
> >are less error cases at the interface from QoS-NSLP to the 
> RMF and not 
> >every QoSM requires its own QSPEC so stacking would be 
> superfluous for 
> >them.
> >
> >Still unclear?
> >
> >Regards,
> > Roland
> >
> 



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



From nsis-bounces@ietf.org Thu Dec 07 08:07:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsIxZ-0005Rm-TK; Thu, 07 Dec 2006 08:06:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsIxY-0005RS-CA
	for nsis@ietf.org; Thu, 07 Dec 2006 08:06:44 -0500
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsIxX-0006mT-2T
	for nsis@ietf.org; Thu, 07 Dec 2006 08:06:44 -0500
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1GsIxO-0005ZK-4z; Thu, 07 Dec 2006 14:06:39 +0100
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by irams1.ira.uni-karlsruhe.de with esmtps 
	id 1GsIxN-0005FD-P1; Thu, 07 Dec 2006 14:06:33 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id B40368799;
	Thu,  7 Dec 2006 14:06:32 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1GsIxL-0003m1-Ic; Thu, 07 Dec 2006 14:06:31 +0100
Message-ID: <457811D6.8070201@tm.uka.de>
Date: Thu, 07 Dec 2006 14:06:30 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: Georgios Karagiannis <karagian@cs.utwente.nl>
Subject: Re: [NSIS] Support for local domain information in the QSPEC
References: <002601c719f9$c91f6ee0$4c0d5982@dynamic.ewi.utwente.nl>
In-Reply-To: <002601c719f9$c91f6ee0$4c0d5982@dynamic.ewi.utwente.nl>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.8 (---)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.6 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: john.loughney@nokia.com, "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>,
	nsis@ietf.org
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

Hi Georgios,

>>> - edge nodes in local domains must interpret initiator QSPEC 
>>> parameters
>>> - edge nodes in local domains can either initiate parallel session 
>>> with local QSPEC or encapsulates a local QSPEC on initiator QSPEC
>>> - local QSPEC interpreted by local domain QNEs
>>> - local QSPEC must be consistent with initiator QSPEC (e.g. 
>> can re-set 
>>> TMOD with r=p, b/m to default)
>> That's ok for me.
>>  Roland
> 
> This is okay for me too. 
> Note that in the second case (local QSPEC must be consistent with initiator
> QSPEC)
> the local QSPEC can use a bandwidth parameter with a value equal to peak
> (p).

IMHO, the local QSPEC can use whatever "effective" bandwidth parameter
derived from the given e2e TMOD for admission control.
But since the local QSPEC remains local I don't really
care about that. The most important thing is that the initially
specified e2e QSPEC parameters (e.g. TMOD and QoS desired/MinQos)
are still the same when the e2e QSPEC leaves the domain again.

Regards,
 Roland


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



From nsis-bounces@ietf.org Thu Dec 07 08:09:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsIzQ-0005s9-On; Thu, 07 Dec 2006 08:08:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsIzP-0005s4-Nv
	for nsis@ietf.org; Thu, 07 Dec 2006 08:08:39 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsIzO-00078R-Aj
	for nsis@ietf.org; Thu, 07 Dec 2006 08:08:39 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kB7D8UoN010194; Thu, 7 Dec 2006 14:08:34 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Roland Bless'" <bless@tm.uka.de>
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Thu, 7 Dec 2006 14:08:26 +0100
Message-ID: <002c01c71a00$cb806520$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AccaAJ9nGbkrXS5PQ9KzAzO1BVNY6QAAB1ig
In-Reply-To: <457811D6.8070201@tm.uka.de>
X-Spam-Score: 0.3 () FVGT_s_OBFU_Q1
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Thu, 07 Dec 2006 14:08:34 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: john.loughney@nokia.com, "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>,
	nsis@ietf.org
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

Hi Roland

Okay, I agree!

Best Regards,
Georgios
 

> -----Original Message-----
> From: Roland Bless [mailto:bless@tm.uka.de] 
> Sent: donderdag 7 december 2006 14:07
> To: Georgios Karagiannis
> Cc: 'Ash, Gerald R (Jerry), ALABS'; john.loughney@nokia.com; 
> nsis@ietf.org
> Subject: Re: [NSIS] Support for local domain information in the QSPEC
> 
> Hi Georgios,
> 
> >>> - edge nodes in local domains must interpret initiator QSPEC 
> >>> parameters
> >>> - edge nodes in local domains can either initiate 
> parallel session 
> >>> with local QSPEC or encapsulates a local QSPEC on initiator QSPEC
> >>> - local QSPEC interpreted by local domain QNEs
> >>> - local QSPEC must be consistent with initiator QSPEC (e.g. 
> >> can re-set
> >>> TMOD with r=p, b/m to default)
> >> That's ok for me.
> >>  Roland
> > 
> > This is okay for me too. 
> > Note that in the second case (local QSPEC must be consistent with 
> > initiator
> > QSPEC)
> > the local QSPEC can use a bandwidth parameter with a value equal to 
> > peak (p).
> 
> IMHO, the local QSPEC can use whatever "effective" bandwidth 
> parameter derived from the given e2e TMOD for admission control.
> But since the local QSPEC remains local I don't really care 
> about that. The most important thing is that the initially 
> specified e2e QSPEC parameters (e.g. TMOD and QoS 
> desired/MinQos) are still the same when the e2e QSPEC leaves 
> the domain again.
> 
> Regards,
>  Roland
> 



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



From nsis-bounces@ietf.org Thu Dec 07 08:55:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsJi6-0006rf-Rt; Thu, 07 Dec 2006 08:54:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsJi6-0006rM-9C
	for nsis@ietf.org; Thu, 07 Dec 2006 08:54:50 -0500
Received: from mclmx2.mail.saic.com ([149.8.64.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsJi3-0006h0-Ve
	for nsis@ietf.org; Thu, 07 Dec 2006 08:54:50 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx2.mail.saic.com; Thu, 7 Dec 2006 08:54:37 -0500
Received: from 0015-ITS-EXBH01.us.saic.com ([10.43.229.18])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006120708543432725 ; Thu, 07 Dec 2006 08:54:36 -0500
Received: from 0591-ITS-EXMP02.us.saic.com ([10.42.81.248]) by
	0015-ITS-EXBH01.us.saic.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Dec 2006 08:54:31 -0500
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
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Thu, 7 Dec 2006 08:54:29 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426230F0F@0591-ITS-EXMP02.us.saic.com>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC018077D2@esebe199.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Thread-Index: AccZDvnJ3Cpc9b4IRquIoetabrDvrQAylngAAAs0yRA=
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: <john.loughney@nokia.com>,
    <bless@tm.uka.de>
X-OriginalArrivalTime: 07 Dec 2006 13:54:31.0198 (UTC)
	FILETIME=[381EBBE0:01C71A07]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: gash@att.com, karagian@cs.utwente.nl, nsis@ietf.org
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

John:

Yes, we agree on Ronald's proposal.

Please also note carefully, we NOT agreeing on anything QOS SLA-specific
things like Y.1451, DSTE, or 3GPP/Y.1451 for QSPEC.

So, anything specific to QOS SLAs (Y.1451, DSTE, or 3GPP/Y.1451) as they
stand in the draft MUST be deleted.

Best regards,
Radhika

-----Original Message-----
From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of
john.loughney@nokia.com
Sent: Thursday, December 07, 2006 3:27 AM
To: bless@tm.uka.de
Cc: gash@att.com; karagian@cs.utwente.nl; nsis@ietf.org
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.

Hi Roland,

This looks reasonable.  Now I just want to make sure this is what the
WG understands and that we can get closure on this.

So, to the WG - are you in agreement with Roland's proposal here?

John=20

>-----Original Message-----
>From: ext Roland Bless [mailto:bless@tm.uka.de]=20
>Sent: 06 December, 2006 10:17
>To: Loughney John (Nokia-NRC/Helsinki)
>Cc: karagian@cs.utwente.nl; nsis@ietf.org; Ash, Gerald R (Jerry), ALABS
>Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
>
>Hi John,
>
>john.loughney@nokia.com wrote:
>> Could you summize your proposal, making it easier just to=20
>verify that=20
>> we can come to consensus on this? It looked like there was some=20
>> meandering on the email threads about some parts of your=20
>proposal, so=20
>> it wasn't clear that we had complete consensus on your initial=20
>> proposal.
>
>Ok, I'll try once again.
>
>1. each QSPEC has a type (QSPEC-ID) instead of this QOSM-ID
>   because I think that some QSPECs are applicable to more
>   than one QOSM (e.g., the e2e QSPEC) and some QOSM may understand
>   more than one QSPEC type.
>
>2. Instead of supporting stacking QSPEC objects in QoS-NSLP
>   I suggest to have only a "single" QSPEC object in a QoS-NSLP.
>   If one wants to carry other QSPECs transparently or simply
>   add parameters of local meaning etc. one could
>   simply define an "encapsulation" for its own QSPEC type
>   like this:
>----------------------------------
>| QSPEC-Type =3D RMD-QSPEC         |  Common QSPEC header
>+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D+\
>|  RMD-specific Parameter 1      | \
>+--------------------------------+  \
>|             ....               |   local QSPEC parameters
>+--------------------------------+  /
>|  RMD-specific Parameter n      | /
>+--------------------------------+/
>| +----------------------------+ |
>| | QSPEC-Type =3D E2E QSPEC     | |
>| =
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D+ |
>| |                            | | Encapsulated "external" QSPEC
>| |          ....              | |
>| +----------------------------+ |
>+--------------------------------+
>
>That's essentially the proposal to remove stacking while=20
>achieving the same functionality with encapsulation.
>
>This simplifies QoS NSLP operation and implementation, because=20
>there are less error cases at the interface from QoS-NSLP to=20
>the RMF and not every QoSM requires its own QSPEC so stacking=20
>would be superfluous for them.
>
>Still unclear?
>
>Regards,
> Roland
>

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

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



From nsis-bounces@ietf.org Thu Dec 07 09:24:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsKAF-0004IW-6Z; Thu, 07 Dec 2006 09:23:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsKAD-0004H1-TP
	for nsis@ietf.org; Thu, 07 Dec 2006 09:23:53 -0500
Received: from mo-p00-ob.rzone.de ([81.169.146.160])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsKAA-0003tw-Sd
	for nsis@ietf.org; Thu, 07 Dec 2006 09:23:53 -0500
Received: from [192.168.178.33]
	(p5484C0EF.dip0.t-ipconnect.de [84.132.192.239])
	by post.webmailer.de (klopstock mo47) (RZmta 3.8)	with ESMTP
	id iB7D9nS903598H;	Thu, 7 Dec 2006 15:23:36 +0100 (MET)
Date: Thu, 7 Dec 2006 15:23:36 +0100 (MET)
Message-ID: <45782354.6080204@cs.uni-goettingen.de>
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Roland Bless <bless@tm.uka.de>
Subject: Re: [NSIS] Support for local domain information in the QSPEC
References: <9473683187ADC049A855ED2DA739ABCA0DDC7FF3@KCCLUST06EVS1.ugd.att.com>
	<4577F133.1010803@tm.uka.de>
In-Reply-To: <4577F133.1010803@tm.uka.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RZG-AUTH: gNvC5ZWVA5d1mEPfeXALj6w=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: john.loughney@nokia.com, "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	nsis@ietf.org
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

Hi Roland,

is my understanding correct?

An e2e QSPEC must contain TMOD-1. TMOD-2 as well as _one_ of the Constraints is
optional. If an optional object is populated it must be interpreted by the QOSM.

Is the local QSPEC mandatory or can the e2e QSPEC be used within local domains?

Bernd



Roland Bless wrote:
> Hi Jerry,
> 
> 
>>I'm concerned that we're straying from what I thought we agreed at
>>IETF-67.  There is no single generic e2e QSPEC, so it isn't possible IMO
>>for a QOSM to specify 'how the e2e QSPEC is used' as a general rule.
> 
> 
> Maybe I can clarify that. What I denote as "e2e QSPEC" is
> roughly "our" traffic source description + the constraints:
> e2e QSPEC:={
> Source traffic Description:
>  TMOD-1 (mandatory to include)
>  TMOD-2 (optional to include)
> 
> Constraints (optional to include):
>  Path Latency
>  Path Jitter
>  Path PLR
>  Path PER
>  Priority (Preemption, Defending, Admission, RPH Priority)
> }
> 
> I simply proposed to leave out any QoSM specific parameters
> from the specification. So an e2e QSPEC will contain the TMOD-1
> and one of the Constraints.
> 
> The idea is now that a domain - using a particular QOSM -
> can take the e2e QSPEC and decide into which class the request
> belongs and whether there are enough resources available there.
> This is what I call mapping.
> For example, within a DiffServ QOSM of one provider, the
> particular constraints can be met by forwarding the flow in the
> AF class, whereas another provider applying the same QOSM
> may decide that this request belongs into another DS class,
> e.g., because the network is engineered differently.
> Mapping a T-MOD1 with Latency < 100ms may be easily mapped
> to Y.1541 class 0 and then to a concrete DiffServ class.
> 
> 
>>The rules for local QSPECs I thought we agreed on were these:
>>
>>- edge nodes in local domains must interpret initiator QSPEC parameters
>>- edge nodes in local domains can either initiate parallel session with
>>local QSPEC or encapsulates a local QSPEC on initiator QSPEC
>>- local QSPEC interpreted by local domain QNEs
>>- local QSPEC must be consistent with initiator QSPEC (e.g. can re-set
>>TMOD with r=p, b/m to default)
> 
> 
> That's ok for me.
>  Roland
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

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



From nsis-bounces@ietf.org Thu Dec 07 09:42:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsKRf-0005xX-TZ; Thu, 07 Dec 2006 09:41:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsKRe-0005wB-Mt
	for nsis@ietf.org; Thu, 07 Dec 2006 09:41:54 -0500
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsKRc-000715-Cs
	for nsis@ietf.org; Thu, 07 Dec 2006 09:41:54 -0500
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1GsKRO-00018n-HZ; Thu, 07 Dec 2006 15:41:45 +0100
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by irams1.ira.uni-karlsruhe.de with esmtps 
	id 1GsKRN-0002rF-Op; Thu, 07 Dec 2006 15:41:37 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 9E2A88799;
	Thu,  7 Dec 2006 15:41:36 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1GsKRM-0003si-3u; Thu, 07 Dec 2006 15:41:36 +0100
Message-ID: <4578281F.8090703@tm.uka.de>
Date: Thu, 07 Dec 2006 15:41:35 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: Bernd Schloer <bschloer@cs.uni-goettingen.de>
Subject: Re: [NSIS] Support for local domain information in the QSPEC
References: <9473683187ADC049A855ED2DA739ABCA0DDC7FF3@KCCLUST06EVS1.ugd.att.com>
	<4577F133.1010803@tm.uka.de>
	<45782354.6080204@cs.uni-goettingen.de>
In-Reply-To: <45782354.6080204@cs.uni-goettingen.de>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.8 (---)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.6 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: john.loughney@nokia.com, "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	nsis@ietf.org
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

Hi Bernd,

Bernd Schloer wrote:
> is my understanding correct?
> 
> An e2e QSPEC must contain TMOD-1. TMOD-2 as well as _one_ of the

can be more than one.

> Constraints is
> optional. If an optional object is populated it must be interpreted by
> the QOSM.

I would say: TMOD-1 is necessary, one or more constraints are optional
but at least one constraint SHOULD be specified. Otherwise Best-effort
would be sufficient anyway, but for that you don't need any QoS
signaling at all.

> Is the local QSPEC mandatory or can the e2e QSPEC be used within local
> domains?

No, you don't have to specify a local QSPEC. The e2e QSPEC should
be sufficient for most of the cases. You only need a local QSPEC if you
want to signal special or QOSM-specific parameters inside your domain.

Regards,
 Roland


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



From nsis-bounces@ietf.org Thu Dec 07 10:03:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsKlo-0006Xu-IQ; Thu, 07 Dec 2006 10:02:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsKln-0006Vd-5N
	for nsis@ietf.org; Thu, 07 Dec 2006 10:02:43 -0500
Received: from mail120.messagelabs.com ([216.82.250.83])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GsKlh-0001pD-C4
	for nsis@ietf.org; Thu, 07 Dec 2006 10:02:43 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-7.tower-120.messagelabs.com!1165503355!16976813!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 23285 invoked from network); 7 Dec 2006 14:55:55 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-7.tower-120.messagelabs.com with SMTP;
	7 Dec 2006 14:55:55 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kB7EtsHF010625; 
	Thu, 7 Dec 2006 09:55:55 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id
	kB7Etm8a010584; Thu, 7 Dec 2006 09:55:49 -0500 (EST)
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
Subject: RE: [NSIS] Support for local domain information in the QSPEC
Date: Thu, 7 Dec 2006 08:55:48 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC800A@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <4578281F.8090703@tm.uka.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Support for local domain information in the QSPEC
Thread-Index: AccaDdshkArZTYxoQ8GvA12YpHIV8wAAPg/A
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "Roland Bless" <bless@tm.uka.de>,
	"Bernd Schloer" <bschloer@cs.uni-goettingen.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: john.loughney@nokia.com, "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	nsis@ietf.org
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

> > Is the local QSPEC mandatory or can the e2e QSPEC be used within
local
> > domains?

> No, you don't have to specify a local QSPEC. The e2e QSPEC should
> be sufficient for most of the cases. You only need a local QSPEC if
you
> want to signal special or QOSM-specific parameters inside your domain.

Furthermore, it should be possible to signal a 'QOSM-specific' parameter
in the initiator QSPEC.  E.g., a QNI may well want to signal Y.1541 QoS
class, which is intended to be an e2e parameter, in the 'e2e'/initiator
QSPEC.  No need for the QNI to put a local QSPEC on top of the initiator
('e2e') QSPEC in that case.

Thanks,
Jerry

> Regards,
> Roland


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



From nsis-bounces@ietf.org Thu Dec 07 11:15:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsLtA-0006Bj-PC; Thu, 07 Dec 2006 11:14:24 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsLtA-0006BV-5n
	for nsis@ietf.org; Thu, 07 Dec 2006 11:14:24 -0500
Received: from mo-p00-ob.rzone.de ([81.169.146.160])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GsLt1-0005s9-Uy
	for nsis@ietf.org; Thu, 07 Dec 2006 11:14:24 -0500
Received: from [192.168.178.33]
	(p5484C0EF.dip0.t-ipconnect.de [84.132.192.239])
	by post.webmailer.de (mrclete mo2) (RZmta 3.8)	with ESMTP	id
	iB7EBlhS00e6bM; Thu, 7 Dec 2006 17:12:19 +0100 (MET)
Date: Thu, 7 Dec 2006 17:12:19 +0100 (MET)
Message-ID: <45783CCF.8030902@cs.uni-goettingen.de>
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: john.loughney@nokia.com
Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
References: <BAA65A575825454CBB0103267553FCCC018077D2@esebe199.NOE.Nokia.com>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC018077D2@esebe199.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RZG-AUTH: gNvC5ZWVA5d1mEPfeXALj6w=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: gash@att.com, karagian@cs.utwente.nl, bless@tm.uka.de, nsis@ietf.org
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

Hi,

I agree.

Best Regards,
Bernd



john.loughney@nokia.com wrote:
> Hi Roland,
> 
> This looks reasonable.  Now I just want to make sure this is what the
> WG understands and that we can get closure on this.
> 
> So, to the WG - are you in agreement with Roland's proposal here?
> 
> John 
> 
> 
>>-----Original Message-----
>>From: ext Roland Bless [mailto:bless@tm.uka.de] 
>>Sent: 06 December, 2006 10:17
>>To: Loughney John (Nokia-NRC/Helsinki)
>>Cc: karagian@cs.utwente.nl; nsis@ietf.org; Ash, Gerald R (Jerry), ALABS
>>Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
>>
>>Hi John,
>>
>>john.loughney@nokia.com wrote:
>>
>>>Could you summize your proposal, making it easier just to 
>>
>>verify that 
>>
>>>we can come to consensus on this? It looked like there was some 
>>>meandering on the email threads about some parts of your 
>>
>>proposal, so 
>>
>>>it wasn't clear that we had complete consensus on your initial 
>>>proposal.
>>
>>Ok, I'll try once again.
>>
>>1. each QSPEC has a type (QSPEC-ID) instead of this QOSM-ID
>>  because I think that some QSPECs are applicable to more
>>  than one QOSM (e.g., the e2e QSPEC) and some QOSM may understand
>>  more than one QSPEC type.
>>
>>2. Instead of supporting stacking QSPEC objects in QoS-NSLP
>>  I suggest to have only a "single" QSPEC object in a QoS-NSLP.
>>  If one wants to carry other QSPECs transparently or simply
>>  add parameters of local meaning etc. one could
>>  simply define an "encapsulation" for its own QSPEC type
>>  like this:
>>----------------------------------
>>| QSPEC-Type = RMD-QSPEC         |  Common QSPEC header
>>+================================+\
>>|  RMD-specific Parameter 1      | \
>>+--------------------------------+  \
>>|             ....               |   local QSPEC parameters
>>+--------------------------------+  /
>>|  RMD-specific Parameter n      | /
>>+--------------------------------+/
>>| +----------------------------+ |
>>| | QSPEC-Type = E2E QSPEC     | |
>>| +============================+ |
>>| |                            | | Encapsulated "external" QSPEC
>>| |          ....              | |
>>| +----------------------------+ |
>>+--------------------------------+
>>
>>That's essentially the proposal to remove stacking while 
>>achieving the same functionality with encapsulation.
>>
>>This simplifies QoS NSLP operation and implementation, because 
>>there are less error cases at the interface from QoS-NSLP to 
>>the RMF and not every QoSM requires its own QSPEC so stacking 
>>would be superfluous for them.
>>
>>Still unclear?
>>
>>Regards,
>>Roland
>>
> 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

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



From nsis-bounces@ietf.org Thu Dec 07 11:28:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsM5u-0004py-Vy; Thu, 07 Dec 2006 11:27:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsM5t-0004pt-QV
	for nsis@ietf.org; Thu, 07 Dec 2006 11:27:34 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsM5S-0004vW-4h
	for nsis@ietf.org; Thu, 07 Dec 2006 11:27:33 -0500
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-5.cisco.com with ESMTP; 07 Dec 2006 08:27:05 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id kB7GR5xi011643; 
	Thu, 7 Dec 2006 08:27:05 -0800
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kB7GR4io018261;
	Thu, 7 Dec 2006 08:27:04 -0800 (PST)
Received: from [161.44.173.209] (dhcp-161-44-173-209.cisco.com
	[161.44.173.209])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id kB7GBwbM008727;
	Thu, 7 Dec 2006 08:11:58 -0800
In-Reply-To: <45767C7F.20509@tm.uka.de>
References: <BAA65A575825454CBB0103267553FCCC017BB967@esebe199.NOE.Nokia.com>
	<45767C7F.20509@tm.uka.de>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2C1E330A-A77D-40D6-86E4-3B305AAE5E48@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Thu, 7 Dec 2006 11:26:48 -0500
To: Roland Bless <bless@tm.uka.de>
X-Mailer: Apple Mail (2.752.2)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2650; t=1165508825;
	x=1166372825; c=relaxed/relaxed; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[NSIS]=20QoS=20NSLP=3A=20Stacking=20vs.=20tunneling=2
	0vs. |Sender:=20;
	bh=RpplpuwJWtCu8I8Ryun28TSiV9LByRIF1PP4RK200DE=;
	b=cGAp+xCQFUbTTivCBnSBTJ8mN7O859LfbXYehLHnJXT9xb911H01jo7N5Y73S7eGAhCjUQJF
	aHZTYgy67fLgGVjhhsdaeTCdAZtyGcxl0+Bq+9w5vDS/JUpZYMyXtmh/;
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2793; t=1165507918;
	x=1166371918; c=relaxed/simple; s=oregon;
	h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; 
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[NSIS]=20QoS=20NSLP=3A=20Stacking=20vs.=20tunneling=2
	0vs. |Sender:=20 |To:=20Roland=20Bless=20<bless@tm.uka.de>;
	bh=DzFkScR+acYPXzGf1vlyBHmsN5Z+mvmbmzCDjis7ELI=;
	b=Jz3XLoTZKfvNEIU3tZC7HtAvr4J4GmqlH+B/xU4/UI5JurokkuTqmepHKags73H0yRrkHFmx
	ra5l2tsd5l663ihNKwd2pWJSn2qTVni2DDgq5zBrvMCKtDarcc/ZvLoY;
Authentication-Results: sj-dkim-8; header.From=oran@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim8002 verified; ); 
	header.From=oran@cisco.com; dkim=pass (
	sig from cisco.com/oregon verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: john.loughney@nokia.com, "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	karagian@cs.utwente.nl, nsis@ietf.org
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


On Dec 6, 2006, at 3:17 AM, Roland Bless wrote:

> Hi John,
>
> john.loughney@nokia.com wrote:
>> Could you summize your proposal, making it easier just to verify
>> that we can come to consensus on this? It looked like there
>> was some meandering on the email threads about some parts
>> of your proposal, so it wasn't clear that we had complete
>> consensus on your initial proposal.
>
> Ok, I'll try once again.
>
> 1. each QSPEC has a type (QSPEC-ID) instead of this QOSM-ID
>    because I think that some QSPECs are applicable to more
>    than one QOSM (e.g., the e2e QSPEC) and some QOSM may understand
>    more than one QSPEC type.
>
> 2. Instead of supporting stacking QSPEC objects in QoS-NSLP
>    I suggest to have only a "single" QSPEC object in a QoS-NSLP.
>    If one wants to carry other QSPECs transparently or simply
>    add parameters of local meaning etc. one could
>    simply define an "encapsulation" for its own QSPEC type
>    like this:
This strikes me as really ugly and bug-prone, but it would work and  
give the necessary functionality. In my opinion, it'sbetter to have  
either an explicit stack (so you don't have to figure out whether  
you've escaped from the closed environment and generate errors), or  
multiple QSPEC objects that an RMF can fetch from QNLSP by registered  
type (so you don't have to co-mingle parsers).

I don't want to make a big deal about how kludgy this encoding  
approach is - if this can get WG consensus it isn't a make-or-break  
design issue.

Dave.

> ----------------------------------
> | QSPEC-Type = RMD-QSPEC         |  Common QSPEC header
> +================================+\
> |  RMD-specific Parameter 1      | \
> +--------------------------------+  \
> |             ....               |   local QSPEC parameters
> +--------------------------------+  /
> |  RMD-specific Parameter n      | /
> +--------------------------------+/
> | +----------------------------+ |
> | | QSPEC-Type = E2E QSPEC     | |
> | +============================+ |
> | |                            | | Encapsulated "external" QSPEC
> | |          ....              | |
> | +----------------------------+ |
> +--------------------------------+
>
> That's essentially the proposal to remove stacking
> while achieving the same functionality with encapsulation.
>
> This simplifies QoS NSLP operation and implementation,
> because there are less error cases at the interface from
> QoS-NSLP to the RMF and not every QoSM requires its own QSPEC
> so stacking would be superfluous for them.
>
> Still unclear?
>
> Regards,
>  Roland
>
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

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



From nsis-bounces@ietf.org Thu Dec 07 12:03:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsMdm-0005rH-WE; Thu, 07 Dec 2006 12:02:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsMdl-0005r9-L8
	for nsis@ietf.org; Thu, 07 Dec 2006 12:02:33 -0500
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsMdL-0001bP-L1
	for nsis@ietf.org; Thu, 07 Dec 2006 12:02:33 -0500
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1GsMdB-0005O9-IK; Thu, 07 Dec 2006 18:02:00 +0100
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by irams1.ira.uni-karlsruhe.de with esmtps 
	id 1GsMdA-00060h-RV; Thu, 07 Dec 2006 18:01:56 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 03A12B59F;
	Thu,  7 Dec 2006 18:01:56 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1GsMd9-0003zM-IC; Thu, 07 Dec 2006 18:01:55 +0100
Message-ID: <45784902.4000104@tm.uka.de>
Date: Thu, 07 Dec 2006 18:01:54 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: David R Oran <oran@cisco.com>
Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
References: <BAA65A575825454CBB0103267553FCCC017BB967@esebe199.NOE.Nokia.com>
	<45767C7F.20509@tm.uka.de>
	<2C1E330A-A77D-40D6-86E4-3B305AAE5E48@cisco.com>
In-Reply-To: <2C1E330A-A77D-40D6-86E4-3B305AAE5E48@cisco.com>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.8 (---)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.6 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: john.loughney@nokia.com, "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	karagian@cs.utwente.nl, nsis@ietf.org
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

Hi Dave,

please see comments inline.

David R Oran wrote:
> 
> On Dec 6, 2006, at 3:17 AM, Roland Bless wrote:
> 
>> Hi John,
>>
>> john.loughney@nokia.com wrote:
>>> Could you summize your proposal, making it easier just to verify
>>> that we can come to consensus on this? It looked like there
>>> was some meandering on the email threads about some parts
>>> of your proposal, so it wasn't clear that we had complete
>>> consensus on your initial proposal.
>>
>> Ok, I'll try once again.
>>
>> 1. each QSPEC has a type (QSPEC-ID) instead of this QOSM-ID
>>    because I think that some QSPECs are applicable to more
>>    than one QOSM (e.g., the e2e QSPEC) and some QOSM may understand
>>    more than one QSPEC type.
>>
>> 2. Instead of supporting stacking QSPEC objects in QoS-NSLP
>>    I suggest to have only a "single" QSPEC object in a QoS-NSLP.
>>    If one wants to carry other QSPECs transparently or simply
>>    add parameters of local meaning etc. one could
>>    simply define an "encapsulation" for its own QSPEC type
>>    like this:
> This strikes me as really ugly and bug-prone, but it would work and give
> the necessary functionality. In my opinion, it'sbetter to have either an

It would be interesting to hear why it's ugly and bug-prone in
more technical detail.

> explicit stack (so you don't have to figure out whether you've escaped
> from the closed environment and generate errors), or multiple QSPEC
> objects that an RMF can fetch from QNLSP by registered type (so you
> don't have to co-mingle parsers).

Maybe I don't get your points completely, let's see, so I have a couple
of questions:
If a local QSPEC escapes, the next domain will probably not
understand the QSPEC type and send back an error indicating the
leakage. Is this a problem? Are there better ways to handle this?
What would happen in the case of stacking?
Would the RMF in the next ingress QNE simply search through the stack of
QSPECs until it hits one of the supported QSPEC types or the e2e QSPECs?
Would it ignore (an/or pass on) unknown QSPECs within the stack?
Should QoS-NSLP pass always the whole QSPEC stack up to the RMF
or only registered types?
How can we guarantee that the QSPECs are still "matching" the request if
some of them are ignored and not adapted in intermediate domains?

With this kludgy encapsulation thing, an RMF should know that
there is an e2e QSPEC (or other QSPECs) enclosed and either may ignore
it completely or process it accordingly, so the semantics should be
clear. But maybe I'm missing something or a lot of things completely,
so if you have more rationale, it would be good to hear that.

> I don't want to make a big deal about how kludgy this encoding approach
> is - if this can get WG consensus it isn't a make-or-break design issue.

We shouldn't really go there if this is really kludgy and ugly.
My understanding was that most people in the WG seemed to
dislike QSPEC stacking and thought it would be too complex
(that's why stacking was limited to two QSPECs only). So Georgios
and his colleagues want to have a functionality like this.
But probably there are better ways to do that...

Regards,
 Roland


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



From nsis-bounces@ietf.org Thu Dec 07 12:58:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsNUs-0005wp-KS; Thu, 07 Dec 2006 12:57:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsNUr-0005wT-Ee
	for nsis@ietf.org; Thu, 07 Dec 2006 12:57:25 -0500
Received: from mo-p00-ob.rzone.de ([81.169.146.162])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsNUq-00015P-2p
	for nsis@ietf.org; Thu, 07 Dec 2006 12:57:25 -0500
Received: from [192.168.178.33]
	(p5484C0EF.dip0.t-ipconnect.de [84.132.192.239])
	by post.webmailer.de (mrclete mo51) (RZmta 3.8)	with ESMTP	id
	iB7HA9ln00f06C; Thu, 7 Dec 2006 18:55:35 +0100 (MET)
Date: Thu, 7 Dec 2006 18:55:35 +0100 (MET)
Message-ID: <45785502.9010602@cs.uni-goettingen.de>
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David R Oran <oran@cisco.com>
Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
References: <BAA65A575825454CBB0103267553FCCC017BB967@esebe199.NOE.Nokia.com>
	<45767C7F.20509@tm.uka.de>
	<2C1E330A-A77D-40D6-86E4-3B305AAE5E48@cisco.com>
In-Reply-To: <2C1E330A-A77D-40D6-86E4-3B305AAE5E48@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RZG-AUTH: gNvC5ZWVA5d1mEPfeXALj6w=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: john.loughney@nokia.com, "Ash, Gerald R
	\(Jerry\), ALABS" <gash@att.com>, karagian@cs.utwente.nl,
	Roland Bless <bless@tm.uka.de>, nsis@ietf.org
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

Hi Dave,

I think that Roland's approach makes the QSPEC handling between QoS NSLP
and RMF easier. There's one object to pass to the RMF. This object has inside
in case of encapsulation another object. In C-like pseudocode it would look
like

qspec->header
qspec->parameter_1
qspec->parameter_2
...
qspec->parameter_n
qspec->external->header
qspec->external->parameter_1
...
qspec->external->parameter_n

In qspec->header you can identify the type, the parameters can be accessed via
qspec->parameter_x and if necessary the encapsulated object can be accessed with
qspec->external->xyz.

I think it's a good solution.

Bernd


David R Oran wrote:
> 
> On Dec 6, 2006, at 3:17 AM, Roland Bless wrote:
> 
>> Hi John,
>>
>> john.loughney@nokia.com wrote:
>>
>>> Could you summize your proposal, making it easier just to verify
>>> that we can come to consensus on this? It looked like there
>>> was some meandering on the email threads about some parts
>>> of your proposal, so it wasn't clear that we had complete
>>> consensus on your initial proposal.
>>
>>
>> Ok, I'll try once again.
>>
>> 1. each QSPEC has a type (QSPEC-ID) instead of this QOSM-ID
>>    because I think that some QSPECs are applicable to more
>>    than one QOSM (e.g., the e2e QSPEC) and some QOSM may understand
>>    more than one QSPEC type.
>>
>> 2. Instead of supporting stacking QSPEC objects in QoS-NSLP
>>    I suggest to have only a "single" QSPEC object in a QoS-NSLP.
>>    If one wants to carry other QSPECs transparently or simply
>>    add parameters of local meaning etc. one could
>>    simply define an "encapsulation" for its own QSPEC type
>>    like this:
> 
> This strikes me as really ugly and bug-prone, but it would work and  
> give the necessary functionality. In my opinion, it'sbetter to have  
> either an explicit stack (so you don't have to figure out whether  
> you've escaped from the closed environment and generate errors), or  
> multiple QSPEC objects that an RMF can fetch from QNLSP by registered  
> type (so you don't have to co-mingle parsers).
> 
> I don't want to make a big deal about how kludgy this encoding  approach 
> is - if this can get WG consensus it isn't a make-or-break  design issue.
> 
> Dave.
> 
>> ----------------------------------
>> | QSPEC-Type = RMD-QSPEC         |  Common QSPEC header
>> +================================+\
>> |  RMD-specific Parameter 1      | \
>> +--------------------------------+  \
>> |             ....               |   local QSPEC parameters
>> +--------------------------------+  /
>> |  RMD-specific Parameter n      | /
>> +--------------------------------+/
>> | +----------------------------+ |
>> | | QSPEC-Type = E2E QSPEC     | |
>> | +============================+ |
>> | |                            | | Encapsulated "external" QSPEC
>> | |          ....              | |
>> | +----------------------------+ |
>> +--------------------------------+
>>
>> That's essentially the proposal to remove stacking
>> while achieving the same functionality with encapsulation.
>>
>> This simplifies QoS NSLP operation and implementation,
>> because there are less error cases at the interface from
>> QoS-NSLP to the RMF and not every QoSM requires its own QSPEC
>> so stacking would be superfluous for them.
>>
>> Still unclear?
>>
>> Regards,
>>  Roland
>>
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
> 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

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



From nsis-bounces@ietf.org Thu Dec 07 13:00:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsNXE-00070B-5R; Thu, 07 Dec 2006 12:59:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsNXD-0006vL-1q
	for nsis@ietf.org; Thu, 07 Dec 2006 12:59:51 -0500
Received: from mclmx.mail.saic.com ([149.8.64.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsNXB-0001wP-N0
	for nsis@ietf.org; Thu, 07 Dec 2006 12:59:51 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx.mail.saic.com; Thu, 7 Dec 2006 12:59:35 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006120712593413013 ; Thu, 07 Dec 2006 12:59:34 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service
	(5.5.2657.72) id <XWKQKB18>; Thu, 7 Dec 2006 12:59:34 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426230F10@0591-ITS-EXMP02.us.saic.com>
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: Roland Bless <bless@tm.uka.de>,
    David R Oran <oran@cisco.com>
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Thu, 7 Dec 2006 12:59:28 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
content-class: urn:content-classes:message
x-mimeole: Produced By Microsoft Exchange V6.5
x-originalarrivaltime: 07 Dec 2006 17:59:29.0984 (UTC)
	FILETIME=[71477C00:01C71A29]
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Cc: john.loughney@nokia.com, "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	karagian@cs.utwente.nl, nsis@ietf.org
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

Dave and Roland:

The stacking will create problems as Roland explained below. Stacking is
not only complex, it will also create problems from the simple elegant
e2e-QSPEC model implementation point of view.

Best regards,
Radhika

PS: 

1. People can see the example that I have provided using Y.1451 QOS SLA
implementation point of view. Similarly, anyone can use e2e-QSPEC as a
reference for implementations of many other things as DiffSev specs are
used as a reference for many implementations.

2. People can create many BCP drafts for implementations of QOS in the
different local domains using e2e-QSPEC spec as their references.
However, a generalized solution using QSPEC-stacking is NOT going to
happen because there are so many others ways that people can implement
in a local QOS domain.

3. One example could be: RSVP-over-DiffServ network. Two QOS models
evolved independently: Now, we have created another standard for
RSVP-over-DiffServ looking to the fact RSVP is scalable in the small
local access network and DiffServ is scalable even for the large
network. Since DiffSev is not being implemented on e2e-basis now,
RSVP-over-DiffServ standard was created (but it wan not necessary though
if e2e support of DiffServ is available).

4. NSIS e2e-QSPEC, like DiffServ, needs to be work on e2e basis making
it simple and scalable for e2e-implementations. If local QOS domains are
there, let us see what those are. If they are QOS SLAs like Y.1451 or
DSTE, they do not need QSPEC of their own. People can bring some
specific examples, we can look into those. Otherwise, let us not break
the e2e-QSPEC template model.

-----Original Message-----
From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of
Roland Bless
Sent: Thursday, December 07, 2006 12:02 PM
To: David R Oran
Cc: john.loughney@nokia.com; Ash, Gerald R (Jerry), ALABS;
karagian@cs.utwente.nl; nsis@ietf.org
Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.

Hi Dave,

please see comments inline.

David R Oran wrote:
> 
> On Dec 6, 2006, at 3:17 AM, Roland Bless wrote:
> 
>> Hi John,
>>
>> john.loughney@nokia.com wrote:
>>> Could you summize your proposal, making it easier just to verify
>>> that we can come to consensus on this? It looked like there
>>> was some meandering on the email threads about some parts
>>> of your proposal, so it wasn't clear that we had complete
>>> consensus on your initial proposal.
>>
>> Ok, I'll try once again.
>>
>> 1. each QSPEC has a type (QSPEC-ID) instead of this QOSM-ID
>>    because I think that some QSPECs are applicable to more
>>    than one QOSM (e.g., the e2e QSPEC) and some QOSM may understand
>>    more than one QSPEC type.
>>
>> 2. Instead of supporting stacking QSPEC objects in QoS-NSLP
>>    I suggest to have only a "single" QSPEC object in a QoS-NSLP.
>>    If one wants to carry other QSPECs transparently or simply
>>    add parameters of local meaning etc. one could
>>    simply define an "encapsulation" for its own QSPEC type
>>    like this:
> This strikes me as really ugly and bug-prone, but it would work and
give
> the necessary functionality. In my opinion, it'sbetter to have either
an

It would be interesting to hear why it's ugly and bug-prone in
more technical detail.

> explicit stack (so you don't have to figure out whether you've escaped
> from the closed environment and generate errors), or multiple QSPEC
> objects that an RMF can fetch from QNLSP by registered type (so you
> don't have to co-mingle parsers).

Maybe I don't get your points completely, let's see, so I have a couple
of questions:
If a local QSPEC escapes, the next domain will probably not
understand the QSPEC type and send back an error indicating the
leakage. Is this a problem? Are there better ways to handle this?
What would happen in the case of stacking?
Would the RMF in the next ingress QNE simply search through the stack of
QSPECs until it hits one of the supported QSPEC types or the e2e QSPECs?
Would it ignore (an/or pass on) unknown QSPECs within the stack?
Should QoS-NSLP pass always the whole QSPEC stack up to the RMF
or only registered types?
How can we guarantee that the QSPECs are still "matching" the request if
some of them are ignored and not adapted in intermediate domains?

With this kludgy encapsulation thing, an RMF should know that
there is an e2e QSPEC (or other QSPECs) enclosed and either may ignore
it completely or process it accordingly, so the semantics should be
clear. But maybe I'm missing something or a lot of things completely,
so if you have more rationale, it would be good to hear that.

> I don't want to make a big deal about how kludgy this encoding
approach
> is - if this can get WG consensus it isn't a make-or-break design
issue.

We shouldn't really go there if this is really kludgy and ugly.
My understanding was that most people in the WG seemed to
dislike QSPEC stacking and thought it would be too complex
(that's why stacking was limited to two QSPECs only). So Georgios
and his colleagues want to have a functionality like this.
But probably there are better ways to do that...

Regards,
 Roland


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

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



From nsis-bounces@ietf.org Fri Dec 08 12:50:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsjrN-000112-Vm; Fri, 08 Dec 2006 12:50:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsjrM-0000ww-2g
	for nsis@ietf.org; Fri, 08 Dec 2006 12:50:08 -0500
Received: from mo-p00-ob.rzone.de ([81.169.146.160])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsjrH-0000YS-Mj
	for nsis@ietf.org; Fri, 08 Dec 2006 12:50:08 -0500
Received: from [192.168.178.33]
	(p5484C0BE.dip0.t-ipconnect.de [84.132.192.190])
	by post.webmailer.de (klopstock mo13) (RZmta 3.8)	with ESMTP
	id iB8EBIOj034e5A;	Fri, 8 Dec 2006 18:49:07 +0100 (MET)
Date: Fri, 8 Dec 2006 18:49:07 +0100 (MET)
Message-ID: <4579A4FC.30601@cs.uni-goettingen.de>
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
In-Reply-To: <Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RZG-AUTH: gNvC5ZWVA5d1mEPfeXALj6w=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: nsis@ietf.org
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

Hi Jukka,

to my knowledge the case of section 3.2.10.2 is not covered in section 5.4.1,
where the Message Processing Rules of RESERVE Messages are explained. A sends a RESERVE
to C while on Node A and C still reservation state for this Session ID is installed. The
FlowID is unchanged, the MRI is unchanged, the REPLACE-Flag is not set, the Session
ID is the same and the SII-Handle is unchanged for C.

However there's a case for sessions with the REPLACE flag = 0 (does this mean a received
RESERVE message where the REPLACE flag in the Common Header is not set?) where it is
assumed that the QoS model includes directions to deal with resource sharing. Adding a
reservation or taking the the maximum of two? Or more complex mathematical operations?
What does this mean?

But back to the rerouting problem. When A attempts to tear down the reservation on the old
path by specifying explicit routing to the old peer with the related SII-Handle, nothing
would happen, when link (1) still fails.

Bernd



Jukka MJ Manner wrote:
> Dear all,
> 
> I sent the following request for feedback two weeks ago. No comments have 
> been raised. I will wait until this Friday, then submit the draft.
> 
> Jukka
> 
> On Tue, 21 Nov 2006, Jukka MJ Manner wrote:
> 
> 
>>Hi all,
>>
>>I have done all the edits I had in my list to the QoS NSLP spec, the main 
>>points are in recent thread with Roland. From the url below you can find 
>>the current draft v. "13-pre1" and a diff to v. 12.
>>
>>http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
>>
>>A direct link to the diff:
>>
>>http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos-nslp-12-from-3-pre1.diff.html
>>
>>
>>I would appreciate comments on the changes I did (what is wrong, what I 
>>missed, etc.).
>>
>>
>>I still have one problem with the spec, namely the way the NSLP suggests 
>>to handle mobility and path changes. I think we need to review that 
>>statement, because it seems like a "hack" (playing with the RSN value), 
>>and not really useful. And the interactions with GIST look partly wrong. 
>>The folks working on the mobility draft (me included) could comment. The 
>>section I'm talking about is 3.2.10, especially 3.2.10.2, in the v.12 
>>draft.
>>
>>BR,
>>Jukka
>>
>>_______________________________________________
>>nsis mailing list
>>nsis@ietf.org
>>https://www1.ietf.org/mailman/listinfo/nsis
>>
> 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

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



From nsis-bounces@ietf.org Fri Dec 08 16:17:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gsn5m-0005qN-AE; Fri, 08 Dec 2006 16:17:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gsn5l-0005qD-GC
	for nsis@ietf.org; Fri, 08 Dec 2006 16:17:13 -0500
Received: from mo-p00-ob.rzone.de ([81.169.146.160])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gsn5j-0006C0-4W
	for nsis@ietf.org; Fri, 08 Dec 2006 16:17:13 -0500
Received: from [192.168.178.33]
	(p5484C0BE.dip0.t-ipconnect.de [84.132.192.190])
	by post.webmailer.de (klopstock mo36) (RZmta 3.8)	with ESMTP
	id iB8HttcG03565F;	Fri, 8 Dec 2006 22:17:09 +0100 (MET)
Date: Fri, 8 Dec 2006 22:17:09 +0100 (MET)
Message-ID: <4579D5BD.5010605@cs.uni-goettingen.de>
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
In-Reply-To: <Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RZG-AUTH: gNvC5ZWVA5d1mEPfeXALj6w=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: nsis@ietf.org
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

Hi Jukka,

the Summary Refresh and Teardown concept doesn't convince me. It might be true that
the number of individual messages gets reduced. The operating overhead increases.
In an error case when the lists are only partly processed, the remaining sessions
of these lists don't get refreshed/torn down.

Bernd




Jukka MJ Manner wrote:
> Dear all,
> 
> I sent the following request for feedback two weeks ago. No comments have 
> been raised. I will wait until this Friday, then submit the draft.
> 
> Jukka
> 
> On Tue, 21 Nov 2006, Jukka MJ Manner wrote:
> 
> 
>>Hi all,
>>
>>I have done all the edits I had in my list to the QoS NSLP spec, the main 
>>points are in recent thread with Roland. From the url below you can find 
>>the current draft v. "13-pre1" and a diff to v. 12.
>>
>>http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
>>
>>A direct link to the diff:
>>
>>http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos-nslp-12-from-3-pre1.diff.html
>>
>>
>>I would appreciate comments on the changes I did (what is wrong, what I 
>>missed, etc.).
>>
>>
>>I still have one problem with the spec, namely the way the NSLP suggests 
>>to handle mobility and path changes. I think we need to review that 
>>statement, because it seems like a "hack" (playing with the RSN value), 
>>and not really useful. And the interactions with GIST look partly wrong. 
>>The folks working on the mobility draft (me included) could comment. The 
>>section I'm talking about is 3.2.10, especially 3.2.10.2, in the v.12 
>>draft.
>>
>>BR,
>>Jukka
>>
>>_______________________________________________
>>nsis mailing list
>>nsis@ietf.org
>>https://www1.ietf.org/mailman/listinfo/nsis
>>
> 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

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



From nsis-bounces@ietf.org Sat Dec 09 06:26:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gt0Kc-0000Oo-AD; Sat, 09 Dec 2006 06:25:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gt0Ka-0000OZ-LN
	for nsis@ietf.org; Sat, 09 Dec 2006 06:25:24 -0500
Received: from mo-p00-ob.rzone.de ([81.169.146.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gt0KY-0007h1-8Q
	for nsis@ietf.org; Sat, 09 Dec 2006 06:25:24 -0500
Received: from [192.168.178.33] (p54849455.dip0.t-ipconnect.de [84.132.148.85])
	by post.webmailer.de (klopstock mo35) (RZmta 3.8)	with ESMTP
	id iB96TeBY03561E	for <nsis@ietf.org>;
	Sat, 9 Dec 2006 12:25:20 +0100 (MET)
Date: Sat, 9 Dec 2006 12:25:20 +0100 (MET)
Message-ID: <457A9C86.3070503@cs.uni-goettingen.de>
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "nsis@ietf.org" <nsis@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RZG-AUTH: gNvC5ZWVA5d1mEPfeXALj6w=
X-Spam-Score: 0.5 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Subject: [NSIS] Interpretation of <Priority> Parameter for QOSM CLS
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

Hi,

here's a suggestion how to handle the <Priority> parameter. What do you think of it?

Bernd



The following object combinations are defined:


1. <Admission Priority>   Priority Queueing  [Y.1541]

2. <Admission Priority>   Preemption         [RFC 3181]
    <Preemption Priority>                     [3GPP-1]
    <Defending Priority>                      [3GPP-2]
                                              [3GPP-3]

3. <RPH Priority>         q735 = Preemption  [RFC 4412]
                           ets  = Priority Q.
                           wps  = Priority Q.


1. The QOSM CLS has 3 priority queues: Best Effort (0), Normal Priority CLS Traffic (1),
and High Priority CLS Traffic (2). According to <Admission Priority> the corresponding
queue is selected. If no <Priority> parameter is given the default priority is Normal
Priority (1). <Defending Priority> is a default value or 0.

2. If <Admission Priority> is not given, the default priority is Normal Priority (1).
A non-admitted flow with any <Preemption Priority> value can preempt an already admitted
flow with lower priority in ascending order of priority. One single higher priority flow
may replace more than one lower priority flow until the requested amount of <Traffic> is
met. <Preemption Priority> and <Defending Priority> are compared when no flow with lower
priority could be preempted. A flow with higher <Preemption Priority> can preempt an already
admitted flow with lower <Defending Priority>. Once the flow is admitted
<Preemption Priority> becomes irrelevant.


3. [RFC4412] defines a number of namespaces. Each namespace has a finite list of relative
priority values. A mapping of 5-6 <RPH Priority> to 3 <Admission Priority> parameters has
to be done, e.g.

  RPH  A.P.
-----------
   4 -> 0   lowest priority
   3 -> 1
   2 -> 1
   1 -> 2
   0 -> 2   highest priority

A non admitted flow using the namespace q735 can preempt an already admitted flow with lower
priority in ascending order of priority. Requests do not preempt flows of equal order. In this
case the flow is queued. Requests with the lowest priority do not preempt any admitted flow and
are queued as well. One single higher priority flow may replace more than one lower priority flow
until the requested amount of <Traffic> is met. The namespaces ets and wps are queued according
to their priority levels.


The following object combinations don't make sense in my opinion:

<Preemption Priority>, <Defending Priority> and <RPH Priority>:
with or without <Admission Priority> it is not clear who is in charge of preempting
<Preemption Pr.> or <RPH PR.> ?

<Preemption Priority>, <Defending Priority>:
<Admission Priority> is missing -> no queue or lower priority flows can be selected.



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



From nsis-bounces@ietf.org Sat Dec 09 10:51:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gt4TU-0005W5-QL; Sat, 09 Dec 2006 10:50:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gt4TT-0005Vm-Sm
	for nsis@ietf.org; Sat, 09 Dec 2006 10:50:51 -0500
Received: from mo-p00-ob.rzone.de ([81.169.146.160])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gt4TP-00044D-9e
	for nsis@ietf.org; Sat, 09 Dec 2006 10:50:51 -0500
Received: from [192.168.178.33] (p54849455.dip0.t-ipconnect.de [84.132.148.85])
	by post.webmailer.de (mrclete mo53) (RZmta 3.8)	with ESMTP	id
	iB9CYL2400f1fE; Sat, 9 Dec 2006 16:49:50 +0100 (MET)
Date: Sat, 9 Dec 2006 16:49:50 +0100 (MET)
Message-ID: <457ADA83.3000600@cs.uni-goettingen.de>
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
In-Reply-To: <Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RZG-AUTH: gNvC5ZWVA5d1mEPfeXALj6w=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: nsis@ietf.org
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

Hi Jukka,


the initial route A-B-C uses links (1) and (3). After link (1) fails, the path is
rerouted using links (2) and (3).


              (1)
            /-----\                       |x| = QoS NSLP aware
          +-+     /-\ (3) +-+             +-+
      ----|A|     |B|-----|C|----
          +-+     \-/     +-+             /-\
            \-----/                       |x| = QoS NSLP unaware
              (2)

section 3.2.10 says

    When the QoS NSLP is aware of the route change, it needs to set up
    the reservation on the new path. This is done by sending a new
    RESERVE message. If the next QNE is, in fact, unchanged then this
    will be used to refresh/update the existing reservation. Otherwise it
    will lead to the reservation being installed on the new path.


section 5.3.1.says

    If the RSN is greater than the current stored value, the current reservation
    MUST be modified appropriately (provided that admission control and policy
    control succeed), and the stored RSN value updated to that for the new
    reservation.

According to section 3.2.10 sending a full RESERVE including a QSPEC and the next
peer is unchanged the reservation will be updated/refreshed. However section 5.3.1
talks not about refreshing/updating, it says the current reservation must be modified
appropriately. What is the meaning of "appropriately" here? What happens to the current
reservation?

When A sends a full RESERVE with set SCOPING-Flag including RII and QSPEC object,
and if the RESERVE will be treated as an updating, refreshing RESERVE, the RESPONSE
will contain an INFO object with Success, Reservation succesful. In case of new
installed state, the RESPONSE contains also an INFO object with Success, Reservation
succesful.

It would be helpful to make a difference between Reservation succesful and Refresh
succesful. In case of Refresh succesful, there's no need to tear down the reservation
on the old path. In case of Reservation succesful it might be. When link (1) still
fails the teardown message would timeout in this example.

What do you think?

Bernd




Jukka MJ Manner wrote:
> Dear all,
> 
> I sent the following request for feedback two weeks ago. No comments have 
> been raised. I will wait until this Friday, then submit the draft.
> 
> Jukka
> 
> On Tue, 21 Nov 2006, Jukka MJ Manner wrote:
> 
> 
>>Hi all,
>>
>>I have done all the edits I had in my list to the QoS NSLP spec, the main 
>>points are in recent thread with Roland. From the url below you can find 
>>the current draft v. "13-pre1" and a diff to v. 12.
>>
>>http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
>>
>>A direct link to the diff:
>>
>>http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos-nslp-12-from-3-pre1.diff.html
>>
>>
>>I would appreciate comments on the changes I did (what is wrong, what I 
>>missed, etc.).
>>
>>
>>I still have one problem with the spec, namely the way the NSLP suggests 
>>to handle mobility and path changes. I think we need to review that 
>>statement, because it seems like a "hack" (playing with the RSN value), 
>>and not really useful. And the interactions with GIST look partly wrong. 
>>The folks working on the mobility draft (me included) could comment. The 
>>section I'm talking about is 3.2.10, especially 3.2.10.2, in the v.12 
>>draft.
>>
>>BR,
>>Jukka
>>
>>_______________________________________________
>>nsis mailing list
>>nsis@ietf.org
>>https://www1.ietf.org/mailman/listinfo/nsis
>>
> 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

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



From nsis-bounces@ietf.org Sat Dec 09 14:34:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gt7we-0007s4-6N; Sat, 09 Dec 2006 14:33:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gt7wc-0007ry-Ld
	for nsis@ietf.org; Sat, 09 Dec 2006 14:33:10 -0500
Received: from mo-p00-ob.rzone.de ([81.169.146.160])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gt7wa-0003UD-51
	for nsis@ietf.org; Sat, 09 Dec 2006 14:33:10 -0500
Received: from [192.168.178.33] (p54849455.dip0.t-ipconnect.de [84.132.148.85])
	by post.webmailer.de (klopstock mo26) (RZmta 3.8)	with ESMTP
	id iB9EjxB303526E;	Sat, 9 Dec 2006 20:32:51 +0100 (MET)
Date: Sat, 9 Dec 2006 20:32:51 +0100 (MET)
Message-ID: <457B0EC7.7010901@schloer.net>
From: Bernd Schloer <bernd@schloer.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
	<457ADA83.3000600@cs.uni-goettingen.de>
In-Reply-To: <457ADA83.3000600@cs.uni-goettingen.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RZG-AUTH: gNvC5ZWVA5d1mEPfeXALj6w=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Cc: nsis@ietf.org
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

section 5.4.1 says

    As discussed in Section 5.2.5.2, to avoid incorrect removal of state
    after a rerouting event, a node receiving a RESERVE message with the
    TEAR flag set which does not come from the current peer QNE,
    identified by its SII, MUST be ignored and MUST NOT be forwarded.


The SII-Handle is generated by GIST and points to the GIST next hop and
to the local interface. In this case for C the current peer QNE is A,
but the SII-Handle points to B. Any existing reservation can neither
over (1), nor over (2) be removed.

In case a router just rebooted, it has no current peer QNE, but should
forward the tearing RESERVE, as discussed here
http://www1.ietf.org/mail-archive/web/nsis/current/msg06697.html
Existing reservations will not be removed further along the path.

Bernd




Bernd Schloer wrote:
> Hi Jukka,
> 
> 
> the initial route A-B-C uses links (1) and (3). After link (1) fails, 
> the path is
> rerouted using links (2) and (3).
> 
> 
>              (1)
>            /-----\                       |x| = QoS NSLP aware
>          +-+     /-\ (3) +-+             +-+
>      ----|A|     |B|-----|C|----
>          +-+     \-/     +-+             /-\
>            \-----/                       |x| = QoS NSLP unaware
>              (2)
> 
> section 3.2.10 says
> 
>    When the QoS NSLP is aware of the route change, it needs to set up
>    the reservation on the new path. This is done by sending a new
>    RESERVE message. If the next QNE is, in fact, unchanged then this
>    will be used to refresh/update the existing reservation. Otherwise it
>    will lead to the reservation being installed on the new path.
> 
> 
> section 5.3.1.says
> 
>    If the RSN is greater than the current stored value, the current 
> reservation
>    MUST be modified appropriately (provided that admission control and 
> policy
>    control succeed), and the stored RSN value updated to that for the new
>    reservation.
> 
> According to section 3.2.10 sending a full RESERVE including a QSPEC and 
> the next
> peer is unchanged the reservation will be updated/refreshed. However 
> section 5.3.1
> talks not about refreshing/updating, it says the current reservation 
> must be modified
> appropriately. What is the meaning of "appropriately" here? What happens 
> to the current
> reservation?
> 
> When A sends a full RESERVE with set SCOPING-Flag including RII and 
> QSPEC object,
> and if the RESERVE will be treated as an updating, refreshing RESERVE, 
> the RESPONSE
> will contain an INFO object with Success, Reservation succesful. In case 
> of new
> installed state, the RESPONSE contains also an INFO object with Success, 
> Reservation
> succesful.
> 
> It would be helpful to make a difference between Reservation succesful 
> and Refresh
> succesful. In case of Refresh succesful, there's no need to tear down 
> the reservation
> on the old path. In case of Reservation succesful it might be. When link 
> (1) still
> fails the teardown message would timeout in this example.
> 
> What do you think?
> 
> Bernd
> 
> 
> 
> 
> Jukka MJ Manner wrote:
> 
>> Dear all,
>>
>> I sent the following request for feedback two weeks ago. No comments 
>> have been raised. I will wait until this Friday, then submit the draft.
>>
>> Jukka
>>
>> On Tue, 21 Nov 2006, Jukka MJ Manner wrote:
>>
>>
>>> Hi all,
>>>
>>> I have done all the edits I had in my list to the QoS NSLP spec, the 
>>> main points are in recent thread with Roland. From the url below you 
>>> can find the current draft v. "13-pre1" and a diff to v. 12.
>>>
>>> http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
>>>
>>> A direct link to the diff:
>>>
>>> http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos-nslp-12-from-3-pre1.diff.html 
>>>
>>>
>>>
>>> I would appreciate comments on the changes I did (what is wrong, what 
>>> I missed, etc.).
>>>
>>>
>>> I still have one problem with the spec, namely the way the NSLP 
>>> suggests to handle mobility and path changes. I think we need to 
>>> review that statement, because it seems like a "hack" (playing with 
>>> the RSN value), and not really useful. And the interactions with GIST 
>>> look partly wrong. The folks working on the mobility draft (me 
>>> included) could comment. The section I'm talking about is 3.2.10, 
>>> especially 3.2.10.2, in the v.12 draft.
>>>
>>> BR,
>>> Jukka
>>>
>>> _______________________________________________
>>> nsis mailing list
>>> nsis@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/nsis
>>>
>>
>>
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
> 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 

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



From nsis-bounces@ietf.org Sun Dec 10 13:45:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtTfh-0001GP-EX; Sun, 10 Dec 2006 13:45:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtTfg-0001GK-MH
	for nsis@ietf.org; Sun, 10 Dec 2006 13:45:08 -0500
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtTfe-0005ur-6m
	for nsis@ietf.org; Sun, 10 Dec 2006 13:45:08 -0500
Received: from sbz-31.cs.helsinki.fi (sbz-31.cs.helsinki.fi [128.214.9.99])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Sun, 10 Dec 2006 20:45:02 +0200
	id 000AFD80.457C55AE.00006C59
Date: Sun, 10 Dec 2006 20:45:02 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Bernd Schloer <bschloer@cs.uni-goettingen.de>
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
In-Reply-To: <4579D5BD.5010605@cs.uni-goettingen.de>
Message-ID: <Pine.LNX.4.64.0612102043250.11174@sbz-31.cs.Helsinki.FI>
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
	<4579D5BD.5010605@cs.uni-goettingen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: nsis@ietf.org
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


This was discussed with a number of people in SD and thought to be a good 
idea. I'd like to hear other people say this is not needed, otherwise I 
will keep the spec as it is.

What is this error case where the list is only partly processed? Don't 
understand.

Jukka

On Fri, 8 Dec 2006, Bernd Schloer wrote:

> Hi Jukka,
> 
> the Summary Refresh and Teardown concept doesn't convince me. It might be true
> that
> the number of individual messages gets reduced. The operating overhead
> increases.
> In an error case when the lists are only partly processed, the remaining
> sessions
> of these lists don't get refreshed/torn down.
> 
> Bernd
> 
> 
> 
> 
> Jukka MJ Manner wrote:
> > Dear all,
> > 
> > I sent the following request for feedback two weeks ago. No comments have
> > been raised. I will wait until this Friday, then submit the draft.
> > 
> > Jukka
> > 
> > On Tue, 21 Nov 2006, Jukka MJ Manner wrote:
> > 
> > 
> > >Hi all,
> > >
> > >I have done all the edits I had in my list to the QoS NSLP spec, the main
> > >points are in recent thread with Roland. From the url below you can find
> > >the current draft v. "13-pre1" and a diff to v. 12.
> > >
> > >http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
> > >
> > >A direct link to the diff:
> > >
> > >http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos-nslp-12-from-3-pre1.diff.html
> > >
> > >
> > >I would appreciate comments on the changes I did (what is wrong, what I
> > >missed, etc.).
> > >
> > >
> > >I still have one problem with the spec, namely the way the NSLP suggests to
> > >handle mobility and path changes. I think we need to review that statement,
> > >because it seems like a "hack" (playing with the RSN value), and not really
> > >useful. And the interactions with GIST look partly wrong. The folks working
> > >on the mobility draft (me included) could comment. The section I'm talking
> > >about is 3.2.10, especially 3.2.10.2, in the v.12 draft.
> > >
> > >BR,
> > >Jukka
> > >
> >>_______________________________________________
> > >nsis mailing list
> > >nsis@ietf.org
> > >https://www1.ietf.org/mailman/listinfo/nsis
> > >
> > 
> > 
> > _______________________________________________
> > nsis mailing list
> > nsis@ietf.org
> > https://www1.ietf.org/mailman/listinfo/nsis
> 
> 

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



From nsis-bounces@ietf.org Sun Dec 10 13:51:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtTlG-0002S5-2R; Sun, 10 Dec 2006 13:50:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtTlE-0002Rz-Kl
	for nsis@ietf.org; Sun, 10 Dec 2006 13:50:52 -0500
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtTlD-0006n6-3A
	for nsis@ietf.org; Sun, 10 Dec 2006 13:50:52 -0500
Received: from sbz-31.cs.helsinki.fi (sbz-31.cs.helsinki.fi [128.214.9.99])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Sun, 10 Dec 2006 20:50:50 +0200
	id 000AFDAE.457C570A.000023B9
Date: Sun, 10 Dec 2006 20:50:50 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Bernd Schloer <bernd@schloer.net>
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
In-Reply-To: <457B0EC7.7010901@schloer.net>
Message-ID: <Pine.LNX.4.64.0612102048270.11174@sbz-31.cs.Helsinki.FI>
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
	<457ADA83.3000600@cs.uni-goettingen.de> <457B0EC7.7010901@schloer.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Cc: nsis@ietf.org
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


Hi,

I think the general design decision in any protocol is that if you don't 
understand a message, you should drop it. In the case of the QoS NSLP, 
dropping the message is the right thing to do; the reservation will be 
torn down eventually due to the refresh timeout.

Jukka

On Sat, 9 Dec 2006, Bernd Schloer wrote:

> section 5.4.1 says
> 
>    As discussed in Section 5.2.5.2, to avoid incorrect removal of state
>    after a rerouting event, a node receiving a RESERVE message with the
>    TEAR flag set which does not come from the current peer QNE,
>    identified by its SII, MUST be ignored and MUST NOT be forwarded.
> 
> 
> The SII-Handle is generated by GIST and points to the GIST next hop and
> to the local interface. In this case for C the current peer QNE is A,
> but the SII-Handle points to B. Any existing reservation can neither
> over (1), nor over (2) be removed.
> 
> In case a router just rebooted, it has no current peer QNE, but should
> forward the tearing RESERVE, as discussed here
> http://www1.ietf.org/mail-archive/web/nsis/current/msg06697.html
> Existing reservations will not be removed further along the path.
> 
> Bernd
> 
> 
> 
> 
> Bernd Schloer wrote:
> > Hi Jukka,
> > 
> > 
> > the initial route A-B-C uses links (1) and (3). After link (1) fails, the
> > path is
> > rerouted using links (2) and (3).
> > 
> > 
> >              (1)
> >            /-----\                       |x| = QoS NSLP aware
> >          +-+     /-\ (3) +-+             +-+
> >      ----|A|     |B|-----|C|----
> >          +-+     \-/     +-+             /-\
> >            \-----/                       |x| = QoS NSLP unaware
> >              (2)
> > 
> > section 3.2.10 says
> > 
> >    When the QoS NSLP is aware of the route change, it needs to set up
> >    the reservation on the new path. This is done by sending a new
> >    RESERVE message. If the next QNE is, in fact, unchanged then this
> >    will be used to refresh/update the existing reservation. Otherwise it
> >    will lead to the reservation being installed on the new path.
> > 
> > 
> > section 5.3.1.says
> > 
> >    If the RSN is greater than the current stored value, the current
> > reservation
> >    MUST be modified appropriately (provided that admission control and
> > policy
> >    control succeed), and the stored RSN value updated to that for the new
> >    reservation.
> > 
> > According to section 3.2.10 sending a full RESERVE including a QSPEC and the
> > next
> > peer is unchanged the reservation will be updated/refreshed. However section
> > 5.3.1
> > talks not about refreshing/updating, it says the current reservation must be
> > modified
> > appropriately. What is the meaning of "appropriately" here? What happens to
> > the current
> > reservation?
> > 
> > When A sends a full RESERVE with set SCOPING-Flag including RII and QSPEC
> > object,
> > and if the RESERVE will be treated as an updating, refreshing RESERVE, the
> > RESPONSE
> > will contain an INFO object with Success, Reservation succesful. In case of
> > new
> > installed state, the RESPONSE contains also an INFO object with Success,
> > Reservation
> > succesful.
> > 
> > It would be helpful to make a difference between Reservation succesful and
> > Refresh
> > succesful. In case of Refresh succesful, there's no need to tear down the
> > reservation
> > on the old path. In case of Reservation succesful it might be. When link (1)
> > still
> > fails the teardown message would timeout in this example.
> > 
> > What do you think?
> > 
> > Bernd
> > 
> > 
> > 
> > 
> > Jukka MJ Manner wrote:
> > 
> > > Dear all,
> > >
> > > I sent the following request for feedback two weeks ago. No comments have
> > > been raised. I will wait until this Friday, then submit the draft.
> > >
> > > Jukka
> > >
> > > On Tue, 21 Nov 2006, Jukka MJ Manner wrote:
> > >
> > >
> > > > Hi all,
> > > >
> > > > I have done all the edits I had in my list to the QoS NSLP spec, the
> > > > main points are in recent thread with Roland. From the url below you can
> > > > find the current draft v. "13-pre1" and a diff to v. 12.
> > > >
> > > > http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
> > > >
> > > > A direct link to the diff:
> > > >
> > > > http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos-nslp-12-from-3-pre1.diff.html 
> > > >
> > > >
> > > >
> > > > I would appreciate comments on the changes I did (what is wrong, what I
> > > > missed, etc.).
> > > >
> > > >
> > > > I still have one problem with the spec, namely the way the NSLP suggests
> > > > to handle mobility and path changes. I think we need to review that
> > > > statement, because it seems like a "hack" (playing with the RSN value),
> > > > and not really useful. And the interactions with GIST look partly wrong.
> > > > The folks working on the mobility draft (me included) could comment. The
> > > > section I'm talking about is 3.2.10, especially 3.2.10.2, in the v.12
> > > > draft.
> > > >
> > > > BR,
> > > > Jukka
> > > >
> >>> _______________________________________________
> > > > nsis mailing list
> > > > nsis@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/nsis
> > > >
> > >
> > >
> >> _______________________________________________
> > > nsis mailing list
> > > nsis@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/nsis
> > 
> > 
> > _______________________________________________
> > nsis mailing list
> > nsis@ietf.org
> > https://www1.ietf.org/mailman/listinfo/nsis
> > 
> 
> 

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



From nsis-bounces@ietf.org Sun Dec 10 13:53:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtTmm-0003At-Kv; Sun, 10 Dec 2006 13:52:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtTml-0003Ak-CY
	for nsis@ietf.org; Sun, 10 Dec 2006 13:52:27 -0500
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtTmj-0006v3-Vk
	for nsis@ietf.org; Sun, 10 Dec 2006 13:52:27 -0500
Received: from sbz-31.cs.helsinki.fi (sbz-31.cs.helsinki.fi [128.214.9.99])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Sun, 10 Dec 2006 20:52:25 +0200
	id 000AFDC0.457C5769.00004D28
Date: Sun, 10 Dec 2006 20:52:25 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Bernd Schloer <bschloer@cs.uni-goettingen.de>,
	"McDonald, Andrew" <andrew.mcdonald@roke.co.uk>
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
In-Reply-To: <4579A4FC.30601@cs.uni-goettingen.de>
Message-ID: <Pine.LNX.4.64.0612102051220.11174@sbz-31.cs.Helsinki.FI>
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
	<4579A4FC.30601@cs.uni-goettingen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: nsis@ietf.org
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


Hi,

I'm a bit lost in what you are talking about.

Andrew, Section 3.2.10 is basically your design, any comment?

Jukka

On Fri, 8 Dec 2006, Bernd Schloer wrote:

> Hi Jukka,
> 
> to my knowledge the case of section 3.2.10.2 is not covered in section 5.4.1,
> where the Message Processing Rules of RESERVE Messages are explained. A sends
> a RESERVE
> to C while on Node A and C still reservation state for this Session ID is
> installed. The
> FlowID is unchanged, the MRI is unchanged, the REPLACE-Flag is not set, the
> Session
> ID is the same and the SII-Handle is unchanged for C.
> 
> However there's a case for sessions with the REPLACE flag = 0 (does this mean
> a received
> RESERVE message where the REPLACE flag in the Common Header is not set?) where
> it is
> assumed that the QoS model includes directions to deal with resource sharing.
> Adding a
> reservation or taking the the maximum of two? Or more complex mathematical
> operations?
> What does this mean?
> 
> But back to the rerouting problem. When A attempts to tear down the
> reservation on the old
> path by specifying explicit routing to the old peer with the related
> SII-Handle, nothing
> would happen, when link (1) still fails.
> 
> Bernd
> 
> 
> 
> Jukka MJ Manner wrote:
> > Dear all,
> > 
> > I sent the following request for feedback two weeks ago. No comments have
> > been raised. I will wait until this Friday, then submit the draft.
> > 
> > Jukka
> > 
> > On Tue, 21 Nov 2006, Jukka MJ Manner wrote:
> > 
> > 
> > >Hi all,
> > >
> > >I have done all the edits I had in my list to the QoS NSLP spec, the main
> > >points are in recent thread with Roland. From the url below you can find
> > >the current draft v. "13-pre1" and a diff to v. 12.
> > >
> > >http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
> > >
> > >A direct link to the diff:
> > >
> > >http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos-nslp-12-from-3-pre1.diff.html
> > >
> > >
> > >I would appreciate comments on the changes I did (what is wrong, what I
> > >missed, etc.).
> > >
> > >
> > >I still have one problem with the spec, namely the way the NSLP suggests to
> > >handle mobility and path changes. I think we need to review that statement,
> > >because it seems like a "hack" (playing with the RSN value), and not really
> > >useful. And the interactions with GIST look partly wrong. The folks working
> > >on the mobility draft (me included) could comment. The section I'm talking
> > >about is 3.2.10, especially 3.2.10.2, in the v.12 draft.
> > >
> > >BR,
> > >Jukka
> > >
> >>_______________________________________________
> > >nsis mailing list
> > >nsis@ietf.org
> > >https://www1.ietf.org/mailman/listinfo/nsis
> > >
> > 
> > 
> > _______________________________________________
> > nsis mailing list
> > nsis@ietf.org
> > https://www1.ietf.org/mailman/listinfo/nsis
> 
> 

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



From nsis-bounces@ietf.org Sun Dec 10 13:53:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtTnN-0003Jg-7C; Sun, 10 Dec 2006 13:53:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtTnM-0003Hy-I8
	for nsis@ietf.org; Sun, 10 Dec 2006 13:53:04 -0500
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtTnL-0006v3-0l
	for nsis@ietf.org; Sun, 10 Dec 2006 13:53:04 -0500
Received: from sbz-31.cs.helsinki.fi (sbz-31.cs.helsinki.fi [128.214.9.99])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Sun, 10 Dec 2006 20:53:02 +0200
	id 000AFDA5.457C578E.00006223
Date: Sun, 10 Dec 2006 20:53:02 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Bernd Schloer <bschloer@cs.uni-goettingen.de>,
	"McDonald, Andrew" <andrew.mcdonald@roke.co.uk>
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
In-Reply-To: <457ADA83.3000600@cs.uni-goettingen.de>
Message-ID: <Pine.LNX.4.64.0612102052340.11174@sbz-31.cs.Helsinki.FI>
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
	<457ADA83.3000600@cs.uni-goettingen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Cc: nsis@ietf.org
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


Andy, since this is your design, any comments?

Jukka

On Sat, 9 Dec 2006, Bernd Schloer wrote:

> Hi Jukka,
> 
> 
> the initial route A-B-C uses links (1) and (3). After link (1) fails, the path
> is
> rerouted using links (2) and (3).
> 
> 
>              (1)
>            /-----\                       |x| = QoS NSLP aware
>          +-+     /-\ (3) +-+             +-+
>      ----|A|     |B|-----|C|----
>          +-+     \-/     +-+             /-\
>            \-----/                       |x| = QoS NSLP unaware
>              (2)
> 
> section 3.2.10 says
> 
>    When the QoS NSLP is aware of the route change, it needs to set up
>    the reservation on the new path. This is done by sending a new
>    RESERVE message. If the next QNE is, in fact, unchanged then this
>    will be used to refresh/update the existing reservation. Otherwise it
>    will lead to the reservation being installed on the new path.
> 
> 
> section 5.3.1.says
> 
>    If the RSN is greater than the current stored value, the current
>    reservation
>    MUST be modified appropriately (provided that admission control and policy
>    control succeed), and the stored RSN value updated to that for the new
>    reservation.
> 
> According to section 3.2.10 sending a full RESERVE including a QSPEC and the
> next
> peer is unchanged the reservation will be updated/refreshed. However section
> 5.3.1
> talks not about refreshing/updating, it says the current reservation must be
> modified
> appropriately. What is the meaning of "appropriately" here? What happens to
> the current
> reservation?
> 
> When A sends a full RESERVE with set SCOPING-Flag including RII and QSPEC
> object,
> and if the RESERVE will be treated as an updating, refreshing RESERVE, the
> RESPONSE
> will contain an INFO object with Success, Reservation succesful. In case of
> new
> installed state, the RESPONSE contains also an INFO object with Success,
> Reservation
> succesful.
> 
> It would be helpful to make a difference between Reservation succesful and
> Refresh
> succesful. In case of Refresh succesful, there's no need to tear down the
> reservation
> on the old path. In case of Reservation succesful it might be. When link (1)
> still
> fails the teardown message would timeout in this example.
> 
> What do you think?
> 
> Bernd
> 
> 
> 
> 
> Jukka MJ Manner wrote:
> > Dear all,
> > 
> > I sent the following request for feedback two weeks ago. No comments have
> > been raised. I will wait until this Friday, then submit the draft.
> > 
> > Jukka
> > 
> > On Tue, 21 Nov 2006, Jukka MJ Manner wrote:
> > 
> > 
> > >Hi all,
> > >
> > >I have done all the edits I had in my list to the QoS NSLP spec, the main
> > >points are in recent thread with Roland. From the url below you can find
> > >the current draft v. "13-pre1" and a diff to v. 12.
> > >
> > >http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
> > >
> > >A direct link to the diff:
> > >
> > >http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos-nslp-12-from-3-pre1.diff.html
> > >
> > >
> > >I would appreciate comments on the changes I did (what is wrong, what I
> > >missed, etc.).
> > >
> > >
> > >I still have one problem with the spec, namely the way the NSLP suggests to
> > >handle mobility and path changes. I think we need to review that statement,
> > >because it seems like a "hack" (playing with the RSN value), and not really
> > >useful. And the interactions with GIST look partly wrong. The folks working
> > >on the mobility draft (me included) could comment. The section I'm talking
> > >about is 3.2.10, especially 3.2.10.2, in the v.12 draft.
> > >
> > >BR,
> > >Jukka
> > >
> >>_______________________________________________
> > >nsis mailing list
> > >nsis@ietf.org
> > >https://www1.ietf.org/mailman/listinfo/nsis
> > >
> > 
> > 
> > _______________________________________________
> > nsis mailing list
> > nsis@ietf.org
> > https://www1.ietf.org/mailman/listinfo/nsis
> 

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



From nsis-bounces@ietf.org Mon Dec 11 04:23:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GthN0-0006Cq-1B; Mon, 11 Dec 2006 04:22:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GthMy-0006Cg-Da
	for nsis@ietf.org; Mon, 11 Dec 2006 04:22:44 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GthMr-000795-6X
	for nsis@ietf.org; Mon, 11 Dec 2006 04:22:44 -0500
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 3EC835DA; 
	Mon, 11 Dec 2006 10:22:32 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 11 Dec 2006 10:22:32 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 11 Dec 2006 10:22:31 +0100
Message-ID: <457D2357.3060503@ericsson.com>
Date: Mon, 11 Dec 2006 10:22:31 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: NSIS <nsis@ietf.org>
Content-Type: multipart/mixed; boundary="------------040102040406090503050904"
X-OriginalArrivalTime: 11 Dec 2006 09:22:31.0698 (UTC)
	FILETIME=[E297A720:01C71D05]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 9f79b8e383fd3af2b1b5b1d0910f6094
Cc: meadows@itd.nrl.navy.mil
Subject: [NSIS] [Fwd: secdir review of draft-ietf-nsis-nslp-natfw-13.txt]
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


This is a multi-part message in MIME format.
--------------040102040406090503050904
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi NSIS

Many thanks to Catherine Meadows (CC) who has done the Security 
Directorate review attached. It was done on my and the WG chairs request 
through the security ADs to help check the security details of the 
document. It contains the normal boilerplate for document that are in 
IESG review, but as you know this document isn't in that step yet. I 
hope this can help improve the document.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

--------------040102040406090503050904
Content-Type: message/rfc822;
	name="secdir review of draft-ietf-nsis-nslp-natfw-13.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename="secdir review of draft-ietf-nsis-nslp-natfw-13.txt"

Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw103.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 10 Dec 2006 15:29:53 +0100
Received: from mailgw5.ericsson.se ([193.180.251.36]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 10 Dec 2006 15:29:53 +0100
Received: from megatron.ietf.org (stiedprmman1.ietf.ORG [156.154.16.145])
	by mailgw5.ericsson.se (Symantec Mail Security) with ESMTP id
	D55CE400026 for <magnus.westerlund@ericsson.com>;
	Sun, 10 Dec 2006 15:29:51 +0100 (CET)
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtPgT-0008F9-3p; Sun, 10 Dec 2006 09:29:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtPgR-0008F4-Um
	for iesg@ietf.org; Sun, 10 Dec 2006 09:29:39 -0500
Received: from fw5540.nrl.navy.mil ([132.250.196.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtPgR-0007sf-GF
	for iesg@ietf.org; Sun, 10 Dec 2006 09:29:39 -0500
Received: from chacs.nrl.navy.mil (sun1.fw5540.net [10.0.0.11])
	by fw5540.nrl.navy.mil (8.13.6/8.13.6) with ESMTP id kBAETVMf011276;
	Sun, 10 Dec 2006 09:29:31 -0500 (EST)
Received: from chacs.nrl.navy.mil (sun1 [10.0.0.11])
	by chacs.nrl.navy.mil (8.13.6/8.13.6) with SMTP id kBAETU0K016183;
	Sun, 10 Dec 2006 09:29:30 -0500 (EST)
Received: from [127.0.0.1] ([10.0.0.13])
	by chacs.nrl.navy.mil (SMSSMTP 4.1.11.41) with SMTP id
	M2006121009292903034 ; Sun, 10 Dec 2006 09:29:29 -0500
Mime-Version: 1.0 (Apple Message framework v752.2)
To: iesg@ietf.org, secdir@mit.edu, nsis-chairs@tools.ietf.org,
	stiemerling@netlab.nec.de, hannes.tschofenig@siemens.com,
	elwynd@dial.pipex.com
Message-Id: <048F2FE6-29A1-4EDF-8C0D-199F98FA3DEA@itd.nrl.navy.mil>
Content-Type: multipart/alternative; boundary=Apple-Mail-2-622888637
From: Catherine Meadows <meadows@itd.nrl.navy.mil>
Date: Sun, 10 Dec 2006 09:32:45 -0500
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bc6181926481d86059e678c9f7cb8b34
Cc: Catherine Meadows <meadows@itd.nrl.navy.mil>
Subject: secdir review of draft-ietf-nsis-nslp-natfw-13.txt 
X-BeenThere: iesg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: iesg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/iesg>,
	<mailto:iesg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www1.ietf.org/mailman/private/iesg>
List-Post: <mailto:iesg@ietf.org>
List-Help: <mailto:iesg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/iesg>,
	<mailto:iesg-request@ietf.org?subject=subscribe>
Errors-To: iesg-bounces@ietf.org
X-Brightmail-Tracker: AAAAAA==
Return-Path: iesg-bounces@ietf.org
X-OriginalArrivalTime: 10 Dec 2006 14:29:53.0221 (UTC)
	FILETIME=[A82EFF50:01C71C67]




--Apple-Mail-2-622888637
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

This ID describes a protocol by which hosts may signal along the path  
used
for transport of data packets the information necessary to configure
NATs and firewalls
according to the needs of the
application data flows.  Not surprisingly, the use of this protocol  
by unauthorized
hosts could cause major security problems.  The security  
considerations considerations section of this document describes the  
problems in detail,
and outlines recommendations for solutions.  These are to have
security mechanisms providing data origin authentication, replay  
protection, integrity protection, and optional confidentiality  
protection.  According to this document, uch security
mechanisms can be provided for neighboring nodes
by using a mutually authenticated
transport layer secured connection and by relying on authorization by  
the
neighboring NATFW NSLP entities, as well as randomly generated (that is,
unpredictable) session IDs.

For non-neighboring nodes (presumably, this means nodes that do not  
share
a security association) some sort of authorization is still  
necessary.  The document
discusses the possibility of using authorization tokens for this, and  
also provides
some recommendations for protecting them (e.g. protection against  
tampering
and confidentiality to protect against replay).  The document does not
go into detail about this, apparently because the usage of  
authorization tokens
in NPLS is covered in another document (referenced in this ID).

This security strategy looks plausible, but I found the justification  
for it very hard to follow.  It starts with a number of possible  
attacks that an unauthorized host could perform using NSLP.  Almost  
all of these attacks can be prevented by providing authorization (the  
exceptions are one or two denial of service attacks), and  
recommendations for authorizations are accordingly provided.    
However, there
are two cases in which such recommendations are lacking.  In one of  
these
(5.2.3, data sender behind a firewall), no reason is given for the  
lack of a recommendation.  In the other (5.8, misuse of unreleased  
sessions), it is claimed
that this will be addressed by the NATFW NSLP.  This last confused me;
isn't that the protocol that this document describes?

The list of attacks appears to have grown up over a period of time as  
the document went through its various iterations.  In its current  
form, the list is not very helpful, especially as the end of the  
security considerations section, in which the actual recommendations  
are made do not reference them explicitly.  Instead, there
are somewhat vague comments such as
    Almost all security threats at the
    NATFW NSLP layer can be prevented by using a mutually authenticated
    Transport Layer secured connection and by relying on  
authorization by
    the neighboring NATFW NSLP entities.
It would have been helpful for the reader to know what is meant by  
"almost all"
without having to go back through the entire list of attacks.

I would suggest that the authors provide a tightened up, condensed  
account of the
security threats against NSLP.  There is no need to try to have an  
exhaustive list
of attacks; indeed such a list will be of limited use since one can  
never be certain that all the possibilities can be exhaustive.   
Instead, it would be more helpful to described classes of threats,  
with some illustrative examples.

In the final section, where the recommendations for security  
mechanisms are
made, you need to be explicit about the types of threats that are  
addressed.
In particular,  some characterization of the types of threats that  
are and are not addressed by authentication and authorization of  
neighboring nodes needs to be provided,


I am wondering if it would not be a good idea to have a separate ID
describing the security mechanisms that need to be used by this  
protocol.
The WG already seems to be halfway there, since they are already working
on an ID for authentication tokens.

Catherine Meadows
Head, Formal Methods Section
Center for High Assurance Computer Systems
Code 5540
Naval Research Laboratory
Washington, DC 20375
phone: +1-202-767-3490
fax: +1-202-404-7942


--Apple-Mail-2-622888637
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; "><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I have =
reviewed this document as part of the security directorate's</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">ongoing effort to review all IETF documents being =
processed by the</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">IESG.=A0 These comments were =
written primarily for the benefit of the</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">security =
area directors.=A0 Document editors and WG chairs should treat</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">these comments just like any other last call =
comments.</DIV><DIV><BR class=3D"khtml-block-placeholder"></DIV><DIV>This =
ID describes a protocol by which hosts may signal along the path =
used</DIV><DIV>for transport of data packets the information necessary =
to configure</DIV><DIV>NATs and firewalls=A0</DIV><DIV>according to the =
needs of the</DIV><DIV>application data flows.=A0 Not surprisingly, the =
use of this protocol by unauthorized</DIV><DIV>hosts could cause major =
security problems.=A0 The security considerations considerations section =
of this document describes the problems in detail,</DIV><DIV>and =
outlines recommendations for solutions.=A0 These are to =
have</DIV><DIV>security mechanisms providing data origin authentication, =
replay protection, integrity protection, and optional confidentiality =
protection.=A0 According to this document, uch =
security</DIV><DIV>mechanisms can be provided for neighboring =
nodes</DIV><DIV>by using a mutually authenticated</DIV><DIV>transport =
layer secured connection and by relying on authorization by =
the</DIV><DIV>neighboring NATFW NSLP entities, as well as randomly =
generated (that is,</DIV><DIV>unpredictable) session =
IDs.</DIV><DIV><BR></DIV><DIV>For non-neighboring nodes (presumably, =
this means nodes that do not share</DIV><DIV>a security association) =
some sort of authorization is still necessary.=A0 The =
document</DIV><DIV>discusses the possibility of using authorization =
tokens for this, and also provides</DIV><DIV>some recommendations for =
protecting them (e.g. protection against tampering</DIV><DIV>and =
confidentiality to protect against replay).=A0 The document does =
not</DIV><DIV>go into detail about this, apparently because the usage of =
authorization tokens</DIV><DIV>in NPLS is covered in another document =
(referenced in this ID).</DIV><DIV><BR></DIV><DIV>This security strategy =
looks plausible, but I found the justification for it very hard to =
follow.=A0 It starts with a number of possible attacks that an =
unauthorized host could perform using NSLP.=A0 Almost all of these =
attacks can be prevented by providing authorization (the exceptions are =
one or two denial of service attacks), and recommendations for =
authorizations are accordingly provided. =A0 However, =
there</DIV><DIV>are two cases in which such recommendations are =
lacking.=A0 In one of these</DIV><DIV>(5.2.3, data sender behind a =
firewall), no reason is given for the lack of a recommendation.=A0 In =
the other (5.8, misuse of unreleased sessions), it is =
claimed</DIV><DIV>that this will be addressed by the NATFW NSLP.=A0 This =
last confused me;</DIV><DIV>isn't that the protocol that this document =
describes?</DIV><DIV><BR></DIV><DIV>The list of attacks appears to have =
grown up over a period of time as the document went through its various =
iterations.=A0 In its current form, the list is not very helpful, =
especially as the end of the security considerations section, in which =
the actual recommendations are made do not reference them explicitly.=A0 =
Instead, there</DIV><DIV>are somewhat vague comments such =
as=A0</DIV><DIV>=A0=A0 Almost all security threats at the</DIV><DIV>=A0=A0=
 NATFW NSLP layer can be prevented by using a mutually =
authenticated</DIV><DIV>=A0=A0 Transport Layer secured connection and by =
relying on authorization by</DIV><DIV>=A0=A0 the neighboring NATFW NSLP =
entities.</DIV><DIV>It would have been helpful for the reader to know =
what is meant by "almost all"</DIV><DIV>without having to go back =
through the entire list of attacks.</DIV><DIV><BR></DIV><DIV>I would =
suggest that the authors provide a tightened up, condensed account of =
the=A0</DIV><DIV>security threats against NSLP.=A0 There is no need to =
try to have an exhaustive list</DIV><DIV>of attacks; indeed such a list =
will be of limited use since one can never be certain that all the =
possibilities can be exhaustive.=A0 Instead, it would be more helpful to =
described classes of threats, with some illustrative =
examples.</DIV><DIV><BR></DIV><DIV>In the final section, where the =
recommendations for security mechanisms are</DIV><DIV>made, you need to =
be explicit about the types of threats that are addressed.</DIV><DIV>In =
particular,=A0 some characterization of the types of threats that are =
and are not addressed by=A0authentication and authorization of =
neighboring nodes needs to be provided,</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>I am wondering if it would =
not be a good idea to have a separate ID</DIV><DIV>describing the =
security mechanisms that need to be used by this protocol.</DIV><DIV>The =
WG already seems to be halfway there, since they are already =
working</DIV><DIV>on an ID for authentication tokens.</DIV><BR><DIV> <P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><FONT face=3D"Helvetica" =
size=3D"3" style=3D"font: 12.0px Helvetica">Catherine Meadows</FONT></P> =
<P style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><FONT face=3D"Helvetica" =
size=3D"3" style=3D"font: 12.0px Helvetica">Head, Formal Methods =
Section</FONT></P> <P style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><FONT =
face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px Helvetica">Center =
for High Assurance Computer Systems</FONT></P> <P style=3D"margin: 0.0px =
0.0px 0.0px 0.0px"><FONT face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica">Code 5540</FONT></P> <P style=3D"margin: 0.0px 0.0px =
0.0px 0.0px"><FONT face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">Naval Research Laboratory</FONT></P> <P style=3D"margin: =
0.0px 0.0px 0.0px 0.0px"><FONT face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica">Washington, DC 20375</FONT></P> <P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><FONT face=3D"Helvetica" =
size=3D"3" style=3D"font: 12.0px Helvetica">phone: =
+1-202-767-3490</FONT></P> <P style=3D"margin: 0.0px 0.0px 0.0px =
0.0px"><FONT face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">fax: +1-202-404-7942</FONT></P>  </DIV><BR></BODY></HTML>=

--Apple-Mail-2-622888637--



--------------040102040406090503050904
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--------------040102040406090503050904--




From nsis-bounces@ietf.org Mon Dec 11 07:20:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gtk7x-0006Zm-4D; Mon, 11 Dec 2006 07:19:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtk7v-0006ZH-Nf
	for nsis@ietf.org; Mon, 11 Dec 2006 07:19:23 -0500
Received: from tmailer.gwdg.de ([134.76.10.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gtk7m-0006gF-Md
	for nsis@ietf.org; Mon, 11 Dec 2006 07:19:16 -0500
Received: from s5.ifi.informatik.uni-goettingen.de ([134.76.81.25]
	helo=[172.22.0.58])
	by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.60)
	(envelope-from <fu@cs.uni-goettingen.de>)
	id 1Gtk7h-0005O8-Qp; Mon, 11 Dec 2006 13:19:09 +0100
Message-ID: <457D4CBE.6050701@cs.uni-goettingen.de>
Date: Mon, 11 Dec 2006 13:19:10 +0100
From: Xiaoming Fu <fu@cs.uni-goettingen.de>
Organization: University of Goettingen, Germany
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Bernd Schloer <bschloer@cs.uni-goettingen.de>
Subject: Re: [NSIS] Question to the CL QoS Model authors
References: <Pine.LNX.4.64.0610102342390.21326@sbz-31.cs.Helsinki.FI>
	<452C87AD.1080702@cs.uni-goettingen.de>
	<4576C336.8020406@cs.uni-goettingen.de>
In-Reply-To: <4576C336.8020406@cs.uni-goettingen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated: Id:xfu
X-Spam-Level: -
X-Virus-Scanned: (clean) by exiscan+sophie
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Cc: Jukka MJ Manner <jmanner@cs.Helsinki.FI>, nsis@ietf.org, "Kappler,
	Cornelia" <cornelia.kappler@siemens.com>
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

Hi Bernd,

Bernd Schloer wrote:
> Hi,
> 
> with the proposed e2e QSPEC object remapping is not necessary any more. 
> Since CLS
> relies on Token Bucket as the only parameter, no local QSPEC needs to be 
> defined.
True.

> I assume QoSClass and Priority is ignored by CLS QOSM from now on. Still 
> interesting
> could be two different queues to handle CL and Best Effort traffic.
This is clear enough to all, I think. Any open issue on this?

> The interoperation with RSVP is another open issue. The table in section 
> 7 shows
> a mapping of objects and parameters between QoS NSLP and RSVP.
> 
> A RSVP PATH message contains a Sender TSpec and an ADSpec object. The 
> Sender TSpec
> describes the traffic specification while the ADSpec probes for 
> available Bandwidth.
> The ADSpec can be mapped to <QoS Available> (Bandwidth) and the Sender 
> TSpec +
> FlowSpec to <QoS Desired> and opt. <Minimum QoS> (both Token Bucket).
> 
> Compared to the table in section 6.4.2 of the QSPEC Template the <QoS 
> Desired> is
> missing in the QUERY and RESERVE message. How does this fit together? 
> The Object
> Combination is not optional from my understanding. The CLS-draft 
> mentions that
> Sender-TSpec and ADSpec cannot be mapped easily. Does this mean 
> multicast flows
> and merged FlowSpecs?
Please do not confuse here: multicast is not considered with current 
NSIS CLS.
The mapping of RSVP Path Sender-TPSEC (key parameter: Token bucket) 
should be clear now, as QoS NSLP Query shall have a key CLS parameter: 
QoS Available which has token bucket as part of "Traffic" now.
RSVP ADSPEC contains MTU, which we didn't include in CLS QoS Available 
(probably can add in the next version?).
> 
> Where is the difference between one-pass, One Pass with 
> Advertising(OPWA) and the
> two-pass reservation model? Are there more? When the Sender includes an 
> ADSpec in the
> Path message, it's OPWA, without ADSpec it's one-pass. The 
> Receiver-Initiated Reservation
> is two-pass?
This can be found in some tutorial. For NSIS I don't think this is a 
fundamental question while specifying CLS service: QoS NSLP simply 
provides necessary facility for CLS service users to use.

> 
> There are three examples in Appendix B.2 showing how the QSPEC in a 
> QUERY message
> can be composed and interpreted.
> 
> 1.The Sender (QNR) collects information about the available bandwidth 
> with a QUERY
> message containing <QoS Available>. The Receiver (QNI) generates a 
> RESERVE message
> with <QoS Desired> based on <QoS Available>. The Sender (QNR) sends back 
> a RESPONSE
> with <QoS Reserved> which carries information about the performed 
> reservation.
> According to the QSPEC Procedures <QoS Available> is missing in the 
> QUERY and RESERVE.

Ok - will fix in Query, but QoS Available might be optional for RESERVE 
(it already contains QoS RESERVED!) here I think.
> 
> The next two examples are not quite clear to me.
> 2.  When the QNR composes the <QoS Desired> based on <QoS Available> it 
> uses a Token
> Bucket (QNE-readonly). A Resource QUERY can get <QoS Available>. I'm not 
> sure if this
> is draft-conform: The QNR could pretend to be a QNI for the QUERY to 
> make then a
> Receiver-Initiated Reservation as QNR. From my understanding a QNR can't 
> do a Resource
> QUERY along the path to the QNI.

I don't get at it. Your assumption of having QNR to act as QNI is not 
necessarily true, if sufficient security measures are provided.

> 
> 3. Peak-Rate can be mapped to Bandwidth. The Traffic object contains 
> both, Token Bucket
> and Bandwidth. Using Bandwidth avoids mapping and interpreting certain 
> fields of TB,
> but each QNE along the path should know how to deal with the new <QoS 
> Available>.

Sorry, what is the question?
Xiaoming
> 
> Comments?
> 
> Bernd
> 
> 
> 
> 
> 
> 
> Xiaoming Fu wrote:
>> Hi Jukka,
>>
>> The CLS draft is actually a remapping of RSVP CLS parameters (and 
>> procedures) to NSIS.
>>
> In the table in section 7 <QoS Desired> (QUERY and RESERVE) is not 
> mentioned
> as in the QSPEC Procedures. The same with <QoS Available> for RESPONSE. 
> Also
> in section 5.3 <QoS Desired> is not mentioned. Are these parameter 
> optional? > In the QSPEC-1 parameters specified in 
> [draft-ietf-nsis-qspec], there
>> are the following two types:
>>
>> - <Excess Treatment> is an optional parameter in QNI, namely it can be 
>> included or excluded in the CLS control information. If it is included 
>> in a message, then CLS QNE must interpret and populate it.
>>
>> - <QoS Desired> and <QoS Reserved> are mandatory for all (QNI QNEs QNR)
>> including other QoSMs; <QoS Available> mandatory for 
>> receiver-initiated reservation, but optional for sender-initiated 
>> reservation.
>>
>> however, we didn't discuss how exactly the objects other than Token 
>> Bucket(s) inside the QoS Desired etc should be handled. We thought a 
>> QNE doesn't need to include (for QNI/QNR) nor interpret any of them.
>>
>> Any remarks on this?
>> Xiaoming
>>
>> Jukka MJ Manner wrote:
>>
>>> Hi Xiaoming and Cornelia,
>>>
>>> I was wondering if you have some ideas on how the CL QoS Model would 
>>> handle all the current QSPEC-1 parameters? Your draft lists that as 
>>> an open issue.
>>>
>>> Cheers,
>>> Jukka
>>>
>>> _______________________________________________
>>> nsis mailing list
>>> nsis@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/nsis
>>
>>

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



From nsis-bounces@ietf.org Mon Dec 11 10:53:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtnSV-0007Lg-Ma; Mon, 11 Dec 2006 10:52:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtnSU-0007La-O0
	for nsis@ietf.org; Mon, 11 Dec 2006 10:52:50 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtnSR-0001QF-RT
	for nsis@ietf.org; Mon, 11 Dec 2006 10:52:50 -0500
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-4.cisco.com with ESMTP; 11 Dec 2006 07:52:47 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id kBBFqk26025107; 
	Mon, 11 Dec 2006 07:52:46 -0800
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kBBFqjin003162;
	Mon, 11 Dec 2006 07:52:46 -0800 (PST)
Received: from [10.32.245.152] ([10.32.245.152])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id kBBFbPDJ011463;
	Mon, 11 Dec 2006 07:37:25 -0800
In-Reply-To: <45784902.4000104@tm.uka.de>
References: <BAA65A575825454CBB0103267553FCCC017BB967@esebe199.NOE.Nokia.com>
	<45767C7F.20509@tm.uka.de>
	<2C1E330A-A77D-40D6-86E4-3B305AAE5E48@cisco.com>
	<45784902.4000104@tm.uka.de>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7D03BA9A-856A-4F70-B8C4-0FCE3B65DA81@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Mon, 11 Dec 2006 10:52:42 -0500
To: Roland Bless <bless@tm.uka.de>
X-Mailer: Apple Mail (2.752.2)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4413; t=1165852366;
	x=1166716366; c=relaxed/simple; s=sjdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[NSIS]=20QoS=20NSLP=3A=20Stacking=20vs.=20tunneling=2
	0vs. |Sender:=20;
	bh=BmtrBsuPGTDS+PmVPMl9bnE7YOJuSr5YZiiVMuqf3OI=;
	b=gRmfqM6N7cpMtzkJlT91awvSsaKTytOJKrL6NZ/iPSW/CW6z/wiU8bTXUts8qgQm2AWFDYAB
	ss0w/ZRxRJsSVTRQWCDtLMgWXwnshMu1/+GmeaElz2O5sarD2ID02Fbf;
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4413; t=1165851446;
	x=1166715446; c=relaxed/simple; s=oregon;
	h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; 
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[NSIS]=20QoS=20NSLP=3A=20Stacking=20vs.=20tunneling=2
	0vs. |Sender:=20 |To:=20Roland=20Bless=20<bless@tm.uka.de>;
	bh=BmtrBsuPGTDS+PmVPMl9bnE7YOJuSr5YZiiVMuqf3OI=;
	b=PR1EnRIWb4n7l/aBMpdeXNEEv/b7iENjjNGk6w7zrDBs/GVhR3XERwn4j4c4l/OFRcOQmNWF
	xtlAKx1AvPwf9uiuW+AkYSh1dhWgTao4pzmQGGIitmEHlcgIBvx28hPP;
Authentication-Results: sj-dkim-1; header.From=oran@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim1002 verified; ); 
	header.From=oran@cisco.com; dkim=pass (
	sig from cisco.com/oregon verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: john.loughney@nokia.com, "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	karagian@cs.utwente.nl, nsis@ietf.org
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


On Dec 7, 2006, at 12:01 PM, Roland Bless wrote:

> Hi Dave,
>
> please see comments inline.
>
> David R Oran wrote:
>>
>> On Dec 6, 2006, at 3:17 AM, Roland Bless wrote:
>>
>>> Hi John,
>>>
>>> john.loughney@nokia.com wrote:
>>>> Could you summize your proposal, making it easier just to verify
>>>> that we can come to consensus on this? It looked like there
>>>> was some meandering on the email threads about some parts
>>>> of your proposal, so it wasn't clear that we had complete
>>>> consensus on your initial proposal.
>>>
>>> Ok, I'll try once again.
>>>
>>> 1. each QSPEC has a type (QSPEC-ID) instead of this QOSM-ID
>>>    because I think that some QSPECs are applicable to more
>>>    than one QOSM (e.g., the e2e QSPEC) and some QOSM may understand
>>>    more than one QSPEC type.
>>>
>>> 2. Instead of supporting stacking QSPEC objects in QoS-NSLP
>>>    I suggest to have only a "single" QSPEC object in a QoS-NSLP.
>>>    If one wants to carry other QSPECs transparently or simply
>>>    add parameters of local meaning etc. one could
>>>    simply define an "encapsulation" for its own QSPEC type
>>>    like this:
>> This strikes me as really ugly and bug-prone, but it would work  
>> and give
>> the necessary functionality. In my opinion, it'sbetter to have  
>> either an
>
> It would be interesting to hear why it's ugly and bug-prone in
> more technical detail.
>
>> explicit stack (so you don't have to figure out whether you've  
>> escaped
>> from the closed environment and generate errors), or multiple QSPEC
>> objects that an RMF can fetch from QNLSP by registered type (so you
>> don't have to co-mingle parsers).
>
> Maybe I don't get your points completely, let's see, so I have a  
> couple
> of questions:
> If a local QSPEC escapes, the next domain will probably not
> understand the QSPEC type and send back an error indicating the
> leakage.
Yes, except if the encoding were stacked or not dependent on  
understanding the local QSPEC in order to find and parse the end-to- 
end QSPEC, things would be much more error resilient.

> Is this a problem? Are there better ways to handle this?
Yes. Allow multiple QSPEC objects.

> What would happen in the case of stacking?
you can pop without having to parse.

> Would the RMF in the next ingress QNE simply search through the  
> stack of
> QSPECs until it hits one of the supported QSPEC types or the e2e  
> QSPECs?
If we did stacking, yes. If we simply had parallel QSPECS, it could  
just scan.

> Would it ignore (an/or pass on) unknown QSPECs within the stack?
Sure. Why not.

> Should QoS-NSLP pass always the whole QSPEC stack up to the RMF
> or only registered types?
API detail... Doesn't matter to the protocol definition.

> How can we guarantee that the QSPECs are still "matching" the  
> request if
> some of them are ignored and not adapted in intermediate domains?
>
We can't. OTOH, since any intermediary can re-write it's a guarantee  
we can't make anyway (unless we want to go to extremes of having  
signed QSPECS and stuff like that).

> With this kludgy encapsulation thing, an RMF should know that
> there is an e2e QSPEC (or other QSPECs) enclosed and either may ignore
> it completely or process it accordingly, so the semantics should be
> clear.
A fee-for all in how you encapsulate an end-to-end QSPEC in a local  
QSPEC will of course "work". My concerns are aesthetic and  
engineering economy, which is why I'm not making a big deal out of this.

> But maybe I'm missing something or a lot of things completely,
> so if you have more rationale, it would be good to hear that.
>
>> I don't want to make a big deal about how kludgy this encoding  
>> approach
>> is - if this can get WG consensus it isn't a make-or-break design  
>> issue.
>
> We shouldn't really go there if this is really kludgy and ugly.
> My understanding was that most people in the WG seemed to
> dislike QSPEC stacking and thought it would be too complex
> (that's why stacking was limited to two QSPECs only).
We can agree to disagree on that. I find stacking to be simple,  
elegant and allows for recursion as an extensibility mechanism.

Dave.


> So Georgios
> and his colleagues want to have a functionality like this.
> But probably there are better ways to do that...
>
> Regards,
>  Roland

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



From nsis-bounces@ietf.org Mon Dec 11 11:42:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtoES-0004xt-SI; Mon, 11 Dec 2006 11:42:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtoEQ-0004wh-TN
	for nsis@ietf.org; Mon, 11 Dec 2006 11:42:22 -0500
Received: from mail146.messagelabs.com ([216.82.245.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GtoEP-0001uX-LH
	for nsis@ietf.org; Mon, 11 Dec 2006 11:42:22 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-15.tower-146.messagelabs.com!1165855340!921297!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 7364 invoked from network); 11 Dec 2006 16:42:20 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-15.tower-146.messagelabs.com with SMTP;
	11 Dec 2006 16:42:20 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kBBGgIeM004226; 
	Mon, 11 Dec 2006 11:42:20 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id
	kBBGgAjq004096; Mon, 11 Dec 2006 11:42:12 -0500 (EST)
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
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Mon, 11 Dec 2006 10:41:55 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC8028@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <7D03BA9A-856A-4F70-B8C4-0FCE3B65DA81@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Thread-Index: AccdPGzoHBHzQbaKQ1yXUmKsVqTXDQABbdOw
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "David R Oran" <oran@cisco.com>, "Roland Bless" <bless@tm.uka.de>,
	<john.loughney@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, nsis@ietf.org
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

> I find stacking to be simple, =20
> elegant and allows for recursion as an extensibility mechanism.

So should we retain stacking instead of encapsulation?  After all, we
allowed stacking of 2 QSPECs for more than 2 years now, so I don't think
there is an urgency to change it now.

It is OK with me to retain stacking instead of using encapsulation.

We need to resolve this issue; it would be good to resolve before the
next update to our QSPEC draft if possible.

Thanks,
Jerry

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



From nsis-bounces@ietf.org Mon Dec 11 15:19:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gtrbh-00047z-NN; Mon, 11 Dec 2006 15:18:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtrbg-00047p-5E
	for nsis@ietf.org; Mon, 11 Dec 2006 15:18:36 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gtrbd-0008FS-S9
	for nsis@ietf.org; Mon, 11 Dec 2006 15:18:36 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 11 Dec 2006 12:18:33 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kBBKIWQR028010; 
	Mon, 11 Dec 2006 12:18:32 -0800
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id kBBKIWW4018716;
	Mon, 11 Dec 2006 12:18:32 -0800 (PST)
Received: from [161.44.182.96] (dhcp-161-44-182-96.cisco.com [161.44.182.96])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id kBBK3AeO021960;
	Mon, 11 Dec 2006 12:03:11 -0800
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC8028@KCCLUST06EVS1.ugd.att.com>
References: <9473683187ADC049A855ED2DA739ABCA0DDC8028@KCCLUST06EVS1.ugd.att.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5D944CA2-DE95-4130-BFFB-03DCFE8429B5@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Mon, 11 Dec 2006 15:18:28 -0500
To: "Ash, Gerald R ((Jerry)), ALABS" <gash@att.com>
X-Mailer: Apple Mail (2.752.2)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=714; t=1165868313;
	x=1166732313; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[NSIS]=20QoS=20NSLP=3A=20Stacking=20vs.=20tunneling=2
	0vs. |Sender:=20;
	bh=GnIhsraiXLqd3wf45pWE52+YAoXs1ywHAS/Nq131JGY=;
	b=FgWtggs+yaLkgRA43rSo/suNjFJhUxXWjYjNkuGfp2zM14npurdOgC8Edc1/juIbx+FpqIol
	94prtgYtevgLzop44Gq+qQMmOAXCuhqqnJyfE/OwZ6hkx2sBogouYeSy;
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=714; t=1165867391;
	x=1166731391; c=relaxed/simple; s=oregon;
	h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; 
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[NSIS]=20QoS=20NSLP=3A=20Stacking=20vs.=20tunneling=2
	0vs. |Sender:=20
	|To:=20=22Ash,=20Gerald=20R=20((Jerry)),=20ALABS=22=20<gash@att.com>;
	bh=GnIhsraiXLqd3wf45pWE52+YAoXs1ywHAS/Nq131JGY=;
	b=T8V2+BioZV75f1HPsBJj0vMRaX9rmkCqt+VjdD9t5VEpVG/lxsiqiE8JslSKfcijzbYKFwSu
	Gy9VFw0GCtXfZbuJrOpQvyrfBa7U9ShV7vfDV2PJ419C6o782+FwfMAB;
Authentication-Results: sj-dkim-2; header.From=oran@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim2002 verified; ); 
	header.From=oran@cisco.com; dkim=pass (
	sig from cisco.com/oregon verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: john.loughney@nokia.com, Roland Bless <bless@tm.uka.de>, nsis@ietf.org
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


On Dec 11, 2006, at 11:41 AM, Ash, Gerald R ((Jerry)), ALABS wrote:

>> I find stacking to be simple,
>> elegant and allows for recursion as an extensibility mechanism.
>
> So should we retain stacking instead of encapsulation?  After all, we
> allowed stacking of 2 QSPECs for more than 2 years now, so I don't  
> think
> there is an urgency to change it now.
>
> It is OK with me to retain stacking instead of using encapsulation.
>
> We need to resolve this issue; it would be good to resolve before the
> next update to our QSPEC draft if possible.
>
As I mentioned my preference is aesthetic and engineering  
sensibilities. It's not a make-or-break design decision.

> Thanks,
> Jerry

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



From nsis-bounces@ietf.org Tue Dec 12 11:04:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuA6M-000347-4S; Tue, 12 Dec 2006 11:03:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuA6J-00033d-FM
	for nsis@ietf.org; Tue, 12 Dec 2006 11:03:27 -0500
Received: from mclmx2.mail.saic.com ([149.8.64.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuA6H-0003H3-6j
	for nsis@ietf.org; Tue, 12 Dec 2006 11:03:27 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx2.mail.saic.com; Tue, 12 Dec 2006 11:03:21 -0500
Received: from 0015-ITS-EXBH01.us.saic.com ([10.43.229.18])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006121211032031518 ; Tue, 12 Dec 2006 11:03:20 -0500
Received: from 0591-ITS-EXMP02.us.saic.com ([10.42.81.248]) by
	0015-ITS-EXBH01.us.saic.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Dec 2006 11:03:19 -0500
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
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Tue, 12 Dec 2006 11:03:18 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426230F12@0591-ITS-EXMP02.us.saic.com>
In-Reply-To: <5D944CA2-DE95-4130-BFFB-03DCFE8429B5@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Thread-Index: AccdZMtKsqR4kCL3TrCLiRLp4eEOdgAoAneQ
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: "David R Oran" <oran@cisco.com>,
	"Ash, Gerald R \(\(Jerry\)\), ALABS" <gash@att.com>
X-OriginalArrivalTime: 12 Dec 2006 16:03:19.0652 (UTC)
	FILETIME=[0AB3FA40:01C71E07]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: john.loughney@nokia.com, Roland Bless <bless@tm.uka.de>, nsis@ietf.org
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

1. Can anyone provide a specific use-case for any standard QOS models
why they need QOS Model stacking?=20

2. Is there any specific case that cannot be solved for any IETF
standard QOS models that Roland and I have already explained using the
e2e-QSPEC?

3. Why do they want to break the e2e-QSPEC model that provides the
standard-based solutions for all standard QOS models and create the door
for "non-interoperability?"

4. If anyone cannot come with a specific use-case as stated above, why
do they make only a philosophical statement like "It's not a
make-or-break design decision?"

More Inline [RRR].

-----Original Message-----
From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of
David R Oran
Sent: Monday, December 11, 2006 3:18 PM
To: Ash, Gerald R ((Jerry)), ALABS
Cc: john.loughney@nokia.com; Roland Bless; nsis@ietf.org
Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.


On Dec 11, 2006, at 11:41 AM, Ash, Gerald R ((Jerry)), ALABS wrote:

>> I find stacking to be simple,
>> elegant and allows for recursion as an extensibility mechanism.
>
> So should we retain stacking instead of encapsulation?  After all, we
> allowed stacking of 2 QSPECs for more than 2 years now, so I don't =20
> think
> there is an urgency to change it now.
>
> It is OK with me to retain stacking instead of using encapsulation.
>
> We need to resolve this issue; it would be good to resolve before the
> next update to our QSPEC draft if possible.
>
As I mentioned my preference is aesthetic and engineering =20
sensibilities. It's not a make-or-break design decision.

[RRR] It is a make-or-break decision for the NSIS QOS protocol. For
example, QOS SLAs like Y.1451 will demand one kinds of stacking; DSTE
QOS SLAs will like to make other kinds of stacking; 3GPP/Y.1451 QOS SLAs
will need another one; all QOS SLAs using OSP will need a numerous
stacking.

[RRR] If QSPEC is extended for all those "non-standard" and
"proprietary" QOS SLA stacking for which no need as it has been
explained numerous times, it will defeat the main purpose of
"interwoking."=20

[RRR] Can you come up with any "use" case that needs stacking?

> Thanks,
> Jerry

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

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



From nsis-bounces@ietf.org Tue Dec 12 12:00:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuAzA-0008DT-De; Tue, 12 Dec 2006 12:00:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuAz5-000842-Rn
	for nsis@ietf.org; Tue, 12 Dec 2006 12:00:04 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuAz2-0005I5-QM
	for nsis@ietf.org; Tue, 12 Dec 2006 12:00:03 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-4.cisco.com with ESMTP; 12 Dec 2006 09:00:00 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id kBCH00MT002759; 
	Tue, 12 Dec 2006 09:00:00 -0800
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kBCH00io018851;
	Tue, 12 Dec 2006 09:00:00 -0800 (PST)
Received: from [10.32.245.152] ([10.32.245.152])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id kBCGiYXB006269;
	Tue, 12 Dec 2006 08:44:35 -0800
In-Reply-To: <62D92A9A02BCC845B202323D49A48426230F12@0591-ITS-EXMP02.us.saic.com>
References: <62D92A9A02BCC845B202323D49A48426230F12@0591-ITS-EXMP02.us.saic.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E13E7D42-5C4C-4DB8-97DB-833DE25F0A40@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Tue, 12 Dec 2006 11:59:54 -0500
To: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
X-Mailer: Apple Mail (2.752.2)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4148; t=1165942800;
	x=1166806800; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[NSIS]=20QoS=20NSLP=3A=20Stacking=20vs.=20tunneling=2
	0vs. |Sender:=20;
	bh=VAD0s19Ou8oyaroVllDrM9DmCK2T9iTeTAw0OTcPXjs=;
	b=ngMfcHR2z+wnJ9RZf34fXvbNfSm5wB5S+RXuH7WguXUWH/GmXhnzAfzj6aF+eiGJSdeKgb4x
	5mr/jsxlIOtTIxTBj2h9GcIpCfzySrbPBmgB0ai1+gMYvZ2t0/4wSX2y;
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4148; t=1165941875;
	x=1166805875; c=relaxed/simple; s=oregon;
	h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; 
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[NSIS]=20QoS=20NSLP=3A=20Stacking=20vs.=20tunneling=2
	0vs. |Sender:=20
	|To:=20=22Roy,=20Radhika=20R.=22=20<RADHIKA.R.ROY@saic.com>;
	bh=VAD0s19Ou8oyaroVllDrM9DmCK2T9iTeTAw0OTcPXjs=;
	b=IcA83bKHHGsltp3unLEfB4uRBuPIkrDwe/W3nCNXb1denoDkTThYQhl4vk5CWqfwkwa1v/nM
	1pds1oiaR3dXU4SwvMtXjlAMciYj8wd28JE/UZqcoN4HExG1vy3C19rl;
Authentication-Results: sj-dkim-3; header.From=oran@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim3002 verified; ); 
	header.From=oran@cisco.com; dkim=pass (
	sig from cisco.com/oregon verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: john.loughney@nokia.com, "Ash, Gerald R \(\(Jerry\)\),
	ALABS" <gash@att.com>, Roland Bless <bless@tm.uka.de>, nsis@ietf.org
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


On Dec 12, 2006, at 11:03 AM, Roy, Radhika R. wrote:

> 1. Can anyone provide a specific use-case for any standard QOS models
> why they need QOS Model stacking?
>
Reservation segmentation ala Packetcable. In this case it might even  
be recursion of a "standard" QSPEC.
I'm not sure what you mean by a "Standard QOS Model" so I can't be  
more specific.

Another use case is a domain that has some clever localized way to  
either compress packet headers, do on-the-fly blocking of packets  
onto lower-layer frames, or have fine-grained control of lower-level  
encryption. Each of these needs some specialized local parameters to  
be passed over and into the domain since those parameters affect  
bandwidth calculations due to the potential for packet expansion or  
contraction in the data plane. Since domains can be recursively  
composed or decomposed, recursion in the expression of QSPECS is  
handy. The most straightforward representation of a recursive data  
structure is a stack.

> 2. Is there any specific case that cannot be solved for any IETF
> standard QOS models that Roland and I have already explained using the
> e2e-QSPEC?
>
No. As I've said multiple times we are talking about aesthetics and  
engineering sensibilities here. You can always implement a stack with  
a linked list or a heap, or punt the problem as Roland suggests by  
simply letting each local QSPEC roll their own in terms of how the  
encapsulate an "outer" QSPEC.

> 3. Why do they want to break the e2e-QSPEC model that provides the
> standard-based solutions for all standard QOS models and create the  
> door
> for "non-interoperability?"
>
I don't understand this sentence at all. I'm not interested in  
engaging in another fruitless round of philosophical tit-for-tat  
about what's a standard QOSM and what's not either, so please don't  
bother responding on this point.

> 4. If anyone cannot come with a specific use-case as stated above, why
> do they make only a philosophical statement like "It's not a
> make-or-break design decision?"
>
That is not philosophical, it's engineering tradeoff.

> More Inline [RRR].
>
> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On  
> Behalf Of
> David R Oran
> Sent: Monday, December 11, 2006 3:18 PM
> To: Ash, Gerald R ((Jerry)), ALABS
> Cc: john.loughney@nokia.com; Roland Bless; nsis@ietf.org
> Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
>
>
> On Dec 11, 2006, at 11:41 AM, Ash, Gerald R ((Jerry)), ALABS wrote:
>
>>> I find stacking to be simple,
>>> elegant and allows for recursion as an extensibility mechanism.
>>
>> So should we retain stacking instead of encapsulation?  After all, we
>> allowed stacking of 2 QSPECs for more than 2 years now, so I don't
>> think
>> there is an urgency to change it now.
>>
>> It is OK with me to retain stacking instead of using encapsulation.
>>
>> We need to resolve this issue; it would be good to resolve before the
>> next update to our QSPEC draft if possible.
>>
> As I mentioned my preference is aesthetic and engineering
> sensibilities. It's not a make-or-break design decision.
>
> [RRR] It is a make-or-break decision for the NSIS QOS protocol. For
> example, QOS SLAs like Y.1451 will demand one kinds of stacking; DSTE
> QOS SLAs will like to make other kinds of stacking; 3GPP/Y.1451 QOS  
> SLAs
> will need another one; all QOS SLAs using OSP will need a numerous
> stacking.
>
Not at all. This is a simple encoding discussion.

> [RRR] If QSPEC is extended for all those "non-standard" and
> "proprietary" QOS SLA stacking for which no need as it has been
> explained numerous times, it will defeat the main purpose of
> "interwoking."
>
Who ever said that what was being stacked was standard, nonstandard,  
global, local, or whatever?

> [RRR] Can you come up with any "use" case that needs stacking?
>
See above.

>> Thanks,
>> Jerry
>
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

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



From nsis-bounces@ietf.org Tue Dec 12 12:45:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuBgH-0004bs-BW; Tue, 12 Dec 2006 12:44:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuBgG-0004bm-SM
	for nsis@ietf.org; Tue, 12 Dec 2006 12:44:40 -0500
Received: from mclmx2.mail.saic.com ([149.8.64.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuBgF-0006Dc-FH
	for nsis@ietf.org; Tue, 12 Dec 2006 12:44:40 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx2.mail.saic.com; Tue, 12 Dec 2006 12:44:30 -0500
Received: from 0015-ITS-EXBH01.us.saic.com ([10.43.229.18])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006121212442917255 ; Tue, 12 Dec 2006 12:44:29 -0500
Received: from 0591-ITS-EXMP02.us.saic.com ([10.42.81.248]) by
	0015-ITS-EXBH01.us.saic.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Dec 2006 12:44:29 -0500
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
Subject: RE: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Date: Tue, 12 Dec 2006 12:44:28 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426230F15@0591-ITS-EXMP02.us.saic.com>
In-Reply-To: <E13E7D42-5C4C-4DB8-97DB-833DE25F0A40@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
Thread-Index: AcceDwq/Lb5fzJEoSJW4fx7d7lYYYwAAEyZQ
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: "David R Oran" <oran@cisco.com>
X-OriginalArrivalTime: 12 Dec 2006 17:44:29.0627 (UTC)
	FILETIME=[2CB0A8B0:01C71E15]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Cc: john.loughney@nokia.com, "Ash, Gerald R \(\(Jerry\)\),
	ALABS" <gash@att.com>, Roland Bless <bless@tm.uka.de>, nsis@ietf.org
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

Let us start from the beginning. I appreciate that you have become more
specific, and let us clarify each item for the benefit of the entire
NSIS WG.

The IETF "standard" QOS models are as follows: RSVP, DiffServ, and
IntServ.

QOS SLAs: Y.1451, DSTE, and 3GPP/Y1451 are NOT QOS models; they are QOS
SLAs with specific values of QOS parameters. Similar, all QOS SLAs that
implement DiffServ QOS models with specific values for implementation
any "standard" DiffServ code points will also have the same
value-specific parameters like those of Y.1451/DSTE/3GPP. These are NOT
standards as there can be almost INFINITE numbers of value-specific QOS
parameters for many services. ISPs are there to implement those.

QOS SLAs are "Non-Standards/Proprietary" and are outside scope of the
IETF QSPEC.

Now, let go us inline [RRR] to have specific answers for all of you
explanations.

Best regards,
Radhika

-----Original Message-----
From: David R Oran [mailto:oran@cisco.com]=20
Sent: Tuesday, December 12, 2006 12:00 PM
To: Roy, Radhika R.
Cc: Ash, Gerald R ((Jerry)), ALABS; john.loughney@nokia.com; Roland
Bless; nsis@ietf.org
Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.


On Dec 12, 2006, at 11:03 AM, Roy, Radhika R. wrote:

> 1. Can anyone provide a specific use-case for any standard QOS models
> why they need QOS Model stacking?
>
Reservation segmentation ala Packetcable. In this case it might even =20
be recursion of a "standard" QSPEC.
I'm not sure what you mean by a "Standard QOS Model" so I can't be =20
more specific.

[RRR] Please specific which standard of QOS model (RSVP, DiffServ,
IntServ) Packet Cable uses? If packet cable does not use any QOS
standards, let us not bring this "proprietary" QOS models into our
discussions. Let them go to any forum like IMTC or even packet cable
forum can do so once IETF's e2e-QSPEC spec is standardized.

Another use case is a domain that has some clever localized way to =20
either compress packet headers, do on-the-fly blocking of packets =20
onto lower-layer frames, or have fine-grained control of lower-level =20
encryption. Each of these needs some specialized local parameters to =20
be passed over and into the domain since those parameters affect =20
bandwidth calculations due to the potential for packet expansion or =20
contraction in the data plane. Since domains can be recursively =20
composed or decomposed, recursion in the expression of QSPECS is =20
handy. The most straightforward representation of a recursive data =20
structure is a stack.

[RRR] Like Ronald, please provide an example with different QOS domains
that use the standard QOS models. We can then discuss this.

[RRR] Our job is to see how e2e-QSPEC is implemented using the "simple"
standard QSPEC template that "interwork" leaving out so-called
"intelligent" domain-specific complexities that create
"non-interoperability."

[RRR] We do not need to solve all those "intelligent QOS schemes" that
create more questions than solving any "meaningful" QOS problems with
one shot as IETF is not going out-of-business soon. It can be two-step
process as stated above.

[RRR] If history is guide for QOS standards, only DIffServ QOS model is
the most successful for scalability and simplicity. All other models are
going to be either obsolete or non-scalable, and are of very limited
use.

[RRR] We do not want to create NSIS QOS QSPEC spec is another "white
elephant" from technical point of view. What is the problem, if we use
all those intelligent QOS schemes after standardization of the e2e-QSPEC
template to see how the things work in implementing the NSIS QOS
protocol first keeping only the e2e-QSPEC "simple?"

> 2. Is there any specific case that cannot be solved for any IETF
> standard QOS models that Roland and I have already explained using the
> e2e-QSPEC?
>
No. As I've said multiple times we are talking about aesthetics and =20
engineering sensibilities here. You can always implement a stack with =20
a linked list or a heap, or punt the problem as Roland suggests by =20
simply letting each local QSPEC roll their own in terms of how the =20
encapsulate an "outer" QSPEC.

[RRR] It is true because to keep it "simple." We not want complexities
and creation of non-interoperability in the name of so-called
intelligent inter-domain QOS support. Moreover, there is no need as no
specific example has been provided using any standard QOS models
(DiffServ, RSVP, IntServ).

> 3. Why do they want to break the e2e-QSPEC model that provides the
> standard-based solutions for all standard QOS models and create the =20
> door
> for "non-interoperability?"
>
I don't understand this sentence at all. I'm not interested in =20
engaging in another fruitless round of philosophical tit-for-tat =20
about what's a standard QOSM and what's not either, so please don't =20
bother responding on this point.

[RRR] For example, RSVP, DiffServ, and IntServ QOS models interwork
among themselves. No implementation-specific value-based QOS SLAs
(Y.1451, DSTE, 3GPP/Y.1451, DiffServ-based QOS SLAs, OSP-based QOS SLAs)
will "interwork" among themselves. They are for "non-interoperability."
Is this clear?

[RRR] So, any extensions of QSPEC template for implementation-specific
value-based QOS SLAs (Y.1451, DSTE, 3GPP/Y.1451, DiffServ-based QOS
SLAs, OSP-based QOS SLAs) are out-of-scope in the IETF. Is this clear?

[RRR] If you have specific-examples, please provide to all of us instead
of speaking in general terms. Otherwise, you will be mixing between
"apples" and "oranges." Is this clear?

> 4. If anyone cannot come with a specific use-case as stated above, why
> do they make only a philosophical statement like "It's not a
> make-or-break design decision?"
>
That is not philosophical, it's engineering tradeoff.

[RRR] It will be philosophical, if you want to generalize mixing between
"apples" and "oranges" without providing any specific examples of any
QOS models as described above.

> More Inline [RRR].
>
> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On =20
> Behalf Of
> David R Oran
> Sent: Monday, December 11, 2006 3:18 PM
> To: Ash, Gerald R ((Jerry)), ALABS
> Cc: john.loughney@nokia.com; Roland Bless; nsis@ietf.org
> Subject: Re: [NSIS] QoS NSLP: Stacking vs. tunneling vs.
>
>
> On Dec 11, 2006, at 11:41 AM, Ash, Gerald R ((Jerry)), ALABS wrote:
>
>>> I find stacking to be simple,
>>> elegant and allows for recursion as an extensibility mechanism.
>>
>> So should we retain stacking instead of encapsulation?  After all, we
>> allowed stacking of 2 QSPECs for more than 2 years now, so I don't
>> think
>> there is an urgency to change it now.
>>
>> It is OK with me to retain stacking instead of using encapsulation.
>>
>> We need to resolve this issue; it would be good to resolve before the
>> next update to our QSPEC draft if possible.
>>
> As I mentioned my preference is aesthetic and engineering
> sensibilities. It's not a make-or-break design decision.
>
> [RRR] It is a make-or-break decision for the NSIS QOS protocol. For
> example, QOS SLAs like Y.1451 will demand one kinds of stacking; DSTE
> QOS SLAs will like to make other kinds of stacking; 3GPP/Y.1451 QOS =20
> SLAs
> will need another one; all QOS SLAs using OSP will need a numerous
> stacking.
>
Not at all. This is a simple encoding discussion.

> [RRR] If QSPEC is extended for all those "non-standard" and
> "proprietary" QOS SLA stacking for which no need as it has been
> explained numerous times, it will defeat the main purpose of
> "interwoking."
>
Who ever said that what was being stacked was standard, nonstandard, =20
global, local, or whatever?

> [RRR] Can you come up with any "use" case that needs stacking?
>
See above.

>> Thanks,
>> Jerry
>
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

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



From nsis-bounces@ietf.org Wed Dec 13 01:03:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuNCZ-0001oo-9R; Wed, 13 Dec 2006 01:02:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuNCY-0001od-Bp
	for nsis@ietf.org; Wed, 13 Dec 2006 01:02:46 -0500
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuNCT-0005Cc-NG
	for nsis@ietf.org; Wed, 13 Dec 2006 01:02:46 -0500
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/jazz) with ESMTP id
	kBD62Uoj028155; Wed, 13 Dec 2006 15:02:30 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx3) with ESMTP id
	kBD62WJ12488; Wed, 13 Dec 2006 15:02:32 +0900 (JST)
Received: from epochmail.jp.panasonic.com (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/astros) with ESMTP id
	kBD62WU01487; Wed, 13 Dec 2006 15:02:32 +0900 (JST)
Received: by epochmail.jp.panasonic.com (8.12.11.20060308/3.7W/soml25) id
	kBD62WsS005892; Wed, 13 Dec 2006 15:02:32 +0900 (JST)
Received: from [10.68.136.72]
	by soml25.jp.panasonic.com (8.12.11.20060308/3.7W) with ESMTP id
	kBD62VYE005854; Wed, 13 Dec 2006 15:02:31 +0900 (JST)
Date: Wed, 13 Dec 2006 15:05:56 +0900
From: Takako Sanda <sanda.takako@jp.panasonic.com>
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>, nsis@ietf.org
Subject: Clarification: tearing down from intermediate node (was: Re: [NSIS]
	QoS NSLP v. "13-pre1")
In-Reply-To: <Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
Message-Id: <20061213150313.5173.SANDA.TAKAKO@jp.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.24.02 [ja]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: 
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

Hi Jukka and all,

I would like to clarify about tearing down operation.

In section 3.2.11 (Rerouting), 5th paragraph, it is said,
   "After the reservation on the new path is set up, the branching node
   may want to tear down the reservation on the old path (sooner than
   would result from normal soft-state time-out)."

This means that the CRN will initiate the TEAR on the old path.

At Munich Interim, It was discussed that tearing down from intermediate
node needs to be avoided because of session ownership issue. But I
cannot find any conclusion of this discussion.
http://www.ietf-nsis.org/nsis/Munich_Interim_Meeting/MeetingMinutes.html

Do we have any decision for "tearing down from intermediate node"?

cheers,
Takako



On Wed, 06 Dec 2006 12:09:25 +0200 (EET)
Jukka MJ Manner <jmanner@cs.Helsinki.FI> wrote:

> 
> Dear all,
> 
> I sent the following request for feedback two weeks ago. No comments have 
> been raised. I will wait until this Friday, then submit the draft.
> 
> Jukka
> 
> On Tue, 21 Nov 2006, Jukka MJ Manner wrote:
> 
> > 
> > Hi all,
> > 
> > I have done all the edits I had in my list to the QoS NSLP spec, the main 
> > points are in recent thread with Roland. From the url below you can find 
> > the current draft v. "13-pre1" and a diff to v. 12.
> > 
> > http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
> > 
> > A direct link to the diff:
> > 
> > http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos-nslp-12-from-3-pre1.diff.html
> > 
> > 
> > I would appreciate comments on the changes I did (what is wrong, what I 
> > missed, etc.).
> > 
> > 
> > I still have one problem with the spec, namely the way the NSLP suggests 
> > to handle mobility and path changes. I think we need to review that 
> > statement, because it seems like a "hack" (playing with the RSN value), 
> > and not really useful. And the interactions with GIST look partly wrong. 
> > The folks working on the mobility draft (me included) could comment. The 
> > section I'm talking about is 3.2.10, especially 3.2.10.2, in the v.12 
> > draft.
> > 
> > BR,
> > Jukka
> > 
> > _______________________________________________
> > nsis mailing list
> > nsis@ietf.org
> > https://www1.ietf.org/mailman/listinfo/nsis
> > 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis


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



From nsis-bounces@ietf.org Wed Dec 13 04:18:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuQFM-0004HT-Tu; Wed, 13 Dec 2006 04:17:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuQFL-0004HE-Ps
	for nsis@ietf.org; Wed, 13 Dec 2006 04:17:51 -0500
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuQFG-0004UM-7O
	for nsis@ietf.org; Wed, 13 Dec 2006 04:17:51 -0500
Received: from sbz-31.cs.helsinki.fi (sbz-31.cs.helsinki.fi [128.214.9.99])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Wed, 13 Dec 2006 11:17:40 +0200
	id 000AFF1D.457FC534.00000EA1
Date: Wed, 13 Dec 2006 11:17:39 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Takako Sanda <sanda.takako@jp.panasonic.com>
Subject: Re: Clarification: tearing down from intermediate node (was: Re:
	[NSIS] QoS NSLP v. "13-pre1")
In-Reply-To: <20061213150313.5173.SANDA.TAKAKO@jp.panasonic.com>
Message-ID: <Pine.LNX.4.64.0612131108500.23802@sbz-31.cs.Helsinki.FI>
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
	<20061213150313.5173.SANDA.TAKAKO@jp.panasonic.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: nsis@ietf.org
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


Hi all,

If you look at how the NSIS protocols work, there is no way a node can
make sure a tear-down was intiated by the QNI. A QNE receives a
teardown from its upstream peer, but it can't tell whether that peer
initiated the tear down in the first place, or the QNI.

If I would do a "mobility enhanced QoS NSLP", I would tear down at the 
cross-over router the unnecessary reservation. Of course the spec can say 
"don't do it", but a QNE can not really confirm it isn't being done. And 
the QNI or the QNR can't see that either.

The QoS NSLP spec could say "only the QNI SHOULD (or MAY) be able to 
initiate a tear down", and thus leave the option open for a QNE to also do 
it.

Or we could make a new INFO_SPEC code for "reservation not need" which is 
a hint sent by the cross-over router to inform downstream QNEs on the old 
path that the MN has moved away. It is then up to each QNE to decide 
whether to remove the resources and state, or not.

Jukka

On Wed, 13 Dec 2006, Takako Sanda wrote:

> Hi Jukka and all,
> 
> I would like to clarify about tearing down operation.
> 
> In section 3.2.11 (Rerouting), 5th paragraph, it is said,
>    "After the reservation on the new path is set up, the branching node
>    may want to tear down the reservation on the old path (sooner than
>    would result from normal soft-state time-out)."
> 
> This means that the CRN will initiate the TEAR on the old path.
> 
> At Munich Interim, It was discussed that tearing down from intermediate
> node needs to be avoided because of session ownership issue. But I
> cannot find any conclusion of this discussion.
> http://www.ietf-nsis.org/nsis/Munich_Interim_Meeting/MeetingMinutes.html
> 
> Do we have any decision for "tearing down from intermediate node"?
> 
> cheers,
> Takako
> 
> 
> 
> On Wed, 06 Dec 2006 12:09:25 +0200 (EET)
> Jukka MJ Manner <jmanner@cs.Helsinki.FI> wrote:
> 
> > 
> > Dear all,
> > 
> > I sent the following request for feedback two weeks ago. No comments have 
> > been raised. I will wait until this Friday, then submit the draft.
> > 
> > Jukka
> > 
> > On Tue, 21 Nov 2006, Jukka MJ Manner wrote:
> > 
> > > 
> > > Hi all,
> > > 
> > > I have done all the edits I had in my list to the QoS NSLP spec, the main 
> > > points are in recent thread with Roland. From the url below you can find 
> > > the current draft v. "13-pre1" and a diff to v. 12.
> > > 
> > > http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
> > > 
> > > A direct link to the diff:
> > > 
> > > http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos-nslp-12-from-3-pre1.diff.html
> > > 
> > > 
> > > I would appreciate comments on the changes I did (what is wrong, what I 
> > > missed, etc.).
> > > 
> > > 
> > > I still have one problem with the spec, namely the way the NSLP suggests 
> > > to handle mobility and path changes. I think we need to review that 
> > > statement, because it seems like a "hack" (playing with the RSN value), 
> > > and not really useful. And the interactions with GIST look partly wrong. 
> > > The folks working on the mobility draft (me included) could comment. The 
> > > section I'm talking about is 3.2.10, especially 3.2.10.2, in the v.12 
> > > draft.
> > > 
> > > BR,
> > > Jukka
> > > 
> > > _______________________________________________
> > > nsis mailing list
> > > nsis@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/nsis
> > > 
> > 
> > _______________________________________________
> > nsis mailing list
> > nsis@ietf.org
> > https://www1.ietf.org/mailman/listinfo/nsis
> 
> 

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



From nsis-bounces@ietf.org Wed Dec 13 15:50:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gub3K-0000JC-FA; Wed, 13 Dec 2006 15:50:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gub3H-0000HW-3s; Wed, 13 Dec 2006 15:50:07 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gub3G-0002j8-R8; Wed, 13 Dec 2006 15:50:07 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 9E89D26E3D;
	Wed, 13 Dec 2006 20:50:06 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Gub3C-00063j-3r; Wed, 13 Dec 2006 15:50:04 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Gub3C-00063j-3r@stiedprstage1.ietf.org>
Date: Wed, 13 Dec 2006 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: nsis@ietf.org
Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt 
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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Next Steps in Signaling Working Group of the IETF.

	Title		: QoS NSLP QSPEC Template
	Author(s)	: J. Ash, et al.
	Filename	: draft-ietf-nsis-qspec-13.txt
	Pages		: 52
	Date		: 2006-12-13
	
The QoS NSLP protocol is used to signal QoS reservations and is
   independent of a specific QoS model (QOSM) such as IntServ or
   DiffServ.  Rather, all information specific to a QOSM is encapsulated
   in a separate object, the QSPEC.  This document defines a template
   for the QSPEC including a number of QSPEC parameters.  The QSPEC
   parameters provide a common language to be re-used in several QOSMs
   and thereby aim to ensure the extensibility and interoperability of
   QoS NSLP.  The node initiating the NSIS signaling adds an initiator
   QSPEC, which indicates the QSPEC parameters that must be interpreted
   by the downstream nodes less the reservation fails, thereby ensuring
   the intention of the NSIS initiator is preserved along the signaling
   path.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-nsis-qspec-13.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nsis-qspec-13.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2006-12-13140908.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-nsis-qspec-13.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-nsis-qspec-13.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-12-13140908.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--




From nsis-bounces@ietf.org Wed Dec 13 19:01:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gue1s-0006Kx-EG; Wed, 13 Dec 2006 19:00:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gue1r-0006KI-F2
	for nsis@ietf.org; Wed, 13 Dec 2006 19:00:51 -0500
Received: from mail120.messagelabs.com ([216.82.250.83])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gue1X-0001oA-On
	for nsis@ietf.org; Wed, 13 Dec 2006 19:00:49 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-2.tower-120.messagelabs.com!1166054429!19876102!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 6469 invoked from network); 14 Dec 2006 00:00:29 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-2.tower-120.messagelabs.com with SMTP;
	14 Dec 2006 00:00:29 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kBE00TqD018440
	for <nsis@ietf.org>; Wed, 13 Dec 2006 19:00:29 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kBE00N2D018376
	for <nsis@ietf.org>; Wed, 13 Dec 2006 19:00:23 -0500 (EST)
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
Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt 
Date: Wed, 13 Dec 2006 18:00:22 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC8043@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <E1Gub3C-00063j-3r@stiedprstage1.ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGg
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: <nsis@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
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

Hi All,

The updated 'QoS NSLP QSPEC Template' I-D is available at
http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.

The main changes are as follows:

1. notion of QOSMs played down
  o language e.g. 'QNSLP/QSPEC can signal for different QOSMs across
    multiple domains' replaced by notion that 'QNSLP/QSPEC allows
    QNEs on the path to implement different data plane QoS mechanisms
    that meet QSPEC constraints'
  o a QOSM describes common capabilities among QNEs to act
    consistently when requested to admit traffic & in treating
    admitted traffic
  o a QOSM ID need not be defined or signaled
  o a QNE need not support any particular QOSM although a  QNI
    normally includes a QSPEC corresponding to a particular QOSM
2. a 'QOSM specification'
  o still provides a rigorous specification of a QOSM & what it does
  o documents how a QNE interprets & treats various elements in QSPEC
  o can define additional QSPEC parameters
3. updated QOSM definition:
  a method to achieve QoS for a traffic flow, e.g., IntServ
  Controlled Load; specifies what sub-set of QSPEC QoS constraints &
  traffic handling directives a QNE implementing that QOSM is capable
  of supporting & how resources will be managed by the RMF
4. QSPEC1/QSPEC2 semantics replaced with following semantics:
  o source traffic description (mandatory to include by QNI &
    mandatory to interpret by downstream QNEs)
    > specified by traffic model (TMOD-1) parameter consisting of
      rate (r), bucket size (b), peak rate (p), minimum policed unit
     (m) (mathematically complete way to describe traffic source)
    > bandwidth only set r=3Dp; b/m to large values (separate
      bandwidth parameter not needed)
    > TMOD-2 (optional to include)
  o constraints (optional to include):
    > Path Latency
    > Path Jitter
    > Path PLR
    > Path PER
    > Slack Term
    > Priority (Preemption, Defending, Admission, RPH Priority)
  o handling directives (optional to include):
    > Excess Treatment
  o traffic classifiers (optional to include):
    > PHB Class (PHB class set by downstream QNE to tell QNI how to
      mark traffic to ensure treatment committed by admission
      control)
    > DSTE Class Type
    > Y.1541 QoS class
  o eliminated:
    > Bandwidth
    > Ctot, Dtot, Csum, Dsum
5. concept of remapping QSPEC parameters eliminated
6. redefine 'interpret' a QSPEC parameter to mean 'must conform to
   RFCs defining parameter & procedures (formerly called 'strictly
   interpret')
7. concept of local QSPECs retained
  o allows simpler control plane in a local domain
  o edge nodes
    > must interpret initiator QSPEC parameters
    > can either initiate parallel session with local QSPEC or
      define a local QSPEC with encapsulated initiator QSPEC
  o local QSPEC interpreted by local domain QNEs
  o local QSPEC must be consistent with initiator QSPEC
    > e.g., RMD can initiate a local QSPEC that contains TMOD =3D
      bandwidth (sets r=3Dp, b/m to large)
8. QSPEC flags modified as follows:
  o QNI sets M flag for each QSPEC parameter it populates that must
    be interpreted or reservation fails
  o if M flag set
    > downstream QNE MUST interpret parameter or reservation fails
    > if QNE does not support parameter it sets N flag & rejects
      reservation
    > if QNE supports parameter but cannot meet parameter, it sets E
      flag & rejects reservation
  o if M flag not set
    > downstream QNE SHOULD interpret parameter
    > if QNE does not support parameter it sets the N flag &
      optionally accepts or rejects reservation
    > if QNE supports parameter but cannot meet parameter, it sets E
      flag & optionally accepts or rejects reservation
  o R (remapped parameter) flag & Q (non QOSM) flag eliminated
9. QSPEC type defined and registry established in IANA section.

Please review the updated draft.

Thanks,
Jerry

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
Sent: Wednesday, December 13, 2006 3:50 PM
To: i-d-announce@ietf.org
Cc: nsis@ietf.org
Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt=20

A New Internet-Draft is available from the on-line Internet-Drafts=20
directories.
This draft is a work item of the Next Steps in Signaling Working Group
of the IETF.

	Title		: QoS NSLP QSPEC Template
	Author(s)	: J. Ash, et al.
	Filename	: draft-ietf-nsis-qspec-13.txt
	Pages		: 52
	Date		: 2006-12-13
=09
The QoS NSLP protocol is used to signal QoS reservations and is
   independent of a specific QoS model (QOSM) such as IntServ or
   DiffServ.  Rather, all information specific to a QOSM is encapsulated
   in a separate object, the QSPEC.  This document defines a template
   for the QSPEC including a number of QSPEC parameters.  The QSPEC
   parameters provide a common language to be re-used in several QOSMs
   and thereby aim to ensure the extensibility and interoperability of
   QoS NSLP.  The node initiating the NSIS signaling adds an initiator
   QSPEC, which indicates the QSPEC parameters that must be interpreted
   by the downstream nodes less the reservation fails, thereby ensuring
   the intention of the NSIS initiator is preserved along the signaling
   path.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt

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



From nsis-bounces@ietf.org Wed Dec 13 20:14:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GufAf-0001Nt-LD; Wed, 13 Dec 2006 20:14:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GufAe-0001No-Po
	for nsis@ietf.org; Wed, 13 Dec 2006 20:14:00 -0500
Received: from mclmx.mail.saic.com ([149.8.64.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GufAc-00041F-Bq
	for nsis@ietf.org; Wed, 13 Dec 2006 20:14:00 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx.mail.saic.com for nsis@ietf.org;
	Wed, 13 Dec 2006 20:13:46 -0500
Received: from 0015-ITS-EXBH01.us.saic.com ([10.43.229.18])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006121320134623053
	for <nsis@ietf.org>; Wed, 13 Dec 2006 20:13:46 -0500
Received: from 0591-ITS-EXMP02.us.saic.com ([10.42.81.248]) by
	0015-ITS-EXBH01.us.saic.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 20:13:46 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt 
Date: Wed, 13 Dec 2006 20:13:44 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426E1CF61@0591-ITS-EXMP02.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+JAaqcNj+MHkRzm/awOqBUve1QAIisW7
References: <E1Gub3C-00063j-3r@stiedprstage1.ietf.org>
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: <nsis@ietf.org>
X-OriginalArrivalTime: 14 Dec 2006 01:13:46.0068 (UTC)
	FILETIME=[1A64E140:01C71F1D]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
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>
Content-Type: multipart/mixed; boundary="===============0965855120=="
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0965855120==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C71F1D.19C047C8"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C71F1D.19C047C8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Folks:
=20
This draft remains almost the so far the basic issues are concerned. The =
so-called Y.1451 QOS-classes are there as if these are the formal =
standardized QOS models (!!!) and their classes are the ones the whole =
world is begging to have.=20
=20
What a technical invention that the whole world is looking for as if =
IETF folks have missed this "original" invention that the world ever =
know - Y.1451 QOS models and their QOS classes! How about QOS SLAs based =
on DiffServ QOS models that all ISPs are using? Are those not to be =
included here too?
=20
What are the properties that differentiate between QOS models and QOS =
SLAs?
=20
Are "apples" and "oranges" still need to be mixed as if they are the =
same?
=20
John L. asked question last time to remove so-called QOS SLAs like =
Y.1451 etc. These (Y.1451 QOS SLAs) are still here as if some how =
something will happen and "apples" and "oranges" will be mixed assuming =
they are the same.
=20
One question to Chairs of the NSIS WG: Did you add another NEW =
editor/author to the draft? Even then all "apples" and "oranges" are =
being mixed despite serious technical problems as we all discussed.
=20
Why has this been happening for about long two years?
=20
Best regards,
Radhika

________________________________

From: nsis-bounces@ietf.org on behalf of Internet-Drafts@ietf.org
Sent: Wed 12/13/2006 3:50 PM
To: i-d-announce@ietf.org
Cc: nsis@ietf.org
Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt=20



A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Next Steps in Signaling Working Group =
of the IETF.

        Title           : QoS NSLP QSPEC Template
        Author(s)       : J. Ash, et al.
        Filename        : draft-ietf-nsis-qspec-13.txt
        Pages           : 52
        Date            : 2006-12-13
      =20
The QoS NSLP protocol is used to signal QoS reservations and is
   independent of a specific QoS model (QOSM) such as IntServ or
   DiffServ.  Rather, all information specific to a QOSM is encapsulated
   in a separate object, the QSPEC.  This document defines a template
   for the QSPEC including a number of QSPEC parameters.  The QSPEC
   parameters provide a common language to be re-used in several QOSMs
   and thereby aim to ensure the extensibility and interoperability of
   QoS NSLP.  The node initiating the NSIS signaling adds an initiator
   QSPEC, which indicates the QSPEC parameters that must be interpreted
   by the downstream nodes less the reservation fails, thereby ensuring
   the intention of the NSIS initiator is preserved along the signaling
   path.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt




------_=_NextPart_001_01C71F1D.19C047C8
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>[NSIS] I-D =
ACTION:draft-ietf-nsis-qspec-13.txt</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.2995" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText29719 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>Folks:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>This draft remains almost the =
so far&nbsp;the basic issues are concerned. The so-called Y.1451 =
QOS-classes are there as if these are the formal standardized QOS models =
(!!!) and their classes are the ones the whole world is begging to have. =
</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>What a technical invention =
that the whole world is looking for as if IETF folks have missed this =
"original" invention that the world ever know - Y.1451 QOS models and =
their QOS classes! How about QOS SLAs based on DiffServ QOS models that =
all ISPs are using? Are those not to be included here too?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>What are the =
properties&nbsp;that differentiate between&nbsp;QOS models&nbsp;and QOS =
SLAs?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Are "apples" and "oranges" =
still need to be mixed as if they are the same?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>John L. asked question last =
time to remove so-called QOS SLAs like Y.1451 etc. These (Y.1451 QOS =
SLAs) are still here as if some how something will happen and "apples" =
and "oranges" will be mixed assuming they are the same.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>One question to Chairs of the =
NSIS WG: Did you add another NEW editor/author to the draft? Even then =
all "apples" and "oranges" are being mixed despite serious =
technical&nbsp;problems as we all discussed.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Why&nbsp;has this been =
happening for about long two years?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Best regards,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Radhika</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> nsis-bounces@ietf.org on =
behalf of Internet-Drafts@ietf.org<BR><B>Sent:</B> Wed 12/13/2006 3:50 =
PM<BR><B>To:</B> i-d-announce@ietf.org<BR><B>Cc:</B> =
nsis@ietf.org<BR><B>Subject:</B> [NSIS] I-D =
ACTION:draft-ietf-nsis-qspec-13.txt <BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>A New Internet-Draft is available from the on-line =
Internet-Drafts<BR>directories.<BR>This draft is a work item of the Next =
Steps in Signaling Working Group of the =
IETF.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Title&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : QoS NSLP =
QSPEC Template<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : J. Ash, et =
al.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
draft-ietf-nsis-qspec-13.txt<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; Pages&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
52<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
2006-12-13<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>The QoS NSLP =
protocol is used to signal QoS reservations and is<BR>&nbsp;&nbsp; =
independent of a specific QoS model (QOSM) such as IntServ =
or<BR>&nbsp;&nbsp; DiffServ.&nbsp; Rather, all information specific to a =
QOSM is encapsulated<BR>&nbsp;&nbsp; in a separate object, the =
QSPEC.&nbsp; This document defines a template<BR>&nbsp;&nbsp; for the =
QSPEC including a number of QSPEC parameters.&nbsp; The =
QSPEC<BR>&nbsp;&nbsp; parameters provide a common language to be re-used =
in several QOSMs<BR>&nbsp;&nbsp; and thereby aim to ensure the =
extensibility and interoperability of<BR>&nbsp;&nbsp; QoS NSLP.&nbsp; =
The node initiating the NSIS signaling adds an initiator<BR>&nbsp;&nbsp; =
QSPEC, which indicates the QSPEC parameters that must be =
interpreted<BR>&nbsp;&nbsp; by the downstream nodes less the reservation =
fails, thereby ensuring<BR>&nbsp;&nbsp; the intention of the NSIS =
initiator is preserved along the signaling<BR>&nbsp;&nbsp; =
path.<BR><BR>A URL for this Internet-Draft is:<BR><A =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt"=
>http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt</A><BR>=
<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C71F1D.19C047C8--


--===============0965855120==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0965855120==--




From nsis-bounces@ietf.org Wed Dec 13 23:13:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuhxZ-0005K1-HJ; Wed, 13 Dec 2006 23:12:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuhxY-0005Jt-Ac
	for nsis@ietf.org; Wed, 13 Dec 2006 23:12:40 -0500
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuhxT-0004hQ-Li
	for nsis@ietf.org; Wed, 13 Dec 2006 23:12:40 -0500
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/bulls) with ESMTP id
	kBE4CQb2019330; Thu, 14 Dec 2006 13:12:26 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx2) with ESMTP id
	kBE4CT706896; Thu, 14 Dec 2006 13:12:29 +0900 (JST)
Received: from localhost (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/astros) with SMTP id
	kBE4CTU28857; Thu, 14 Dec 2006 13:12:29 +0900 (JST)
Received: from [127.0.0.1] ([10.81.113.78]) by pslexc01.psl.local with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 14 Dec 2006 12:10:25 +0800
Message-ID: <4580CEAC.6000908@sg.panasonic.com>
Date: Thu, 14 Dec 2006 12:10:20 +0800
From: Hong Cheng <hong.cheng@sg.panasonic.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>	<20061213150313.5173.SANDA.TAKAKO@jp.panasonic.com>
	<Pine.LNX.4.64.0612131108500.23802@sbz-31.cs.Helsinki.FI>
In-Reply-To: <Pine.LNX.4.64.0612131108500.23802@sbz-31.cs.Helsinki.FI>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Dec 2006 04:10:25.0424 (UTC)
	FILETIME=[C81A4100:01C71F35]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: nsis@ietf.org, Takako Sanda <sanda.takako@jp.panasonic.com>
Subject: [NSIS] Re: Clarification: tearing down from intermediate node
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

Hi Jukka,

I would agree that the cross-over router should be left capable of 
tearing down the unneeded reservations. Please see some comments inline 
below:

cheers

Cheng Hong


Jukka MJ Manner wrote:
> Hi all,
>
> If you look at how the NSIS protocols work, there is no way a node can
> make sure a tear-down was intiated by the QNI. A QNE receives a
> teardown from its upstream peer, but it can't tell whether that peer
> initiated the tear down in the first place, or the QNI.
>
> If I would do a "mobility enhanced QoS NSLP", I would tear down at the 
> cross-over router the unnecessary reservation. Of course the spec can say 
> "don't do it", but a QNE can not really confirm it isn't being done. And 
> the QNI or the QNR can't see that either.
>
> The QoS NSLP spec could say "only the QNI SHOULD (or MAY) be able to 
> initiate a tear down", and thus leave the option open for a QNE to also do 
> it.
>   

[Cheng] Agree. This should be left open. And I think the quoted text in 
current QoS NSLP draft is reflecting this point.

> Or we could make a new INFO_SPEC code for "reservation not need" which is 
> a hint sent by the cross-over router to inform downstream QNEs on the old 
> path that the MN has moved away. It is then up to each QNE to decide 
> whether to remove the resources and state, or not.
>
>   

[Cheng] This option might lead to some problem though, since it could 
leave the QNEs on the path unsynchronized should they decide to do 
different things in response to the INFO_SPEC.

> Jukka
>
> On Wed, 13 Dec 2006, Takako Sanda wrote:
>
>   
>> Hi Jukka and all,
>>
>> I would like to clarify about tearing down operation.
>>
>> In section 3.2.11 (Rerouting), 5th paragraph, it is said,
>>    "After the reservation on the new path is set up, the branching node
>>    may want to tear down the reservation on the old path (sooner than
>>    would result from normal soft-state time-out)."
>>
>> This means that the CRN will initiate the TEAR on the old path.
>>
>> At Munich Interim, It was discussed that tearing down from intermediate
>> node needs to be avoided because of session ownership issue. But I
>> cannot find any conclusion of this discussion.
>> http://www.ietf-nsis.org/nsis/Munich_Interim_Meeting/MeetingMinutes.html
>>
>> Do we have any decision for "tearing down from intermediate node"?
>>
>> cheers,
>> Takako
>>
>>
>>
>> On Wed, 06 Dec 2006 12:09:25 +0200 (EET)
>> Jukka MJ Manner <jmanner@cs.Helsinki.FI> wrote:
>>
>>     
>>> Dear all,
>>>
>>> I sent the following request for feedback two weeks ago. No comments have 
>>> been raised. I will wait until this Friday, then submit the draft.
>>>
>>> Jukka
>>>
>>> On Tue, 21 Nov 2006, Jukka MJ Manner wrote:
>>>
>>>       
>>>> Hi all,
>>>>
>>>> I have done all the edits I had in my list to the QoS NSLP spec, the main 
>>>> points are in recent thread with Roland. From the url below you can find 
>>>> the current draft v. "13-pre1" and a diff to v. 12.
>>>>
>>>> http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
>>>>
>>>> A direct link to the diff:
>>>>
>>>> http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos-nslp-12-from-3-pre1.diff.html
>>>>
>>>>
>>>> I would appreciate comments on the changes I did (what is wrong, what I 
>>>> missed, etc.).
>>>>
>>>>
>>>> I still have one problem with the spec, namely the way the NSLP suggests 
>>>> to handle mobility and path changes. I think we need to review that 
>>>> statement, because it seems like a "hack" (playing with the RSN value), 
>>>> and not really useful. And the interactions with GIST look partly wrong. 
>>>> The folks working on the mobility draft (me included) could comment. The 
>>>> section I'm talking about is 3.2.10, especially 3.2.10.2, in the v.12 
>>>> draft.
>>>>
>>>> BR,
>>>> Jukka
>>>>
>>>>         




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



From nsis-bounces@ietf.org Fri Dec 15 07:21:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GvC40-0006XR-5Q; Fri, 15 Dec 2006 07:21:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GvC3z-0006XJ-BW
	for nsis@ietf.org; Fri, 15 Dec 2006 07:21:19 -0500
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GvC3w-0002mT-OG
	for nsis@ietf.org; Fri, 15 Dec 2006 07:21:19 -0500
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/jazz) with ESMTP id
	kBFCKsoI010595; Fri, 15 Dec 2006 21:20:54 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx2) with ESMTP id
	kBFCKtg17439; Fri, 15 Dec 2006 21:20:55 +0900 (JST)
Received: from epochmail.jp.panasonic.com (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/mariners) with ESMTP id
	kBFCKro01370; Fri, 15 Dec 2006 21:20:53 +0900 (JST)
Received: by epochmail.jp.panasonic.com (8.12.11.20060308/3.7W/soml27) id
	kBFCKsfh029347; Fri, 15 Dec 2006 21:20:54 +0900 (JST)
Received: from [10.68.136.72]
	by soml27.jp.panasonic.com (8.12.11.20060308/3.7W) with ESMTP id
	kBFCKrft029325; Fri, 15 Dec 2006 21:20:53 +0900 (JST)
Date: Fri, 15 Dec 2006 21:24:20 +0900
From: Takako Sanda <sanda.takako@jp.panasonic.com>
To: nsis@ietf.org
Message-Id: <20061215212000.03D3.SANDA.TAKAKO@jp.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.24.02 [ja]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: Xiaoming Fu <fu@cs.uni-goettingen.de>, Seong-Ho Jeong <shjeong@hufs.ac.kr>,
	Sung-Hyuck Lee <starsu@MIT.EDU>, Jukka MJ Manner <jmanner@cs.Helsinki.FI>,
	Hannes Tschofenig <hannes.tschofenig@siemens.com>
Subject: [NSIS] Change proposal for Mobility Applicability draft
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

Dear all,

After the last IETF meeting, authors of NSIS Mobility Applicability
draft (draft-ietf-nsis-applicability-mobility-signaling-05.txt) have
discussed how the draft should be cleaned up and which topics are still
missing.

The followings are discussion result for proposed changes. Please review
them and give your comments by 5th Jan 2007. If no discussion has been made,
authors will start editing text based on the decision below.


1. Section 4 and 5 ("Basic Operations for Mobility Support" and
"Applicability Statement") should be divided into two parts and
rewritten:-

  o "Main" part, which is focusing on examples and describing how
  mobility is handled by the NSIS protocols. Topics here will be 
  route change handling and NSIS interwork with MIP v4/v6 
  (including tunneling management). This part must not include 
  "should work" or "may work" sort of description.

  o "Further Study" part, which introduces summary of potential
  issues and possible approaches for other topics. These topics are
  out-of-scope for discussing details, such as interwork with other
  mobility protocols, multihoming, peer failure (and frequent
  path change, may be)

2. Description of mobility objects should be removed.

3. Security part needs to be cleaned up. Concrete change plan is still
under discussions.

4. As for new open issue, NAT/FW should be raised
    "If a MN moves, IP addresses and routing change so that the 
    packets enter and leave the network through a new NAT/FW node.
    We need to open the old ports on this new NAT/FW node, and remove
    the ones on the previous NAT/FW."
  How would this work in real like?
  The main difference for the NAT/FW work with respect is two-fold:
   * We only use e2e refreshes. This makes things easier. 
   * Most firewalls drop packets if a pinhole does not exist. 
  We need to capture these two things.

5. Detailed Operations in current texts should be moved to Appendix or
discussed in separate draft.

6. Section 3 (Problem Statement) may need to be cleaned up based on 
changes in main body.

BR,
Takako


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



From nsis-bounces@ietf.org Tue Dec 19 05:58:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwcfA-0006g4-Cu; Tue, 19 Dec 2006 05:57:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwcf8-0006bj-Ph
	for nsis@ietf.org; Tue, 19 Dec 2006 05:57:34 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gwcf7-0002Ah-Az
	for nsis@ietf.org; Tue, 19 Dec 2006 05:57:34 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 449892004BFA;
	Tue, 19 Dec 2006 11:58:08 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QlDkQkyvaaEw; Tue, 19 Dec 2006 11:58:08 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 21D3A2000296;
	Tue, 19 Dec 2006 11:58:08 +0100 (CET)
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
Subject: RE: [NSIS] Change proposal for Mobility Applicability draft
Date: Tue, 19 Dec 2006 11:57:31 +0100
Message-ID: <113091BD57179D4491C19DA7E10CD6968C8554@mx1.office>
In-Reply-To: <20061215212000.03D3.SANDA.TAKAKO@jp.panasonic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Change proposal for Mobility Applicability draft
Thread-Index: AccgQ7zP3vIf2wRzQsGCiGG2yXRWqQDF/m5Q
From: "Martin Stiemerling" <Stiemerling@netlab.nec.de>
To: <nsis@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: Seong-Ho Jeong <shjeong@hufs.ac.kr>,
	Hannes Tschofenig <hannes.tschofenig@siemens.com>,
	Xiaoming Fu <fu@cs.uni-goettingen.de>, Sung-Hyuck Lee <starsu@MIT.EDU>,
	Takako Sanda <sanda.takako@jp.panasonic.com>,
	Jukka MJ Manner <jmanner@cs.Helsinki.FI>
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

Dear all,

Thanks to the authors for pushing this forward on time!

Please review the proposed changes and comment on them whether they are
are to the WG or not.

Do send your comments (good, bad, etc) to the mailing list by January
8th latest (to fit with the holiday schedules :). By January 8th we
should have a clear view if the proposed changes can go in the draft.

Thanks,

  Martin

-----Original Message-----
From: Takako Sanda [mailto:sanda.takako@jp.panasonic.com]=20
Sent: Friday, December 15, 2006 1:24 PM
To: nsis@ietf.org
Cc: Xiaoming Fu; Seong-Ho Jeong; Sung-Hyuck Lee; Jukka MJ Manner; Hannes
Tschofenig
Subject: [NSIS] Change proposal for Mobility Applicability draft

Dear all,

After the last IETF meeting, authors of NSIS Mobility Applicability
draft (draft-ietf-nsis-applicability-mobility-signaling-05.txt) have
discussed how the draft should be cleaned up and which topics are still
missing.

The followings are discussion result for proposed changes. Please review
them and give your comments by 5th Jan 2007. If no discussion has been
made, authors will start editing text based on the decision below.


1. Section 4 and 5 ("Basic Operations for Mobility Support" and
"Applicability Statement") should be divided into two parts and
rewritten:-

  o "Main" part, which is focusing on examples and describing how
  mobility is handled by the NSIS protocols. Topics here will be
  route change handling and NSIS interwork with MIP v4/v6
  (including tunneling management). This part must not include
  "should work" or "may work" sort of description.

  o "Further Study" part, which introduces summary of potential
  issues and possible approaches for other topics. These topics are
  out-of-scope for discussing details, such as interwork with other
  mobility protocols, multihoming, peer failure (and frequent
  path change, may be)

2. Description of mobility objects should be removed.

3. Security part needs to be cleaned up. Concrete change plan is still
under discussions.

4. As for new open issue, NAT/FW should be raised
    "If a MN moves, IP addresses and routing change so that the=20
    packets enter and leave the network through a new NAT/FW node.
    We need to open the old ports on this new NAT/FW node, and remove
    the ones on the previous NAT/FW."
  How would this work in real like?
  The main difference for the NAT/FW work with respect is two-fold:
   * We only use e2e refreshes. This makes things easier.=20
   * Most firewalls drop packets if a pinhole does not exist.=20
  We need to capture these two things.

5. Detailed Operations in current texts should be moved to Appendix or
discussed in separate draft.

6. Section 3 (Problem Statement) may need to be cleaned up based on
changes in main body.

BR,
Takako


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

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



From nsis-bounces@ietf.org Tue Dec 19 06:06:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwcnZ-0004gS-3m; Tue, 19 Dec 2006 06:06:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwcnX-0004gL-T7
	for nsis@ietf.org; Tue, 19 Dec 2006 06:06:15 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwcnT-0003kf-D4
	for nsis@ietf.org; Tue, 19 Dec 2006 06:06:15 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 728642004BFA;
	Tue, 19 Dec 2006 12:06:46 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ey-NYUJULoLs; Tue, 19 Dec 2006 12:06:46 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 512262000296;
	Tue, 19 Dec 2006 12:06:46 +0100 (CET)
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
Subject: RE: [NSIS] Change proposal for Mobility Applicability draft
Date: Tue, 19 Dec 2006 12:06:10 +0100
Message-ID: <113091BD57179D4491C19DA7E10CD6968C8557@mx1.office>
In-Reply-To: <20061215212000.03D3.SANDA.TAKAKO@jp.panasonic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Change proposal for Mobility Applicability draft
Thread-Index: AccgQ7zP3vIf2wRzQsGCiGG2yXRWqQDGRKpQ
From: "Martin Stiemerling" <Stiemerling@netlab.nec.de>
To: "Takako Sanda" <sanda.takako@jp.panasonic.com>, <nsis@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: Xiaoming Fu <fu@cs.uni-goettingen.de>, Sung-Hyuck Lee <starsu@MIT.EDU>,
	Hannes Tschofenig <hannes.tschofenig@siemens.com>,
	Seong-Ho Jeong <shjeong@hufs.ac.kr>,
	Jukka MJ Manner <jmanner@cs.Helsinki.FI>
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

(chair's hat off)

Hi all,

Here are my comments:  =20

> -----Original Message-----
> From: Takako Sanda [mailto:sanda.takako@jp.panasonic.com]=20
> Sent: Friday, December 15, 2006 1:24 PM
> To: nsis@ietf.org
> Cc: Xiaoming Fu; Seong-Ho Jeong; Sung-Hyuck Lee; Jukka MJ=20
> Manner; Hannes Tschofenig
> Subject: [NSIS] Change proposal for Mobility Applicability draft
>=20
> Dear all,
>=20
> After the last IETF meeting, authors of NSIS Mobility=20
> Applicability draft=20
> (draft-ietf-nsis-applicability-mobility-signaling-05.txt)=20
> have discussed how the draft should be cleaned up and which=20
> topics are still missing.
>=20
> The followings are discussion result for proposed changes.=20
> Please review them and give your comments by 5th Jan 2007. If=20
> no discussion has been made, authors will start editing text=20
> based on the decision below.
>=20
>=20
> 1. Section 4 and 5 ("Basic Operations for Mobility Support"=20
> and "Applicability Statement") should be divided into two parts and
> rewritten:-
>=20
>   o "Main" part, which is focusing on examples and describing how
>   mobility is handled by the NSIS protocols. Topics here will be
>   route change handling and NSIS interwork with MIP v4/v6
>   (including tunneling management). This part must not include
>   "should work" or "may work" sort of description.

I see in the same way. Probably it would also be good to talk with
Charles and Henning (i.e., the authors of NSIS Operation Over IP
Tunnels) about the tunnel management.=20

>=20
>   o "Further Study" part, which introduces summary of potential
>   issues and possible approaches for other topics. These topics are
>   out-of-scope for discussing details, such as interwork with other
>   mobility protocols, multihoming, peer failure (and frequent
>   path change, may be)

Agreed and really stay brief, i.e., not exploring it too much.

>=20
> 2. Description of mobility objects should be removed.

Yes, indeed. Since it is anyway not include in GIST and not required.=20

>=20
> 3. Security part needs to be cleaned up. Concrete change plan=20
> is still under discussions.

Do you have any plans here in general?

>=20
> 4. As for new open issue, NAT/FW should be raised
>     "If a MN moves, IP addresses and routing change so that the=20
>     packets enter and leave the network through a new NAT/FW node.
>     We need to open the old ports on this new NAT/FW node, and remove
>     the ones on the previous NAT/FW."
>   How would this work in real like?
>   The main difference for the NAT/FW work with respect is two-fold:
>    * We only use e2e refreshes. This makes things easier.=20
>    * Most firewalls drop packets if a pinhole does not exist.=20
>   We need to capture these two things.

The protocol operations for the NATFW NSLP are quite easy but I see the
need for more carefully considerations wrt mobility. Hannes and I will
take care about it. I have just created a entry in the NATFW issue
tracker:

https://kobe.netlab.nec.de/roundup/nsis-natfw-nslp/issue87

>=20
> 5. Detailed Operations in current texts should be moved to=20
> Appendix or discussed in separate draft.

What do you refer to with "Detailed Operations"?

Thanks!

  Martin

>=20
> 6. Section 3 (Problem Statement) may need to be cleaned up=20
> based on changes in main body.
>=20
> BR,
> Takako
>=20
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
>=20

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



From nsis-bounces@ietf.org Tue Dec 19 17:20:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwnJa-0002az-Vu; Tue, 19 Dec 2006 17:20:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwnJa-0002at-4O
	for nsis@ietf.org; Tue, 19 Dec 2006 17:20:02 -0500
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwnJY-0007j1-Rb
	for nsis@ietf.org; Tue, 19 Dec 2006 17:20:02 -0500
Received: from sbz-31.cs.helsinki.fi (sbz-31.cs.helsinki.fi [128.214.9.99])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Wed, 20 Dec 2006 00:19:55 +0200
	id 000808D9.4588658B.00004A96
Date: Wed, 20 Dec 2006 00:19:55 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: nsis@ietf.org
Message-ID: <Pine.LNX.4.64.0612200007580.15055@sbz-31.cs.Helsinki.FI>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: [NSIS] Simple question to NATFW people
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


We are working on the NATFW, but a simple question just occured to me.

For browsing a simple web site, do I need 1 or 2 requests to the firewall?

Consider the following:

1) MyPC--->WWWserver  - I send a TCP SYN packet to the destination,
2) WWWserver <---MyPC - destination sends back SYN-ACK
3) MyPC--->WWWserver  -  I reply with an ACK.
4) From now on, data can be sent on both directions

I have a NATFW capable firewall protecting my network, working in proxy 
mode.

The spec doesn't mention any bi-directional firewall holes, so basically, 
do I need to request a hole for MyPC->WWWserver and a second for 
WWWserver->MyPC? 

Or can I just ask for 1 hole for this particular connection, for all 
packets belonging to this TCP flow, regardless of the direction?

Jukka


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



From nsis-bounces@ietf.org Wed Dec 20 04:16:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwxYI-0003vS-Vx; Wed, 20 Dec 2006 04:15:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwxYI-0003vH-26
	for nsis@ietf.org; Wed, 20 Dec 2006 04:15:54 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwxYG-0003bR-Mx
	for nsis@ietf.org; Wed, 20 Dec 2006 04:15:54 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id C336F2004BFC;
	Wed, 20 Dec 2006 10:16:25 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Dm03OdB39hmv; Wed, 20 Dec 2006 10:16:25 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id AE49F2000296;
	Wed, 20 Dec 2006 10:16:25 +0100 (CET)
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
Subject: RE: [NSIS] Simple question to NATFW people
Date: Wed, 20 Dec 2006 10:15:49 +0100
Message-ID: <113091BD57179D4491C19DA7E10CD6968C8689@mx1.office>
In-Reply-To: <Pine.LNX.4.64.0612200007580.15055@sbz-31.cs.Helsinki.FI>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Simple question to NATFW people
Thread-Index: AccjvACnqjbgxu6SSI2Km397f9lo1QAWrBiw
From: "Martin Stiemerling" <Stiemerling@netlab.nec.de>
To: "Jukka MJ Manner" <jmanner@cs.Helsinki.FI>, <nsis@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: 
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

Hi Jukka, =20

> -----Original Message-----
> From: Jukka MJ Manner [mailto:jmanner@cs.Helsinki.FI]=20
> Sent: Tuesday, December 19, 2006 11:20 PM
> To: nsis@ietf.org
> Subject: [NSIS] Simple question to NATFW people
>=20
>=20
> We are working on the NATFW, but a simple question just occured to me.
>=20
> For browsing a simple web site, do I need 1 or 2 requests to=20
> the firewall?
>=20
> Consider the following:
>=20
> 1) MyPC--->WWWserver  - I send a TCP SYN packet to the destination,
> 2) WWWserver <---MyPC - destination sends back SYN-ACK
> 3) MyPC--->WWWserver  -  I reply with an ACK.
> 4) From now on, data can be sent on both directions
>=20
> I have a NATFW capable firewall protecting my network,=20
> working in proxy mode.
>=20
> The spec doesn't mention any bi-directional firewall holes,=20
> so basically, do I need to request a hole for MyPC->WWWserver=20
> and a second for=20
> WWWserver->MyPC?=20
>=20

You do need two requests to the firewall when operating in the regular
mode, i.e., both ends support NSIS:
- 1st request MyPC->WWWserver
- 2nd request WWWserver->MyPC

Basically, from an NSIS model view, those bi-directional flows are two
uni-directional flows, as also in the RSVP model.

However, you can use the proxy mode, where your local firewall is
generating the 2nd request, if only your side needs to be configured.=20

> Or can I just ask for 1 hole for this particular connection, for all=20
> packets belonging to this TCP flow, regardless of the direction?

No, that is not possible.=20

 Martin=20

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



From nsis-bounces@ietf.org Wed Dec 20 05:02:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwyGr-0001MQ-L2; Wed, 20 Dec 2006 05:01:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwyGp-0001M7-Q5
	for nsis@ietf.org; Wed, 20 Dec 2006 05:01:55 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwyEc-0005P4-7d
	for nsis@ietf.org; Wed, 20 Dec 2006 04:59:40 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kBK9xJBh001066; Wed, 20 Dec 2006 10:59:31 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>, <nsis@ietf.org>
Date: Wed, 20 Dec 2006 10:59:14 +0100
Message-ID: <001101c7241d$86f408e0$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC8043@KCCLUST06EVS1.ugd.att.com>
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAULntzA=
X-Spam-Score: 0.3 () FVGT_s_OBFU_Q1
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Wed, 20 Dec 2006 10:59:32 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de
Cc: attila.bader@ericsson.com
Subject: [NSIS] Why is QSPEC control information removed?
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

Hi Jerry

I have not yet finished reviewing the QSEPC template draft, 
but I have seen that you have removed the concept of QSPEC control
information.
Why is that?
The concept of QSPEC control information has to remain. 

Best Regards,
Georgios



 

> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> Sent: donderdag 14 december 2006 1:00
> To: nsis@ietf.org
> Cc: Ash, Gerald R (Jerry), ALABS
> Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt 
> 
> Hi All,
> 
> The updated 'QoS NSLP QSPEC Template' I-D is available at 
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
> 
> The main changes are as follows:
> 
> 1. notion of QOSMs played down
>   o language e.g. 'QNSLP/QSPEC can signal for different QOSMs across
>     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
>     QNEs on the path to implement different data plane QoS mechanisms
>     that meet QSPEC constraints'
>   o a QOSM describes common capabilities among QNEs to act
>     consistently when requested to admit traffic & in treating
>     admitted traffic
>   o a QOSM ID need not be defined or signaled
>   o a QNE need not support any particular QOSM although a  QNI
>     normally includes a QSPEC corresponding to a particular 
> QOSM 2. a 'QOSM specification'
>   o still provides a rigorous specification of a QOSM & what it does
>   o documents how a QNE interprets & treats various elements in QSPEC
>   o can define additional QSPEC parameters 3. updated QOSM definition:
>   a method to achieve QoS for a traffic flow, e.g., IntServ
>   Controlled Load; specifies what sub-set of QSPEC QoS constraints &
>   traffic handling directives a QNE implementing that QOSM is capable
>   of supporting & how resources will be managed by the RMF 4. 
> QSPEC1/QSPEC2 semantics replaced with following semantics:
>   o source traffic description (mandatory to include by QNI &
>     mandatory to interpret by downstream QNEs)
>     > specified by traffic model (TMOD-1) parameter consisting of
>       rate (r), bucket size (b), peak rate (p), minimum policed unit
>      (m) (mathematically complete way to describe traffic source)
>     > bandwidth only set r=p; b/m to large values (separate
>       bandwidth parameter not needed)
>     > TMOD-2 (optional to include)
>   o constraints (optional to include):
>     > Path Latency
>     > Path Jitter
>     > Path PLR
>     > Path PER
>     > Slack Term
>     > Priority (Preemption, Defending, Admission, RPH Priority)
>   o handling directives (optional to include):
>     > Excess Treatment
>   o traffic classifiers (optional to include):
>     > PHB Class (PHB class set by downstream QNE to tell QNI how to
>       mark traffic to ensure treatment committed by admission
>       control)
>     > DSTE Class Type
>     > Y.1541 QoS class
>   o eliminated:
>     > Bandwidth
>     > Ctot, Dtot, Csum, Dsum
> 5. concept of remapping QSPEC parameters eliminated 6. 
> redefine 'interpret' a QSPEC parameter to mean 'must conform to
>    RFCs defining parameter & procedures (formerly called 'strictly
>    interpret')
> 7. concept of local QSPECs retained
>   o allows simpler control plane in a local domain
>   o edge nodes
>     > must interpret initiator QSPEC parameters
>     > can either initiate parallel session with local QSPEC or
>       define a local QSPEC with encapsulated initiator QSPEC
>   o local QSPEC interpreted by local domain QNEs
>   o local QSPEC must be consistent with initiator QSPEC
>     > e.g., RMD can initiate a local QSPEC that contains TMOD =
>       bandwidth (sets r=p, b/m to large) 8. QSPEC flags 
> modified as follows:
>   o QNI sets M flag for each QSPEC parameter it populates that must
>     be interpreted or reservation fails
>   o if M flag set
>     > downstream QNE MUST interpret parameter or reservation fails
>     > if QNE does not support parameter it sets N flag & rejects
>       reservation
>     > if QNE supports parameter but cannot meet parameter, it sets E
>       flag & rejects reservation
>   o if M flag not set
>     > downstream QNE SHOULD interpret parameter
>     > if QNE does not support parameter it sets the N flag &
>       optionally accepts or rejects reservation
>     > if QNE supports parameter but cannot meet parameter, it sets E
>       flag & optionally accepts or rejects reservation
>   o R (remapped parameter) flag & Q (non QOSM) flag 
> eliminated 9. QSPEC type defined and registry established in 
> IANA section.
> 
> Please review the updated draft.
> 
> Thanks,
> Jerry
> 
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Wednesday, December 13, 2006 3:50 PM
> To: i-d-announce@ietf.org
> Cc: nsis@ietf.org
> Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Next Steps in Signaling 
> Working Group of the IETF.
> 
> 	Title		: QoS NSLP QSPEC Template
> 	Author(s)	: J. Ash, et al.
> 	Filename	: draft-ietf-nsis-qspec-13.txt
> 	Pages		: 52
> 	Date		: 2006-12-13
> 	
> The QoS NSLP protocol is used to signal QoS reservations and is
>    independent of a specific QoS model (QOSM) such as IntServ or
>    DiffServ.  Rather, all information specific to a QOSM is 
> encapsulated
>    in a separate object, the QSPEC.  This document defines a template
>    for the QSPEC including a number of QSPEC parameters.  The QSPEC
>    parameters provide a common language to be re-used in several QOSMs
>    and thereby aim to ensure the extensibility and interoperability of
>    QoS NSLP.  The node initiating the NSIS signaling adds an initiator
>    QSPEC, which indicates the QSPEC parameters that must be 
> interpreted
>    by the downstream nodes less the reservation fails, 
> thereby ensuring
>    the intention of the NSIS initiator is preserved along the 
> signaling
>    path.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 



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



From nsis-bounces@ietf.org Wed Dec 20 05:26:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwyeZ-0001xc-EX; Wed, 20 Dec 2006 05:26:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwyeY-0001xS-5Z
	for nsis@ietf.org; Wed, 20 Dec 2006 05:26:26 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwyeR-0005R6-0f
	for nsis@ietf.org; Wed, 20 Dec 2006 05:26:26 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kBKAQAmr001873; Wed, 20 Dec 2006 11:26:15 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>, <nsis@ietf.org>
Date: Wed, 20 Dec 2006 11:26:05 +0100
Message-ID: <001201c72421$44c636b0$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC8043@KCCLUST06EVS1.ugd.att.com>
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5A=
X-Spam-Score: 0.4 () FVGT_s_OBFU_Q1,FVGT_u_HAS_2LETTERFLDR
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Wed, 20 Dec 2006 11:26:16 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ba0d4c5f57f7c289496fce758bbf4798
Cc: 
Subject: [NSIS] Comments on draft-ietf-nsis-qspec-13.txt 
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

Hi Jerry

Here are my comments on draft-ietf-nsis-qspec-13.txt:

Comment_1:
--------------
Please reinclude the concept of QSPEC control information 
that was included in all previous versions of the QSPEC template draft.
In http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
concept
was described in Section 5.1.


------------------

Comment_2:
-----------

Section 6.1:
Please reintroduce the format that is required in order to specify the QSEPC
control information, see:
Section 7.1 of:
http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt

----------------


Comment_3:
----------
Section 4.1 :QoS Models
The definition of the QoS model is not complete. An important sentence that 
was used in the previous version of the draft is removed. 
Please add the following sentence to the definition of the QoS Model (QOSM):

The same as described above have to be applied in this section.
After the following sentence:

"A QOSM specification MAY include the following:"

include the following bullet:
"- it specifies how to use QOS NSLP to signal for this QOSM"

------------------

Comment_4:
-------------
Section 5.1 Local QSPEC definition and processing

By reading this section it gives the impression that 
the two methods a) and b) cannot be used by the same QoS model. 
Method a): translate the
   initiator QSPEC into a local QSPEC and encapsulate the initiator
   QSPEC in the RESERVE message
Method b): b) tunnel the initiator QSPEC
   through the local domain and reserve resources by generating a new
   RESERVE message through the local domain containing the local QSPEC.

Note that according to the discussions that we have had until now 
method a) should be able to be used in combination with method b) by the
same QoS model 
for the situation that the local QSPEC encapsulates the initiator QSPEC 
in order to satisfy requirement 5.4.2 that is specified in 
RFC 3726, see:
http://www.ietf.org/rfc/rfc3726.txt

Please add the following sentence at the end of the first paragraph of
Section 5.1.
"Note that when method b) is used, the encapsulation of the initiator QSPEC
into a
local QSPEC should also be possible when the local QoS model needs to
satisfy Requirement 
5.4.2 specified in RFC 3726, by adding and removing local QOSM-specific
Control 
Information parameters on top of the initiator QSPEC."

-----------------------------

Comment_5:
-----------
Section 5.1, last paragraph:

Please change the following:
"For example, RMD can define a local QSPEC that contains 
TMOD = bandwidth (sets r=p, b/m to large)."

Into:
"For example, in RMD the TMOD parameters contained in the original initiator
QSPEC 
are mapped into the equivalent TMOD parameter representing only the peak
bandwidth 
in the local QSPEC."


----------------------------

Comment_6:
-------------
In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to be followed regarding
the 
QSEPC control information are not given: 

Please include the following paragraph at the end of this section:
"Regarding QSPEC Control Information, the default rule is that all
   QSPEC parameters that have been included in the RESERVE message by
   the QNI are also included in the RESPONSE message by the QNR with the
   value they had when arriving at the QNR.  When traveling in the
   RESPONSE message, all QSPEC Control Information parameters are
   read-only.  Note that a QOSM specification may define its own
   QOSM-specific Control Information parameters and processing rules."

---------------------------

Comment_7:
------------
Section 6.1:
I do not undersatnd the second sentence from the below two sentences:
"N Flag: Not-supported QSPEC parameter flag (see Section 5.2.2).
           For QSPEC parameters the value of this flag is always zero."

---------------------

Best Regards,
Georgios

> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> Sent: donderdag 14 december 2006 1:00
> To: nsis@ietf.org
> Cc: Ash, Gerald R (Jerry), ALABS
> Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt 
> 
> Hi All,
> 
> The updated 'QoS NSLP QSPEC Template' I-D is available at 
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
> 
> The main changes are as follows:
> 
> 1. notion of QOSMs played down
>   o language e.g. 'QNSLP/QSPEC can signal for different QOSMs across
>     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
>     QNEs on the path to implement different data plane QoS mechanisms
>     that meet QSPEC constraints'
>   o a QOSM describes common capabilities among QNEs to act
>     consistently when requested to admit traffic & in treating
>     admitted traffic
>   o a QOSM ID need not be defined or signaled
>   o a QNE need not support any particular QOSM although a  QNI
>     normally includes a QSPEC corresponding to a particular 
> QOSM 2. a 'QOSM specification'
>   o still provides a rigorous specification of a QOSM & what it does
>   o documents how a QNE interprets & treats various elements in QSPEC
>   o can define additional QSPEC parameters 3. updated QOSM definition:
>   a method to achieve QoS for a traffic flow, e.g., IntServ
>   Controlled Load; specifies what sub-set of QSPEC QoS constraints &
>   traffic handling directives a QNE implementing that QOSM is capable
>   of supporting & how resources will be managed by the RMF 4. 
> QSPEC1/QSPEC2 semantics replaced with following semantics:
>   o source traffic description (mandatory to include by QNI &
>     mandatory to interpret by downstream QNEs)
>     > specified by traffic model (TMOD-1) parameter consisting of
>       rate (r), bucket size (b), peak rate (p), minimum policed unit
>      (m) (mathematically complete way to describe traffic source)
>     > bandwidth only set r=p; b/m to large values (separate
>       bandwidth parameter not needed)
>     > TMOD-2 (optional to include)
>   o constraints (optional to include):
>     > Path Latency
>     > Path Jitter
>     > Path PLR
>     > Path PER
>     > Slack Term
>     > Priority (Preemption, Defending, Admission, RPH Priority)
>   o handling directives (optional to include):
>     > Excess Treatment
>   o traffic classifiers (optional to include):
>     > PHB Class (PHB class set by downstream QNE to tell QNI how to
>       mark traffic to ensure treatment committed by admission
>       control)
>     > DSTE Class Type
>     > Y.1541 QoS class
>   o eliminated:
>     > Bandwidth
>     > Ctot, Dtot, Csum, Dsum
> 5. concept of remapping QSPEC parameters eliminated 6. 
> redefine 'interpret' a QSPEC parameter to mean 'must conform to
>    RFCs defining parameter & procedures (formerly called 'strictly
>    interpret')
> 7. concept of local QSPECs retained
>   o allows simpler control plane in a local domain
>   o edge nodes
>     > must interpret initiator QSPEC parameters
>     > can either initiate parallel session with local QSPEC or
>       define a local QSPEC with encapsulated initiator QSPEC
>   o local QSPEC interpreted by local domain QNEs
>   o local QSPEC must be consistent with initiator QSPEC
>     > e.g., RMD can initiate a local QSPEC that contains TMOD =
>       bandwidth (sets r=p, b/m to large) 8. QSPEC flags 
> modified as follows:
>   o QNI sets M flag for each QSPEC parameter it populates that must
>     be interpreted or reservation fails
>   o if M flag set
>     > downstream QNE MUST interpret parameter or reservation fails
>     > if QNE does not support parameter it sets N flag & rejects
>       reservation
>     > if QNE supports parameter but cannot meet parameter, it sets E
>       flag & rejects reservation
>   o if M flag not set
>     > downstream QNE SHOULD interpret parameter
>     > if QNE does not support parameter it sets the N flag &
>       optionally accepts or rejects reservation
>     > if QNE supports parameter but cannot meet parameter, it sets E
>       flag & optionally accepts or rejects reservation
>   o R (remapped parameter) flag & Q (non QOSM) flag 
> eliminated 9. QSPEC type defined and registry established in 
> IANA section.
> 
> Please review the updated draft.
> 
> Thanks,
> Jerry
> 
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Wednesday, December 13, 2006 3:50 PM
> To: i-d-announce@ietf.org
> Cc: nsis@ietf.org
> Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Next Steps in Signaling 
> Working Group of the IETF.
> 
> 	Title		: QoS NSLP QSPEC Template
> 	Author(s)	: J. Ash, et al.
> 	Filename	: draft-ietf-nsis-qspec-13.txt
> 	Pages		: 52
> 	Date		: 2006-12-13
> 	
> The QoS NSLP protocol is used to signal QoS reservations and is
>    independent of a specific QoS model (QOSM) such as IntServ or
>    DiffServ.  Rather, all information specific to a QOSM is 
> encapsulated
>    in a separate object, the QSPEC.  This document defines a template
>    for the QSPEC including a number of QSPEC parameters.  The QSPEC
>    parameters provide a common language to be re-used in several QOSMs
>    and thereby aim to ensure the extensibility and interoperability of
>    QoS NSLP.  The node initiating the NSIS signaling adds an initiator
>    QSPEC, which indicates the QSPEC parameters that must be 
> interpreted
>    by the downstream nodes less the reservation fails, 
> thereby ensuring
>    the intention of the NSIS initiator is preserved along the 
> signaling
>    path.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 



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



From nsis-bounces@ietf.org Wed Dec 20 06:54:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx01g-0008TE-Ha; Wed, 20 Dec 2006 06:54:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx01f-0008Sn-4E
	for nsis@ietf.org; Wed, 20 Dec 2006 06:54:23 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx01a-0003LT-Bg
	for nsis@ietf.org; Wed, 20 Dec 2006 06:54:23 -0500
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	25E774F0001; Wed, 20 Dec 2006 12:53:41 +0100 (CET)
Received: from esealmw116.eemea.ericsson.se ([153.88.200.7]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Dec 2006 12:53:41 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Dec 2006 12:53:40 +0100
Message-ID: <53CCFDD6E346CB43994852666C210E910F7386@esealmw116.eemea.ericsson.se>
In-Reply-To: <001101c7241d$86f408e0$4c0d5982@dynamic.ewi.utwente.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Why is QSPEC control information removed?
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAULntzAAAvUVQA==
From: =?iso-8859-1?Q?Attila_B=E1der_=28IJ/ETH=29?= <attila.bader@ericsson.com>
To: "Georgios Karagiannis" <karagian@cs.utwente.nl>,
	"Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, <nsis@ietf.org>
X-OriginalArrivalTime: 20 Dec 2006 11:53:41.0016 (UTC)
	FILETIME=[7E0B8180:01C7242D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2bf730a014b318fd3efd65b39b48818c
Cc: 
Subject: [NSIS] RE: Why is QSPEC control information removed?
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

Hi Georgios, Jerry,

I think mostly just the name changed, the concept is still there. =
Control info is changed to traffic handling directives, see 4.3.3.. I =
assume that defining new control parameters or directives in QOS Model =
is still possible. The QoS Model should specify which QOS NSLP option is =
used, it also belongs to directives, is not it?

Best regards, Attila
=20

>-----Original Message-----
>From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]=20
>Sent: Wednesday, December 20, 2006 10:59 AM
>To: 'Ash, Gerald R (Jerry), ALABS'; nsis@ietf.org
>Cc: Attila B=E1der (IJ/ETH)
>Subject: Why is QSPEC control information removed?
>
>Hi Jerry
>
>I have not yet finished reviewing the QSEPC template draft,=20
>but I have seen that you have removed the concept of QSPEC=20
>control information.
>Why is that?
>The concept of QSPEC control information has to remain.=20
>
>Best Regards,
>Georgios
>
>
>
>=20
>
>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>> Sent: donderdag 14 december 2006 1:00
>> To: nsis@ietf.org
>> Cc: Ash, Gerald R (Jerry), ALABS
>> Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
>>=20
>> Hi All,
>>=20
>> The updated 'QoS NSLP QSPEC Template' I-D is available at=20
>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
>>=20
>> The main changes are as follows:
>>=20
>> 1. notion of QOSMs played down
>>   o language e.g. 'QNSLP/QSPEC can signal for different QOSMs across
>>     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
>>     QNEs on the path to implement different data plane QoS mechanisms
>>     that meet QSPEC constraints'
>>   o a QOSM describes common capabilities among QNEs to act
>>     consistently when requested to admit traffic & in treating
>>     admitted traffic
>>   o a QOSM ID need not be defined or signaled
>>   o a QNE need not support any particular QOSM although a  QNI
>>     normally includes a QSPEC corresponding to a particular=20
>QOSM 2. a=20
>> 'QOSM specification'
>>   o still provides a rigorous specification of a QOSM & what it does
>>   o documents how a QNE interprets & treats various elements in QSPEC
>>   o can define additional QSPEC parameters 3. updated QOSM=20
>definition:
>>   a method to achieve QoS for a traffic flow, e.g., IntServ
>>   Controlled Load; specifies what sub-set of QSPEC QoS constraints &
>>   traffic handling directives a QNE implementing that QOSM is capable
>>   of supporting & how resources will be managed by the RMF 4.=20
>> QSPEC1/QSPEC2 semantics replaced with following semantics:
>>   o source traffic description (mandatory to include by QNI &
>>     mandatory to interpret by downstream QNEs)
>>     > specified by traffic model (TMOD-1) parameter consisting of
>>       rate (r), bucket size (b), peak rate (p), minimum policed unit
>>      (m) (mathematically complete way to describe traffic source)
>>     > bandwidth only set r=3Dp; b/m to large values (separate
>>       bandwidth parameter not needed)
>>     > TMOD-2 (optional to include)
>>   o constraints (optional to include):
>>     > Path Latency
>>     > Path Jitter
>>     > Path PLR
>>     > Path PER
>>     > Slack Term
>>     > Priority (Preemption, Defending, Admission, RPH Priority)
>>   o handling directives (optional to include):
>>     > Excess Treatment
>>   o traffic classifiers (optional to include):
>>     > PHB Class (PHB class set by downstream QNE to tell QNI how to
>>       mark traffic to ensure treatment committed by admission
>>       control)
>>     > DSTE Class Type
>>     > Y.1541 QoS class
>>   o eliminated:
>>     > Bandwidth
>>     > Ctot, Dtot, Csum, Dsum
>> 5. concept of remapping QSPEC parameters eliminated 6.=20
>> redefine 'interpret' a QSPEC parameter to mean 'must conform to
>>    RFCs defining parameter & procedures (formerly called 'strictly
>>    interpret')
>> 7. concept of local QSPECs retained
>>   o allows simpler control plane in a local domain
>>   o edge nodes
>>     > must interpret initiator QSPEC parameters
>>     > can either initiate parallel session with local QSPEC or
>>       define a local QSPEC with encapsulated initiator QSPEC
>>   o local QSPEC interpreted by local domain QNEs
>>   o local QSPEC must be consistent with initiator QSPEC
>>     > e.g., RMD can initiate a local QSPEC that contains TMOD =3D
>>       bandwidth (sets r=3Dp, b/m to large) 8. QSPEC flags modified as =

>> follows:
>>   o QNI sets M flag for each QSPEC parameter it populates that must
>>     be interpreted or reservation fails
>>   o if M flag set
>>     > downstream QNE MUST interpret parameter or reservation fails
>>     > if QNE does not support parameter it sets N flag & rejects
>>       reservation
>>     > if QNE supports parameter but cannot meet parameter, it sets E
>>       flag & rejects reservation
>>   o if M flag not set
>>     > downstream QNE SHOULD interpret parameter
>>     > if QNE does not support parameter it sets the N flag &
>>       optionally accepts or rejects reservation
>>     > if QNE supports parameter but cannot meet parameter, it sets E
>>       flag & optionally accepts or rejects reservation
>>   o R (remapped parameter) flag & Q (non QOSM) flag eliminated 9.=20
>> QSPEC type defined and registry established in IANA section.
>>=20
>> Please review the updated draft.
>>=20
>> Thanks,
>> Jerry
>>=20
>> -----Original Message-----
>> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>> Sent: Wednesday, December 13, 2006 3:50 PM
>> To: i-d-announce@ietf.org
>> Cc: nsis@ietf.org
>> Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
>>=20
>> A New Internet-Draft is available from the on-line Internet-Drafts=20
>> directories.
>> This draft is a work item of the Next Steps in Signaling=20
>Working Group=20
>> of the IETF.
>>=20
>> 	Title		: QoS NSLP QSPEC Template
>> 	Author(s)	: J. Ash, et al.
>> 	Filename	: draft-ietf-nsis-qspec-13.txt
>> 	Pages		: 52
>> 	Date		: 2006-12-13
>> =09
>> The QoS NSLP protocol is used to signal QoS reservations and is
>>    independent of a specific QoS model (QOSM) such as IntServ or
>>    DiffServ.  Rather, all information specific to a QOSM is=20
>> encapsulated
>>    in a separate object, the QSPEC.  This document defines a template
>>    for the QSPEC including a number of QSPEC parameters.  The QSPEC
>>    parameters provide a common language to be re-used in=20
>several QOSMs
>>    and thereby aim to ensure the extensibility and=20
>interoperability of
>>    QoS NSLP.  The node initiating the NSIS signaling adds an=20
>initiator
>>    QSPEC, which indicates the QSPEC parameters that must be=20
>> interpreted
>>    by the downstream nodes less the reservation fails, thereby=20
>> ensuring
>>    the intention of the NSIS initiator is preserved along the=20
>> signaling
>>    path.
>>=20
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt
>>=20
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>=20
>
>
>

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



From nsis-bounces@ietf.org Wed Dec 20 07:27:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx0Xh-0000ZL-12; Wed, 20 Dec 2006 07:27:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx0Xf-0000ZG-Rg
	for nsis@ietf.org; Wed, 20 Dec 2006 07:27:27 -0500
Received: from mail120.messagelabs.com ([216.82.250.83])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gx0Xd-0003Ow-97
	for nsis@ietf.org; Wed, 20 Dec 2006 07:27:27 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-4.tower-120.messagelabs.com!1166617643!18785246!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 16354 invoked from network); 20 Dec 2006 12:27:23 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-4.tower-120.messagelabs.com with SMTP;
	20 Dec 2006 12:27:23 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kBKCRNKI001768; 
	Wed, 20 Dec 2006 07:27:23 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst12.ugd.att.com [135.38.164.89])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id
	kBKCREa7001681; Wed, 20 Dec 2006 07:27:14 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Dec 2006 06:27:14 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC805D@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <53CCFDD6E346CB43994852666C210E910F7386@esealmw116.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Why is QSPEC control information removed?
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAULntzAAAvUVQAAB/i+A
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, nsis@ietf.org,
	=?iso-8859-1?Q?Attila_B=E1der_=28IJ/ETH=29?= <attila.bader@ericsson.com>
Subject: [NSIS] RE: Why is QSPEC control information removed?
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

Hi Georgios,

Attila is right.  No functionality has changed. =20

In the previous draft the only 'control information' parameter was =
'excess treatment'.  That parameter is now defined as a 'traffic =
handling directive' parameter in Sections 4.3.3 and 6.2.11. =20

New QSPEC parameters can still be defined in QOSM specification =
documents, as specified in Section 5.4.

Thanks,
Regards,
Jerry

-----Original Message-----
From: Attila B=E1der (IJ/ETH) [mailto:attila.bader@ericsson.com]=20
Sent: Wednesday, December 20, 2006 6:54 AM
To: Georgios Karagiannis; Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
Subject: RE: Why is QSPEC control information removed?

Hi Georgios, Jerry,

I think mostly just the name changed, the concept is still there. =
Control info is changed to traffic handling directives, see 4.3.3.. I =
assume that defining new control parameters or directives in QOS Model =
is still possible. The QoS Model should specify which QOS NSLP option is =
used, it also belongs to directives, is not it?

Best regards, Attila
=20

>-----Original Message-----
>From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]=20
>Sent: Wednesday, December 20, 2006 10:59 AM
>To: 'Ash, Gerald R (Jerry), ALABS'; nsis@ietf.org
>Cc: Attila B=E1der (IJ/ETH)
>Subject: Why is QSPEC control information removed?
>
>Hi Jerry
>
>I have not yet finished reviewing the QSEPC template draft,=20
>but I have seen that you have removed the concept of QSPEC=20
>control information.
>Why is that?
>The concept of QSPEC control information has to remain.=20
>
>Best Regards,
>Georgios
>
>
>
>=20
>
>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>> Sent: donderdag 14 december 2006 1:00
>> To: nsis@ietf.org
>> Cc: Ash, Gerald R (Jerry), ALABS
>> Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
>>=20
>> Hi All,
>>=20
>> The updated 'QoS NSLP QSPEC Template' I-D is available at=20
>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
>>=20
>> The main changes are as follows:
>>=20
>> 1. notion of QOSMs played down
>>   o language e.g. 'QNSLP/QSPEC can signal for different QOSMs across
>>     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
>>     QNEs on the path to implement different data plane QoS mechanisms
>>     that meet QSPEC constraints'
>>   o a QOSM describes common capabilities among QNEs to act
>>     consistently when requested to admit traffic & in treating
>>     admitted traffic
>>   o a QOSM ID need not be defined or signaled
>>   o a QNE need not support any particular QOSM although a  QNI
>>     normally includes a QSPEC corresponding to a particular=20
>QOSM 2. a=20
>> 'QOSM specification'
>>   o still provides a rigorous specification of a QOSM & what it does
>>   o documents how a QNE interprets & treats various elements in QSPEC
>>   o can define additional QSPEC parameters 3. updated QOSM=20
>definition:
>>   a method to achieve QoS for a traffic flow, e.g., IntServ
>>   Controlled Load; specifies what sub-set of QSPEC QoS constraints &
>>   traffic handling directives a QNE implementing that QOSM is capable
>>   of supporting & how resources will be managed by the RMF 4.=20
>> QSPEC1/QSPEC2 semantics replaced with following semantics:
>>   o source traffic description (mandatory to include by QNI &
>>     mandatory to interpret by downstream QNEs)
>>     > specified by traffic model (TMOD-1) parameter consisting of
>>       rate (r), bucket size (b), peak rate (p), minimum policed unit
>>      (m) (mathematically complete way to describe traffic source)
>>     > bandwidth only set r=3Dp; b/m to large values (separate
>>       bandwidth parameter not needed)
>>     > TMOD-2 (optional to include)
>>   o constraints (optional to include):
>>     > Path Latency
>>     > Path Jitter
>>     > Path PLR
>>     > Path PER
>>     > Slack Term
>>     > Priority (Preemption, Defending, Admission, RPH Priority)
>>   o handling directives (optional to include):
>>     > Excess Treatment
>>   o traffic classifiers (optional to include):
>>     > PHB Class (PHB class set by downstream QNE to tell QNI how to
>>       mark traffic to ensure treatment committed by admission
>>       control)
>>     > DSTE Class Type
>>     > Y.1541 QoS class
>>   o eliminated:
>>     > Bandwidth
>>     > Ctot, Dtot, Csum, Dsum
>> 5. concept of remapping QSPEC parameters eliminated 6.=20
>> redefine 'interpret' a QSPEC parameter to mean 'must conform to
>>    RFCs defining parameter & procedures (formerly called 'strictly
>>    interpret')
>> 7. concept of local QSPECs retained
>>   o allows simpler control plane in a local domain
>>   o edge nodes
>>     > must interpret initiator QSPEC parameters
>>     > can either initiate parallel session with local QSPEC or
>>       define a local QSPEC with encapsulated initiator QSPEC
>>   o local QSPEC interpreted by local domain QNEs
>>   o local QSPEC must be consistent with initiator QSPEC
>>     > e.g., RMD can initiate a local QSPEC that contains TMOD =3D
>>       bandwidth (sets r=3Dp, b/m to large) 8. QSPEC flags modified as =

>> follows:
>>   o QNI sets M flag for each QSPEC parameter it populates that must
>>     be interpreted or reservation fails
>>   o if M flag set
>>     > downstream QNE MUST interpret parameter or reservation fails
>>     > if QNE does not support parameter it sets N flag & rejects
>>       reservation
>>     > if QNE supports parameter but cannot meet parameter, it sets E
>>       flag & rejects reservation
>>   o if M flag not set
>>     > downstream QNE SHOULD interpret parameter
>>     > if QNE does not support parameter it sets the N flag &
>>       optionally accepts or rejects reservation
>>     > if QNE supports parameter but cannot meet parameter, it sets E
>>       flag & optionally accepts or rejects reservation
>>   o R (remapped parameter) flag & Q (non QOSM) flag eliminated 9.=20
>> QSPEC type defined and registry established in IANA section.
>>=20
>> Please review the updated draft.
>>=20
>> Thanks,
>> Jerry
>>=20
>> -----Original Message-----
>> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>> Sent: Wednesday, December 13, 2006 3:50 PM
>> To: i-d-announce@ietf.org
>> Cc: nsis@ietf.org
>> Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
>>=20
>> A New Internet-Draft is available from the on-line Internet-Drafts=20
>> directories.
>> This draft is a work item of the Next Steps in Signaling=20
>Working Group=20
>> of the IETF.
>>=20
>> 	Title		: QoS NSLP QSPEC Template
>> 	Author(s)	: J. Ash, et al.
>> 	Filename	: draft-ietf-nsis-qspec-13.txt
>> 	Pages		: 52
>> 	Date		: 2006-12-13
>> =09
>> The QoS NSLP protocol is used to signal QoS reservations and is
>>    independent of a specific QoS model (QOSM) such as IntServ or
>>    DiffServ.  Rather, all information specific to a QOSM is=20
>> encapsulated
>>    in a separate object, the QSPEC.  This document defines a template
>>    for the QSPEC including a number of QSPEC parameters.  The QSPEC
>>    parameters provide a common language to be re-used in=20
>several QOSMs
>>    and thereby aim to ensure the extensibility and=20
>interoperability of
>>    QoS NSLP.  The node initiating the NSIS signaling adds an=20
>initiator
>>    QSPEC, which indicates the QSPEC parameters that must be=20
>> interpreted
>>    by the downstream nodes less the reservation fails, thereby=20
>> ensuring
>>    the intention of the NSIS initiator is preserved along the=20
>> signaling
>>    path.
>>=20
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt
>>=20
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>=20
>
>
>

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



From nsis-bounces@ietf.org Wed Dec 20 08:20:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx1N9-0001s4-0l; Wed, 20 Dec 2006 08:20:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx1N7-0001qN-Ea
	for nsis@ietf.org; Wed, 20 Dec 2006 08:20:37 -0500
Received: from mail146.messagelabs.com ([216.82.245.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gx1N2-0006sV-Un
	for nsis@ietf.org; Wed, 20 Dec 2006 08:20:37 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-7.tower-146.messagelabs.com!1166620831!11659127!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 6992 invoked from network); 20 Dec 2006 13:20:31 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-7.tower-146.messagelabs.com with SMTP;
	20 Dec 2006 13:20:31 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kBKDKUt9021981; 
	Wed, 20 Dec 2006 08:20:30 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst12.ugd.att.com [135.38.164.89])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id
	kBKDKPgR021926; Wed, 20 Dec 2006 08:20:25 -0500 (EST)
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: Wed, 20 Dec 2006 07:20:25 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC805E@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <001201c72421$44c636b0$4c0d5982@dynamic.ewi.utwente.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8A==
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "Georgios Karagiannis" <karagian@cs.utwente.nl>, <nsis@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fe105289edd72640d9f392da880eefa2
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
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

Hi Georgios,

See below.=20

> -----Original Message-----
> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]=20
> Sent: Wednesday, December 20, 2006 5:26 AM
> To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> Subject: Comments on draft-ietf-nsis-qspec-13.txt=20
>=20
> Hi Jerry
>=20
> Here are my comments on draft-ietf-nsis-qspec-13.txt:
>=20
> Comment_1:
> --------------
> Please reinclude the concept of QSPEC control information=20
> that was included in all previous versions of the QSPEC=20
> template draft.
> In=20
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
> concept
> was described in Section 5.1.

Please see previous email comment on QSPEC control information.

> Comment_2:
> -----------
>=20
> Section 6.1:
> Please reintroduce the format that is required in order to=20
> specify the QSPEC
> control information, see:
> Section 7.1 of:
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt

Please see previous email comment on QSPEC control information.

> Comment_3:
> ----------
> Section 4.1 :QoS Models
> The definition of the QoS model is not complete. An important=20
> sentence that=20
> was used in the previous version of the draft is removed.=20
> Please add the following sentence to the definition of the=20
> QoS Model (QOSM):
>=20
> The same as described above have to be applied in this section.
> After the following sentence:
>=20
> "A QOSM specification MAY include the following:"
>=20
> include the following bullet:
> "- it specifies how to use QOS NSLP to signal for this QOSM"

That sentence was removed in Dave's proposed QOSM re-definition, see
http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.html.  It
was unclear what that sentence meant, QoS-NSLP specifies how to signal,
not QOSM specifications, so the sentence was removed. =20

I believe the sentence was intended to mean that when QoS NSLP allows
various options to be selected, a QOSM should be able to determine which
option is used.  For that purpose the following sentence was added in
Section 4.1:

"     A QOSM specification MAY include the following:
     ...
     - can state which QoS-NSLP options a QOSM wants to use, when
     several options are available for a QOSM (e.g., local QSPEC to
     either be a) tunneled or b) encapsulate initiator QSPEC)."

Also, to avoid any misinterpretation that QOSMs are free to specify
additional constraints, state machines, protocol data, etc. for NSLP
beyond that which is specific =20
in the QoS NSLP specification, the following was added to Section 4.1:

"  QOSMs affect the operation of the RMF in NSIS-capable nodes, the
   information carried in QSPEC objects, and may under some
   circumstances (e.g. aggregation) cause a separate NSLP session to be
   instantiated by having the RMF as a QNI. QOSMs all utilize the common
   data, state machines, and APIs of the underlying NSIS protocols and
   are not expected to re-define or extend these in any way."

> Comment_4:
> -------------
> Section 5.1 Local QSPEC definition and processing
>=20
> By reading this section it gives the impression that=20
> the two methods a) and b) cannot be used by the same QoS model.=20
> Method a): translate the
>    initiator QSPEC into a local QSPEC and encapsulate the initiator
>    QSPEC in the RESERVE message
> Method b): b) tunnel the initiator QSPEC
>    through the local domain and reserve resources by generating a new
>    RESERVE message through the local domain containing the=20
> local QSPEC.
>=20
> Note that according to the discussions that we have had until now=20
> method a) should be able to be used in combination with=20
> method b) by the
> same QoS model=20
> for the situation that the local QSPEC encapsulates the=20
> initiator QSPEC=20
> in order to satisfy requirement 5.4.2 that is specified in=20
> RFC 3726, see:
> http://www.ietf.org/rfc/rfc3726.txt
>=20
> Please add the following sentence at the end of the first paragraph of
> Section 5.1.
> "Note that when method b) is used, the encapsulation of the=20
> initiator QSPEC
> into a
> local QSPEC should also be possible when the local QoS model needs to
> satisfy Requirement=20
> 5.4.2 specified in RFC 3726, by adding and removing local=20
> QOSM-specific
> Control=20
> Information parameters on top of the initiator QSPEC."

Your comment here is not clear to me.  It would help to provide an
example to illustrate what you are trying to accomplish.  It seems that
you are trying to specify QoS-NSLP functionality, rather than QSPEC
functionality.  If so, that functionality should be specified in the
QoS-NSLP draft rather than the QSPEC draft, perhaps the QoS-NSLP authors
can comment.

> Comment_5:
> -----------
> Section 5.1, last paragraph:
>=20
> Please change the following:
> "For example, RMD can define a local QSPEC that contains=20
> TMOD =3D bandwidth (sets r=3Dp, b/m to large)."
>=20
> Into:
> "For example, in RMD the TMOD parameters contained in the=20
> original initiator
> QSPEC=20
> are mapped into the equivalent TMOD parameter representing=20
> only the peak
> bandwidth=20
> in the local QSPEC."

OK with me.

> Comment_6:
> -------------
> In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to be=20
> followed regarding
> the=20
> QSPEC control information are not given:=20
>=20
> Please include the following paragraph at the end of this section:
> "Regarding QSPEC Control Information, the default rule is that all
>    QSPEC parameters that have been included in the RESERVE message by
>    the QNI are also included in the RESPONSE message by the=20
> QNR with the
>    value they had when arriving at the QNR.  When traveling in the
>    RESPONSE message, all QSPEC Control Information parameters are
>    read-only.  Note that a QOSM specification may define its own
>    QOSM-specific Control Information parameters and processing rules."

Please see previous email comment on QSPEC control information.

> Comment_7:
> ------------
> Section 6.1:
> I do not understand the second sentence from the below two sentences:
> "N Flag: Not-supported QSPEC parameter flag (see Section 5.2.2).
>            For QSPEC parameters the value of this flag is=20
> always zero."

Good catch, this is a typo, the sentence should be removed.

Thanks,
Regards,
Jerry

>=20
> ---------------------
>=20
> Best Regards,
> Georgios
>=20
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]=20
> > Sent: donderdag 14 december 2006 1:00
> > To: nsis@ietf.org
> > Cc: Ash, Gerald R (Jerry), ALABS
> > Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt=20
> >=20
> > Hi All,
> >=20
> > The updated 'QoS NSLP QSPEC Template' I-D is available at=20
> > http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
> >=20
> > The main changes are as follows:
> >=20
> > 1. notion of QOSMs played down
> >   o language e.g. 'QNSLP/QSPEC can signal for different QOSMs across
> >     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
> >     QNEs on the path to implement different data plane QoS=20
> mechanisms
> >     that meet QSPEC constraints'
> >   o a QOSM describes common capabilities among QNEs to act
> >     consistently when requested to admit traffic & in treating
> >     admitted traffic
> >   o a QOSM ID need not be defined or signaled
> >   o a QNE need not support any particular QOSM although a  QNI
> >     normally includes a QSPEC corresponding to a particular=20
> > QOSM 2. a 'QOSM specification'
> >   o still provides a rigorous specification of a QOSM & what it does
> >   o documents how a QNE interprets & treats various=20
> elements in QSPEC
> >   o can define additional QSPEC parameters 3. updated QOSM=20
> definition:
> >   a method to achieve QoS for a traffic flow, e.g., IntServ
> >   Controlled Load; specifies what sub-set of QSPEC QoS constraints &
> >   traffic handling directives a QNE implementing that QOSM=20
> is capable
> >   of supporting & how resources will be managed by the RMF 4.=20
> > QSPEC1/QSPEC2 semantics replaced with following semantics:
> >   o source traffic description (mandatory to include by QNI &
> >     mandatory to interpret by downstream QNEs)
> >     > specified by traffic model (TMOD-1) parameter consisting of
> >       rate (r), bucket size (b), peak rate (p), minimum policed unit
> >      (m) (mathematically complete way to describe traffic source)
> >     > bandwidth only set r=3Dp; b/m to large values (separate
> >       bandwidth parameter not needed)
> >     > TMOD-2 (optional to include)
> >   o constraints (optional to include):
> >     > Path Latency
> >     > Path Jitter
> >     > Path PLR
> >     > Path PER
> >     > Slack Term
> >     > Priority (Preemption, Defending, Admission, RPH Priority)
> >   o handling directives (optional to include):
> >     > Excess Treatment
> >   o traffic classifiers (optional to include):
> >     > PHB Class (PHB class set by downstream QNE to tell QNI how to
> >       mark traffic to ensure treatment committed by admission
> >       control)
> >     > DSTE Class Type
> >     > Y.1541 QoS class
> >   o eliminated:
> >     > Bandwidth
> >     > Ctot, Dtot, Csum, Dsum
> > 5. concept of remapping QSPEC parameters eliminated 6.=20
> > redefine 'interpret' a QSPEC parameter to mean 'must conform to
> >    RFCs defining parameter & procedures (formerly called 'strictly
> >    interpret')
> > 7. concept of local QSPECs retained
> >   o allows simpler control plane in a local domain
> >   o edge nodes
> >     > must interpret initiator QSPEC parameters
> >     > can either initiate parallel session with local QSPEC or
> >       define a local QSPEC with encapsulated initiator QSPEC
> >   o local QSPEC interpreted by local domain QNEs
> >   o local QSPEC must be consistent with initiator QSPEC
> >     > e.g., RMD can initiate a local QSPEC that contains TMOD =3D
> >       bandwidth (sets r=3Dp, b/m to large) 8. QSPEC flags=20
> > modified as follows:
> >   o QNI sets M flag for each QSPEC parameter it populates that must
> >     be interpreted or reservation fails
> >   o if M flag set
> >     > downstream QNE MUST interpret parameter or reservation fails
> >     > if QNE does not support parameter it sets N flag & rejects
> >       reservation
> >     > if QNE supports parameter but cannot meet parameter, it sets E
> >       flag & rejects reservation
> >   o if M flag not set
> >     > downstream QNE SHOULD interpret parameter
> >     > if QNE does not support parameter it sets the N flag &
> >       optionally accepts or rejects reservation
> >     > if QNE supports parameter but cannot meet parameter, it sets E
> >       flag & optionally accepts or rejects reservation
> >   o R (remapped parameter) flag & Q (non QOSM) flag=20
> > eliminated 9. QSPEC type defined and registry established in=20
> > IANA section.
> >=20
> > Please review the updated draft.
> >=20
> > Thanks,
> > Jerry

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



From nsis-bounces@ietf.org Wed Dec 20 10:20:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx3F0-0005IL-U3; Wed, 20 Dec 2006 10:20:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx3Ey-0005IF-WF
	for nsis@ietf.org; Wed, 20 Dec 2006 10:20:21 -0500
Received: from rsys002x.roke.co.uk ([193.118.201.109])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx3Es-0003H1-Um
	for nsis@ietf.org; Wed, 20 Dec 2006 10:20:20 -0500
Received: from rsys005a.comm.ad.roke.co.uk (rsys005a [193.118.193.85])
	by rsys002x.roke.co.uk (8.13.1/8.13.1) with ESMTP id kBKFJKb4005524;
	Wed, 20 Dec 2006 15:19:22 GMT
Received: from [193.118.197.186] ([193.118.197.186]) by
	rsys005a.comm.ad.roke.co.uk with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Dec 2006 15:19:20 +0000
Message-ID: <45895478.6020908@roke.co.uk>
Date: Wed, 20 Dec 2006 15:19:20 +0000
From: Andrew McDonald <andrew.mcdonald@roke.co.uk>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>	<457ADA83.3000600@cs.uni-goettingen.de>
	<Pine.LNX.4.64.0612102052340.11174@sbz-31.cs.Helsinki.FI>
In-Reply-To: <Pine.LNX.4.64.0612102052340.11174@sbz-31.cs.Helsinki.FI>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Dec 2006 15:19:20.0329 (UTC)
	FILETIME=[38D93F90:01C7244A]
X-MailScanner-roke-co-uk: Found to be clean
X-MailScanner-roke-co-uk-SpamCheck: 
X-MailScanner-From: andrew.mcdonald@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: Bernd Schloer <bschloer@cs.uni-goettingen.de>, nsis@ietf.org
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

Hi Jukka, Bernd,

Jukka MJ Manner wrote:
> Andy, since this is your design, any comments?

Not sure I'd claim responsibility for all of this (though I undoubtably 
wrote some of it).

> On Sat, 9 Dec 2006, Bernd Schloer wrote:
> 
>> Hi Jukka,
>>
>>
>> the initial route A-B-C uses links (1) and (3). After link (1) fails, the path
>> is
>> rerouted using links (2) and (3).
>>
>>
>>              (1)
>>            /-----\                       |x| = QoS NSLP aware
>>          +-+     /-\ (3) +-+             +-+
>>      ----|A|     |B|-----|C|----
>>          +-+     \-/     +-+             /-\
>>            \-----/                       |x| = QoS NSLP unaware
>>              (2)
>>
>> section 3.2.10 says
>>
>>    When the QoS NSLP is aware of the route change, it needs to set up
>>    the reservation on the new path. This is done by sending a new
>>    RESERVE message. If the next QNE is, in fact, unchanged then this
>>    will be used to refresh/update the existing reservation. Otherwise it
>>    will lead to the reservation being installed on the new path.
>>
>>
>> section 5.3.1.says
>>
>>    If the RSN is greater than the current stored value, the current
>>    reservation
>>    MUST be modified appropriately (provided that admission control and policy
>>    control succeed), and the stored RSN value updated to that for the new
>>    reservation.
>>
>> According to section 3.2.10 sending a full RESERVE including a QSPEC and the
>> next
>> peer is unchanged the reservation will be updated/refreshed. However section
>> 5.3.1
>> talks not about refreshing/updating, it says the current reservation must be
>> modified
>> appropriately. What is the meaning of "appropriately" here? What happens to
>> the current
>> reservation?

"Appropriately" means "as instructed by the QSpec in the message". If 
that QSpec is unchanged (as in the section 3.2.10 case) then the only 
effect is to refresh the current reservation.

>> When A sends a full RESERVE with set SCOPING-Flag including RII and QSPEC
>> object,
>> and if the RESERVE will be treated as an updating, refreshing RESERVE, the
>> RESPONSE
>> will contain an INFO object with Success, Reservation succesful. In case of
>> new
>> installed state, the RESPONSE contains also an INFO object with Success,
>> Reservation
>> succesful.
>>
>> It would be helpful to make a difference between Reservation succesful and
>> Refresh
>> succesful. In case of Refresh succesful, there's no need to tear down the
>> reservation
>> on the old path. In case of Reservation succesful it might be. When link (1)
>> still
>> fails the teardown message would timeout in this example.
>>
>> What do you think?

It doesn't sound unreasonable.

Would the intention be to mandate a different behaviour? Or, should it 
be documented as a 'hint' (i.e. you might not want to do the tear if you 
get the 'successful refresh' response)? Or is no further information 
needed on how it might affect your processing?


Andrew

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



From nsis-bounces@ietf.org Wed Dec 20 10:44:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx3bm-0000vP-93; Wed, 20 Dec 2006 10:43:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx3bk-0000uj-EL
	for nsis@ietf.org; Wed, 20 Dec 2006 10:43:52 -0500
Received: from rsys002x.roke.co.uk ([193.118.201.109])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx3bg-0007rq-Ie
	for nsis@ietf.org; Wed, 20 Dec 2006 10:43:52 -0500
Received: from rsys005a.comm.ad.roke.co.uk (rsys005a [193.118.193.85])
	by rsys002x.roke.co.uk (8.13.1/8.13.1) with ESMTP id kBKFhOq4012067;
	Wed, 20 Dec 2006 15:43:24 GMT
Received: from [193.118.197.186] ([193.118.197.186]) by
	rsys005a.comm.ad.roke.co.uk with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Dec 2006 15:43:24 +0000
Message-ID: <45895A1C.7070807@roke.co.uk>
Date: Wed, 20 Dec 2006 15:43:24 +0000
From: Andrew McDonald <andrew.mcdonald@roke.co.uk>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
References: <Pine.LNX.4.64.0611211228220.5808@sbz-31.cs.Helsinki.FI>
	<Pine.LNX.4.64.0612061208010.6831@sbz-31.cs.Helsinki.FI>
	<4579A4FC.30601@cs.uni-goettingen.de>
	<Pine.LNX.4.64.0612102051220.11174@sbz-31.cs.Helsinki.FI>
In-Reply-To: <Pine.LNX.4.64.0612102051220.11174@sbz-31.cs.Helsinki.FI>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Dec 2006 15:43:24.0657 (UTC)
	FILETIME=[95BC3610:01C7244D]
X-MailScanner-roke-co-uk: Found to be clean
X-MailScanner-roke-co-uk-SpamCheck: 
X-MailScanner-From: andrew.mcdonald@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: Bernd Schloer <bschloer@cs.uni-goettingen.de>, nsis@ietf.org
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

Jukka MJ Manner wrote:
> I'm a bit lost in what you are talking about.
> 
> Andrew, Section 3.2.10 is basically your design, any comment?

So it is (though you can't pin the REPLACE flag on me). Comments below:

> On Fri, 8 Dec 2006, Bernd Schloer wrote:
>>
>> to my knowledge the case of section 3.2.10.2 is not covered in section 5.4.1,
>> where the Message Processing Rules of RESERVE Messages are explained. A sends
>> a RESERVE
>> to C while on Node A and C still reservation state for this Session ID is
>> installed. The
>> FlowID is unchanged, the MRI is unchanged, the REPLACE-Flag is not set, the
>> Session
>> ID is the same and the SII-Handle is unchanged for C.

It is covered in section 5.2.5.2. I can't see any obvious conflicts 
between 5.4.1 and 5.2.5.2. Are there any specific clarifying words that 
you think are required?

>> However there's a case for sessions with the REPLACE flag = 0 (does this mean
>> a received
>> RESERVE message where the REPLACE flag in the Common Header is not set?) where
>> it is
>> assumed that the QoS model includes directions to deal with resource sharing.
>> Adding a
>> reservation or taking the the maximum of two? Or more complex mathematical
>> operations?
>> What does this mean?

Hmm. I would not interpret REPLACE as involving any mathematical 
operation. My understanding was that it more simply means "in the case 
where there are two available paths, should there be a reservation on both".

>> But back to the rerouting problem. When A attempts to tear down the
>> reservation on the old
>> path by specifying explicit routing to the old peer with the related
>> SII-Handle, nothing
>> would happen, when link (1) still fails.

(I assume you are referring to figure 6)

Yes, I think that is the point.

The core of the discussion in 3.2.10.2 is:
- sometimes A may think that a route change has happened when it hasn't
- when that happens we don't want A to accidently tear down the state


Or am I missing something in your question?


Andrew

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



From nsis-bounces@ietf.org Wed Dec 20 11:13:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx449-0007jp-P7; Wed, 20 Dec 2006 11:13:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx448-0007iN-FZ
	for nsis@ietf.org; Wed, 20 Dec 2006 11:13:12 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx443-0004Fs-Se
	for nsis@ietf.org; Wed, 20 Dec 2006 11:13:12 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kBKGCr3l015103; Wed, 20 Dec 2006 17:13:01 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "=?iso-8859-1?Q?'Attila_B=E1der_=28IJ/ETH=29'?="
	<attila.bader@ericsson.com>, 
	"'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>, <nsis@ietf.org>
Subject: RE: [NSIS] RE: Why is QSPEC control information removed?
Date: Wed, 20 Dec 2006 17:12:48 +0100
Message-ID: <002201c72451$b662fd00$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <53CCFDD6E346CB43994852666C210E910F7386@esealmw116.eemea.ericsson.se>
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAULntzAAAvUVQAAKFscA
X-Spam-Score: 0.3 () FVGT_s_OBFU_Q1
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Wed, 20 Dec 2006 17:13:02 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b66a1e94d7d92973ece9e5da449ff80
Cc: 
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

Hi Attila and Jerry

Okay, but I would then like to introduce a sentence in Section 4.3.3 =
that
would say:
"Note that a QOS model could specify any QSPEC parameter that could be
considered
as a QoS model-specific control information parameter, which could=20
specify any other traffic handling directive."


Best Regards,
Georgios


=20

> -----Original Message-----
> From: Attila B=E1der (IJ/ETH) [mailto:attila.bader@ericsson.com]=20
> Sent: woensdag 20 december 2006 12:54
> To: Georgios Karagiannis; Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> Subject: [NSIS] RE: Why is QSPEC control information removed?
>=20
> Hi Georgios, Jerry,
>=20
> I think mostly just the name changed, the concept is still=20
> there. Control info is changed to traffic handling=20
> directives, see 4.3.3.. I assume that defining new control=20
> parameters or directives in QOS Model is still possible. The=20
> QoS Model should specify which QOS NSLP option is used, it=20
> also belongs to directives, is not it?
>=20
> Best regards, Attila
> =20
>=20
> >-----Original Message-----
> >From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> >Sent: Wednesday, December 20, 2006 10:59 AM
> >To: 'Ash, Gerald R (Jerry), ALABS'; nsis@ietf.org
> >Cc: Attila B=E1der (IJ/ETH)
> >Subject: Why is QSPEC control information removed?
> >
> >Hi Jerry
> >
> >I have not yet finished reviewing the QSEPC template draft,=20
> but I have=20
> >seen that you have removed the concept of QSPEC control information.
> >Why is that?
> >The concept of QSPEC control information has to remain.=20
> >
> >Best Regards,
> >Georgios
> >
> >
> >
> >=20
> >
> >> -----Original Message-----
> >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> >> Sent: donderdag 14 december 2006 1:00
> >> To: nsis@ietf.org
> >> Cc: Ash, Gerald R (Jerry), ALABS
> >> Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
> >>=20
> >> Hi All,
> >>=20
> >> The updated 'QoS NSLP QSPEC Template' I-D is available at=20
> >> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
> >>=20
> >> The main changes are as follows:
> >>=20
> >> 1. notion of QOSMs played down
> >>   o language e.g. 'QNSLP/QSPEC can signal for different=20
> QOSMs across
> >>     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
> >>     QNEs on the path to implement different data plane QoS=20
> mechanisms
> >>     that meet QSPEC constraints'
> >>   o a QOSM describes common capabilities among QNEs to act
> >>     consistently when requested to admit traffic & in treating
> >>     admitted traffic
> >>   o a QOSM ID need not be defined or signaled
> >>   o a QNE need not support any particular QOSM although a  QNI
> >>     normally includes a QSPEC corresponding to a particular
> >QOSM 2. a
> >> 'QOSM specification'
> >>   o still provides a rigorous specification of a QOSM &=20
> what it does
> >>   o documents how a QNE interprets & treats various=20
> elements in QSPEC
> >>   o can define additional QSPEC parameters 3. updated QOSM
> >definition:
> >>   a method to achieve QoS for a traffic flow, e.g., IntServ
> >>   Controlled Load; specifies what sub-set of QSPEC QoS=20
> constraints &
> >>   traffic handling directives a QNE implementing that QOSM=20
> is capable
> >>   of supporting & how resources will be managed by the RMF 4.=20
> >> QSPEC1/QSPEC2 semantics replaced with following semantics:
> >>   o source traffic description (mandatory to include by QNI &
> >>     mandatory to interpret by downstream QNEs)
> >>     > specified by traffic model (TMOD-1) parameter consisting of
> >>       rate (r), bucket size (b), peak rate (p), minimum=20
> policed unit
> >>      (m) (mathematically complete way to describe traffic source)
> >>     > bandwidth only set r=3Dp; b/m to large values (separate
> >>       bandwidth parameter not needed)
> >>     > TMOD-2 (optional to include)
> >>   o constraints (optional to include):
> >>     > Path Latency
> >>     > Path Jitter
> >>     > Path PLR
> >>     > Path PER
> >>     > Slack Term
> >>     > Priority (Preemption, Defending, Admission, RPH Priority)
> >>   o handling directives (optional to include):
> >>     > Excess Treatment
> >>   o traffic classifiers (optional to include):
> >>     > PHB Class (PHB class set by downstream QNE to tell QNI how to
> >>       mark traffic to ensure treatment committed by admission
> >>       control)
> >>     > DSTE Class Type
> >>     > Y.1541 QoS class
> >>   o eliminated:
> >>     > Bandwidth
> >>     > Ctot, Dtot, Csum, Dsum
> >> 5. concept of remapping QSPEC parameters eliminated 6.=20
> >> redefine 'interpret' a QSPEC parameter to mean 'must conform to
> >>    RFCs defining parameter & procedures (formerly called 'strictly
> >>    interpret')
> >> 7. concept of local QSPECs retained
> >>   o allows simpler control plane in a local domain
> >>   o edge nodes
> >>     > must interpret initiator QSPEC parameters
> >>     > can either initiate parallel session with local QSPEC or
> >>       define a local QSPEC with encapsulated initiator QSPEC
> >>   o local QSPEC interpreted by local domain QNEs
> >>   o local QSPEC must be consistent with initiator QSPEC
> >>     > e.g., RMD can initiate a local QSPEC that contains TMOD =3D
> >>       bandwidth (sets r=3Dp, b/m to large) 8. QSPEC flags modified =
as
> >> follows:
> >>   o QNI sets M flag for each QSPEC parameter it populates that must
> >>     be interpreted or reservation fails
> >>   o if M flag set
> >>     > downstream QNE MUST interpret parameter or reservation fails
> >>     > if QNE does not support parameter it sets N flag & rejects
> >>       reservation
> >>     > if QNE supports parameter but cannot meet parameter,=20
> it sets E
> >>       flag & rejects reservation
> >>   o if M flag not set
> >>     > downstream QNE SHOULD interpret parameter
> >>     > if QNE does not support parameter it sets the N flag &
> >>       optionally accepts or rejects reservation
> >>     > if QNE supports parameter but cannot meet parameter,=20
> it sets E
> >>       flag & optionally accepts or rejects reservation
> >>   o R (remapped parameter) flag & Q (non QOSM) flag eliminated 9.=20
> >> QSPEC type defined and registry established in IANA section.
> >>=20
> >> Please review the updated draft.
> >>=20
> >> Thanks,
> >> Jerry
> >>=20
> >> -----Original Message-----
> >> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> >> Sent: Wednesday, December 13, 2006 3:50 PM
> >> To: i-d-announce@ietf.org
> >> Cc: nsis@ietf.org
> >> Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
> >>=20
> >> A New Internet-Draft is available from the on-line Internet-Drafts=20
> >> directories.
> >> This draft is a work item of the Next Steps in Signaling
> >Working Group
> >> of the IETF.
> >>=20
> >> 	Title		: QoS NSLP QSPEC Template
> >> 	Author(s)	: J. Ash, et al.
> >> 	Filename	: draft-ietf-nsis-qspec-13.txt
> >> 	Pages		: 52
> >> 	Date		: 2006-12-13
> >> =09
> >> The QoS NSLP protocol is used to signal QoS reservations and is
> >>    independent of a specific QoS model (QOSM) such as IntServ or
> >>    DiffServ.  Rather, all information specific to a QOSM is=20
> >> encapsulated
> >>    in a separate object, the QSPEC.  This document defines=20
> a template
> >>    for the QSPEC including a number of QSPEC parameters.  The QSPEC
> >>    parameters provide a common language to be re-used in
> >several QOSMs
> >>    and thereby aim to ensure the extensibility and
> >interoperability of
> >>    QoS NSLP.  The node initiating the NSIS signaling adds an
> >initiator
> >>    QSPEC, which indicates the QSPEC parameters that must be=20
> >> interpreted
> >>    by the downstream nodes less the reservation fails, thereby=20
> >> ensuring
> >>    the intention of the NSIS initiator is preserved along the=20
> >> signaling
> >>    path.
> >>=20
> >> A URL for this Internet-Draft is:
> >> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt
> >>=20
> >> _______________________________________________
> >> nsis mailing list
> >> nsis@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/nsis
> >>=20
> >
> >
> >
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
>=20



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



From nsis-bounces@ietf.org Wed Dec 20 11:25:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx4Fu-0007PB-2R; Wed, 20 Dec 2006 11:25:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx4Fs-0007Os-Je
	for nsis@ietf.org; Wed, 20 Dec 2006 11:25:20 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx4Fo-00067q-JT
	for nsis@ietf.org; Wed, 20 Dec 2006 11:25:20 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kBKGOvNc015574; Wed, 20 Dec 2006 17:25:01 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>, <nsis@ietf.org>
Date: Wed, 20 Dec 2006 17:24:52 +0100
Message-ID: <002a01c72453$6394f360$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC805E@KCCLUST06EVS1.ugd.att.com>
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AAHf3VQ
X-Spam-Score: 0.4 () FVGT_s_OBFU_Q1,FVGT_u_HAS_2LETTERFLDR
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Wed, 20 Dec 2006 17:25:03 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: efb5d987e2484f3d9a304cc31a003441
Cc: 
Subject: [NSIS] Comment regarding section 5.1 of QSPEC tempalet draft
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

 Hi Jerry

Below is my comment_4 on the QSPEC template draft, 
(note that I am an author of QOS-NSLP draft):
What I am trying to say is that all the discussion that we 
have had regarding the encapsulation of the QSEPC object 
were associated with requiremet 5.4.2 of RFC 3726, see below:

-----------------
"5.4.2.  It SHOULD be Possible to Add and Remove Local Domain Information

   It SHOULD be possible to add and remove local scope elements.
   Compared to Requirement 5.3.5 this requirement does use the normal
   signaling process and message exchange for transporting local
   information.  For example, at the entrance to a domain, domain-
   specific information is added information is added, which is used in
   this domain only, and the information is removed again when a
   signaling message leaves the domain.  The motivation is in the
   economy of re-using the protocol for domain internal signaling of
   various information pieces.  Where additional information is needed
   within a particular domain, it should be possible to carry this at
   the same time as the end-to-end information.", from RFC 3726
------------------
Thus what I am saying is:
Please add the following sentence at the end of the first 
paragraph of Section 5.1.

"Note that when method b) is used, the encapsulation of the 
initiator QSPEC into a local QSPEC should also be possible when the local
QoS 
model needs to satisfy Requirement 5.4.2 specified in RFC 3726, by adding
and removing local 
QOSM-specific Control Information parameters on top of the initiator QSPEC."

Best Regards,
Georgios


> > Comment_4:
> > -------------
> > Section 5.1 Local QSPEC definition and processing
> > 
> > By reading this section it gives the impression that the 
> two methods 
> > a) and b) cannot be used by the same QoS model.
> > Method a): translate the
> >    initiator QSPEC into a local QSPEC and encapsulate the initiator
> >    QSPEC in the RESERVE message
> > Method b): b) tunnel the initiator QSPEC
> >    through the local domain and reserve resources by 
> generating a new
> >    RESERVE message through the local domain containing the local 
> > QSPEC.
> > 
> > Note that according to the discussions that we have had until now 
> > method a) should be able to be used in combination with 
> method b) by 
> > the same QoS model for the situation that the local QSPEC 
> encapsulates 
> > the initiator QSPEC in order to satisfy requirement 5.4.2 that is 
> > specified in RFC 3726, see:
> > http://www.ietf.org/rfc/rfc3726.txt
> > 
> > Please add the following sentence at the end of the first 
> paragraph of 
> > Section 5.1.
> > "Note that when method b) is used, the encapsulation of the 
> initiator 
> > QSPEC into a local QSPEC should also be possible when the local QoS 
> > model needs to satisfy Requirement
> > 5.4.2 specified in RFC 3726, by adding and removing local 
> > QOSM-specific Control Information parameters on top of the 
> initiator 
> > QSPEC."
> 
> Your comment here is not clear to me.  It would help to 
> provide an example to illustrate what you are trying to 
> accomplish.  It seems that you are trying to specify QoS-NSLP 
> functionality, rather than QSPEC functionality.  If so, that 
> functionality should be specified in the QoS-NSLP draft 
> rather than the QSPEC draft, perhaps the QoS-NSLP authors can comment.




> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> Sent: woensdag 20 december 2006 14:20
> To: Georgios Karagiannis; nsis@ietf.org
> Cc: Ash, Gerald R (Jerry), ALABS
> Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt 
> 
> Hi Georgios,
> 
> See below. 
> 
> > -----Original Message-----
> > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > Sent: Wednesday, December 20, 2006 5:26 AM
> > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > Subject: Comments on draft-ietf-nsis-qspec-13.txt
> > 
> > Hi Jerry
> > 
> > Here are my comments on draft-ietf-nsis-qspec-13.txt:
> > 
> > Comment_1:
> > --------------
> > Please reinclude the concept of QSPEC control information that was 
> > included in all previous versions of the QSPEC template draft.
> > In
> > 
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this 
> > concept was described in Section 5.1.
> 
> Please see previous email comment on QSPEC control information.
> 
> > Comment_2:
> > -----------
> > 
> > Section 6.1:
> > Please reintroduce the format that is required in order to 
> specify the 
> > QSPEC control information, see:
> > Section 7.1 of:
> > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
> 
> Please see previous email comment on QSPEC control information.
> 
> > Comment_3:
> > ----------
> > Section 4.1 :QoS Models
> > The definition of the QoS model is not complete. An 
> important sentence 
> > that was used in the previous version of the draft is removed.
> > Please add the following sentence to the definition of the 
> QoS Model 
> > (QOSM):
> > 
> > The same as described above have to be applied in this section.
> > After the following sentence:
> > 
> > "A QOSM specification MAY include the following:"
> > 
> > include the following bullet:
> > "- it specifies how to use QOS NSLP to signal for this QOSM"
> 
> That sentence was removed in Dave's proposed QOSM 
> re-definition, see 
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
> ml.  It was unclear what that sentence meant, QoS-NSLP 
> specifies how to signal, not QOSM specifications, so the 
> sentence was removed.  
> 
> I believe the sentence was intended to mean that when QoS 
> NSLP allows various options to be selected, a QOSM should be 
> able to determine which option is used.  For that purpose the 
> following sentence was added in Section 4.1:
> 
> "     A QOSM specification MAY include the following:
>      ...
>      - can state which QoS-NSLP options a QOSM wants to use, when
>      several options are available for a QOSM (e.g., local QSPEC to
>      either be a) tunneled or b) encapsulate initiator QSPEC)."
> 
> Also, to avoid any misinterpretation that QOSMs are free to 
> specify additional constraints, state machines, protocol 
> data, etc. for NSLP beyond that which is specific in the QoS 
> NSLP specification, the following was added to Section 4.1:
> 
> "  QOSMs affect the operation of the RMF in NSIS-capable nodes, the
>    information carried in QSPEC objects, and may under some
>    circumstances (e.g. aggregation) cause a separate NSLP 
> session to be
>    instantiated by having the RMF as a QNI. QOSMs all utilize 
> the common
>    data, state machines, and APIs of the underlying NSIS protocols and
>    are not expected to re-define or extend these in any way."
> 
> > Comment_4:
> > -------------
> > Section 5.1 Local QSPEC definition and processing
> > 
> > By reading this section it gives the impression that the 
> two methods 
> > a) and b) cannot be used by the same QoS model.
> > Method a): translate the
> >    initiator QSPEC into a local QSPEC and encapsulate the initiator
> >    QSPEC in the RESERVE message
> > Method b): b) tunnel the initiator QSPEC
> >    through the local domain and reserve resources by 
> generating a new
> >    RESERVE message through the local domain containing the local 
> > QSPEC.
> > 
> > Note that according to the discussions that we have had until now 
> > method a) should be able to be used in combination with 
> method b) by 
> > the same QoS model for the situation that the local QSPEC 
> encapsulates 
> > the initiator QSPEC in order to satisfy requirement 5.4.2 that is 
> > specified in RFC 3726, see:
> > http://www.ietf.org/rfc/rfc3726.txt
> > 
> > Please add the following sentence at the end of the first 
> paragraph of 
> > Section 5.1.
> > "Note that when method b) is used, the encapsulation of the 
> initiator 
> > QSPEC into a local QSPEC should also be possible when the local QoS 
> > model needs to satisfy Requirement
> > 5.4.2 specified in RFC 3726, by adding and removing local 
> > QOSM-specific Control Information parameters on top of the 
> initiator 
> > QSPEC."
> 
> Your comment here is not clear to me.  It would help to 
> provide an example to illustrate what you are trying to 
> accomplish.  It seems that you are trying to specify QoS-NSLP 
> functionality, rather than QSPEC functionality.  If so, that 
> functionality should be specified in the QoS-NSLP draft 
> rather than the QSPEC draft, perhaps the QoS-NSLP authors can comment.
> 
> > Comment_5:
> > -----------
> > Section 5.1, last paragraph:
> > 
> > Please change the following:
> > "For example, RMD can define a local QSPEC that contains TMOD = 
> > bandwidth (sets r=p, b/m to large)."
> > 
> > Into:
> > "For example, in RMD the TMOD parameters contained in the original 
> > initiator QSPEC are mapped into the equivalent TMOD parameter 
> > representing only the peak bandwidth in the local QSPEC."
> 
> OK with me.
> 
> > Comment_6:
> > -------------
> > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to be followed 
> > regarding the QSPEC control information are not given:
> > 
> > Please include the following paragraph at the end of this section:
> > "Regarding QSPEC Control Information, the default rule is that all
> >    QSPEC parameters that have been included in the RESERVE 
> message by
> >    the QNI are also included in the RESPONSE message by the 
> QNR with 
> > the
> >    value they had when arriving at the QNR.  When traveling in the
> >    RESPONSE message, all QSPEC Control Information parameters are
> >    read-only.  Note that a QOSM specification may define its own
> >    QOSM-specific Control Information parameters and 
> processing rules."
> 
> Please see previous email comment on QSPEC control information.
> 
> > Comment_7:
> > ------------
> > Section 6.1:
> > I do not understand the second sentence from the below two 
> sentences:
> > "N Flag: Not-supported QSPEC parameter flag (see Section 5.2.2).
> >            For QSPEC parameters the value of this flag is always 
> > zero."
> 
> Good catch, this is a typo, the sentence should be removed.
> 
> Thanks,
> Regards,
> Jerry
> 
> > 
> > ---------------------
> > 
> > Best Regards,
> > Georgios
> > 
> > > -----Original Message-----
> > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > > Sent: donderdag 14 december 2006 1:00
> > > To: nsis@ietf.org
> > > Cc: Ash, Gerald R (Jerry), ALABS
> > > Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
> > > 
> > > Hi All,
> > > 
> > > The updated 'QoS NSLP QSPEC Template' I-D is available at 
> > > http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
> > > 
> > > The main changes are as follows:
> > > 
> > > 1. notion of QOSMs played down
> > >   o language e.g. 'QNSLP/QSPEC can signal for different 
> QOSMs across
> > >     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
> > >     QNEs on the path to implement different data plane QoS
> > mechanisms
> > >     that meet QSPEC constraints'
> > >   o a QOSM describes common capabilities among QNEs to act
> > >     consistently when requested to admit traffic & in treating
> > >     admitted traffic
> > >   o a QOSM ID need not be defined or signaled
> > >   o a QNE need not support any particular QOSM although a  QNI
> > >     normally includes a QSPEC corresponding to a 
> particular QOSM 2. 
> > > a 'QOSM specification'
> > >   o still provides a rigorous specification of a QOSM & 
> what it does
> > >   o documents how a QNE interprets & treats various
> > elements in QSPEC
> > >   o can define additional QSPEC parameters 3. updated QOSM
> > definition:
> > >   a method to achieve QoS for a traffic flow, e.g., IntServ
> > >   Controlled Load; specifies what sub-set of QSPEC QoS 
> constraints &
> > >   traffic handling directives a QNE implementing that QOSM
> > is capable
> > >   of supporting & how resources will be managed by the RMF 4. 
> > > QSPEC1/QSPEC2 semantics replaced with following semantics:
> > >   o source traffic description (mandatory to include by QNI &
> > >     mandatory to interpret by downstream QNEs)
> > >     > specified by traffic model (TMOD-1) parameter consisting of
> > >       rate (r), bucket size (b), peak rate (p), minimum 
> policed unit
> > >      (m) (mathematically complete way to describe traffic source)
> > >     > bandwidth only set r=p; b/m to large values (separate
> > >       bandwidth parameter not needed)
> > >     > TMOD-2 (optional to include)
> > >   o constraints (optional to include):
> > >     > Path Latency
> > >     > Path Jitter
> > >     > Path PLR
> > >     > Path PER
> > >     > Slack Term
> > >     > Priority (Preemption, Defending, Admission, RPH Priority)
> > >   o handling directives (optional to include):
> > >     > Excess Treatment
> > >   o traffic classifiers (optional to include):
> > >     > PHB Class (PHB class set by downstream QNE to tell 
> QNI how to
> > >       mark traffic to ensure treatment committed by admission
> > >       control)
> > >     > DSTE Class Type
> > >     > Y.1541 QoS class
> > >   o eliminated:
> > >     > Bandwidth
> > >     > Ctot, Dtot, Csum, Dsum
> > > 5. concept of remapping QSPEC parameters eliminated 6. 
> > > redefine 'interpret' a QSPEC parameter to mean 'must conform to
> > >    RFCs defining parameter & procedures (formerly called 'strictly
> > >    interpret')
> > > 7. concept of local QSPECs retained
> > >   o allows simpler control plane in a local domain
> > >   o edge nodes
> > >     > must interpret initiator QSPEC parameters
> > >     > can either initiate parallel session with local QSPEC or
> > >       define a local QSPEC with encapsulated initiator QSPEC
> > >   o local QSPEC interpreted by local domain QNEs
> > >   o local QSPEC must be consistent with initiator QSPEC
> > >     > e.g., RMD can initiate a local QSPEC that contains TMOD =
> > >       bandwidth (sets r=p, b/m to large) 8. QSPEC flags 
> modified as 
> > > follows:
> > >   o QNI sets M flag for each QSPEC parameter it populates 
> that must
> > >     be interpreted or reservation fails
> > >   o if M flag set
> > >     > downstream QNE MUST interpret parameter or reservation fails
> > >     > if QNE does not support parameter it sets N flag & rejects
> > >       reservation
> > >     > if QNE supports parameter but cannot meet 
> parameter, it sets E
> > >       flag & rejects reservation
> > >   o if M flag not set
> > >     > downstream QNE SHOULD interpret parameter
> > >     > if QNE does not support parameter it sets the N flag &
> > >       optionally accepts or rejects reservation
> > >     > if QNE supports parameter but cannot meet 
> parameter, it sets E
> > >       flag & optionally accepts or rejects reservation
> > >   o R (remapped parameter) flag & Q (non QOSM) flag eliminated 9. 
> > > QSPEC type defined and registry established in IANA section.
> > > 
> > > Please review the updated draft.
> > > 
> > > Thanks,
> > > Jerry
> 



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



From nsis-bounces@ietf.org Wed Dec 20 11:31:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx4Ll-0001Yz-2p; Wed, 20 Dec 2006 11:31:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx4Lk-0001Yr-1n
	for nsis@ietf.org; Wed, 20 Dec 2006 11:31:24 -0500
Received: from mclmx.mail.saic.com ([149.8.64.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx4Li-000725-IO
	for nsis@ietf.org; Wed, 20 Dec 2006 11:31:24 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx.mail.saic.com; Wed, 20 Dec 2006 11:31:07 -0500
Received: from 0015-ITS-EXBH01.us.saic.com ([10.43.229.18])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006122011310616951 ; Wed, 20 Dec 2006 11:31:06 -0500
Received: from 0591-ITS-EXMP02.us.saic.com ([10.42.81.248]) by
	0015-ITS-EXBH01.us.saic.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Dec 2006 11:31:06 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] RE: Why is QSPEC control information removed?
Date: Wed, 20 Dec 2006 11:31:06 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426230F18@0591-ITS-EXMP02.us.saic.com>
In-Reply-To: <002201c72451$b662fd00$4c0d5982@dynamic.ewi.utwente.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] RE: Why is QSPEC control information removed?
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAULntzAAAvUVQAAKFscAAABg+rA=
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: "Georgios Karagiannis" <karagian@cs.utwente.nl>,
	=?iso-8859-1?Q?Attila_B=E1der_=28IJ/ETH=29?= <attila.bader@ericsson.com>,
	"Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, <nsis@ietf.org>
X-OriginalArrivalTime: 20 Dec 2006 16:31:06.0832 (UTC)
	FILETIME=[3FB97500:01C72454]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dd7e0c3fd18d19cffdd4de99a114001d
Cc: 
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

Georgios and all:

We have a fundamental problem here if those wordings are used as =
suggested by Georgios. We are suggesting to add one more sentence as =
follows in addition to Georgios's:

"[..... Georgios sentence + this one...] The QOS model-specific QSPEC =
parameters SHALL be specified in a separate QOSM draft/RFC for each QOS =
model as this QSPEC RFC deals with the general e2e-QSPEC parameter."

Best regards,
Raddhika

-----Original Message-----
From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of =
Georgios Karagiannis
Sent: Wednesday, December 20, 2006 11:13 AM
To: 'Attila B=E1der (IJ/ETH)'; 'Ash, Gerald R (Jerry), ALABS'; =
nsis@ietf.org
Subject: RE: [NSIS] RE: Why is QSPEC control information removed?

Hi Attila and Jerry

Okay, but I would then like to introduce a sentence in Section 4.3.3 =
that
would say:
"Note that a QOS model could specify any QSPEC parameter that could be
considered
as a QoS model-specific control information parameter, which could=20
specify any other traffic handling directive."


Best Regards,
Georgios


=20

> -----Original Message-----
> From: Attila B=E1der (IJ/ETH) [mailto:attila.bader@ericsson.com]=20
> Sent: woensdag 20 december 2006 12:54
> To: Georgios Karagiannis; Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> Subject: [NSIS] RE: Why is QSPEC control information removed?
>=20
> Hi Georgios, Jerry,
>=20
> I think mostly just the name changed, the concept is still=20
> there. Control info is changed to traffic handling=20
> directives, see 4.3.3.. I assume that defining new control=20
> parameters or directives in QOS Model is still possible. The=20
> QoS Model should specify which QOS NSLP option is used, it=20
> also belongs to directives, is not it?
>=20
> Best regards, Attila
> =20
>=20
> >-----Original Message-----
> >From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> >Sent: Wednesday, December 20, 2006 10:59 AM
> >To: 'Ash, Gerald R (Jerry), ALABS'; nsis@ietf.org
> >Cc: Attila B=E1der (IJ/ETH)
> >Subject: Why is QSPEC control information removed?
> >
> >Hi Jerry
> >
> >I have not yet finished reviewing the QSEPC template draft,=20
> but I have=20
> >seen that you have removed the concept of QSPEC control information.
> >Why is that?
> >The concept of QSPEC control information has to remain.=20
> >
> >Best Regards,
> >Georgios
> >
> >
> >
> >=20
> >
> >> -----Original Message-----
> >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> >> Sent: donderdag 14 december 2006 1:00
> >> To: nsis@ietf.org
> >> Cc: Ash, Gerald R (Jerry), ALABS
> >> Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
> >>=20
> >> Hi All,
> >>=20
> >> The updated 'QoS NSLP QSPEC Template' I-D is available at=20
> >> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
> >>=20
> >> The main changes are as follows:
> >>=20
> >> 1. notion of QOSMs played down
> >>   o language e.g. 'QNSLP/QSPEC can signal for different=20
> QOSMs across
> >>     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
> >>     QNEs on the path to implement different data plane QoS=20
> mechanisms
> >>     that meet QSPEC constraints'
> >>   o a QOSM describes common capabilities among QNEs to act
> >>     consistently when requested to admit traffic & in treating
> >>     admitted traffic
> >>   o a QOSM ID need not be defined or signaled
> >>   o a QNE need not support any particular QOSM although a  QNI
> >>     normally includes a QSPEC corresponding to a particular
> >QOSM 2. a
> >> 'QOSM specification'
> >>   o still provides a rigorous specification of a QOSM &=20
> what it does
> >>   o documents how a QNE interprets & treats various=20
> elements in QSPEC
> >>   o can define additional QSPEC parameters 3. updated QOSM
> >definition:
> >>   a method to achieve QoS for a traffic flow, e.g., IntServ
> >>   Controlled Load; specifies what sub-set of QSPEC QoS=20
> constraints &
> >>   traffic handling directives a QNE implementing that QOSM=20
> is capable
> >>   of supporting & how resources will be managed by the RMF 4.=20
> >> QSPEC1/QSPEC2 semantics replaced with following semantics:
> >>   o source traffic description (mandatory to include by QNI &
> >>     mandatory to interpret by downstream QNEs)
> >>     > specified by traffic model (TMOD-1) parameter consisting of
> >>       rate (r), bucket size (b), peak rate (p), minimum=20
> policed unit
> >>      (m) (mathematically complete way to describe traffic source)
> >>     > bandwidth only set r=3Dp; b/m to large values (separate
> >>       bandwidth parameter not needed)
> >>     > TMOD-2 (optional to include)
> >>   o constraints (optional to include):
> >>     > Path Latency
> >>     > Path Jitter
> >>     > Path PLR
> >>     > Path PER
> >>     > Slack Term
> >>     > Priority (Preemption, Defending, Admission, RPH Priority)
> >>   o handling directives (optional to include):
> >>     > Excess Treatment
> >>   o traffic classifiers (optional to include):
> >>     > PHB Class (PHB class set by downstream QNE to tell QNI how to
> >>       mark traffic to ensure treatment committed by admission
> >>       control)
> >>     > DSTE Class Type
> >>     > Y.1541 QoS class
> >>   o eliminated:
> >>     > Bandwidth
> >>     > Ctot, Dtot, Csum, Dsum
> >> 5. concept of remapping QSPEC parameters eliminated 6.=20
> >> redefine 'interpret' a QSPEC parameter to mean 'must conform to
> >>    RFCs defining parameter & procedures (formerly called 'strictly
> >>    interpret')
> >> 7. concept of local QSPECs retained
> >>   o allows simpler control plane in a local domain
> >>   o edge nodes
> >>     > must interpret initiator QSPEC parameters
> >>     > can either initiate parallel session with local QSPEC or
> >>       define a local QSPEC with encapsulated initiator QSPEC
> >>   o local QSPEC interpreted by local domain QNEs
> >>   o local QSPEC must be consistent with initiator QSPEC
> >>     > e.g., RMD can initiate a local QSPEC that contains TMOD =3D
> >>       bandwidth (sets r=3Dp, b/m to large) 8. QSPEC flags modified =
as
> >> follows:
> >>   o QNI sets M flag for each QSPEC parameter it populates that must
> >>     be interpreted or reservation fails
> >>   o if M flag set
> >>     > downstream QNE MUST interpret parameter or reservation fails
> >>     > if QNE does not support parameter it sets N flag & rejects
> >>       reservation
> >>     > if QNE supports parameter but cannot meet parameter,=20
> it sets E
> >>       flag & rejects reservation
> >>   o if M flag not set
> >>     > downstream QNE SHOULD interpret parameter
> >>     > if QNE does not support parameter it sets the N flag &
> >>       optionally accepts or rejects reservation
> >>     > if QNE supports parameter but cannot meet parameter,=20
> it sets E
> >>       flag & optionally accepts or rejects reservation
> >>   o R (remapped parameter) flag & Q (non QOSM) flag eliminated 9.=20
> >> QSPEC type defined and registry established in IANA section.
> >>=20
> >> Please review the updated draft.
> >>=20
> >> Thanks,
> >> Jerry
> >>=20
> >> -----Original Message-----
> >> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> >> Sent: Wednesday, December 13, 2006 3:50 PM
> >> To: i-d-announce@ietf.org
> >> Cc: nsis@ietf.org
> >> Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
> >>=20
> >> A New Internet-Draft is available from the on-line Internet-Drafts=20
> >> directories.
> >> This draft is a work item of the Next Steps in Signaling
> >Working Group
> >> of the IETF.
> >>=20
> >> 	Title		: QoS NSLP QSPEC Template
> >> 	Author(s)	: J. Ash, et al.
> >> 	Filename	: draft-ietf-nsis-qspec-13.txt
> >> 	Pages		: 52
> >> 	Date		: 2006-12-13
> >> =09
> >> The QoS NSLP protocol is used to signal QoS reservations and is
> >>    independent of a specific QoS model (QOSM) such as IntServ or
> >>    DiffServ.  Rather, all information specific to a QOSM is=20
> >> encapsulated
> >>    in a separate object, the QSPEC.  This document defines=20
> a template
> >>    for the QSPEC including a number of QSPEC parameters.  The QSPEC
> >>    parameters provide a common language to be re-used in
> >several QOSMs
> >>    and thereby aim to ensure the extensibility and
> >interoperability of
> >>    QoS NSLP.  The node initiating the NSIS signaling adds an
> >initiator
> >>    QSPEC, which indicates the QSPEC parameters that must be=20
> >> interpreted
> >>    by the downstream nodes less the reservation fails, thereby=20
> >> ensuring
> >>    the intention of the NSIS initiator is preserved along the=20
> >> signaling
> >>    path.
> >>=20
> >> A URL for this Internet-Draft is:
> >> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt
> >>=20
> >> _______________________________________________
> >> nsis mailing list
> >> nsis@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/nsis
> >>=20
> >
> >
> >
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
>=20



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

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



From nsis-bounces@ietf.org Wed Dec 20 12:08:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx4ve-0005Di-TD; Wed, 20 Dec 2006 12:08:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx4vd-0005DW-Vy
	for nsis@ietf.org; Wed, 20 Dec 2006 12:08:29 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx4vd-0004ZR-Bf
	for nsis@ietf.org; Wed, 20 Dec 2006 12:08:29 -0500
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-4.cisco.com with ESMTP; 20 Dec 2006 09:08:29 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id kBKH8SSS017790; 
	Wed, 20 Dec 2006 09:08:28 -0800
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kBKH8SZg015663;
	Wed, 20 Dec 2006 09:08:28 -0800 (PST)
Received: from [10.32.245.152] ([10.32.245.152])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id kBKGqX09011933;
	Wed, 20 Dec 2006 08:52:33 -0800
In-Reply-To: <002201c72451$b662fd00$4c0d5982@dynamic.ewi.utwente.nl>
References: <002201c72451$b662fd00$4c0d5982@dynamic.ewi.utwente.nl>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <BED43802-A19A-496F-B5F9-0C92EBA6562F@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: David R Oran <oran@cisco.com>
Subject: Re: [NSIS] RE: Why is QSPEC control information removed?
Date: Wed, 20 Dec 2006 12:08:25 -0500
To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
X-Mailer: Apple Mail (2.752.2)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=9223; t=1166634508;
	x=1167498508; c=relaxed/simple; s=sjdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[NSIS]=20RE=3A=20Why=20is=20QSPEC=20control=20informa
	tion=20removed? |Sender:=20;
	bh=flv3/NVygRqXIbVaUBGtNA4GeKQj5hoHUTPwN9R67iM=;
	b=O1eHbEkkqguYIG+T7B0DmLwUZCvrdyjUpDGqmw1jLZ0dLuyB3RWbRcpSrs7ENAT8mzkDN/YJ
	UNw/BUcvaO3no/pAwKQ+WRX/OFR4Movff2/hur4f1jPBpNwS4IOUaUcF;
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=9223; t=1166633554;
	x=1167497554; c=relaxed/simple; s=oregon;
	h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; 
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[NSIS]=20RE=3A=20Why=20is=20QSPEC=20control=20informa
	tion=20removed? |Sender:=20
	|To:=20=22Georgios=20Karagiannis=22=20<karagian@cs.utwente.nl>;
	bh=flv3/NVygRqXIbVaUBGtNA4GeKQj5hoHUTPwN9R67iM=;
	b=fOjnzV/bGqQNEIv2cORShagydute9Xt+M79bADdgEy8Nzt5sAa0YPnJiiDXj9lEoAgx+j0E3
	vOoRejW3TCMLoDx4HefKD5VDVNF0WWhnE2hYztP/4UVr5qoxoRuLn6g6;
Authentication-Results: sj-dkim-1; header.From=oran@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim1002 verified; ); 
	header.From=oran@cisco.com; dkim=pass (
	sig from cisco.com/oregon verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6907f330301e69261fa73bed91449a20
Cc: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>, nsis@ietf.org,
	=?ISO-8859-1?Q? 'Attila_B=E1der_=28IJ/ETH=29' ?=
	<attila.bader@ericsson.com>
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


On Dec 20, 2006, at 11:12 AM, Georgios Karagiannis wrote:

> Hi Attila and Jerry
>
> Okay, but I would then like to introduce a sentence in Section =20
> 4.3.3 that
> would say:
> "Note that a QOS model could specify any QSPEC parameter that could be
> considered
> as a QoS model-specific control information parameter, which could
> specify any other traffic handling directive."
>
I have a hard time understanding what this is actually saying, as =20
opposed to what it is trying to say, which I believe is that QOSMs =20
used in various domains may wish to extend the QSPEC in various ways, =20=

and those extensions may include any category of qspec parameter.

How about:
"QoSMs are free, subject to IANA registration and review rules, to =20
extend QSPECs by adding parameters of any of the kinds supported by =20
the standard QSPEC. This includes traffic description parameters, =20
constraint parameters and handling directives. QoSMs are not =20
permitted, however, to reinterpret or redefine the standard QSPEC =20
parameters specified in this document"

Dave.


>
> Best Regards,
> Georgios
>
>
>
>
>> -----Original Message-----
>> From: Attila B=E1der (IJ/ETH) [mailto:attila.bader@ericsson.com]
>> Sent: woensdag 20 december 2006 12:54
>> To: Georgios Karagiannis; Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>> Subject: [NSIS] RE: Why is QSPEC control information removed?
>>
>> Hi Georgios, Jerry,
>>
>> I think mostly just the name changed, the concept is still
>> there. Control info is changed to traffic handling
>> directives, see 4.3.3.. I assume that defining new control
>> parameters or directives in QOS Model is still possible. The
>> QoS Model should specify which QOS NSLP option is used, it
>> also belongs to directives, is not it?
>>
>> Best regards, Attila
>>
>>
>>> -----Original Message-----
>>> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>>> Sent: Wednesday, December 20, 2006 10:59 AM
>>> To: 'Ash, Gerald R (Jerry), ALABS'; nsis@ietf.org
>>> Cc: Attila B=E1der (IJ/ETH)
>>> Subject: Why is QSPEC control information removed?
>>>
>>> Hi Jerry
>>>
>>> I have not yet finished reviewing the QSEPC template draft,
>> but I have
>>> seen that you have removed the concept of QSPEC control information.
>>> Why is that?
>>> The concept of QSPEC control information has to remain.
>>>
>>> Best Regards,
>>> Georgios
>>>
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>>>> Sent: donderdag 14 december 2006 1:00
>>>> To: nsis@ietf.org
>>>> Cc: Ash, Gerald R (Jerry), ALABS
>>>> Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
>>>>
>>>> Hi All,
>>>>
>>>> The updated 'QoS NSLP QSPEC Template' I-D is available at
>>>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
>>>>
>>>> The main changes are as follows:
>>>>
>>>> 1. notion of QOSMs played down
>>>>   o language e.g. 'QNSLP/QSPEC can signal for different
>> QOSMs across
>>>>     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
>>>>     QNEs on the path to implement different data plane QoS
>> mechanisms
>>>>     that meet QSPEC constraints'
>>>>   o a QOSM describes common capabilities among QNEs to act
>>>>     consistently when requested to admit traffic & in treating
>>>>     admitted traffic
>>>>   o a QOSM ID need not be defined or signaled
>>>>   o a QNE need not support any particular QOSM although a  QNI
>>>>     normally includes a QSPEC corresponding to a particular
>>> QOSM 2. a
>>>> 'QOSM specification'
>>>>   o still provides a rigorous specification of a QOSM &
>> what it does
>>>>   o documents how a QNE interprets & treats various
>> elements in QSPEC
>>>>   o can define additional QSPEC parameters 3. updated QOSM
>>> definition:
>>>>   a method to achieve QoS for a traffic flow, e.g., IntServ
>>>>   Controlled Load; specifies what sub-set of QSPEC QoS
>> constraints &
>>>>   traffic handling directives a QNE implementing that QOSM
>> is capable
>>>>   of supporting & how resources will be managed by the RMF 4.
>>>> QSPEC1/QSPEC2 semantics replaced with following semantics:
>>>>   o source traffic description (mandatory to include by QNI &
>>>>     mandatory to interpret by downstream QNEs)
>>>>> specified by traffic model (TMOD-1) parameter consisting of
>>>>       rate (r), bucket size (b), peak rate (p), minimum
>> policed unit
>>>>      (m) (mathematically complete way to describe traffic source)
>>>>> bandwidth only set r=3Dp; b/m to large values (separate
>>>>       bandwidth parameter not needed)
>>>>> TMOD-2 (optional to include)
>>>>   o constraints (optional to include):
>>>>> Path Latency
>>>>> Path Jitter
>>>>> Path PLR
>>>>> Path PER
>>>>> Slack Term
>>>>> Priority (Preemption, Defending, Admission, RPH Priority)
>>>>   o handling directives (optional to include):
>>>>> Excess Treatment
>>>>   o traffic classifiers (optional to include):
>>>>> PHB Class (PHB class set by downstream QNE to tell QNI how to
>>>>       mark traffic to ensure treatment committed by admission
>>>>       control)
>>>>> DSTE Class Type
>>>>> Y.1541 QoS class
>>>>   o eliminated:
>>>>> Bandwidth
>>>>> Ctot, Dtot, Csum, Dsum
>>>> 5. concept of remapping QSPEC parameters eliminated 6.
>>>> redefine 'interpret' a QSPEC parameter to mean 'must conform to
>>>>    RFCs defining parameter & procedures (formerly called 'strictly
>>>>    interpret')
>>>> 7. concept of local QSPECs retained
>>>>   o allows simpler control plane in a local domain
>>>>   o edge nodes
>>>>> must interpret initiator QSPEC parameters
>>>>> can either initiate parallel session with local QSPEC or
>>>>       define a local QSPEC with encapsulated initiator QSPEC
>>>>   o local QSPEC interpreted by local domain QNEs
>>>>   o local QSPEC must be consistent with initiator QSPEC
>>>>> e.g., RMD can initiate a local QSPEC that contains TMOD =3D
>>>>       bandwidth (sets r=3Dp, b/m to large) 8. QSPEC flags modified =
as
>>>> follows:
>>>>   o QNI sets M flag for each QSPEC parameter it populates that must
>>>>     be interpreted or reservation fails
>>>>   o if M flag set
>>>>> downstream QNE MUST interpret parameter or reservation fails
>>>>> if QNE does not support parameter it sets N flag & rejects
>>>>       reservation
>>>>> if QNE supports parameter but cannot meet parameter,
>> it sets E
>>>>       flag & rejects reservation
>>>>   o if M flag not set
>>>>> downstream QNE SHOULD interpret parameter
>>>>> if QNE does not support parameter it sets the N flag &
>>>>       optionally accepts or rejects reservation
>>>>> if QNE supports parameter but cannot meet parameter,
>> it sets E
>>>>       flag & optionally accepts or rejects reservation
>>>>   o R (remapped parameter) flag & Q (non QOSM) flag eliminated 9.
>>>> QSPEC type defined and registry established in IANA section.
>>>>
>>>> Please review the updated draft.
>>>>
>>>> Thanks,
>>>> Jerry
>>>>
>>>> -----Original Message-----
>>>> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>>>> Sent: Wednesday, December 13, 2006 3:50 PM
>>>> To: i-d-announce@ietf.org
>>>> Cc: nsis@ietf.org
>>>> Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
>>>>
>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>> directories.
>>>> This draft is a work item of the Next Steps in Signaling
>>> Working Group
>>>> of the IETF.
>>>>
>>>> 	Title		: QoS NSLP QSPEC Template
>>>> 	Author(s)	: J. Ash, et al.
>>>> 	Filename	: draft-ietf-nsis-qspec-13.txt
>>>> 	Pages		: 52
>>>> 	Date		: 2006-12-13
>>>> =09
>>>> The QoS NSLP protocol is used to signal QoS reservations and is
>>>>    independent of a specific QoS model (QOSM) such as IntServ or
>>>>    DiffServ.  Rather, all information specific to a QOSM is
>>>> encapsulated
>>>>    in a separate object, the QSPEC.  This document defines
>> a template
>>>>    for the QSPEC including a number of QSPEC parameters.  The QSPEC
>>>>    parameters provide a common language to be re-used in
>>> several QOSMs
>>>>    and thereby aim to ensure the extensibility and
>>> interoperability of
>>>>    QoS NSLP.  The node initiating the NSIS signaling adds an
>>> initiator
>>>>    QSPEC, which indicates the QSPEC parameters that must be
>>>> interpreted
>>>>    by the downstream nodes less the reservation fails, thereby
>>>> ensuring
>>>>    the intention of the NSIS initiator is preserved along the
>>>> signaling
>>>>    path.
>>>>
>>>> A URL for this Internet-Draft is:
>>>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt
>>>>
>>>> _______________________________________________
>>>> nsis mailing list
>>>> nsis@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/nsis
>>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>
>
>
>
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

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



From nsis-bounces@ietf.org Wed Dec 20 12:19:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx562-0001or-8Z; Wed, 20 Dec 2006 12:19:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx560-0001oc-HC
	for nsis@ietf.org; Wed, 20 Dec 2006 12:19:12 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx55z-0006XT-Tr
	for nsis@ietf.org; Wed, 20 Dec 2006 12:19:12 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kBKHIsVF017160; Wed, 20 Dec 2006 18:19:05 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'David R Oran'" <oran@cisco.com>
Subject: RE: [NSIS] RE: Why is QSPEC control information removed?
Date: Wed, 20 Dec 2006 18:18:50 +0100
Message-ID: <004201c7245a$f00aba80$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <BED43802-A19A-496F-B5F9-0C92EBA6562F@cisco.com>
Thread-Index: AcckWXxVeQdL9P5bQ32I0W3+OB4P1gAAVPbA
X-Spam-Score: 0.3 () FVGT_s_OBFU_Q1
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Wed, 20 Dec 2006 18:19:06 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 453b1bfcf0292bffe4cab90ba115f503
Cc: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>, nsis@ietf.org,
	=?iso-8859-1?Q?''Attila_B=E1der_=28IJ/ETH=29'_'?=
	<attila.bader@ericsson.com>
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

Hi Dave

Thank you!
I agree with the provided text!

Best Regards,
Georgios
=20

> -----Original Message-----
> From: David R Oran [mailto:oran@cisco.com]=20
> Sent: woensdag 20 december 2006 18:08
> To: Georgios Karagiannis
> Cc: 'Attila B=E1der (IJ/ETH)' ; 'Ash, Gerald R (Jerry), ALABS';=20
> nsis@ietf.org
> Subject: Re: [NSIS] RE: Why is QSPEC control information removed?
>=20
>=20
> On Dec 20, 2006, at 11:12 AM, Georgios Karagiannis wrote:
>=20
> > Hi Attila and Jerry
> >
> > Okay, but I would then like to introduce a sentence in Section
> > 4.3.3 that
> > would say:
> > "Note that a QOS model could specify any QSPEC parameter=20
> that could be=20
> > considered as a QoS model-specific control information parameter,=20
> > which could specify any other traffic handling directive."
> >
> I have a hard time understanding what this is actually=20
> saying, as opposed to what it is trying to say, which I=20
> believe is that QOSMs used in various domains may wish to=20
> extend the QSPEC in various ways, and those extensions may=20
> include any category of qspec parameter.
>=20
> How about:
> "QoSMs are free, subject to IANA registration and review=20
> rules, to extend QSPECs by adding parameters of any of the=20
> kinds supported by the standard QSPEC. This includes traffic=20
> description parameters, constraint parameters and handling=20
> directives. QoSMs are not permitted, however, to reinterpret=20
> or redefine the standard QSPEC parameters specified in this document"
>=20
> Dave.
>=20
>=20
> >
> > Best Regards,
> > Georgios
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: Attila B=E1der (IJ/ETH) [mailto:attila.bader@ericsson.com]
> >> Sent: woensdag 20 december 2006 12:54
> >> To: Georgios Karagiannis; Ash, Gerald R (Jerry), ALABS;=20
> nsis@ietf.org
> >> Subject: [NSIS] RE: Why is QSPEC control information removed?
> >>
> >> Hi Georgios, Jerry,
> >>
> >> I think mostly just the name changed, the concept is still there.=20
> >> Control info is changed to traffic handling directives,=20
> see 4.3.3.. I=20
> >> assume that defining new control parameters or directives in QOS=20
> >> Model is still possible. The QoS Model should specify=20
> which QOS NSLP=20
> >> option is used, it also belongs to directives, is not it?
> >>
> >> Best regards, Attila
> >>
> >>
> >>> -----Original Message-----
> >>> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> >>> Sent: Wednesday, December 20, 2006 10:59 AM
> >>> To: 'Ash, Gerald R (Jerry), ALABS'; nsis@ietf.org
> >>> Cc: Attila B=E1der (IJ/ETH)
> >>> Subject: Why is QSPEC control information removed?
> >>>
> >>> Hi Jerry
> >>>
> >>> I have not yet finished reviewing the QSEPC template draft,
> >> but I have
> >>> seen that you have removed the concept of QSPEC control=20
> information.
> >>> Why is that?
> >>> The concept of QSPEC control information has to remain.
> >>>
> >>> Best Regards,
> >>> Georgios
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> >>>> Sent: donderdag 14 december 2006 1:00
> >>>> To: nsis@ietf.org
> >>>> Cc: Ash, Gerald R (Jerry), ALABS
> >>>> Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
> >>>>
> >>>> Hi All,
> >>>>
> >>>> The updated 'QoS NSLP QSPEC Template' I-D is available at=20
> >>>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
> >>>>
> >>>> The main changes are as follows:
> >>>>
> >>>> 1. notion of QOSMs played down
> >>>>   o language e.g. 'QNSLP/QSPEC can signal for different
> >> QOSMs across
> >>>>     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
> >>>>     QNEs on the path to implement different data plane QoS
> >> mechanisms
> >>>>     that meet QSPEC constraints'
> >>>>   o a QOSM describes common capabilities among QNEs to act
> >>>>     consistently when requested to admit traffic & in treating
> >>>>     admitted traffic
> >>>>   o a QOSM ID need not be defined or signaled
> >>>>   o a QNE need not support any particular QOSM although a  QNI
> >>>>     normally includes a QSPEC corresponding to a particular
> >>> QOSM 2. a
> >>>> 'QOSM specification'
> >>>>   o still provides a rigorous specification of a QOSM &
> >> what it does
> >>>>   o documents how a QNE interprets & treats various
> >> elements in QSPEC
> >>>>   o can define additional QSPEC parameters 3. updated QOSM
> >>> definition:
> >>>>   a method to achieve QoS for a traffic flow, e.g., IntServ
> >>>>   Controlled Load; specifies what sub-set of QSPEC QoS
> >> constraints &
> >>>>   traffic handling directives a QNE implementing that QOSM
> >> is capable
> >>>>   of supporting & how resources will be managed by the RMF 4.
> >>>> QSPEC1/QSPEC2 semantics replaced with following semantics:
> >>>>   o source traffic description (mandatory to include by QNI &
> >>>>     mandatory to interpret by downstream QNEs)
> >>>>> specified by traffic model (TMOD-1) parameter consisting of
> >>>>       rate (r), bucket size (b), peak rate (p), minimum
> >> policed unit
> >>>>      (m) (mathematically complete way to describe traffic source)
> >>>>> bandwidth only set r=3Dp; b/m to large values (separate
> >>>>       bandwidth parameter not needed)
> >>>>> TMOD-2 (optional to include)
> >>>>   o constraints (optional to include):
> >>>>> Path Latency
> >>>>> Path Jitter
> >>>>> Path PLR
> >>>>> Path PER
> >>>>> Slack Term
> >>>>> Priority (Preemption, Defending, Admission, RPH Priority)
> >>>>   o handling directives (optional to include):
> >>>>> Excess Treatment
> >>>>   o traffic classifiers (optional to include):
> >>>>> PHB Class (PHB class set by downstream QNE to tell QNI how to
> >>>>       mark traffic to ensure treatment committed by admission
> >>>>       control)
> >>>>> DSTE Class Type
> >>>>> Y.1541 QoS class
> >>>>   o eliminated:
> >>>>> Bandwidth
> >>>>> Ctot, Dtot, Csum, Dsum
> >>>> 5. concept of remapping QSPEC parameters eliminated 6.
> >>>> redefine 'interpret' a QSPEC parameter to mean 'must conform to
> >>>>    RFCs defining parameter & procedures (formerly called=20
> 'strictly
> >>>>    interpret')
> >>>> 7. concept of local QSPECs retained
> >>>>   o allows simpler control plane in a local domain
> >>>>   o edge nodes
> >>>>> must interpret initiator QSPEC parameters can either initiate=20
> >>>>> parallel session with local QSPEC or
> >>>>       define a local QSPEC with encapsulated initiator QSPEC
> >>>>   o local QSPEC interpreted by local domain QNEs
> >>>>   o local QSPEC must be consistent with initiator QSPEC
> >>>>> e.g., RMD can initiate a local QSPEC that contains TMOD =3D
> >>>>       bandwidth (sets r=3Dp, b/m to large) 8. QSPEC flags=20
> modified as
> >>>> follows:
> >>>>   o QNI sets M flag for each QSPEC parameter it=20
> populates that must
> >>>>     be interpreted or reservation fails
> >>>>   o if M flag set
> >>>>> downstream QNE MUST interpret parameter or reservation fails if=20
> >>>>> QNE does not support parameter it sets N flag & rejects
> >>>>       reservation
> >>>>> if QNE supports parameter but cannot meet parameter,
> >> it sets E
> >>>>       flag & rejects reservation
> >>>>   o if M flag not set
> >>>>> downstream QNE SHOULD interpret parameter if QNE does=20
> not support=20
> >>>>> parameter it sets the N flag &
> >>>>       optionally accepts or rejects reservation
> >>>>> if QNE supports parameter but cannot meet parameter,
> >> it sets E
> >>>>       flag & optionally accepts or rejects reservation
> >>>>   o R (remapped parameter) flag & Q (non QOSM) flag eliminated 9.
> >>>> QSPEC type defined and registry established in IANA section.
> >>>>
> >>>> Please review the updated draft.
> >>>>
> >>>> Thanks,
> >>>> Jerry
> >>>>
> >>>> -----Original Message-----
> >>>> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> >>>> Sent: Wednesday, December 13, 2006 3:50 PM
> >>>> To: i-d-announce@ietf.org
> >>>> Cc: nsis@ietf.org
> >>>> Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
> >>>>
> >>>> A New Internet-Draft is available from the on-line=20
> Internet-Drafts=20
> >>>> directories.
> >>>> This draft is a work item of the Next Steps in Signaling
> >>> Working Group
> >>>> of the IETF.
> >>>>
> >>>> 	Title		: QoS NSLP QSPEC Template
> >>>> 	Author(s)	: J. Ash, et al.
> >>>> 	Filename	: draft-ietf-nsis-qspec-13.txt
> >>>> 	Pages		: 52
> >>>> 	Date		: 2006-12-13
> >>>> =09
> >>>> The QoS NSLP protocol is used to signal QoS reservations and is
> >>>>    independent of a specific QoS model (QOSM) such as IntServ or
> >>>>    DiffServ.  Rather, all information specific to a QOSM is=20
> >>>> encapsulated
> >>>>    in a separate object, the QSPEC.  This document defines
> >> a template
> >>>>    for the QSPEC including a number of QSPEC parameters.=20
>  The QSPEC
> >>>>    parameters provide a common language to be re-used in
> >>> several QOSMs
> >>>>    and thereby aim to ensure the extensibility and
> >>> interoperability of
> >>>>    QoS NSLP.  The node initiating the NSIS signaling adds an
> >>> initiator
> >>>>    QSPEC, which indicates the QSPEC parameters that must be=20
> >>>> interpreted
> >>>>    by the downstream nodes less the reservation fails, thereby=20
> >>>> ensuring
> >>>>    the intention of the NSIS initiator is preserved along the=20
> >>>> signaling
> >>>>    path.
> >>>>
> >>>> A URL for this Internet-Draft is:
> >>>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt
> >>>>
> >>>> _______________________________________________
> >>>> nsis mailing list
> >>>> nsis@ietf.org
> >>>> https://www1.ietf.org/mailman/listinfo/nsis
> >>>>
> >>>
> >>>
> >>>
> >>
> >> _______________________________________________
> >> nsis mailing list
> >> nsis@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/nsis
> >>
> >
> >
> >
> > _______________________________________________
> > nsis mailing list
> > nsis@ietf.org
> > https://www1.ietf.org/mailman/listinfo/nsis
>=20



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



From nsis-bounces@ietf.org Wed Dec 20 12:22:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx59P-00037l-EF; Wed, 20 Dec 2006 12:22:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx59O-000318-CQ
	for nsis@ietf.org; Wed, 20 Dec 2006 12:22:42 -0500
Received: from mclmx2.mail.saic.com ([149.8.64.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx59N-00071l-Th
	for nsis@ietf.org; Wed, 20 Dec 2006 12:22:42 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx2.mail.saic.com; Wed, 20 Dec 2006 12:22:36 -0500
Received: from 0015-its-exbh02.us.saic.com ([10.43.229.22])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006122012223625501 ; Wed, 20 Dec 2006 12:22:36 -0500
Received: from 0591-ITS-EXMP02.us.saic.com ([10.42.81.248]) by
	0015-its-exbh02.us.saic.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Dec 2006 12:22:34 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] RE: Why is QSPEC control information removed?
Date: Wed, 20 Dec 2006 12:22:33 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426230F1A@0591-ITS-EXMP02.us.saic.com>
In-Reply-To: <BED43802-A19A-496F-B5F9-0C92EBA6562F@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] RE: Why is QSPEC control information removed?
Thread-Index: AcckWaLLxq7q7rdPRwS5P0S34ogcMAAALPSQ
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: "David R Oran" <oran@cisco.com>,
	"Georgios Karagiannis" <karagian@cs.utwente.nl>
X-OriginalArrivalTime: 20 Dec 2006 17:22:34.0890 (UTC)
	FILETIME=[7059B6A0:01C7245B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d2fdecab7a7fa796e06e001d026c91
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, nsis@ietf.org,
	=?iso-8859-1?Q?_=27Attila_B=E1der_=28IJ/ETH=29=27_?=
	<attila.bader@ericsson.com>
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

Dave:

Yes, we agree with your proposal with the adding of only ONE word =
"end-to-end (e2e)" before the word "QSPEC." That is, ".... standard =
end-to-end QSPEC..."

The whole things will read like this:

"QoSMs are free, subject to IANA registration and review rules, to =
extend QSPECs by adding parameters of any of the kinds supported by the =
standard end-to-end QSPEC. This includes traffic description parameters, =
constraint parameters and handling directives. QoSMs are not permitted, =
however, to reinterpret or redefine the standard QSPEC parameters =
specified in this document"

Best regards,
Radhika

-----Original Message-----
From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of =
David R Oran
Sent: Wednesday, December 20, 2006 12:08 PM
To: Georgios Karagiannis
Cc: 'Ash, Gerald R (Jerry), ALABS'; nsis@ietf.org; 'Attila B=E1der =
(IJ/ETH)'=20
Subject: Re: [NSIS] RE: Why is QSPEC control information removed?


On Dec 20, 2006, at 11:12 AM, Georgios Karagiannis wrote:

> Hi Attila and Jerry
>
> Okay, but I would then like to introduce a sentence in Section =20
> 4.3.3 that
> would say:
> "Note that a QOS model could specify any QSPEC parameter that could be
> considered
> as a QoS model-specific control information parameter, which could
> specify any other traffic handling directive."
>
I have a hard time understanding what this is actually saying, as =20
opposed to what it is trying to say, which I believe is that QOSMs =20
used in various domains may wish to extend the QSPEC in various ways, =20
and those extensions may include any category of qspec parameter.

How about:
"QoSMs are free, subject to IANA registration and review rules, to =20
extend QSPECs by adding parameters of any of the kinds supported by =20
the standard QSPEC. This includes traffic description parameters, =20
constraint parameters and handling directives. QoSMs are not =20
permitted, however, to reinterpret or redefine the standard QSPEC =20
parameters specified in this document"

Dave.


>
> Best Regards,
> Georgios
>
>
>
>
>> -----Original Message-----
>> From: Attila B=E1der (IJ/ETH) [mailto:attila.bader@ericsson.com]
>> Sent: woensdag 20 december 2006 12:54
>> To: Georgios Karagiannis; Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>> Subject: [NSIS] RE: Why is QSPEC control information removed?
>>
>> Hi Georgios, Jerry,
>>
>> I think mostly just the name changed, the concept is still
>> there. Control info is changed to traffic handling
>> directives, see 4.3.3.. I assume that defining new control
>> parameters or directives in QOS Model is still possible. The
>> QoS Model should specify which QOS NSLP option is used, it
>> also belongs to directives, is not it?
>>
>> Best regards, Attila
>>
>>
>>> -----Original Message-----
>>> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>>> Sent: Wednesday, December 20, 2006 10:59 AM
>>> To: 'Ash, Gerald R (Jerry), ALABS'; nsis@ietf.org
>>> Cc: Attila B=E1der (IJ/ETH)
>>> Subject: Why is QSPEC control information removed?
>>>
>>> Hi Jerry
>>>
>>> I have not yet finished reviewing the QSEPC template draft,
>> but I have
>>> seen that you have removed the concept of QSPEC control information.
>>> Why is that?
>>> The concept of QSPEC control information has to remain.
>>>
>>> Best Regards,
>>> Georgios
>>>
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>>>> Sent: donderdag 14 december 2006 1:00
>>>> To: nsis@ietf.org
>>>> Cc: Ash, Gerald R (Jerry), ALABS
>>>> Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
>>>>
>>>> Hi All,
>>>>
>>>> The updated 'QoS NSLP QSPEC Template' I-D is available at
>>>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
>>>>
>>>> The main changes are as follows:
>>>>
>>>> 1. notion of QOSMs played down
>>>>   o language e.g. 'QNSLP/QSPEC can signal for different
>> QOSMs across
>>>>     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
>>>>     QNEs on the path to implement different data plane QoS
>> mechanisms
>>>>     that meet QSPEC constraints'
>>>>   o a QOSM describes common capabilities among QNEs to act
>>>>     consistently when requested to admit traffic & in treating
>>>>     admitted traffic
>>>>   o a QOSM ID need not be defined or signaled
>>>>   o a QNE need not support any particular QOSM although a  QNI
>>>>     normally includes a QSPEC corresponding to a particular
>>> QOSM 2. a
>>>> 'QOSM specification'
>>>>   o still provides a rigorous specification of a QOSM &
>> what it does
>>>>   o documents how a QNE interprets & treats various
>> elements in QSPEC
>>>>   o can define additional QSPEC parameters 3. updated QOSM
>>> definition:
>>>>   a method to achieve QoS for a traffic flow, e.g., IntServ
>>>>   Controlled Load; specifies what sub-set of QSPEC QoS
>> constraints &
>>>>   traffic handling directives a QNE implementing that QOSM
>> is capable
>>>>   of supporting & how resources will be managed by the RMF 4.
>>>> QSPEC1/QSPEC2 semantics replaced with following semantics:
>>>>   o source traffic description (mandatory to include by QNI &
>>>>     mandatory to interpret by downstream QNEs)
>>>>> specified by traffic model (TMOD-1) parameter consisting of
>>>>       rate (r), bucket size (b), peak rate (p), minimum
>> policed unit
>>>>      (m) (mathematically complete way to describe traffic source)
>>>>> bandwidth only set r=3Dp; b/m to large values (separate
>>>>       bandwidth parameter not needed)
>>>>> TMOD-2 (optional to include)
>>>>   o constraints (optional to include):
>>>>> Path Latency
>>>>> Path Jitter
>>>>> Path PLR
>>>>> Path PER
>>>>> Slack Term
>>>>> Priority (Preemption, Defending, Admission, RPH Priority)
>>>>   o handling directives (optional to include):
>>>>> Excess Treatment
>>>>   o traffic classifiers (optional to include):
>>>>> PHB Class (PHB class set by downstream QNE to tell QNI how to
>>>>       mark traffic to ensure treatment committed by admission
>>>>       control)
>>>>> DSTE Class Type
>>>>> Y.1541 QoS class
>>>>   o eliminated:
>>>>> Bandwidth
>>>>> Ctot, Dtot, Csum, Dsum
>>>> 5. concept of remapping QSPEC parameters eliminated 6.
>>>> redefine 'interpret' a QSPEC parameter to mean 'must conform to
>>>>    RFCs defining parameter & procedures (formerly called 'strictly
>>>>    interpret')
>>>> 7. concept of local QSPECs retained
>>>>   o allows simpler control plane in a local domain
>>>>   o edge nodes
>>>>> must interpret initiator QSPEC parameters
>>>>> can either initiate parallel session with local QSPEC or
>>>>       define a local QSPEC with encapsulated initiator QSPEC
>>>>   o local QSPEC interpreted by local domain QNEs
>>>>   o local QSPEC must be consistent with initiator QSPEC
>>>>> e.g., RMD can initiate a local QSPEC that contains TMOD =3D
>>>>       bandwidth (sets r=3Dp, b/m to large) 8. QSPEC flags modified =
as
>>>> follows:
>>>>   o QNI sets M flag for each QSPEC parameter it populates that must
>>>>     be interpreted or reservation fails
>>>>   o if M flag set
>>>>> downstream QNE MUST interpret parameter or reservation fails
>>>>> if QNE does not support parameter it sets N flag & rejects
>>>>       reservation
>>>>> if QNE supports parameter but cannot meet parameter,
>> it sets E
>>>>       flag & rejects reservation
>>>>   o if M flag not set
>>>>> downstream QNE SHOULD interpret parameter
>>>>> if QNE does not support parameter it sets the N flag &
>>>>       optionally accepts or rejects reservation
>>>>> if QNE supports parameter but cannot meet parameter,
>> it sets E
>>>>       flag & optionally accepts or rejects reservation
>>>>   o R (remapped parameter) flag & Q (non QOSM) flag eliminated 9.
>>>> QSPEC type defined and registry established in IANA section.
>>>>
>>>> Please review the updated draft.
>>>>
>>>> Thanks,
>>>> Jerry
>>>>
>>>> -----Original Message-----
>>>> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>>>> Sent: Wednesday, December 13, 2006 3:50 PM
>>>> To: i-d-announce@ietf.org
>>>> Cc: nsis@ietf.org
>>>> Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
>>>>
>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>> directories.
>>>> This draft is a work item of the Next Steps in Signaling
>>> Working Group
>>>> of the IETF.
>>>>
>>>> 	Title		: QoS NSLP QSPEC Template
>>>> 	Author(s)	: J. Ash, et al.
>>>> 	Filename	: draft-ietf-nsis-qspec-13.txt
>>>> 	Pages		: 52
>>>> 	Date		: 2006-12-13
>>>> =09
>>>> The QoS NSLP protocol is used to signal QoS reservations and is
>>>>    independent of a specific QoS model (QOSM) such as IntServ or
>>>>    DiffServ.  Rather, all information specific to a QOSM is
>>>> encapsulated
>>>>    in a separate object, the QSPEC.  This document defines
>> a template
>>>>    for the QSPEC including a number of QSPEC parameters.  The QSPEC
>>>>    parameters provide a common language to be re-used in
>>> several QOSMs
>>>>    and thereby aim to ensure the extensibility and
>>> interoperability of
>>>>    QoS NSLP.  The node initiating the NSIS signaling adds an
>>> initiator
>>>>    QSPEC, which indicates the QSPEC parameters that must be
>>>> interpreted
>>>>    by the downstream nodes less the reservation fails, thereby
>>>> ensuring
>>>>    the intention of the NSIS initiator is preserved along the
>>>> signaling
>>>>    path.
>>>>
>>>> A URL for this Internet-Draft is:
>>>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt
>>>>
>>>> _______________________________________________
>>>> nsis mailing list
>>>> nsis@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/nsis
>>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>
>
>
>
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

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

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



From nsis-bounces@ietf.org Wed Dec 20 13:41:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx6Ni-0004ya-2m; Wed, 20 Dec 2006 13:41:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx6Nh-0004yU-DH
	for nsis@ietf.org; Wed, 20 Dec 2006 13:41:33 -0500
Received: from mclmx2.mail.saic.com ([149.8.64.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx6Ne-0000ZS-QK
	for nsis@ietf.org; Wed, 20 Dec 2006 13:41:33 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx2.mail.saic.com; Wed, 20 Dec 2006 13:41:16 -0500
Received: from 0015-its-exbh02.us.saic.com ([10.43.229.22])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006122013411305153 ; Wed, 20 Dec 2006 13:41:13 -0500
Received: from 0591-ITS-EXMP02.us.saic.com ([10.42.81.248]) by
	0015-its-exbh02.us.saic.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Dec 2006 13:41:13 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] RE: Why is QSPEC control information removed?
Date: Wed, 20 Dec 2006 13:41:13 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426230F1C@0591-ITS-EXMP02.us.saic.com>
In-Reply-To: <62D92A9A02BCC845B202323D49A48426230F1A@0591-ITS-EXMP02.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] RE: Why is QSPEC control information removed?
Thread-Index: AcckWaLLxq7q7rdPRwS5P0S34ogcMAAALPSQAAK8FRA=
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: "David R Oran" <oran@cisco.com>,
	"Georgios Karagiannis" <karagian@cs.utwente.nl>
X-OriginalArrivalTime: 20 Dec 2006 18:41:13.0594 (UTC)
	FILETIME=[6CEACDA0:01C72466]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 918f4bd8440e8de4700bcf6d658bc801
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, nsis@ietf.org,
	=?iso-8859-1?Q?_=27Attila_B=E1der_=28IJ/ETH=29=27_?=
	<attila.bader@ericsson.com>
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

Dave:

In addition, as an editor (I think that you should be the ONLY editor of =
this draft as others took ITU-T things as standards in the IETF), you =
have the responsibility to define "Standard QSPEC."

The "standard" QSPEC template needs to be specified as a reference =
throughout the document.

As we discussed before, QOS SLAs like Y.1415, DSTE, etc. and any =
references of those QOS SLAs like Y.1451 QOS classes MUST be removed =
from this draft.

Please resubmit the draft accordingly.

Best regards,
Radhika

-----Original Message-----
From: Roy, Radhika R.=20
Sent: Wednesday, December 20, 2006 12:23 PM
To: 'David R Oran'; Georgios Karagiannis
Cc: 'Ash, Gerald R (Jerry), ALABS'; nsis@ietf.org; 'Attila B=E1der =
(IJ/ETH)'=20
Subject: RE: [NSIS] RE: Why is QSPEC control information removed?

Dave:

Yes, we agree with your proposal with the adding of only ONE word =
"end-to-end (e2e)" before the word "QSPEC." That is, ".... standard =
end-to-end QSPEC..."

The whole things will read like this:

"QoSMs are free, subject to IANA registration and review rules, to =
extend QSPECs by adding parameters of any of the kinds supported by the =
standard end-to-end QSPEC. This includes traffic description parameters, =
constraint parameters and handling directives. QoSMs are not permitted, =
however, to reinterpret or redefine the standard QSPEC parameters =
specified in this document"

Best regards,
Radhika

-----Original Message-----
From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of =
David R Oran
Sent: Wednesday, December 20, 2006 12:08 PM
To: Georgios Karagiannis
Cc: 'Ash, Gerald R (Jerry), ALABS'; nsis@ietf.org; 'Attila B=E1der =
(IJ/ETH)'=20
Subject: Re: [NSIS] RE: Why is QSPEC control information removed?


On Dec 20, 2006, at 11:12 AM, Georgios Karagiannis wrote:

> Hi Attila and Jerry
>
> Okay, but I would then like to introduce a sentence in Section =20
> 4.3.3 that
> would say:
> "Note that a QOS model could specify any QSPEC parameter that could be
> considered
> as a QoS model-specific control information parameter, which could
> specify any other traffic handling directive."
>
I have a hard time understanding what this is actually saying, as =20
opposed to what it is trying to say, which I believe is that QOSMs =20
used in various domains may wish to extend the QSPEC in various ways, =20
and those extensions may include any category of qspec parameter.

How about:
"QoSMs are free, subject to IANA registration and review rules, to =20
extend QSPECs by adding parameters of any of the kinds supported by =20
the standard QSPEC. This includes traffic description parameters, =20
constraint parameters and handling directives. QoSMs are not =20
permitted, however, to reinterpret or redefine the standard QSPEC =20
parameters specified in this document"

Dave.


>
> Best Regards,
> Georgios
>
>
>
>
>> -----Original Message-----
>> From: Attila B=E1der (IJ/ETH) [mailto:attila.bader@ericsson.com]
>> Sent: woensdag 20 december 2006 12:54
>> To: Georgios Karagiannis; Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>> Subject: [NSIS] RE: Why is QSPEC control information removed?
>>
>> Hi Georgios, Jerry,
>>
>> I think mostly just the name changed, the concept is still
>> there. Control info is changed to traffic handling
>> directives, see 4.3.3.. I assume that defining new control
>> parameters or directives in QOS Model is still possible. The
>> QoS Model should specify which QOS NSLP option is used, it
>> also belongs to directives, is not it?
>>
>> Best regards, Attila
>>
>>
>>> -----Original Message-----
>>> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>>> Sent: Wednesday, December 20, 2006 10:59 AM
>>> To: 'Ash, Gerald R (Jerry), ALABS'; nsis@ietf.org
>>> Cc: Attila B=E1der (IJ/ETH)
>>> Subject: Why is QSPEC control information removed?
>>>
>>> Hi Jerry
>>>
>>> I have not yet finished reviewing the QSEPC template draft,
>> but I have
>>> seen that you have removed the concept of QSPEC control information.
>>> Why is that?
>>> The concept of QSPEC control information has to remain.
>>>
>>> Best Regards,
>>> Georgios
>>>
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>>>> Sent: donderdag 14 december 2006 1:00
>>>> To: nsis@ietf.org
>>>> Cc: Ash, Gerald R (Jerry), ALABS
>>>> Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
>>>>
>>>> Hi All,
>>>>
>>>> The updated 'QoS NSLP QSPEC Template' I-D is available at
>>>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
>>>>
>>>> The main changes are as follows:
>>>>
>>>> 1. notion of QOSMs played down
>>>>   o language e.g. 'QNSLP/QSPEC can signal for different
>> QOSMs across
>>>>     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
>>>>     QNEs on the path to implement different data plane QoS
>> mechanisms
>>>>     that meet QSPEC constraints'
>>>>   o a QOSM describes common capabilities among QNEs to act
>>>>     consistently when requested to admit traffic & in treating
>>>>     admitted traffic
>>>>   o a QOSM ID need not be defined or signaled
>>>>   o a QNE need not support any particular QOSM although a  QNI
>>>>     normally includes a QSPEC corresponding to a particular
>>> QOSM 2. a
>>>> 'QOSM specification'
>>>>   o still provides a rigorous specification of a QOSM &
>> what it does
>>>>   o documents how a QNE interprets & treats various
>> elements in QSPEC
>>>>   o can define additional QSPEC parameters 3. updated QOSM
>>> definition:
>>>>   a method to achieve QoS for a traffic flow, e.g., IntServ
>>>>   Controlled Load; specifies what sub-set of QSPEC QoS
>> constraints &
>>>>   traffic handling directives a QNE implementing that QOSM
>> is capable
>>>>   of supporting & how resources will be managed by the RMF 4.
>>>> QSPEC1/QSPEC2 semantics replaced with following semantics:
>>>>   o source traffic description (mandatory to include by QNI &
>>>>     mandatory to interpret by downstream QNEs)
>>>>> specified by traffic model (TMOD-1) parameter consisting of
>>>>       rate (r), bucket size (b), peak rate (p), minimum
>> policed unit
>>>>      (m) (mathematically complete way to describe traffic source)
>>>>> bandwidth only set r=3Dp; b/m to large values (separate
>>>>       bandwidth parameter not needed)
>>>>> TMOD-2 (optional to include)
>>>>   o constraints (optional to include):
>>>>> Path Latency
>>>>> Path Jitter
>>>>> Path PLR
>>>>> Path PER
>>>>> Slack Term
>>>>> Priority (Preemption, Defending, Admission, RPH Priority)
>>>>   o handling directives (optional to include):
>>>>> Excess Treatment
>>>>   o traffic classifiers (optional to include):
>>>>> PHB Class (PHB class set by downstream QNE to tell QNI how to
>>>>       mark traffic to ensure treatment committed by admission
>>>>       control)
>>>>> DSTE Class Type
>>>>> Y.1541 QoS class
>>>>   o eliminated:
>>>>> Bandwidth
>>>>> Ctot, Dtot, Csum, Dsum
>>>> 5. concept of remapping QSPEC parameters eliminated 6.
>>>> redefine 'interpret' a QSPEC parameter to mean 'must conform to
>>>>    RFCs defining parameter & procedures (formerly called 'strictly
>>>>    interpret')
>>>> 7. concept of local QSPECs retained
>>>>   o allows simpler control plane in a local domain
>>>>   o edge nodes
>>>>> must interpret initiator QSPEC parameters
>>>>> can either initiate parallel session with local QSPEC or
>>>>       define a local QSPEC with encapsulated initiator QSPEC
>>>>   o local QSPEC interpreted by local domain QNEs
>>>>   o local QSPEC must be consistent with initiator QSPEC
>>>>> e.g., RMD can initiate a local QSPEC that contains TMOD =3D
>>>>       bandwidth (sets r=3Dp, b/m to large) 8. QSPEC flags modified =
as
>>>> follows:
>>>>   o QNI sets M flag for each QSPEC parameter it populates that must
>>>>     be interpreted or reservation fails
>>>>   o if M flag set
>>>>> downstream QNE MUST interpret parameter or reservation fails
>>>>> if QNE does not support parameter it sets N flag & rejects
>>>>       reservation
>>>>> if QNE supports parameter but cannot meet parameter,
>> it sets E
>>>>       flag & rejects reservation
>>>>   o if M flag not set
>>>>> downstream QNE SHOULD interpret parameter
>>>>> if QNE does not support parameter it sets the N flag &
>>>>       optionally accepts or rejects reservation
>>>>> if QNE supports parameter but cannot meet parameter,
>> it sets E
>>>>       flag & optionally accepts or rejects reservation
>>>>   o R (remapped parameter) flag & Q (non QOSM) flag eliminated 9.
>>>> QSPEC type defined and registry established in IANA section.
>>>>
>>>> Please review the updated draft.
>>>>
>>>> Thanks,
>>>> Jerry
>>>>
>>>> -----Original Message-----
>>>> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>>>> Sent: Wednesday, December 13, 2006 3:50 PM
>>>> To: i-d-announce@ietf.org
>>>> Cc: nsis@ietf.org
>>>> Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
>>>>
>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>> directories.
>>>> This draft is a work item of the Next Steps in Signaling
>>> Working Group
>>>> of the IETF.
>>>>
>>>> 	Title		: QoS NSLP QSPEC Template
>>>> 	Author(s)	: J. Ash, et al.
>>>> 	Filename	: draft-ietf-nsis-qspec-13.txt
>>>> 	Pages		: 52
>>>> 	Date		: 2006-12-13
>>>> =09
>>>> The QoS NSLP protocol is used to signal QoS reservations and is
>>>>    independent of a specific QoS model (QOSM) such as IntServ or
>>>>    DiffServ.  Rather, all information specific to a QOSM is
>>>> encapsulated
>>>>    in a separate object, the QSPEC.  This document defines
>> a template
>>>>    for the QSPEC including a number of QSPEC parameters.  The QSPEC
>>>>    parameters provide a common language to be re-used in
>>> several QOSMs
>>>>    and thereby aim to ensure the extensibility and
>>> interoperability of
>>>>    QoS NSLP.  The node initiating the NSIS signaling adds an
>>> initiator
>>>>    QSPEC, which indicates the QSPEC parameters that must be
>>>> interpreted
>>>>    by the downstream nodes less the reservation fails, thereby
>>>> ensuring
>>>>    the intention of the NSIS initiator is preserved along the
>>>> signaling
>>>>    path.
>>>>
>>>> A URL for this Internet-Draft is:
>>>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt
>>>>
>>>> _______________________________________________
>>>> nsis mailing list
>>>> nsis@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/nsis
>>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>
>
>
>
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

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

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



From nsis-bounces@ietf.org Wed Dec 20 23:43:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxFm4-0004XZ-Vp; Wed, 20 Dec 2006 23:43:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxFm3-0004XU-E6
	for nsis@ietf.org; Wed, 20 Dec 2006 23:43:19 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxFm0-00088u-WA
	for nsis@ietf.org; Wed, 20 Dec 2006 23:43:19 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kBL4g5hb010333; Thu, 21 Dec 2006 06:42:12 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Dec 2006 06:42:50 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Dec 2006 06:42:49 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] RE: Why is QSPEC control information removed?
Date: Thu, 21 Dec 2006 06:42:46 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC019ADFF0@esebe199.NOE.Nokia.com>
In-Reply-To: <BED43802-A19A-496F-B5F9-0C92EBA6562F@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] RE: Why is QSPEC control information removed?
Thread-Index: AcckWZeQOvAFis52TCeu9L9ApdTPgwAYNfBw
From: <john.loughney@nokia.com>
To: <oran@cisco.com>, <karagian@cs.utwente.nl>
X-OriginalArrivalTime: 21 Dec 2006 04:42:49.0071 (UTC)
	FILETIME=[777F7FF0:01C724BA]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061221064212-28150BB0-3FBC54BB/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: gash@att.com, nsis@ietf.org, attila.bader@ericsson.com
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


>> Okay, but I would then like to introduce a sentence in Section
>> 4.3.3 that
>> would say:
>> "Note that a QOS model could specify any QSPEC parameter=20
>that could be=20
>> considered as a QoS model-specific control information parameter,=20
>> which could specify any other traffic handling directive."
>>
>I have a hard time understanding what this is actually saying,=20
>as opposed to what it is trying to say, which I believe is=20
>that QOSMs used in various domains may wish to extend the=20
>QSPEC in various ways, and those extensions may include any=20
>category of qspec parameter.
>
>How about:
>"QoSMs are free, subject to IANA registration and review=20
>rules, to extend QSPECs by adding parameters of any of the=20
>kinds supported by the standard QSPEC. This includes traffic=20
>description parameters, constraint parameters and handling=20
>directives. QoSMs are not permitted, however, to reinterpret=20
>or redefine the standard QSPEC parameters specified in this document"

Sounds good to me.

John

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



From nsis-bounces@ietf.org Thu Dec 21 02:26:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxIJA-0000dU-S4; Thu, 21 Dec 2006 02:25:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxIJ9-0000dL-H2
	for nsis@ietf.org; Thu, 21 Dec 2006 02:25:39 -0500
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxIJ7-00071x-QL
	for nsis@ietf.org; Thu, 21 Dec 2006 02:25:39 -0500
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/kings) with ESMTP id
	kBL7PCdV029565; Thu, 21 Dec 2006 16:25:12 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx3) with ESMTP id
	kBL7PB705288; Thu, 21 Dec 2006 16:25:11 +0900 (JST)
Received: from epochmail.jp.panasonic.com (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/mariners) with ESMTP id
	kBL7PCS23605; Thu, 21 Dec 2006 16:25:12 +0900 (JST)
Received: by epochmail.jp.panasonic.com (8.12.11.20060308/3.7W/soml25) id
	kBL7PB0S002721; Thu, 21 Dec 2006 16:25:11 +0900 (JST)
Received: from [10.68.136.71]
	by soml25.jp.panasonic.com (8.12.11.20060308/3.7W) with ESMTP id
	kBL7PAC4002685; Thu, 21 Dec 2006 16:25:10 +0900 (JST)
Date: Thu, 21 Dec 2006 16:28:42 +0900
From: Takako Sanda <sanda.takako@jp.panasonic.com>
To: Martin Stiemerling <Stiemerling@netlab.nec.de>
Subject: Re: [NSIS] Change proposal for Mobility Applicability draft
In-Reply-To: <113091BD57179D4491C19DA7E10CD6968C8557@mx1.office>
References: <20061215212000.03D3.SANDA.TAKAKO@jp.panasonic.com>
	<113091BD57179D4491C19DA7E10CD6968C8557@mx1.office>
Message-Id: <20061221162803.F7FE.SANDA.TAKAKO@jp.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.24.02 [ja]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Cc: Jukka MJ Manner <jmanner@cs.Helsinki.FI>, nsis@ietf.org,
	Hannes Tschofenig <hannes.tschofenig@siemens.com>,
	Xiaoming Fu <fu@cs.uni-goettingen.de>, Sung-Hyuck Lee <starsu@MIT.EDU>,
	Seong-Ho Jeong <shjeong@hufs.ac.kr>
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

Hi Martin and all,

Thank you for your comments. Please see my comments in line.

cheers,
Takako


On Tue, 19 Dec 2006 12:06:10 +0100
Martin Stiemerling <Stiemerling@netlab.nec.de> wrote:

> (chair's hat off)
> 
> Hi all,
> 
> Here are my comments:   
> 
> > -----Original Message-----
> > From: Takako Sanda [mailto:sanda.takako@jp.panasonic.com] 
> > Sent: Friday, December 15, 2006 1:24 PM
> > To: nsis@ietf.org
> > Cc: Xiaoming Fu; Seong-Ho Jeong; Sung-Hyuck Lee; Jukka MJ 
> > Manner; Hannes Tschofenig
> > Subject: [NSIS] Change proposal for Mobility Applicability draft
> > 
> > Dear all,
> > 
> > After the last IETF meeting, authors of NSIS Mobility 
> > Applicability draft 
> > (draft-ietf-nsis-applicability-mobility-signaling-05.txt) 
> > have discussed how the draft should be cleaned up and which 
> > topics are still missing.
> > 
> > The followings are discussion result for proposed changes. 
> > Please review them and give your comments by 5th Jan 2007. If 
> > no discussion has been made, authors will start editing text 
> > based on the decision below.
> > 
> > 
> > 1. Section 4 and 5 ("Basic Operations for Mobility Support" 
> > and "Applicability Statement") should be divided into two parts and
> > rewritten:-
> > 
> >   o "Main" part, which is focusing on examples and describing how
> >   mobility is handled by the NSIS protocols. Topics here will be
> >   route change handling and NSIS interwork with MIP v4/v6
> >   (including tunneling management). This part must not include
> >   "should work" or "may work" sort of description.
> 
> I see in the same way. Probably it would also be good to talk with
> Charles and Henning (i.e., the authors of NSIS Operation Over IP
> Tunnels) about the tunnel management. 

This is good idea.


> 
> > 
> >   o "Further Study" part, which introduces summary of potential
> >   issues and possible approaches for other topics. These topics are
> >   out-of-scope for discussing details, such as interwork with other
> >   mobility protocols, multihoming, peer failure (and frequent
> >   path change, may be)
> 
> Agreed and really stay brief, i.e., not exploring it too much.
> 
> > 
> > 2. Description of mobility objects should be removed.
> 
> Yes, indeed. Since it is anyway not include in GIST and not required. 
> 
> > 
> > 3. Security part needs to be cleaned up. Concrete change plan 
> > is still under discussions.
> 
> Do you have any plans here in general?

Authors just discussed that we would not be able to leave the section as
is, because the section just outlined a number of options and their
pros/cons.

Discussions among authors/WG members for getting conclusion should be
necessary.

> 
> > 
> > 4. As for new open issue, NAT/FW should be raised
> >     "If a MN moves, IP addresses and routing change so that the 
> >     packets enter and leave the network through a new NAT/FW node.
> >     We need to open the old ports on this new NAT/FW node, and remove
> >     the ones on the previous NAT/FW."
> >   How would this work in real like?
> >   The main difference for the NAT/FW work with respect is two-fold:
> >    * We only use e2e refreshes. This makes things easier. 
> >    * Most firewalls drop packets if a pinhole does not exist. 
> >   We need to capture these two things.
> 
> The protocol operations for the NATFW NSLP are quite easy but I see the
> need for more carefully considerations wrt mobility. Hannes and I will
> take care about it. I have just created a entry in the NATFW issue
> tracker:
> 
> https://kobe.netlab.nec.de/roundup/nsis-natfw-nslp/issue87

Appreciated!

> 
> > 
> > 5. Detailed Operations in current texts should be moved to 
> > Appendix or discussed in separate draft.
> 
> What do you refer to with "Detailed Operations"?

Honestly, authors have not defined actual scope of detailed operations
yet.
IMO, for example, when we make summary for each topic in "Further Study"
part, remaining texts can be categorized as "detailed operations", such
as concrete signaling flows to find the best access router in multihoming
case.


> 
> Thanks!
> 
>   Martin
> 
> > 
> > 6. Section 3 (Problem Statement) may need to be cleaned up 
> > based on changes in main body.
> > 
> > BR,
> > Takako
> > 
> > 
> > _______________________________________________
> > nsis mailing list
> > nsis@ietf.org
> > https://www1.ietf.org/mailman/listinfo/nsis
> > 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis


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



From nsis-bounces@ietf.org Thu Dec 21 04:36:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxKKz-0004LD-Sf; Thu, 21 Dec 2006 04:35:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxKKy-0004K2-N3
	for nsis@ietf.org; Thu, 21 Dec 2006 04:35:40 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxKKy-0003Ts-55
	for nsis@ietf.org; Thu, 21 Dec 2006 04:35:40 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kBL9ZOEh010878; Thu, 21 Dec 2006 10:35:35 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>
Date: Thu, 21 Dec 2006 10:35:20 +0100
Message-ID: <000101c724e3$59aa2f10$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC805D@KCCLUST06EVS1.ugd.att.com>
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAULntzAAAvUVQAAB/i+AACx8qXA=
X-Spam-Score: 0.3 () FVGT_s_OBFU_Q1
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Thu, 21 Dec 2006 10:35:36 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1e467ff145ef391eb7b594ef62b8301f
Cc: nsis@ietf.org,
	=?iso-8859-1?Q?'Attila_B=E1der_=28IJ/ETH=29'?= <attila.bader@ericsson.com>
Subject: [NSIS] RE: Why is QSPEC control information removed?
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

Hi Jerry

In order to emphasize the need of having QSPEC control information
parameters=20
 I  would however appreciate if the name of Section 4.3.3 is changed=20
From:
4.3.3 Traffic Handling Directives
INTO:
4.3.3 QSPEC control information
 =20
Best Regards,
Georgios

> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]=20
> Sent: woensdag 20 december 2006 13:27
> To: Georgios Karagiannis
> Cc: Ash, Gerald R (Jerry), ALABS; Attila B=E1der (IJ/ETH); =
nsis@ietf.org
> Subject: RE: Why is QSPEC control information removed?
>=20
> Hi Georgios,
>=20
> Attila is right.  No functionality has changed. =20
>=20
> In the previous draft the only 'control information'=20
> parameter was 'excess treatment'.  That parameter is now=20
> defined as a 'traffic handling directive' parameter in=20
> Sections 4.3.3 and 6.2.11. =20
>=20
> New QSPEC parameters can still be defined in QOSM=20
> specification documents, as specified in Section 5.4.
>=20
> Thanks,
> Regards,
> Jerry
>=20
> -----Original Message-----
> From: Attila B=E1der (IJ/ETH) [mailto:attila.bader@ericsson.com]
> Sent: Wednesday, December 20, 2006 6:54 AM
> To: Georgios Karagiannis; Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> Subject: RE: Why is QSPEC control information removed?
>=20
> Hi Georgios, Jerry,
>=20
> I think mostly just the name changed, the concept is still=20
> there. Control info is changed to traffic handling=20
> directives, see 4.3.3.. I assume that defining new control=20
> parameters or directives in QOS Model is still possible. The=20
> QoS Model should specify which QOS NSLP option is used, it=20
> also belongs to directives, is not it?
>=20
> Best regards, Attila
> =20
>=20
> >-----Original Message-----
> >From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> >Sent: Wednesday, December 20, 2006 10:59 AM
> >To: 'Ash, Gerald R (Jerry), ALABS'; nsis@ietf.org
> >Cc: Attila B=E1der (IJ/ETH)
> >Subject: Why is QSPEC control information removed?
> >
> >Hi Jerry
> >
> >I have not yet finished reviewing the QSEPC template draft,=20
> but I have=20
> >seen that you have removed the concept of QSPEC control information.
> >Why is that?
> >The concept of QSPEC control information has to remain.=20
> >
> >Best Regards,
> >Georgios
> >
> >
> >
> >=20
> >
> >> -----Original Message-----
> >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> >> Sent: donderdag 14 december 2006 1:00
> >> To: nsis@ietf.org
> >> Cc: Ash, Gerald R (Jerry), ALABS
> >> Subject: RE: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
> >>=20
> >> Hi All,
> >>=20
> >> The updated 'QoS NSLP QSPEC Template' I-D is available at=20
> >> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
> >>=20
> >> The main changes are as follows:
> >>=20
> >> 1. notion of QOSMs played down
> >>   o language e.g. 'QNSLP/QSPEC can signal for different=20
> QOSMs across
> >>     multiple domains' replaced by notion that 'QNSLP/QSPEC allows
> >>     QNEs on the path to implement different data plane QoS=20
> mechanisms
> >>     that meet QSPEC constraints'
> >>   o a QOSM describes common capabilities among QNEs to act
> >>     consistently when requested to admit traffic & in treating
> >>     admitted traffic
> >>   o a QOSM ID need not be defined or signaled
> >>   o a QNE need not support any particular QOSM although a  QNI
> >>     normally includes a QSPEC corresponding to a particular
> >QOSM 2. a
> >> 'QOSM specification'
> >>   o still provides a rigorous specification of a QOSM &=20
> what it does
> >>   o documents how a QNE interprets & treats various=20
> elements in QSPEC
> >>   o can define additional QSPEC parameters 3. updated QOSM
> >definition:
> >>   a method to achieve QoS for a traffic flow, e.g., IntServ
> >>   Controlled Load; specifies what sub-set of QSPEC QoS=20
> constraints &
> >>   traffic handling directives a QNE implementing that QOSM=20
> is capable
> >>   of supporting & how resources will be managed by the RMF 4.=20
> >> QSPEC1/QSPEC2 semantics replaced with following semantics:
> >>   o source traffic description (mandatory to include by QNI &
> >>     mandatory to interpret by downstream QNEs)
> >>     > specified by traffic model (TMOD-1) parameter consisting of
> >>       rate (r), bucket size (b), peak rate (p), minimum=20
> policed unit
> >>      (m) (mathematically complete way to describe traffic source)
> >>     > bandwidth only set r=3Dp; b/m to large values (separate
> >>       bandwidth parameter not needed)
> >>     > TMOD-2 (optional to include)
> >>   o constraints (optional to include):
> >>     > Path Latency
> >>     > Path Jitter
> >>     > Path PLR
> >>     > Path PER
> >>     > Slack Term
> >>     > Priority (Preemption, Defending, Admission, RPH Priority)
> >>   o handling directives (optional to include):
> >>     > Excess Treatment
> >>   o traffic classifiers (optional to include):
> >>     > PHB Class (PHB class set by downstream QNE to tell QNI how to
> >>       mark traffic to ensure treatment committed by admission
> >>       control)
> >>     > DSTE Class Type
> >>     > Y.1541 QoS class
> >>   o eliminated:
> >>     > Bandwidth
> >>     > Ctot, Dtot, Csum, Dsum
> >> 5. concept of remapping QSPEC parameters eliminated 6.=20
> >> redefine 'interpret' a QSPEC parameter to mean 'must conform to
> >>    RFCs defining parameter & procedures (formerly called 'strictly
> >>    interpret')
> >> 7. concept of local QSPECs retained
> >>   o allows simpler control plane in a local domain
> >>   o edge nodes
> >>     > must interpret initiator QSPEC parameters
> >>     > can either initiate parallel session with local QSPEC or
> >>       define a local QSPEC with encapsulated initiator QSPEC
> >>   o local QSPEC interpreted by local domain QNEs
> >>   o local QSPEC must be consistent with initiator QSPEC
> >>     > e.g., RMD can initiate a local QSPEC that contains TMOD =3D
> >>       bandwidth (sets r=3Dp, b/m to large) 8. QSPEC flags modified =
as
> >> follows:
> >>   o QNI sets M flag for each QSPEC parameter it populates that must
> >>     be interpreted or reservation fails
> >>   o if M flag set
> >>     > downstream QNE MUST interpret parameter or reservation fails
> >>     > if QNE does not support parameter it sets N flag & rejects
> >>       reservation
> >>     > if QNE supports parameter but cannot meet parameter,=20
> it sets E
> >>       flag & rejects reservation
> >>   o if M flag not set
> >>     > downstream QNE SHOULD interpret parameter
> >>     > if QNE does not support parameter it sets the N flag &
> >>       optionally accepts or rejects reservation
> >>     > if QNE supports parameter but cannot meet parameter,=20
> it sets E
> >>       flag & optionally accepts or rejects reservation
> >>   o R (remapped parameter) flag & Q (non QOSM) flag eliminated 9.=20
> >> QSPEC type defined and registry established in IANA section.
> >>=20
> >> Please review the updated draft.
> >>=20
> >> Thanks,
> >> Jerry
> >>=20
> >> -----Original Message-----
> >> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> >> Sent: Wednesday, December 13, 2006 3:50 PM
> >> To: i-d-announce@ietf.org
> >> Cc: nsis@ietf.org
> >> Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-13.txt
> >>=20
> >> A New Internet-Draft is available from the on-line Internet-Drafts=20
> >> directories.
> >> This draft is a work item of the Next Steps in Signaling
> >Working Group
> >> of the IETF.
> >>=20
> >> 	Title		: QoS NSLP QSPEC Template
> >> 	Author(s)	: J. Ash, et al.
> >> 	Filename	: draft-ietf-nsis-qspec-13.txt
> >> 	Pages		: 52
> >> 	Date		: 2006-12-13
> >> =09
> >> The QoS NSLP protocol is used to signal QoS reservations and is
> >>    independent of a specific QoS model (QOSM) such as IntServ or
> >>    DiffServ.  Rather, all information specific to a QOSM is=20
> >> encapsulated
> >>    in a separate object, the QSPEC.  This document defines=20
> a template
> >>    for the QSPEC including a number of QSPEC parameters.  The QSPEC
> >>    parameters provide a common language to be re-used in
> >several QOSMs
> >>    and thereby aim to ensure the extensibility and
> >interoperability of
> >>    QoS NSLP.  The node initiating the NSIS signaling adds an
> >initiator
> >>    QSPEC, which indicates the QSPEC parameters that must be=20
> >> interpreted
> >>    by the downstream nodes less the reservation fails, thereby=20
> >> ensuring
> >>    the intention of the NSIS initiator is preserved along the=20
> >> signaling
> >>    path.
> >>=20
> >> A URL for this Internet-Draft is:
> >> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt
> >>=20
> >> _______________________________________________
> >> nsis mailing list
> >> nsis@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/nsis
> >>=20
> >
> >
> >
>=20



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



From nsis-bounces@ietf.org Thu Dec 21 09:01:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxOU2-0004Ez-LW; Thu, 21 Dec 2006 09:01:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxOU1-0004Eu-B4
	for nsis@ietf.org; Thu, 21 Dec 2006 09:01:17 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxOTy-0005Hg-Jo
	for nsis@ietf.org; Thu, 21 Dec 2006 09:01:17 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kBLE11B4021997; Thu, 21 Dec 2006 15:01:05 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Jukka MJ Manner'" <jmanner@cs.Helsinki.FI>,
	"'Bernd Schloer'" <bernd@schloer.net>
Subject: RE: [NSIS] QoS NSLP v. "13-pre1"
Date: Thu, 21 Dec 2006 15:00:57 +0100
Message-ID: <001b01c72508$733b7130$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <Pine.LNX.4.64.0612102048270.11174@sbz-31.cs.Helsinki.FI>
Thread-Index: AcccjCjesfchn+kbTWObZSptAnWeIgIfDF6w
X-Spam-Score: 0 () 
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Thu, 21 Dec 2006 15:01:05 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
Cc: nsis@ietf.org
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

Hi Bernd 

I agree with Jukka!

Best regards,
Georgios
 
> -----Original Message-----
> From: Jukka MJ Manner [mailto:jmanner@cs.Helsinki.FI] 
> Sent: zondag 10 december 2006 19:51
> To: Bernd Schloer
> Cc: nsis@ietf.org
> Subject: Re: [NSIS] QoS NSLP v. "13-pre1"
> 
> 
> Hi,
> 
> I think the general design decision in any protocol is that 
> if you don't understand a message, you should drop it. In the 
> case of the QoS NSLP, dropping the message is the right thing 
> to do; the reservation will be torn down eventually due to 
> the refresh timeout.
> 
> Jukka
> 
> On Sat, 9 Dec 2006, Bernd Schloer wrote:
> 
> > section 5.4.1 says
> > 
> >    As discussed in Section 5.2.5.2, to avoid incorrect 
> removal of state
> >    after a rerouting event, a node receiving a RESERVE 
> message with the
> >    TEAR flag set which does not come from the current peer QNE,
> >    identified by its SII, MUST be ignored and MUST NOT be forwarded.
> > 
> > 
> > The SII-Handle is generated by GIST and points to the GIST next hop 
> > and to the local interface. In this case for C the current 
> peer QNE is 
> > A, but the SII-Handle points to B. Any existing reservation can 
> > neither over (1), nor over (2) be removed.
> > 
> > In case a router just rebooted, it has no current peer QNE, 
> but should 
> > forward the tearing RESERVE, as discussed here 
> > http://www1.ietf.org/mail-archive/web/nsis/current/msg06697.html
> > Existing reservations will not be removed further along the path.
> > 
> > Bernd
> > 
> > 
> > 
> > 
> > Bernd Schloer wrote:
> > > Hi Jukka,
> > > 
> > > 
> > > the initial route A-B-C uses links (1) and (3). After link (1) 
> > > fails, the path is rerouted using links (2) and (3).
> > > 
> > > 
> > >              (1)
> > >            /-----\                       |x| = QoS NSLP aware
> > >          +-+     /-\ (3) +-+             +-+
> > >      ----|A|     |B|-----|C|----
> > >          +-+     \-/     +-+             /-\
> > >            \-----/                       |x| = QoS NSLP unaware
> > >              (2)
> > > 
> > > section 3.2.10 says
> > > 
> > >    When the QoS NSLP is aware of the route change, it 
> needs to set up
> > >    the reservation on the new path. This is done by sending a new
> > >    RESERVE message. If the next QNE is, in fact, 
> unchanged then this
> > >    will be used to refresh/update the existing 
> reservation. Otherwise it
> > >    will lead to the reservation being installed on the new path.
> > > 
> > > 
> > > section 5.3.1.says
> > > 
> > >    If the RSN is greater than the current stored value, 
> the current 
> > > reservation
> > >    MUST be modified appropriately (provided that 
> admission control 
> > > and policy
> > >    control succeed), and the stored RSN value updated to 
> that for the new
> > >    reservation.
> > > 
> > > According to section 3.2.10 sending a full RESERVE 
> including a QSPEC 
> > > and the next peer is unchanged the reservation will be 
> > > updated/refreshed. However section
> > > 5.3.1
> > > talks not about refreshing/updating, it says the current 
> reservation 
> > > must be modified appropriately. What is the meaning of 
> > > "appropriately" here? What happens to the current reservation?
> > > 
> > > When A sends a full RESERVE with set SCOPING-Flag 
> including RII and 
> > > QSPEC object, and if the RESERVE will be treated as an updating, 
> > > refreshing RESERVE, the RESPONSE will contain an INFO object with 
> > > Success, Reservation succesful. In case of new installed 
> state, the 
> > > RESPONSE contains also an INFO object with Success, Reservation 
> > > succesful.
> > > 
> > > It would be helpful to make a difference between Reservation 
> > > succesful and Refresh succesful. In case of Refresh succesful, 
> > > there's no need to tear down the reservation on the old path. In 
> > > case of Reservation succesful it might be. When link (1) 
> still fails 
> > > the teardown message would timeout in this example.
> > > 
> > > What do you think?
> > > 
> > > Bernd
> > > 
> > > 
> > > 
> > > 
> > > Jukka MJ Manner wrote:
> > > 
> > > > Dear all,
> > > >
> > > > I sent the following request for feedback two weeks ago. No 
> > > > comments have been raised. I will wait until this 
> Friday, then submit the draft.
> > > >
> > > > Jukka
> > > >
> > > > On Tue, 21 Nov 2006, Jukka MJ Manner wrote:
> > > >
> > > >
> > > > > Hi all,
> > > > >
> > > > > I have done all the edits I had in my list to the QoS 
> NSLP spec, 
> > > > > the main points are in recent thread with Roland. 
> From the url 
> > > > > below you can find the current draft v. "13-pre1" and 
> a diff to v. 12.
> > > > >
> > > > > http://www.cs.helsinki.fi/u/jmanner/qos-nslp/
> > > > >
> > > > > A direct link to the diff:
> > > > >
> > > > > 
> http://www.cs.helsinki.fi/u/jmanner/qos-nslp/draft-ietf-nsis-qos
> > > > > -nslp-12-from-3-pre1.diff.html
> > > > >
> > > > >
> > > > >
> > > > > I would appreciate comments on the changes I did 
> (what is wrong, 
> > > > > what I missed, etc.).
> > > > >
> > > > >
> > > > > I still have one problem with the spec, namely the 
> way the NSLP 
> > > > > suggests to handle mobility and path changes. I think 
> we need to 
> > > > > review that statement, because it seems like a "hack" 
> (playing 
> > > > > with the RSN value), and not really useful. And the 
> interactions with GIST look partly wrong.
> > > > > The folks working on the mobility draft (me included) could 
> > > > > comment. The section I'm talking about is 3.2.10, especially 
> > > > > 3.2.10.2, in the v.12 draft.
> > > > >
> > > > > BR,
> > > > > Jukka
> > > > >
> > >>> _______________________________________________
> > > > > nsis mailing list
> > > > > nsis@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/nsis
> > > > >
> > > >
> > > >
> > >> _______________________________________________
> > > > nsis mailing list
> > > > nsis@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/nsis
> > > 
> > > 
> > > _______________________________________________
> > > nsis mailing list
> > > nsis@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/nsis
> > > 
> > 
> > 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 



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



From nsis-bounces@ietf.org Thu Dec 21 09:26:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxOsF-0008Qs-Hm; Thu, 21 Dec 2006 09:26:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxOsD-0008Pt-8D
	for nsis@ietf.org; Thu, 21 Dec 2006 09:26:17 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxOpJ-0001g4-Ea
	for nsis@ietf.org; Thu, 21 Dec 2006 09:23:23 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kBLELo5v022863; Thu, 21 Dec 2006 15:21:59 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>, <nsis@ietf.org>
Date: Thu, 21 Dec 2006 15:21:46 +0100
Message-ID: <001c01c7250b$5e88cc80$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC805E@KCCLUST06EVS1.ugd.att.com>
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8g
X-Spam-Score: 0.4 () FVGT_s_OBFU_Q1,FVGT_u_HAS_2LETTERFLDR
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Thu, 21 Dec 2006 15:22:01 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d2fdecab7a7fa796e06e001d026c91
Cc: 'Lars Westberg' <Lars.westberg@ericsson.com>,
	=?us-ascii?Q?'Attila_Bader_=28IJ/ETH=29'?= <attila.bader@ericsson.com>
Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
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

Hi Jerry

Please see below! I have severe concerns about some changes that have been
done
in the QSPEC template draft.

> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> Sent: woensdag 20 december 2006 14:20
> To: Georgios Karagiannis; nsis@ietf.org
> Cc: Ash, Gerald R (Jerry), ALABS
> Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt 
> 
> Hi Georgios,
> 
> See below. 
> 
> > -----Original Message-----
> > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > Sent: Wednesday, December 20, 2006 5:26 AM
> > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > Subject: Comments on draft-ietf-nsis-qspec-13.txt
> > 
> > Hi Jerry
> > 
> > Here are my comments on draft-ietf-nsis-qspec-13.txt:
> > 
> > Comment_1:
> > --------------
> > Please reinclude the concept of QSPEC control information that was 
> > included in all previous versions of the QSPEC template draft.
> > In
> > 
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this 
> > concept was described in Section 5.1.
> 
> Please see previous email comment on QSPEC control information.

Georgios: 
In order to emphasize the need of having QSPEC control information 
parameters  I  would however appreciate if the name of Section 4.3.3 is
changed
From:
4.3.3 Traffic Handling Directives
INTO:
4.3.3 QSPEC control information


> 
> > Comment_2:
> > -----------
> > 
> > Section 6.1:
> > Please reintroduce the format that is required in order to 
> specify the 
> > QSPEC control information, see:
> > Section 7.1 of:
> > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
> 
> Please see previous email comment on QSPEC control information.


Georgios: If you rename section 4.3.3 to QSPEC control information then I
think that reformatting 
of section 6.1 is not needed.
Please add the proposed sentence by Dave (but change the term "handling
directives" to "QSPEC control 
Information"). I am not sure where it is better to add this sentence, maybe
in Section 5.4.

"QoSMs are free, subject to IANA registration and review rules, to extend
QSPECs by adding parameters of any of the kinds supported by the standard
QSPEC. This includes traffic description parameters, constraint parameters
and QSPEC control information. QoSMs are not permitted, however, to
reinterpret or redefine the standard QSPEC parameters specified in this
document"
 

> > Comment_3:
> > ----------
> > Section 4.1 :QoS Models
> > The definition of the QoS model is not complete. An 
> important sentence 
> > that was used in the previous version of the draft is removed.
> > Please add the following sentence to the definition of the 
> QoS Model 
> > (QOSM):
> > 
> > The same as described above have to be applied in this section.
> > After the following sentence:
> > 
> > "A QOSM specification MAY include the following:"
> > 
> > include the following bullet:
> > "- it specifies how to use QOS NSLP to signal for this QOSM"
> 
> That sentence was removed in Dave's proposed QOSM 
> re-definition, see 
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
> ml.  It was unclear what that sentence meant, QoS-NSLP 
> specifies how to signal, not QOSM specifications, so the 
> sentence was removed.  
> 
> I believe the sentence was intended to mean that when QoS 
> NSLP allows various options to be selected, a QOSM should be 
> able to determine which option is used.  For that purpose the 
> following sentence was added in Section 4.1:
> 
> "     A QOSM specification MAY include the following:
>      ...
>      - can state which QoS-NSLP options a QOSM wants to use, when
>      several options are available for a QOSM (e.g., local QSPEC to
>      either be a) tunneled or b) encapsulate initiator QSPEC)."
> 
> Also, to avoid any misinterpretation that QOSMs are free to 
> specify additional constraints, state machines, protocol 
> data, etc. for NSLP beyond that which is specific in the QoS 
> NSLP specification, the following was added to Section 4.1:
> 
> "  QOSMs affect the operation of the RMF in NSIS-capable nodes, the
>    information carried in QSPEC objects, and may under some
>    circumstances (e.g. aggregation) cause a separate NSLP 
> session to be
>    instantiated by having the RMF as a QNI. QOSMs all utilize 
> the common
>    data, state machines, and APIs of the underlying NSIS protocols and
>    are not expected to re-define or extend these in any way."

Georgios:
Regarding the sentence in Section 4.1:
"QOSMs all utilize 
the common data, state machines, and APIs of the underlying NSIS protocols
and
are not expected to re-define or extend these in any way."

This sentence restricts the possibility of QoS model to use RMF states and
data 
that are not been defined in neither QoS-NSLP or QSPEC.
This sentence should be removed.




 
> > Comment_4:
> > -------------
> > Section 5.1 Local QSPEC definition and processing
> > 
> > By reading this section it gives the impression that the 
> two methods 
> > a) and b) cannot be used by the same QoS model.
> > Method a): translate the
> >    initiator QSPEC into a local QSPEC and encapsulate the initiator
> >    QSPEC in the RESERVE message
> > Method b): b) tunnel the initiator QSPEC
> >    through the local domain and reserve resources by 
> generating a new
> >    RESERVE message through the local domain containing the local 
> > QSPEC.
> > 
> > Note that according to the discussions that we have had until now 
> > method a) should be able to be used in combination with 
> method b) by 
> > the same QoS model for the situation that the local QSPEC 
> encapsulates 
> > the initiator QSPEC in order to satisfy requirement 5.4.2 that is 
> > specified in RFC 3726, see:
> > http://www.ietf.org/rfc/rfc3726.txt
> > 
> > Please add the following sentence at the end of the first 
> paragraph of 
> > Section 5.1.
> > "Note that when method b) is used, the encapsulation of the 
> initiator 
> > QSPEC into a local QSPEC should also be possible when the local QoS 
> > model needs to satisfy Requirement
> > 5.4.2 specified in RFC 3726, by adding and removing local 
> > QOSM-specific Control Information parameters on top of the 
> initiator 
> > QSPEC."
> 
> Your comment here is not clear to me.  It would help to 
> provide an example to illustrate what you are trying to 
> accomplish.  It seems that you are trying to specify QoS-NSLP 
> functionality, rather than QSPEC functionality.  If so, that 
> functionality should be specified in the QoS-NSLP draft 
> rather than the QSPEC draft, perhaps the QoS-NSLP authors can comment.

Georgios:
No I am not trying to define QOS-NSLP functionality.
This is realted to QSPOEC control informtaion that has to be carried 
by end-to-end messages.
What I am trying to say is that all the discussion that we have had 
regarding the encapsulation of the QSEPC object were associated 
with requiremet 5.4.2 of RFC 3726, see below:

-----------------
"5.4.2.  It SHOULD be Possible to Add and Remove Local Domain Information

   It SHOULD be possible to add and remove local scope elements.
   Compared to Requirement 5.3.5 this requirement does use the normal
   signaling process and message exchange for transporting local
   information.  For example, at the entrance to a domain, domain-
   specific information is added information is added, which is used in
   this domain only, and the information is removed again when a
   signaling message leaves the domain.  The motivation is in the
   economy of re-using the protocol for domain internal signaling of
   various information pieces.  Where additional information is needed
   within a particular domain, it should be possible to carry this at
   the same time as the end-to-end information.", from RFC 3726
------------------
Thus what I am saying is:
Please add the following sentence at the end of the first paragraph 
of Section 5.1.

"Note that when method b) is used, the encapsulation of the 
initiator QSPEC into a local QSPEC should also be possible 
when the local QoS model needs to satisfy Requirement 
5.4.2 specified in RFC 3726, by adding and removing local 
QOSM-specific Control Information parameters on top of the 
initiator QSPEC."


> 
> > Comment_5:
> > -----------
> > Section 5.1, last paragraph:
> > 
> > Please change the following:
> > "For example, RMD can define a local QSPEC that contains TMOD = 
> > bandwidth (sets r=p, b/m to large)."
> > 
> > Into:
> > "For example, in RMD the TMOD parameters contained in the original 
> > initiator QSPEC are mapped into the equivalent TMOD parameter 
> > representing only the peak bandwidth in the local QSPEC."
> 
> OK with me.
> 
> > Comment_6:
> > -------------
> > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to be followed 
> > regarding the QSPEC control information are not given:
> > 
> > Please include the following paragraph at the end of this section:
> > "Regarding QSPEC Control Information, the default rule is that all
> >    QSPEC parameters that have been included in the RESERVE 
> message by
> >    the QNI are also included in the RESPONSE message by the 
> QNR with 
> > the
> >    value they had when arriving at the QNR.  When traveling in the
> >    RESPONSE message, all QSPEC Control Information parameters are
> >    read-only.  Note that a QOSM specification may define its own
> >    QOSM-specific Control Information parameters and 
> processing rules."
> 
> Please see previous email comment on QSPEC control information.


Georgios: I think that a description of how the QSPEC control information is
handled 
is needed.

> > Comment_7:
> > ------------
> > Section 6.1:
> > I do not understand the second sentence from the below two 
> sentences:
> > "N Flag: Not-supported QSPEC parameter flag (see Section 5.2.2).
> >            For QSPEC parameters the value of this flag is always 
> > zero."
> 
> Good catch, this is a typo, the sentence should be removed.
> 


Best Regards,
Georgios



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



From nsis-bounces@ietf.org Thu Dec 21 22:56:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxbVY-0006qU-Co; Thu, 21 Dec 2006 22:55:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxbVW-0006qM-Uf
	for nsis@ietf.org; Thu, 21 Dec 2006 22:55:42 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxbVU-0005yc-By
	for nsis@ietf.org; Thu, 21 Dec 2006 22:55:42 -0500
Received: from webmail.cs.utwente.nl (janus.ewi.utwente.nl [130.89.10.26])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with SMTP id kBM3tZlv018053
	for <nsis@ietf.org>; Fri, 22 Dec 2006 04:55:35 +0100 (MET)
Received: from 84.82.109.231 (auth. user karagian@imap2.cs.utwente.nl)
	by webmail.cs.utwente.nl with HTTP; Fri, 22 Dec 2006 03:55:34 +0000
To: nsis@ietf.org
Date: Fri, 22 Dec 2006 03:55:33 +0000
X-Mailer: IlohaMail/0.8.13 (On: webmail.cs.utwente.nl)
Message-ID: <zR6nrG1z.1166759733.7707530.karagian@ewi.utwente.nl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Bounce-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
MIME-Version: 1.0 
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0 () 
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Fri, 22 Dec 2006 04:55:35 +0100 (MET)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Subject: [NSIS] severe change on QoS Model definition and capabilities
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

Hi all

Version 13 of the QSPEC template draft introduces a severe change in the
capabilities and definition of a QoS Model.
This implies that a lot of work that has been done until now on QoS
models might be considered to be useless.

These changes are related to the following text that is included in
Section 4.1 of version 13 of the QSPEC template draft:

"QOSMs affect the operation of the RMF in NSIS-capable nodes, the
   information carried in QSPEC objects, and may under some
   circumstances (e.g. aggregation) cause a separate NSLP session to be
   instantiated by having the RMF as a QNI. QOSMs all utilize the common
   data, state machines, and APIs of the underlying NSIS protocols and
   are not expected to re-define or extend these in any way.", from
draft-ietf-nsis-qspec-13.txt

The changes are also related to the fact that the following QoS Model
capability that was supported by all the previous versions of the QSPEC
template draft is currently removed:
"- it specifies how to use QOS NSLP to signal for this QOSM"


My proposal is to either reuse the QoS model definition (including
apabilities) that was given in the previous versions of the QSPEC
template draft or use the following QoS Model definition that is
currently given in the QOS-NSLP draft.
Anyway, I believe that the QoS-NSLP draft is responsible on specifying
what a QoS model is allowed to do and not the QSPEC template draft.

---------

"3.1.2.  QoS Models and QoS Specifications

   The QoS NSLP provides flexibility over the exact patterns of
   signaling messages that are exchanged. The decoupling of QoS NSLP and
   QSPEC allows the QoS NSLP to be ignorant about the ways in which
   traffic, resources, etc. are described, and it can treat the QSPEC as
   an opaque object.  Various QoS models can be designed, and these do
   not affect the specification of the QoS NSLP protocol. Only the RMF
   specific to a given QoS model will need to interpret the QSPEC.  The
   Resource Management Function (RMF) reserves resources for each flow.

   An ongoing effort attempts to specify a QSPEC template [I-D.ietf-
   nsis-qspec]. The QSPEC template contains object formats for generally
   useful elements of the QoS description, which is designed to ensure
   interoperability when using the basic set of objects.

   The QSPEC fulfills a similar purpose to the TSpec, RSpec and AdSpec
   objects used with RSVP and specified in RFC 2205 [RFC2205] and RFC
   2210 [RFC2210]. At each QNE, the content of the QSPEC is interpreted
   by the Resource Management Function and the Policy Control Function
   for the purposes of traffic and policy control (including admission
   control and configuration of the packet classifier and scheduler).

   The QoS NSLP does not mandate any particular behavior for the RMF,
   instead providing interoperability at the signaling protocol level
   whilst leaving the validation of RMF behavior to contracts external
   to the protocol itself. The RMF may make use of various elements from
   the QoS NSLP message, not only the QSPEC object.

   Still, this specification assumes that resource sharing is possible
   between flows with the same SESSION_ID that originate from the same
   QNI or between flows with a different SESSION_ID that are related
   through the BOUND_SESSION_ID object. For flows with the same
   SESSION_ID, resource sharing is only applicable when the existing
   reservation is not just replaced (which is indicated by the REPLACE
   flag in the common header. We assume that the QoS model supports
   resource sharing between flows. A QoS Model may elect to implement a
   more general behavior of supporting relative operations on existing
   reservations, such as ADDING or SUBTRACTING a certain amount of
   resources from the current reservation. A QoS Model may also elect to
   allow resource sharing more generally, e.g., between all flows with
   the same DSCP.

   The QSPEC carries a collection of objects that can describe QoS
   specifications in a number of different ways. A generic template is
   defined in [I-D.ietf-nsis-qspec]. A QSPEC describing the resources
   requested will usually contain objects which need to be understood by
   all implementations, and it can also be enhanced with additional
   objects specific to a QoS model to provide a more exact definition to
   the RMF, which may be better able to use its specific resource
   management mechanisms (which may, e.g., be link specific) as a
   result.

  A QoS Model defines the behavior of the RMF, including inputs and
   outputs, and how QSPEC information is used to describe resources
   available, resources required, traffic descriptions, and control
   information required by the RMF. A QoS Model also describes the
   minimum set of parameters QNEs should use in the QSPEC when signaling
   about this QoS Model.

   QoS Models may be local (private to one network), implementation/
   vendor specific, or global (implementable by different networks and
   vendors).  All QSPECs must follow the QSPEC template [I-D.ietf-nsis-
   qspec].

   The definition of a QoS model may also have implications on how local
   behavior should be implemented in the areas where the QoS NSLP gives
   freedom to implementers. For example, it may be useful to identify
   recommended behavior for how a RESERVE message that is forwarded
   relates to that received, or when additional signaling sessions
   should be started based on existing sessions, such as required for
   aggregate reservations. In some cases, suggestions may be made on
   whether state that may optionally be retained should be held in
   particular scenarios.  A QoS model may specify reservation
   preemption, e.g., an incoming resource request may cause removal of
   an earlier reservation." from draft-ietf-nsis-qos-nslp-12.txt.

Best Regards,
Georgios

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



From nsis-bounces@ietf.org Thu Dec 21 23:20:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxbtJ-0003uF-IG; Thu, 21 Dec 2006 23:20:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxbtI-0003uA-R3
	for nsis@ietf.org; Thu, 21 Dec 2006 23:20:16 -0500
Received: from mclmx.mail.saic.com ([149.8.64.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxbtI-000128-4c
	for nsis@ietf.org; Thu, 21 Dec 2006 23:20:16 -0500
Received: from 0015-its-ieg01.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx.mail.saic.com; Thu, 21 Dec 2006 23:20:00 -0500
Received: from 0015-ITS-EXBH01.us.saic.com ([10.43.229.18])
	by 0015-its-ieg01.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006122123200030132 ; Thu, 21 Dec 2006 23:20:00 -0500
Received: from 0591-ITS-EXMP02.us.saic.com ([10.42.81.248]) by
	0015-ITS-EXBH01.us.saic.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Dec 2006 23:20:01 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [NSIS] severe change on QoS Model definition and capabilities
Date: Thu, 21 Dec 2006 23:20:00 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426E1CF71@0591-ITS-EXMP02.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] severe change on QoS Model definition and capabilities
Thread-Index: AcclfUNVwdLIjf6lRe+zDrpbq1NzzAAAI6i3
References: <zR6nrG1z.1166759733.7707530.karagian@ewi.utwente.nl>
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: "Georgios Karagiannis" <karagian@cs.utwente.nl>,
    <nsis@ietf.org>
X-OriginalArrivalTime: 22 Dec 2006 04:20:01.0010 (UTC)
	FILETIME=[727BB520:01C72580]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: d8921dd2ebcb07edebf7bfaf4808c2ad
Cc: 
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>
Content-Type: multipart/mixed; boundary="===============1908981994=="
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1908981994==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C72580.721FBD14"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C72580.721FBD14
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Georgios:
=20
Definitely, you have raised the most important point. Again, it is not =
an isolated case. I agree with you.
=20
Let me rephrase it. What is this QSPEC draft for? Is it not a template =
of QOS parameters? If it is so, why does it deal with how a OQS model =
should use this QSPEC template does not have any knowledge how a QOS =
model works or how QOS-NSLP will instruct QOS models to use the QSPEC =
template based on the circumstances (e.g., applications' needs, =
networks' needs, etc.)?
=20
Now, you can see why we are saying that this draft must NOT deal with =
any extensions of any parameters for using by any specific QOS SLAs like =
so-called non-standard Y.1451, DSTE, etc.
=20
More is coming on this ...
=20
Thanks to you for reading this highly confused and technically =
inconsistent draft so carefully. More importantly, when people want to =
mix between "apples" and "oranges" using brutal force ignoring all =
technical justification just because they have been the EDITORs (God =
knows why still they want to be the editors!!!) for the last couple of =
years, it will end like this.
=20
Best regards,
Radhika
=20
PS:=20
=20
1. There is also a new term "standard QSPEC." We will talk about this =
later as well.
=20
2. We will talk about: What a QOS model is and what are its properties. =
Do Y.1451 and DSTE QOS SLA have the same properties like those of RSVP, =
DiffServ, and IntServ?
=20
3. Do they use the brute force through technical misinterpretation of =
the very QOS model definition so that "apples" and "oranges" can be =
mixed?

________________________________

From: nsis-bounces@ietf.org on behalf of Georgios Karagiannis
Sent: Thu 12/21/2006 10:55 PM
To: nsis@ietf.org
Subject: [NSIS] severe change on QoS Model definition and capabilities



Hi all

Version 13 of the QSPEC template draft introduces a severe change in the
capabilities and definition of a QoS Model.
This implies that a lot of work that has been done until now on QoS
models might be considered to be useless.

These changes are related to the following text that is included in
Section 4.1 of version 13 of the QSPEC template draft:

"QOSMs affect the operation of the RMF in NSIS-capable nodes, the
   information carried in QSPEC objects, and may under some
   circumstances (e.g. aggregation) cause a separate NSLP session to be
   instantiated by having the RMF as a QNI. QOSMs all utilize the common
   data, state machines, and APIs of the underlying NSIS protocols and
   are not expected to re-define or extend these in any way.", from
draft-ietf-nsis-qspec-13.txt

The changes are also related to the fact that the following QoS Model
capability that was supported by all the previous versions of the QSPEC
template draft is currently removed:
"- it specifies how to use QOS NSLP to signal for this QOSM"


My proposal is to either reuse the QoS model definition (including
apabilities) that was given in the previous versions of the QSPEC
template draft or use the following QoS Model definition that is
currently given in the QOS-NSLP draft.
Anyway, I believe that the QoS-NSLP draft is responsible on specifying
what a QoS model is allowed to do and not the QSPEC template draft.

---------

"3.1.2.  QoS Models and QoS Specifications

   The QoS NSLP provides flexibility over the exact patterns of
   signaling messages that are exchanged. The decoupling of QoS NSLP and
   QSPEC allows the QoS NSLP to be ignorant about the ways in which
   traffic, resources, etc. are described, and it can treat the QSPEC as
   an opaque object.  Various QoS models can be designed, and these do
   not affect the specification of the QoS NSLP protocol. Only the RMF
   specific to a given QoS model will need to interpret the QSPEC.  The
   Resource Management Function (RMF) reserves resources for each flow.

   An ongoing effort attempts to specify a QSPEC template [I-D.ietf-
   nsis-qspec]. The QSPEC template contains object formats for generally
   useful elements of the QoS description, which is designed to ensure
   interoperability when using the basic set of objects.

   The QSPEC fulfills a similar purpose to the TSpec, RSpec and AdSpec
   objects used with RSVP and specified in RFC 2205 [RFC2205] and RFC
   2210 [RFC2210]. At each QNE, the content of the QSPEC is interpreted
   by the Resource Management Function and the Policy Control Function
   for the purposes of traffic and policy control (including admission
   control and configuration of the packet classifier and scheduler).

   The QoS NSLP does not mandate any particular behavior for the RMF,
   instead providing interoperability at the signaling protocol level
   whilst leaving the validation of RMF behavior to contracts external
   to the protocol itself. The RMF may make use of various elements from
   the QoS NSLP message, not only the QSPEC object.

   Still, this specification assumes that resource sharing is possible
   between flows with the same SESSION_ID that originate from the same
   QNI or between flows with a different SESSION_ID that are related
   through the BOUND_SESSION_ID object. For flows with the same
   SESSION_ID, resource sharing is only applicable when the existing
   reservation is not just replaced (which is indicated by the REPLACE
   flag in the common header. We assume that the QoS model supports
   resource sharing between flows. A QoS Model may elect to implement a
   more general behavior of supporting relative operations on existing
   reservations, such as ADDING or SUBTRACTING a certain amount of
   resources from the current reservation. A QoS Model may also elect to
   allow resource sharing more generally, e.g., between all flows with
   the same DSCP.

   The QSPEC carries a collection of objects that can describe QoS
   specifications in a number of different ways. A generic template is
   defined in [I-D.ietf-nsis-qspec]. A QSPEC describing the resources
   requested will usually contain objects which need to be understood by
   all implementations, and it can also be enhanced with additional
   objects specific to a QoS model to provide a more exact definition to
   the RMF, which may be better able to use its specific resource
   management mechanisms (which may, e.g., be link specific) as a
   result.

  A QoS Model defines the behavior of the RMF, including inputs and
   outputs, and how QSPEC information is used to describe resources
   available, resources required, traffic descriptions, and control
   information required by the RMF. A QoS Model also describes the
   minimum set of parameters QNEs should use in the QSPEC when signaling
   about this QoS Model.

   QoS Models may be local (private to one network), implementation/
   vendor specific, or global (implementable by different networks and
   vendors).  All QSPECs must follow the QSPEC template [I-D.ietf-nsis-
   qspec].

   The definition of a QoS model may also have implications on how local
   behavior should be implemented in the areas where the QoS NSLP gives
   freedom to implementers. For example, it may be useful to identify
   recommended behavior for how a RESERVE message that is forwarded
   relates to that received, or when additional signaling sessions
   should be started based on existing sessions, such as required for
   aggregate reservations. In some cases, suggestions may be made on
   whether state that may optionally be retained should be held in
   particular scenarios.  A QoS model may specify reservation
   preemption, e.g., an incoming resource request may cause removal of
   an earlier reservation." from draft-ietf-nsis-qos-nslp-12.txt.

Best Regards,
Georgios

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



------_=_NextPart_001_01C72580.721FBD14
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>[NSIS] severe change on QoS Model =
definition and capabilities</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText29418 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>Georgios:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Definitely, you have raised =
the most important point. Again, it is not an isolated case. I agree =
with you.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Let me rephrase it. What is =
this QSPEC draft for? Is it not a template of QOS parameters? If it is =
so, why does it deal with how a OQS model should use this QSPEC template =
does not have any knowledge how a QOS model works or how QOS-NSLP will =
instruct QOS models to use the QSPEC template based on the circumstances =
(e.g., applications' needs, networks' needs, etc.)?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Now, you can see why we are =
saying that this draft must NOT deal with any extensions of any =
parameters for using by any specific QOS SLAs like so-called =
non-standard Y.1451, DSTE, etc.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>More is coming on this =
...</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Thanks to you for reading =
this highly confused and technically inconsistent draft so carefully. =
More importantly, when people want to mix between "apples" and "oranges" =
using brutal force ignoring all technical justification just because =
they have been the EDITORs (God knows why still they want to be the =
editors!!!) for the last couple of years, it will end like =
this.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Best regards,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Radhika</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>PS: </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>1. There is also a new term =
"standard QSPEC." We will talk about this later as well.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>2. We will talk about: What a =
QOS model is and what are its properties.&nbsp;Do Y.1451 and =
DSTE&nbsp;QOS SLA have the same properties like those of RSVP, DiffServ, =
and IntServ?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>3. Do they use the brute =
force through technical misinterpretation of&nbsp;the very QOS model =
definition so that "apples" and "oranges" can be =
mixed?</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> nsis-bounces@ietf.org on =
behalf of Georgios Karagiannis<BR><B>Sent:</B> Thu 12/21/2006 10:55 =
PM<BR><B>To:</B> nsis@ietf.org<BR><B>Subject:</B> [NSIS] severe change =
on QoS Model definition and capabilities<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Hi all<BR><BR>Version 13 of the QSPEC template draft =
introduces a severe change in the<BR>capabilities and definition of a =
QoS Model.<BR>This implies that a lot of work that has been done until =
now on QoS<BR>models might be considered to be useless.<BR><BR>These =
changes are related to the following text that is included in<BR>Section =
4.1 of version 13 of the QSPEC template draft:<BR><BR>"QOSMs affect the =
operation of the RMF in NSIS-capable nodes, the<BR>&nbsp;&nbsp; =
information carried in QSPEC objects, and may under some<BR>&nbsp;&nbsp; =
circumstances (e.g. aggregation) cause a separate NSLP session to =
be<BR>&nbsp;&nbsp; instantiated by having the RMF as a QNI. QOSMs all =
utilize the common<BR>&nbsp;&nbsp; data, state machines, and APIs of the =
underlying NSIS protocols and<BR>&nbsp;&nbsp; are not expected to =
re-define or extend these in any way.", =
from<BR>draft-ietf-nsis-qspec-13.txt<BR><BR>The changes are also related =
to the fact that the following QoS Model<BR>capability that was =
supported by all the previous versions of the QSPEC<BR>template draft is =
currently removed:<BR>"- it specifies how to use QOS NSLP to signal for =
this QOSM"<BR><BR><BR>My proposal is to either reuse the QoS model =
definition (including<BR>apabilities) that was given in the previous =
versions of the QSPEC<BR>template draft or use the following QoS Model =
definition that is<BR>currently given in the QOS-NSLP draft.<BR>Anyway, =
I believe that the QoS-NSLP draft is responsible on specifying<BR>what a =
QoS model is allowed to do and not the QSPEC template =
draft.<BR><BR>---------<BR><BR>"3.1.2.&nbsp; QoS Models and QoS =
Specifications<BR><BR>&nbsp;&nbsp; The QoS NSLP provides flexibility =
over the exact patterns of<BR>&nbsp;&nbsp; signaling messages that are =
exchanged. The decoupling of QoS NSLP and<BR>&nbsp;&nbsp; QSPEC allows =
the QoS NSLP to be ignorant about the ways in which<BR>&nbsp;&nbsp; =
traffic, resources, etc. are described, and it can treat the QSPEC =
as<BR>&nbsp;&nbsp; an opaque object.&nbsp; Various QoS models can be =
designed, and these do<BR>&nbsp;&nbsp; not affect the specification of =
the QoS NSLP protocol. Only the RMF<BR>&nbsp;&nbsp; specific to a given =
QoS model will need to interpret the QSPEC.&nbsp; The<BR>&nbsp;&nbsp; =
Resource Management Function (RMF) reserves resources for each =
flow.<BR><BR>&nbsp;&nbsp; An ongoing effort attempts to specify a QSPEC =
template [I-D.ietf-<BR>&nbsp;&nbsp; nsis-qspec]. The QSPEC template =
contains object formats for generally<BR>&nbsp;&nbsp; useful elements of =
the QoS description, which is designed to ensure<BR>&nbsp;&nbsp; =
interoperability when using the basic set of =
objects.<BR><BR>&nbsp;&nbsp; The QSPEC fulfills a similar purpose to the =
TSpec, RSpec and AdSpec<BR>&nbsp;&nbsp; objects used with RSVP and =
specified in RFC 2205 [RFC2205] and RFC<BR>&nbsp;&nbsp; 2210 [RFC2210]. =
At each QNE, the content of the QSPEC is interpreted<BR>&nbsp;&nbsp; by =
the Resource Management Function and the Policy Control =
Function<BR>&nbsp;&nbsp; for the purposes of traffic and policy control =
(including admission<BR>&nbsp;&nbsp; control and configuration of the =
packet classifier and scheduler).<BR><BR>&nbsp;&nbsp; The QoS NSLP does =
not mandate any particular behavior for the RMF,<BR>&nbsp;&nbsp; instead =
providing interoperability at the signaling protocol =
level<BR>&nbsp;&nbsp; whilst leaving the validation of RMF behavior to =
contracts external<BR>&nbsp;&nbsp; to the protocol itself. The RMF may =
make use of various elements from<BR>&nbsp;&nbsp; the QoS NSLP message, =
not only the QSPEC object.<BR><BR>&nbsp;&nbsp; Still, this specification =
assumes that resource sharing is possible<BR>&nbsp;&nbsp; between flows =
with the same SESSION_ID that originate from the same<BR>&nbsp;&nbsp; =
QNI or between flows with a different SESSION_ID that are =
related<BR>&nbsp;&nbsp; through the BOUND_SESSION_ID object. For flows =
with the same<BR>&nbsp;&nbsp; SESSION_ID, resource sharing is only =
applicable when the existing<BR>&nbsp;&nbsp; reservation is not just =
replaced (which is indicated by the REPLACE<BR>&nbsp;&nbsp; flag in the =
common header. We assume that the QoS model supports<BR>&nbsp;&nbsp; =
resource sharing between flows. A QoS Model may elect to implement =
a<BR>&nbsp;&nbsp; more general behavior of supporting relative =
operations on existing<BR>&nbsp;&nbsp; reservations, such as ADDING or =
SUBTRACTING a certain amount of<BR>&nbsp;&nbsp; resources from the =
current reservation. A QoS Model may also elect to<BR>&nbsp;&nbsp; allow =
resource sharing more generally, e.g., between all flows =
with<BR>&nbsp;&nbsp; the same DSCP.<BR><BR>&nbsp;&nbsp; The QSPEC =
carries a collection of objects that can describe QoS<BR>&nbsp;&nbsp; =
specifications in a number of different ways. A generic template =
is<BR>&nbsp;&nbsp; defined in [I-D.ietf-nsis-qspec]. A QSPEC describing =
the resources<BR>&nbsp;&nbsp; requested will usually contain objects =
which need to be understood by<BR>&nbsp;&nbsp; all implementations, and =
it can also be enhanced with additional<BR>&nbsp;&nbsp; objects specific =
to a QoS model to provide a more exact definition to<BR>&nbsp;&nbsp; the =
RMF, which may be better able to use its specific =
resource<BR>&nbsp;&nbsp; management mechanisms (which may, e.g., be link =
specific) as a<BR>&nbsp;&nbsp; result.<BR><BR>&nbsp; A QoS Model defines =
the behavior of the RMF, including inputs and<BR>&nbsp;&nbsp; outputs, =
and how QSPEC information is used to describe resources<BR>&nbsp;&nbsp; =
available, resources required, traffic descriptions, and =
control<BR>&nbsp;&nbsp; information required by the RMF. A QoS Model =
also describes the<BR>&nbsp;&nbsp; minimum set of parameters QNEs should =
use in the QSPEC when signaling<BR>&nbsp;&nbsp; about this QoS =
Model.<BR><BR>&nbsp;&nbsp; QoS Models may be local (private to one =
network), implementation/<BR>&nbsp;&nbsp; vendor specific, or global =
(implementable by different networks and<BR>&nbsp;&nbsp; vendors).&nbsp; =
All QSPECs must follow the QSPEC template =
[I-D.ietf-nsis-<BR>&nbsp;&nbsp; qspec].<BR><BR>&nbsp;&nbsp; The =
definition of a QoS model may also have implications on how =
local<BR>&nbsp;&nbsp; behavior should be implemented in the areas where =
the QoS NSLP gives<BR>&nbsp;&nbsp; freedom to implementers. For example, =
it may be useful to identify<BR>&nbsp;&nbsp; recommended behavior for =
how a RESERVE message that is forwarded<BR>&nbsp;&nbsp; relates to that =
received, or when additional signaling sessions<BR>&nbsp;&nbsp; should =
be started based on existing sessions, such as required =
for<BR>&nbsp;&nbsp; aggregate reservations. In some cases, suggestions =
may be made on<BR>&nbsp;&nbsp; whether state that may optionally be =
retained should be held in<BR>&nbsp;&nbsp; particular scenarios.&nbsp; A =
QoS model may specify reservation<BR>&nbsp;&nbsp; preemption, e.g., an =
incoming resource request may cause removal of<BR>&nbsp;&nbsp; an =
earlier reservation." from draft-ietf-nsis-qos-nslp-12.txt.<BR><BR>Best =
Regards,<BR>Georgios<BR><BR>_____________________________________________=
__<BR>nsis mailing list<BR>nsis@ietf.org<BR><A =
href=3D"https://www1.ietf.org/mailman/listinfo/nsis">https://www1.ietf.or=
g/mailman/listinfo/nsis</A><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C72580.721FBD14--


--===============1908981994==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1908981994==--




From nsis-bounces@ietf.org Thu Dec 21 23:36:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gxc8H-0001vJ-DX; Thu, 21 Dec 2006 23:35:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxc8G-0001vE-3a
	for nsis@ietf.org; Thu, 21 Dec 2006 23:35:44 -0500
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gxc8E-0003HH-KY
	for nsis@ietf.org; Thu, 21 Dec 2006 23:35:44 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kBM4Yea8004547; Fri, 22 Dec 2006 06:35:00 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Dec 2006 06:35:15 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Dec 2006 06:35:14 +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
Subject: RE: [NSIS] severe change on QoS Model definition and capabilities
Date: Fri, 22 Dec 2006 06:35:13 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC019F01E7@esebe199.NOE.Nokia.com>
In-Reply-To: <zR6nrG1z.1166759733.7707530.karagian@ewi.utwente.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] severe change on QoS Model definition and capabilities
Thread-Index: AcclfUMu3Q3OdwTOSj2SN/H3AwjIsQABS3KA
From: <john.loughney@nokia.com>
To: <karagian@cs.utwente.nl>, <nsis@ietf.org>
X-OriginalArrivalTime: 22 Dec 2006 04:35:14.0900 (UTC)
	FILETIME=[93344140:01C72582]
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: 
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

Georgios,

It might make some sense to attach some more technical reasoning
behind your request. =20

>Version 13 of the QSPEC template draft introduces a severe=20
>change in the capabilities and definition of a QoS Model.
>This implies that a lot of work that has been done until now=20
>on QoS models might be considered to be useless.

Can you explain why you think this?

John

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



From nsis-bounces@ietf.org Fri Dec 22 02:05:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxeSu-0004LW-Ba; Fri, 22 Dec 2006 02:05:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxeSs-0004LK-SS
	for nsis@ietf.org; Fri, 22 Dec 2006 02:05:10 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxeSr-00047A-E3
	for nsis@ietf.org; Fri, 22 Dec 2006 02:05:10 -0500
Received: from webmail.cs.utwente.nl (janus.ewi.utwente.nl [130.89.10.26])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with SMTP id kBM754lh023446;
	Fri, 22 Dec 2006 08:05:04 +0100 (MET)
Received: from 84.82.109.231 (auth. user karagian@imap2.cs.utwente.nl)
	by webmail.cs.utwente.nl with HTTP; Fri, 22 Dec 2006 07:05:03 +0000
To: "john.loughney@nokia.com" <john.loughney@nokia.com>,
	"nsis@ietf.org" <nsis@ietf.org>
Subject: RE: [NSIS] severe change on QoS Model definition and capabilities
Date: Fri, 22 Dec 2006 07:05:03 +0000
X-Mailer: IlohaMail/0.8.13 (On: webmail.cs.utwente.nl)
Message-ID: <V5A1EVYs.1166771103.8436620.karagian@ewi.utwente.nl>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC019F01E7@esebe199.NOE.Nokia.com>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Bounce-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
MIME-Version: 1.0 
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0 () 
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Fri, 22 Dec 2006 08:05:04 +0100 (MET)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: 
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

Hi John

I do not understand your question.
Do you mean that no change is introduced in the QSPEC template draft or
do you mean why should the until now supported QoS Model and
capabilities should comply with the ones given in the previous versions
of the QoS Template draft.

If you refer to the latter, I think that the QSPEC template draft authors
should give a technical reasoning for doing this severe change in the
QoS Model definition and capabilities.
Please note that the QoS Model definition and capabilities given in the
previous versions of the QSPEC template draft and the QoS-NSLP draft are
supported by the NSIS WG group until now!

Best Regards,
Georgios


On 12/22/2006, "john.loughney@nokia.com" <john.loughney@nokia.com>
wrote:

>Georgios,
>
>It might make some sense to attach some more technical reasoning
>behind your request.
>
>>Version 13 of the QSPEC template draft introduces a severe
>>change in the capabilities and definition of a QoS Model.
>>This implies that a lot of work that has been done until now
>>on QoS models might be considered to be useless.
>
>Can you explain why you think this?
>
>John
>
>_______________________________________________
>nsis mailing list
>nsis@ietf.org
>https://www1.ietf.org/mailman/listinfo/nsis

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



From nsis-bounces@ietf.org Fri Dec 22 09:01:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gxkxk-0004jz-GR; Fri, 22 Dec 2006 09:01:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxkxi-0004ii-QJ
	for nsis@ietf.org; Fri, 22 Dec 2006 09:01:26 -0500
Received: from mail146.messagelabs.com ([216.82.245.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gxkxe-0004l1-5n
	for nsis@ietf.org; Fri, 22 Dec 2006 09:01:26 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-13.tower-146.messagelabs.com!1166796081!7570264!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 6115 invoked from network); 22 Dec 2006 14:01:21 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-13.tower-146.messagelabs.com with SMTP;
	22 Dec 2006 14:01:21 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kBME1KfN021680; 
	Fri, 22 Dec 2006 09:01:20 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst12.ugd.att.com [135.38.164.89])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id
	kBME1Ebj021638; Fri, 22 Dec 2006 09:01:15 -0500 (EST)
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, 22 Dec 2006 08:01:14 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC806C@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <001c01c7250b$5e88cc80$4c0d5982@dynamic.ewi.utwente.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsA=
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "Georgios Karagiannis" <karagian@cs.utwente.nl>, <nsis@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 841b5d6ad57042632519d2198f34cc8d
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
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

Georgios,

See below.=20

> -----Original Message-----
> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]=20
> Sent: Thursday, December 21, 2006 9:22 AM
> To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
> Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt=20
>=20
> Hi Jerry
>=20
> Please see below! I have severe concerns about some changes=20
> that have been
> done
> in the QSPEC template draft.
>=20
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]=20
> > Sent: woensdag 20 december 2006 14:20
> > To: Georgios Karagiannis; nsis@ietf.org
> > Cc: Ash, Gerald R (Jerry), ALABS
> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt=20
> >=20
> > Hi Georgios,
> >=20
> > See below.=20
> >=20
> > > -----Original Message-----
> > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > Sent: Wednesday, December 20, 2006 5:26 AM
> > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
> > >=20
> > > Hi Jerry
> > >=20
> > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
> > >=20
> > > Comment_1:
> > > --------------
> > > Please reinclude the concept of QSPEC control information=20
> > > that was=20
> > > included in all previous versions of the QSPEC template draft.
> > > In
> > >=20
> >=20
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this=20
> > > concept was described in Section 5.1.
> >=20
> > Please see previous email comment on QSPEC control information.
>=20
> Georgios:=20
> In order to emphasize the need of having QSPEC control information=20
> parameters  I  would however appreciate if the name of=20
> Section 4.3.3 is
> changed
> From:
> 4.3.3 Traffic Handling Directives
> INTO:
> 4.3.3 QSPEC control information

The updated QSPEC parameter terminology/semantics are as suggested by
Dave Oran (see slides presented at IETF-67
http://www3.ietf.org/proceedings/06nov/index.html).  I think the current
terminology is more clear/descriptive of the QSPEC parameters so I don't
favor going backwards to less clear terminology.  I was never clear on
why we used the 'control information' terminology in the first place,
e.g., I don't think it's a very good descriptor of the 'excess
treatment' parameter.

Perhaps Dave can comment on this point also when he gets a chance.

> > > Comment_2:
> > > -----------
> > >=20
> > > Section 6.1:
> > > Please reintroduce the format that is required in order to=20
> > specify the=20
> > > QSPEC control information, see:
> > > Section 7.1 of:
> > > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
> >=20
> > Please see previous email comment on QSPEC control information.
>=20
>=20
> Georgios: If you rename section 4.3.3 to QSPEC control=20
> information then I
> think that reformatting=20
> of section 6.1 is not needed.
> Please add the proposed sentence by Dave (but change the term=20
> "handling
> directives" to "QSPEC control=20
> Information"). I am not sure where it is better to add this=20
> sentence, maybe
> in Section 5.4.
>=20
> "QoSMs are free, subject to IANA registration and review=20
> rules, to extend
> QSPECs by adding parameters of any of the kinds supported by=20
> the standard
> QSPEC. This includes traffic description parameters,=20
> constraint parameters
> and QSPEC control information. QoSMs are not permitted, however, to
> reinterpret or redefine the standard QSPEC parameters=20
> specified in this
> document"

Yes, the text suggested by Dave will be added.

> > > Comment_3:
> > > ----------
> > > Section 4.1 :QoS Models
> > > The definition of the QoS model is not complete. An=20
> > > important sentence=20
> > > that was used in the previous version of the draft is removed.
> > > Please add the following sentence to the definition of the=20
> > > QoS Model=20
> > > (QOSM):
> > >=20
> > > The same as described above have to be applied in this section.
> > > After the following sentence:
> > >=20
> > > "A QOSM specification MAY include the following:"
> > >=20
> > > include the following bullet:
> > > "- it specifies how to use QOS NSLP to signal for this QOSM"
> >=20
> > That sentence was removed in Dave's proposed QOSM=20
> > re-definition, see=20
> > http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
> > ml.  It was unclear what that sentence meant, QoS-NSLP=20
> > specifies how to signal, not QOSM specifications, so the=20
> > sentence was removed. =20
> >=20
> > I believe the sentence was intended to mean that when QoS=20
> > NSLP allows various options to be selected, a QOSM should be=20
> > able to determine which option is used.  For that purpose the=20
> > following sentence was added in Section 4.1:
> >=20
> > "     A QOSM specification MAY include the following:
> >      ...
> >      - can state which QoS-NSLP options a QOSM wants to use, when
> >      several options are available for a QOSM (e.g., local QSPEC to
> >      either be a) tunneled or b) encapsulate initiator QSPEC)."
> >=20
> > Also, to avoid any misinterpretation that QOSMs are free to=20
> > specify additional constraints, state machines, protocol=20
> > data, etc. for NSLP beyond that which is specific in the QoS=20
> > NSLP specification, the following was added to Section 4.1:
> >=20
> > "  QOSMs affect the operation of the RMF in NSIS-capable nodes, the
> >    information carried in QSPEC objects, and may under some
> >    circumstances (e.g. aggregation) cause a separate NSLP=20
> >    session to be
> >    instantiated by having the RMF as a QNI. QOSMs all utilize=20
> >    the common
> >    data, state machines, and APIs of the underlying NSIS=20
> >    protocols and
> >    are not expected to re-define or extend these in any way."
>=20
> Georgios:
> Regarding the sentence in Section 4.1:
> "QOSMs all utilize=20
> the common data, state machines, and APIs of the underlying=20
> NSIS protocols and
> are not expected to re-define or extend these in any way."
>=20
> This sentence restricts the possibility of QoS model to use=20
> RMF states and data=20
> that are not been defined in neither QoS-NSLP or QSPEC.
> This sentence should be removed.

I disagree.  The quoted text was introduced by Dave Oran in addition to
removing the phrase implying that a QOSM could specify signaling
protocol changes, and I agree with this.  Any changes/extensions to the
signaling protocol or state machines are within the scope of QoS-NSLP
draft and not the QSPEC draft or a QOSM specification draft.  I think
you have noted that also in your subsequent posting at
http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html. =20

If any extensions are required to the NSIS signaling protocol as a
result of the 'severe change on QoS Model definition and capabilities'
you have noted, those proposed changes/extensions should be addressed to
the QoS NSLP draft IMO.

Perhaps Dave can comment here also when he gets a chance.

> > > Comment_4:
> > > -------------
> > > Section 5.1 Local QSPEC definition and processing
> > >=20
> > > By reading this section it gives the impression that the=20
> > > two methods=20
> > > a) and b) cannot be used by the same QoS model.
> > > Method a): translate the
> > > initiator QSPEC into a local QSPEC and encapsulate the=20
> > > initiator
> > > QSPEC in the RESERVE message
> > > Method b): b) tunnel the initiator QSPEC
> > > through the local domain and reserve resources by=20
> > > generating a new
> > > RESERVE message through the local domain containing the local=20
> > > QSPEC.
> > >=20
> > > Note that according to the discussions that we have had until now=20
> > > method a) should be able to be used in combination with=20
> > > method b) by=20
> > > the same QoS model for the situation that the local QSPEC=20
> > > encapsulates=20
> > > the initiator QSPEC in order to satisfy requirement 5.4.2 that is=20
> > > specified in RFC 3726, see:
> > > http://www.ietf.org/rfc/rfc3726.txt
> > >=20
> > > Please add the following sentence at the end of the first=20
> > > paragraph of=20
> > > Section 5.1.
> > > "Note that when method b) is used, the encapsulation of the=20
> > > initiator=20
> > > QSPEC into a local QSPEC should also be possible when the=20
> > > local QoS=20
> > > model needs to satisfy Requirement
> > > 5.4.2 specified in RFC 3726, by adding and removing local=20
> > > QOSM-specific Control Information parameters on top of the=20
> > > initiator QSPEC."
> >=20
> > Your comment here is not clear to me.  It would help to=20
> > provide an example to illustrate what you are trying to=20
> > accomplish.  It seems that you are trying to specify QoS-NSLP=20
> > functionality, rather than QSPEC functionality.  If so, that=20
> > functionality should be specified in the QoS-NSLP draft=20
> > rather than the QSPEC draft, perhaps the QoS-NSLP authors=20
> > can comment.
>=20
> Georgios:
> No I am not trying to define QOS-NSLP functionality.
> This is related to QSPEC control information that has to be carried=20
> by end-to-end messages.
> What I am trying to say is that all the discussion that we have had=20
> regarding the encapsulation of the QSPEC object were associated=20
> with requirement 5.4.2 of RFC 3726, see below:
>=20
> -----------------
> "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain=20
> Information
>=20
>    It SHOULD be possible to add and remove local scope elements.
>    Compared to Requirement 5.3.5 this requirement does use the normal
>    signaling process and message exchange for transporting local
>    information.  For example, at the entrance to a domain, domain-
>    specific information is added information is added, which=20
>    is used in
>    this domain only, and the information is removed again when a
>    signaling message leaves the domain.  The motivation is in the
>    economy of re-using the protocol for domain internal signaling of
>    various information pieces.  Where additional information is needed
>    within a particular domain, it should be possible to carry this at
>    the same time as the end-to-end information.", from RFC 3726
> ------------------
> Thus what I am saying is:
> Please add the following sentence at the end of the first paragraph=20
> of Section 5.1.
>=20
> "Note that when method b) is used, the encapsulation of the=20
> initiator QSPEC into a local QSPEC should also be possible=20
> when the local QoS model needs to satisfy Requirement=20
> 5.4.2 specified in RFC 3726, by adding and removing local=20
> QOSM-specific Control Information parameters on top of the=20
> initiator QSPEC."

First, the suggested text isn't clear.  If method b) is used (tunneling)
then presumably method a) is not also used at the same time.  However,
the phrasing of the above makes it sound that way.

Second, an example would help here.  I presume you are referring e.g.,
to RMD adding 'control information' (i.e., 'handling directive')
parameters to the local QSPEC that are not included in the initiator
QSPEC.  I think the requirement would be that the RMD QOSM provides a
local QSPEC that is consistent with the initiator QSPEC, as we agreed on
the list (see also slide 8 of the IETF-67 presentation).

If the local QSPEC introduces functionality inconsistent with the
initiator QSPEC by appending the handling directive parameters, then it
is not allowed.

> > > Comment_5:
> > > -----------
> > > Section 5.1, last paragraph:
> > >=20
> > > Please change the following:
> > > "For example, RMD can define a local QSPEC that contains TMOD =3D=20
> > > bandwidth (sets r=3Dp, b/m to large)."
> > >=20
> > > Into:
> > > "For example, in RMD the TMOD parameters contained in the=20
> > > original=20
> > > initiator QSPEC are mapped into the equivalent TMOD parameter=20
> > > representing only the peak bandwidth in the local QSPEC."
> >=20
> > OK with me.
> >=20
> > > Comment_6:
> > > -------------
> > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to be followed=20
> > > regarding the QSPEC control information are not given:
> > >=20
> > > Please include the following paragraph at the end of this section:
> > > "Regarding QSPEC Control Information, the default rule is that all
> > >    QSPEC parameters that have been included in the RESERVE=20
> > >    message by
> > >    the QNI are also included in the RESPONSE message by the=20
> > >    QNR with the
> > >    value they had when arriving at the QNR.  When traveling in the
> > >    RESPONSE message, all QSPEC Control Information parameters are
> > >    read-only.  Note that a QOSM specification may define its own
> > >    QOSM-specific Control Information parameters and=20
> > >    processing rules."
> >=20
> > Please see previous email comment on QSPEC control information.
>=20
> Georgios: I think that a description of how the QSPEC control=20
> information is handled is needed.

Please see above comments on 'control information' terminology.

Thanks,
Jerry
=20
> > > Comment_7:
> > > ------------
> > > Section 6.1:
> > > I do not understand the second sentence from the below two=20
> > > sentences:
> > > "N Flag: Not-supported QSPEC parameter flag (see Section 5.2.2).
> > >            For QSPEC parameters the value of this flag is always=20
> > > zero."
> >=20
> > Good catch, this is a typo, the sentence should be removed.
> >=20
>=20
>=20
> Best Regards,
> Georgios
>=20

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



From nsis-bounces@ietf.org Fri Dec 22 09:10:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gxl6c-0000S8-KY; Fri, 22 Dec 2006 09:10:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxl6b-0000Rz-64
	for nsis@ietf.org; Fri, 22 Dec 2006 09:10:37 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gxl6Y-0005kp-3u
	for nsis@ietf.org; Fri, 22 Dec 2006 09:10:37 -0500
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 830204F5; 
	Fri, 22 Dec 2006 15:10:33 +0100 (CET)
Received: from esealmw106.eemea.ericsson.se ([153.88.200.69]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Dec 2006 15:10:22 +0100
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
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Date: Fri, 22 Dec 2006 15:10:22 +0100
Message-ID: <582B939025E978418C0B92DC134ADE9F3654F0@esealmw106.eemea.ericsson.se>
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC806C@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAg3qsA==
From: "Lars Westberg \(KI/EAB\)" <lars.westberg@ericsson.com>
To: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	"Georgios Karagiannis" <karagian@cs.utwente.nl>, <nsis@ietf.org>
X-OriginalArrivalTime: 22 Dec 2006 14:10:22.0784 (UTC)
	FILETIME=[EB817C00:01C725D2]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4fc59e88b356924367ae169e6a06365d
Cc: 
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

I have a severe problem with the procedure of changing the draft.=20
The changes you are refereing to has to be discussed before the draft is
changed.=20

I therefore requesting that the new draft should be an working group
draft.

Regard Lasse=20

-----Original Message-----
From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]=20
Sent: den 22 december 2006 15:01
To: Georgios Karagiannis; nsis@ietf.org
Cc: Ash, Gerald R (Jerry), ALABS
Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20

Georgios,

See below.=20

> -----Original Message-----
> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> Sent: Thursday, December 21, 2006 9:22 AM
> To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
> Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>=20
> Hi Jerry
>=20
> Please see below! I have severe concerns about some changes that have=20
> been done in the QSPEC template draft.
>=20
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > Sent: woensdag 20 december 2006 14:20
> > To: Georgios Karagiannis; nsis@ietf.org
> > Cc: Ash, Gerald R (Jerry), ALABS
> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> >=20
> > Hi Georgios,
> >=20
> > See below.=20
> >=20
> > > -----Original Message-----
> > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > Sent: Wednesday, December 20, 2006 5:26 AM
> > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
> > >=20
> > > Hi Jerry
> > >=20
> > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
> > >=20
> > > Comment_1:
> > > --------------
> > > Please reinclude the concept of QSPEC control information that was

> > > included in all previous versions of the QSPEC template draft.
> > > In
> > >=20
> >=20
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
> > > concept was described in Section 5.1.
> >=20
> > Please see previous email comment on QSPEC control information.
>=20
> Georgios:=20
> In order to emphasize the need of having QSPEC control information=20
> parameters  I  would however appreciate if the name of Section 4.3.3=20
> is changed
> From:
> 4.3.3 Traffic Handling Directives
> INTO:
> 4.3.3 QSPEC control information

The updated QSPEC parameter terminology/semantics are as suggested by
Dave Oran (see slides presented at IETF-67
http://www3.ietf.org/proceedings/06nov/index.html).  I think the current
terminology is more clear/descriptive of the QSPEC parameters so I don't
favor going backwards to less clear terminology.  I was never clear on
why we used the 'control information' terminology in the first place,
e.g., I don't think it's a very good descriptor of the 'excess
treatment' parameter.

Perhaps Dave can comment on this point also when he gets a chance.

> > > Comment_2:
> > > -----------
> > >=20
> > > Section 6.1:
> > > Please reintroduce the format that is required in order to
> > specify the
> > > QSPEC control information, see:
> > > Section 7.1 of:
> > > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
> >=20
> > Please see previous email comment on QSPEC control information.
>=20
>=20
> Georgios: If you rename section 4.3.3 to QSPEC control information=20
> then I think that reformatting of section 6.1 is not needed.
> Please add the proposed sentence by Dave (but change the term=20
> "handling directives" to "QSPEC control Information"). I am not sure=20
> where it is better to add this sentence, maybe in Section 5.4.
>=20
> "QoSMs are free, subject to IANA registration and review rules, to=20
> extend QSPECs by adding parameters of any of the kinds supported by=20
> the standard QSPEC. This includes traffic description parameters,=20
> constraint parameters and QSPEC control information. QoSMs are not=20
> permitted, however, to reinterpret or redefine the standard QSPEC=20
> parameters specified in this document"

Yes, the text suggested by Dave will be added.

> > > Comment_3:
> > > ----------
> > > Section 4.1 :QoS Models
> > > The definition of the QoS model is not complete. An important=20
> > > sentence that was used in the previous version of the draft is=20
> > > removed.
> > > Please add the following sentence to the definition of the QoS=20
> > > Model
> > > (QOSM):
> > >=20
> > > The same as described above have to be applied in this section.
> > > After the following sentence:
> > >=20
> > > "A QOSM specification MAY include the following:"
> > >=20
> > > include the following bullet:
> > > "- it specifies how to use QOS NSLP to signal for this QOSM"
> >=20
> > That sentence was removed in Dave's proposed QOSM re-definition, see

> > http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
> > ml.  It was unclear what that sentence meant, QoS-NSLP specifies how

> > to signal, not QOSM specifications, so the sentence was removed.
> >=20
> > I believe the sentence was intended to mean that when QoS NSLP=20
> > allows various options to be selected, a QOSM should be able to=20
> > determine which option is used.  For that purpose the following=20
> > sentence was added in Section 4.1:
> >=20
> > "     A QOSM specification MAY include the following:
> >      ...
> >      - can state which QoS-NSLP options a QOSM wants to use, when
> >      several options are available for a QOSM (e.g., local QSPEC to
> >      either be a) tunneled or b) encapsulate initiator QSPEC)."
> >=20
> > Also, to avoid any misinterpretation that QOSMs are free to specify=20
> > additional constraints, state machines, protocol data, etc. for NSLP

> > beyond that which is specific in the QoS NSLP specification, the=20
> > following was added to Section 4.1:
> >=20
> > "  QOSMs affect the operation of the RMF in NSIS-capable nodes, the
> >    information carried in QSPEC objects, and may under some
> >    circumstances (e.g. aggregation) cause a separate NSLP=20
> >    session to be
> >    instantiated by having the RMF as a QNI. QOSMs all utilize=20
> >    the common
> >    data, state machines, and APIs of the underlying NSIS=20
> >    protocols and
> >    are not expected to re-define or extend these in any way."
>=20
> Georgios:
> Regarding the sentence in Section 4.1:
> "QOSMs all utilize
> the common data, state machines, and APIs of the underlying NSIS=20
> protocols and are not expected to re-define or extend these in any=20
> way."
>=20
> This sentence restricts the possibility of QoS model to use RMF states

> and data that are not been defined in neither QoS-NSLP or QSPEC.
> This sentence should be removed.

I disagree.  The quoted text was introduced by Dave Oran in addition to
removing the phrase implying that a QOSM could specify signaling
protocol changes, and I agree with this.  Any changes/extensions to the
signaling protocol or state machines are within the scope of QoS-NSLP
draft and not the QSPEC draft or a QOSM specification draft.  I think
you have noted that also in your subsequent posting at
http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html. =20

If any extensions are required to the NSIS signaling protocol as a
result of the 'severe change on QoS Model definition and capabilities'
you have noted, those proposed changes/extensions should be addressed to
the QoS NSLP draft IMO.

Perhaps Dave can comment here also when he gets a chance.

> > > Comment_4:
> > > -------------
> > > Section 5.1 Local QSPEC definition and processing
> > >=20
> > > By reading this section it gives the impression that the two=20
> > > methods
> > > a) and b) cannot be used by the same QoS model.
> > > Method a): translate the
> > > initiator QSPEC into a local QSPEC and encapsulate the initiator=20
> > > QSPEC in the RESERVE message Method b): b) tunnel the initiator=20
> > > QSPEC through the local domain and reserve resources by generating

> > > a new RESERVE message through the local domain containing the=20
> > > local QSPEC.
> > >=20
> > > Note that according to the discussions that we have had until now=20
> > > method a) should be able to be used in combination with method b)=20
> > > by the same QoS model for the situation that the local QSPEC=20
> > > encapsulates the initiator QSPEC in order to satisfy requirement=20
> > > 5.4.2 that is specified in RFC 3726, see:
> > > http://www.ietf.org/rfc/rfc3726.txt
> > >=20
> > > Please add the following sentence at the end of the first=20
> > > paragraph of Section 5.1.
> > > "Note that when method b) is used, the encapsulation of the=20
> > > initiator QSPEC into a local QSPEC should also be possible when=20
> > > the local QoS model needs to satisfy Requirement
> > > 5.4.2 specified in RFC 3726, by adding and removing local=20
> > > QOSM-specific Control Information parameters on top of the=20
> > > initiator QSPEC."
> >=20
> > Your comment here is not clear to me.  It would help to provide an=20
> > example to illustrate what you are trying to accomplish.  It seems=20
> > that you are trying to specify QoS-NSLP functionality, rather than=20
> > QSPEC functionality.  If so, that functionality should be specified=20
> > in the QoS-NSLP draft rather than the QSPEC draft, perhaps the=20
> > QoS-NSLP authors can comment.
>=20
> Georgios:
> No I am not trying to define QOS-NSLP functionality.
> This is related to QSPEC control information that has to be carried by

> end-to-end messages.
> What I am trying to say is that all the discussion that we have had=20
> regarding the encapsulation of the QSPEC object were associated with=20
> requirement 5.4.2 of RFC 3726, see below:
>=20
> -----------------
> "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain=20
> Information
>=20
>    It SHOULD be possible to add and remove local scope elements.
>    Compared to Requirement 5.3.5 this requirement does use the normal
>    signaling process and message exchange for transporting local
>    information.  For example, at the entrance to a domain, domain-
>    specific information is added information is added, which=20
>    is used in
>    this domain only, and the information is removed again when a
>    signaling message leaves the domain.  The motivation is in the
>    economy of re-using the protocol for domain internal signaling of
>    various information pieces.  Where additional information is needed
>    within a particular domain, it should be possible to carry this at
>    the same time as the end-to-end information.", from RFC 3726
> ------------------
> Thus what I am saying is:
> Please add the following sentence at the end of the first paragraph of

> Section 5.1.
>=20
> "Note that when method b) is used, the encapsulation of the initiator=20
> QSPEC into a local QSPEC should also be possible when the local QoS=20
> model needs to satisfy Requirement
> 5.4.2 specified in RFC 3726, by adding and removing local=20
> QOSM-specific Control Information parameters on top of the initiator=20
> QSPEC."

First, the suggested text isn't clear.  If method b) is used (tunneling)
then presumably method a) is not also used at the same time.  However,
the phrasing of the above makes it sound that way.

Second, an example would help here.  I presume you are referring e.g.,
to RMD adding 'control information' (i.e., 'handling directive')
parameters to the local QSPEC that are not included in the initiator
QSPEC.  I think the requirement would be that the RMD QOSM provides a
local QSPEC that is consistent with the initiator QSPEC, as we agreed on
the list (see also slide 8 of the IETF-67 presentation).

If the local QSPEC introduces functionality inconsistent with the
initiator QSPEC by appending the handling directive parameters, then it
is not allowed.

> > > Comment_5:
> > > -----------
> > > Section 5.1, last paragraph:
> > >=20
> > > Please change the following:
> > > "For example, RMD can define a local QSPEC that contains TMOD =3D=20
> > > bandwidth (sets r=3Dp, b/m to large)."
> > >=20
> > > Into:
> > > "For example, in RMD the TMOD parameters contained in the original

> > > initiator QSPEC are mapped into the equivalent TMOD parameter=20
> > > representing only the peak bandwidth in the local QSPEC."
> >=20
> > OK with me.
> >=20
> > > Comment_6:
> > > -------------
> > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to be followed=20
> > > regarding the QSPEC control information are not given:
> > >=20
> > > Please include the following paragraph at the end of this section:
> > > "Regarding QSPEC Control Information, the default rule is that all
> > >    QSPEC parameters that have been included in the RESERVE=20
> > >    message by
> > >    the QNI are also included in the RESPONSE message by the=20
> > >    QNR with the
> > >    value they had when arriving at the QNR.  When traveling in the
> > >    RESPONSE message, all QSPEC Control Information parameters are
> > >    read-only.  Note that a QOSM specification may define its own
> > >    QOSM-specific Control Information parameters and=20
> > >    processing rules."
> >=20
> > Please see previous email comment on QSPEC control information.
>=20
> Georgios: I think that a description of how the QSPEC control=20
> information is handled is needed.

Please see above comments on 'control information' terminology.

Thanks,
Jerry
=20
> > > Comment_7:
> > > ------------
> > > Section 6.1:
> > > I do not understand the second sentence from the below two
> > > sentences:
> > > "N Flag: Not-supported QSPEC parameter flag (see Section 5.2.2).
> > >            For QSPEC parameters the value of this flag is always=20
> > > zero."
> >=20
> > Good catch, this is a typo, the sentence should be removed.
> >=20
>=20
>=20
> Best Regards,
> Georgios
>=20

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

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



From nsis-bounces@ietf.org Fri Dec 22 09:14:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gxl9g-0002XJ-Pn; Fri, 22 Dec 2006 09:13:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxl9f-0002VK-NO
	for nsis@ietf.org; Fri, 22 Dec 2006 09:13:47 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gxl9f-0006Ca-0x
	for nsis@ietf.org; Fri, 22 Dec 2006 09:13:47 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kBMEDMpC009545; Fri, 22 Dec 2006 15:13:35 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>, <nsis@ietf.org>
Date: Fri, 22 Dec 2006 15:13:18 +0100
Message-ID: <003201c725d3$581448c0$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAfQcYA==
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC806C@KCCLUST06EVS1.ugd.att.com>
X-Spam-Score: 0.4 () FVGT_s_OBFU_Q1,FVGT_u_HAS_2LETTERFLDR
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Fri, 22 Dec 2006 15:13:37 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3dc828214e948ff35b815af10e94a823
Cc: 
Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
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

Hi Jerry

By just saying that "these changes are suggested by Dave in the e-mail" 
does not work.

The proposal of Dave was not clear on the QoS model changes that 
you wanted to do. 
Now I understand which changes you want to include in the 
QSPEC template draft.
This is also the reason of disagreeing with you now and 
sending comments to the nsis list.

Furthermore, note that the QOS-NSLP draft defines which capabilities 
should be supported by the QoS models and not the 
QSPEC template draft.

Best Regards,
Georgios


> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> Sent: vrijdag 22 december 2006 15:01
> To: Georgios Karagiannis; nsis@ietf.org
> Cc: Ash, Gerald R (Jerry), ALABS
> Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt 
> 
> Georgios,
> 
> See below. 
> 
> > -----Original Message-----
> > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > Sent: Thursday, December 21, 2006 9:22 AM
> > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > 
> > Hi Jerry
> > 
> > Please see below! I have severe concerns about some changes 
> that have 
> > been done in the QSPEC template draft.
> > 
> > > -----Original Message-----
> > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > > Sent: woensdag 20 december 2006 14:20
> > > To: Georgios Karagiannis; nsis@ietf.org
> > > Cc: Ash, Gerald R (Jerry), ALABS
> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > 
> > > Hi Georgios,
> > > 
> > > See below. 
> > > 
> > > > -----Original Message-----
> > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > > Sent: Wednesday, December 20, 2006 5:26 AM
> > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
> > > > 
> > > > Hi Jerry
> > > > 
> > > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
> > > > 
> > > > Comment_1:
> > > > --------------
> > > > Please reinclude the concept of QSPEC control 
> information that was 
> > > > included in all previous versions of the QSPEC template draft.
> > > > In
> > > > 
> > > 
> > 
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
> > > > concept was described in Section 5.1.
> > > 
> > > Please see previous email comment on QSPEC control information.
> > 
> > Georgios: 
> > In order to emphasize the need of having QSPEC control information 
> > parameters  I  would however appreciate if the name of 
> Section 4.3.3 
> > is changed
> > From:
> > 4.3.3 Traffic Handling Directives
> > INTO:
> > 4.3.3 QSPEC control information
> 
> The updated QSPEC parameter terminology/semantics are as 
> suggested by Dave Oran (see slides presented at IETF-67 
> http://www3.ietf.org/proceedings/06nov/index.html).  I think 
> the current terminology is more clear/descriptive of the 
> QSPEC parameters so I don't favor going backwards to less 
> clear terminology.  I was never clear on why we used the 
> 'control information' terminology in the first place, e.g., I 
> don't think it's a very good descriptor of the 'excess 
> treatment' parameter.
> 
> Perhaps Dave can comment on this point also when he gets a chance.
> 
> > > > Comment_2:
> > > > -----------
> > > > 
> > > > Section 6.1:
> > > > Please reintroduce the format that is required in order to
> > > specify the
> > > > QSPEC control information, see:
> > > > Section 7.1 of:
> > > > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
> > > 
> > > Please see previous email comment on QSPEC control information.
> > 
> > 
> > Georgios: If you rename section 4.3.3 to QSPEC control information 
> > then I think that reformatting of section 6.1 is not needed.
> > Please add the proposed sentence by Dave (but change the term 
> > "handling directives" to "QSPEC control Information"). I am 
> not sure 
> > where it is better to add this sentence, maybe in Section 5.4.
> > 
> > "QoSMs are free, subject to IANA registration and review rules, to 
> > extend QSPECs by adding parameters of any of the kinds supported by 
> > the standard QSPEC. This includes traffic description parameters, 
> > constraint parameters and QSPEC control information. QoSMs are not 
> > permitted, however, to reinterpret or redefine the standard QSPEC 
> > parameters specified in this document"
> 
> Yes, the text suggested by Dave will be added.
> 
> > > > Comment_3:
> > > > ----------
> > > > Section 4.1 :QoS Models
> > > > The definition of the QoS model is not complete. An important 
> > > > sentence that was used in the previous version of the draft is 
> > > > removed.
> > > > Please add the following sentence to the definition of the QoS 
> > > > Model
> > > > (QOSM):
> > > > 
> > > > The same as described above have to be applied in this section.
> > > > After the following sentence:
> > > > 
> > > > "A QOSM specification MAY include the following:"
> > > > 
> > > > include the following bullet:
> > > > "- it specifies how to use QOS NSLP to signal for this QOSM"
> > > 
> > > That sentence was removed in Dave's proposed QOSM 
> re-definition, see 
> > > http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
> > > ml.  It was unclear what that sentence meant, QoS-NSLP 
> specifies how 
> > > to signal, not QOSM specifications, so the sentence was removed.
> > > 
> > > I believe the sentence was intended to mean that when QoS NSLP 
> > > allows various options to be selected, a QOSM should be able to 
> > > determine which option is used.  For that purpose the following 
> > > sentence was added in Section 4.1:
> > > 
> > > "     A QOSM specification MAY include the following:
> > >      ...
> > >      - can state which QoS-NSLP options a QOSM wants to use, when
> > >      several options are available for a QOSM (e.g., 
> local QSPEC to
> > >      either be a) tunneled or b) encapsulate initiator QSPEC)."
> > > 
> > > Also, to avoid any misinterpretation that QOSMs are free 
> to specify 
> > > additional constraints, state machines, protocol data, 
> etc. for NSLP 
> > > beyond that which is specific in the QoS NSLP specification, the 
> > > following was added to Section 4.1:
> > > 
> > > "  QOSMs affect the operation of the RMF in NSIS-capable 
> nodes, the
> > >    information carried in QSPEC objects, and may under some
> > >    circumstances (e.g. aggregation) cause a separate NSLP 
> > >    session to be
> > >    instantiated by having the RMF as a QNI. QOSMs all utilize 
> > >    the common
> > >    data, state machines, and APIs of the underlying NSIS 
> > >    protocols and
> > >    are not expected to re-define or extend these in any way."
> > 
> > Georgios:
> > Regarding the sentence in Section 4.1:
> > "QOSMs all utilize
> > the common data, state machines, and APIs of the underlying NSIS 
> > protocols and are not expected to re-define or extend these in any 
> > way."
> > 
> > This sentence restricts the possibility of QoS model to use 
> RMF states 
> > and data that are not been defined in neither QoS-NSLP or QSPEC.
> > This sentence should be removed.
> 
> I disagree.  The quoted text was introduced by Dave Oran in 
> addition to removing the phrase implying that a QOSM could 
> specify signaling protocol changes, and I agree with this.  
> Any changes/extensions to the signaling protocol or state 
> machines are within the scope of QoS-NSLP draft and not the 
> QSPEC draft or a QOSM specification draft.  I think you have 
> noted that also in your subsequent posting at 
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html.  
> 
> If any extensions are required to the NSIS signaling protocol 
> as a result of the 'severe change on QoS Model definition and 
> capabilities'
> you have noted, those proposed changes/extensions should be 
> addressed to the QoS NSLP draft IMO.
> 
> Perhaps Dave can comment here also when he gets a chance.
> 
> > > > Comment_4:
> > > > -------------
> > > > Section 5.1 Local QSPEC definition and processing
> > > > 
> > > > By reading this section it gives the impression that the two 
> > > > methods
> > > > a) and b) cannot be used by the same QoS model.
> > > > Method a): translate the
> > > > initiator QSPEC into a local QSPEC and encapsulate the 
> initiator 
> > > > QSPEC in the RESERVE message Method b): b) tunnel the initiator 
> > > > QSPEC through the local domain and reserve resources by 
> generating 
> > > > a new RESERVE message through the local domain containing the 
> > > > local QSPEC.
> > > > 
> > > > Note that according to the discussions that we have had 
> until now 
> > > > method a) should be able to be used in combination with 
> method b) 
> > > > by the same QoS model for the situation that the local QSPEC 
> > > > encapsulates the initiator QSPEC in order to satisfy 
> requirement 
> > > > 5.4.2 that is specified in RFC 3726, see:
> > > > http://www.ietf.org/rfc/rfc3726.txt
> > > > 
> > > > Please add the following sentence at the end of the first 
> > > > paragraph of Section 5.1.
> > > > "Note that when method b) is used, the encapsulation of the 
> > > > initiator QSPEC into a local QSPEC should also be possible when 
> > > > the local QoS model needs to satisfy Requirement
> > > > 5.4.2 specified in RFC 3726, by adding and removing local 
> > > > QOSM-specific Control Information parameters on top of the 
> > > > initiator QSPEC."
> > > 
> > > Your comment here is not clear to me.  It would help to 
> provide an 
> > > example to illustrate what you are trying to accomplish.  
> It seems 
> > > that you are trying to specify QoS-NSLP functionality, 
> rather than 
> > > QSPEC functionality.  If so, that functionality should be 
> specified 
> > > in the QoS-NSLP draft rather than the QSPEC draft, perhaps the 
> > > QoS-NSLP authors can comment.
> > 
> > Georgios:
> > No I am not trying to define QOS-NSLP functionality.
> > This is related to QSPEC control information that has to be 
> carried by 
> > end-to-end messages.
> > What I am trying to say is that all the discussion that we have had 
> > regarding the encapsulation of the QSPEC object were 
> associated with 
> > requirement 5.4.2 of RFC 3726, see below:
> > 
> > -----------------
> > "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain 
> > Information
> > 
> >    It SHOULD be possible to add and remove local scope elements.
> >    Compared to Requirement 5.3.5 this requirement does use 
> the normal
> >    signaling process and message exchange for transporting local
> >    information.  For example, at the entrance to a domain, domain-
> >    specific information is added information is added, which 
> >    is used in
> >    this domain only, and the information is removed again when a
> >    signaling message leaves the domain.  The motivation is in the
> >    economy of re-using the protocol for domain internal signaling of
> >    various information pieces.  Where additional 
> information is needed
> >    within a particular domain, it should be possible to 
> carry this at
> >    the same time as the end-to-end information.", from RFC 3726
> > ------------------
> > Thus what I am saying is:
> > Please add the following sentence at the end of the first 
> paragraph of 
> > Section 5.1.
> > 
> > "Note that when method b) is used, the encapsulation of the 
> initiator 
> > QSPEC into a local QSPEC should also be possible when the local QoS 
> > model needs to satisfy Requirement
> > 5.4.2 specified in RFC 3726, by adding and removing local 
> > QOSM-specific Control Information parameters on top of the 
> initiator 
> > QSPEC."
> 
> First, the suggested text isn't clear.  If method b) is used 
> (tunneling) then presumably method a) is not also used at the 
> same time.  However, the phrasing of the above makes it sound 
> that way.
> 
> Second, an example would help here.  I presume you are 
> referring e.g., to RMD adding 'control information' (i.e., 
> 'handling directive') parameters to the local QSPEC that are 
> not included in the initiator QSPEC.  I think the requirement 
> would be that the RMD QOSM provides a local QSPEC that is 
> consistent with the initiator QSPEC, as we agreed on the list 
> (see also slide 8 of the IETF-67 presentation).
> 
> If the local QSPEC introduces functionality inconsistent with 
> the initiator QSPEC by appending the handling directive 
> parameters, then it is not allowed.
> 
> > > > Comment_5:
> > > > -----------
> > > > Section 5.1, last paragraph:
> > > > 
> > > > Please change the following:
> > > > "For example, RMD can define a local QSPEC that contains TMOD = 
> > > > bandwidth (sets r=p, b/m to large)."
> > > > 
> > > > Into:
> > > > "For example, in RMD the TMOD parameters contained in 
> the original 
> > > > initiator QSPEC are mapped into the equivalent TMOD parameter 
> > > > representing only the peak bandwidth in the local QSPEC."
> > > 
> > > OK with me.
> > > 
> > > > Comment_6:
> > > > -------------
> > > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to 
> be followed 
> > > > regarding the QSPEC control information are not given:
> > > > 
> > > > Please include the following paragraph at the end of 
> this section:
> > > > "Regarding QSPEC Control Information, the default rule 
> is that all
> > > >    QSPEC parameters that have been included in the RESERVE 
> > > >    message by
> > > >    the QNI are also included in the RESPONSE message by the 
> > > >    QNR with the
> > > >    value they had when arriving at the QNR.  When 
> traveling in the
> > > >    RESPONSE message, all QSPEC Control Information 
> parameters are
> > > >    read-only.  Note that a QOSM specification may define its own
> > > >    QOSM-specific Control Information parameters and 
> > > >    processing rules."
> > > 
> > > Please see previous email comment on QSPEC control information.
> > 
> > Georgios: I think that a description of how the QSPEC control 
> > information is handled is needed.
> 
> Please see above comments on 'control information' terminology.
> 
> Thanks,
> Jerry
>  
> > > > Comment_7:
> > > > ------------
> > > > Section 6.1:
> > > > I do not understand the second sentence from the below two
> > > > sentences:
> > > > "N Flag: Not-supported QSPEC parameter flag (see Section 5.2.2).
> > > >            For QSPEC parameters the value of this flag 
> is always 
> > > > zero."
> > > 
> > > Good catch, this is a typo, the sentence should be removed.
> > > 
> > 
> > 
> > Best Regards,
> > Georgios
> > 
> 



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



From nsis-bounces@ietf.org Fri Dec 22 09:14:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gxl9p-0002jK-EM; Fri, 22 Dec 2006 09:13:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxl9o-0002fP-2W
	for nsis@ietf.org; Fri, 22 Dec 2006 09:13:56 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gxl9n-0006DU-3l
	for nsis@ietf.org; Fri, 22 Dec 2006 09:13:56 -0500
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 829DFF3A; 
	Fri, 22 Dec 2006 15:13:54 +0100 (CET)
Received: from esealmw106.eemea.ericsson.se ([153.88.200.69]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Dec 2006 15:13:47 +0100
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
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Date: Fri, 22 Dec 2006 15:13:47 +0100
Message-ID: <582B939025E978418C0B92DC134ADE9F3654F7@esealmw106.eemea.ericsson.se>
In-Reply-To: <582B939025E978418C0B92DC134ADE9F3654F0@esealmw106.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAg3qsAAAKEiw
From: "Lars Westberg \(KI/EAB\)" <lars.westberg@ericsson.com>
To: "Lars Westberg \(KI/EAB\)" <lars.westberg@ericsson.com>,
	"Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	"Georgios Karagiannis" <karagian@cs.utwente.nl>, <nsis@ietf.org>
X-OriginalArrivalTime: 22 Dec 2006 14:13:47.0639 (UTC)
	FILETIME=[659BE070:01C725D3]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e06437eb72f6703f11713d345be8298a
Cc: 
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

I am sorry spelling error.

The new draft should NOT be a working group draft!!
It should be a indiviual submission!!!!

Regards Lasse
-----Original Message-----
From: Lars Westberg (KI/EAB) [mailto:lars.westberg@ericsson.com]=20
Sent: den 22 december 2006 15:10
To: Ash, Gerald R (Jerry), ALABS; Georgios Karagiannis; nsis@ietf.org
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20

I have a severe problem with the procedure of changing the draft.=20
The changes you are refereing to has to be discussed before the draft is
changed.=20

I therefore requesting that the new draft should be an working group
draft.

Regard Lasse=20

-----Original Message-----
From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
Sent: den 22 december 2006 15:01
To: Georgios Karagiannis; nsis@ietf.org
Cc: Ash, Gerald R (Jerry), ALABS
Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20

Georgios,

See below.=20

> -----Original Message-----
> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> Sent: Thursday, December 21, 2006 9:22 AM
> To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
> Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>=20
> Hi Jerry
>=20
> Please see below! I have severe concerns about some changes that have=20
> been done in the QSPEC template draft.
>=20
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > Sent: woensdag 20 december 2006 14:20
> > To: Georgios Karagiannis; nsis@ietf.org
> > Cc: Ash, Gerald R (Jerry), ALABS
> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> >=20
> > Hi Georgios,
> >=20
> > See below.=20
> >=20
> > > -----Original Message-----
> > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > Sent: Wednesday, December 20, 2006 5:26 AM
> > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
> > >=20
> > > Hi Jerry
> > >=20
> > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
> > >=20
> > > Comment_1:
> > > --------------
> > > Please reinclude the concept of QSPEC control information that was

> > > included in all previous versions of the QSPEC template draft.
> > > In
> > >=20
> >=20
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
> > > concept was described in Section 5.1.
> >=20
> > Please see previous email comment on QSPEC control information.
>=20
> Georgios:=20
> In order to emphasize the need of having QSPEC control information=20
> parameters  I  would however appreciate if the name of Section 4.3.3=20
> is changed
> From:
> 4.3.3 Traffic Handling Directives
> INTO:
> 4.3.3 QSPEC control information

The updated QSPEC parameter terminology/semantics are as suggested by
Dave Oran (see slides presented at IETF-67
http://www3.ietf.org/proceedings/06nov/index.html).  I think the current
terminology is more clear/descriptive of the QSPEC parameters so I don't
favor going backwards to less clear terminology.  I was never clear on
why we used the 'control information' terminology in the first place,
e.g., I don't think it's a very good descriptor of the 'excess
treatment' parameter.

Perhaps Dave can comment on this point also when he gets a chance.

> > > Comment_2:
> > > -----------
> > >=20
> > > Section 6.1:
> > > Please reintroduce the format that is required in order to
> > specify the
> > > QSPEC control information, see:
> > > Section 7.1 of:
> > > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
> >=20
> > Please see previous email comment on QSPEC control information.
>=20
>=20
> Georgios: If you rename section 4.3.3 to QSPEC control information=20
> then I think that reformatting of section 6.1 is not needed.
> Please add the proposed sentence by Dave (but change the term=20
> "handling directives" to "QSPEC control Information"). I am not sure=20
> where it is better to add this sentence, maybe in Section 5.4.
>=20
> "QoSMs are free, subject to IANA registration and review rules, to=20
> extend QSPECs by adding parameters of any of the kinds supported by=20
> the standard QSPEC. This includes traffic description parameters,=20
> constraint parameters and QSPEC control information. QoSMs are not=20
> permitted, however, to reinterpret or redefine the standard QSPEC=20
> parameters specified in this document"

Yes, the text suggested by Dave will be added.

> > > Comment_3:
> > > ----------
> > > Section 4.1 :QoS Models
> > > The definition of the QoS model is not complete. An important=20
> > > sentence that was used in the previous version of the draft is=20
> > > removed.
> > > Please add the following sentence to the definition of the QoS=20
> > > Model
> > > (QOSM):
> > >=20
> > > The same as described above have to be applied in this section.
> > > After the following sentence:
> > >=20
> > > "A QOSM specification MAY include the following:"
> > >=20
> > > include the following bullet:
> > > "- it specifies how to use QOS NSLP to signal for this QOSM"
> >=20
> > That sentence was removed in Dave's proposed QOSM re-definition, see

> > http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
> > ml.  It was unclear what that sentence meant, QoS-NSLP specifies how

> > to signal, not QOSM specifications, so the sentence was removed.
> >=20
> > I believe the sentence was intended to mean that when QoS NSLP=20
> > allows various options to be selected, a QOSM should be able to=20
> > determine which option is used.  For that purpose the following=20
> > sentence was added in Section 4.1:
> >=20
> > "     A QOSM specification MAY include the following:
> >      ...
> >      - can state which QoS-NSLP options a QOSM wants to use, when
> >      several options are available for a QOSM (e.g., local QSPEC to
> >      either be a) tunneled or b) encapsulate initiator QSPEC)."
> >=20
> > Also, to avoid any misinterpretation that QOSMs are free to specify=20
> > additional constraints, state machines, protocol data, etc. for NSLP

> > beyond that which is specific in the QoS NSLP specification, the=20
> > following was added to Section 4.1:
> >=20
> > "  QOSMs affect the operation of the RMF in NSIS-capable nodes, the
> >    information carried in QSPEC objects, and may under some
> >    circumstances (e.g. aggregation) cause a separate NSLP=20
> >    session to be
> >    instantiated by having the RMF as a QNI. QOSMs all utilize=20
> >    the common
> >    data, state machines, and APIs of the underlying NSIS=20
> >    protocols and
> >    are not expected to re-define or extend these in any way."
>=20
> Georgios:
> Regarding the sentence in Section 4.1:
> "QOSMs all utilize
> the common data, state machines, and APIs of the underlying NSIS=20
> protocols and are not expected to re-define or extend these in any=20
> way."
>=20
> This sentence restricts the possibility of QoS model to use RMF states

> and data that are not been defined in neither QoS-NSLP or QSPEC.
> This sentence should be removed.

I disagree.  The quoted text was introduced by Dave Oran in addition to
removing the phrase implying that a QOSM could specify signaling
protocol changes, and I agree with this.  Any changes/extensions to the
signaling protocol or state machines are within the scope of QoS-NSLP
draft and not the QSPEC draft or a QOSM specification draft.  I think
you have noted that also in your subsequent posting at
http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html. =20

If any extensions are required to the NSIS signaling protocol as a
result of the 'severe change on QoS Model definition and capabilities'
you have noted, those proposed changes/extensions should be addressed to
the QoS NSLP draft IMO.

Perhaps Dave can comment here also when he gets a chance.

> > > Comment_4:
> > > -------------
> > > Section 5.1 Local QSPEC definition and processing
> > >=20
> > > By reading this section it gives the impression that the two=20
> > > methods
> > > a) and b) cannot be used by the same QoS model.
> > > Method a): translate the
> > > initiator QSPEC into a local QSPEC and encapsulate the initiator=20
> > > QSPEC in the RESERVE message Method b): b) tunnel the initiator=20
> > > QSPEC through the local domain and reserve resources by generating

> > > a new RESERVE message through the local domain containing the=20
> > > local QSPEC.
> > >=20
> > > Note that according to the discussions that we have had until now=20
> > > method a) should be able to be used in combination with method b)=20
> > > by the same QoS model for the situation that the local QSPEC=20
> > > encapsulates the initiator QSPEC in order to satisfy requirement
> > > 5.4.2 that is specified in RFC 3726, see:
> > > http://www.ietf.org/rfc/rfc3726.txt
> > >=20
> > > Please add the following sentence at the end of the first=20
> > > paragraph of Section 5.1.
> > > "Note that when method b) is used, the encapsulation of the=20
> > > initiator QSPEC into a local QSPEC should also be possible when=20
> > > the local QoS model needs to satisfy Requirement
> > > 5.4.2 specified in RFC 3726, by adding and removing local=20
> > > QOSM-specific Control Information parameters on top of the=20
> > > initiator QSPEC."
> >=20
> > Your comment here is not clear to me.  It would help to provide an=20
> > example to illustrate what you are trying to accomplish.  It seems=20
> > that you are trying to specify QoS-NSLP functionality, rather than=20
> > QSPEC functionality.  If so, that functionality should be specified=20
> > in the QoS-NSLP draft rather than the QSPEC draft, perhaps the=20
> > QoS-NSLP authors can comment.
>=20
> Georgios:
> No I am not trying to define QOS-NSLP functionality.
> This is related to QSPEC control information that has to be carried by

> end-to-end messages.
> What I am trying to say is that all the discussion that we have had=20
> regarding the encapsulation of the QSPEC object were associated with=20
> requirement 5.4.2 of RFC 3726, see below:
>=20
> -----------------
> "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain=20
> Information
>=20
>    It SHOULD be possible to add and remove local scope elements.
>    Compared to Requirement 5.3.5 this requirement does use the normal
>    signaling process and message exchange for transporting local
>    information.  For example, at the entrance to a domain, domain-
>    specific information is added information is added, which=20
>    is used in
>    this domain only, and the information is removed again when a
>    signaling message leaves the domain.  The motivation is in the
>    economy of re-using the protocol for domain internal signaling of
>    various information pieces.  Where additional information is needed
>    within a particular domain, it should be possible to carry this at
>    the same time as the end-to-end information.", from RFC 3726
> ------------------
> Thus what I am saying is:
> Please add the following sentence at the end of the first paragraph of

> Section 5.1.
>=20
> "Note that when method b) is used, the encapsulation of the initiator=20
> QSPEC into a local QSPEC should also be possible when the local QoS=20
> model needs to satisfy Requirement
> 5.4.2 specified in RFC 3726, by adding and removing local=20
> QOSM-specific Control Information parameters on top of the initiator=20
> QSPEC."

First, the suggested text isn't clear.  If method b) is used (tunneling)
then presumably method a) is not also used at the same time.  However,
the phrasing of the above makes it sound that way.

Second, an example would help here.  I presume you are referring e.g.,
to RMD adding 'control information' (i.e., 'handling directive')
parameters to the local QSPEC that are not included in the initiator
QSPEC.  I think the requirement would be that the RMD QOSM provides a
local QSPEC that is consistent with the initiator QSPEC, as we agreed on
the list (see also slide 8 of the IETF-67 presentation).

If the local QSPEC introduces functionality inconsistent with the
initiator QSPEC by appending the handling directive parameters, then it
is not allowed.

> > > Comment_5:
> > > -----------
> > > Section 5.1, last paragraph:
> > >=20
> > > Please change the following:
> > > "For example, RMD can define a local QSPEC that contains TMOD =3D=20
> > > bandwidth (sets r=3Dp, b/m to large)."
> > >=20
> > > Into:
> > > "For example, in RMD the TMOD parameters contained in the original

> > > initiator QSPEC are mapped into the equivalent TMOD parameter=20
> > > representing only the peak bandwidth in the local QSPEC."
> >=20
> > OK with me.
> >=20
> > > Comment_6:
> > > -------------
> > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to be followed=20
> > > regarding the QSPEC control information are not given:
> > >=20
> > > Please include the following paragraph at the end of this section:
> > > "Regarding QSPEC Control Information, the default rule is that all
> > >    QSPEC parameters that have been included in the RESERVE=20
> > >    message by
> > >    the QNI are also included in the RESPONSE message by the=20
> > >    QNR with the
> > >    value they had when arriving at the QNR.  When traveling in the
> > >    RESPONSE message, all QSPEC Control Information parameters are
> > >    read-only.  Note that a QOSM specification may define its own
> > >    QOSM-specific Control Information parameters and=20
> > >    processing rules."
> >=20
> > Please see previous email comment on QSPEC control information.
>=20
> Georgios: I think that a description of how the QSPEC control=20
> information is handled is needed.

Please see above comments on 'control information' terminology.

Thanks,
Jerry
=20
> > > Comment_7:
> > > ------------
> > > Section 6.1:
> > > I do not understand the second sentence from the below two
> > > sentences:
> > > "N Flag: Not-supported QSPEC parameter flag (see Section 5.2.2).
> > >            For QSPEC parameters the value of this flag is always=20
> > > zero."
> >=20
> > Good catch, this is a typo, the sentence should be removed.
> >=20
>=20
>=20
> Best Regards,
> Georgios
>=20

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

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

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



From nsis-bounces@ietf.org Fri Dec 22 09:31:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxlQd-0002aV-W1; Fri, 22 Dec 2006 09:31:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxlQc-0002Yv-Sl
	for nsis@ietf.org; Fri, 22 Dec 2006 09:31:18 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxlQX-0000c8-P3
	for nsis@ietf.org; Fri, 22 Dec 2006 09:31:18 -0500
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id ED4C31CF; 
	Fri, 22 Dec 2006 15:31:08 +0100 (CET)
Received: from esealmw106.eemea.ericsson.se ([153.88.200.69]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Dec 2006 15:31:08 +0100
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
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Date: Fri, 22 Dec 2006 15:31:08 +0100
Message-ID: <582B939025E978418C0B92DC134ADE9F365510@esealmw106.eemea.ericsson.se>
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC806C@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAiO6wA==
From: "Lars Westberg \(KI/EAB\)" <lars.westberg@ericsson.com>
To: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	"Georgios Karagiannis" <karagian@cs.utwente.nl>, <nsis@ietf.org>
X-OriginalArrivalTime: 22 Dec 2006 14:31:08.0731 (UTC)
	FILETIME=[D225E8B0:01C725D5]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f460acdc4aacf7fc5e6f9bd32f8fd8c6
Cc: 
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

Let's discuss it once more regarding the control information in the
QoS-model,.

The basic purpose with the QOS-model is to have modularity and
extendabillity for future needs. We have discussed into the protocol
design and I am very suprised that it suddently disappear from the
draft.

We have one very good example: RSVP-proxy.

If one wan't to have NSIS-proxies,=20
	we need to control information such as: Proxy is found!!=20
							    Proxy is
located at this address!

This could very well be described by QoS-model control information!!!

The basic problem is that this drafts tries to limit the extendabillity
to exactly the same as RSVP!!! I completely disagree with that approach.

There are no need to re-design RSVP with exactly the same
functionality!! We already have RSVP but RSVP is better designed from
scalabillity perspective and have support for Mutlicast support. We are
designing exactly the same protocol but with limited functional support
and without Multicast!!!!!
Note, that we can't use NSIS for TV-broadcast !!!=20

I do not beleive that NSIS can replace RSVP!!!=20
Therefore, QOS-NSLP must support other usage than RSVP!!!

I agree that the description of control information may be explained
better but it has to be possible to have control information in the
QoS-model.

But the statement into this draft makes the QoS-NSLP useless!!


Regards Lasse


-----Original Message-----
From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]=20
Sent: den 22 december 2006 15:01
To: Georgios Karagiannis; nsis@ietf.org
Cc: Ash, Gerald R (Jerry), ALABS
Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20

Georgios,

See below.=20

> -----Original Message-----
> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> Sent: Thursday, December 21, 2006 9:22 AM
> To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
> Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>=20
> Hi Jerry
>=20
> Please see below! I have severe concerns about some changes that have=20
> been done in the QSPEC template draft.
>=20
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > Sent: woensdag 20 december 2006 14:20
> > To: Georgios Karagiannis; nsis@ietf.org
> > Cc: Ash, Gerald R (Jerry), ALABS
> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> >=20
> > Hi Georgios,
> >=20
> > See below.=20
> >=20
> > > -----Original Message-----
> > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > Sent: Wednesday, December 20, 2006 5:26 AM
> > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
> > >=20
> > > Hi Jerry
> > >=20
> > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
> > >=20
> > > Comment_1:
> > > --------------
> > > Please reinclude the concept of QSPEC control information that was

> > > included in all previous versions of the QSPEC template draft.
> > > In
> > >=20
> >=20
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
> > > concept was described in Section 5.1.
> >=20
> > Please see previous email comment on QSPEC control information.
>=20
> Georgios:=20
> In order to emphasize the need of having QSPEC control information=20
> parameters  I  would however appreciate if the name of Section 4.3.3=20
> is changed
> From:
> 4.3.3 Traffic Handling Directives
> INTO:
> 4.3.3 QSPEC control information

The updated QSPEC parameter terminology/semantics are as suggested by
Dave Oran (see slides presented at IETF-67
http://www3.ietf.org/proceedings/06nov/index.html).  I think the current
terminology is more clear/descriptive of the QSPEC parameters so I don't
favor going backwards to less clear terminology.  I was never clear on
why we used the 'control information' terminology in the first place,
e.g., I don't think it's a very good descriptor of the 'excess
treatment' parameter.

Perhaps Dave can comment on this point also when he gets a chance.

> > > Comment_2:
> > > -----------
> > >=20
> > > Section 6.1:
> > > Please reintroduce the format that is required in order to
> > specify the
> > > QSPEC control information, see:
> > > Section 7.1 of:
> > > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
> >=20
> > Please see previous email comment on QSPEC control information.
>=20
>=20
> Georgios: If you rename section 4.3.3 to QSPEC control information=20
> then I think that reformatting of section 6.1 is not needed.
> Please add the proposed sentence by Dave (but change the term=20
> "handling directives" to "QSPEC control Information"). I am not sure=20
> where it is better to add this sentence, maybe in Section 5.4.
>=20
> "QoSMs are free, subject to IANA registration and review rules, to=20
> extend QSPECs by adding parameters of any of the kinds supported by=20
> the standard QSPEC. This includes traffic description parameters,=20
> constraint parameters and QSPEC control information. QoSMs are not=20
> permitted, however, to reinterpret or redefine the standard QSPEC=20
> parameters specified in this document"

Yes, the text suggested by Dave will be added.

> > > Comment_3:
> > > ----------
> > > Section 4.1 :QoS Models
> > > The definition of the QoS model is not complete. An important=20
> > > sentence that was used in the previous version of the draft is=20
> > > removed.
> > > Please add the following sentence to the definition of the QoS=20
> > > Model
> > > (QOSM):
> > >=20
> > > The same as described above have to be applied in this section.
> > > After the following sentence:
> > >=20
> > > "A QOSM specification MAY include the following:"
> > >=20
> > > include the following bullet:
> > > "- it specifies how to use QOS NSLP to signal for this QOSM"
> >=20
> > That sentence was removed in Dave's proposed QOSM re-definition, see

> > http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
> > ml.  It was unclear what that sentence meant, QoS-NSLP specifies how

> > to signal, not QOSM specifications, so the sentence was removed.
> >=20
> > I believe the sentence was intended to mean that when QoS NSLP=20
> > allows various options to be selected, a QOSM should be able to=20
> > determine which option is used.  For that purpose the following=20
> > sentence was added in Section 4.1:
> >=20
> > "     A QOSM specification MAY include the following:
> >      ...
> >      - can state which QoS-NSLP options a QOSM wants to use, when
> >      several options are available for a QOSM (e.g., local QSPEC to
> >      either be a) tunneled or b) encapsulate initiator QSPEC)."
> >=20
> > Also, to avoid any misinterpretation that QOSMs are free to specify=20
> > additional constraints, state machines, protocol data, etc. for NSLP

> > beyond that which is specific in the QoS NSLP specification, the=20
> > following was added to Section 4.1:
> >=20
> > "  QOSMs affect the operation of the RMF in NSIS-capable nodes, the
> >    information carried in QSPEC objects, and may under some
> >    circumstances (e.g. aggregation) cause a separate NSLP=20
> >    session to be
> >    instantiated by having the RMF as a QNI. QOSMs all utilize=20
> >    the common
> >    data, state machines, and APIs of the underlying NSIS=20
> >    protocols and
> >    are not expected to re-define or extend these in any way."
>=20
> Georgios:
> Regarding the sentence in Section 4.1:
> "QOSMs all utilize
> the common data, state machines, and APIs of the underlying NSIS=20
> protocols and are not expected to re-define or extend these in any=20
> way."
>=20
> This sentence restricts the possibility of QoS model to use RMF states

> and data that are not been defined in neither QoS-NSLP or QSPEC.
> This sentence should be removed.

I disagree.  The quoted text was introduced by Dave Oran in addition to
removing the phrase implying that a QOSM could specify signaling
protocol changes, and I agree with this.  Any changes/extensions to the
signaling protocol or state machines are within the scope of QoS-NSLP
draft and not the QSPEC draft or a QOSM specification draft.  I think
you have noted that also in your subsequent posting at
http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html. =20

If any extensions are required to the NSIS signaling protocol as a
result of the 'severe change on QoS Model definition and capabilities'
you have noted, those proposed changes/extensions should be addressed to
the QoS NSLP draft IMO.

Perhaps Dave can comment here also when he gets a chance.

> > > Comment_4:
> > > -------------
> > > Section 5.1 Local QSPEC definition and processing
> > >=20
> > > By reading this section it gives the impression that the two=20
> > > methods
> > > a) and b) cannot be used by the same QoS model.
> > > Method a): translate the
> > > initiator QSPEC into a local QSPEC and encapsulate the initiator=20
> > > QSPEC in the RESERVE message Method b): b) tunnel the initiator=20
> > > QSPEC through the local domain and reserve resources by generating

> > > a new RESERVE message through the local domain containing the=20
> > > local QSPEC.
> > >=20
> > > Note that according to the discussions that we have had until now=20
> > > method a) should be able to be used in combination with method b)=20
> > > by the same QoS model for the situation that the local QSPEC=20
> > > encapsulates the initiator QSPEC in order to satisfy requirement=20
> > > 5.4.2 that is specified in RFC 3726, see:
> > > http://www.ietf.org/rfc/rfc3726.txt
> > >=20
> > > Please add the following sentence at the end of the first=20
> > > paragraph of Section 5.1.
> > > "Note that when method b) is used, the encapsulation of the=20
> > > initiator QSPEC into a local QSPEC should also be possible when=20
> > > the local QoS model needs to satisfy Requirement
> > > 5.4.2 specified in RFC 3726, by adding and removing local=20
> > > QOSM-specific Control Information parameters on top of the=20
> > > initiator QSPEC."
> >=20
> > Your comment here is not clear to me.  It would help to provide an=20
> > example to illustrate what you are trying to accomplish.  It seems=20
> > that you are trying to specify QoS-NSLP functionality, rather than=20
> > QSPEC functionality.  If so, that functionality should be specified=20
> > in the QoS-NSLP draft rather than the QSPEC draft, perhaps the=20
> > QoS-NSLP authors can comment.
>=20
> Georgios:
> No I am not trying to define QOS-NSLP functionality.
> This is related to QSPEC control information that has to be carried by

> end-to-end messages.
> What I am trying to say is that all the discussion that we have had=20
> regarding the encapsulation of the QSPEC object were associated with=20
> requirement 5.4.2 of RFC 3726, see below:
>=20
> -----------------
> "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain=20
> Information
>=20
>    It SHOULD be possible to add and remove local scope elements.
>    Compared to Requirement 5.3.5 this requirement does use the normal
>    signaling process and message exchange for transporting local
>    information.  For example, at the entrance to a domain, domain-
>    specific information is added information is added, which=20
>    is used in
>    this domain only, and the information is removed again when a
>    signaling message leaves the domain.  The motivation is in the
>    economy of re-using the protocol for domain internal signaling of
>    various information pieces.  Where additional information is needed
>    within a particular domain, it should be possible to carry this at
>    the same time as the end-to-end information.", from RFC 3726
> ------------------
> Thus what I am saying is:
> Please add the following sentence at the end of the first paragraph of

> Section 5.1.
>=20
> "Note that when method b) is used, the encapsulation of the initiator=20
> QSPEC into a local QSPEC should also be possible when the local QoS=20
> model needs to satisfy Requirement
> 5.4.2 specified in RFC 3726, by adding and removing local=20
> QOSM-specific Control Information parameters on top of the initiator=20
> QSPEC."

First, the suggested text isn't clear.  If method b) is used (tunneling)
then presumably method a) is not also used at the same time.  However,
the phrasing of the above makes it sound that way.

Second, an example would help here.  I presume you are referring e.g.,
to RMD adding 'control information' (i.e., 'handling directive')
parameters to the local QSPEC that are not included in the initiator
QSPEC.  I think the requirement would be that the RMD QOSM provides a
local QSPEC that is consistent with the initiator QSPEC, as we agreed on
the list (see also slide 8 of the IETF-67 presentation).

If the local QSPEC introduces functionality inconsistent with the
initiator QSPEC by appending the handling directive parameters, then it
is not allowed.

> > > Comment_5:
> > > -----------
> > > Section 5.1, last paragraph:
> > >=20
> > > Please change the following:
> > > "For example, RMD can define a local QSPEC that contains TMOD =3D=20
> > > bandwidth (sets r=3Dp, b/m to large)."
> > >=20
> > > Into:
> > > "For example, in RMD the TMOD parameters contained in the original

> > > initiator QSPEC are mapped into the equivalent TMOD parameter=20
> > > representing only the peak bandwidth in the local QSPEC."
> >=20
> > OK with me.
> >=20
> > > Comment_6:
> > > -------------
> > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to be followed=20
> > > regarding the QSPEC control information are not given:
> > >=20
> > > Please include the following paragraph at the end of this section:
> > > "Regarding QSPEC Control Information, the default rule is that all
> > >    QSPEC parameters that have been included in the RESERVE=20
> > >    message by
> > >    the QNI are also included in the RESPONSE message by the=20
> > >    QNR with the
> > >    value they had when arriving at the QNR.  When traveling in the
> > >    RESPONSE message, all QSPEC Control Information parameters are
> > >    read-only.  Note that a QOSM specification may define its own
> > >    QOSM-specific Control Information parameters and=20
> > >    processing rules."
> >=20
> > Please see previous email comment on QSPEC control information.
>=20
> Georgios: I think that a description of how the QSPEC control=20
> information is handled is needed.

Please see above comments on 'control information' terminology.

Thanks,
Jerry
=20
> > > Comment_7:
> > > ------------
> > > Section 6.1:
> > > I do not understand the second sentence from the below two
> > > sentences:
> > > "N Flag: Not-supported QSPEC parameter flag (see Section 5.2.2).
> > >            For QSPEC parameters the value of this flag is always=20
> > > zero."
> >=20
> > Good catch, this is a typo, the sentence should be removed.
> >=20
>=20
>=20
> Best Regards,
> Georgios
>=20

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

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



From nsis-bounces@ietf.org Fri Dec 22 09:47:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gxlfy-0003zJ-2x; Fri, 22 Dec 2006 09:47:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxlfw-0003yg-39
	for nsis@ietf.org; Fri, 22 Dec 2006 09:47:08 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gxlfu-0002h2-9c
	for nsis@ietf.org; Fri, 22 Dec 2006 09:47:08 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kBMEkqfS010732; Fri, 22 Dec 2006 15:46:58 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Lars Westberg \(KI/EAB\)'" <lars.westberg@ericsson.com>,
	"'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>, <nsis@ietf.org>
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Date: Fri, 22 Dec 2006 15:46:49 +0100
Message-ID: <003401c725d8$06315b10$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAiO6wAABHXYg
In-Reply-To: <582B939025E978418C0B92DC134ADE9F365510@esealmw106.eemea.ericsson.se>
X-Spam-Score: 0.4 () FVGT_s_OBFU_Q1,FVGT_u_HAS_2LETTERFLDR
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Fri, 22 Dec 2006 15:47:00 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 17589c7043b24a47064a4b7516f59671
Cc: 
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

Hi Lars

I agree with you! Furthermore, by limiting the capabilities of the QOS
models
also the modularity and flexibility characteristrics and advanteges of NSIS
are limited.

Best regards,
Georgios

> -----Original Message-----
> From: Lars Westberg (KI/EAB) [mailto:lars.westberg@ericsson.com] 
> Sent: vrijdag 22 december 2006 15:31
> To: Ash, Gerald R (Jerry), ALABS; Georgios Karagiannis; nsis@ietf.org
> Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
> 
> Let's discuss it once more regarding the control information 
> in the QoS-model,.
> 
> The basic purpose with the QOS-model is to have modularity 
> and extendabillity for future needs. We have discussed into 
> the protocol design and I am very suprised that it suddently 
> disappear from the draft.
> 
> We have one very good example: RSVP-proxy.
> 
> If one wan't to have NSIS-proxies, 
> 	we need to control information such as: Proxy is found!! 
> 							    Proxy is
> located at this address!
> 
> This could very well be described by QoS-model control information!!!
> 
> The basic problem is that this drafts tries to limit the 
> extendabillity to exactly the same as RSVP!!! I completely 
> disagree with that approach.
> 
> There are no need to re-design RSVP with exactly the same 
> functionality!! We already have RSVP but RSVP is better 
> designed from scalabillity perspective and have support for 
> Mutlicast support. We are designing exactly the same protocol 
> but with limited functional support and without Multicast!!!!!
> Note, that we can't use NSIS for TV-broadcast !!! 
> 
> I do not beleive that NSIS can replace RSVP!!! 
> Therefore, QOS-NSLP must support other usage than RSVP!!!
> 
> I agree that the description of control information may be 
> explained better but it has to be possible to have control 
> information in the QoS-model.
> 
> But the statement into this draft makes the QoS-NSLP useless!!
> 
> 
> Regards Lasse
> 
> 
> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> Sent: den 22 december 2006 15:01
> To: Georgios Karagiannis; nsis@ietf.org
> Cc: Ash, Gerald R (Jerry), ALABS
> Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
> 
> Georgios,
> 
> See below. 
> 
> > -----Original Message-----
> > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > Sent: Thursday, December 21, 2006 9:22 AM
> > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > 
> > Hi Jerry
> > 
> > Please see below! I have severe concerns about some changes 
> that have 
> > been done in the QSPEC template draft.
> > 
> > > -----Original Message-----
> > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > > Sent: woensdag 20 december 2006 14:20
> > > To: Georgios Karagiannis; nsis@ietf.org
> > > Cc: Ash, Gerald R (Jerry), ALABS
> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > 
> > > Hi Georgios,
> > > 
> > > See below. 
> > > 
> > > > -----Original Message-----
> > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > > Sent: Wednesday, December 20, 2006 5:26 AM
> > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
> > > > 
> > > > Hi Jerry
> > > > 
> > > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
> > > > 
> > > > Comment_1:
> > > > --------------
> > > > Please reinclude the concept of QSPEC control 
> information that was
> 
> > > > included in all previous versions of the QSPEC template draft.
> > > > In
> > > > 
> > > 
> > 
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
> > > > concept was described in Section 5.1.
> > > 
> > > Please see previous email comment on QSPEC control information.
> > 
> > Georgios: 
> > In order to emphasize the need of having QSPEC control information 
> > parameters  I  would however appreciate if the name of 
> Section 4.3.3 
> > is changed
> > From:
> > 4.3.3 Traffic Handling Directives
> > INTO:
> > 4.3.3 QSPEC control information
> 
> The updated QSPEC parameter terminology/semantics are as 
> suggested by Dave Oran (see slides presented at IETF-67 
> http://www3.ietf.org/proceedings/06nov/index.html).  I think 
> the current terminology is more clear/descriptive of the 
> QSPEC parameters so I don't favor going backwards to less 
> clear terminology.  I was never clear on why we used the 
> 'control information' terminology in the first place, e.g., I 
> don't think it's a very good descriptor of the 'excess 
> treatment' parameter.
> 
> Perhaps Dave can comment on this point also when he gets a chance.
> 
> > > > Comment_2:
> > > > -----------
> > > > 
> > > > Section 6.1:
> > > > Please reintroduce the format that is required in order to
> > > specify the
> > > > QSPEC control information, see:
> > > > Section 7.1 of:
> > > > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
> > > 
> > > Please see previous email comment on QSPEC control information.
> > 
> > 
> > Georgios: If you rename section 4.3.3 to QSPEC control information 
> > then I think that reformatting of section 6.1 is not needed.
> > Please add the proposed sentence by Dave (but change the term 
> > "handling directives" to "QSPEC control Information"). I am 
> not sure 
> > where it is better to add this sentence, maybe in Section 5.4.
> > 
> > "QoSMs are free, subject to IANA registration and review rules, to 
> > extend QSPECs by adding parameters of any of the kinds supported by 
> > the standard QSPEC. This includes traffic description parameters, 
> > constraint parameters and QSPEC control information. QoSMs are not 
> > permitted, however, to reinterpret or redefine the standard QSPEC 
> > parameters specified in this document"
> 
> Yes, the text suggested by Dave will be added.
> 
> > > > Comment_3:
> > > > ----------
> > > > Section 4.1 :QoS Models
> > > > The definition of the QoS model is not complete. An important 
> > > > sentence that was used in the previous version of the draft is 
> > > > removed.
> > > > Please add the following sentence to the definition of the QoS 
> > > > Model
> > > > (QOSM):
> > > > 
> > > > The same as described above have to be applied in this section.
> > > > After the following sentence:
> > > > 
> > > > "A QOSM specification MAY include the following:"
> > > > 
> > > > include the following bullet:
> > > > "- it specifies how to use QOS NSLP to signal for this QOSM"
> > > 
> > > That sentence was removed in Dave's proposed QOSM 
> re-definition, see
> 
> > > http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
> > > ml.  It was unclear what that sentence meant, QoS-NSLP 
> specifies how
> 
> > > to signal, not QOSM specifications, so the sentence was removed.
> > > 
> > > I believe the sentence was intended to mean that when QoS NSLP 
> > > allows various options to be selected, a QOSM should be able to 
> > > determine which option is used.  For that purpose the following 
> > > sentence was added in Section 4.1:
> > > 
> > > "     A QOSM specification MAY include the following:
> > >      ...
> > >      - can state which QoS-NSLP options a QOSM wants to use, when
> > >      several options are available for a QOSM (e.g., 
> local QSPEC to
> > >      either be a) tunneled or b) encapsulate initiator QSPEC)."
> > > 
> > > Also, to avoid any misinterpretation that QOSMs are free 
> to specify 
> > > additional constraints, state machines, protocol data, 
> etc. for NSLP
> 
> > > beyond that which is specific in the QoS NSLP specification, the 
> > > following was added to Section 4.1:
> > > 
> > > "  QOSMs affect the operation of the RMF in NSIS-capable 
> nodes, the
> > >    information carried in QSPEC objects, and may under some
> > >    circumstances (e.g. aggregation) cause a separate NSLP 
> > >    session to be
> > >    instantiated by having the RMF as a QNI. QOSMs all utilize 
> > >    the common
> > >    data, state machines, and APIs of the underlying NSIS 
> > >    protocols and
> > >    are not expected to re-define or extend these in any way."
> > 
> > Georgios:
> > Regarding the sentence in Section 4.1:
> > "QOSMs all utilize
> > the common data, state machines, and APIs of the underlying NSIS 
> > protocols and are not expected to re-define or extend these in any 
> > way."
> > 
> > This sentence restricts the possibility of QoS model to use 
> RMF states
> 
> > and data that are not been defined in neither QoS-NSLP or QSPEC.
> > This sentence should be removed.
> 
> I disagree.  The quoted text was introduced by Dave Oran in 
> addition to removing the phrase implying that a QOSM could 
> specify signaling protocol changes, and I agree with this.  
> Any changes/extensions to the signaling protocol or state 
> machines are within the scope of QoS-NSLP draft and not the 
> QSPEC draft or a QOSM specification draft.  I think you have 
> noted that also in your subsequent posting at 
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html.  
> 
> If any extensions are required to the NSIS signaling protocol 
> as a result of the 'severe change on QoS Model definition and 
> capabilities'
> you have noted, those proposed changes/extensions should be 
> addressed to the QoS NSLP draft IMO.
> 
> Perhaps Dave can comment here also when he gets a chance.
> 
> > > > Comment_4:
> > > > -------------
> > > > Section 5.1 Local QSPEC definition and processing
> > > > 
> > > > By reading this section it gives the impression that the two 
> > > > methods
> > > > a) and b) cannot be used by the same QoS model.
> > > > Method a): translate the
> > > > initiator QSPEC into a local QSPEC and encapsulate the 
> initiator 
> > > > QSPEC in the RESERVE message Method b): b) tunnel the initiator 
> > > > QSPEC through the local domain and reserve resources by 
> generating
> 
> > > > a new RESERVE message through the local domain containing the 
> > > > local QSPEC.
> > > > 
> > > > Note that according to the discussions that we have had 
> until now 
> > > > method a) should be able to be used in combination with 
> method b) 
> > > > by the same QoS model for the situation that the local QSPEC 
> > > > encapsulates the initiator QSPEC in order to satisfy requirement
> > > > 5.4.2 that is specified in RFC 3726, see:
> > > > http://www.ietf.org/rfc/rfc3726.txt
> > > > 
> > > > Please add the following sentence at the end of the first 
> > > > paragraph of Section 5.1.
> > > > "Note that when method b) is used, the encapsulation of the 
> > > > initiator QSPEC into a local QSPEC should also be possible when 
> > > > the local QoS model needs to satisfy Requirement
> > > > 5.4.2 specified in RFC 3726, by adding and removing local 
> > > > QOSM-specific Control Information parameters on top of the 
> > > > initiator QSPEC."
> > > 
> > > Your comment here is not clear to me.  It would help to 
> provide an 
> > > example to illustrate what you are trying to accomplish.  
> It seems 
> > > that you are trying to specify QoS-NSLP functionality, 
> rather than 
> > > QSPEC functionality.  If so, that functionality should be 
> specified 
> > > in the QoS-NSLP draft rather than the QSPEC draft, perhaps the 
> > > QoS-NSLP authors can comment.
> > 
> > Georgios:
> > No I am not trying to define QOS-NSLP functionality.
> > This is related to QSPEC control information that has to be 
> carried by
> 
> > end-to-end messages.
> > What I am trying to say is that all the discussion that we have had 
> > regarding the encapsulation of the QSPEC object were 
> associated with 
> > requirement 5.4.2 of RFC 3726, see below:
> > 
> > -----------------
> > "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain 
> > Information
> > 
> >    It SHOULD be possible to add and remove local scope elements.
> >    Compared to Requirement 5.3.5 this requirement does use 
> the normal
> >    signaling process and message exchange for transporting local
> >    information.  For example, at the entrance to a domain, domain-
> >    specific information is added information is added, which 
> >    is used in
> >    this domain only, and the information is removed again when a
> >    signaling message leaves the domain.  The motivation is in the
> >    economy of re-using the protocol for domain internal signaling of
> >    various information pieces.  Where additional 
> information is needed
> >    within a particular domain, it should be possible to 
> carry this at
> >    the same time as the end-to-end information.", from RFC 3726
> > ------------------
> > Thus what I am saying is:
> > Please add the following sentence at the end of the first 
> paragraph of
> 
> > Section 5.1.
> > 
> > "Note that when method b) is used, the encapsulation of the 
> initiator 
> > QSPEC into a local QSPEC should also be possible when the local QoS 
> > model needs to satisfy Requirement
> > 5.4.2 specified in RFC 3726, by adding and removing local 
> > QOSM-specific Control Information parameters on top of the 
> initiator 
> > QSPEC."
> 
> First, the suggested text isn't clear.  If method b) is used 
> (tunneling) then presumably method a) is not also used at the 
> same time.  However, the phrasing of the above makes it sound 
> that way.
> 
> Second, an example would help here.  I presume you are 
> referring e.g., to RMD adding 'control information' (i.e., 
> 'handling directive') parameters to the local QSPEC that are 
> not included in the initiator QSPEC.  I think the requirement 
> would be that the RMD QOSM provides a local QSPEC that is 
> consistent with the initiator QSPEC, as we agreed on the list 
> (see also slide 8 of the IETF-67 presentation).
> 
> If the local QSPEC introduces functionality inconsistent with 
> the initiator QSPEC by appending the handling directive 
> parameters, then it is not allowed.
> 
> > > > Comment_5:
> > > > -----------
> > > > Section 5.1, last paragraph:
> > > > 
> > > > Please change the following:
> > > > "For example, RMD can define a local QSPEC that contains TMOD = 
> > > > bandwidth (sets r=p, b/m to large)."
> > > > 
> > > > Into:
> > > > "For example, in RMD the TMOD parameters contained in 
> the original
> 
> > > > initiator QSPEC are mapped into the equivalent TMOD parameter 
> > > > representing only the peak bandwidth in the local QSPEC."
> > > 
> > > OK with me.
> > > 
> > > > Comment_6:
> > > > -------------
> > > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to 
> be followed 
> > > > regarding the QSPEC control information are not given:
> > > > 
> > > > Please include the following paragraph at the end of 
> this section:
> > > > "Regarding QSPEC Control Information, the default rule 
> is that all
> > > >    QSPEC parameters that have been included in the RESERVE 
> > > >    message by
> > > >    the QNI are also included in the RESPONSE message by the 
> > > >    QNR with the
> > > >    value they had when arriving at the QNR.  When 
> traveling in the
> > > >    RESPONSE message, all QSPEC Control Information 
> parameters are
> > > >    read-only.  Note that a QOSM specification may define its own
> > > >    QOSM-specific Control Information parameters and 
> > > >    processing rules."
> > > 
> > > Please see previous email comment on QSPEC control information.
> > 
> > Georgios: I think that a description of how the QSPEC control 
> > information is handled is needed.
> 
> Please see above comments on 'control information' terminology.
> 
> Thanks,
> Jerry
>  
> > > > Comment_7:
> > > > ------------
> > > > Section 6.1:
> > > > I do not understand the second sentence from the below two
> > > > sentences:
> > > > "N Flag: Not-supported QSPEC parameter flag (see Section 5.2.2).
> > > >            For QSPEC parameters the value of this flag 
> is always 
> > > > zero."
> > > 
> > > Good catch, this is a typo, the sentence should be removed.
> > > 
> > 
> > 
> > Best Regards,
> > Georgios
> > 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 



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



From nsis-bounces@ietf.org Fri Dec 22 10:37:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxmSb-0005A0-1y; Fri, 22 Dec 2006 10:37:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxmSZ-000597-79
	for nsis@ietf.org; Fri, 22 Dec 2006 10:37:23 -0500
Received: from mail120.messagelabs.com ([216.82.250.83])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GxmSV-0002qi-Bb
	for nsis@ietf.org; Fri, 22 Dec 2006 10:37:23 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-5.tower-120.messagelabs.com!1166801835!15658553!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 23433 invoked from network); 22 Dec 2006 15:37:15 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-5.tower-120.messagelabs.com with SMTP;
	22 Dec 2006 15:37:15 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kBMFbE7L024359; 
	Fri, 22 Dec 2006 10:37:15 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst12.ugd.att.com [135.38.164.89])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id
	kBMFb2Ke024225; Fri, 22 Dec 2006 10:37:10 -0500 (EST)
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, 22 Dec 2006 09:36:47 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC806D@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <003201c725d3$581448c0$4c0d5982@dynamic.ewi.utwente.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAfQcYAABi6fQ
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "Georgios Karagiannis" <karagian@cs.utwente.nl>, <nsis@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 916029c14bdb340aa234d3ec4cd24f52
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
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

Georgios,=20

> -----Original Message-----
> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]=20
> Sent: Friday, December 22, 2006 9:13 AM
> To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt=20
>=20
> Hi Jerry
>=20
> By just saying that "these changes are suggested by Dave in=20
> the e-mail" does not work.
>=20
> The proposal of Dave was not clear on the QoS model changes that=20
> you wanted to do.=20

All changes to the draft have been extensively discussed on the list and
are all contained in the slides presented at IETF-67.  You were there at
IETF-67 and participated in all the list discussion.  The summary of
changes in the slides is quite specific and clear, take another look.
Have a look at the minutes as well
http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt.  The only
disagreements noted are with regard to stacking, which is an issue that
we later resolved on the list.  Go back and check it out.

> Now I understand which changes you want to include in the=20
> QSPEC template draft.
> This is also the reason of disagreeing with you now and=20
> sending comments to the nsis list.

I responded to your further comments, see below.  Others are encouraged
to comment as well.

Jerry

>=20
> Furthermore, note that the QOS-NSLP draft defines which capabilities=20
> should be supported by the QoS models and not the=20
> QSPEC template draft.
>=20
> Best Regards,
> Georgios
>=20
>=20
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]=20
> > Sent: vrijdag 22 december 2006 15:01
> > To: Georgios Karagiannis; nsis@ietf.org
> > Cc: Ash, Gerald R (Jerry), ALABS
> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt=20
> >=20
> > Georgios,
> >=20
> > See below.=20
> >=20
> > > -----Original Message-----
> > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > Sent: Thursday, December 21, 2006 9:22 AM
> > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > >=20
> > > Hi Jerry
> > >=20
> > > Please see below! I have severe concerns about some changes=20
> > that have=20
> > > been done in the QSPEC template draft.
> > >=20
> > > > -----Original Message-----
> > > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > > > Sent: woensdag 20 december 2006 14:20
> > > > To: Georgios Karagiannis; nsis@ietf.org
> > > > Cc: Ash, Gerald R (Jerry), ALABS
> > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > >=20
> > > > Hi Georgios,
> > > >=20
> > > > See below.=20
> > > >=20
> > > > > -----Original Message-----
> > > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > > > Sent: Wednesday, December 20, 2006 5:26 AM
> > > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
> > > > >=20
> > > > > Hi Jerry
> > > > >=20
> > > > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
> > > > >=20
> > > > > Comment_1:
> > > > > --------------
> > > > > Please reinclude the concept of QSPEC control=20
> > information that was=20
> > > > > included in all previous versions of the QSPEC template draft.
> > > > > In
> > > > >=20
> > > >=20
> > >=20
> >=20
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
> > > > > concept was described in Section 5.1.
> > > >=20
> > > > Please see previous email comment on QSPEC control information.
> > >=20
> > > Georgios:=20
> > > In order to emphasize the need of having QSPEC control=20
> information=20
> > > parameters  I  would however appreciate if the name of=20
> > Section 4.3.3=20
> > > is changed
> > > From:
> > > 4.3.3 Traffic Handling Directives
> > > INTO:
> > > 4.3.3 QSPEC control information
> >=20
> > The updated QSPEC parameter terminology/semantics are as=20
> > suggested by Dave Oran (see slides presented at IETF-67=20
> > http://www3.ietf.org/proceedings/06nov/index.html).  I think=20
> > the current terminology is more clear/descriptive of the=20
> > QSPEC parameters so I don't favor going backwards to less=20
> > clear terminology.  I was never clear on why we used the=20
> > 'control information' terminology in the first place, e.g., I=20
> > don't think it's a very good descriptor of the 'excess=20
> > treatment' parameter.
> >=20
> > Perhaps Dave can comment on this point also when he gets a chance.
> >=20
> > > > > Comment_2:
> > > > > -----------
> > > > >=20
> > > > > Section 6.1:
> > > > > Please reintroduce the format that is required in order to
> > > > specify the
> > > > > QSPEC control information, see:
> > > > > Section 7.1 of:
> > > > >=20
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
> > > >=20
> > > > Please see previous email comment on QSPEC control information.
> > >=20
> > >=20
> > > Georgios: If you rename section 4.3.3 to QSPEC control=20
> information=20
> > > then I think that reformatting of section 6.1 is not needed.
> > > Please add the proposed sentence by Dave (but change the term=20
> > > "handling directives" to "QSPEC control Information"). I am=20
> > not sure=20
> > > where it is better to add this sentence, maybe in Section 5.4.
> > >=20
> > > "QoSMs are free, subject to IANA registration and review=20
> rules, to=20
> > > extend QSPECs by adding parameters of any of the kinds=20
> supported by=20
> > > the standard QSPEC. This includes traffic description parameters,=20
> > > constraint parameters and QSPEC control information.=20
> QoSMs are not=20
> > > permitted, however, to reinterpret or redefine the standard QSPEC=20
> > > parameters specified in this document"
> >=20
> > Yes, the text suggested by Dave will be added.
> >=20
> > > > > Comment_3:
> > > > > ----------
> > > > > Section 4.1 :QoS Models
> > > > > The definition of the QoS model is not complete. An important=20
> > > > > sentence that was used in the previous version of the=20
> draft is=20
> > > > > removed.
> > > > > Please add the following sentence to the definition=20
> of the QoS=20
> > > > > Model
> > > > > (QOSM):
> > > > >=20
> > > > > The same as described above have to be applied in=20
> this section.
> > > > > After the following sentence:
> > > > >=20
> > > > > "A QOSM specification MAY include the following:"
> > > > >=20
> > > > > include the following bullet:
> > > > > "- it specifies how to use QOS NSLP to signal for this QOSM"
> > > >=20
> > > > That sentence was removed in Dave's proposed QOSM=20
> > re-definition, see=20
> > > > http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
> > > > ml.  It was unclear what that sentence meant, QoS-NSLP=20
> > specifies how=20
> > > > to signal, not QOSM specifications, so the sentence was removed.
> > > >=20
> > > > I believe the sentence was intended to mean that when QoS NSLP=20
> > > > allows various options to be selected, a QOSM should be able to=20
> > > > determine which option is used.  For that purpose the following=20
> > > > sentence was added in Section 4.1:
> > > >=20
> > > > "     A QOSM specification MAY include the following:
> > > >      ...
> > > >      - can state which QoS-NSLP options a QOSM wants to=20
> use, when
> > > >      several options are available for a QOSM (e.g.,=20
> > local QSPEC to
> > > >      either be a) tunneled or b) encapsulate initiator QSPEC)."
> > > >=20
> > > > Also, to avoid any misinterpretation that QOSMs are free=20
> > to specify=20
> > > > additional constraints, state machines, protocol data,=20
> > etc. for NSLP=20
> > > > beyond that which is specific in the QoS NSLP=20
> specification, the=20
> > > > following was added to Section 4.1:
> > > >=20
> > > > "  QOSMs affect the operation of the RMF in NSIS-capable=20
> > nodes, the
> > > >    information carried in QSPEC objects, and may under some
> > > >    circumstances (e.g. aggregation) cause a separate NSLP=20
> > > >    session to be
> > > >    instantiated by having the RMF as a QNI. QOSMs all utilize=20
> > > >    the common
> > > >    data, state machines, and APIs of the underlying NSIS=20
> > > >    protocols and
> > > >    are not expected to re-define or extend these in any way."
> > >=20
> > > Georgios:
> > > Regarding the sentence in Section 4.1:
> > > "QOSMs all utilize
> > > the common data, state machines, and APIs of the underlying NSIS=20
> > > protocols and are not expected to re-define or extend=20
> these in any=20
> > > way."
> > >=20
> > > This sentence restricts the possibility of QoS model to use=20
> > RMF states=20
> > > and data that are not been defined in neither QoS-NSLP or QSPEC.
> > > This sentence should be removed.
> >=20
> > I disagree.  The quoted text was introduced by Dave Oran in=20
> > addition to removing the phrase implying that a QOSM could=20
> > specify signaling protocol changes, and I agree with this. =20
> > Any changes/extensions to the signaling protocol or state=20
> > machines are within the scope of QoS-NSLP draft and not the=20
> > QSPEC draft or a QOSM specification draft.  I think you have=20
> > noted that also in your subsequent posting at=20
> > http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html. =20
> >=20
> > If any extensions are required to the NSIS signaling protocol=20
> > as a result of the 'severe change on QoS Model definition and=20
> > capabilities'
> > you have noted, those proposed changes/extensions should be=20
> > addressed to the QoS NSLP draft IMO.
> >=20
> > Perhaps Dave can comment here also when he gets a chance.
> >=20
> > > > > Comment_4:
> > > > > -------------
> > > > > Section 5.1 Local QSPEC definition and processing
> > > > >=20
> > > > > By reading this section it gives the impression that the two=20
> > > > > methods
> > > > > a) and b) cannot be used by the same QoS model.
> > > > > Method a): translate the
> > > > > initiator QSPEC into a local QSPEC and encapsulate the=20
> > initiator=20
> > > > > QSPEC in the RESERVE message Method b): b) tunnel the=20
> initiator=20
> > > > > QSPEC through the local domain and reserve resources by=20
> > generating=20
> > > > > a new RESERVE message through the local domain containing the=20
> > > > > local QSPEC.
> > > > >=20
> > > > > Note that according to the discussions that we have had=20
> > until now=20
> > > > > method a) should be able to be used in combination with=20
> > method b)=20
> > > > > by the same QoS model for the situation that the local QSPEC=20
> > > > > encapsulates the initiator QSPEC in order to satisfy=20
> > requirement=20
> > > > > 5.4.2 that is specified in RFC 3726, see:
> > > > > http://www.ietf.org/rfc/rfc3726.txt
> > > > >=20
> > > > > Please add the following sentence at the end of the first=20
> > > > > paragraph of Section 5.1.
> > > > > "Note that when method b) is used, the encapsulation of the=20
> > > > > initiator QSPEC into a local QSPEC should also be=20
> possible when=20
> > > > > the local QoS model needs to satisfy Requirement
> > > > > 5.4.2 specified in RFC 3726, by adding and removing local=20
> > > > > QOSM-specific Control Information parameters on top of the=20
> > > > > initiator QSPEC."
> > > >=20
> > > > Your comment here is not clear to me.  It would help to=20
> > provide an=20
> > > > example to illustrate what you are trying to accomplish. =20
> > It seems=20
> > > > that you are trying to specify QoS-NSLP functionality,=20
> > rather than=20
> > > > QSPEC functionality.  If so, that functionality should be=20
> > specified=20
> > > > in the QoS-NSLP draft rather than the QSPEC draft, perhaps the=20
> > > > QoS-NSLP authors can comment.
> > >=20
> > > Georgios:
> > > No I am not trying to define QOS-NSLP functionality.
> > > This is related to QSPEC control information that has to be=20
> > carried by=20
> > > end-to-end messages.
> > > What I am trying to say is that all the discussion that=20
> we have had=20
> > > regarding the encapsulation of the QSPEC object were=20
> > associated with=20
> > > requirement 5.4.2 of RFC 3726, see below:
> > >=20
> > > -----------------
> > > "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain=20
> > > Information
> > >=20
> > >    It SHOULD be possible to add and remove local scope elements.
> > >    Compared to Requirement 5.3.5 this requirement does use=20
> > the normal
> > >    signaling process and message exchange for transporting local
> > >    information.  For example, at the entrance to a domain, domain-
> > >    specific information is added information is added, which=20
> > >    is used in
> > >    this domain only, and the information is removed again when a
> > >    signaling message leaves the domain.  The motivation is in the
> > >    economy of re-using the protocol for domain internal=20
> signaling of
> > >    various information pieces.  Where additional=20
> > information is needed
> > >    within a particular domain, it should be possible to=20
> > carry this at
> > >    the same time as the end-to-end information.", from RFC 3726
> > > ------------------
> > > Thus what I am saying is:
> > > Please add the following sentence at the end of the first=20
> > paragraph of=20
> > > Section 5.1.
> > >=20
> > > "Note that when method b) is used, the encapsulation of the=20
> > initiator=20
> > > QSPEC into a local QSPEC should also be possible when the=20
> local QoS=20
> > > model needs to satisfy Requirement
> > > 5.4.2 specified in RFC 3726, by adding and removing local=20
> > > QOSM-specific Control Information parameters on top of the=20
> > initiator=20
> > > QSPEC."
> >=20
> > First, the suggested text isn't clear.  If method b) is used=20
> > (tunneling) then presumably method a) is not also used at the=20
> > same time.  However, the phrasing of the above makes it sound=20
> > that way.
> >=20
> > Second, an example would help here.  I presume you are=20
> > referring e.g., to RMD adding 'control information' (i.e.,=20
> > 'handling directive') parameters to the local QSPEC that are=20
> > not included in the initiator QSPEC.  I think the requirement=20
> > would be that the RMD QOSM provides a local QSPEC that is=20
> > consistent with the initiator QSPEC, as we agreed on the list=20
> > (see also slide 8 of the IETF-67 presentation).
> >=20
> > If the local QSPEC introduces functionality inconsistent with=20
> > the initiator QSPEC by appending the handling directive=20
> > parameters, then it is not allowed.
> >=20
> > > > > Comment_5:
> > > > > -----------
> > > > > Section 5.1, last paragraph:
> > > > >=20
> > > > > Please change the following:
> > > > > "For example, RMD can define a local QSPEC that=20
> contains TMOD =3D=20
> > > > > bandwidth (sets r=3Dp, b/m to large)."
> > > > >=20
> > > > > Into:
> > > > > "For example, in RMD the TMOD parameters contained in=20
> > the original=20
> > > > > initiator QSPEC are mapped into the equivalent TMOD parameter=20
> > > > > representing only the peak bandwidth in the local QSPEC."
> > > >=20
> > > > OK with me.
> > > >=20
> > > > > Comment_6:
> > > > > -------------
> > > > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to=20
> > be followed=20
> > > > > regarding the QSPEC control information are not given:
> > > > >=20
> > > > > Please include the following paragraph at the end of=20
> > this section:
> > > > > "Regarding QSPEC Control Information, the default rule=20
> > is that all
> > > > >    QSPEC parameters that have been included in the RESERVE=20
> > > > >    message by
> > > > >    the QNI are also included in the RESPONSE message by the=20
> > > > >    QNR with the
> > > > >    value they had when arriving at the QNR.  When=20
> > traveling in the
> > > > >    RESPONSE message, all QSPEC Control Information=20
> > parameters are
> > > > >    read-only.  Note that a QOSM specification may=20
> define its own
> > > > >    QOSM-specific Control Information parameters and=20
> > > > >    processing rules."
> > > >=20
> > > > Please see previous email comment on QSPEC control information.
> > >=20
> > > Georgios: I think that a description of how the QSPEC control=20
> > > information is handled is needed.
> >=20
> > Please see above comments on 'control information' terminology.
> >=20
> > Thanks,
> > Jerry
> > =20
> > > > > Comment_7:
> > > > > ------------
> > > > > Section 6.1:
> > > > > I do not understand the second sentence from the below two
> > > > > sentences:
> > > > > "N Flag: Not-supported QSPEC parameter flag (see=20
> Section 5.2.2).
> > > > >            For QSPEC parameters the value of this flag=20
> > is always=20
> > > > > zero."
> > > >=20
> > > > Good catch, this is a typo, the sentence should be removed.
> > > >=20
> > >=20
> > >=20
> > > Best Regards,
> > > Georgios
> > >=20
> >=20
>=20
>=20
>=20

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



From nsis-bounces@ietf.org Fri Dec 22 10:41:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxmW4-0007EE-ED; Fri, 22 Dec 2006 10:41:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxmW3-0007E8-1f
	for nsis@ietf.org; Fri, 22 Dec 2006 10:40:59 -0500
Received: from mclmx.mail.saic.com ([149.8.64.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxmW1-0003Pn-PG
	for nsis@ietf.org; Fri, 22 Dec 2006 10:40:59 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx.mail.saic.com; Fri, 22 Dec 2006 10:40:44 -0500
Received: from 0015-ITS-EXBH01.us.saic.com ([10.43.229.18])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006122210404317289 ; Fri, 22 Dec 2006 10:40:44 -0500
Received: from 0591-ITS-EXMP02.us.saic.com ([10.42.81.248]) by
	0015-ITS-EXBH01.us.saic.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Dec 2006 10:40:44 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Date: Fri, 22 Dec 2006 10:40:43 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426E1CF72@0591-ITS-EXMP02.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAg3qsAAC7+Zv
References: <582B939025E978418C0B92DC134ADE9F3654F0@esealmw106.eemea.ericsson.se>
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: "Lars Westberg \(KI/EAB\)" <lars.westberg@ericsson.com>,
	"Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	"Georgios Karagiannis" <karagian@cs.utwente.nl>, <nsis@ietf.org>
X-OriginalArrivalTime: 22 Dec 2006 15:40:44.0426 (UTC)
	FILETIME=[8B0E66A0:01C725DF]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: 
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>
Content-Type: multipart/mixed; boundary="===============1063962949=="
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1063962949==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C725DF.8A735A0E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C725DF.8A735A0E
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Lars and all:
=20
The root cause has been that this draft has only one purpose: "Sell =
so-called ITU-T's QOS SLA  - Y.1415 as QOS Model in the IETF."
=20
No matter what you suggest technically, the so-called =
"like-minded-people" will come back with different arguments even =
modifying the basic thing like - deform the very definition of QOS model =
or make QOS-NSLP useless.=20
=20
But they will NEVER remove QOS SLA Y.1415!!!
=20
Now is the time to appoint of a NEW (single) EDITOR for this draft.
=20
Otherwise, let is be an individual non-WG draft, and no one will make =
any comments and let the "like-minded-people" work as they like.
=20
Best regards,
Radhika

________________________________

From: nsis-bounces@ietf.org on behalf of Lars Westberg (KI/EAB)
Sent: Fri 12/22/2006 9:10 AM
To: Ash, Gerald R (Jerry), ALABS; Georgios Karagiannis; nsis@ietf.org
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20



I have a severe problem with the procedure of changing the draft.
The changes you are refereing to has to be discussed before the draft is
changed.

I therefore requesting that the new draft should be an working group
draft.

Regard Lasse




------_=_NextPart_001_01C725DF.8A735A0E
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: [NSIS] RE: Comments on =
draft-ietf-nsis-qspec-13.txt</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText89459 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Lars and =
all:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>The root cause has been that =
this draft has only one purpose:&nbsp;"Sell so-called ITU-T's QOS =
SLA&nbsp; - Y.1415 as QOS Model in the IETF."</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>No matter what you suggest =
technically, the so-called "like-minded-people" will come back with =
different arguments even modifying the basic thing like - deform the =
very definition of QOS model or make QOS-NSLP useless. </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>But they will NEVER remove =
QOS SLA Y.1415!!!</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Now is the time to appoint of =
a NEW (single) EDITOR for this draft.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Otherwise, let is be an =
individual non-WG draft, and no one will make any comments and let the =
"like-minded-people" work as they like.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Best regards,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Radhika</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> nsis-bounces@ietf.org on =
behalf of Lars Westberg (KI/EAB)<BR><B>Sent:</B> Fri 12/22/2006 9:10 =
AM<BR><B>To:</B> Ash, Gerald R (Jerry), ALABS; Georgios Karagiannis; =
nsis@ietf.org<BR><B>Subject:</B> RE: [NSIS] RE: Comments on =
draft-ietf-nsis-qspec-13.txt <BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>I have a severe problem with the procedure of changing =
the draft.<BR>The changes you are refereing to has to be discussed =
before the draft is<BR>changed.<BR><BR>I therefore requesting that the =
new draft should be an working group<BR>draft.<BR><BR>Regard =
Lasse<BR><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C725DF.8A735A0E--


--===============1063962949==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1063962949==--




From nsis-bounces@ietf.org Fri Dec 22 10:48:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gxmd2-0002UL-Lr; Fri, 22 Dec 2006 10:48:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxmd1-0002TP-DJ
	for nsis@ietf.org; Fri, 22 Dec 2006 10:48:11 -0500
Received: from mclmx.mail.saic.com ([149.8.64.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gxmcz-0004bZ-VW
	for nsis@ietf.org; Fri, 22 Dec 2006 10:48:11 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx.mail.saic.com; Fri, 22 Dec 2006 10:47:57 -0500
Received: from 0015-ITS-EXBH01.us.saic.com ([10.43.229.18])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006122210475618643 ; Fri, 22 Dec 2006 10:47:56 -0500
Received: from 0591-ITS-EXMP02.us.saic.com ([10.42.81.248]) by
	0015-ITS-EXBH01.us.saic.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Dec 2006 10:47:56 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Date: Fri, 22 Dec 2006 10:47:55 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426E1CF73@0591-ITS-EXMP02.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAfQcYAABi6fQAAHO094=
References: <9473683187ADC049A855ED2DA739ABCA0DDC806D@KCCLUST06EVS1.ugd.att.com>
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	"Georgios Karagiannis" <karagian@cs.utwente.nl>, <nsis@ietf.org>
X-OriginalArrivalTime: 22 Dec 2006 15:47:56.0190 (UTC)
	FILETIME=[8C685BE0:01C725E0]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a92270ba83d7ead10c5001bb42ec3221
Cc: 
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>
Content-Type: multipart/mixed; boundary="===============0161292788=="
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0161292788==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C725E0.8C08775C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C725E0.8C08775C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

All those changes do not reflect the work group discussions as some of =
them Georgios mentioned.
=20
It does not have to the way you so-called co-editors think so. If the WG =
agrees with the changes that you have made in the draft, then why do =
these WG people disagree with you?
=20
Do you have technical explanations to answer Georgeo's points?
=20
If not, it is the time to leave this draft to a NEW editor who work =
based on WG technical consensus. Or, submit as individual non-WG draft. =
It is so simple.
=20
Best regards,
Radhika

________________________________

From: nsis-bounces@ietf.org on behalf of Ash, Gerald R (Jerry), ALABS
Sent: Fri 12/22/2006 10:36 AM
To: Georgios Karagiannis; nsis@ietf.org
Cc: Ash, Gerald R (Jerry), ALABS
Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20



Georgios,

> -----Original Message-----
> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> Sent: Friday, December 22, 2006 9:13 AM
> To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>
> Hi Jerry
>
> By just saying that "these changes are suggested by Dave in
> the e-mail" does not work.
>
> The proposal of Dave was not clear on the QoS model changes that
> you wanted to do.

All changes to the draft have been extensively discussed on the list and
are all contained in the slides presented at IETF-67.  You were there at
IETF-67 and participated in all the list discussion.  The summary of
changes in the slides is quite specific and clear, take another look.
Have a look at the minutes as well
http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt.  The only
disagreements noted are with regard to stacking, which is an issue that
we later resolved on the list.  Go back and check it out.

> Now I understand which changes you want to include in the
> QSPEC template draft.
> This is also the reason of disagreeing with you now and
> sending comments to the nsis list.

I responded to your further comments, see below.  Others are encouraged
to comment as well.

Jerry

>
> Furthermore, note that the QOS-NSLP draft defines which capabilities
> should be supported by the QoS models and not the
> QSPEC template draft.
>
> Best Regards,
> Georgios
>
>
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > Sent: vrijdag 22 december 2006 15:01
> > To: Georgios Karagiannis; nsis@ietf.org
> > Cc: Ash, Gerald R (Jerry), ALABS
> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> >
> > Georgios,
> >
> > See below.
> >
> > > -----Original Message-----
> > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > Sent: Thursday, December 21, 2006 9:22 AM
> > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > >
> > > Hi Jerry
> > >
> > > Please see below! I have severe concerns about some changes
> > that have
> > > been done in the QSPEC template draft.
> > >
>


------_=_NextPart_001_01C725E0.8C08775C
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>[NSIS] RE: Comments on =
draft-ietf-nsis-qspec-13.txt</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText222 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>All those =
changes do not reflect the work group discussions as some of them =
Georgios mentioned.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>It does not have to the way =
you so-called co-editors think so. If the WG agrees with the changes =
that you have made in the draft, then why do these WG people disagree =
with you?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Do you have technical =
explanations to answer Georgeo's points?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>If not, it is the time to =
leave this draft to&nbsp;a NEW editor who work based on WG technical =
consensus. Or, submit as individual non-WG draft. It is so =
simple.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Best regards,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Radhika</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> nsis-bounces@ietf.org on =
behalf of Ash, Gerald R (Jerry), ALABS<BR><B>Sent:</B> Fri 12/22/2006 =
10:36 AM<BR><B>To:</B> Georgios Karagiannis; nsis@ietf.org<BR><B>Cc:</B> =
Ash, Gerald R (Jerry), ALABS<BR><B>Subject:</B> [NSIS] RE: Comments on =
draft-ietf-nsis-qspec-13.txt <BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Georgios,<BR><BR>&gt; -----Original =
Message-----<BR>&gt; From: Georgios Karagiannis [<A =
href=3D"mailto:karagian@cs.utwente.nl">mailto:karagian@cs.utwente.nl</A>]=
<BR>&gt; Sent: Friday, December 22, 2006 9:13 AM<BR>&gt; To: Ash, Gerald =
R (Jerry), ALABS; nsis@ietf.org<BR>&gt; Subject: RE: Comments on =
draft-ietf-nsis-qspec-13.txt<BR>&gt;<BR>&gt; Hi Jerry<BR>&gt;<BR>&gt; By =
just saying that "these changes are suggested by Dave in<BR>&gt; the =
e-mail" does not work.<BR>&gt;<BR>&gt; The proposal of Dave was not =
clear on the QoS model changes that<BR>&gt; you wanted to do.<BR><BR>All =
changes to the draft have been extensively discussed on the list =
and<BR>are all contained in the slides presented at IETF-67.&nbsp; You =
were there at<BR>IETF-67 and participated in all the list =
discussion.&nbsp; The summary of<BR>changes in the slides is quite =
specific and clear, take another look.<BR>Have a look at the minutes as =
well<BR><A =
href=3D"http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt">http://w=
ww3.ietf.org/proceedings/06nov/minutes/nsis.txt</A>.&nbsp; The =
only<BR>disagreements noted are with regard to stacking, which is an =
issue that<BR>we later resolved on the list.&nbsp; Go back and check it =
out.<BR><BR>&gt; Now I understand which changes you want to include in =
the<BR>&gt; QSPEC template draft.<BR>&gt; This is also the reason of =
disagreeing with you now and<BR>&gt; sending comments to the nsis =
list.<BR><BR>I responded to your further comments, see below.&nbsp; =
Others are encouraged<BR>to comment as =
well.<BR><BR>Jerry<BR><BR>&gt;<BR>&gt; Furthermore, note that the =
QOS-NSLP draft defines which capabilities<BR>&gt; should be supported by =
the QoS models and not the<BR>&gt; QSPEC template draft.<BR>&gt;<BR>&gt; =
Best Regards,<BR>&gt; Georgios<BR>&gt;<BR>&gt;<BR>&gt; &gt; =
-----Original Message-----<BR>&gt; &gt; From: Ash, Gerald R (Jerry), =
ALABS [<A href=3D"mailto:gash@att.com">mailto:gash@att.com</A>]<BR>&gt; =
&gt; Sent: vrijdag 22 december 2006 15:01<BR>&gt; &gt; To: Georgios =
Karagiannis; nsis@ietf.org<BR>&gt; &gt; Cc: Ash, Gerald R (Jerry), =
ALABS<BR>&gt; &gt; Subject: RE: Comments on =
draft-ietf-nsis-qspec-13.txt<BR>&gt; &gt;<BR>&gt; &gt; Georgios,<BR>&gt; =
&gt;<BR>&gt; &gt; See below.<BR>&gt; &gt;<BR>&gt; &gt; &gt; =
-----Original Message-----<BR>&gt; &gt; &gt; From: Georgios Karagiannis =
[<A =
href=3D"mailto:karagian@cs.utwente.nl">mailto:karagian@cs.utwente.nl</A>]=
<BR>&gt; &gt; &gt; Sent: Thursday, December 21, 2006 9:22 AM<BR>&gt; =
&gt; &gt; To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org<BR>&gt; &gt; =
&gt; Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'<BR>&gt; &gt; &gt; =
Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt; Hi Jerry<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; =
Please see below! I have severe concerns about some changes<BR>&gt; &gt; =
that have<BR>&gt; &gt; &gt; been done in the QSPEC template =
draft.<BR>&gt; &gt; &gt;<BR>&gt;</FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C725E0.8C08775C--


--===============0161292788==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0161292788==--




From nsis-bounces@ietf.org Fri Dec 22 11:28:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxnG8-0006lJ-N7; Fri, 22 Dec 2006 11:28:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxnG7-0006jq-Ky
	for nsis@ietf.org; Fri, 22 Dec 2006 11:28:35 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxnG4-0005JK-Ob
	for nsis@ietf.org; Fri, 22 Dec 2006 11:28:35 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kBMGSGxC014514; Fri, 22 Dec 2006 17:28:25 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>, <nsis@ietf.org>
Date: Fri, 22 Dec 2006 17:28:12 +0100
Message-ID: <003801c725e6$304b8570$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAfQcYAABi6fQAANLmKA=
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC806D@KCCLUST06EVS1.ugd.att.com>
X-Spam-Score: 0.4 () FVGT_s_OBFU_Q1,FVGT_u_HAS_2LETTERFLDR
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Fri, 22 Dec 2006 17:28:27 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d4a1871e876bd836d4c351e861e8720d
Cc: 
Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
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

Hi Jerry

The changes that are included in version 13 of the QSEPC template draft 
regarding the QSPEC control information and the
limitations of the QoS models have never been 
discussed because they were never stated clearly. 

If they would have been stated clearly then I would 
have sent my comments at that time instead 
of sending them now!

Best Regards,
Georgios

 

> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> Sent: vrijdag 22 december 2006 16:37
> To: Georgios Karagiannis; nsis@ietf.org
> Cc: Ash, Gerald R (Jerry), ALABS
> Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt 
> 
> Georgios, 
> 
> > -----Original Message-----
> > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > Sent: Friday, December 22, 2006 9:13 AM
> > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > 
> > Hi Jerry
> > 
> > By just saying that "these changes are suggested by Dave in the 
> > e-mail" does not work.
> > 
> > The proposal of Dave was not clear on the QoS model changes 
> that you 
> > wanted to do.
> 
> All changes to the draft have been extensively discussed on 
> the list and are all contained in the slides presented at 
> IETF-67.  You were there at
> IETF-67 and participated in all the list discussion.  The 
> summary of changes in the slides is quite specific and clear, 
> take another look.
> Have a look at the minutes as well
> http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt.  The 
> only disagreements noted are with regard to stacking, which 
> is an issue that we later resolved on the list.  Go back and 
> check it out.
> 
> > Now I understand which changes you want to include in the QSPEC 
> > template draft.
> > This is also the reason of disagreeing with you now and sending 
> > comments to the nsis list.
> 
> I responded to your further comments, see below.  Others are 
> encouraged to comment as well.
> 
> Jerry
> 
> > 
> > Furthermore, note that the QOS-NSLP draft defines which 
> capabilities 
> > should be supported by the QoS models and not the QSPEC template 
> > draft.
> > 
> > Best Regards,
> > Georgios
> > 
> > 
> > > -----Original Message-----
> > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > > Sent: vrijdag 22 december 2006 15:01
> > > To: Georgios Karagiannis; nsis@ietf.org
> > > Cc: Ash, Gerald R (Jerry), ALABS
> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > 
> > > Georgios,
> > > 
> > > See below. 
> > > 
> > > > -----Original Message-----
> > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > > Sent: Thursday, December 21, 2006 9:22 AM
> > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
> > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > > 
> > > > Hi Jerry
> > > > 
> > > > Please see below! I have severe concerns about some changes
> > > that have
> > > > been done in the QSPEC template draft.
> > > > 
> > > > > -----Original Message-----
> > > > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > > > > Sent: woensdag 20 december 2006 14:20
> > > > > To: Georgios Karagiannis; nsis@ietf.org
> > > > > Cc: Ash, Gerald R (Jerry), ALABS
> > > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > > > 
> > > > > Hi Georgios,
> > > > > 
> > > > > See below. 
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > > > > Sent: Wednesday, December 20, 2006 5:26 AM
> > > > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > > > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
> > > > > > 
> > > > > > Hi Jerry
> > > > > > 
> > > > > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
> > > > > > 
> > > > > > Comment_1:
> > > > > > --------------
> > > > > > Please reinclude the concept of QSPEC control
> > > information that was
> > > > > > included in all previous versions of the QSPEC 
> template draft.
> > > > > > In
> > > > > > 
> > > > > 
> > > > 
> > > 
> > 
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
> > > > > > concept was described in Section 5.1.
> > > > > 
> > > > > Please see previous email comment on QSPEC control 
> information.
> > > > 
> > > > Georgios: 
> > > > In order to emphasize the need of having QSPEC control
> > information
> > > > parameters  I  would however appreciate if the name of
> > > Section 4.3.3
> > > > is changed
> > > > From:
> > > > 4.3.3 Traffic Handling Directives
> > > > INTO:
> > > > 4.3.3 QSPEC control information
> > > 
> > > The updated QSPEC parameter terminology/semantics are as 
> suggested 
> > > by Dave Oran (see slides presented at IETF-67 
> > > http://www3.ietf.org/proceedings/06nov/index.html).  I think the 
> > > current terminology is more clear/descriptive of the QSPEC 
> > > parameters so I don't favor going backwards to less clear 
> > > terminology.  I was never clear on why we used the 'control 
> > > information' terminology in the first place, e.g., I don't think 
> > > it's a very good descriptor of the 'excess treatment' parameter.
> > > 
> > > Perhaps Dave can comment on this point also when he gets a chance.
> > > 
> > > > > > Comment_2:
> > > > > > -----------
> > > > > > 
> > > > > > Section 6.1:
> > > > > > Please reintroduce the format that is required in order to
> > > > > specify the
> > > > > > QSPEC control information, see:
> > > > > > Section 7.1 of:
> > > > > > 
> > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
> > > > > 
> > > > > Please see previous email comment on QSPEC control 
> information.
> > > > 
> > > > 
> > > > Georgios: If you rename section 4.3.3 to QSPEC control
> > information
> > > > then I think that reformatting of section 6.1 is not needed.
> > > > Please add the proposed sentence by Dave (but change the term 
> > > > "handling directives" to "QSPEC control Information"). I am
> > > not sure
> > > > where it is better to add this sentence, maybe in Section 5.4.
> > > > 
> > > > "QoSMs are free, subject to IANA registration and review
> > rules, to
> > > > extend QSPECs by adding parameters of any of the kinds
> > supported by
> > > > the standard QSPEC. This includes traffic description 
> parameters, 
> > > > constraint parameters and QSPEC control information.
> > QoSMs are not
> > > > permitted, however, to reinterpret or redefine the 
> standard QSPEC 
> > > > parameters specified in this document"
> > > 
> > > Yes, the text suggested by Dave will be added.
> > > 
> > > > > > Comment_3:
> > > > > > ----------
> > > > > > Section 4.1 :QoS Models
> > > > > > The definition of the QoS model is not complete. An 
> important 
> > > > > > sentence that was used in the previous version of the
> > draft is
> > > > > > removed.
> > > > > > Please add the following sentence to the definition
> > of the QoS
> > > > > > Model
> > > > > > (QOSM):
> > > > > > 
> > > > > > The same as described above have to be applied in
> > this section.
> > > > > > After the following sentence:
> > > > > > 
> > > > > > "A QOSM specification MAY include the following:"
> > > > > > 
> > > > > > include the following bullet:
> > > > > > "- it specifies how to use QOS NSLP to signal for this QOSM"
> > > > > 
> > > > > That sentence was removed in Dave's proposed QOSM
> > > re-definition, see
> > > > > http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
> > > > > ml.  It was unclear what that sentence meant, QoS-NSLP
> > > specifies how
> > > > > to signal, not QOSM specifications, so the sentence 
> was removed.
> > > > > 
> > > > > I believe the sentence was intended to mean that when 
> QoS NSLP 
> > > > > allows various options to be selected, a QOSM should 
> be able to 
> > > > > determine which option is used.  For that purpose the 
> following 
> > > > > sentence was added in Section 4.1:
> > > > > 
> > > > > "     A QOSM specification MAY include the following:
> > > > >      ...
> > > > >      - can state which QoS-NSLP options a QOSM wants to
> > use, when
> > > > >      several options are available for a QOSM (e.g.,
> > > local QSPEC to
> > > > >      either be a) tunneled or b) encapsulate 
> initiator QSPEC)."
> > > > > 
> > > > > Also, to avoid any misinterpretation that QOSMs are free
> > > to specify
> > > > > additional constraints, state machines, protocol data,
> > > etc. for NSLP
> > > > > beyond that which is specific in the QoS NSLP
> > specification, the
> > > > > following was added to Section 4.1:
> > > > > 
> > > > > "  QOSMs affect the operation of the RMF in NSIS-capable
> > > nodes, the
> > > > >    information carried in QSPEC objects, and may under some
> > > > >    circumstances (e.g. aggregation) cause a separate NSLP 
> > > > >    session to be
> > > > >    instantiated by having the RMF as a QNI. QOSMs all utilize 
> > > > >    the common
> > > > >    data, state machines, and APIs of the underlying NSIS 
> > > > >    protocols and
> > > > >    are not expected to re-define or extend these in any way."
> > > > 
> > > > Georgios:
> > > > Regarding the sentence in Section 4.1:
> > > > "QOSMs all utilize
> > > > the common data, state machines, and APIs of the 
> underlying NSIS 
> > > > protocols and are not expected to re-define or extend
> > these in any
> > > > way."
> > > > 
> > > > This sentence restricts the possibility of QoS model to use
> > > RMF states
> > > > and data that are not been defined in neither QoS-NSLP or QSPEC.
> > > > This sentence should be removed.
> > > 
> > > I disagree.  The quoted text was introduced by Dave Oran 
> in addition 
> > > to removing the phrase implying that a QOSM could specify 
> signaling 
> > > protocol changes, and I agree with this.
> > > Any changes/extensions to the signaling protocol or state 
> machines 
> > > are within the scope of QoS-NSLP draft and not the QSPEC 
> draft or a 
> > > QOSM specification draft.  I think you have noted that 
> also in your 
> > > subsequent posting at 
> > > http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html.
> > > 
> > > If any extensions are required to the NSIS signaling 
> protocol as a 
> > > result of the 'severe change on QoS Model definition and 
> > > capabilities'
> > > you have noted, those proposed changes/extensions should be 
> > > addressed to the QoS NSLP draft IMO.
> > > 
> > > Perhaps Dave can comment here also when he gets a chance.
> > > 
> > > > > > Comment_4:
> > > > > > -------------
> > > > > > Section 5.1 Local QSPEC definition and processing
> > > > > > 
> > > > > > By reading this section it gives the impression 
> that the two 
> > > > > > methods
> > > > > > a) and b) cannot be used by the same QoS model.
> > > > > > Method a): translate the
> > > > > > initiator QSPEC into a local QSPEC and encapsulate the
> > > initiator
> > > > > > QSPEC in the RESERVE message Method b): b) tunnel the
> > initiator
> > > > > > QSPEC through the local domain and reserve resources by
> > > generating
> > > > > > a new RESERVE message through the local domain 
> containing the 
> > > > > > local QSPEC.
> > > > > > 
> > > > > > Note that according to the discussions that we have had
> > > until now
> > > > > > method a) should be able to be used in combination with
> > > method b)
> > > > > > by the same QoS model for the situation that the 
> local QSPEC 
> > > > > > encapsulates the initiator QSPEC in order to satisfy
> > > requirement
> > > > > > 5.4.2 that is specified in RFC 3726, see:
> > > > > > http://www.ietf.org/rfc/rfc3726.txt
> > > > > > 
> > > > > > Please add the following sentence at the end of the first 
> > > > > > paragraph of Section 5.1.
> > > > > > "Note that when method b) is used, the encapsulation of the 
> > > > > > initiator QSPEC into a local QSPEC should also be
> > possible when
> > > > > > the local QoS model needs to satisfy Requirement
> > > > > > 5.4.2 specified in RFC 3726, by adding and removing local 
> > > > > > QOSM-specific Control Information parameters on top of the 
> > > > > > initiator QSPEC."
> > > > > 
> > > > > Your comment here is not clear to me.  It would help to
> > > provide an
> > > > > example to illustrate what you are trying to accomplish.  
> > > It seems
> > > > > that you are trying to specify QoS-NSLP functionality,
> > > rather than
> > > > > QSPEC functionality.  If so, that functionality should be
> > > specified
> > > > > in the QoS-NSLP draft rather than the QSPEC draft, 
> perhaps the 
> > > > > QoS-NSLP authors can comment.
> > > > 
> > > > Georgios:
> > > > No I am not trying to define QOS-NSLP functionality.
> > > > This is related to QSPEC control information that has to be
> > > carried by
> > > > end-to-end messages.
> > > > What I am trying to say is that all the discussion that
> > we have had
> > > > regarding the encapsulation of the QSPEC object were
> > > associated with
> > > > requirement 5.4.2 of RFC 3726, see below:
> > > > 
> > > > -----------------
> > > > "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain 
> > > > Information
> > > > 
> > > >    It SHOULD be possible to add and remove local scope elements.
> > > >    Compared to Requirement 5.3.5 this requirement does use
> > > the normal
> > > >    signaling process and message exchange for transporting local
> > > >    information.  For example, at the entrance to a 
> domain, domain-
> > > >    specific information is added information is added, which 
> > > >    is used in
> > > >    this domain only, and the information is removed again when a
> > > >    signaling message leaves the domain.  The motivation 
> is in the
> > > >    economy of re-using the protocol for domain internal
> > signaling of
> > > >    various information pieces.  Where additional
> > > information is needed
> > > >    within a particular domain, it should be possible to
> > > carry this at
> > > >    the same time as the end-to-end information.", from RFC 3726
> > > > ------------------
> > > > Thus what I am saying is:
> > > > Please add the following sentence at the end of the first
> > > paragraph of
> > > > Section 5.1.
> > > > 
> > > > "Note that when method b) is used, the encapsulation of the
> > > initiator
> > > > QSPEC into a local QSPEC should also be possible when the
> > local QoS
> > > > model needs to satisfy Requirement
> > > > 5.4.2 specified in RFC 3726, by adding and removing local 
> > > > QOSM-specific Control Information parameters on top of the
> > > initiator
> > > > QSPEC."
> > > 
> > > First, the suggested text isn't clear.  If method b) is used
> > > (tunneling) then presumably method a) is not also used at 
> the same 
> > > time.  However, the phrasing of the above makes it sound that way.
> > > 
> > > Second, an example would help here.  I presume you are referring 
> > > e.g., to RMD adding 'control information' (i.e., 'handling 
> > > directive') parameters to the local QSPEC that are not 
> included in 
> > > the initiator QSPEC.  I think the requirement would be 
> that the RMD 
> > > QOSM provides a local QSPEC that is consistent with the initiator 
> > > QSPEC, as we agreed on the list (see also slide 8 of the IETF-67 
> > > presentation).
> > > 
> > > If the local QSPEC introduces functionality inconsistent with the 
> > > initiator QSPEC by appending the handling directive 
> parameters, then 
> > > it is not allowed.
> > > 
> > > > > > Comment_5:
> > > > > > -----------
> > > > > > Section 5.1, last paragraph:
> > > > > > 
> > > > > > Please change the following:
> > > > > > "For example, RMD can define a local QSPEC that
> > contains TMOD =
> > > > > > bandwidth (sets r=p, b/m to large)."
> > > > > > 
> > > > > > Into:
> > > > > > "For example, in RMD the TMOD parameters contained in
> > > the original
> > > > > > initiator QSPEC are mapped into the equivalent TMOD 
> parameter 
> > > > > > representing only the peak bandwidth in the local QSPEC."
> > > > > 
> > > > > OK with me.
> > > > > 
> > > > > > Comment_6:
> > > > > > -------------
> > > > > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to
> > > be followed
> > > > > > regarding the QSPEC control information are not given:
> > > > > > 
> > > > > > Please include the following paragraph at the end of
> > > this section:
> > > > > > "Regarding QSPEC Control Information, the default rule
> > > is that all
> > > > > >    QSPEC parameters that have been included in the RESERVE 
> > > > > >    message by
> > > > > >    the QNI are also included in the RESPONSE message by the 
> > > > > >    QNR with the
> > > > > >    value they had when arriving at the QNR.  When
> > > traveling in the
> > > > > >    RESPONSE message, all QSPEC Control Information
> > > parameters are
> > > > > >    read-only.  Note that a QOSM specification may
> > define its own
> > > > > >    QOSM-specific Control Information parameters and 
> > > > > >    processing rules."
> > > > > 
> > > > > Please see previous email comment on QSPEC control 
> information.
> > > > 
> > > > Georgios: I think that a description of how the QSPEC control 
> > > > information is handled is needed.
> > > 
> > > Please see above comments on 'control information' terminology.
> > > 
> > > Thanks,
> > > Jerry
> > >  
> > > > > > Comment_7:
> > > > > > ------------
> > > > > > Section 6.1:
> > > > > > I do not understand the second sentence from the below two
> > > > > > sentences:
> > > > > > "N Flag: Not-supported QSPEC parameter flag (see
> > Section 5.2.2).
> > > > > >            For QSPEC parameters the value of this flag
> > > is always
> > > > > > zero."
> > > > > 
> > > > > Good catch, this is a typo, the sentence should be removed.
> > > > > 
> > > > 
> > > > 
> > > > Best Regards,
> > > > Georgios
> > > > 
> > > 
> > 
> > 
> > 
> 



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



From nsis-bounces@ietf.org Fri Dec 22 11:37:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxnO3-0002JG-2i; Fri, 22 Dec 2006 11:36:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxnO1-0002JA-Ge
	for nsis@ietf.org; Fri, 22 Dec 2006 11:36:45 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxnO0-0006i7-JU
	for nsis@ietf.org; Fri, 22 Dec 2006 11:36:45 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	kBMGaV78014772; Fri, 22 Dec 2006 17:36:37 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>, <nsis@ietf.org>
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Date: Fri, 22 Dec 2006 17:36:27 +0100
Message-ID: <003c01c725e7$572f9e00$4c0d5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAfQcYAABi6fQAANLmKAAAE4mgA==
In-Reply-To: <003801c725e6$304b8570$4c0d5982@dynamic.ewi.utwente.nl>
X-Spam-Score: 0.4 () FVGT_s_OBFU_Q1,FVGT_u_HAS_2LETTERFLDR
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Fri, 22 Dec 2006 17:36:39 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0d6b5666eba887052ef5e87a9de0d3b8
Cc: 
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

Hi Jerry

The changes that are included in version 13 of the QSEPC 
template draft regarding the QSPEC control information and 
the limitations of the QoS models have never been discussed 
because they were never stated clearly. 

If they would have been stated clearly then I would have sent 
my comments at that time instead of sending them now!

Furthermore, from what I have seen in v. 13 of the draft 
you also have not solved the 
stacking issue, because you are actually dictating that 
encapsulation cannot be combined and used together with 
the tunneling (parallel sessions) method.


Best Regards,
Georgios

> 
>  
> 
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > Sent: vrijdag 22 december 2006 16:37
> > To: Georgios Karagiannis; nsis@ietf.org
> > Cc: Ash, Gerald R (Jerry), ALABS
> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > 
> > Georgios,
> > 
> > > -----Original Message-----
> > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > Sent: Friday, December 22, 2006 9:13 AM
> > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > 
> > > Hi Jerry
> > > 
> > > By just saying that "these changes are suggested by Dave in the 
> > > e-mail" does not work.
> > > 
> > > The proposal of Dave was not clear on the QoS model changes
> > that you
> > > wanted to do.
> > 
> > All changes to the draft have been extensively discussed on 
> the list 
> > and are all contained in the slides presented at IETF-67.  You were 
> > there at
> > IETF-67 and participated in all the list discussion.  The 
> summary of 
> > changes in the slides is quite specific and clear, take 
> another look.
> > Have a look at the minutes as well
> > http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt.  The only 
> > disagreements noted are with regard to stacking, which is an issue 
> > that we later resolved on the list.  Go back and check it out.
> > 
> > > Now I understand which changes you want to include in the QSPEC 
> > > template draft.
> > > This is also the reason of disagreeing with you now and sending 
> > > comments to the nsis list.
> > 
> > I responded to your further comments, see below.  Others are 
> > encouraged to comment as well.
> > 
> > Jerry
> > 
> > > 
> > > Furthermore, note that the QOS-NSLP draft defines which
> > capabilities
> > > should be supported by the QoS models and not the QSPEC template 
> > > draft.
> > > 
> > > Best Regards,
> > > Georgios
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > > > Sent: vrijdag 22 december 2006 15:01
> > > > To: Georgios Karagiannis; nsis@ietf.org
> > > > Cc: Ash, Gerald R (Jerry), ALABS
> > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > > 
> > > > Georgios,
> > > > 
> > > > See below. 
> > > > 
> > > > > -----Original Message-----
> > > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > > > Sent: Thursday, December 21, 2006 9:22 AM
> > > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > > > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
> > > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > > > 
> > > > > Hi Jerry
> > > > > 
> > > > > Please see below! I have severe concerns about some changes
> > > > that have
> > > > > been done in the QSPEC template draft.
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > > > > > Sent: woensdag 20 december 2006 14:20
> > > > > > To: Georgios Karagiannis; nsis@ietf.org
> > > > > > Cc: Ash, Gerald R (Jerry), ALABS
> > > > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > > > > 
> > > > > > Hi Georgios,
> > > > > > 
> > > > > > See below. 
> > > > > > 
> > > > > > > -----Original Message-----
> > > > > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > > > > > Sent: Wednesday, December 20, 2006 5:26 AM
> > > > > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > > > > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
> > > > > > > 
> > > > > > > Hi Jerry
> > > > > > > 
> > > > > > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
> > > > > > > 
> > > > > > > Comment_1:
> > > > > > > --------------
> > > > > > > Please reinclude the concept of QSPEC control
> > > > information that was
> > > > > > > included in all previous versions of the QSPEC
> > template draft.
> > > > > > > In
> > > > > > > 
> > > > > > 
> > > > > 
> > > > 
> > > 
> > 
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
> > > > > > > concept was described in Section 5.1.
> > > > > > 
> > > > > > Please see previous email comment on QSPEC control
> > information.
> > > > > 
> > > > > Georgios: 
> > > > > In order to emphasize the need of having QSPEC control
> > > information
> > > > > parameters  I  would however appreciate if the name of
> > > > Section 4.3.3
> > > > > is changed
> > > > > From:
> > > > > 4.3.3 Traffic Handling Directives
> > > > > INTO:
> > > > > 4.3.3 QSPEC control information
> > > > 
> > > > The updated QSPEC parameter terminology/semantics are as
> > suggested
> > > > by Dave Oran (see slides presented at IETF-67 
> > > > http://www3.ietf.org/proceedings/06nov/index.html).  I 
> think the 
> > > > current terminology is more clear/descriptive of the QSPEC 
> > > > parameters so I don't favor going backwards to less clear 
> > > > terminology.  I was never clear on why we used the 'control 
> > > > information' terminology in the first place, e.g., I 
> don't think 
> > > > it's a very good descriptor of the 'excess treatment' parameter.
> > > > 
> > > > Perhaps Dave can comment on this point also when he 
> gets a chance.
> > > > 
> > > > > > > Comment_2:
> > > > > > > -----------
> > > > > > > 
> > > > > > > Section 6.1:
> > > > > > > Please reintroduce the format that is required in order to
> > > > > > specify the
> > > > > > > QSPEC control information, see:
> > > > > > > Section 7.1 of:
> > > > > > > 
> > > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
> > > > > > 
> > > > > > Please see previous email comment on QSPEC control
> > information.
> > > > > 
> > > > > 
> > > > > Georgios: If you rename section 4.3.3 to QSPEC control
> > > information
> > > > > then I think that reformatting of section 6.1 is not needed.
> > > > > Please add the proposed sentence by Dave (but change the term 
> > > > > "handling directives" to "QSPEC control Information"). I am
> > > > not sure
> > > > > where it is better to add this sentence, maybe in Section 5.4.
> > > > > 
> > > > > "QoSMs are free, subject to IANA registration and review
> > > rules, to
> > > > > extend QSPECs by adding parameters of any of the kinds
> > > supported by
> > > > > the standard QSPEC. This includes traffic description
> > parameters,
> > > > > constraint parameters and QSPEC control information.
> > > QoSMs are not
> > > > > permitted, however, to reinterpret or redefine the
> > standard QSPEC
> > > > > parameters specified in this document"
> > > > 
> > > > Yes, the text suggested by Dave will be added.
> > > > 
> > > > > > > Comment_3:
> > > > > > > ----------
> > > > > > > Section 4.1 :QoS Models
> > > > > > > The definition of the QoS model is not complete. An
> > important
> > > > > > > sentence that was used in the previous version of the
> > > draft is
> > > > > > > removed.
> > > > > > > Please add the following sentence to the definition
> > > of the QoS
> > > > > > > Model
> > > > > > > (QOSM):
> > > > > > > 
> > > > > > > The same as described above have to be applied in
> > > this section.
> > > > > > > After the following sentence:
> > > > > > > 
> > > > > > > "A QOSM specification MAY include the following:"
> > > > > > > 
> > > > > > > include the following bullet:
> > > > > > > "- it specifies how to use QOS NSLP to signal for 
> this QOSM"
> > > > > > 
> > > > > > That sentence was removed in Dave's proposed QOSM
> > > > re-definition, see
> > > > > > 
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
> > > > > > ml.  It was unclear what that sentence meant, QoS-NSLP
> > > > specifies how
> > > > > > to signal, not QOSM specifications, so the sentence
> > was removed.
> > > > > > 
> > > > > > I believe the sentence was intended to mean that when
> > QoS NSLP
> > > > > > allows various options to be selected, a QOSM should
> > be able to
> > > > > > determine which option is used.  For that purpose the
> > following
> > > > > > sentence was added in Section 4.1:
> > > > > > 
> > > > > > "     A QOSM specification MAY include the following:
> > > > > >      ...
> > > > > >      - can state which QoS-NSLP options a QOSM wants to
> > > use, when
> > > > > >      several options are available for a QOSM (e.g.,
> > > > local QSPEC to
> > > > > >      either be a) tunneled or b) encapsulate
> > initiator QSPEC)."
> > > > > > 
> > > > > > Also, to avoid any misinterpretation that QOSMs are free
> > > > to specify
> > > > > > additional constraints, state machines, protocol data,
> > > > etc. for NSLP
> > > > > > beyond that which is specific in the QoS NSLP
> > > specification, the
> > > > > > following was added to Section 4.1:
> > > > > > 
> > > > > > "  QOSMs affect the operation of the RMF in NSIS-capable
> > > > nodes, the
> > > > > >    information carried in QSPEC objects, and may under some
> > > > > >    circumstances (e.g. aggregation) cause a separate NSLP 
> > > > > >    session to be
> > > > > >    instantiated by having the RMF as a QNI. QOSMs 
> all utilize 
> > > > > >    the common
> > > > > >    data, state machines, and APIs of the underlying NSIS 
> > > > > >    protocols and
> > > > > >    are not expected to re-define or extend these in 
> any way."
> > > > > 
> > > > > Georgios:
> > > > > Regarding the sentence in Section 4.1:
> > > > > "QOSMs all utilize
> > > > > the common data, state machines, and APIs of the
> > underlying NSIS
> > > > > protocols and are not expected to re-define or extend
> > > these in any
> > > > > way."
> > > > > 
> > > > > This sentence restricts the possibility of QoS model to use
> > > > RMF states
> > > > > and data that are not been defined in neither 
> QoS-NSLP or QSPEC.
> > > > > This sentence should be removed.
> > > > 
> > > > I disagree.  The quoted text was introduced by Dave Oran
> > in addition
> > > > to removing the phrase implying that a QOSM could specify
> > signaling
> > > > protocol changes, and I agree with this.
> > > > Any changes/extensions to the signaling protocol or state
> > machines
> > > > are within the scope of QoS-NSLP draft and not the QSPEC
> > draft or a
> > > > QOSM specification draft.  I think you have noted that
> > also in your
> > > > subsequent posting at
> > > > 
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html.
> > > > 
> > > > If any extensions are required to the NSIS signaling
> > protocol as a
> > > > result of the 'severe change on QoS Model definition and 
> > > > capabilities'
> > > > you have noted, those proposed changes/extensions should be 
> > > > addressed to the QoS NSLP draft IMO.
> > > > 
> > > > Perhaps Dave can comment here also when he gets a chance.
> > > > 
> > > > > > > Comment_4:
> > > > > > > -------------
> > > > > > > Section 5.1 Local QSPEC definition and processing
> > > > > > > 
> > > > > > > By reading this section it gives the impression
> > that the two
> > > > > > > methods
> > > > > > > a) and b) cannot be used by the same QoS model.
> > > > > > > Method a): translate the
> > > > > > > initiator QSPEC into a local QSPEC and encapsulate the
> > > > initiator
> > > > > > > QSPEC in the RESERVE message Method b): b) tunnel the
> > > initiator
> > > > > > > QSPEC through the local domain and reserve resources by
> > > > generating
> > > > > > > a new RESERVE message through the local domain
> > containing the
> > > > > > > local QSPEC.
> > > > > > > 
> > > > > > > Note that according to the discussions that we have had
> > > > until now
> > > > > > > method a) should be able to be used in combination with
> > > > method b)
> > > > > > > by the same QoS model for the situation that the
> > local QSPEC
> > > > > > > encapsulates the initiator QSPEC in order to satisfy
> > > > requirement
> > > > > > > 5.4.2 that is specified in RFC 3726, see:
> > > > > > > http://www.ietf.org/rfc/rfc3726.txt
> > > > > > > 
> > > > > > > Please add the following sentence at the end of the first 
> > > > > > > paragraph of Section 5.1.
> > > > > > > "Note that when method b) is used, the 
> encapsulation of the 
> > > > > > > initiator QSPEC into a local QSPEC should also be
> > > possible when
> > > > > > > the local QoS model needs to satisfy Requirement
> > > > > > > 5.4.2 specified in RFC 3726, by adding and removing local 
> > > > > > > QOSM-specific Control Information parameters on 
> top of the 
> > > > > > > initiator QSPEC."
> > > > > > 
> > > > > > Your comment here is not clear to me.  It would help to
> > > > provide an
> > > > > > example to illustrate what you are trying to accomplish.  
> > > > It seems
> > > > > > that you are trying to specify QoS-NSLP functionality,
> > > > rather than
> > > > > > QSPEC functionality.  If so, that functionality should be
> > > > specified
> > > > > > in the QoS-NSLP draft rather than the QSPEC draft,
> > perhaps the
> > > > > > QoS-NSLP authors can comment.
> > > > > 
> > > > > Georgios:
> > > > > No I am not trying to define QOS-NSLP functionality.
> > > > > This is related to QSPEC control information that has to be
> > > > carried by
> > > > > end-to-end messages.
> > > > > What I am trying to say is that all the discussion that
> > > we have had
> > > > > regarding the encapsulation of the QSPEC object were
> > > > associated with
> > > > > requirement 5.4.2 of RFC 3726, see below:
> > > > > 
> > > > > -----------------
> > > > > "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain 
> > > > > Information
> > > > > 
> > > > >    It SHOULD be possible to add and remove local 
> scope elements.
> > > > >    Compared to Requirement 5.3.5 this requirement does use
> > > > the normal
> > > > >    signaling process and message exchange for 
> transporting local
> > > > >    information.  For example, at the entrance to a
> > domain, domain-
> > > > >    specific information is added information is added, which 
> > > > >    is used in
> > > > >    this domain only, and the information is removed 
> again when a
> > > > >    signaling message leaves the domain.  The motivation
> > is in the
> > > > >    economy of re-using the protocol for domain internal
> > > signaling of
> > > > >    various information pieces.  Where additional
> > > > information is needed
> > > > >    within a particular domain, it should be possible to
> > > > carry this at
> > > > >    the same time as the end-to-end information.", 
> from RFC 3726
> > > > > ------------------
> > > > > Thus what I am saying is:
> > > > > Please add the following sentence at the end of the first
> > > > paragraph of
> > > > > Section 5.1.
> > > > > 
> > > > > "Note that when method b) is used, the encapsulation of the
> > > > initiator
> > > > > QSPEC into a local QSPEC should also be possible when the
> > > local QoS
> > > > > model needs to satisfy Requirement
> > > > > 5.4.2 specified in RFC 3726, by adding and removing local 
> > > > > QOSM-specific Control Information parameters on top of the
> > > > initiator
> > > > > QSPEC."
> > > > 
> > > > First, the suggested text isn't clear.  If method b) is used
> > > > (tunneling) then presumably method a) is not also used at
> > the same
> > > > time.  However, the phrasing of the above makes it 
> sound that way.
> > > > 
> > > > Second, an example would help here.  I presume you are 
> referring 
> > > > e.g., to RMD adding 'control information' (i.e., 'handling
> > > > directive') parameters to the local QSPEC that are not
> > included in
> > > > the initiator QSPEC.  I think the requirement would be
> > that the RMD
> > > > QOSM provides a local QSPEC that is consistent with the 
> initiator 
> > > > QSPEC, as we agreed on the list (see also slide 8 of 
> the IETF-67 
> > > > presentation).
> > > > 
> > > > If the local QSPEC introduces functionality 
> inconsistent with the 
> > > > initiator QSPEC by appending the handling directive
> > parameters, then
> > > > it is not allowed.
> > > > 
> > > > > > > Comment_5:
> > > > > > > -----------
> > > > > > > Section 5.1, last paragraph:
> > > > > > > 
> > > > > > > Please change the following:
> > > > > > > "For example, RMD can define a local QSPEC that
> > > contains TMOD =
> > > > > > > bandwidth (sets r=p, b/m to large)."
> > > > > > > 
> > > > > > > Into:
> > > > > > > "For example, in RMD the TMOD parameters contained in
> > > > the original
> > > > > > > initiator QSPEC are mapped into the equivalent TMOD
> > parameter
> > > > > > > representing only the peak bandwidth in the local QSPEC."
> > > > > > 
> > > > > > OK with me.
> > > > > > 
> > > > > > > Comment_6:
> > > > > > > -------------
> > > > > > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to
> > > > be followed
> > > > > > > regarding the QSPEC control information are not given:
> > > > > > > 
> > > > > > > Please include the following paragraph at the end of
> > > > this section:
> > > > > > > "Regarding QSPEC Control Information, the default rule
> > > > is that all
> > > > > > >    QSPEC parameters that have been included in 
> the RESERVE 
> > > > > > >    message by
> > > > > > >    the QNI are also included in the RESPONSE 
> message by the 
> > > > > > >    QNR with the
> > > > > > >    value they had when arriving at the QNR.  When
> > > > traveling in the
> > > > > > >    RESPONSE message, all QSPEC Control Information
> > > > parameters are
> > > > > > >    read-only.  Note that a QOSM specification may
> > > define its own
> > > > > > >    QOSM-specific Control Information parameters and 
> > > > > > >    processing rules."
> > > > > > 
> > > > > > Please see previous email comment on QSPEC control
> > information.
> > > > > 
> > > > > Georgios: I think that a description of how the QSPEC control 
> > > > > information is handled is needed.
> > > > 
> > > > Please see above comments on 'control information' terminology.
> > > > 
> > > > Thanks,
> > > > Jerry
> > > >  
> > > > > > > Comment_7:
> > > > > > > ------------
> > > > > > > Section 6.1:
> > > > > > > I do not understand the second sentence from the below two
> > > > > > > sentences:
> > > > > > > "N Flag: Not-supported QSPEC parameter flag (see
> > > Section 5.2.2).
> > > > > > >            For QSPEC parameters the value of this flag
> > > > is always
> > > > > > > zero."
> > > > > > 
> > > > > > Good catch, this is a typo, the sentence should be removed.
> > > > > > 
> > > > > 
> > > > > 
> > > > > Best Regards,
> > > > > Georgios
> > > > > 
> > > > 
> > > 
> > > 
> > > 
> > 
> 
> 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 



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



From nsis-bounces@ietf.org Fri Dec 22 13:12:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gxosg-0000Sx-Sq; Fri, 22 Dec 2006 13:12:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxosf-0000QD-7x
	for nsis@ietf.org; Fri, 22 Dec 2006 13:12:29 -0500
Received: from mail120.messagelabs.com ([216.82.250.83])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gxosa-00049J-Ms
	for nsis@ietf.org; Fri, 22 Dec 2006 13:12:29 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-13.tower-120.messagelabs.com!1166811143!5325061!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 18097 invoked from network); 22 Dec 2006 18:12:23 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-13.tower-120.messagelabs.com with SMTP;
	22 Dec 2006 18:12:23 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id kBMICM1N013326; 
	Fri, 22 Dec 2006 13:12:22 -0500 (EST)
Received: from kcclust06evs1.ugd.att.com (kcst12.ugd.att.com [135.38.164.89])
	by attrh3i.attrh.att.com (8.13.7/8.13.7) with ESMTP id
	kBMICBYB013180; Fri, 22 Dec 2006 13:12:14 -0500 (EST)
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
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Date: Fri, 22 Dec 2006 12:12:11 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC8072@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <003c01c725e7$572f9e00$4c0d5982@dynamic.ewi.utwente.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAfQcYAABi6fQAANLmKAAAE4mgAACINgg
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "Georgios Karagiannis" <karagian@cs.utwente.nl>, <nsis@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8bebc843ecf489bb7d907f63ccb001af
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
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

Georgios,

It's not true as you and 2 others have stated that the changes were not
discussed.  They were discussed, at length.  For example, the revised
definition of QOSM was clearly stated and discussed on the list, see
http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.html and
also see all the list discussion following that post.  The revised
definition and all the other changes were clearly presented in the
slides at IETF-67, see minutes and slides at
http://www3.ietf.org/proceedings/06nov/index.html.  You can listen to
the complete IETF-67 presentation/discussion again at
http://limestone.uoregon.edu/ftp/pub/videolab/media/ietf67/ietf67ch4-thu
-am.mp3. =20

You can review the slides, meeting discussion, list discussion, meeting
minutes, and verify that for yourself.

So the editors did not 'make up the changes without discussion' as you
and 2 others have suggested.  That is certainly wrong and I think you
should acknowledge that.

It is not useful going forward to debate the past, but incendiary wrong
statements should not go unanswered.

Once again, I've responded to your technical comments, you can comment
further if you wish.=20

It would be good for others to comment on the technical points.

Jerry=20

-----Original Message-----
From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]=20
Sent: Friday, December 22, 2006 11:36 AM
To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20

Hi Jerry

The changes that are included in version 13 of the QSEPC=20
template draft regarding the QSPEC control information and=20
the limitations of the QoS models have never been discussed=20
because they were never stated clearly.=20

If they would have been stated clearly then I would have sent=20
my comments at that time instead of sending them now!

Furthermore, from what I have seen in v. 13 of the draft=20
you also have not solved the=20
stacking issue, because you are actually dictating that=20
encapsulation cannot be combined and used together with=20
the tunneling (parallel sessions) method.


Best Regards,
Georgios

>=20
> =20
>=20
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > Sent: vrijdag 22 december 2006 16:37
> > To: Georgios Karagiannis; nsis@ietf.org
> > Cc: Ash, Gerald R (Jerry), ALABS
> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> >=20
> > Georgios,
> >=20
> > > -----Original Message-----
> > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > Sent: Friday, December 22, 2006 9:13 AM
> > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > >=20
> > > Hi Jerry
> > >=20
> > > By just saying that "these changes are suggested by Dave in the=20
> > > e-mail" does not work.
> > >=20
> > > The proposal of Dave was not clear on the QoS model changes
> > that you
> > > wanted to do.
> >=20
> > All changes to the draft have been extensively discussed on=20
> the list=20
> > and are all contained in the slides presented at IETF-67.  You were=20
> > there at
> > IETF-67 and participated in all the list discussion.  The=20
> summary of=20
> > changes in the slides is quite specific and clear, take=20
> another look.
> > Have a look at the minutes as well
> > http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt.  The only=20
> > disagreements noted are with regard to stacking, which is an issue=20
> > that we later resolved on the list.  Go back and check it out.
> >=20
> > > Now I understand which changes you want to include in the QSPEC=20
> > > template draft.
> > > This is also the reason of disagreeing with you now and sending=20
> > > comments to the nsis list.
> >=20
> > I responded to your further comments, see below.  Others are=20
> > encouraged to comment as well.
> >=20
> > Jerry
> >=20
> > >=20
> > > Furthermore, note that the QOS-NSLP draft defines which
> > capabilities
> > > should be supported by the QoS models and not the QSPEC template=20
> > > draft.
> > >=20
> > > Best Regards,
> > > Georgios
> > >=20
> > >=20
> > > > -----Original Message-----
> > > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > > > Sent: vrijdag 22 december 2006 15:01
> > > > To: Georgios Karagiannis; nsis@ietf.org
> > > > Cc: Ash, Gerald R (Jerry), ALABS
> > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > >=20
> > > > Georgios,
> > > >=20
> > > > See below.=20
> > > >=20
> > > > > -----Original Message-----
> > > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > > > Sent: Thursday, December 21, 2006 9:22 AM
> > > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > > > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
> > > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > > >=20
> > > > > Hi Jerry
> > > > >=20
> > > > > Please see below! I have severe concerns about some changes
> > > > that have
> > > > > been done in the QSPEC template draft.
> > > > >=20
> > > > > > -----Original Message-----
> > > > > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > > > > > Sent: woensdag 20 december 2006 14:20
> > > > > > To: Georgios Karagiannis; nsis@ietf.org
> > > > > > Cc: Ash, Gerald R (Jerry), ALABS
> > > > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
> > > > > >=20
> > > > > > Hi Georgios,
> > > > > >=20
> > > > > > See below.=20
> > > > > >=20
> > > > > > > -----Original Message-----
> > > > > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> > > > > > > Sent: Wednesday, December 20, 2006 5:26 AM
> > > > > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
> > > > > > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
> > > > > > >=20
> > > > > > > Hi Jerry
> > > > > > >=20
> > > > > > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
> > > > > > >=20
> > > > > > > Comment_1:
> > > > > > > --------------
> > > > > > > Please reinclude the concept of QSPEC control
> > > > information that was
> > > > > > > included in all previous versions of the QSPEC
> > template draft.
> > > > > > > In
> > > > > > >=20
> > > > > >=20
> > > > >=20
> > > >=20
> > >=20
> >=20
> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
> > > > > > > concept was described in Section 5.1.
> > > > > >=20
> > > > > > Please see previous email comment on QSPEC control
> > information.
> > > > >=20
> > > > > Georgios:=20
> > > > > In order to emphasize the need of having QSPEC control
> > > information
> > > > > parameters  I  would however appreciate if the name of
> > > > Section 4.3.3
> > > > > is changed
> > > > > From:
> > > > > 4.3.3 Traffic Handling Directives
> > > > > INTO:
> > > > > 4.3.3 QSPEC control information
> > > >=20
> > > > The updated QSPEC parameter terminology/semantics are as
> > suggested
> > > > by Dave Oran (see slides presented at IETF-67=20
> > > > http://www3.ietf.org/proceedings/06nov/index.html).  I=20
> think the=20
> > > > current terminology is more clear/descriptive of the QSPEC=20
> > > > parameters so I don't favor going backwards to less clear=20
> > > > terminology.  I was never clear on why we used the 'control=20
> > > > information' terminology in the first place, e.g., I=20
> don't think=20
> > > > it's a very good descriptor of the 'excess treatment' parameter.
> > > >=20
> > > > Perhaps Dave can comment on this point also when he=20
> gets a chance.
> > > >=20
> > > > > > > Comment_2:
> > > > > > > -----------
> > > > > > >=20
> > > > > > > Section 6.1:
> > > > > > > Please reintroduce the format that is required in order to
> > > > > > specify the
> > > > > > > QSPEC control information, see:
> > > > > > > Section 7.1 of:
> > > > > > >=20
> > > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
> > > > > >=20
> > > > > > Please see previous email comment on QSPEC control
> > information.
> > > > >=20
> > > > >=20
> > > > > Georgios: If you rename section 4.3.3 to QSPEC control
> > > information
> > > > > then I think that reformatting of section 6.1 is not needed.
> > > > > Please add the proposed sentence by Dave (but change the term=20
> > > > > "handling directives" to "QSPEC control Information"). I am
> > > > not sure
> > > > > where it is better to add this sentence, maybe in Section 5.4.
> > > > >=20
> > > > > "QoSMs are free, subject to IANA registration and review
> > > rules, to
> > > > > extend QSPECs by adding parameters of any of the kinds
> > > supported by
> > > > > the standard QSPEC. This includes traffic description
> > parameters,
> > > > > constraint parameters and QSPEC control information.
> > > QoSMs are not
> > > > > permitted, however, to reinterpret or redefine the
> > standard QSPEC
> > > > > parameters specified in this document"
> > > >=20
> > > > Yes, the text suggested by Dave will be added.
> > > >=20
> > > > > > > Comment_3:
> > > > > > > ----------
> > > > > > > Section 4.1 :QoS Models
> > > > > > > The definition of the QoS model is not complete. An
> > important
> > > > > > > sentence that was used in the previous version of the
> > > draft is
> > > > > > > removed.
> > > > > > > Please add the following sentence to the definition
> > > of the QoS
> > > > > > > Model
> > > > > > > (QOSM):
> > > > > > >=20
> > > > > > > The same as described above have to be applied in
> > > this section.
> > > > > > > After the following sentence:
> > > > > > >=20
> > > > > > > "A QOSM specification MAY include the following:"
> > > > > > >=20
> > > > > > > include the following bullet:
> > > > > > > "- it specifies how to use QOS NSLP to signal for=20
> this QOSM"
> > > > > >=20
> > > > > > That sentence was removed in Dave's proposed QOSM
> > > > re-definition, see
> > > > > >=20
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
> > > > > > ml.  It was unclear what that sentence meant, QoS-NSLP
> > > > specifies how
> > > > > > to signal, not QOSM specifications, so the sentence
> > was removed.
> > > > > >=20
> > > > > > I believe the sentence was intended to mean that when
> > QoS NSLP
> > > > > > allows various options to be selected, a QOSM should
> > be able to
> > > > > > determine which option is used.  For that purpose the
> > following
> > > > > > sentence was added in Section 4.1:
> > > > > >=20
> > > > > > "     A QOSM specification MAY include the following:
> > > > > >      ...
> > > > > >      - can state which QoS-NSLP options a QOSM wants to
> > > use, when
> > > > > >      several options are available for a QOSM (e.g.,
> > > > local QSPEC to
> > > > > >      either be a) tunneled or b) encapsulate
> > initiator QSPEC)."
> > > > > >=20
> > > > > > Also, to avoid any misinterpretation that QOSMs are free
> > > > to specify
> > > > > > additional constraints, state machines, protocol data,
> > > > etc. for NSLP
> > > > > > beyond that which is specific in the QoS NSLP
> > > specification, the
> > > > > > following was added to Section 4.1:
> > > > > >=20
> > > > > > "  QOSMs affect the operation of the RMF in NSIS-capable
> > > > nodes, the
> > > > > >    information carried in QSPEC objects, and may under some
> > > > > >    circumstances (e.g. aggregation) cause a separate NSLP=20
> > > > > >    session to be
> > > > > >    instantiated by having the RMF as a QNI. QOSMs=20
> all utilize=20
> > > > > >    the common
> > > > > >    data, state machines, and APIs of the underlying NSIS=20
> > > > > >    protocols and
> > > > > >    are not expected to re-define or extend these in=20
> any way."
> > > > >=20
> > > > > Georgios:
> > > > > Regarding the sentence in Section 4.1:
> > > > > "QOSMs all utilize
> > > > > the common data, state machines, and APIs of the
> > underlying NSIS
> > > > > protocols and are not expected to re-define or extend
> > > these in any
> > > > > way."
> > > > >=20
> > > > > This sentence restricts the possibility of QoS model to use
> > > > RMF states
> > > > > and data that are not been defined in neither=20
> QoS-NSLP or QSPEC.
> > > > > This sentence should be removed.
> > > >=20
> > > > I disagree.  The quoted text was introduced by Dave Oran
> > in addition
> > > > to removing the phrase implying that a QOSM could specify
> > signaling
> > > > protocol changes, and I agree with this.
> > > > Any changes/extensions to the signaling protocol or state
> > machines
> > > > are within the scope of QoS-NSLP draft and not the QSPEC
> > draft or a
> > > > QOSM specification draft.  I think you have noted that
> > also in your
> > > > subsequent posting at
> > > >=20
> http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html.
> > > >=20
> > > > If any extensions are required to the NSIS signaling
> > protocol as a
> > > > result of the 'severe change on QoS Model definition and=20
> > > > capabilities'
> > > > you have noted, those proposed changes/extensions should be=20
> > > > addressed to the QoS NSLP draft IMO.
> > > >=20
> > > > Perhaps Dave can comment here also when he gets a chance.
> > > >=20
> > > > > > > Comment_4:
> > > > > > > -------------
> > > > > > > Section 5.1 Local QSPEC definition and processing
> > > > > > >=20
> > > > > > > By reading this section it gives the impression
> > that the two
> > > > > > > methods
> > > > > > > a) and b) cannot be used by the same QoS model.
> > > > > > > Method a): translate the
> > > > > > > initiator QSPEC into a local QSPEC and encapsulate the
> > > > initiator
> > > > > > > QSPEC in the RESERVE message Method b): b) tunnel the
> > > initiator
> > > > > > > QSPEC through the local domain and reserve resources by
> > > > generating
> > > > > > > a new RESERVE message through the local domain
> > containing the
> > > > > > > local QSPEC.
> > > > > > >=20
> > > > > > > Note that according to the discussions that we have had
> > > > until now
> > > > > > > method a) should be able to be used in combination with
> > > > method b)
> > > > > > > by the same QoS model for the situation that the
> > local QSPEC
> > > > > > > encapsulates the initiator QSPEC in order to satisfy
> > > > requirement
> > > > > > > 5.4.2 that is specified in RFC 3726, see:
> > > > > > > http://www.ietf.org/rfc/rfc3726.txt
> > > > > > >=20
> > > > > > > Please add the following sentence at the end of the first=20
> > > > > > > paragraph of Section 5.1.
> > > > > > > "Note that when method b) is used, the=20
> encapsulation of the=20
> > > > > > > initiator QSPEC into a local QSPEC should also be
> > > possible when
> > > > > > > the local QoS model needs to satisfy Requirement
> > > > > > > 5.4.2 specified in RFC 3726, by adding and removing local=20
> > > > > > > QOSM-specific Control Information parameters on=20
> top of the=20
> > > > > > > initiator QSPEC."
> > > > > >=20
> > > > > > Your comment here is not clear to me.  It would help to
> > > > provide an
> > > > > > example to illustrate what you are trying to accomplish. =20
> > > > It seems
> > > > > > that you are trying to specify QoS-NSLP functionality,
> > > > rather than
> > > > > > QSPEC functionality.  If so, that functionality should be
> > > > specified
> > > > > > in the QoS-NSLP draft rather than the QSPEC draft,
> > perhaps the
> > > > > > QoS-NSLP authors can comment.
> > > > >=20
> > > > > Georgios:
> > > > > No I am not trying to define QOS-NSLP functionality.
> > > > > This is related to QSPEC control information that has to be
> > > > carried by
> > > > > end-to-end messages.
> > > > > What I am trying to say is that all the discussion that
> > > we have had
> > > > > regarding the encapsulation of the QSPEC object were
> > > > associated with
> > > > > requirement 5.4.2 of RFC 3726, see below:
> > > > >=20
> > > > > -----------------
> > > > > "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain=20
> > > > > Information
> > > > >=20
> > > > >    It SHOULD be possible to add and remove local=20
> scope elements.
> > > > >    Compared to Requirement 5.3.5 this requirement does use
> > > > the normal
> > > > >    signaling process and message exchange for=20
> transporting local
> > > > >    information.  For example, at the entrance to a
> > domain, domain-
> > > > >    specific information is added information is added, which=20
> > > > >    is used in
> > > > >    this domain only, and the information is removed=20
> again when a
> > > > >    signaling message leaves the domain.  The motivation
> > is in the
> > > > >    economy of re-using the protocol for domain internal
> > > signaling of
> > > > >    various information pieces.  Where additional
> > > > information is needed
> > > > >    within a particular domain, it should be possible to
> > > > carry this at
> > > > >    the same time as the end-to-end information.",=20
> from RFC 3726
> > > > > ------------------
> > > > > Thus what I am saying is:
> > > > > Please add the following sentence at the end of the first
> > > > paragraph of
> > > > > Section 5.1.
> > > > >=20
> > > > > "Note that when method b) is used, the encapsulation of the
> > > > initiator
> > > > > QSPEC into a local QSPEC should also be possible when the
> > > local QoS
> > > > > model needs to satisfy Requirement
> > > > > 5.4.2 specified in RFC 3726, by adding and removing local=20
> > > > > QOSM-specific Control Information parameters on top of the
> > > > initiator
> > > > > QSPEC."
> > > >=20
> > > > First, the suggested text isn't clear.  If method b) is used
> > > > (tunneling) then presumably method a) is not also used at
> > the same
> > > > time.  However, the phrasing of the above makes it=20
> sound that way.
> > > >=20
> > > > Second, an example would help here.  I presume you are=20
> referring=20
> > > > e.g., to RMD adding 'control information' (i.e., 'handling
> > > > directive') parameters to the local QSPEC that are not
> > included in
> > > > the initiator QSPEC.  I think the requirement would be
> > that the RMD
> > > > QOSM provides a local QSPEC that is consistent with the=20
> initiator=20
> > > > QSPEC, as we agreed on the list (see also slide 8 of=20
> the IETF-67=20
> > > > presentation).
> > > >=20
> > > > If the local QSPEC introduces functionality=20
> inconsistent with the=20
> > > > initiator QSPEC by appending the handling directive
> > parameters, then
> > > > it is not allowed.
> > > >=20
> > > > > > > Comment_5:
> > > > > > > -----------
> > > > > > > Section 5.1, last paragraph:
> > > > > > >=20
> > > > > > > Please change the following:
> > > > > > > "For example, RMD can define a local QSPEC that
> > > contains TMOD =3D
> > > > > > > bandwidth (sets r=3Dp, b/m to large)."
> > > > > > >=20
> > > > > > > Into:
> > > > > > > "For example, in RMD the TMOD parameters contained in
> > > > the original
> > > > > > > initiator QSPEC are mapped into the equivalent TMOD
> > parameter
> > > > > > > representing only the peak bandwidth in the local QSPEC."
> > > > > >=20
> > > > > > OK with me.
> > > > > >=20
> > > > > > > Comment_6:
> > > > > > > -------------
> > > > > > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to
> > > > be followed
> > > > > > > regarding the QSPEC control information are not given:
> > > > > > >=20
> > > > > > > Please include the following paragraph at the end of
> > > > this section:
> > > > > > > "Regarding QSPEC Control Information, the default rule
> > > > is that all
> > > > > > >    QSPEC parameters that have been included in=20
> the RESERVE=20
> > > > > > >    message by
> > > > > > >    the QNI are also included in the RESPONSE=20
> message by the=20
> > > > > > >    QNR with the
> > > > > > >    value they had when arriving at the QNR.  When
> > > > traveling in the
> > > > > > >    RESPONSE message, all QSPEC Control Information
> > > > parameters are
> > > > > > >    read-only.  Note that a QOSM specification may
> > > define its own
> > > > > > >    QOSM-specific Control Information parameters and=20
> > > > > > >    processing rules."
> > > > > >=20
> > > > > > Please see previous email comment on QSPEC control
> > information.
> > > > >=20
> > > > > Georgios: I think that a description of how the QSPEC control=20
> > > > > information is handled is needed.
> > > >=20
> > > > Please see above comments on 'control information' terminology.
> > > >=20
> > > > Thanks,
> > > > Jerry
> > > > =20
> > > > > > > Comment_7:
> > > > > > > ------------
> > > > > > > Section 6.1:
> > > > > > > I do not understand the second sentence from the below two
> > > > > > > sentences:
> > > > > > > "N Flag: Not-supported QSPEC parameter flag (see
> > > Section 5.2.2).
> > > > > > >            For QSPEC parameters the value of this flag
> > > > is always
> > > > > > > zero."
> > > > > >=20
> > > > > > Good catch, this is a typo, the sentence should be removed.
> > > > > >=20
> > > > >=20
> > > > >=20
> > > > > Best Regards,
> > > > > Georgios
> > > > >=20
> > > >=20
> > >=20
> > >=20
> > >=20
> >=20
>=20
>=20
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
>=20



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



From nsis-bounces@ietf.org Sat Dec 23 12:28:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GyAf3-0001hg-Oy; Sat, 23 Dec 2006 12:27:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GyAf2-0001hb-3P
	for nsis@ietf.org; Sat, 23 Dec 2006 12:27:52 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GyAf1-0007tz-96
	for nsis@ietf.org; Sat, 23 Dec 2006 12:27:52 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kBNHQi8D023511; Sat, 23 Dec 2006 19:26:45 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Dec 2006 19:27:06 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Dec 2006 19:27:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 23 Dec 2006 19:27:00 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC019F091C@esebe199.NOE.Nokia.com>
In-Reply-To: <62D92A9A02BCC845B202323D49A48426E1CF73@0591-ITS-EXMP02.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: warning (was:: Comments on draft-ietf-nsis-qspec-13.txt )
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAfQcYAABi6fQAAHO094ANbr/0A==
From: <john.loughney@nokia.com>
To: <RADHIKA.R.ROY@saic.com>, <nsis@ietf.org>
X-OriginalArrivalTime: 23 Dec 2006 17:27:06.0290 (UTC)
	FILETIME=[915B5120:01C726B7]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061223192645-5B3EFBB0-63E0F0B5/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f5932bfc8385127f631fc458a872feb1
Cc: lars.eggert@gmail.com
Subject: [NSIS] warning (was:: Comments on draft-ietf-nsis-qspec-13.txt )
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>
Content-Type: multipart/mixed; boundary="===============0475221940=="
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0475221940==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C726B7.91981F2B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C726B7.91981F2B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Rahdhika,
=20
I have tried to politely ask you to restrain from content-free posting.
You are not the working group chair, so you are not in a position to
declare working group concensus.  Additionally, it is clearly within our
charter to work with QoS defined by other SDOs.
=20
If you continue in your inappropriate postings, I will be forced to
consider revoking your posting rights.
=20
John


________________________________

	From: ext Roy, Radhika R. [mailto:RADHIKA.R.ROY@saic.com]=20
	Sent: 22 December, 2006 17:48
	To: Ash, Gerald R (Jerry), ALABS; Georgios Karagiannis;
nsis@ietf.org
	Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt

=09
=09
	All those changes do not reflect the work group discussions as
some of them Georgios mentioned.
	=20
	It does not have to the way you so-called co-editors think so.
If the WG agrees with the changes that you have made in the draft, then
why do these WG people disagree with you?
	=20
	Do you have technical explanations to answer Georgeo's points?
	=20
	If not, it is the time to leave this draft to a NEW editor who
work based on WG technical consensus. Or, submit as individual non-WG
draft. It is so simple.
	=20
	Best regards,
	Radhika

________________________________

	From: nsis-bounces@ietf.org on behalf of Ash, Gerald R (Jerry),
ALABS
	Sent: Fri 12/22/2006 10:36 AM
	To: Georgios Karagiannis; nsis@ietf.org
	Cc: Ash, Gerald R (Jerry), ALABS
	Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20
=09
=09

	Georgios,
=09
	> -----Original Message-----
	> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
	> Sent: Friday, December 22, 2006 9:13 AM
	> To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
	> Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
	>
	> Hi Jerry
	>
	> By just saying that "these changes are suggested by Dave in
	> the e-mail" does not work.
	>
	> The proposal of Dave was not clear on the QoS model changes
that
	> you wanted to do.
=09
	All changes to the draft have been extensively discussed on the
list and
	are all contained in the slides presented at IETF-67.  You were
there at
	IETF-67 and participated in all the list discussion.  The
summary of
	changes in the slides is quite specific and clear, take another
look.
	Have a look at the minutes as well
	http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt.  The
only
	disagreements noted are with regard to stacking, which is an
issue that
	we later resolved on the list.  Go back and check it out.
=09
	> Now I understand which changes you want to include in the
	> QSPEC template draft.
	> This is also the reason of disagreeing with you now and
	> sending comments to the nsis list.
=09
	I responded to your further comments, see below.  Others are
encouraged
	to comment as well.
=09
	Jerry
=09
	>
	> Furthermore, note that the QOS-NSLP draft defines which
capabilities
	> should be supported by the QoS models and not the
	> QSPEC template draft.
	>
	> Best Regards,
	> Georgios
	>
	>
	> > -----Original Message-----
	> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
	> > Sent: vrijdag 22 december 2006 15:01
	> > To: Georgios Karagiannis; nsis@ietf.org
	> > Cc: Ash, Gerald R (Jerry), ALABS
	> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
	> >
	> > Georgios,
	> >
	> > See below.
	> >
	> > > -----Original Message-----
	> > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
	> > > Sent: Thursday, December 21, 2006 9:22 AM
	> > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
	> > > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
	> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
	> > >
	> > > Hi Jerry
	> > >
	> > > Please see below! I have severe concerns about some
changes
	> > that have
	> > > been done in the QSPEC template draft.
	> > >
	>


------_=_NextPart_001_01C726B7.91981F2B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML=20
dir=3Dltr><HEAD><TITLE>[NSIS] RE: Comments on =
draft-ietf-nsis-qspec-13.txt</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D391431917-23122006>Rahdhika,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D391431917-23122006></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D391431917-23122006>I have tried to politely ask you to restrain =
from=20
content-free posting.&nbsp; You are not the working group chair, so you =
are not=20
in a position to declare working group concensus.&nbsp; Additionally, it =
is=20
clearly within our charter to work with QoS defined by other=20
SDOs.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D391431917-23122006></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D391431917-23122006>If you continue in your inappropriate =
postings, I will=20
be forced to consider revoking your posting rights.</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><SPAN class=3D391431917-23122006></SPAN><FONT face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>J<SPAN=20
class=3D391431917-23122006>ohn</SPAN></FONT></FONT></FONT><BR></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ext Roy, Radhika R.=20
  [mailto:RADHIKA.R.ROY@saic.com] <BR><B>Sent:</B> 22 December, 2006=20
  17:48<BR><B>To:</B> Ash, Gerald R (Jerry), ALABS; Georgios =
Karagiannis;=20
  nsis@ietf.org<BR><B>Subject:</B> RE: [NSIS] RE: Comments on=20
  draft-ietf-nsis-qspec-13.txt <BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV id=3DidOWAReplyText222 dir=3Dltr>
  <DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>All those =
changes do not=20
  reflect the work group discussions as some of them Georgios=20
  mentioned.</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>It does not have to the way =
you so-called=20
  co-editors think so. If the WG agrees with the changes that you have =
made in=20
  the draft, then why do these WG people disagree with you?</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>Do you have technical =
explanations to=20
  answer Georgeo's points?</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>If not, it is the time to =
leave this=20
  draft to&nbsp;a NEW editor who work based on WG technical consensus. =
Or,=20
  submit as individual non-WG draft. It is so simple.</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>Best regards,</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>Radhika</FONT></DIV></DIV>
  <DIV dir=3Dltr><BR>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> nsis-bounces@ietf.org on =
behalf of Ash,=20
  Gerald R (Jerry), ALABS<BR><B>Sent:</B> Fri 12/22/2006 10:36 =
AM<BR><B>To:</B>=20
  Georgios Karagiannis; nsis@ietf.org<BR><B>Cc:</B> Ash, Gerald R =
(Jerry),=20
  ALABS<BR><B>Subject:</B> [NSIS] RE: Comments on =
draft-ietf-nsis-qspec-13.txt=20
  <BR></FONT><BR></DIV>
  <DIV>
  <P><FONT size=3D2>Georgios,<BR><BR>&gt; -----Original =
Message-----<BR>&gt; From:=20
  Georgios Karagiannis [<A=20
  =
href=3D"mailto:karagian@cs.utwente.nl">mailto:karagian@cs.utwente.nl</A>]=
<BR>&gt;=20
  Sent: Friday, December 22, 2006 9:13 AM<BR>&gt; To: Ash, Gerald R =
(Jerry),=20
  ALABS; nsis@ietf.org<BR>&gt; Subject: RE: Comments on=20
  draft-ietf-nsis-qspec-13.txt<BR>&gt;<BR>&gt; Hi Jerry<BR>&gt;<BR>&gt; =
By just=20
  saying that "these changes are suggested by Dave in<BR>&gt; the =
e-mail" does=20
  not work.<BR>&gt;<BR>&gt; The proposal of Dave was not clear on the =
QoS model=20
  changes that<BR>&gt; you wanted to do.<BR><BR>All changes to the draft =
have=20
  been extensively discussed on the list and<BR>are all contained in the =
slides=20
  presented at IETF-67.&nbsp; You were there at<BR>IETF-67 and =
participated in=20
  all the list discussion.&nbsp; The summary of<BR>changes in the slides =
is=20
  quite specific and clear, take another look.<BR>Have a look at the =
minutes as=20
  well<BR><A=20
  =
href=3D"http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt">http://w=
ww3.ietf.org/proceedings/06nov/minutes/nsis.txt</A>.&nbsp;=20
  The only<BR>disagreements noted are with regard to stacking, which is =
an issue=20
  that<BR>we later resolved on the list.&nbsp; Go back and check it=20
  out.<BR><BR>&gt; Now I understand which changes you want to include in =

  the<BR>&gt; QSPEC template draft.<BR>&gt; This is also the reason of=20
  disagreeing with you now and<BR>&gt; sending comments to the nsis=20
  list.<BR><BR>I responded to your further comments, see below.&nbsp; =
Others are=20
  encouraged<BR>to comment as well.<BR><BR>Jerry<BR><BR>&gt;<BR>&gt;=20
  Furthermore, note that the QOS-NSLP draft defines which =
capabilities<BR>&gt;=20
  should be supported by the QoS models and not the<BR>&gt; QSPEC =
template=20
  draft.<BR>&gt;<BR>&gt; Best Regards,<BR>&gt; =
Georgios<BR>&gt;<BR>&gt;<BR>&gt;=20
  &gt; -----Original Message-----<BR>&gt; &gt; From: Ash, Gerald R =
(Jerry),=20
  ALABS [<A =
href=3D"mailto:gash@att.com">mailto:gash@att.com</A>]<BR>&gt; &gt;=20
  Sent: vrijdag 22 december 2006 15:01<BR>&gt; &gt; To: Georgios =
Karagiannis;=20
  nsis@ietf.org<BR>&gt; &gt; Cc: Ash, Gerald R (Jerry), ALABS<BR>&gt; =
&gt;=20
  Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt<BR>&gt; =
&gt;<BR>&gt;=20
  &gt; Georgios,<BR>&gt; &gt;<BR>&gt; &gt; See below.<BR>&gt; =
&gt;<BR>&gt; &gt;=20
  &gt; -----Original Message-----<BR>&gt; &gt; &gt; From: Georgios =
Karagiannis=20
  [<A=20
  =
href=3D"mailto:karagian@cs.utwente.nl">mailto:karagian@cs.utwente.nl</A>]=
<BR>&gt;=20
  &gt; &gt; Sent: Thursday, December 21, 2006 9:22 AM<BR>&gt; &gt; &gt; =
To: Ash,=20
  Gerald R (Jerry), ALABS; nsis@ietf.org<BR>&gt; &gt; &gt; Cc: 'Attila =
Bader=20
  (IJ/ETH)'; 'Lars Westberg'<BR>&gt; &gt; &gt; Subject: RE: Comments on=20
  draft-ietf-nsis-qspec-13.txt<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; Hi=20
  Jerry<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; Please see below! I have =
severe=20
  concerns about some changes<BR>&gt; &gt; that have<BR>&gt; &gt; &gt; =
been done=20
  in the QSPEC template draft.<BR>&gt; &gt;=20
&gt;<BR>&gt;</FONT></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C726B7.91981F2B--


--===============0475221940==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0475221940==--




From nsis-bounces@ietf.org Sat Dec 23 12:39:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GyAph-0005QH-OQ; Sat, 23 Dec 2006 12:38:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GyApf-0005Q6-W5
	for nsis@ietf.org; Sat, 23 Dec 2006 12:38:51 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GyApb-0001Np-Ny
	for nsis@ietf.org; Sat, 23 Dec 2006 12:38:51 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kBNHbTAg026029; Sat, 23 Dec 2006 19:37:39 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Dec 2006 19:38:33 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Dec 2006 19:38:31 +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
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Date: Sat, 23 Dec 2006 19:36:05 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC019F0920@esebe199.NOE.Nokia.com>
In-Reply-To: <003401c725d8$06315b10$4c0d5982@dynamic.ewi.utwente.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAiO6wAABHXYgADg6H8A=
From: <john.loughney@nokia.com>
To: <karagian@cs.utwente.nl>, <lars.westberg@ericsson.com>, <gash@att.com>,
	<nsis@ietf.org>
X-OriginalArrivalTime: 23 Dec 2006 17:38:31.0971 (UTC)
	FILETIME=[2A0DEF30:01C726B9]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061223193739-64C03BB0-00DE69CD/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 680445c3afe8c9e96925f2dfef141924
Cc: 
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

Georgios and Lars,

As has been discussed earlier, the IESG does not approve of unlimited
extensibility and flexibility in protocols.  This type of thing actually
harms interoperability more than helps.  If we want flexibility in the
protocols, we need to be able to bound that extensibility & have some
explanations of the trade-offs.  My understanding of the current draft
text is that the editors were trying to clarify some ambiguity in
the draft.

I don't think it is good to have ambiguity in the document, so we need
to have some clarification of the text. If you are unhappy with
the current text, please submit new text. If you wish to support
more extensibility, then we need to have some text in the document
that explains the trade-offs.

thanks,
John

>-----Original Message-----
>From: ext Georgios Karagiannis [mailto:karagian@cs.utwente.nl]=20
>Sent: 22 December, 2006 16:47
>To: 'Lars Westberg (KI/EAB)'; 'Ash, Gerald R (Jerry), ALABS';=20
>nsis@ietf.org
>Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20
>
>Hi Lars
>
>I agree with you! Furthermore, by limiting the capabilities of=20
>the QOS models also the modularity and flexibility=20
>characteristrics and advanteges of NSIS are limited.
>
>Best regards,
>Georgios
>
>> -----Original Message-----
>> From: Lars Westberg (KI/EAB) [mailto:lars.westberg@ericsson.com]
>> Sent: vrijdag 22 december 2006 15:31
>> To: Ash, Gerald R (Jerry), ALABS; Georgios Karagiannis; nsis@ietf.org
>> Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt
>>=20
>> Let's discuss it once more regarding the control information in the=20
>> QoS-model,.
>>=20
>> The basic purpose with the QOS-model is to have modularity and=20
>> extendabillity for future needs. We have discussed into the protocol=20
>> design and I am very suprised that it suddently disappear from the=20
>> draft.
>>=20
>> We have one very good example: RSVP-proxy.
>>=20
>> If one wan't to have NSIS-proxies,=20
>> 	we need to control information such as: Proxy is found!!=20
>> 							    Proxy is
>> located at this address!
>>=20
>> This could very well be described by QoS-model control information!!!
>>=20
>> The basic problem is that this drafts tries to limit the=20
>> extendabillity to exactly the same as RSVP!!! I completely disagree=20
>> with that approach.
>>=20
>> There are no need to re-design RSVP with exactly the same=20
>> functionality!! We already have RSVP but RSVP is better=20
>designed from=20
>> scalabillity perspective and have support for Mutlicast support. We=20
>> are designing exactly the same protocol but with limited functional=20
>> support and without Multicast!!!!!
>> Note, that we can't use NSIS for TV-broadcast !!!=20
>>=20
>> I do not beleive that NSIS can replace RSVP!!!=20
>> Therefore, QOS-NSLP must support other usage than RSVP!!!
>>=20
>> I agree that the description of control information may be explained=20
>> better but it has to be possible to have control information in the=20
>> QoS-model.
>>=20
>> But the statement into this draft makes the QoS-NSLP useless!!
>>=20
>>=20
>> Regards Lasse
>>=20
>>=20
>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>> Sent: den 22 december 2006 15:01
>> To: Georgios Karagiannis; nsis@ietf.org
>> Cc: Ash, Gerald R (Jerry), ALABS
>> Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt
>>=20
>> Georgios,
>>=20
>> See below.=20
>>=20
>> > -----Original Message-----
>> > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>> > Sent: Thursday, December 21, 2006 9:22 AM
>> > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>> > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
>> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>> >=20
>> > Hi Jerry
>> >=20
>> > Please see below! I have severe concerns about some changes
>> that have
>> > been done in the QSPEC template draft.
>> >=20
>> > > -----Original Message-----
>> > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>> > > Sent: woensdag 20 december 2006 14:20
>> > > To: Georgios Karagiannis; nsis@ietf.org
>> > > Cc: Ash, Gerald R (Jerry), ALABS
>> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>> > >=20
>> > > Hi Georgios,
>> > >=20
>> > > See below.=20
>> > >=20
>> > > > -----Original Message-----
>> > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>> > > > Sent: Wednesday, December 20, 2006 5:26 AM
>> > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>> > > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
>> > > >=20
>> > > > Hi Jerry
>> > > >=20
>> > > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
>> > > >=20
>> > > > Comment_1:
>> > > > --------------
>> > > > Please reinclude the concept of QSPEC control
>> information that was
>>=20
>> > > > included in all previous versions of the QSPEC template draft.
>> > > > In
>> > > >=20
>> > >=20
>> >=20
>> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
>> > > > concept was described in Section 5.1.
>> > >=20
>> > > Please see previous email comment on QSPEC control information.
>> >=20
>> > Georgios:=20
>> > In order to emphasize the need of having QSPEC control information=20
>> > parameters  I  would however appreciate if the name of
>> Section 4.3.3
>> > is changed
>> > From:
>> > 4.3.3 Traffic Handling Directives
>> > INTO:
>> > 4.3.3 QSPEC control information
>>=20
>> The updated QSPEC parameter terminology/semantics are as=20
>suggested by=20
>> Dave Oran (see slides presented at IETF-67=20
>> http://www3.ietf.org/proceedings/06nov/index.html).  I think the=20
>> current terminology is more clear/descriptive of the QSPEC=20
>parameters=20
>> so I don't favor going backwards to less clear terminology.  I was=20
>> never clear on why we used the 'control information' terminology in=20
>> the first place, e.g., I don't think it's a very good descriptor of=20
>> the 'excess treatment' parameter.
>>=20
>> Perhaps Dave can comment on this point also when he gets a chance.
>>=20
>> > > > Comment_2:
>> > > > -----------
>> > > >=20
>> > > > Section 6.1:
>> > > > Please reintroduce the format that is required in order to
>> > > specify the
>> > > > QSPEC control information, see:
>> > > > Section 7.1 of:
>> > > > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
>> > >=20
>> > > Please see previous email comment on QSPEC control information.
>> >=20
>> >=20
>> > Georgios: If you rename section 4.3.3 to QSPEC control information=20
>> > then I think that reformatting of section 6.1 is not needed.
>> > Please add the proposed sentence by Dave (but change the term=20
>> > "handling directives" to "QSPEC control Information"). I am
>> not sure
>> > where it is better to add this sentence, maybe in Section 5.4.
>> >=20
>> > "QoSMs are free, subject to IANA registration and review rules, to=20
>> > extend QSPECs by adding parameters of any of the kinds=20
>supported by=20
>> > the standard QSPEC. This includes traffic description parameters,=20
>> > constraint parameters and QSPEC control information. QoSMs are not=20
>> > permitted, however, to reinterpret or redefine the standard QSPEC=20
>> > parameters specified in this document"
>>=20
>> Yes, the text suggested by Dave will be added.
>>=20
>> > > > Comment_3:
>> > > > ----------
>> > > > Section 4.1 :QoS Models
>> > > > The definition of the QoS model is not complete. An important=20
>> > > > sentence that was used in the previous version of the draft is=20
>> > > > removed.
>> > > > Please add the following sentence to the definition of the QoS=20
>> > > > Model
>> > > > (QOSM):
>> > > >=20
>> > > > The same as described above have to be applied in this section.
>> > > > After the following sentence:
>> > > >=20
>> > > > "A QOSM specification MAY include the following:"
>> > > >=20
>> > > > include the following bullet:
>> > > > "- it specifies how to use QOS NSLP to signal for this QOSM"
>> > >=20
>> > > That sentence was removed in Dave's proposed QOSM
>> re-definition, see
>>=20
>> > > http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
>> > > ml.  It was unclear what that sentence meant, QoS-NSLP
>> specifies how
>>=20
>> > > to signal, not QOSM specifications, so the sentence was removed.
>> > >=20
>> > > I believe the sentence was intended to mean that when QoS NSLP=20
>> > > allows various options to be selected, a QOSM should be able to=20
>> > > determine which option is used.  For that purpose the following=20
>> > > sentence was added in Section 4.1:
>> > >=20
>> > > "     A QOSM specification MAY include the following:
>> > >      ...
>> > >      - can state which QoS-NSLP options a QOSM wants to use, when
>> > >      several options are available for a QOSM (e.g.,
>> local QSPEC to
>> > >      either be a) tunneled or b) encapsulate initiator QSPEC)."
>> > >=20
>> > > Also, to avoid any misinterpretation that QOSMs are free
>> to specify
>> > > additional constraints, state machines, protocol data,
>> etc. for NSLP
>>=20
>> > > beyond that which is specific in the QoS NSLP specification, the=20
>> > > following was added to Section 4.1:
>> > >=20
>> > > "  QOSMs affect the operation of the RMF in NSIS-capable
>> nodes, the
>> > >    information carried in QSPEC objects, and may under some
>> > >    circumstances (e.g. aggregation) cause a separate NSLP=20
>> > >    session to be
>> > >    instantiated by having the RMF as a QNI. QOSMs all utilize=20
>> > >    the common
>> > >    data, state machines, and APIs of the underlying NSIS=20
>> > >    protocols and
>> > >    are not expected to re-define or extend these in any way."
>> >=20
>> > Georgios:
>> > Regarding the sentence in Section 4.1:
>> > "QOSMs all utilize
>> > the common data, state machines, and APIs of the underlying NSIS=20
>> > protocols and are not expected to re-define or extend these in any=20
>> > way."
>> >=20
>> > This sentence restricts the possibility of QoS model to use
>> RMF states
>>=20
>> > and data that are not been defined in neither QoS-NSLP or QSPEC.
>> > This sentence should be removed.
>>=20
>> I disagree.  The quoted text was introduced by Dave Oran in addition=20
>> to removing the phrase implying that a QOSM could specify signaling=20
>> protocol changes, and I agree with this.
>> Any changes/extensions to the signaling protocol or state=20
>machines are=20
>> within the scope of QoS-NSLP draft and not the QSPEC draft or a QOSM=20
>> specification draft.  I think you have noted that also in your=20
>> subsequent posting at=20
>> http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html.
>>=20
>> If any extensions are required to the NSIS signaling protocol as a=20
>> result of the 'severe change on QoS Model definition and=20
>capabilities'
>> you have noted, those proposed changes/extensions should be=20
>addressed=20
>> to the QoS NSLP draft IMO.
>>=20
>> Perhaps Dave can comment here also when he gets a chance.
>>=20
>> > > > Comment_4:
>> > > > -------------
>> > > > Section 5.1 Local QSPEC definition and processing
>> > > >=20
>> > > > By reading this section it gives the impression that the two=20
>> > > > methods
>> > > > a) and b) cannot be used by the same QoS model.
>> > > > Method a): translate the
>> > > > initiator QSPEC into a local QSPEC and encapsulate the
>> initiator
>> > > > QSPEC in the RESERVE message Method b): b) tunnel the=20
>initiator=20
>> > > > QSPEC through the local domain and reserve resources by
>> generating
>>=20
>> > > > a new RESERVE message through the local domain containing the=20
>> > > > local QSPEC.
>> > > >=20
>> > > > Note that according to the discussions that we have had
>> until now
>> > > > method a) should be able to be used in combination with
>> method b)
>> > > > by the same QoS model for the situation that the local QSPEC=20
>> > > > encapsulates the initiator QSPEC in order to satisfy=20
>requirement
>> > > > 5.4.2 that is specified in RFC 3726, see:
>> > > > http://www.ietf.org/rfc/rfc3726.txt
>> > > >=20
>> > > > Please add the following sentence at the end of the first=20
>> > > > paragraph of Section 5.1.
>> > > > "Note that when method b) is used, the encapsulation of the=20
>> > > > initiator QSPEC into a local QSPEC should also be=20
>possible when=20
>> > > > the local QoS model needs to satisfy Requirement
>> > > > 5.4.2 specified in RFC 3726, by adding and removing local=20
>> > > > QOSM-specific Control Information parameters on top of the=20
>> > > > initiator QSPEC."
>> > >=20
>> > > Your comment here is not clear to me.  It would help to
>> provide an
>> > > example to illustrate what you are trying to accomplish. =20
>> It seems
>> > > that you are trying to specify QoS-NSLP functionality,
>> rather than
>> > > QSPEC functionality.  If so, that functionality should be
>> specified
>> > > in the QoS-NSLP draft rather than the QSPEC draft, perhaps the=20
>> > > QoS-NSLP authors can comment.
>> >=20
>> > Georgios:
>> > No I am not trying to define QOS-NSLP functionality.
>> > This is related to QSPEC control information that has to be
>> carried by
>>=20
>> > end-to-end messages.
>> > What I am trying to say is that all the discussion that we=20
>have had=20
>> > regarding the encapsulation of the QSPEC object were
>> associated with
>> > requirement 5.4.2 of RFC 3726, see below:
>> >=20
>> > -----------------
>> > "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain=20
>> > Information
>> >=20
>> >    It SHOULD be possible to add and remove local scope elements.
>> >    Compared to Requirement 5.3.5 this requirement does use
>> the normal
>> >    signaling process and message exchange for transporting local
>> >    information.  For example, at the entrance to a domain, domain-
>> >    specific information is added information is added, which=20
>> >    is used in
>> >    this domain only, and the information is removed again when a
>> >    signaling message leaves the domain.  The motivation is in the
>> >    economy of re-using the protocol for domain internal=20
>signaling of
>> >    various information pieces.  Where additional
>> information is needed
>> >    within a particular domain, it should be possible to
>> carry this at
>> >    the same time as the end-to-end information.", from RFC 3726
>> > ------------------
>> > Thus what I am saying is:
>> > Please add the following sentence at the end of the first
>> paragraph of
>>=20
>> > Section 5.1.
>> >=20
>> > "Note that when method b) is used, the encapsulation of the
>> initiator
>> > QSPEC into a local QSPEC should also be possible when the=20
>local QoS=20
>> > model needs to satisfy Requirement
>> > 5.4.2 specified in RFC 3726, by adding and removing local=20
>> > QOSM-specific Control Information parameters on top of the
>> initiator
>> > QSPEC."
>>=20
>> First, the suggested text isn't clear.  If method b) is used
>> (tunneling) then presumably method a) is not also used at the same=20
>> time.  However, the phrasing of the above makes it sound that way.
>>=20
>> Second, an example would help here.  I presume you are=20
>referring e.g.,=20
>> to RMD adding 'control information' (i.e., 'handling directive')=20
>> parameters to the local QSPEC that are not included in the initiator=20
>> QSPEC.  I think the requirement would be that the RMD QOSM=20
>provides a=20
>> local QSPEC that is consistent with the initiator QSPEC, as=20
>we agreed=20
>> on the list (see also slide 8 of the IETF-67 presentation).
>>=20
>> If the local QSPEC introduces functionality inconsistent with the=20
>> initiator QSPEC by appending the handling directive parameters, then=20
>> it is not allowed.
>>=20
>> > > > Comment_5:
>> > > > -----------
>> > > > Section 5.1, last paragraph:
>> > > >=20
>> > > > Please change the following:
>> > > > "For example, RMD can define a local QSPEC that=20
>contains TMOD =3D=20
>> > > > bandwidth (sets r=3Dp, b/m to large)."
>> > > >=20
>> > > > Into:
>> > > > "For example, in RMD the TMOD parameters contained in
>> the original
>>=20
>> > > > initiator QSPEC are mapped into the equivalent TMOD parameter=20
>> > > > representing only the peak bandwidth in the local QSPEC."
>> > >=20
>> > > OK with me.
>> > >=20
>> > > > Comment_6:
>> > > > -------------
>> > > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to
>> be followed
>> > > > regarding the QSPEC control information are not given:
>> > > >=20
>> > > > Please include the following paragraph at the end of
>> this section:
>> > > > "Regarding QSPEC Control Information, the default rule
>> is that all
>> > > >    QSPEC parameters that have been included in the RESERVE=20
>> > > >    message by
>> > > >    the QNI are also included in the RESPONSE message by the=20
>> > > >    QNR with the
>> > > >    value they had when arriving at the QNR.  When
>> traveling in the
>> > > >    RESPONSE message, all QSPEC Control Information
>> parameters are
>> > > >    read-only.  Note that a QOSM specification may=20
>define its own
>> > > >    QOSM-specific Control Information parameters and=20
>> > > >    processing rules."
>> > >=20
>> > > Please see previous email comment on QSPEC control information.
>> >=20
>> > Georgios: I think that a description of how the QSPEC control=20
>> > information is handled is needed.
>>=20
>> Please see above comments on 'control information' terminology.
>>=20
>> Thanks,
>> Jerry
>> =20
>> > > > Comment_7:
>> > > > ------------
>> > > > Section 6.1:
>> > > > I do not understand the second sentence from the below two
>> > > > sentences:
>> > > > "N Flag: Not-supported QSPEC parameter flag (see=20
>Section 5.2.2).
>> > > >            For QSPEC parameters the value of this flag
>> is always
>> > > > zero."
>> > >=20
>> > > Good catch, this is a typo, the sentence should be removed.
>> > >=20
>> >=20
>> >=20
>> > Best Regards,
>> > Georgios
>> >=20
>>=20
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>=20
>
>
>
>_______________________________________________
>nsis mailing list
>nsis@ietf.org
>https://www1.ietf.org/mailman/listinfo/nsis
>

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



From nsis-bounces@ietf.org Sat Dec 23 12:39:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GyAq6-0005Z1-Nb; Sat, 23 Dec 2006 12:39:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GyAq5-0005Yt-9K
	for nsis@ietf.org; Sat, 23 Dec 2006 12:39:17 -0500
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GyAq1-0001Ub-KW
	for nsis@ietf.org; Sat, 23 Dec 2006 12:39:17 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kBNHbpNV022970; Sat, 23 Dec 2006 19:38:02 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Dec 2006 19:38:32 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Dec 2006 19:38:31 +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
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Date: Sat, 23 Dec 2006 19:31:46 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC019F091F@esebe199.NOE.Nokia.com>
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC8072@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAfQcYAABi6fQAANLmKAAAE4mgAACINggADIkUFA=
From: <john.loughney@nokia.com>
To: <gash@att.com>, <karagian@cs.utwente.nl>, <nsis@ietf.org>
X-OriginalArrivalTime: 23 Dec 2006 17:38:31.0768 (UTC)
	FILETIME=[29EEF580:01C726B9]
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d9da51c9fdb90403a7d571fc0f0dbf29
Cc: 
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

Hi all,

When Jerry posted the draft with the change log, I basically noted
that the changes were based upon previous discussions, on the=20
mailing list and the meeting.

I am unsure of the techincal issues that are being raised.  Rather
than get into a discussion of what was discussed or not, what I
would like to understand better is more understanding what are=20
the technical issues behind Georgios' issues.

Additionally, I would like to hear from others about their opinions
on this issue.

thanks,
John

>-----Original Message-----
>From: ext Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]=20
>Sent: 22 December, 2006 20:12
>To: Georgios Karagiannis; nsis@ietf.org
>Cc: Ash, Gerald R (Jerry), ALABS
>Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20
>
>Georgios,
>
>It's not true as you and 2 others have stated that the changes=20
>were not discussed.  They were discussed, at length.  For=20
>example, the revised definition of QOSM was clearly stated and=20
>discussed on the list, see=20
>http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.htm
>l and also see all the list discussion following that post. =20
>The revised definition and all the other changes were clearly=20
>presented in the slides at IETF-67, see minutes and slides at=20
>http://www3.ietf.org/proceedings/06nov/index.html.  You can=20
>listen to the complete IETF-67 presentation/discussion again=20
>at=20
>http://limestone.uoregon.edu/ftp/pub/videolab/media/ietf67/ietf
>67ch4-thu
>-am.mp3. =20
>
>You can review the slides, meeting discussion, list=20
>discussion, meeting minutes, and verify that for yourself.
>
>So the editors did not 'make up the changes without=20
>discussion' as you and 2 others have suggested.  That is=20
>certainly wrong and I think you should acknowledge that.
>
>It is not useful going forward to debate the past, but=20
>incendiary wrong statements should not go unanswered.
>
>Once again, I've responded to your technical comments, you can=20
>comment further if you wish.=20
>
>It would be good for others to comment on the technical points.
>
>Jerry=20
>
>-----Original Message-----
>From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>Sent: Friday, December 22, 2006 11:36 AM
>To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20
>
>Hi Jerry
>
>The changes that are included in version 13 of the QSEPC=20
>template draft regarding the QSPEC control information and the=20
>limitations of the QoS models have never been discussed=20
>because they were never stated clearly.=20
>
>If they would have been stated clearly then I would have sent=20
>my comments at that time instead of sending them now!
>
>Furthermore, from what I have seen in v. 13 of the draft you=20
>also have not solved the stacking issue, because you are=20
>actually dictating that encapsulation cannot be combined and=20
>used together with the tunneling (parallel sessions) method.
>
>
>Best Regards,
>Georgios
>
>>=20
>> =20
>>=20
>> > -----Original Message-----
>> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>> > Sent: vrijdag 22 december 2006 16:37
>> > To: Georgios Karagiannis; nsis@ietf.org
>> > Cc: Ash, Gerald R (Jerry), ALABS
>> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>> >=20
>> > Georgios,
>> >=20
>> > > -----Original Message-----
>> > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>> > > Sent: Friday, December 22, 2006 9:13 AM
>> > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>> > >=20
>> > > Hi Jerry
>> > >=20
>> > > By just saying that "these changes are suggested by Dave in the=20
>> > > e-mail" does not work.
>> > >=20
>> > > The proposal of Dave was not clear on the QoS model changes
>> > that you
>> > > wanted to do.
>> >=20
>> > All changes to the draft have been extensively discussed on
>> the list
>> > and are all contained in the slides presented at IETF-67. =20
>You were=20
>> > there at
>> > IETF-67 and participated in all the list discussion.  The
>> summary of
>> > changes in the slides is quite specific and clear, take
>> another look.
>> > Have a look at the minutes as well
>> > http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt.  The only=20
>> > disagreements noted are with regard to stacking, which is an issue=20
>> > that we later resolved on the list.  Go back and check it out.
>> >=20
>> > > Now I understand which changes you want to include in the QSPEC=20
>> > > template draft.
>> > > This is also the reason of disagreeing with you now and sending=20
>> > > comments to the nsis list.
>> >=20
>> > I responded to your further comments, see below.  Others are=20
>> > encouraged to comment as well.
>> >=20
>> > Jerry
>> >=20
>> > >=20
>> > > Furthermore, note that the QOS-NSLP draft defines which
>> > capabilities
>> > > should be supported by the QoS models and not the QSPEC template=20
>> > > draft.
>> > >=20
>> > > Best Regards,
>> > > Georgios
>> > >=20
>> > >=20
>> > > > -----Original Message-----
>> > > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>> > > > Sent: vrijdag 22 december 2006 15:01
>> > > > To: Georgios Karagiannis; nsis@ietf.org
>> > > > Cc: Ash, Gerald R (Jerry), ALABS
>> > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>> > > >=20
>> > > > Georgios,
>> > > >=20
>> > > > See below.=20
>> > > >=20
>> > > > > -----Original Message-----
>> > > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>> > > > > Sent: Thursday, December 21, 2006 9:22 AM
>> > > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>> > > > > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
>> > > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>> > > > >=20
>> > > > > Hi Jerry
>> > > > >=20
>> > > > > Please see below! I have severe concerns about some changes
>> > > > that have
>> > > > > been done in the QSPEC template draft.
>> > > > >=20
>> > > > > > -----Original Message-----
>> > > > > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>> > > > > > Sent: woensdag 20 december 2006 14:20
>> > > > > > To: Georgios Karagiannis; nsis@ietf.org
>> > > > > > Cc: Ash, Gerald R (Jerry), ALABS
>> > > > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>> > > > > >=20
>> > > > > > Hi Georgios,
>> > > > > >=20
>> > > > > > See below.=20
>> > > > > >=20
>> > > > > > > -----Original Message-----
>> > > > > > > From: Georgios Karagiannis=20
>[mailto:karagian@cs.utwente.nl]
>> > > > > > > Sent: Wednesday, December 20, 2006 5:26 AM
>> > > > > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>> > > > > > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
>> > > > > > >=20
>> > > > > > > Hi Jerry
>> > > > > > >=20
>> > > > > > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
>> > > > > > >=20
>> > > > > > > Comment_1:
>> > > > > > > --------------
>> > > > > > > Please reinclude the concept of QSPEC control
>> > > > information that was
>> > > > > > > included in all previous versions of the QSPEC
>> > template draft.
>> > > > > > > In
>> > > > > > >=20
>> > > > > >=20
>> > > > >=20
>> > > >=20
>> > >=20
>> >=20
>> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
>> > > > > > > concept was described in Section 5.1.
>> > > > > >=20
>> > > > > > Please see previous email comment on QSPEC control
>> > information.
>> > > > >=20
>> > > > > Georgios:=20
>> > > > > In order to emphasize the need of having QSPEC control
>> > > information
>> > > > > parameters  I  would however appreciate if the name of
>> > > > Section 4.3.3
>> > > > > is changed
>> > > > > From:
>> > > > > 4.3.3 Traffic Handling Directives
>> > > > > INTO:
>> > > > > 4.3.3 QSPEC control information
>> > > >=20
>> > > > The updated QSPEC parameter terminology/semantics are as
>> > suggested
>> > > > by Dave Oran (see slides presented at IETF-67=20
>> > > > http://www3.ietf.org/proceedings/06nov/index.html).  I
>> think the
>> > > > current terminology is more clear/descriptive of the QSPEC=20
>> > > > parameters so I don't favor going backwards to less clear=20
>> > > > terminology.  I was never clear on why we used the 'control=20
>> > > > information' terminology in the first place, e.g., I
>> don't think
>> > > > it's a very good descriptor of the 'excess treatment'=20
>parameter.
>> > > >=20
>> > > > Perhaps Dave can comment on this point also when he
>> gets a chance.
>> > > >=20
>> > > > > > > Comment_2:
>> > > > > > > -----------
>> > > > > > >=20
>> > > > > > > Section 6.1:
>> > > > > > > Please reintroduce the format that is required=20
>in order to
>> > > > > > specify the
>> > > > > > > QSPEC control information, see:
>> > > > > > > Section 7.1 of:
>> > > > > > >=20
>> > > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
>> > > > > >=20
>> > > > > > Please see previous email comment on QSPEC control
>> > information.
>> > > > >=20
>> > > > >=20
>> > > > > Georgios: If you rename section 4.3.3 to QSPEC control
>> > > information
>> > > > > then I think that reformatting of section 6.1 is not needed.
>> > > > > Please add the proposed sentence by Dave (but change=20
>the term=20
>> > > > > "handling directives" to "QSPEC control Information"). I am
>> > > > not sure
>> > > > > where it is better to add this sentence, maybe in=20
>Section 5.4.
>> > > > >=20
>> > > > > "QoSMs are free, subject to IANA registration and review
>> > > rules, to
>> > > > > extend QSPECs by adding parameters of any of the kinds
>> > > supported by
>> > > > > the standard QSPEC. This includes traffic description
>> > parameters,
>> > > > > constraint parameters and QSPEC control information.
>> > > QoSMs are not
>> > > > > permitted, however, to reinterpret or redefine the
>> > standard QSPEC
>> > > > > parameters specified in this document"
>> > > >=20
>> > > > Yes, the text suggested by Dave will be added.
>> > > >=20
>> > > > > > > Comment_3:
>> > > > > > > ----------
>> > > > > > > Section 4.1 :QoS Models
>> > > > > > > The definition of the QoS model is not complete. An
>> > important
>> > > > > > > sentence that was used in the previous version of the
>> > > draft is
>> > > > > > > removed.
>> > > > > > > Please add the following sentence to the definition
>> > > of the QoS
>> > > > > > > Model
>> > > > > > > (QOSM):
>> > > > > > >=20
>> > > > > > > The same as described above have to be applied in
>> > > this section.
>> > > > > > > After the following sentence:
>> > > > > > >=20
>> > > > > > > "A QOSM specification MAY include the following:"
>> > > > > > >=20
>> > > > > > > include the following bullet:
>> > > > > > > "- it specifies how to use QOS NSLP to signal for
>> this QOSM"
>> > > > > >=20
>> > > > > > That sentence was removed in Dave's proposed QOSM
>> > > > re-definition, see
>> > > > > >=20
>> http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
>> > > > > > ml.  It was unclear what that sentence meant, QoS-NSLP
>> > > > specifies how
>> > > > > > to signal, not QOSM specifications, so the sentence
>> > was removed.
>> > > > > >=20
>> > > > > > I believe the sentence was intended to mean that when
>> > QoS NSLP
>> > > > > > allows various options to be selected, a QOSM should
>> > be able to
>> > > > > > determine which option is used.  For that purpose the
>> > following
>> > > > > > sentence was added in Section 4.1:
>> > > > > >=20
>> > > > > > "     A QOSM specification MAY include the following:
>> > > > > >      ...
>> > > > > >      - can state which QoS-NSLP options a QOSM wants to
>> > > use, when
>> > > > > >      several options are available for a QOSM (e.g.,
>> > > > local QSPEC to
>> > > > > >      either be a) tunneled or b) encapsulate
>> > initiator QSPEC)."
>> > > > > >=20
>> > > > > > Also, to avoid any misinterpretation that QOSMs are free
>> > > > to specify
>> > > > > > additional constraints, state machines, protocol data,
>> > > > etc. for NSLP
>> > > > > > beyond that which is specific in the QoS NSLP
>> > > specification, the
>> > > > > > following was added to Section 4.1:
>> > > > > >=20
>> > > > > > "  QOSMs affect the operation of the RMF in NSIS-capable
>> > > > nodes, the
>> > > > > >    information carried in QSPEC objects, and may under some
>> > > > > >    circumstances (e.g. aggregation) cause a separate NSLP=20
>> > > > > >    session to be
>> > > > > >    instantiated by having the RMF as a QNI. QOSMs
>> all utilize
>> > > > > >    the common
>> > > > > >    data, state machines, and APIs of the underlying NSIS=20
>> > > > > >    protocols and
>> > > > > >    are not expected to re-define or extend these in
>> any way."
>> > > > >=20
>> > > > > Georgios:
>> > > > > Regarding the sentence in Section 4.1:
>> > > > > "QOSMs all utilize
>> > > > > the common data, state machines, and APIs of the
>> > underlying NSIS
>> > > > > protocols and are not expected to re-define or extend
>> > > these in any
>> > > > > way."
>> > > > >=20
>> > > > > This sentence restricts the possibility of QoS model to use
>> > > > RMF states
>> > > > > and data that are not been defined in neither
>> QoS-NSLP or QSPEC.
>> > > > > This sentence should be removed.
>> > > >=20
>> > > > I disagree.  The quoted text was introduced by Dave Oran
>> > in addition
>> > > > to removing the phrase implying that a QOSM could specify
>> > signaling
>> > > > protocol changes, and I agree with this.
>> > > > Any changes/extensions to the signaling protocol or state
>> > machines
>> > > > are within the scope of QoS-NSLP draft and not the QSPEC
>> > draft or a
>> > > > QOSM specification draft.  I think you have noted that
>> > also in your
>> > > > subsequent posting at
>> > > >=20
>> http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html.
>> > > >=20
>> > > > If any extensions are required to the NSIS signaling
>> > protocol as a
>> > > > result of the 'severe change on QoS Model definition and=20
>> > > > capabilities'
>> > > > you have noted, those proposed changes/extensions should be=20
>> > > > addressed to the QoS NSLP draft IMO.
>> > > >=20
>> > > > Perhaps Dave can comment here also when he gets a chance.
>> > > >=20
>> > > > > > > Comment_4:
>> > > > > > > -------------
>> > > > > > > Section 5.1 Local QSPEC definition and processing
>> > > > > > >=20
>> > > > > > > By reading this section it gives the impression
>> > that the two
>> > > > > > > methods
>> > > > > > > a) and b) cannot be used by the same QoS model.
>> > > > > > > Method a): translate the
>> > > > > > > initiator QSPEC into a local QSPEC and encapsulate the
>> > > > initiator
>> > > > > > > QSPEC in the RESERVE message Method b): b) tunnel the
>> > > initiator
>> > > > > > > QSPEC through the local domain and reserve resources by
>> > > > generating
>> > > > > > > a new RESERVE message through the local domain
>> > containing the
>> > > > > > > local QSPEC.
>> > > > > > >=20
>> > > > > > > Note that according to the discussions that we have had
>> > > > until now
>> > > > > > > method a) should be able to be used in combination with
>> > > > method b)
>> > > > > > > by the same QoS model for the situation that the
>> > local QSPEC
>> > > > > > > encapsulates the initiator QSPEC in order to satisfy
>> > > > requirement
>> > > > > > > 5.4.2 that is specified in RFC 3726, see:
>> > > > > > > http://www.ietf.org/rfc/rfc3726.txt
>> > > > > > >=20
>> > > > > > > Please add the following sentence at the end of=20
>the first=20
>> > > > > > > paragraph of Section 5.1.
>> > > > > > > "Note that when method b) is used, the
>> encapsulation of the
>> > > > > > > initiator QSPEC into a local QSPEC should also be
>> > > possible when
>> > > > > > > the local QoS model needs to satisfy Requirement
>> > > > > > > 5.4.2 specified in RFC 3726, by adding and=20
>removing local=20
>> > > > > > > QOSM-specific Control Information parameters on
>> top of the
>> > > > > > > initiator QSPEC."
>> > > > > >=20
>> > > > > > Your comment here is not clear to me.  It would help to
>> > > > provide an
>> > > > > > example to illustrate what you are trying to accomplish. =20
>> > > > It seems
>> > > > > > that you are trying to specify QoS-NSLP functionality,
>> > > > rather than
>> > > > > > QSPEC functionality.  If so, that functionality should be
>> > > > specified
>> > > > > > in the QoS-NSLP draft rather than the QSPEC draft,
>> > perhaps the
>> > > > > > QoS-NSLP authors can comment.
>> > > > >=20
>> > > > > Georgios:
>> > > > > No I am not trying to define QOS-NSLP functionality.
>> > > > > This is related to QSPEC control information that has to be
>> > > > carried by
>> > > > > end-to-end messages.
>> > > > > What I am trying to say is that all the discussion that
>> > > we have had
>> > > > > regarding the encapsulation of the QSPEC object were
>> > > > associated with
>> > > > > requirement 5.4.2 of RFC 3726, see below:
>> > > > >=20
>> > > > > -----------------
>> > > > > "5.4.2.  It SHOULD be Possible to Add and Remove=20
>Local Domain=20
>> > > > > Information
>> > > > >=20
>> > > > >    It SHOULD be possible to add and remove local
>> scope elements.
>> > > > >    Compared to Requirement 5.3.5 this requirement does use
>> > > > the normal
>> > > > >    signaling process and message exchange for
>> transporting local
>> > > > >    information.  For example, at the entrance to a
>> > domain, domain-
>> > > > >    specific information is added information is added, which=20
>> > > > >    is used in
>> > > > >    this domain only, and the information is removed
>> again when a
>> > > > >    signaling message leaves the domain.  The motivation
>> > is in the
>> > > > >    economy of re-using the protocol for domain internal
>> > > signaling of
>> > > > >    various information pieces.  Where additional
>> > > > information is needed
>> > > > >    within a particular domain, it should be possible to
>> > > > carry this at
>> > > > >    the same time as the end-to-end information.",
>> from RFC 3726
>> > > > > ------------------
>> > > > > Thus what I am saying is:
>> > > > > Please add the following sentence at the end of the first
>> > > > paragraph of
>> > > > > Section 5.1.
>> > > > >=20
>> > > > > "Note that when method b) is used, the encapsulation of the
>> > > > initiator
>> > > > > QSPEC into a local QSPEC should also be possible when the
>> > > local QoS
>> > > > > model needs to satisfy Requirement
>> > > > > 5.4.2 specified in RFC 3726, by adding and removing local=20
>> > > > > QOSM-specific Control Information parameters on top of the
>> > > > initiator
>> > > > > QSPEC."
>> > > >=20
>> > > > First, the suggested text isn't clear.  If method b) is used
>> > > > (tunneling) then presumably method a) is not also used at
>> > the same
>> > > > time.  However, the phrasing of the above makes it
>> sound that way.
>> > > >=20
>> > > > Second, an example would help here.  I presume you are
>> referring
>> > > > e.g., to RMD adding 'control information' (i.e., 'handling
>> > > > directive') parameters to the local QSPEC that are not
>> > included in
>> > > > the initiator QSPEC.  I think the requirement would be
>> > that the RMD
>> > > > QOSM provides a local QSPEC that is consistent with the
>> initiator
>> > > > QSPEC, as we agreed on the list (see also slide 8 of
>> the IETF-67
>> > > > presentation).
>> > > >=20
>> > > > If the local QSPEC introduces functionality
>> inconsistent with the
>> > > > initiator QSPEC by appending the handling directive
>> > parameters, then
>> > > > it is not allowed.
>> > > >=20
>> > > > > > > Comment_5:
>> > > > > > > -----------
>> > > > > > > Section 5.1, last paragraph:
>> > > > > > >=20
>> > > > > > > Please change the following:
>> > > > > > > "For example, RMD can define a local QSPEC that
>> > > contains TMOD =3D
>> > > > > > > bandwidth (sets r=3Dp, b/m to large)."
>> > > > > > >=20
>> > > > > > > Into:
>> > > > > > > "For example, in RMD the TMOD parameters contained in
>> > > > the original
>> > > > > > > initiator QSPEC are mapped into the equivalent TMOD
>> > parameter
>> > > > > > > representing only the peak bandwidth in the local QSPEC."
>> > > > > >=20
>> > > > > > OK with me.
>> > > > > >=20
>> > > > > > > Comment_6:
>> > > > > > > -------------
>> > > > > > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to
>> > > > be followed
>> > > > > > > regarding the QSPEC control information are not given:
>> > > > > > >=20
>> > > > > > > Please include the following paragraph at the end of
>> > > > this section:
>> > > > > > > "Regarding QSPEC Control Information, the default rule
>> > > > is that all
>> > > > > > >    QSPEC parameters that have been included in
>> the RESERVE
>> > > > > > >    message by
>> > > > > > >    the QNI are also included in the RESPONSE
>> message by the
>> > > > > > >    QNR with the
>> > > > > > >    value they had when arriving at the QNR.  When
>> > > > traveling in the
>> > > > > > >    RESPONSE message, all QSPEC Control Information
>> > > > parameters are
>> > > > > > >    read-only.  Note that a QOSM specification may
>> > > define its own
>> > > > > > >    QOSM-specific Control Information parameters and=20
>> > > > > > >    processing rules."
>> > > > > >=20
>> > > > > > Please see previous email comment on QSPEC control
>> > information.
>> > > > >=20
>> > > > > Georgios: I think that a description of how the=20
>QSPEC control=20
>> > > > > information is handled is needed.
>> > > >=20
>> > > > Please see above comments on 'control information' terminology.
>> > > >=20
>> > > > Thanks,
>> > > > Jerry
>> > > > =20
>> > > > > > > Comment_7:
>> > > > > > > ------------
>> > > > > > > Section 6.1:
>> > > > > > > I do not understand the second sentence from the=20
>below two
>> > > > > > > sentences:
>> > > > > > > "N Flag: Not-supported QSPEC parameter flag (see
>> > > Section 5.2.2).
>> > > > > > >            For QSPEC parameters the value of this flag
>> > > > is always
>> > > > > > > zero."
>> > > > > >=20
>> > > > > > Good catch, this is a typo, the sentence should be removed.
>> > > > > >=20
>> > > > >=20
>> > > > >=20
>> > > > > Best Regards,
>> > > > > Georgios
>> > > > >=20
>> > > >=20
>> > >=20
>> > >=20
>> > >=20
>> >=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>=20
>
>
>
>_______________________________________________
>nsis mailing list
>nsis@ietf.org
>https://www1.ietf.org/mailman/listinfo/nsis
>

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



From nsis-bounces@ietf.org Sat Dec 23 12:48:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GyAyL-0000mM-GY; Sat, 23 Dec 2006 12:47:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GyAyK-0000mH-3i
	for nsis@ietf.org; Sat, 23 Dec 2006 12:47:48 -0500
Received: from mclmx2.mail.saic.com ([149.8.64.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GyAyJ-0003rw-Ji
	for nsis@ietf.org; Sat, 23 Dec 2006 12:47:48 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx2.mail.saic.com; Sat, 23 Dec 2006 12:47:38 -0500
Received: from 0015-ITS-EXBH01.us.saic.com ([10.43.229.18])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006122312473119565 ; Sat, 23 Dec 2006 12:47:36 -0500
Received: from 0591-ITS-EXMP02.us.saic.com ([10.42.81.248]) by
	0015-ITS-EXBH01.us.saic.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Dec 2006 12:47:31 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 23 Dec 2006 12:45:57 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426E1CF76@0591-ITS-EXMP02.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: warning (was:: Comments on draft-ietf-nsis-qspec-13.txt )
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAfQcYAABi6fQAAHO094ANbr/0AAA6oD/
References: <BAA65A575825454CBB0103267553FCCC019F091C@esebe199.NOE.Nokia.com>
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: <john.loughney@nokia.com>,
    <nsis@ietf.org>
X-OriginalArrivalTime: 23 Dec 2006 17:47:31.0895 (UTC)
	FILETIME=[6BDFCC70:01C726BA]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f60fbf3dbcaca652b6d10036f0630412
Cc: lars.eggert@gmail.com
Subject: [NSIS] RE: warning (was:: Comments on draft-ietf-nsis-qspec-13.txt )
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>
Content-Type: multipart/mixed; boundary="===============1156141096=="
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1156141096==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C726BA.6B918A7A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C726BA.6B918A7A
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

John;
=20
I am sorry if you think so.
=20
One thing is not clear: Did we define QOS model?
=20
Best regards,
Radhika

________________________________

From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
Sent: Sat 12/23/2006 12:27 PM
To: RADHIKA.R.ROY@saic.com; nsis@ietf.org
Cc: magnus.westerlund@ericsson.com; lars.eggert@gmail.com
Subject: warning (was:: Comments on draft-ietf-nsis-qspec-13.txt )


Rahdhika,
=20
I have tried to politely ask you to restrain from content-free posting.  =
You are not the working group chair, so you are not in a position to =
declare working group concensus.  Additionally, it is clearly within our =
charter to work with QoS defined by other SDOs.
=20
If you continue in your inappropriate postings, I will be forced to =
consider revoking your posting rights.
=20
John


________________________________

	From: ext Roy, Radhika R. [mailto:RADHIKA.R.ROY@saic.com]=20
	Sent: 22 December, 2006 17:48
	To: Ash, Gerald R (Jerry), ALABS; Georgios Karagiannis; nsis@ietf.org
	Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20
=09
=09
	All those changes do not reflect the work group discussions as some of =
them Georgios mentioned.
	=20
	It does not have to the way you so-called co-editors think so. If the =
WG agrees with the changes that you have made in the draft, then why do =
these WG people disagree with you?
	=20
	Do you have technical explanations to answer Georgeo's points?
	=20
	If not, it is the time to leave this draft to a NEW editor who work =
based on WG technical consensus. Or, submit as individual non-WG draft. =
It is so simple.
	=20
	Best regards,
	Radhika

________________________________

	From: nsis-bounces@ietf.org on behalf of Ash, Gerald R (Jerry), ALABS
	Sent: Fri 12/22/2006 10:36 AM
	To: Georgios Karagiannis; nsis@ietf.org
	Cc: Ash, Gerald R (Jerry), ALABS
	Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20
=09
=09

	Georgios,
=09
	> -----Original Message-----
	> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
	> Sent: Friday, December 22, 2006 9:13 AM
	> To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
	> Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
	>
	> Hi Jerry
	>
	> By just saying that "these changes are suggested by Dave in
	> the e-mail" does not work.
	>
	> The proposal of Dave was not clear on the QoS model changes that
	> you wanted to do.
=09
	All changes to the draft have been extensively discussed on the list =
and
	are all contained in the slides presented at IETF-67.  You were there =
at
	IETF-67 and participated in all the list discussion.  The summary of
	changes in the slides is quite specific and clear, take another look.
	Have a look at the minutes as well
	http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt.  The only
	disagreements noted are with regard to stacking, which is an issue that
	we later resolved on the list.  Go back and check it out.
=09
	> Now I understand which changes you want to include in the
	> QSPEC template draft.
	> This is also the reason of disagreeing with you now and
	> sending comments to the nsis list.
=09
	I responded to your further comments, see below.  Others are encouraged
	to comment as well.
=09
	Jerry
=09
	>
	> Furthermore, note that the QOS-NSLP draft defines which capabilities
	> should be supported by the QoS models and not the
	> QSPEC template draft.
	>
	> Best Regards,
	> Georgios
	>
	>
	> > -----Original Message-----
	> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
	> > Sent: vrijdag 22 december 2006 15:01
	> > To: Georgios Karagiannis; nsis@ietf.org
	> > Cc: Ash, Gerald R (Jerry), ALABS
	> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
	> >
	> > Georgios,
	> >
	> > See below.
	> >
	> > > -----Original Message-----
	> > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
	> > > Sent: Thursday, December 21, 2006 9:22 AM
	> > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
	> > > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
	> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
	> > >
	> > > Hi Jerry
	> > >
	> > > Please see below! I have severe concerns about some changes
	> > that have
	> > > been done in the QSPEC template draft.
	> > >
	>


------_=_NextPart_001_01C726BA.6B918A7A
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>[NSIS] RE: Comments on =
draft-ietf-nsis-qspec-13.txt</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText61908 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>John;</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I am sorry if you think =
so.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>One thing is not clear: Did =
we define QOS model?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Best regards,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Radhika</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> john.loughney@nokia.com =
[mailto:john.loughney@nokia.com]<BR><B>Sent:</B> Sat 12/23/2006 12:27 =
PM<BR><B>To:</B> RADHIKA.R.ROY@saic.com; nsis@ietf.org<BR><B>Cc:</B> =
magnus.westerlund@ericsson.com; lars.eggert@gmail.com<BR><B>Subject:</B> =
warning (was:: Comments on draft-ietf-nsis-qspec-13.txt =
)<BR></FONT><BR></DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN class=3D391431917-23122006>Rahdhika,</SPAN></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN class=3D391431917-23122006></SPAN></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN class=3D391431917-23122006>I have tried to politely ask =
you to restrain from content-free posting.&nbsp; You are not the working =
group chair, so you are not in a position to declare working group =
concensus.&nbsp; Additionally, it is clearly within our charter to work =
with QoS defined by other SDOs.</SPAN></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN class=3D391431917-23122006></SPAN></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN class=3D391431917-23122006>If you continue in your =
inappropriate postings, I will be forced to consider revoking your =
posting rights.</SPAN></FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><SPAN class=3D391431917-23122006></SPAN><FONT face=3DArial><FONT =
color=3D#0000ff><FONT size=3D2>J<SPAN =
class=3D391431917-23122006>ohn</SPAN></FONT></FONT></FONT><BR></DIV>=0A=
<BLOCKQUOTE dir=3Dltr style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">=0A=
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> ext Roy, Radhika R. =
[mailto:RADHIKA.R.ROY@saic.com] <BR><B>Sent:</B> 22 December, 2006 =
17:48<BR><B>To:</B> Ash, Gerald R (Jerry), ALABS; Georgios Karagiannis; =
nsis@ietf.org<BR><B>Subject:</B> RE: [NSIS] RE: Comments on =
draft-ietf-nsis-qspec-13.txt <BR></FONT><BR></DIV>=0A=
<DIV></DIV>=0A=
<DIV id=3DidOWAReplyText222 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>All those =
changes do not reflect the work group discussions as some of them =
Georgios mentioned.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>It does not have to the way =
you so-called co-editors think so. If the WG agrees with the changes =
that you have made in the draft, then why do these WG people disagree =
with you?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Do you have technical =
explanations to answer Georgeo's points?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>If not, it is the time to =
leave this draft to&nbsp;a NEW editor who work based on WG technical =
consensus. Or, submit as individual non-WG draft. It is so =
simple.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Best regards,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Radhika</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> nsis-bounces@ietf.org on =
behalf of Ash, Gerald R (Jerry), ALABS<BR><B>Sent:</B> Fri 12/22/2006 =
10:36 AM<BR><B>To:</B> Georgios Karagiannis; nsis@ietf.org<BR><B>Cc:</B> =
Ash, Gerald R (Jerry), ALABS<BR><B>Subject:</B> [NSIS] RE: Comments on =
draft-ietf-nsis-qspec-13.txt <BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Georgios,<BR><BR>&gt; -----Original =
Message-----<BR>&gt; From: Georgios Karagiannis [<A =
href=3D"mailto:karagian@cs.utwente.nl">mailto:karagian@cs.utwente.nl</A>]=
<BR>&gt; Sent: Friday, December 22, 2006 9:13 AM<BR>&gt; To: Ash, Gerald =
R (Jerry), ALABS; nsis@ietf.org<BR>&gt; Subject: RE: Comments on =
draft-ietf-nsis-qspec-13.txt<BR>&gt;<BR>&gt; Hi Jerry<BR>&gt;<BR>&gt; By =
just saying that "these changes are suggested by Dave in<BR>&gt; the =
e-mail" does not work.<BR>&gt;<BR>&gt; The proposal of Dave was not =
clear on the QoS model changes that<BR>&gt; you wanted to do.<BR><BR>All =
changes to the draft have been extensively discussed on the list =
and<BR>are all contained in the slides presented at IETF-67.&nbsp; You =
were there at<BR>IETF-67 and participated in all the list =
discussion.&nbsp; The summary of<BR>changes in the slides is quite =
specific and clear, take another look.<BR>Have a look at the minutes as =
well<BR><A =
href=3D"http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt">http://w=
ww3.ietf.org/proceedings/06nov/minutes/nsis.txt</A>.&nbsp; The =
only<BR>disagreements noted are with regard to stacking, which is an =
issue that<BR>we later resolved on the list.&nbsp; Go back and check it =
out.<BR><BR>&gt; Now I understand which changes you want to include in =
the<BR>&gt; QSPEC template draft.<BR>&gt; This is also the reason of =
disagreeing with you now and<BR>&gt; sending comments to the nsis =
list.<BR><BR>I responded to your further comments, see below.&nbsp; =
Others are encouraged<BR>to comment as =
well.<BR><BR>Jerry<BR><BR>&gt;<BR>&gt; Furthermore, note that the =
QOS-NSLP draft defines which capabilities<BR>&gt; should be supported by =
the QoS models and not the<BR>&gt; QSPEC template draft.<BR>&gt;<BR>&gt; =
Best Regards,<BR>&gt; Georgios<BR>&gt;<BR>&gt;<BR>&gt; &gt; =
-----Original Message-----<BR>&gt; &gt; From: Ash, Gerald R (Jerry), =
ALABS [<A href=3D"mailto:gash@att.com">mailto:gash@att.com</A>]<BR>&gt; =
&gt; Sent: vrijdag 22 december 2006 15:01<BR>&gt; &gt; To: Georgios =
Karagiannis; nsis@ietf.org<BR>&gt; &gt; Cc: Ash, Gerald R (Jerry), =
ALABS<BR>&gt; &gt; Subject: RE: Comments on =
draft-ietf-nsis-qspec-13.txt<BR>&gt; &gt;<BR>&gt; &gt; Georgios,<BR>&gt; =
&gt;<BR>&gt; &gt; See below.<BR>&gt; &gt;<BR>&gt; &gt; &gt; =
-----Original Message-----<BR>&gt; &gt; &gt; From: Georgios Karagiannis =
[<A =
href=3D"mailto:karagian@cs.utwente.nl">mailto:karagian@cs.utwente.nl</A>]=
<BR>&gt; &gt; &gt; Sent: Thursday, December 21, 2006 9:22 AM<BR>&gt; =
&gt; &gt; To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org<BR>&gt; &gt; =
&gt; Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'<BR>&gt; &gt; &gt; =
Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt; Hi Jerry<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; =
Please see below! I have severe concerns about some changes<BR>&gt; &gt; =
that have<BR>&gt; &gt; &gt; been done in the QSPEC template =
draft.<BR>&gt; &gt; =
&gt;<BR>&gt;</FONT></P></DIV></BLOCKQUOTE></DIV></BODY></HTML>
------_=_NextPart_001_01C726BA.6B918A7A--


--===============1156141096==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1156141096==--




From nsis-bounces@ietf.org Sat Dec 23 13:42:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GyBop-0004ah-FI; Sat, 23 Dec 2006 13:42:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GyBoo-0004aa-Ie
	for nsis@ietf.org; Sat, 23 Dec 2006 13:42:02 -0500
Received: from mclmx.mail.saic.com ([149.8.64.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GyBon-00060d-4T
	for nsis@ietf.org; Sat, 23 Dec 2006 13:42:02 -0500
Received: from 0015-its-ieg01.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx.mail.saic.com; Sat, 23 Dec 2006 13:41:55 -0500
Received: from 0015-its-exbh02.us.saic.com ([10.43.229.22])
	by 0015-its-ieg01.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006122313415419769 ; Sat, 23 Dec 2006 13:41:54 -0500
Received: from 0591-ITS-EXMP02.us.saic.com ([10.42.81.248]) by
	0015-its-exbh02.us.saic.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Dec 2006 13:41:55 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Date: Sat, 23 Dec 2006 13:39:59 -0500
Message-Id: <62D92A9A02BCC845B202323D49A48426E1CF79@0591-ITS-EXMP02.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt 
Thread-Index: Acce+I4jTBSuFFclSjKBKdQNpa5rQgAGNPGgAUGhQ5AABx2r8AA1GS8gADBoKsAAAfQcYAABi6fQAANLmKAAAE4mgAACINggADIkUFAAATBaRwABSDcJ
References: <BAA65A575825454CBB0103267553FCCC019F091F@esebe199.NOE.Nokia.com>
	<62D92A9A02BCC845B202323D49A48426E1CF77@0591-ITS-EXMP02.us.saic.com>
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: <john.loughney@nokia.com>, <gash@att.com>, <karagian@cs.utwente.nl>,
	<nsis@ietf.org>
X-OriginalArrivalTime: 23 Dec 2006 18:41:55.0055 (UTC)
	FILETIME=[04DE7FF0:01C726C2]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Cc: 
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>
Content-Type: multipart/mixed; boundary="===============2006109617=="
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2006109617==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C726C2.04AD1B38"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C726C2.04AD1B38
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

John:
=20
In addition to Georgio's comments, here are some as follows:
=20
1. We have to define what is "standard" QSPEC as Dave's proposed =
modifications.
=20
2. Our understanding with respect to "standard" QSPEC is the end-to-end =
QSPEC template only as proposed by Roland. This needs to be clarified =
throughout the whole draft. Any inconsistencies to this must be removed =
from the draft. (If needed, a separate detail proposal will be posted in =
the Web site of this draft "showing" what needs to be done throughout =
the draft and people can see and then can make comment if the draft is =
not modified to change as proposed here.)
=20
3. If we refer to QOS model in this draft, what does it mean? What is =
the definition of QOS model? Do RSVP, IntServ, and DiffServ qualify as =
standard QOS model? If so, why? Do QOS SLAs qualify as standard QOS =
models? If not, why do this draft refer Y.1451, DSTE, and 3GPP/Y.1415 as =
QOS models? If Y.1451, DSTE, and 3GPP/Y.1415 qualify as QOS models, will =
all the QOS SLAs based on DiffServ that are being performed throughout =
the world be included in this draft as a part of it? If not, why not?
=20
4. Why do we want to include Y.1451 QOS classes extensions for this =
"generic" standard QSPEC draft as proposed in item 1 proposed by Dave =
mixing between "apples" and "oranges" bring technical inconsistencies =
like non-interoperability?
=20
5. Why do the draft NOT refer all QOSM drafts as mentioned in item 1 for =
all QOS model-specific extensions of the standard generic QSPEC template =
and "remove" all QOS model-specific extensions like Y.1415? What happen =
to this when this question was resolved through agreement that there is =
no consensus on this point? The reply from an editor had been that these =
Y.1415 QOS SLAs were in the draft from the beginning, but was expected =
to be removed as they mix between "apples" and "oranges?" Why do these =
remain in this draft yet? Why are we keeping this technical =
inconsistency despite all those discussions and consensus?
=20
6. The general "tone" of this draft should be to "describe" the generic =
"standard" QSPEC template parameters. It must NOT describe how this =
template be used by NSIS QOS signaling protocol. The NSIS QOS protocols =
be free to use this QSPEC template the way the applications like to use =
any specific parameters to serve its purpose. (If needed, a separate =
detail proposal will be posted in the Web site of this draft "showing" =
what needs to be done throughout the draft and people can see and then =
can make comment if the draft is not modified to change as proposed =
here.)
=20
7. (By the way, all QOSM drafts that describe QOS model-specific will =
deal with all specific use of the generic "standard" QSPEC template as =
mentioned item 1.)
=20
Best regards,
Radhika

________________________________

From: nsis-bounces@ietf.org on behalf of john.loughney@nokia.com
Sent: Sat 12/23/2006 12:31 PM
To: gash@att.com; karagian@cs.utwente.nl; nsis@ietf.org
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt=20



Hi all,

When Jerry posted the draft with the change log, I basically noted
that the changes were based upon previous discussions, on the
mailing list and the meeting.

I am unsure of the techincal issues that are being raised.  Rather
than get into a discussion of what was discussed or not, what I
would like to understand better is more understanding what are
the technical issues behind Georgios' issues.

Additionally, I would like to hear from others about their opinions
on this issue.

thanks,
John




------_=_NextPart_001_01C726C2.04AD1B38
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: [NSIS] RE: Comments on =
draft-ietf-nsis-qspec-13.txt</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText11944 dir=3Dltr><FONT face=3DArial =
color=3D#000000 size=3D2>John:</FONT></DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV id=3DidOWAReplyText57665 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>In addition to&nbsp;Georgio's =
comments, here are some as follows:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>1. We have to define what is =
"standard" QSPEC as Dave's&nbsp;proposed modifications.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>2. Our understanding with =
respect to "standard" QSPEC is the end-to-end QSPEC template only as =
proposed by Roland. This needs to be clarified throughout the whole =
draft. Any inconsistencies to this must be removed from the draft. (If =
needed, a separate detail&nbsp;proposal will be posted in the Web site =
of this draft "showing" what needs to be done throughout the draft and =
people can see and then can make comment if the draft is not modified to =
change as proposed here.)</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>3. If we refer to QOS model =
in this draft, what does it mean? What is the definition of QOS =
model?&nbsp;Do RSVP, IntServ, and DiffServ qualify as standard QOS =
model? If so, why? Do QOS SLAs qualify as standard QOS models? If not, =
why do this draft refer Y.1451, DSTE, and 3GPP/Y.1415 as QOS models? If =
Y.1451, DSTE, and 3GPP/Y.1415 qualify as QOS models, will&nbsp;all the =
QOS SLAs based on DiffServ that are being performed throughout the world =
be included in this draft as a part of it? If not, why not?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>4. Why do we want to include =
Y.1451 QOS classes extensions for this "generic" standard QSPEC draft as =
proposed in item 1 proposed by Dave mixing between "apples" and =
"oranges" bring technical inconsistencies like =
non-interoperability?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>5. Why do the draft NOT refer =
all QOSM drafts as mentioned in item 1 for all QOS model-specific =
extensions of the standard generic QSPEC template and "remove" all QOS =
model-specific extensions like Y.1415? What happen to this when this =
question was resolved through agreement that there is no consensus on =
this point? The reply from an editor had been that these Y.1415 QOS SLAs =
were in the draft from the beginning, but was expected to be removed as =
they mix between "apples" and "oranges?" Why do these remain in this =
draft yet? Why are we keeping this technical inconsistency despite all =
those discussions and consensus?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>6. The general&nbsp;"tone" of =
this draft should be to "describe" the generic "standard" QSPEC template =
parameters. It must NOT describe how this template be used by NSIS QOS =
signaling protocol. The NSIS QOS protocols be free to use this QSPEC =
template the way the applications like to use any specific parameters to =
serve its purpose. (If needed, a separate detail&nbsp;proposal will be =
posted in the Web site of this draft "showing" what needs to be done =
throughout the draft and people can see and then can make comment if the =
draft is not modified to change as proposed here.)</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>7. (By the way, all QOSM =
drafts that describe QOS model-specific will deal with all specific use =
of the generic "standard" QSPEC template as mentioned item =
1.)</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Best regards,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Radhika</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> nsis-bounces@ietf.org on =
behalf of john.loughney@nokia.com<BR><B>Sent:</B> Sat 12/23/2006 12:31 =
PM<BR><B>To:</B> gash@att.com; karagian@cs.utwente.nl; =
nsis@ietf.org<BR><B>Subject:</B> RE: [NSIS] RE: Comments on =
draft-ietf-nsis-qspec-13.txt <BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Hi all,<BR><BR>When Jerry posted the draft with the =
change log, I basically noted<BR>that the changes were based upon =
previous discussions, on the<BR>mailing list and the meeting.<BR><BR>I =
am unsure of the techincal issues that are being raised.&nbsp; =
Rather<BR>than get into a discussion of what was discussed or not, what =
I<BR>would like to understand better is more understanding what =
are<BR>the technical issues behind Georgios' =
issues.<BR><BR>Additionally, I would like to hear from others about =
their opinions<BR>on this =
issue.<BR><BR>thanks,<BR>John<BR><BR></FONT></P></DIV></DIV></BODY></HTML=
>
------_=_NextPart_001_01C726C2.04AD1B38--


--===============2006109617==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============2006109617==--




From nsis-bounces@ietf.org Sun Dec 24 02:29:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GyNn2-0004F9-RQ; Sun, 24 Dec 2006 02:29:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GyNn0-0004Ew-Uk
	for nsis@ietf.org; Sun, 24 Dec 2006 02:28:58 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GyNmv-00021K-UQ
	for nsis@ietf.org; Sun, 24 Dec 2006 02:28:58 -0500
Received: from webmail.cs.utwente.nl (janus.ewi.utwente.nl [130.89.10.26])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with SMTP id kBO7SWvv022467;
	Sun, 24 Dec 2006 08:28:36 +0100 (MET)
Received: from 84.82.109.231 (auth. user karagian@imap2.cs.utwente.nl)
	by webmail.cs.utwente.nl with HTTP; Sun, 24 Dec 2006 07:28:31 +0000
To: "john.loughney@nokia.com" <john.loughney@nokia.com>,
	"lars.westberg@ericsson.com" <lars.westberg@ericsson.com>,
	"gash@att.com" <gash@att.com>, "nsis@ietf.org" <nsis@ietf.org>
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt
Date: Sun, 24 Dec 2006 07:28:30 +0000
X-Mailer: IlohaMail/0.8.13 (On: webmail.cs.utwente.nl)
Message-ID: <GvZb9rPF.1166945310.2783630.karagian@ewi.utwente.nl>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC019F0920@esebe199.NOE.Nokia.com>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Bounce-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
MIME-Version: 1.0 
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.4 () FVGT_s_OBFU_Q1,FVGT_u_HAS_2LETTERFLDR
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Sun, 24 Dec 2006 08:28:47 +0100 (MET)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 54f716cba2c98b25bc07e094cc18394c
Cc: 
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

Hi John

The modularity, flexibility and extensibility bounds of the QSEPC
template draft and the of the QoS models are set at ther starting time
of the NSIS WG.
These modularity, flexibility and extensibility bounds cannot be changed
after the completion of the QoS model work without having convincing
arguments.

My main diagreement on the current changes is that they are introduced
without any discussion, while their impact is very severe on the
functionality of other current and ongoing NSIS specifications.

Best Regards,
Georgios



On 12/23/2006, "john.loughney@nokia.com" <john.loughney@nokia.com>
wrote:

>Georgios and Lars,
>
>As has been discussed earlier, the IESG does not approve of unlimited
>extensibility and flexibility in protocols.  This type of thing actually
>harms interoperability more than helps.  If we want flexibility in the
>protocols, we need to be able to bound that extensibility & have some
>explanations of the trade-offs.  My understanding of the current draft
>text is that the editors were trying to clarify some ambiguity in
>the draft.
>
>I don't think it is good to have ambiguity in the document, so we need
>to have some clarification of the text. If you are unhappy with
>the current text, please submit new text. If you wish to support
>more extensibility, then we need to have some text in the document
>that explains the trade-offs.
>
>thanks,
>John
>
>>-----Original Message-----
>>From: ext Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>>Sent: 22 December, 2006 16:47
>>To: 'Lars Westberg (KI/EAB)'; 'Ash, Gerald R (Jerry), ALABS';
>>nsis@ietf.org
>>Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt
>>
>>Hi Lars
>>
>>I agree with you! Furthermore, by limiting the capabilities of
>>the QOS models also the modularity and flexibility
>>characteristrics and advanteges of NSIS are limited.
>>
>>Best regards,
>>Georgios
>>
>>> -----Original Message-----
>>> From: Lars Westberg (KI/EAB) [mailto:lars.westberg@ericsson.com]
>>> Sent: vrijdag 22 december 2006 15:31
>>> To: Ash, Gerald R (Jerry), ALABS; Georgios Karagiannis; nsis@ietf.org
>>> Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt
>>>
>>> Let's discuss it once more regarding the control information in the
>>> QoS-model,.
>>>
>>> The basic purpose with the QOS-model is to have modularity and
>>> extendabillity for future needs. We have discussed into the protocol
>>> design and I am very suprised that it suddently disappear from the
>>> draft.
>>>
>>> We have one very good example: RSVP-proxy.
>>>
>>> If one wan't to have NSIS-proxies,
>>> =09we need to control information such as: Proxy is found!!
>>> =09=09=09=09=09=09=09    Proxy is
>>> located at this address!
>>>
>>> This could very well be described by QoS-model control information!!!
>>>
>>> The basic problem is that this drafts tries to limit the
>>> extendabillity to exactly the same as RSVP!!! I completely disagree
>>> with that approach.
>>>
>>> There are no need to re-design RSVP with exactly the same
>>> functionality!! We already have RSVP but RSVP is better
>>designed from
>>> scalabillity perspective and have support for Mutlicast support. We
>>> are designing exactly the same protocol but with limited functional
>>> support and without Multicast!!!!!
>>> Note, that we can't use NSIS for TV-broadcast !!!
>>>
>>> I do not beleive that NSIS can replace RSVP!!!
>>> Therefore, QOS-NSLP must support other usage than RSVP!!!
>>>
>>> I agree that the description of control information may be explained
>>> better but it has to be possible to have control information in the
>>> QoS-model.
>>>
>>> But the statement into this draft makes the QoS-NSLP useless!!
>>>
>>>
>>> Regards Lasse
>>>
>>>
>>> -----Original Message-----
>>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>>> Sent: den 22 december 2006 15:01
>>> To: Georgios Karagiannis; nsis@ietf.org
>>> Cc: Ash, Gerald R (Jerry), ALABS
>>> Subject: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt
>>>
>>> Georgios,
>>>
>>> See below.
>>>
>>> > -----Original Message-----
>>> > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>>> > Sent: Thursday, December 21, 2006 9:22 AM
>>> > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>>> > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
>>> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>>> >
>>> > Hi Jerry
>>> >
>>> > Please see below! I have severe concerns about some changes
>>> that have
>>> > been done in the QSPEC template draft.
>>> >
>>> > > -----Original Message-----
>>> > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>>> > > Sent: woensdag 20 december 2006 14:20
>>> > > To: Georgios Karagiannis; nsis@ietf.org
>>> > > Cc: Ash, Gerald R (Jerry), ALABS
>>> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>>> > >
>>> > > Hi Georgios,
>>> > >
>>> > > See below.
>>> > >
>>> > > > -----Original Message-----
>>> > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>>> > > > Sent: Wednesday, December 20, 2006 5:26 AM
>>> > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>>> > > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
>>> > > >
>>> > > > Hi Jerry
>>> > > >
>>> > > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
>>> > > >
>>> > > > Comment_1:
>>> > > > --------------
>>> > > > Please reinclude the concept of QSPEC control
>>> information that was
>>>
>>> > > > included in all previous versions of the QSPEC template draft.
>>> > > > In
>>> > > >
>>> > >
>>> >
>>> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
>>> > > > concept was described in Section 5.1.
>>> > >
>>> > > Please see previous email comment on QSPEC control information.
>>> >
>>> > Georgios:
>>> > In order to emphasize the need of having QSPEC control information
>>> > parameters  I  would however appreciate if the name of
>>> Section 4.3.3
>>> > is changed
>>> > From:
>>> > 4.3.3 Traffic Handling Directives
>>> > INTO:
>>> > 4.3.3 QSPEC control information
>>>
>>> The updated QSPEC parameter terminology/semantics are as
>>suggested by
>>> Dave Oran (see slides presented at IETF-67
>>> http://www3.ietf.org/proceedings/06nov/index.html).  I think the
>>> current terminology is more clear/descriptive of the QSPEC
>>parameters
>>> so I don't favor going backwards to less clear terminology.  I was
>>> never clear on why we used the 'control information' terminology in
>>> the first place, e.g., I don't think it's a very good descriptor of
>>> the 'excess treatment' parameter.
>>>
>>> Perhaps Dave can comment on this point also when he gets a chance.
>>>
>>> > > > Comment_2:
>>> > > > -----------
>>> > > >
>>> > > > Section 6.1:
>>> > > > Please reintroduce the format that is required in order to
>>> > > specify the
>>> > > > QSPEC control information, see:
>>> > > > Section 7.1 of:
>>> > > > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
>>> > >
>>> > > Please see previous email comment on QSPEC control information.
>>> >
>>> >
>>> > Georgios: If you rename section 4.3.3 to QSPEC control information
>>> > then I think that reformatting of section 6.1 is not needed.
>>> > Please add the proposed sentence by Dave (but change the term
>>> > "handling directives" to "QSPEC control Information"). I am
>>> not sure
>>> > where it is better to add this sentence, maybe in Section 5.4.
>>> >
>>> > "QoSMs are free, subject to IANA registration and review rules, to
>>> > extend QSPECs by adding parameters of any of the kinds
>>supported by
>>> > the standard QSPEC. This includes traffic description parameters,
>>> > constraint parameters and QSPEC control information. QoSMs are not
>>> > permitted, however, to reinterpret or redefine the standard QSPEC
>>> > parameters specified in this document"
>>>
>>> Yes, the text suggested by Dave will be added.
>>>
>>> > > > Comment_3:
>>> > > > ----------
>>> > > > Section 4.1 :QoS Models
>>> > > > The definition of the QoS model is not complete. An important
>>> > > > sentence that was used in the previous version of the draft is
>>> > > > removed.
>>> > > > Please add the following sentence to the definition of the QoS
>>> > > > Model
>>> > > > (QOSM):
>>> > > >
>>> > > > The same as described above have to be applied in this section.
>>> > > > After the following sentence:
>>> > > >
>>> > > > "A QOSM specification MAY include the following:"
>>> > > >
>>> > > > include the following bullet:
>>> > > > "- it specifies how to use QOS NSLP to signal for this QOSM"
>>> > >
>>> > > That sentence was removed in Dave's proposed QOSM
>>> re-definition, see
>>>
>>> > > http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
>>> > > ml.  It was unclear what that sentence meant, QoS-NSLP
>>> specifies how
>>>
>>> > > to signal, not QOSM specifications, so the sentence was removed.
>>> > >
>>> > > I believe the sentence was intended to mean that when QoS NSLP
>>> > > allows various options to be selected, a QOSM should be able to
>>> > > determine which option is used.  For that purpose the following
>>> > > sentence was added in Section 4.1:
>>> > >
>>> > > "     A QOSM specification MAY include the following:
>>> > >      ...
>>> > >      - can state which QoS-NSLP options a QOSM wants to use, when
>>> > >      several options are available for a QOSM (e.g.,
>>> local QSPEC to
>>> > >      either be a) tunneled or b) encapsulate initiator QSPEC)."
>>> > >
>>> > > Also, to avoid any misinterpretation that QOSMs are free
>>> to specify
>>> > > additional constraints, state machines, protocol data,
>>> etc. for NSLP
>>>
>>> > > beyond that which is specific in the QoS NSLP specification, the
>>> > > following was added to Section 4.1:
>>> > >
>>> > > "  QOSMs affect the operation of the RMF in NSIS-capable
>>> nodes, the
>>> > >    information carried in QSPEC objects, and may under some
>>> > >    circumstances (e.g. aggregation) cause a separate NSLP
>>> > >    session to be
>>> > >    instantiated by having the RMF as a QNI. QOSMs all utilize
>>> > >    the common
>>> > >    data, state machines, and APIs of the underlying NSIS
>>> > >    protocols and
>>> > >    are not expected to re-define or extend these in any way."
>>> >
>>> > Georgios:
>>> > Regarding the sentence in Section 4.1:
>>> > "QOSMs all utilize
>>> > the common data, state machines, and APIs of the underlying NSIS
>>> > protocols and are not expected to re-define or extend these in any
>>> > way."
>>> >
>>> > This sentence restricts the possibility of QoS model to use
>>> RMF states
>>>
>>> > and data that are not been defined in neither QoS-NSLP or QSPEC.
>>> > This sentence should be removed.
>>>
>>> I disagree.  The quoted text was introduced by Dave Oran in addition
>>> to removing the phrase implying that a QOSM could specify signaling
>>> protocol changes, and I agree with this.
>>> Any changes/extensions to the signaling protocol or state
>>machines are
>>> within the scope of QoS-NSLP draft and not the QSPEC draft or a QOSM
>>> specification draft.  I think you have noted that also in your
>>> subsequent posting at
>>> http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html.
>>>
>>> If any extensions are required to the NSIS signaling protocol as a
>>> result of the 'severe change on QoS Model definition and
>>capabilities'
>>> you have noted, those proposed changes/extensions should be
>>addressed
>>> to the QoS NSLP draft IMO.
>>>
>>> Perhaps Dave can comment here also when he gets a chance.
>>>
>>> > > > Comment_4:
>>> > > > -------------
>>> > > > Section 5.1 Local QSPEC definition and processing
>>> > > >
>>> > > > By reading this section it gives the impression that the two
>>> > > > methods
>>> > > > a) and b) cannot be used by the same QoS model.
>>> > > > Method a): translate the
>>> > > > initiator QSPEC into a local QSPEC and encapsulate the
>>> initiator
>>> > > > QSPEC in the RESERVE message Method b): b) tunnel the
>>initiator
>>> > > > QSPEC through the local domain and reserve resources by
>>> generating
>>>
>>> > > > a new RESERVE message through the local domain containing the
>>> > > > local QSPEC.
>>> > > >
>>> > > > Note that according to the discussions that we have had
>>> until now
>>> > > > method a) should be able to be used in combination with
>>> method b)
>>> > > > by the same QoS model for the situation that the local QSPEC
>>> > > > encapsulates the initiator QSPEC in order to satisfy
>>requirement
>>> > > > 5.4.2 that is specified in RFC 3726, see:
>>> > > > http://www.ietf.org/rfc/rfc3726.txt
>>> > > >
>>> > > > Please add the following sentence at the end of the first
>>> > > > paragraph of Section 5.1.
>>> > > > "Note that when method b) is used, the encapsulation of the
>>> > > > initiator QSPEC into a local QSPEC should also be
>>possible when
>>> > > > the local QoS model needs to satisfy Requirement
>>> > > > 5.4.2 specified in RFC 3726, by adding and removing local
>>> > > > QOSM-specific Control Information parameters on top of the
>>> > > > initiator QSPEC."
>>> > >
>>> > > Your comment here is not clear to me.  It would help to
>>> provide an
>>> > > example to illustrate what you are trying to accomplish.
>>> It seems
>>> > > that you are trying to specify QoS-NSLP functionality,
>>> rather than
>>> > > QSPEC functionality.  If so, that functionality should be
>>> specified
>>> > > in the QoS-NSLP draft rather than the QSPEC draft, perhaps the
>>> > > QoS-NSLP authors can comment.
>>> >
>>> > Georgios:
>>> > No I am not trying to define QOS-NSLP functionality.
>>> > This is related to QSPEC control information that has to be
>>> carried by
>>>
>>> > end-to-end messages.
>>> > What I am trying to say is that all the discussion that we
>>have had
>>> > regarding the encapsulation of the QSPEC object were
>>> associated with
>>> > requirement 5.4.2 of RFC 3726, see below:
>>> >
>>> > -----------------
>>> > "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain
>>> > Information
>>> >
>>> >    It SHOULD be possible to add and remove local scope elements.
>>> >    Compared to Requirement 5.3.5 this requirement does use
>>> the normal
>>> >    signaling process and message exchange for transporting local
>>> >    information.  For example, at the entrance to a domain, domain-
>>> >    specific information is added information is added, which
>>> >    is used in
>>> >    this domain only, and the information is removed again when a
>>> >    signaling message leaves the domain.  The motivation is in the
>>> >    economy of re-using the protocol for domain internal
>>signaling of
>>> >    various information pieces.  Where additional
>>> information is needed
>>> >    within a particular domain, it should be possible to
>>> carry this at
>>> >    the same time as the end-to-end information.", from RFC 3726
>>> > ------------------
>>> > Thus what I am saying is:
>>> > Please add the following sentence at the end of the first
>>> paragraph of
>>>
>>> > Section 5.1.
>>> >
>>> > "Note that when method b) is used, the encapsulation of the
>>> initiator
>>> > QSPEC into a local QSPEC should also be possible when the
>>local QoS
>>> > model needs to satisfy Requirement
>>> > 5.4.2 specified in RFC 3726, by adding and removing local
>>> > QOSM-specific Control Information parameters on top of the
>>> initiator
>>> > QSPEC."
>>>
>>> First, the suggested text isn't clear.  If method b) is used
>>> (tunneling) then presumably method a) is not also used at the same
>>> time.  However, the phrasing of the above makes it sound that way.
>>>
>>> Second, an example would help here.  I presume you are
>>referring e.g.,
>>> to RMD adding 'control information' (i.e., 'handling directive')
>>> parameters to the local QSPEC that are not included in the initiator
>>> QSPEC.  I think the requirement would be that the RMD QOSM
>>provides a
>>> local QSPEC that is consistent with the initiator QSPEC, as
>>we agreed
>>> on the list (see also slide 8 of the IETF-67 presentation).
>>>
>>> If the local QSPEC introduces functionality inconsistent with the
>>> initiator QSPEC by appending the handling directive parameters, then
>>> it is not allowed.
>>>
>>> > > > Comment_5:
>>> > > > -----------
>>> > > > Section 5.1, last paragraph:
>>> > > >
>>> > > > Please change the following:
>>> > > > "For example, RMD can define a local QSPEC that
>>contains TMOD =3D
>>> > > > bandwidth (sets r=3Dp, b/m to large)."
>>> > > >
>>> > > > Into:
>>> > > > "For example, in RMD the TMOD parameters contained in
>>> the original
>>>
>>> > > > initiator QSPEC are mapped into the equivalent TMOD parameter
>>> > > > representing only the peak bandwidth in the local QSPEC."
>>> > >
>>> > > OK with me.
>>> > >
>>> > > > Comment_6:
>>> > > > -------------
>>> > > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to
>>> be followed
>>> > > > regarding the QSPEC control information are not given:
>>> > > >
>>> > > > Please include the following paragraph at the end of
>>> this section:
>>> > > > "Regarding QSPEC Control Information, the default rule
>>> is that all
>>> > > >    QSPEC parameters that have been included in the RESERVE
>>> > > >    message by
>>> > > >    the QNI are also included in the RESPONSE message by the
>>> > > >    QNR with the
>>> > > >    value they had when arriving at the QNR.  When
>>> traveling in the
>>> > > >    RESPONSE message, all QSPEC Control Information
>>> parameters are
>>> > > >    read-only.  Note that a QOSM specification may
>>define its own
>>> > > >    QOSM-specific Control Information parameters and
>>> > > >    processing rules."
>>> > >
>>> > > Please see previous email comment on QSPEC control information.
>>> >
>>> > Georgios: I think that a description of how the QSPEC control
>>> > information is handled is needed.
>>>
>>> Please see above comments on 'control information' terminology.
>>>
>>> Thanks,
>>> Jerry
>>>
>>> > > > Comment_7:
>>> > > > ------------
>>> > > > Section 6.1:
>>> > > > I do not understand the second sentence from the below two
>>> > > > sentences:
>>> > > > "N Flag: Not-supported QSPEC parameter flag (see
>>Section 5.2.2).
>>> > > >            For QSPEC parameters the value of this flag
>>> is always
>>> > > > zero."
>>> > >
>>> > > Good catch, this is a typo, the sentence should be removed.
>>> > >
>>> >
>>> >
>>> > Best Regards,
>>> > Georgios
>>> >
>>>
>>> _______________________________________________
>>> nsis mailing list
>>> nsis@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/nsis
>>>
>>
>>
>>
>>_______________________________________________
>>nsis mailing list
>>nsis@ietf.org
>>https://www1.ietf.org/mailman/listinfo/nsis
>>

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



From nsis-bounces@ietf.org Sun Dec 24 03:18:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GyOYQ-0005Xd-N9; Sun, 24 Dec 2006 03:17:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GyOYP-0005XY-Rw
	for nsis@ietf.org; Sun, 24 Dec 2006 03:17:57 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GyOYM-0001xt-NC
	for nsis@ietf.org; Sun, 24 Dec 2006 03:17:57 -0500
Received: from webmail.cs.utwente.nl (janus.ewi.utwente.nl [130.89.10.26])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with SMTP id kBO8HfCJ023612;
	Sun, 24 Dec 2006 09:17:41 +0100 (MET)
Received: from 84.82.109.231 (auth. user karagian@imap2.cs.utwente.nl)
	by webmail.cs.utwente.nl with HTTP; Sun, 24 Dec 2006 08:17:41 +0000
To: "john.loughney@nokia.com" <john.loughney@nokia.com>,
	"gash@att.com" <gash@att.com>, "nsis@ietf.org" <nsis@ietf.org>
Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt
Date: Sun, 24 Dec 2006 08:17:39 +0000
X-Mailer: IlohaMail/0.8.13 (On: webmail.cs.utwente.nl)
Message-ID: <lDkLETuc.1166948259.7314610.karagian@ewi.utwente.nl>
In-Reply-To: <BAA65A575825454CBB0103267553FCCC019F091F@esebe199.NOE.Nokia.com>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Bounce-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
MIME-Version: 1.0 
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.4 () FVGT_s_OBFU_Q1,FVGT_u_HAS_2LETTERFLDR
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Sun, 24 Dec 2006 09:17:49 +0100 (MET)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 69a78ee79e7121d5e3529be34866f161
Cc: 
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

Hi John

I mainly disagree with the following three points that were never
discussed before:

Point_1):Removed the QSPEC control information
---------------------------------------------------------------
Jerry mentioned in a previous e-mail that this QSPEC control information
concept is not removed but it is renamed to Traffic Handling Directives.

If that is the case then Jerry will have to use the same definitions for
the
QSEPC control information as used in Section 5.3.1 of:
http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt

Thus my proposal is to change section 4.3.3 as given in v.13 of the QSEPC
template draft and include the general concept of the QSPEC control
information that was given in Section 5.3.1 of version 12 of the QSEPC
template draft. Note that the name can be changed but the semantics
should remain the same. Thus please chnage Section 4.3.3 as follows:

FROM:

4.3.3 Traffic Handling Directives

   The <Excess Treatment> parameter describes how the QNE will process
   excess traffic, that is, out-of-profile traffic.  Excess traffic MAY
   be dropped, shaped and/or remarked. The excess treatment parameter is
   initially set by the QNI and cannot be overwritten.


INTO:

4.3.3  Traffic Handling Directives

   Traffic Handling Directives are used for signaling QOSM RMF functions
   not defined in QoS NSLP.  It enables building new RMF functions
   required by a QOSM within a QoS NSLP signaling framework, such as
   specified, for example, in [RMD-QOSM] and [Y.1541-QOSM].

   <QSPEC Control Information> =3D <Excess Treatment>

   The <Excess Treatment> parameter describes how the QNE will process
   excess traffic, that is, out-of-profile traffic.  Excess traffic MAY
   be dropped, shaped and/or remarked. The excess treatment parameter is
   initially set by the QNI and is read-only.

-------------------------------

Point_2: dictates that encpasulation of the original initiator QSEPC
feature cannot be used in combination with the tunneling (parallel
session) feature.

In the discussion that we have had in the nsis mailing list and during
the IETF meeting it was stated that both these features should be
possible, while now version 13 of the QSPEC template draft dicates that
these two feratures cannot be used togetherand at the same time by the
same QoS model.
As I mentioned in all the discussions the encapsulation of the original
QSPEC feature is needed to satisfy Requirement:
"5.4.2.  It SHOULD be Possible to Add and Remove Local Domain
Information" given in: http://www.ietf.org/rfc/rfc3726.txt
Therefore the encapsulation (of the original initiator QSEPC into a local
QSPEC) feature should be seen as an independent feature and it should be
able to be used in combination with the tunneling (parallel session)
feature that is used for another goal.

Thius my proposal is that it should be mentioned that even when the
tunneling (parallel session) feature is used, it is also allowed to use,
at the same time, the encapsulation (of the original initiator QSEPC
into a local QSPEC) feature in order to satisfy Requirement 5.4.2 of RFC
3726.
---------------------------

Point_3: QSEPC 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 tempate draft should adpat the definitiojn 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.

Best Regards,
Georgios







On 12/23/2006, "john.loughney@nokia.com" <john.loughney@nokia.com>
wrote:

>Hi all,
>
>When Jerry posted the draft with the change log, I basically noted
>that the changes were based upon previous discussions, on the
>mailing list and the meeting.
>
>I am unsure of the techincal issues that are being raised.  Rather
>than get into a discussion of what was discussed or not, what I
>would like to understand better is more understanding what are
>the technical issues behind Georgios' issues.
>
>Additionally, I would like to hear from others about their opinions
>on this issue.
>
>thanks,
>John
>
>>-----Original Message-----
>>From: ext Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>>Sent: 22 December, 2006 20:12
>>To: Georgios Karagiannis; nsis@ietf.org
>>Cc: Ash, Gerald R (Jerry), ALABS
>>Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt
>>
>>Georgios,
>>
>>It's not true as you and 2 others have stated that the changes
>>were not discussed.  They were discussed, at length.  For
>>example, the revised definition of QOSM was clearly stated and
>>discussed on the list, see
>>http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.htm
>>l and also see all the list discussion following that post.
>>The revised definition and all the other changes were clearly
>>presented in the slides at IETF-67, see minutes and slides at
>>http://www3.ietf.org/proceedings/06nov/index.html.  You can
>>listen to the complete IETF-67 presentation/discussion again
>>at
>>http://limestone.uoregon.edu/ftp/pub/videolab/media/ietf67/ietf
>>67ch4-thu
>>-am.mp3.
>>
>>You can review the slides, meeting discussion, list
>>discussion, meeting minutes, and verify that for yourself.
>>
>>So the editors did not 'make up the changes without
>>discussion' as you and 2 others have suggested.  That is
>>certainly wrong and I think you should acknowledge that.
>>
>>It is not useful going forward to debate the past, but
>>incendiary wrong statements should not go unanswered.
>>
>>Once again, I've responded to your technical comments, you can
>>comment further if you wish.
>>
>>It would be good for others to comment on the technical points.
>>
>>Jerry
>>
>>-----Original Message-----
>>From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>>Sent: Friday, December 22, 2006 11:36 AM
>>To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>>Subject: RE: [NSIS] RE: Comments on draft-ietf-nsis-qspec-13.txt
>>
>>Hi Jerry
>>
>>The changes that are included in version 13 of the QSEPC
>>template draft regarding the QSPEC control information and the
>>limitations of the QoS models have never been discussed
>>because they were never stated clearly.
>>
>>If they would have been stated clearly then I would have sent
>>my comments at that time instead of sending them now!
>>
>>Furthermore, from what I have seen in v. 13 of the draft you
>>also have not solved the stacking issue, because you are
>>actually dictating that encapsulation cannot be combined and
>>used together with the tunneling (parallel sessions) method.
>>
>>
>>Best Regards,
>>Georgios
>>
>>>
>>>
>>>
>>> > -----Original Message-----
>>> > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>>> > Sent: vrijdag 22 december 2006 16:37
>>> > To: Georgios Karagiannis; nsis@ietf.org
>>> > Cc: Ash, Gerald R (Jerry), ALABS
>>> > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>>> >
>>> > Georgios,
>>> >
>>> > > -----Original Message-----
>>> > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>>> > > Sent: Friday, December 22, 2006 9:13 AM
>>> > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>>> > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>>> > >
>>> > > Hi Jerry
>>> > >
>>> > > By just saying that "these changes are suggested by Dave in the
>>> > > e-mail" does not work.
>>> > >
>>> > > The proposal of Dave was not clear on the QoS model changes
>>> > that you
>>> > > wanted to do.
>>> >
>>> > All changes to the draft have been extensively discussed on
>>> the list
>>> > and are all contained in the slides presented at IETF-67.
>>You were
>>> > there at
>>> > IETF-67 and participated in all the list discussion.  The
>>> summary of
>>> > changes in the slides is quite specific and clear, take
>>> another look.
>>> > Have a look at the minutes as well
>>> > http://www3.ietf.org/proceedings/06nov/minutes/nsis.txt.  The only
>>> > disagreements noted are with regard to stacking, which is an issue
>>> > that we later resolved on the list.  Go back and check it out.
>>> >
>>> > > Now I understand which changes you want to include in the QSPEC
>>> > > template draft.
>>> > > This is also the reason of disagreeing with you now and sending
>>> > > comments to the nsis list.
>>> >
>>> > I responded to your further comments, see below.  Others are
>>> > encouraged to comment as well.
>>> >
>>> > Jerry
>>> >
>>> > >
>>> > > Furthermore, note that the QOS-NSLP draft defines which
>>> > capabilities
>>> > > should be supported by the QoS models and not the QSPEC template
>>> > > draft.
>>> > >
>>> > > Best Regards,
>>> > > Georgios
>>> > >
>>> > >
>>> > > > -----Original Message-----
>>> > > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>>> > > > Sent: vrijdag 22 december 2006 15:01
>>> > > > To: Georgios Karagiannis; nsis@ietf.org
>>> > > > Cc: Ash, Gerald R (Jerry), ALABS
>>> > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>>> > > >
>>> > > > Georgios,
>>> > > >
>>> > > > See below.
>>> > > >
>>> > > > > -----Original Message-----
>>> > > > > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
>>> > > > > Sent: Thursday, December 21, 2006 9:22 AM
>>> > > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>>> > > > > Cc: 'Attila Bader (IJ/ETH)'; 'Lars Westberg'
>>> > > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>>> > > > >
>>> > > > > Hi Jerry
>>> > > > >
>>> > > > > Please see below! I have severe concerns about some changes
>>> > > > that have
>>> > > > > been done in the QSPEC template draft.
>>> > > > >
>>> > > > > > -----Original Message-----
>>> > > > > > From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>>> > > > > > Sent: woensdag 20 december 2006 14:20
>>> > > > > > To: Georgios Karagiannis; nsis@ietf.org
>>> > > > > > Cc: Ash, Gerald R (Jerry), ALABS
>>> > > > > > Subject: RE: Comments on draft-ietf-nsis-qspec-13.txt
>>> > > > > >
>>> > > > > > Hi Georgios,
>>> > > > > >
>>> > > > > > See below.
>>> > > > > >
>>> > > > > > > -----Original Message-----
>>> > > > > > > From: Georgios Karagiannis
>>[mailto:karagian@cs.utwente.nl]
>>> > > > > > > Sent: Wednesday, December 20, 2006 5:26 AM
>>> > > > > > > To: Ash, Gerald R (Jerry), ALABS; nsis@ietf.org
>>> > > > > > > Subject: Comments on draft-ietf-nsis-qspec-13.txt
>>> > > > > > >
>>> > > > > > > Hi Jerry
>>> > > > > > >
>>> > > > > > > Here are my comments on draft-ietf-nsis-qspec-13.txt:
>>> > > > > > >
>>> > > > > > > Comment_1:
>>> > > > > > > --------------
>>> > > > > > > Please reinclude the concept of QSPEC control
>>> > > > information that was
>>> > > > > > > included in all previous versions of the QSPEC
>>> > template draft.
>>> > > > > > > In
>>> > > > > > >
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt: this
>>> > > > > > > concept was described in Section 5.1.
>>> > > > > >
>>> > > > > > Please see previous email comment on QSPEC control
>>> > information.
>>> > > > >
>>> > > > > Georgios:
>>> > > > > In order to emphasize the need of having QSPEC control
>>> > > information
>>> > > > > parameters  I  would however appreciate if the name of
>>> > > > Section 4.3.3
>>> > > > > is changed
>>> > > > > From:
>>> > > > > 4.3.3 Traffic Handling Directives
>>> > > > > INTO:
>>> > > > > 4.3.3 QSPEC control information
>>> > > >
>>> > > > The updated QSPEC parameter terminology/semantics are as
>>> > suggested
>>> > > > by Dave Oran (see slides presented at IETF-67
>>> > > > http://www3.ietf.org/proceedings/06nov/index.html).  I
>>> think the
>>> > > > current terminology is more clear/descriptive of the QSPEC
>>> > > > parameters so I don't favor going backwards to less clear
>>> > > > terminology.  I was never clear on why we used the 'control
>>> > > > information' terminology in the first place, e.g., I
>>> don't think
>>> > > > it's a very good descriptor of the 'excess treatment'
>>parameter.
>>> > > >
>>> > > > Perhaps Dave can comment on this point also when he
>>> gets a chance.
>>> > > >
>>> > > > > > > Comment_2:
>>> > > > > > > -----------
>>> > > > > > >
>>> > > > > > > Section 6.1:
>>> > > > > > > Please reintroduce the format that is required
>>in order to
>>> > > > > > specify the
>>> > > > > > > QSPEC control information, see:
>>> > > > > > > Section 7.1 of:
>>> > > > > > >
>>> > > http://www.watersprings.org/pub/id/draft-ietf-nsis-qspec-12.txt
>>> > > > > >
>>> > > > > > Please see previous email comment on QSPEC control
>>> > information.
>>> > > > >
>>> > > > >
>>> > > > > Georgios: If you rename section 4.3.3 to QSPEC control
>>> > > information
>>> > > > > then I think that reformatting of section 6.1 is not needed.
>>> > > > > Please add the proposed sentence by Dave (but change
>>the term
>>> > > > > "handling directives" to "QSPEC control Information"). I am
>>> > > > not sure
>>> > > > > where it is better to add this sentence, maybe in
>>Section 5.4.
>>> > > > >
>>> > > > > "QoSMs are free, subject to IANA registration and review
>>> > > rules, to
>>> > > > > extend QSPECs by adding parameters of any of the kinds
>>> > > supported by
>>> > > > > the standard QSPEC. This includes traffic description
>>> > parameters,
>>> > > > > constraint parameters and QSPEC control information.
>>> > > QoSMs are not
>>> > > > > permitted, however, to reinterpret or redefine the
>>> > standard QSPEC
>>> > > > > parameters specified in this document"
>>> > > >
>>> > > > Yes, the text suggested by Dave will be added.
>>> > > >
>>> > > > > > > Comment_3:
>>> > > > > > > ----------
>>> > > > > > > Section 4.1 :QoS Models
>>> > > > > > > The definition of the QoS model is not complete. An
>>> > important
>>> > > > > > > sentence that was used in the previous version of the
>>> > > draft is
>>> > > > > > > removed.
>>> > > > > > > Please add the following sentence to the definition
>>> > > of the QoS
>>> > > > > > > Model
>>> > > > > > > (QOSM):
>>> > > > > > >
>>> > > > > > > The same as described above have to be applied in
>>> > > this section.
>>> > > > > > > After the following sentence:
>>> > > > > > >
>>> > > > > > > "A QOSM specification MAY include the following:"
>>> > > > > > >
>>> > > > > > > include the following bullet:
>>> > > > > > > "- it specifies how to use QOS NSLP to signal for
>>> this QOSM"
>>> > > > > >
>>> > > > > > That sentence was removed in Dave's proposed QOSM
>>> > > > re-definition, see
>>> > > > > >
>>> http://www1.ietf.org/mail-archive/web/nsis/current/msg07084.ht
>>> > > > > > ml.  It was unclear what that sentence meant, QoS-NSLP
>>> > > > specifies how
>>> > > > > > to signal, not QOSM specifications, so the sentence
>>> > was removed.
>>> > > > > >
>>> > > > > > I believe the sentence was intended to mean that when
>>> > QoS NSLP
>>> > > > > > allows various options to be selected, a QOSM should
>>> > be able to
>>> > > > > > determine which option is used.  For that purpose the
>>> > following
>>> > > > > > sentence was added in Section 4.1:
>>> > > > > >
>>> > > > > > "     A QOSM specification MAY include the following:
>>> > > > > >      ...
>>> > > > > >      - can state which QoS-NSLP options a QOSM wants to
>>> > > use, when
>>> > > > > >      several options are available for a QOSM (e.g.,
>>> > > > local QSPEC to
>>> > > > > >      either be a) tunneled or b) encapsulate
>>> > initiator QSPEC)."
>>> > > > > >
>>> > > > > > Also, to avoid any misinterpretation that QOSMs are free
>>> > > > to specify
>>> > > > > > additional constraints, state machines, protocol data,
>>> > > > etc. for NSLP
>>> > > > > > beyond that which is specific in the QoS NSLP
>>> > > specification, the
>>> > > > > > following was added to Section 4.1:
>>> > > > > >
>>> > > > > > "  QOSMs affect the operation of the RMF in NSIS-capable
>>> > > > nodes, the
>>> > > > > >    information carried in QSPEC objects, and may under some
>>> > > > > >    circumstances (e.g. aggregation) cause a separate NSLP
>>> > > > > >    session to be
>>> > > > > >    instantiated by having the RMF as a QNI. QOSMs
>>> all utilize
>>> > > > > >    the common
>>> > > > > >    data, state machines, and APIs of the underlying NSIS
>>> > > > > >    protocols and
>>> > > > > >    are not expected to re-define or extend these in
>>> any way."
>>> > > > >
>>> > > > > Georgios:
>>> > > > > Regarding the sentence in Section 4.1:
>>> > > > > "QOSMs all utilize
>>> > > > > the common data, state machines, and APIs of the
>>> > underlying NSIS
>>> > > > > protocols and are not expected to re-define or extend
>>> > > these in any
>>> > > > > way."
>>> > > > >
>>> > > > > This sentence restricts the possibility of QoS model to use
>>> > > > RMF states
>>> > > > > and data that are not been defined in neither
>>> QoS-NSLP or QSPEC.
>>> > > > > This sentence should be removed.
>>> > > >
>>> > > > I disagree.  The quoted text was introduced by Dave Oran
>>> > in addition
>>> > > > to removing the phrase implying that a QOSM could specify
>>> > signaling
>>> > > > protocol changes, and I agree with this.
>>> > > > Any changes/extensions to the signaling protocol or state
>>> > machines
>>> > > > are within the scope of QoS-NSLP draft and not the QSPEC
>>> > draft or a
>>> > > > QOSM specification draft.  I think you have noted that
>>> > also in your
>>> > > > subsequent posting at
>>> > > >
>>> http://www1.ietf.org/mail-archive/web/nsis/current/msg07352.html.
>>> > > >
>>> > > > If any extensions are required to the NSIS signaling
>>> > protocol as a
>>> > > > result of the 'severe change on QoS Model definition and
>>> > > > capabilities'
>>> > > > you have noted, those proposed changes/extensions should be
>>> > > > addressed to the QoS NSLP draft IMO.
>>> > > >
>>> > > > Perhaps Dave can comment here also when he gets a chance.
>>> > > >
>>> > > > > > > Comment_4:
>>> > > > > > > -------------
>>> > > > > > > Section 5.1 Local QSPEC definition and processing
>>> > > > > > >
>>> > > > > > > By reading this section it gives the impression
>>> > that the two
>>> > > > > > > methods
>>> > > > > > > a) and b) cannot be used by the same QoS model.
>>> > > > > > > Method a): translate the
>>> > > > > > > initiator QSPEC into a local QSPEC and encapsulate the
>>> > > > initiator
>>> > > > > > > QSPEC in the RESERVE message Method b): b) tunnel the
>>> > > initiator
>>> > > > > > > QSPEC through the local domain and reserve resources by
>>> > > > generating
>>> > > > > > > a new RESERVE message through the local domain
>>> > containing the
>>> > > > > > > local QSPEC.
>>> > > > > > >
>>> > > > > > > Note that according to the discussions that we have had
>>> > > > until now
>>> > > > > > > method a) should be able to be used in combination with
>>> > > > method b)
>>> > > > > > > by the same QoS model for the situation that the
>>> > local QSPEC
>>> > > > > > > encapsulates the initiator QSPEC in order to satisfy
>>> > > > requirement
>>> > > > > > > 5.4.2 that is specified in RFC 3726, see:
>>> > > > > > > http://www.ietf.org/rfc/rfc3726.txt
>>> > > > > > >
>>> > > > > > > Please add the following sentence at the end of
>>the first
>>> > > > > > > paragraph of Section 5.1.
>>> > > > > > > "Note that when method b) is used, the
>>> encapsulation of the
>>> > > > > > > initiator QSPEC into a local QSPEC should also be
>>> > > possible when
>>> > > > > > > the local QoS model needs to satisfy Requirement
>>> > > > > > > 5.4.2 specified in RFC 3726, by adding and
>>removing local
>>> > > > > > > QOSM-specific Control Information parameters on
>>> top of the
>>> > > > > > > initiator QSPEC."
>>> > > > > >
>>> > > > > > Your comment here is not clear to me.  It would help to
>>> > > > provide an
>>> > > > > > example to illustrate what you are trying to accomplish.
>>> > > > It seems
>>> > > > > > that you are trying to specify QoS-NSLP functionality,
>>> > > > rather than
>>> > > > > > QSPEC functionality.  If so, that functionality should be
>>> > > > specified
>>> > > > > > in the QoS-NSLP draft rather than the QSPEC draft,
>>> > perhaps the
>>> > > > > > QoS-NSLP authors can comment.
>>> > > > >
>>> > > > > Georgios:
>>> > > > > No I am not trying to define QOS-NSLP functionality.
>>> > > > > This is related to QSPEC control information that has to be
>>> > > > carried by
>>> > > > > end-to-end messages.
>>> > > > > What I am trying to say is that all the discussion that
>>> > > we have had
>>> > > > > regarding the encapsulation of the QSPEC object were
>>> > > > associated with
>>> > > > > requirement 5.4.2 of RFC 3726, see below:
>>> > > > >
>>> > > > > -----------------
>>> > > > > "5.4.2.  It SHOULD be Possible to Add and Remove
>>Local Domain
>>> > > > > Information
>>> > > > >
>>> > > > >    It SHOULD be possible to add and remove local
>>> scope elements.
>>> > > > >    Compared to Requirement 5.3.5 this requirement does use
>>> > > > the normal
>>> > > > >    signaling process and message exchange for
>>> transporting local
>>> > > > >    information.  For example, at the entrance to a
>>> > domain, domain-
>>> > > > >    specific information is added information is added, which
>>> > > > >    is used in
>>> > > > >    this domain only, and the information is removed
>>> again when a
>>> > > > >    signaling message leaves the domain.  The motivation
>>> > is in the
>>> > > > >    economy of re-using the protocol for domain internal
>>> > > signaling of
>>> > > > >    various information pieces.  Where additional
>>> > > > information is needed
>>> > > > >    within a particular domain, it should be possible to
>>> > > > carry this at
>>> > > > >    the same time as the end-to-end information.",
>>> from RFC 3726
>>> > > > > ------------------
>>> > > > > Thus what I am saying is:
>>> > > > > Please add the following sentence at the end of the first
>>> > > > paragraph of
>>> > > > > Section 5.1.
>>> > > > >
>>> > > > > "Note that when method b) is used, the encapsulation of the
>>> > > > initiator
>>> > > > > QSPEC into a local QSPEC should also be possible when the
>>> > > local QoS
>>> > > > > model needs to satisfy Requirement
>>> > > > > 5.4.2 specified in RFC 3726, by adding and removing local
>>> > > > > QOSM-specific Control Information parameters on top of the
>>> > > > initiator
>>> > > > > QSPEC."
>>> > > >
>>> > > > First, the suggested text isn't clear.  If method b) is used
>>> > > > (tunneling) then presumably method a) is not also used at
>>> > the same
>>> > > > time.  However, the phrasing of the above makes it
>>> sound that way.
>>> > > >
>>> > > > Second, an example would help here.  I presume you are
>>> referring
>>> > > > e.g., to RMD adding 'control information' (i.e., 'handling
>>> > > > directive') parameters to the local QSPEC that are not
>>> > included in
>>> > > > the initiator QSPEC.  I think the requirement would be
>>> > that the RMD
>>> > > > QOSM provides a local QSPEC that is consistent with the
>>> initiator
>>> > > > QSPEC, as we agreed on the list (see also slide 8 of
>>> the IETF-67
>>> > > > presentation).
>>> > > >
>>> > > > If the local QSPEC introduces functionality
>>> inconsistent with the
>>> > > > initiator QSPEC by appending the handling directive
>>> > parameters, then
>>> > > > it is not allowed.
>>> > > >
>>> > > > > > > Comment_5:
>>> > > > > > > -----------
>>> > > > > > > Section 5.1, last paragraph:
>>> > > > > > >
>>> > > > > > > Please change the following:
>>> > > > > > > "For example, RMD can define a local QSPEC that
>>> > > contains TMOD =3D
>>> > > > > > > bandwidth (sets r=3Dp, b/m to large)."
>>> > > > > > >
>>> > > > > > > Into:
>>> > > > > > > "For example, in RMD the TMOD parameters contained in
>>> > > > the original
>>> > > > > > > initiator QSPEC are mapped into the equivalent TMOD
>>> > parameter
>>> > > > > > > representing only the peak bandwidth in the local QSPEC."
>>> > > > > >
>>> > > > > > OK with me.
>>> > > > > >
>>> > > > > > > Comment_6:
>>> > > > > > > -------------
>>> > > > > > > In Section 5.3.1, 5.3.2, 5.3.3 the rules that have to
>>> > > > be followed
>>> > > > > > > regarding the QSPEC control information are not given:
>>> > > > > > >
>>> > > > > > > Please include the following paragraph at the end of
>>> > > > this section:
>>> > > > > > > "Regarding QSPEC Control Information, the default rule
>>> > > > is that all
>>> > > > > > >    QSPEC parameters that have been included in
>>> the RESERVE
>>> > > > > > >    message by
>>> > > > > > >    the QNI are also included in the RESPONSE
>>> message by the
>>> > > > > > >    QNR with the
>>> > > > > > >    value they had when arriving at the QNR.  When
>>> > > > traveling in the
>>> > > > > > >    RESPONSE message, all QSPEC Control Information
>>> > > > parameters are
>>> > > > > > >    read-only.  Note that a QOSM specification may
>>> > > define its own
>>> > > > > > >    QOSM-specific Control Information parameters and
>>> > > > > > >    processing rules."
>>> > > > > >
>>> > > > > > Please see previous email comment on QSPEC control
>>> > information.
>>> > > > >
>>> > > > > Georgios: I think that a description of how the
>>QSPEC control
>>> > > > > information is handled is needed.
>>> > > >
>>> > > > Please see above comments on 'control information' terminology.
>>> > > >
>>> > > > Thanks,
>>> > > > Jerry
>>> > > >
>>> > > > > > > Comment_7:
>>> > > > > > > ------------
>>> > > > > > > Section 6.1:
>>> > > > > > > I do not understand the second sentence from the
>>below two
>>> > > > > > > sentences:
>>> > > > > > > "N Flag: Not-supported QSPEC parameter flag (see
>>> > > Section 5.2.2).
>>> > > > > > >            For QSPEC parameters the value of this flag
>>> > > > is always
>>> > > > > > > zero."
>>> > > > > >
>>> > > > > > Good catch, this is a typo, the sentence should be removed.
>>> > > > > >
>>> > > > >
>>> > > > >
>>> > > > > Best Regards,
>>> > > > > Georgios
>>> > > > >
>>> > > >
>>> > >
>>> > >
>>> > >
>>> >
>>>
>>>
>>>
>>> _______________________________________________
>>> nsis mailing list
>>> nsis@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/nsis
>>>
>>
>>
>>
>>_______________________________________________
>>nsis mailing list
>>nsis@ietf.org
>>https://www1.ietf.org/mailman/listinfo/nsis
>>

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



From nsis-bounces@ietf.org Thu Dec 28 15:44:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H026N-0005fI-7J; Thu, 28 Dec 2006 15:43:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H026M-0005fB-83
	for nsis@ietf.org; Thu, 28 Dec 2006 15:43:46 -0500
Received: from mo-p00-ob.rzone.de ([81.169.146.162])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H026K-0000s3-QC
	for nsis@ietf.org; Thu, 28 Dec 2006 15:43:46 -0500
Received: from [192.168.178.33] (p5484C24D.dip0.t-ipconnect.de [84.132.194.77])
	by post.webmailer.de (mrclete mo48) (RZmta 3.11)	with ESMTP
	id iBSEcuXv002c8I;	Thu, 28 Dec 2006 21:43:00 +0100 (MET)
Date: Thu, 28 Dec 2006 21:43:00 +0100 (MET)
Message-ID: <45942BB8.1030700@cs.uni-goettingen.de>
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: nsis@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RZG-AUTH: gNvC5ZWVA5d1mEPfeXALj6w=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: fu@cs.uni-goettingen.de, Hannes.Tschofenig@siemens.com
Subject: [NSIS] Update draft "QoS NSLP State Machine"
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

Hi all,

a new version of the "QoS NSLP State Machine" draft is available.

http://www.ietf.org/internet-drafts/draft-fu-nsis-qos-nslp-statemachine-05.pdf
http://www.ietf.org/internet-drafts/draft-fu-nsis-qos-nslp-statemachine-05.txt

The important changes are:

    * combination of ST_WR2 and ST_INST to ST_INST. The FSM has 3 instead of 4 states now.
    * explaining text on FSM execution, timers and every function added.


Comments are welcome.

Bernd






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



