Re: [tcpinc] Review of draft-bittau-tcpinc-tcpeno-01

Eric Rescorla <ekr@rtfm.com> Fri, 28 August 2015 17:19 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: tcpinc@ietfa.amsl.com
Delivered-To: tcpinc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63C141ACEEF for <tcpinc@ietfa.amsl.com>; Fri, 28 Aug 2015 10:19:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 swk1-siISL9m for <tcpinc@ietfa.amsl.com>; Fri, 28 Aug 2015 10:19:02 -0700 (PDT)
Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (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 D37F41ACDF2 for <tcpinc@ietf.org>; Fri, 28 Aug 2015 10:19:01 -0700 (PDT)
Received: by wicfv10 with SMTP id fv10so17928143wic.0 for <tcpinc@ietf.org>; Fri, 28 Aug 2015 10:19:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=+0qxQ4aOadmt5etk11hWHPlL705lccoFPJB7QSNAQK0=; b=X+NtPClXL+3WK/LF+q9b3ZMSTWHNm9Vj6MlZTm3AciGnpHXSvLrXnvYzq1sniRwkrR i7BHM11ao7KUpwaNqRA8qWDau03ERvlN62GQKovvMqQhmXlEWYTWf3vCD8jiINmAtCxD kCtxPsfSV2lNPC/pi3xcTG1+iFsn5bwKDnMU/F5ziPa6RmnxpseFgFaFiTsyBcmxvVhX oJRh4v45DFlBtD3mx4uuAj92jl6IQJui2gT5/gfk7K9qcIkhs5oCooDDpIdbBj96kNyq 4HCXvDcjIYqL+9v1oBvOMOxqAcm8l0lPB7Wv02HywPmfkL/UkCXOytThb/3NCRHAT1fU b7+A==
X-Gm-Message-State: ALoCoQm9STo1EdcYS0mkTKe8rSeNrM9/TDBG24d2vaGO86H+/C9hXqq4jhtAb87pAWaYMLXiRms2
X-Received: by 10.180.99.73 with SMTP id eo9mr4042085wib.68.1440782340564; Fri, 28 Aug 2015 10:19:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.27.179.221 with HTTP; Fri, 28 Aug 2015 10:18:20 -0700 (PDT)
In-Reply-To: <8737z3kijy.fsf@ta.scs.stanford.edu>
References: <CABcZeBNEFVkDi38y3G-C2nQF=dzW2mGDsj5DVK_OKVkPwK=G0g@mail.gmail.com> <878u92oadf.fsf@ta.scs.stanford.edu> <CABcZeBMfk5C4-LF0fDLKpJktV3hJyzRUNfe0gO8RYDnzcs3yMA@mail.gmail.com> <87zj1inf7n.fsf@ta.scs.stanford.edu> <CABcZeBMZCjrwpTH+CkZS_p8TYGEFsXwxGn=KfPe28hY5f=2oXw@mail.gmail.com> <87oahuta7j.fsf@ta.scs.stanford.edu> <CABcZeBPiUxByxUVJ3cb5LaeH5T1LX3iZFetP4cXM3O9avzBkCA@mail.gmail.com> <87si75jo4s.fsf@ta.scs.stanford.edu> <BDF93B3E-9DE0-4FEA-A4A7-6E6A69E4169B@tik.ee.ethz.ch> <87h9nkkcqc.fsf@ta.scs.stanford.edu> <55DF25DC.2040001@tik.ee.ethz.ch> <87twrkhfpg.fsf@ta.scs.stanford.edu> <CAJU8_nWktUwni0=nywx-bbHg+j_K5GWFAZD8g3ZbKx7GLk4jpQ@mail.gmail.com> <877fogvdq7.fsf@ta.scs.stanford.edu> <CABcZeBPTGQvjdP7-6=+mN0S6wWOZC8PrsZhGu85NMkFQF-nMXg@mail.gmail.com> <8737z3kijy.fsf@ta.scs.stanford.edu>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 28 Aug 2015 10:18:20 -0700
Message-ID: <CABcZeBPVhQ-nJw4zjELXeU8LwhkyMGxi3gEROaEa0iTsjt=y4g@mail.gmail.com>
To: David Mazieres <dm-list-tcpcrypt@scs.stanford.edu>
Content-Type: multipart/alternative; boundary="f46d04428f489bc205051e62477a"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tcpinc/spnDS5VdltFkyvDYf3dgEsH9-FM>
Cc: tcpinc <tcpinc@ietf.org>, Kyle Rose <krose@krose.org>, Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [tcpinc] Review of draft-bittau-tcpinc-tcpeno-01
X-BeenThere: tcpinc@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for adding encryption to TCP." <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: Fri, 28 Aug 2015 17:19:03 -0000

On Thu, Aug 27, 2015 at 11:56 PM, David Mazieres <
dm-list-tcpcrypt@scs.stanford.edu> wrote:

> Eric Rescorla <ekr@rtfm.com> writes:
>
> >>  1. Does TCP-SO really exist in the wild, and if so under what
> >>     circumstances (NAT, no NAT, etc.)?
> >
> > TCP-SO definitely exists in the wild. We do it in Firefox's ICE stack.
>
> So I'm not familiar with ICE over TCP, though I see there's now an
> RFC6544 on this.  Is that what firefox does?  That's great information.
>
> With RFC6544, could the controlling/controlled roles be used to break
> ties?  E.g., with TCP-ENO, could the controlling peer just always set
> b=1?


The problem is that there are situations where each side thinks it is
controlling
("role conflicts"). RFC 5245 has the tiebreaker field to resolve this.

-Ekr