RE: [QOS_INBAND] next steps?
"McGeer, Patrick C" <rick.mcgeer@hp.com> Wed, 31 January 2007 21:23 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCMvW-0002ds-M6; Wed, 31 Jan 2007 16:23:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCMvU-0002dl-WC for qos_inband@ietf.org; Wed, 31 Jan 2007 16:23:33 -0500
Received: from ccerelbas01.cce.hp.com ([161.114.21.104]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCMvJ-00052g-L1 for qos_inband@ietf.org; Wed, 31 Jan 2007 16:23:32 -0500
Received: from cceexg11.americas.cpqcorp.net (cceexg11.americas.cpqcorp.net [16.81.1.59]) by ccerelbas01.cce.hp.com (Postfix) with ESMTP id B5766346CA; Wed, 31 Jan 2007 15:23:18 -0600 (CST)
Received: from G3W0067.americas.hpqcorp.net ([16.232.1.13]) by cceexg11.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 Jan 2007 15:23:18 -0600
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: [QOS_INBAND] next steps?
Date: Wed, 31 Jan 2007 15:23:19 -0600
Message-ID: <BDA38860DCFD334EAEA905E44EE8E7EF6DD79D@G3W0067.americas.hpqcorp.net>
In-Reply-To: <45C06856.3060804@ericsson.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [QOS_INBAND] next steps?
Thread-Index: AcdFHp3rz+ruji2+QP2Bk3m94XoM3QAXmA0Q
References: <1A5D7A2D-51A2-46FF-A7EC-4B1CBE28E506@nokia.com><070d01c744e3$4de7f2a0$6501a8c0@eng17> <45C06856.3060804@ericsson.com>
From: "McGeer, Patrick C" <rick.mcgeer@hp.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, John Harper <john@anagran.com>
X-OriginalArrivalTime: 31 Jan 2007 21:23:18.0435 (UTC) FILETIME=[06B94730:01C7457E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
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>
Errors-To: qos_inband-bounces@ietf.org
Magnus, As I recall, we discussed discussing this in NSIS in Prague, and having a "bar BoF" there, in preparation for a BoF in Chicago. John Loughney was certainly agreeable to discussing this in NSIS, and a number of people at he meeting in San Diego (John Loughney and Scott Brim, in particular) strongly suggested that in addition to the steps of forming a discussion list, that we spend at least one more IETF meeting socializing the idea before pursuing a BoF, and that NSIS was the correct venue to start in because there were many others in that group interested in the same issues. Both John Harper and I are happy to do this -- while we're understandably eager to move forward, we also feel that it's extremely important to do this the right way within IETF, respecting IETF's procedures and culture, and, most important, fitting this work in the context of ongoing work within IETF. NSIS and QuickStart are two of the most prominent examples. Cheers Rick -----Original Message----- From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com] Sent: Wednesday, January 31, 2007 1:59 AM To: John Harper Cc: qos_inband@ietf.org Subject: Re: [QOS_INBAND] next steps? Hi, Some comments. John Harper skrev: > 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. I can't remember any agreement on taking work or even a requirements discussion into NSIS. Talking with the people active in that group is certainly fine. However as responsible AD for NSIS I don't want any proposals around this to be handled in NSIS. There are several reasons for this. You proposal has major impact on the infrastructure and needs to be discussed openly with good attendance of people from different fields. Thus a real BOF is needed before any real work can be taken on. Putting this discussion into NSIS would hide it from many that would need to participate in this. Secondly, NSIS should focus on resolving its own issues so that it can finish the currently ongoing work. I don't want time taken away from their agenda. My memory of the agreement was that you should update the drafts, continue build interest and set together a BOF for these topics. As we stated in San Diego you needed to get on this directly. As this hasn't happened I think you will have to focus on building some interest with key persons, maybe hold a bar-BOF to discuss things. 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 ---------------------------------------------------------------------- _______________________________________________ QOS_INBAND mailing list QOS_INBAND@ietf.org https://www1.ietf.org/mailman/listinfo/qos_inband _______________________________________________ QOS_INBAND mailing list QOS_INBAND@ietf.org https://www1.ietf.org/mailman/listinfo/qos_inband
- [QOS_INBAND] next steps? Lars Eggert
- RE: [QOS_INBAND] next steps? John Harper
- Re: [QOS_INBAND] next steps? Magnus Westerlund
- Re: [QOS_INBAND] next steps? Lars Eggert
- RE: [QOS_INBAND] next steps? McGeer, Patrick C
- Re: [QOS_INBAND] next steps? Magnus Westerlund