IETF Logo Mail Archive

Re: [tcpinc] Spencer Dawkins' Yes on draft-ietf-tcpinc-tcpcrypt-08: (with COMMENT)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 26 October 2017 18:02 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tcpinc@ietfa.amsl.com
Delivered-To: tcpinc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55CE613F5D8; Thu, 26 Oct 2017 11:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 oSvAiDmDN14C; Thu, 26 Oct 2017 11:02:48 -0700 (PDT)
Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91D4713F5D4; Thu, 26 Oct 2017 11:02:48 -0700 (PDT)
Received: by mail-yw0-x233.google.com with SMTP id q1so3661712ywh.5; Thu, 26 Oct 2017 11:02:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uymGjDK5u2iW+dXU3naXoUMhvBcNoYwTvrE2f3WFx+M=; b=HJiTdKTtS6Vo8MmNZcsifyTKfeJyX8jELXmeTasdNzVkjTAll51ekhRPysjTCNqgGd IDUf3nmSGoMbGnjPTeM47Z/1JR/S3iLobDATZV9Wtok/MWy5e8dhqFO0VOGx+IeTMD5D EItm2V5LLLkJn2kybwzZ0WchkjJIdtmSyiEmP0LanXWaUy6OO/9zqcri1kv/+5hQw+VA HIh9tawZE4UqRjuqayWJclEnvRFt9P591v/3oR4jLsssbduKh9v/hFPa6yeVzLkvTOvE Dghq3sfpPdQ0954ReuWYcyA5ODap7bOtsEy6QC4tfLps+UU7jBUA01k8pAxXZ3u2eoWr jNqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uymGjDK5u2iW+dXU3naXoUMhvBcNoYwTvrE2f3WFx+M=; b=Tymzj8FBF1Daz4763lsTqlx97sYQVJhAGV4/vMR2pm7+9x3Zt7fBjc66hFjLpL7RTG G1GJqrYqeVDB2/hxiErpu5GMyNPck1GdfdzdRJorjAbVcC0UmlNQjKfmnc7xQMkjmTXI MHTqf0ox2EE+3fTEIhb2go+2Ozj1PFJtJ8vVHTs3wrU331mRMPckRr1ay4hTVHX5xDE6 LPOaF6Fk2iGqBsBiLLauqB7nr7AFFELqEOegDi8OTM8d/15MhJJiNJJ74cEORAfRukb5 j9UJOkbDN5Umc3zxfQ4v1GnhdUffkVlZ4vdSJWffZebzszh7JqEmdVU5bk7mCoGLvVB7 v0Qg==
X-Gm-Message-State: AMCzsaVTOfq/etlNrV0Gh4rPceevBpKMphc78xGq4YVFe+PR1HU3wYZR c9aOTAv1vj5gPa+orEwOnexBhRkMXQZmLuryrcU=
X-Google-Smtp-Source: ABhQp+RoKC7JkLoo7YE40F+Txs5hHla0FWGlbPDmM20yaaLZ5BKSkFfXG6awjFMiWPftVlALyevvvSiP+4UOWgUNKDM=
X-Received: by 10.129.85.202 with SMTP id j193mr15576718ywb.342.1509040967774; Thu, 26 Oct 2017 11:02:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.87.131 with HTTP; Thu, 26 Oct 2017 11:02:46 -0700 (PDT)
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362FD0DC20@MX307CL04.corp.emc.com>
References: <150896122698.4705.6610152257692277567.idtracker@ietfa.amsl.com> <CE03DB3D7B45C245BCA0D243277949362FD0DC20@MX307CL04.corp.emc.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 26 Oct 2017 13:02:46 -0500
Message-ID: <CAKKJt-fMn5EOg0Qjhp=OyxYmqcZx7k-4_kFoPg=2-xktzk9nUQ@mail.gmail.com>
To: "Black, David" <David.Black@dell.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-tcpinc-tcpcrypt@ietf.org" <draft-ietf-tcpinc-tcpcrypt@ietf.org>, "tcpinc-chairs@ietf.org" <tcpinc-chairs@ietf.org>, "krose@krose.org" <krose@krose.org>, "tcpinc@ietf.org" <tcpinc@ietf.org>
Content-Type: multipart/alternative; boundary="001a113f2bd2d5f528055c76faf7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/vjCgoAG5a_lBrMRve8rHZvzHqic>
Subject: Re: [tcpinc] Spencer Dawkins' Yes on draft-ietf-tcpinc-tcpcrypt-08: (with COMMENT)
X-BeenThere: tcpinc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Working group mailing list for TCP Increased Security \(tcpinc\)" <tcpinc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpinc>, <mailto:tcpinc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpinc/>
List-Post: <mailto:tcpinc@ietf.org>
List-Help: <mailto:tcpinc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpinc>, <mailto:tcpinc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Oct 2017 18:02:50 -0000

Hi, David,

On Wed, Oct 25, 2017 at 3:52 PM, Black, David <David.Black@dell.com> wrote:

> Hi Spencer,
>
> > Also for my benefit, but somewhat more worrying - is the working group
> fairly
> > confident that a specifying second MTI key management scheme will be
> possible
> > at some point, that does not trip over the problems described in
> [nist-ecc] and
> > can be implemented in kernels, or is conforming to the guidance in
> [RFC7696]
> > going to be problematic? I see Mirja mentioned SEC discussions about
> only one
> > MTI key management mechanism being chosen now, but my question is a
> little
> > different - I'm asking if the situation is likely to improve anytime
> soon.
>
> Short answer: Yes.
>
> Longer answer: See https://www.ietf.org/mail-archive/web/tcpinc/current/
> msg01363.html
>
> The draft will be revised to reflect the contents of that message,
> including a "SHOULD" requirement for a second key exchange mechanism that
> is not based on a NIST curve.  This approach has been checked with the
> Security ADs, and they're OK with it.


Fabulous.

Spencer

v2.23.0 | Report a Bug | By Email