RE: ISMS working group and charter problems

"Fleischman, Eric" <eric.fleischman@boeing.com> Wed, 07 September 2005 18:33 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED4jT-0000k4-9f; Wed, 07 Sep 2005 14:33:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED4jR-0000jo-0F for ietf@megatron.ietf.org; Wed, 07 Sep 2005 14:33:13 -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 OAA07990 for <ietf@ietf.org>; Wed, 7 Sep 2005 14:33:11 -0400 (EDT)
Received: from blv-smtpout-01.boeing.com ([130.76.32.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ED4mb-0006ZO-S0 for ietf@ietf.org; Wed, 07 Sep 2005 14:36:33 -0400
Received: from stl-av-01.boeing.com ([192.76.190.6]) by blv-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id LAA16547; Wed, 7 Sep 2005 11:32:39 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id j87IWcS06658; Wed, 7 Sep 2005 13:32:38 -0500 (CDT)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Sep 2005 11:32:35 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 07 Sep 2005 11:32:34 -0700
Message-ID: <474EEBD229DF754FB83D256004D02108BBC8EE@XCH-NW-6V1.nw.nos.boeing.com>
Thread-Topic: ISMS working group and charter problems
Thread-Index: AcWzKTkqrO7TsOlZQ3K6VCx2/vcrLAAr1L3g
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>, Eliot Lear <lear@cisco.com>
X-OriginalArrivalTime: 07 Sep 2005 18:32:35.0359 (UTC) FILETIME=[8449AAF0:01C5B3DA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>
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

From: Iljitsch van Beijnum [mailto:iljitsch@muada.com] 
Sent: Tuesday, September 06, 2005 2:22 PM
To: Eliot Lear
>>> The IETF has been doing extensive work on NAT traversal, have a look

>>> and see if you can reuse some existing mechanism.

>> All mechanisms used with the possible exception of an additional SNMP

>> table will be re-used from existing IETF work (mostly SSH with help
>> from
>> the fact that it's based on TCP).

>You do realize that you import all the weaknesses of TCP then, don't  
>you?

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 mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf