[6lowapp] Where does TCP not work

Cullen Jennings <fluffy@cisco.com> Sat, 31 October 2009 17:33 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: 6lowapp@core3.amsl.com
Delivered-To: 6lowapp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE4713A6935 for <6lowapp@core3.amsl.com>; Sat, 31 Oct 2009 10:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.358
X-Spam-Level:
X-Spam-Status: No, score=-110.358 tagged_above=-999 required=5 tests=[AWL=0.241, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 5OmO2KlodDb3 for <6lowapp@core3.amsl.com>; Sat, 31 Oct 2009 10:33:12 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id CABE63A691D for <6lowapp@ietf.org>; Sat, 31 Oct 2009 10:33:11 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjgAAKoR7EqQ/uCWe2dsb2JhbACbUwEBFiQGqBaXeIQ5BA
X-IronPort-AV: E=Sophos;i="4.44,659,1249257600"; d="scan'208";a="53281438"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 31 Oct 2009 17:33:28 +0000
Received: from ams3-vpn-dhcp4750.cisco.com (ams3-vpn-dhcp4750.cisco.com [10.61.82.141]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n9VHXSjK024626 for <6lowapp@ietf.org>; Sat, 31 Oct 2009 17:33:28 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Date: Sat, 31 Oct 2009 11:33:24 -0600
Message-Id: <5A85AE5A-4C5D-4A0F-8CDF-BEB4C69FF002@cisco.com>
To: 6lowapp@ietf.org
Mime-Version: 1.0 (Apple Message framework v1076)
X-Mailer: Apple Mail (2.1076)
Subject: [6lowapp] Where does TCP not work
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowapp>
List-Post: <mailto:6lowapp@ietf.org>
List-Help: <mailto:6lowapp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Oct 2009 17:33:13 -0000

Multiple people have told me that TCP won't work on some of the types  
of networks we want to run on. Anyway I'd like to understand a bit  
more on why this is.

I could go dig a 9600 baud modem out of my closet, set the MTU at 100,  
and emulate 10% packet loss on server side and go try some things. I'm  
relatively confidently TCP, HTTP, pop, imap, SSH, and TLS will all  
work just fine.

So, what are the network conditions that we think are going to cause a  
problem for TCP? and, what might one do to make something that worked  
better than TCP in these cases.

Thanks, Cullen