Re: [tcpm] poll for adopting draft-gont-tcp-security

Joe Touch <touch@ISI.EDU> Sat, 04 July 2009 06:09 UTC

Return-Path: <touch@ISI.EDU>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D25893A6931 for <tcpm@core3.amsl.com>; Fri, 3 Jul 2009 23:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.482
X-Spam-Level:
X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599]
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 jqYLsZmPUQb9 for <tcpm@core3.amsl.com>; Fri, 3 Jul 2009 23:09:15 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 6DB823A6B8E for <tcpm@ietf.org>; Fri, 3 Jul 2009 23:09:06 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-105-84-152.lsanca.dsl-w.verizon.net [71.105.84.152]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n64684VT029550; Fri, 3 Jul 2009 23:08:05 -0700 (PDT)
Message-ID: <4A4EF1C4.50305@isi.edu>
Date: Fri, 03 Jul 2009 23:08:04 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Lloyd Wood <L.Wood@surrey.ac.uk>
References: <C304DB494AC0C04C87C6A6E2FF5603DB2217B28763@NDJSSCC01.ndc.nasa.gov> <fc0ff13d0906241711k44de4f77u8ec825e1ea151a1e@mail.gmail.com> <4A4317ED.1040905@gont.com.ar> <4A48F60A.7020602@gmail.com> <4A49CA1A.6060702@gont.com.ar> <4A4A2A73.0@isi.edu> <C304DB494AC0C04C87C6A6E2FF5603DB2217BA03DF@NDJSSCC01.ndc.nasa.gov> <4A4A3F1F.1060904@isi.edu> <4A4A56F5.30806@gont.com.ar> <4A4A5A23.1010009@isi.edu> <D04557F4-BEAF-4885-AF33-D9643AF5D049@surrey.ac.uk> <4A4EA787.4090004@isi.edu> <528F1AE1-67BC-42EA-AFF7-44A231970342@surrey.ac.uk>
In-Reply-To: <528F1AE1-67BC-42EA-AFF7-44A231970342@surrey.ac.uk>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm Extensions WG <tcpm@ietf.org>
Subject: Re: [tcpm] poll for adopting draft-gont-tcp-security
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jul 2009 06:09:15 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Lloyd Wood wrote:
> On 4 Jul 2009, at 01:51, Joe Touch wrote:
>> Lloyd Wood wrote:
>>>
>>> On 30 Jun 2009, at 19:32, Joe Touch wrote:
>>>>
>>>> I've repeatedly said why I don't want to proceed on this path. It puts
>>>> the WG in the position of repeating ourselves on issues we've already
>>>> decided. Specific example - ICMP in-window checking. We acknowledge
>>>> systems do this,
>>>
>>> where is it acknowledged?
>>
>> In Gont's ID.
> 
> What, in the same individual ID you're spending so much energy suggesting
> shouldn't even exist, and which you're dismissing as implementation advice
> outside of the scope of the IETF and have otherwise been trying to prevent
> being adopted as a WG draft?

draft-ietf-tcpm-icmp-attacks, not this one.

> How can this be the WG repeating itself on a decided issue, if the WG
> has not
> yet acknowledged this in a WG document in the first place?

The WG acknowledged the icmp-attacks ID, not this one.

> Obviously, it would be entirely unreasonable for someone to argue against
> this document's adoption as a WG item while simultaneously using this same
> document as an example of acknowledgement of decided WG issues not written
> anywhere else, for that would be... well, hypocrisy.

If this document contained only information of decided WG issues,
including WG consensus on those issues, you would be correct. I have
pointed out several cases where that is not the case - and that has been
(and remains) my concern.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpO8cMACgkQE5f5cImnZru6LACgmnwHac9lRXPC41U4dW4j/xZo
Fe8AoJGyeHw+XvYx/ii5EvG5rCUKrkyH
=31TT
-----END PGP SIGNATURE-----