IETF Logo Mail Archive

Re: [tcpm] Please read

"Caitlin Bestler" <Caitlin.Bestler@neterion.com> Thu, 31 July 2008 19:12 UTC

Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C24A928C303; Thu, 31 Jul 2008 12:12:55 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19B7628C300 for <tcpm@core3.amsl.com>; Thu, 31 Jul 2008 12:12:55 -0700 (PDT)
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 5VW+2UD8ErkD for <tcpm@core3.amsl.com>; Thu, 31 Jul 2008 12:12:49 -0700 (PDT)
Received: from owa.neterion.com (mx.neterion.com [72.1.205.142]) by core3.amsl.com (Postfix) with ESMTP id A3A0E28C303 for <tcpm@ietf.org>; Thu, 31 Jul 2008 12:12:49 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 31 Jul 2008 15:13:06 -0400
Message-ID: <78C9135A3D2ECE4B8162EBDCE82CAD7704041514@nekter>
In-Reply-To: <4891FB44.50704@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] Please read
Thread-Index: AcjzNe3fYDEP7eyjQ2iaMYdiBM+z+wACx+Dg
References: <4891FB44.50704@cisco.com>
From: Caitlin Bestler <Caitlin.Bestler@neterion.com>
To: Mahesh Jethanandani <mahesh@cisco.com>, tcpm@ietf.org
Subject: Re: [tcpm] Please read
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Is an RFC really needed?

I've always assumed that the application layer MAY
do pretty much whatever it wants. Further application
layer servers SHOULD protect their own resources against
abusive clients. Those protection mechanisms MAY include
terminating connections.

All of that is true independent of any specific method
of abusing server resources.

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

v2.23.0 | Report a Bug | By Email