IETF Logo Mail Archive

RE: ISMS working group and charter problems

"Thomas Gal" <thomas.gal@triagewireless.com> Tue, 06 September 2005 22:06 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EClag-0000aK-DT; Tue, 06 Sep 2005 18:06:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EClae-0000Zt-OT for ietf@megatron.ietf.org; Tue, 06 Sep 2005 18:06:52 -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 SAA03802 for <ietf@ietf.org>; Tue, 6 Sep 2005 18:06:50 -0400 (EDT)
Message-Id: <200509062206.SAA03802@ietf.org>
Received: from epsilon.postal.redwire.net ([64.186.240.40]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1ECldf-00054C-EM for ietf@ietf.org; Tue, 06 Sep 2005 18:10:02 -0400
Received: (qmail 30782 invoked from network); 6 Sep 2005 14:59:46 -0700
Received: from c-064-186-224-138.sd2.redwire.net (HELO horatio) (tom.gal@64.186.224.138) by smtp.redwire.net with SMTP; 6 Sep 2005 14:59:46 -0700
From: Thomas Gal <thomas.gal@triagewireless.com>
To: 'Iljitsch van Beijnum' <iljitsch@muada.com>, 'Eliot Lear' <lear@cisco.com>
Date: Tue, 06 Sep 2005 15:00:01 -0700
Organization: Triage Wireless
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <CBB3A9E7-295F-461F-8627-2DD6EDA85769@muada.com>
Thread-Index: AcWzKTe7qLnY6pmqR62q5yagPnqbhAAA6UjQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
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
Reply-To: tom@triagewireless.com
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

>> 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).

Perhaps then it's time we consider mandating a "NAT-Traversal" section to
standards track documents much like IANA and Security considerations have
become common place to this day. Anything that's not covered by the BEHAVE
work already done should be covered there, as the IETF seems to have indeed
accepted the proliferation and widespread acceptance of NAT functionality.

-Tom


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

v2.23.0 | Report a Bug | By Email