RE: [QOS_INBAND] next steps?

"John Harper" <john@anagran.com> Wed, 31 January 2007 02:55 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HC5dX-0002C6-Ov; Tue, 30 Jan 2007 21:55:51 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HC5dW-0002Bq-5M for qos_inband@ietf.org; Tue, 30 Jan 2007 21:55:50 -0500
Received: from elasmtp-masked.atl.sa.earthlink.net ([209.86.89.68]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HC5dU-0005F9-PC for qos_inband@ietf.org; Tue, 30 Jan 2007 21:55:50 -0500
Received: from [66.166.72.130] (helo=eng17) by elasmtp-masked.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1HC5dQ-0000aU-1t; Tue, 30 Jan 2007 21:55:44 -0500
From: John Harper <john@anagran.com>
To: 'Lars Eggert' <lars.eggert@nokia.com>, qos_inband@ietf.org
References: <1A5D7A2D-51A2-46FF-A7EC-4B1CBE28E506@nokia.com>
Subject: RE: [QOS_INBAND] next steps?
Date: Tue, 30 Jan 2007 18:55:44 -0800
Message-ID: <070d01c744e3$4de7f2a0$6501a8c0@eng17>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <1A5D7A2D-51A2-46FF-A7EC-4B1CBE28E506@nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
thread-index: AcdEVIFD1FapxDjTQY683wEZcX+3CwAjgA/g
X-ELNK-Trace: d2700a7eadf1db8bd780f4a490ca69563f9fea00a6dd62bc84aeeaa4e5a4abff021d02f71f656eea350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 66.166.72.130
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc:
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>
Errors-To: qos_inband-bounces@ietf.org

Lars,

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.

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?

Thanks,

John

> -----Original Message-----
> From: Lars Eggert [mailto:lars.eggert@nokia.com]
> Sent: Tuesday, January 30, 2007 1:53 AM
> To: qos_inband@ietf.org
> Subject: [QOS_INBAND] next steps?
> 
> Hi,
> 
> since the BOF deadline for Prague has come and gone, I'm wondering
> what the current status of the QoS-inband proposal is?
> 
> At the last IETF meeting, there was agreement that the community
> interested in this proposal would bring it to the IETF, because it
> relies on extensions to IETF protocols that we should discuss. (There
> was also a related IETF liaison statement.) After the San Diego
> meeting, there was some encouraging follow-on activity, and draft-
> harper-inband-signalling-requirements has recently been posted. What
> is the plan for next steps?
> 
> Thanks,
> Lars
> 



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