[tsvwg] draft-carlberg-tsvwg-ecn-reactions -- which WG?

ken carlberg <carlberg@g11.org.uk> Tue, 23 October 2012 13:15 UTC

Return-Path: <carlberg@g11.org.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D30921F8705 for <tsvwg@ietfa.amsl.com>; Tue, 23 Oct 2012 06:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.045
X-Spam-Level:
X-Spam-Status: No, score=-0.045 tagged_above=-999 required=5 tests=[AWL=-0.046, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XCeDR0pjftW7 for <tsvwg@ietfa.amsl.com>; Tue, 23 Oct 2012 06:15:30 -0700 (PDT)
Received: from portland.eukhosting.net (portland.ukserverhosting.net [92.48.103.133]) by ietfa.amsl.com (Postfix) with ESMTP id A8D1321F86FA for <tsvwg@ietf.org>; Tue, 23 Oct 2012 06:15:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=g11.org.uk; s=default; h=Mime-Version:To:Message-Id:Date:Subject:Content-Transfer-Encoding:Content-Type:From; bh=besAkfMnbzPsNBE9D8/QxBm6k+GaGcEzLVEzAwyrJyY=; b=L9Nkp3OGOoNdyh84eI+cNQTxfUs6lQ7xfCAivhzJ3M5OSkxvI1IXq8oudSbYa2mMtUNKQYMurUPIiwkoxOdYhqggRDs1bAKkwd3j/sC0+SmcYP35x7+AIt17IuRloNvB;
Received: from c-76-111-69-4.hsd1.va.comcast.net ([76.111.69.4]:56840 helo=[192.168.0.20]) by portland.eukhosting.net with esmtpa (Exim 4.80) (envelope-from <carlberg@g11.org.uk>) id 1TQeKK-0006ao-KH for tsvwg@ietf.org; Tue, 23 Oct 2012 13:15:24 +0000
From: ken carlberg <carlberg@g11.org.uk>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 23 Oct 2012 09:15:26 -0400
Message-Id: <EA690191-7825-4FCD-873D-3BFCFF92A59B@g11.org.uk>
To: tsvwg <tsvwg@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - portland.eukhosting.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - g11.org.uk
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: [tsvwg] draft-carlberg-tsvwg-ecn-reactions -- which WG?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 13:15:31 -0000

Hi,

I've been asked publically and privately about my thoughts as to where this document should end up -- TSVWG or RMCAT.  When the question was first brought up I was indifferent because I could see a case for both.  However, when I thought about it for a while, I felt more comfortable advancing this through TSVWG.  

The reason for this line of thoughts is that only a portion of the ECN Reactions draft deals with congestion control algorithms.  And while RMCAT talks about the generic term of "mechanisms" in its charter, the heart of the charter and deliverables seems to focus on algorithms, which is really just one type of mechanism.  On the other hand, the Reactions draft looks into other "mechanisms" like FEC, signaling, and most importantly, the impact of a set of users not responding to ECN.  And its this last item where we bring in some simulation work and is probably the strongest reason (ie, the simulation results) as to why its beneficial to have this in an IETF document.  And its these other items that seem out of scope of RMCAT.

Assuming this draft is accepted as a working group item in TSVWG, I would also want to send the document to RMCAT for review when we get to a WG last call for comments stage, though I sure the core set of folks will be attending both sets of meetings and mailing lists.

If folks feel I've missed something, please don't be shy in letting us know :-)

-ken