Re: [6lowapp] Where does TCP not work

"Don Sturek" <d.sturek@att.net> Tue, 03 November 2009 21:44 UTC

Return-Path: <d.sturek@att.net>
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 A325F28C0EB for <6lowapp@core3.amsl.com>; Tue, 3 Nov 2009 13:44:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.272
X-Spam-Level:
X-Spam-Status: No, score=0.272 tagged_above=-999 required=5 tests=[AWL=-0.993, BAYES_40=-0.185, MSGID_MULTIPLE_AT=1.449, UNPARSEABLE_RELAY=0.001]
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 C17FrnR1Vufn for <6lowapp@core3.amsl.com>; Tue, 3 Nov 2009 13:44:15 -0800 (PST)
Received: from n15.bullet.mail.mud.yahoo.com (n15.bullet.mail.mud.yahoo.com [68.142.206.42]) by core3.amsl.com (Postfix) with SMTP id 31E143A67E2 for <6lowapp@ietf.org>; Tue, 3 Nov 2009 13:44:12 -0800 (PST)
Received: from [68.142.200.225] by n15.bullet.mail.mud.yahoo.com with NNFMP; 03 Nov 2009 21:44:31 -0000
Received: from [68.142.201.251] by t6.bullet.mud.yahoo.com with NNFMP; 03 Nov 2009 21:44:31 -0000
Received: from [127.0.0.1] by omp412.mail.mud.yahoo.com with NNFMP; 03 Nov 2009 21:44:31 -0000
X-Yahoo-Newman-Id: 522085.33551.bm@omp412.mail.mud.yahoo.com
Received: (qmail 38014 invoked from network); 3 Nov 2009 21:44:31 -0000
Received: from adsl-69-225-120-110.dsl.sndg02.pacbell.net (d.sturek@69.225.120.110 with login) by smtp102.sbc.mail.sp1.yahoo.com with SMTP; 03 Nov 2009 13:44:30 -0800 PST
X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo-
X-YMail-OSG: ZuKRdEQVM1nTUrUt0kZbq2GYARNniuP7WHQHgLxtv3iRzK81fEKqBVX6pzddI9fY3sjVoJ9MkN3p2gHRGfzvMI6BxpTfyq9Z.Y9ad3CiaXyXXrB6EdX9eYBM4Hpnhfu6yafkUutmSiooqIAfd2eskcWYNhULxAEoG1swEoCqT7BbyQNlD0NmuLZQeSHIuMGkN3udHS9goJSiQW8MuK6Z7kO1xH4q9UUGzTawFI.WY.QvvQwg9KacvTd2.gtgefR0jwa6cGMf1nD_7AFm1mPCiymX3DW9iTD67UNt.__dZsPy5Adxiw--
X-Yahoo-Newman-Property: ymail-3
From: "Don Sturek" <d.sturek@att.net>
To: "'Lars Eggert'" <lars.eggert@nokia.com>
References: <5A85AE5A-4C5D-4A0F-8CDF-BEB4C69FF002@cisco.com> <005c01ca5a86$9a3f2ef0$cebd8cd0$@sturek@att.net> <DEF214D0-1324-493C-B855-E0A2018658A7@cisco.com> <01d801ca5c90$ba1031f0$2e3095d0$@sturek@att.net> <B3D361C4-4D1C-4985-BC7C-4A8F03204F14@nokia.com>
In-Reply-To: <B3D361C4-4D1C-4985-BC7C-4A8F03204F14@nokia.com>
Date: Tue, 3 Nov 2009 13:44:28 -0800
Message-ID: <00a801ca5cce$d1ba5b30$752f1190$@sturek@att.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcpcziBlamEVxnJ2QZSTHuFLv9zvuAAAD9gA
Content-Language: en-us
Cc: 6lowapp@ietf.org
Subject: Re: [6lowapp] Where does TCP not work
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: d.sturek@att.net
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: Tue, 03 Nov 2009 21:44:20 -0000

Hi Lars,

Yes, I would expect that someone who needs this feature will help sponsor it
via I-Ds and participation.

Could be ZigBee Smart Energy depending on how our interop is going and what
issues come up.

Don


-----Original Message-----
From: Lars Eggert [mailto:lars.eggert@nokia.com] 
Sent: Tuesday, November 03, 2009 1:39 PM
To: d.sturek@att.net
Cc: 'Cullen Jennings'; 6lowapp@ietf.org
Subject: Re: [6lowapp] Where does TCP not work

Hi,

On 2009-11-3, at 6:19, Don Sturek wrote:
> I think there is a Smart Grid bar BOF in Hiroshima.  This is  
> probably in
> response to the NIST Smart Grid roadmap and "Priority Action Plan"  
> activity
> (IETF is involved in priority action plan #1, IP for Smart Grid).   
> This
> might be the place to suggest work on this topic in the Transport  
> area.

that's a reasonable idea, but I think you've all been hanging around  
the IETF long enough to realize that any such effort will need to be  
driven by folks who want a solution. In other words, saying that "the  
TSV area should solve this" and then hoping that someone else will  
produce a solution isn't going to happen. We need the folks who need a  
solution put their cycles into designing one (in TSV, if that's where  
it'll fit, or wherever).

Lars