Re: [QOS_INBAND] next steps?

Lars Eggert <lars.eggert@nokia.com> Wed, 31 January 2007 10:25 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCCes-0002aT-Rv; Wed, 31 Jan 2007 05:25:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCCeq-0002aN-Tv for qos_inband@ietf.org; Wed, 31 Jan 2007 05:25:40 -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 1HCCep-0001fN-G8 for qos_inband@ietf.org; Wed, 31 Jan 2007 05:25:40 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l0VAN19p032538; Wed, 31 Jan 2007 12:23:24 +0200
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 Jan 2007 12:25:02 +0200
Received: from [192.168.1.33] ([10.162.252.246]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 31 Jan 2007 12:25:02 +0200
In-Reply-To: <070d01c744e3$4de7f2a0$6501a8c0@eng17>
References: <1A5D7A2D-51A2-46FF-A7EC-4B1CBE28E506@nokia.com> <070d01c744e3$4de7f2a0$6501a8c0@eng17>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <F341B66C-DEA7-4DF5-8F0A-73029C0CC346@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [QOS_INBAND] next steps?
Date: Wed, 31 Jan 2007 12:25:13 +0200
To: ext John Harper <john@anagran.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 31 Jan 2007 10:25:02.0135 (UTC) FILETIME=[11182C70:01C74522]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: qos_inband@ietf.org
X-BeenThere: qos_inband@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of in-band methods for Quality-of-service signaling <qos_inband.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/qos_inband>, <mailto:qos_inband-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/qos_inband>
List-Post: <mailto:qos_inband@ietf.org>
List-Help: <mailto:qos_inband-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/qos_inband>, <mailto:qos_inband-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1292497043=="
Errors-To: qos_inband-bounces@ietf.org

Hi,

On 2007-1-31, at 4:55, ext John Harper wrote:
> When we discussed this in San Diego, I believe the agreement was  
> that some
> time would be scheduled in NSIS to look at the requirements for  
> this work,
> and I was about to get in touch with John Loughney to ask about  
> this when I
> got your mail.

that seems reasonable. NSIS is currently somewhat busy with their  
existing documents, so an alternative may be to schedule some time in  
a different meeting.

> In the meantime I also learned about the work on TCP QuickStart  
> which I
> guess must also be under your directorship. From a requirements  
> point of
> view, at least as far as TCP-based applications are concerned,  
> there is a
> great deal of similarity between these two topics. It would seem to  
> make
> sense, given the effort that has already gone into QuickStart, to  
> address
> this further. How would you advise that this should be addressed?

In my view, QuickStart has a much narrower scope that the QoS-inband  
proposal - there is no quality-of-service reservations or  
negotiations with QS, it simply enabled flows to more efficiently  
ramp up to consume currently idle path capacity. I agree that the of  
an IP option is similar, but the mechanisms surrounding QS seem much  
simpler.

Lars


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