Re: [tcpm] sequence number validation?

Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Wed, 13 August 2014 07:37 UTC

Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D56F1A7023 for <tcpm@ietfa.amsl.com>; Wed, 13 Aug 2014 00:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.556
X-Spam-Level: *
X-Spam-Status: No, score=1.556 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x63kyERHJi_2 for <tcpm@ietfa.amsl.com>; Wed, 13 Aug 2014 00:37:36 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41F3F1A7022 for <tcpm@ietf.org>; Wed, 13 Aug 2014 00:37:34 -0700 (PDT)
Received: from mail-lb0-f173.google.com (mail-lb0-f173.google.com [209.85.217.173]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id D04482780CD for <tcpm@ietf.org>; Wed, 13 Aug 2014 16:37:29 +0900 (JST)
Received: by mail-lb0-f173.google.com with SMTP id u10so5986185lbd.4 for <tcpm@ietf.org>; Wed, 13 Aug 2014 00:37:26 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.157.132 with SMTP id wm4mr811214lbb.89.1407915446889; Wed, 13 Aug 2014 00:37:26 -0700 (PDT)
Received: by 10.114.160.145 with HTTP; Wed, 13 Aug 2014 00:37:26 -0700 (PDT)
In-Reply-To: <53EA111D.9040106@mti-systems.com>
References: <53EA111D.9040106@mti-systems.com>
Date: Wed, 13 Aug 2014 00:37:26 -0700
Message-ID: <CAO249yddsvO=f_UghNyG=2bVHvP9_7K=w912Pu3Nmga1GZ9cdQ@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Wesley Eddy <wes@mti-systems.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/tcpm/aMrw6RWkFUwuvBHJBwjAvKxlMp0
Cc: "tcpm@ietf.org" <tcpm@ietf.org>
Subject: Re: [tcpm] sequence number validation?
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 13 Aug 2014 07:37:37 -0000

Hi Wes,
I agree the problem described in the draft,
However, I'm not very sure we can take care of it quickly.
There seems to be some solutions in the wild as the problem has
existed for long time.

If this draft will be incorporated into 793bis work, it should be a
single solution.
I think we should check other existing solutions (at least major OSs)
to see if there's any differences or conflicts.
Also, I would like to know if the solution in the draft have some
implementation experiences.

Thanks,
--
Yoshi

On Tue, Aug 12, 2014 at 6:05 AM, Wesley Eddy <wes@mti-systems.com> wrote:
> I'm curious about the working group status of:
> http://tools.ietf.org/html/draft-gont-tcpm-tcp-seq-validation-01
>
> It seems quite obvious to me that it should be adopted.
>
> Since this should be fairly quick to take care of, and is one
> of the open issues with RFC 793, I'd like to see it adopted,
> finished off relatively quickly, and then incorporated into the
> 793bis work.
>
> To that end, I'll happily contribute reviews or any other support
> needed.
>
> --
> Wes Eddy
> MTI Systems
>
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm