Re: [Tsvwg] Suggestion for Transport Area Working Group (tsvwg)

"James M. Polk" <jmpolk@cisco.com> Thu, 28 May 2009 19:26 UTC

Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 381633A6E80 for <tsvwg@core3.amsl.com>; Thu, 28 May 2009 12:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.513
X-Spam-Level:
X-Spam-Status: No, score=-6.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 c6w-rlpjkQJ6 for <tsvwg@core3.amsl.com>; Thu, 28 May 2009 12:26:47 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id CDD5B3A6D89 for <tsvwg@ietf.org>; Thu, 28 May 2009 12:26:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,267,1241395200"; d="scan'208";a="170117384"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-2.cisco.com with ESMTP; 28 May 2009 19:28:07 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n4SJS7vu008276; Thu, 28 May 2009 12:28:07 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id n4SJS7hj017877; Thu, 28 May 2009 19:28:07 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 May 2009 12:28:06 -0700
Received: from jmpolk-wxp01.cisco.com ([10.89.9.105]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 28 May 2009 12:28:06 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 28 May 2009 14:28:05 -0500
To: tim robertson <tim987@email.com>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <20090528053426.B7B1010603@ws1-3.us4.outblaze.com>
References: <20090528053426.B7B1010603@ws1-3.us4.outblaze.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID: <XFE-SJC-211JlHr3Oud0000b05b@xfe-sjc-211.amer.cisco.com>
X-OriginalArrivalTime: 28 May 2009 19:28:06.0591 (UTC) FILETIME=[6D3D94F0:01C9DFCA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2001; t=1243538887; x=1244402887; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jmpolk@cisco.com; z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com> |Subject:=20Re=3A=20[Tsvwg]=20Suggestion=20for=20Transport= 20Area=20Working=20Group=20(tsvwg) |Sender:=20; bh=LeNYutieBpAtKcTipeaz1KRHU4Vvd68kChMEOzvomao=; b=jKt6FyE3La0LqfAC6auWS29FWhQ4VET55rn3gTzdp4Rp0DVKFjaUoBUIFR XFJXby5kB76AueJk8hW6PjX9pwmr60nmXizLk4FqEFdjHXRYP9E/+dk0ygVr buRS7cgq6Q;
Authentication-Results: sj-dkim-4; header.From=jmpolk@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Cc: tsvwg@ietf.org
Subject: Re: [Tsvwg] Suggestion for Transport Area Working Group (tsvwg)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 28 May 2009 19:26:54 -0000

Tim

I believe this WG isn't the right place to discuss TCP anymore. We 
split off the TCP aspects of our WG into a new WG a couple of years 
ago, called TCPM (TCP Maintenance). Here is their charter page:
http://www.ietf.org/html.charters/tcpm-charter.html

That said, and the TCPM WG chairs can correct me, but I think what 
you're really getting at is a policy issue, not a protocol issue. 
Therefore, perhaps this idea of yours ought to be taken to the 
TSVAREA WG, for a more generalized - yet still Transport specific - 
discussion. Here is how to subscribe to that WG:
http://www.ietf.org/mailman/listinfo/tsv-area
here is the mailing list archive:
http://www.ietf.org/pipermail/tsv-area/

If that is not the right venue, you might want to address the IETF 
audience in whole, by either sending this message to the IETF.ORG 
mailing list (for all the IETF to see -- subscribe by sending a 
"subscribe" in the message body - directed at <ietf@ietf.org>), or 
speak at the microphone during one of the open plenaries during an 
IETF conference. The next conference is in Stockholm in July, 
followed by Hiroshima in November, followed by Anaheim in March 2010.

James
TSVWG WG chair

At 12:34 AM 5/28/2009, tim robertson wrote:
>Hi, I have a suggestion for the Transport Area Working Group 
>(tsvwg). You should make TCP censorship free. By that I mean isp's 
>shouldn't be able to block websites by using blacklists, url 
>blocking, ip address block, dns, keyword block etc. For example, in 
>China, some perfectly legal websites like wikipedia are blocked, so 
>that is why TCP should be changed so isp's cannot block websites. So 
>you may have to work with operating system makers and router makers 
>to update their software, but it should be backwards compatible too.
>
>Can you pass on my suggestion?
>Thanks
>
>--
>Be Yourself @ mail.com!
>Choose From 200+ Email Addresses
>Get a Free Account at <http://www.mail.com/Product.aspx>www.mail.com!