IETF Logo Mail Archive

[QOS_INBAND] next steps?

Lars Eggert <lars.eggert@nokia.com> Tue, 30 January 2007 09:53 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBpfz-00011E-Iz; Tue, 30 Jan 2007 04:53:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBpfx-000118-NZ for qos_inband@ietf.org; Tue, 30 Jan 2007 04:53:17 -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 1HBpfw-0007Rn-9n for qos_inband@ietf.org; Tue, 30 Jan 2007 04:53:17 -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 l0U9oGh7013728; Tue, 30 Jan 2007 11:50:23 +0200
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 30 Jan 2007 11:52:44 +0200
Received: from [172.21.38.109] ([172.21.38.109]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 30 Jan 2007 11:52:44 +0200
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <1A5D7A2D-51A2-46FF-A7EC-4B1CBE28E506@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Date: Tue, 30 Jan 2007 11:52:55 +0200
To: qos_inband@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 30 Jan 2007 09:52:44.0658 (UTC) FILETIME=[63DAE520:01C74454]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070130115023-35286BB0-16444927/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc:
Subject: [QOS_INBAND] next steps?
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="===============1029887860=="
Errors-To: qos_inband-bounces@ietf.org

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

v2.23.0 | Report a Bug | By Email