[tcpinc] Meeting session alternative: coding

Kyle Rose <krose@krose.org> Thu, 09 March 2017 19:58 UTC

Return-Path: <krose@krose.org>
X-Original-To: tcpinc@ietfa.amsl.com
Delivered-To: tcpinc@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 698D2129413 for <tcpinc@ietfa.amsl.com>; Thu, 9 Mar 2017 11:58:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=krose.org
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id XAYbv6ugeu6V for <tcpinc@ietfa.amsl.com>; Thu, 9 Mar 2017 11:58:42 -0800 (PST)
Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 2E562126D74 for <tcpinc@ietf.org>; Thu, 9 Mar 2017 11:58:42 -0800 (PST)
Received: by mail-qk0-x231.google.com with SMTP id y76so137159553qkb.0 for <tcpinc@ietf.org>; Thu, 09 Mar 2017 11:58:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=tuKfEL9VOT90RrGx+DlauP9XsDPiVIl3JB9DWlYtoOc=; b=qwWrJ83uLJi3CvqfP2nh2FLG//HjO1M5HmoEii9C3zk4DZsCNn80fg8F4VW2dXI4MV Aw6fLCPVzo+32KwWb4TqVOajGGjdhejqEjU6wQ6Z4qfecYem1lr3T7g9jv0/buOkR0A5 CxJyFqhckTWTBoruZ8VsmmCbiD6LLKwJoS4L4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=tuKfEL9VOT90RrGx+DlauP9XsDPiVIl3JB9DWlYtoOc=; b=JuJzZkJyf1PICK1kpBcUWFCFLHEkACRlwvRQjet9zpsLDw33SR/FOegQ5+UcppPASR EbpcN2/L5D3gvdIoN1ZMUyIqoIH7ThIkx8vt5uGAlge4K9MEEJeNZTzrXavKawdSny5w S019UZTTJIL7TMsel7yadcWZ0N8yM1cGODE5htgboQQM1wKB2xNpUQtd7GzMRG6VsxC3 KWbo1FUXkxGcBFORfmMxSzNlXnLbaqcZPbftlLRJX9uarZSDNah2ihsFJZpaGD9KGl7s zhoaJT9OOF7fOXs9BbpPB1zjCzfiZccSStLA9TXu+w/RCMr5X6JhpFWyNM1OcMtDkR89 O9og==
X-Gm-Message-State: AMke39nP34EsQ8HwKQO3ooLINPd5+eB2zvGq1YTeBCTayABYmI6EYICd/+0+ctcImHkiRVaETSMrcb9LRr0iCg==
X-Received: by with SMTP id h12mr15965542qtb.44.1489089520835; Thu, 09 Mar 2017 11:58:40 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Thu, 9 Mar 2017 11:58:40 -0800 (PST)
X-Originating-IP: []
From: Kyle Rose <krose@krose.org>
Date: Thu, 09 Mar 2017 14:58:40 -0500
Message-ID: <CAJU8_nUz-qFH4KM7uxQpRZ712JaGpB_L5VnH+ZAy3ZRhQi2FfQ@mail.gmail.com>
To: tcpinc <tcpinc@ietf.org>
Content-Type: multipart/alternative; boundary="001a11403046edbfb3054a51abb5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/oY7eYMB-83SLIfG0nzR3WQnNqbY>
Subject: [tcpinc] Meeting session alternative: coding
X-BeenThere: tcpinc@ietf.org
X-Mailman-Version: 2.1.17
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, 09 Mar 2017 19:58:44 -0000

The tcpinc session for Chicago currently has no agenda, as the two main
drafts will likely be out of WGLC by that time and the API draft isn’t
really a good use of meeting time on its own. (We’ll plan to take that
draft up on the mailing list sometime after the Chicago meeting week).

The chairs would like to propose an alternative use of tcpinc meeting time
in Chicago: a mini-hackathon to work on implementations and interop.

I started an ENO implementation for the Linux kernel some months ago, an
effort that would have benefited from domain expertise in the same room.
It's a short time period, so coding an implementation from scratch probably
wouldn't get very far (though you should not let this discourage you!), but
this could be a good time to get developers bootstrapped with resources and
connections so we can continue coding and interop testing when we return to
our places of origin.

If you're interested, please respond on the list and we'll take it into

Kyle (& David B.)