Re: [tcpm] Minimum nonce length in draft-touch-tcpm-experimental-options

Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Tue, 28 February 2012 20:14 UTC

Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6E0621E805B for <tcpm@ietfa.amsl.com>; Tue, 28 Feb 2012 12:14:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.474
X-Spam-Level:
X-Spam-Status: No, score=-98.474 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IaelEEhAId+y for <tcpm@ietfa.amsl.com>; Tue, 28 Feb 2012 12:14:56 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) by ietfa.amsl.com (Postfix) with ESMTP id 3C44921E8051 for <tcpm@ietf.org>; Tue, 28 Feb 2012 12:14:56 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 8C9BD2780B8 for <tcpm@ietf.org>; Wed, 29 Feb 2012 05:14:52 +0900 (JST)
Received: by eeke51 with SMTP id e51so1412104eek.31 for <tcpm@ietf.org>; Tue, 28 Feb 2012 12:14:50 -0800 (PST)
Received-SPF: pass (google.com: domain of nishida@sfc.wide.ad.jp designates 10.112.25.40 as permitted sender) client-ip=10.112.25.40;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of nishida@sfc.wide.ad.jp designates 10.112.25.40 as permitted sender) smtp.mail=nishida@sfc.wide.ad.jp
Received: from mr.google.com ([10.112.25.40]) by 10.112.25.40 with SMTP id z8mr2402920lbf.11.1330460090078 (num_hops = 1); Tue, 28 Feb 2012 12:14:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.25.40 with SMTP id z8mr1963593lbf.11.1330460090061; Tue, 28 Feb 2012 12:14:50 -0800 (PST)
Received: by 10.112.94.43 with HTTP; Tue, 28 Feb 2012 12:14:50 -0800 (PST)
In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C06C80E75@SLFSNX.rcs.alcatel-research.de>
References: <133D9897FB9C5E4E9DF2779DC91E947C06C80E75@SLFSNX.rcs.alcatel-research.de>
Date: Tue, 28 Feb 2012 12:14:50 -0800
Message-ID: <CAO249ycxh75VETJ6jYScpw-ChCi9As6x6x35RnXHKWY1TVEkYw@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: tcpm@ietf.org, Joe Touch <touch@isi.edu>
Subject: Re: [tcpm] Minimum nonce length in draft-touch-tcpm-experimental-options
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 28 Feb 2012 20:14:56 -0000

Hi,

On Mon, Feb 20, 2012 at 3:34 AM, SCHARF, Michael
<Michael.Scharf@alcatel-lucent.com> wrote:
> Joe,
>
> The wording on the nonce length in draft-touch-tcpm-experimental-options
> may be a little bit unclear ("it MAY be as few as 16 bits if desired").
>
> Does that statement intend to say something like "MUST NOT be shorter
> than 16 bits long"? Or shall even a nonce of length 0 be allowed,
> provided that there are additional security mechanism such as checksums
> or digital signatures? In the latter case, existing use of the
> codepoints without nonce could be compliant to the recommendation,
> provided that there are other means to detect false positives.

I don't have strong opinion on this yet, but I personally think we
don't have to mention minimum length specifically in the draft.
However, I might prefer to put a little bit more stress in this regards, like,
   o It's implementor's responsibility to find good balance between
the overhead of magic number and the overhead to handle false
positive.
   o the draft doesn't guarantee anything even if an implementor
chooses longer magic number

Thanks,
--
Yoshifumi Nishida