RE: [tcpm] Is this a problem?

"Caitlin Bestler" <Caitlin.Bestler@neterion.com> Mon, 29 October 2007 22:04 UTC

Return-path: <tcpm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImciJ-0004GR-7F; Mon, 29 Oct 2007 18:04:03 -0400
Received: from tcpm by megatron.ietf.org with local (Exim 4.43) id 1ImciI-0004G6-43 for tcpm-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 18:04:02 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImciH-0004Fu-Nx for tcpm@ietf.org; Mon, 29 Oct 2007 18:04:01 -0400
Received: from mx.neterion.com ([72.1.205.142] helo=owa.neterion.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImciH-0002u6-FE for tcpm@ietf.org; Mon, 29 Oct 2007 18:04:01 -0400
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [tcpm] Is this a problem?
Date: Mon, 29 Oct 2007 18:04:00 -0400
Message-ID: <78C9135A3D2ECE4B8162EBDCE82CAD7702765252@nekter>
In-Reply-To: <472654F9.5030308@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] Is this a problem?
Thread-Index: AcgadvbLvjljhruEQAaiZp2HBKxqhgAAGJbw
References: <472654F9.5030308@cisco.com>
From: "Caitlin Bestler" <Caitlin.Bestler@neterion.com>
To: "Mahesh Jethanandani" <mahesh@cisco.com>, <tcpm@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Cc:
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0606004907=="
Errors-To: tcpm-bounces@ietf.org

This is indeed a problem. I'm just not convinced it's a transport
problem.

 

Only the application layer has enough information to know when a
client's

behavior is abusive and/or suspicious. The transport layer should remain

militantly ignorant of these matters.

 

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