Re: ISMS working group and charter problems

"Spencer Dawkins" <spencer@mcsr-labs.org> Wed, 07 September 2005 20:04 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED69S-0006Vr-Kk; Wed, 07 Sep 2005 16:04:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED69Q-0006VD-5a for ietf@megatron.ietf.org; Wed, 07 Sep 2005 16:04:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15041 for <ietf@ietf.org>; Wed, 7 Sep 2005 16:04:06 -0400 (EDT)
Received: from rwcrmhc13.comcast.net ([216.148.227.118] helo=rwcrmhc12.comcast.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ED6Cc-00016n-LT for ietf@ietf.org; Wed, 07 Sep 2005 16:07:29 -0400
Received: from s73602 (unknown[65.104.224.98]) by comcast.net (rwcrmhc13) with SMTP id <2005090720034901500i7t5ne>; Wed, 7 Sep 2005 20:03:49 +0000
Message-ID: <0a0a01c5b3e7$3f86bfe0$0500a8c0@china.huawei.com>
From: Spencer Dawkins <spencer@mcsr-labs.org>
To: IETF Discussion <ietf@ietf.org>
References: <474EEBD229DF754FB83D256004D02108BBC8EE@XCH-NW-6V1.nw.nos.boeing.com>
Date: Wed, 07 Sep 2005 15:03:42 -0500
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Subject: Re: ISMS working group and charter problems
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

FWIW, the RUTS BoF in Orlando captured a decently canonical list of "why TCP 
is not the right answer for my application" points, in case anyone needs to 
look at prior art :-)

http://www.ietf.org/proceedings/98dec/43rd-ietf-98dec-142.html

Ummm, when you guys are thinking about "SNMP over bandwidth-constrained 
wireless links", I'm wondering what kind of "wireless links" you're thinking 
of - but that's gotta be off-topic for this thread.

Spencer

From: "Fleischman, Eric" <eric.fleischman@boeing.com>

This issue was discussed within the ISMS WG over a period of several
weeks. During those discussions, I tried to explain why I believe that a
UDP transport alternative for ISMS needs to be available. I offered the
following technical reasons supporting this position:
1) Our experience is that SNMP over TCP has significantly worse behavior
in bandwidth constrained environments (e.g., wireless links) and during
times of network congestion than SNMP over UDP.
2)TCP's inappropriate behavior (i.e., treating latency as congestion and
thus "backing off") in high latency environments such as across
geo-stationary satellite links.

I do not understand why the WG did not resonate with these observations,
since these are very well known issues and the technical underlying
reasons easy to understand. I can only conclude that while these issues
are very important to the deployments with which I am familiar, they are
sadly not relevant to the majority of the ISMS WG. I believe that ISMS
would be a better solution if it could operate within all envisioned
environments.

--Eric/ietf 


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