IETF Logo Mail Archive

Re: [EME] Relationship betwen

Lars Eggert <lars.eggert@netlab.nec.de> Tue, 21 November 2006 13:58 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GmW8Y-0006tB-46; Tue, 21 Nov 2006 08:58:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GmRh6-000646-WF for eme@irtf.org; Tue, 21 Nov 2006 04:13:33 -0500
Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmRh5-0002Yr-Fi for eme@irtf.org; Tue, 21 Nov 2006 04:13:32 -0500
Received: from net-32.nrpn.net (net-32.nrpn.net [192.89.6.32]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 840B113CF82; Tue, 21 Nov 2006 10:16:48 +0100 (CET)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by net-32.nrpn.net (Postfix) with ESMTP id 956A5297F86; Tue, 21 Nov 2006 11:13:31 +0200 (EET)
In-Reply-To: <455EDF09.6060901@wanadoo.fr>
References: <E6F7A586E0A3F94D921755964F6BE00662575C@EXCHANGE2.cs.cornell.edu> <455B48BD.5050201@isi.edu> <455B56C9.7080307@rd-iptech.com> <455B6358.4000703@isi.edu> <455C38AC.1090306@rd-iptech.com> <455CDFFF.8000500@isi.edu> <455D9BD5.7000900@wanadoo.fr> <1163775763.8736.114.camel@sioux.systems.cs.cornell.edu> <c70bc85d0611170827t36b9443fm2b5581721142b769@mail.gmail.com> <455DE7D1.6030805@isi.edu> <c70bc85d0611170940s26d906aak4241fe728be5590d@mail.gmail.com> <455DFF44.9060208@isi.edu> <1163793934.17915.52.camel@sioux.systems.cs.cornell.edu> <455E180B.4050907@isi.edu> <455EDF09.6060901@wanadoo.fr>
Mime-Version: 1.0 (Apple Message framework v752.2)
Message-Id: <5DF569C5-C806-49B6-BA75-006F3474124F@netlab.nec.de>
From: Lars Eggert <lars.eggert@netlab.nec.de>
Subject: Re: [EME] Relationship betwen
Date: Tue, 21 Nov 2006 11:13:25 +0200
To: Rémi Després <remi.despres@wanadoo.fr>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
X-Mailman-Approved-At: Tue, 21 Nov 2006 08:58:08 -0500
Cc: eme <eme@irtf.org>, Joe Touch <touch@ISI.EDU>
X-BeenThere: eme@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: end-middle-end research group <eme.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/eme>
List-Post: <mailto:eme@irtf.org>
List-Help: <mailto:eme-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0810496759=="
Errors-To: eme-bounces@irtf.org

On Nov 18, 2006, at 12:23, Rémi Després wrote:
> Joe Touch wrote
>> EME is a RG. IMO, it should definitely explore this interaction and
>> advise the IETF, which would then help set boundaries for future
>> TCPM/BEHAVE/etc. WGs. Those issues should not be driven by WGs.
>>
> I agree with Joe that IETF ongoing work should NOT restrict the  
> scope of an IRTF research group.
> Experiments, in particular with running code, may be precious input  
> to IETF.
> TCPM/BEHAVE scopes should therefore not restrict that of EME..

I don't read Joe's statement (which I agree with) to mean what you  
paraphrased it as.

But in any case, IETF WG charters cannot place restrictions on what  
EME can or cannot look at. The only potential for conflicts I can see  
is if work in EME is based on certain assumptions that are later  
invalidated by new IETF standards. It be good if such cases could be  
identified early on.

Lars


_______________________________________________
EME mailing list
EME@irtf.org
https://www1.ietf.org/mailman/listinfo/eme

v2.23.0 | Report a Bug | By Email