Re: [tcpinc] tcpcrypt v0.5 release

Joe Touch <touch@isi.edu> Fri, 15 July 2016 17:37 UTC

Return-Path: <touch@isi.edu>
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 657DD12D18E for <tcpinc@ietfa.amsl.com>; Fri, 15 Jul 2016 10:37:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level:
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=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 PrjgGh5rHjHB for <tcpinc@ietfa.amsl.com>; Fri, 15 Jul 2016 10:37:39 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (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 9A22012D14B for <tcpinc@ietf.org>; Fri, 15 Jul 2016 10:37:39 -0700 (PDT)
Received: from [128.9.184.131] ([128.9.184.131]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id u6FHb9rI014437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 15 Jul 2016 10:37:09 -0700 (PDT)
To: Kyle Rose <krose@krose.org>
References: <CABu4T3LYef73rLAQwG6pdhz0BVW72P2CEAJLY1=rnC=WxeWBgQ@mail.gmail.com> <57891D62.6030803@isi.edu> <CAJU8_nUmsFiYk7sXuyNB+3-8AvBREookPUxRjHy0oU4JcCUT+A@mail.gmail.com> <CAJU8_nVyA2_Ls1yJv12wTT_+VaEkssSgZteVEsGVaKmNDvjYjQ@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <57891F42.40207@isi.edu>
Date: Fri, 15 Jul 2016 10:37:06 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAJU8_nVyA2_Ls1yJv12wTT_+VaEkssSgZteVEsGVaKmNDvjYjQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: u6FHb9rI014437
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/LtoOtzgVfk9ICZ__tL9jdjn4ImQ>
Cc: Andrea Bittau <bittau@cs.stanford.edu>, tcpinc <tcpinc@ietf.org>
Subject: Re: [tcpinc] tcpcrypt v0.5 release
X-BeenThere: tcpinc@ietf.org
X-Mailman-Version: 2.1.17
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, 15 Jul 2016 17:37:40 -0000


On 7/15/2016 10:34 AM, Kyle Rose wrote:
>
> > Although I'm glad to see this happen, it's frankly very long overdue and
> > the damage created by squatting on unassigned TCP codepoints is
> > something we really need to take seriously in how codepoints are
> > assigned to this (or other squatters) in the future.
>
> Perhaps so, but I'm pretty sure the proposed discussion isn't business
> for the tcpinc mailing list.
>

It is if/when tcpcrypt applies for an assigned TCP codepoint. If
tcpcrypt never does this, it'll merely be used as a example of behavior
to avoid in d iscussions on other lists.

Joe