[re-ECN] BOF follow-up

Lars Eggert <lars.eggert@nokia.com> Wed, 18 November 2009 14:47 UTC

Return-Path: <lars.eggert@nokia.com>
X-Original-To: re-ecn@core3.amsl.com
Delivered-To: re-ecn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A6A73A68D1 for <re-ecn@core3.amsl.com>; Wed, 18 Nov 2009 06:47:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4RVUCT-pUDv for <re-ecn@core3.amsl.com>; Wed, 18 Nov 2009 06:47:54 -0800 (PST)
Received: from mail.fit.nokia.com (mail.fit.nokia.com [195.148.124.195]) by core3.amsl.com (Postfix) with ESMTP id 729D03A6959 for <re-ecn@ietf.org>; Wed, 18 Nov 2009 06:47:54 -0800 (PST)
Received: from [IPv6:2001:708:40:fff2:225:ff:fe45:eccf] (lars.local [IPv6:2001:708:40:fff2:225:ff:fe45:eccf] (may be forged)) (authenticated bits=0) by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id nAIEljTt036860 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <re-ecn@ietf.org>; Wed, 18 Nov 2009 16:47:45 +0200 (EET) (envelope-from lars.eggert@nokia.com)
From: Lars Eggert <lars.eggert@nokia.com>
Content-Type: multipart/signed; boundary=Apple-Mail-64--1071892902; protocol="application/pkcs7-signature"; micalg=sha1
Date: Wed, 18 Nov 2009 16:47:44 +0200
Message-Id: <2DA39553-18E7-443A-BD4C-413E3B6C814F@nokia.com>
To: "re-ecn@ietf.org list" <re-ecn@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1077)
X-Mailer: Apple Mail (2.1077)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (mail.fit.nokia.com [IPv6:2001:708:40:fff1::1]); Wed, 18 Nov 2009 16:47:45 +0200 (EET)
Subject: [re-ECN] BOF follow-up
X-BeenThere: re-ecn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: re-inserted explicit congestion notification <re-ecn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/re-ecn>, <mailto:re-ecn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/re-ecn>
List-Post: <mailto:re-ecn@ietf.org>
List-Help: <mailto:re-ecn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/re-ecn>, <mailto:re-ecn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2009 14:47:55 -0000

Hi,

I wanted to send a quick follow-up now that the BOF has happened, to let you all know where I think we are.

My take-away was that the BOF went rather well, considering that the topic is complex and has many architectural implications. It seemed that many folks thought that the problem space was important, and that the IETF should begin some work here.

The discussion of Re-ECN as one possible example for how a solution in this space could look like sidetracked for a bit, because people needed to ask clarification questions about  the proposal, and then tried to understand in more detail all the different aspects of the proposal. (Which I also took as an indication of interest in the problem, although we did probably spend more time here than planned.)

The strongest impression I came away with from the BOF is that there is significant interest and energy in the community, but that we need more time to discuss and work through exactly what problems we'd try to solve, before it'll be productive to spent a lot of time on specific solution proposals.

This discussion can obviously happen on a mailing list, but because CONEX is complex and architectural, I could also see us starting a WG here to provide a forum for this (preparatory) discussion, rather than as a vessel for working out the details of a solution. Having another BOF isn't quite the right thing to do IMO, because we're not at a stage where just a few kinks need to be worked out to start working on a solution.

For now, while we work out what we want to do, I'd like to ask the BOF chairs (Leslie and Phil) to continue to lead the discussion.

Lars

PS: We may want to think about starting a CONEX mailing list - several folks have indicated to me that they thought that CONEX was about standardizing Re-ECN, because of which mailing list was used for the BOF.