Re: [tcpinc] Meeting session alternative: coding

Kyle Rose <> Sat, 11 March 2017 02:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9E9571294F5 for <>; Fri, 10 Mar 2017 18:07:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Status: No, score=-2.699 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id t37uBYPYeD8n for <>; Fri, 10 Mar 2017 18:07:05 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4A7FF1294DA for <>; Fri, 10 Mar 2017 18:07:05 -0800 (PST)
Received: by with SMTP id p64so191962227qke.1 for <>; Fri, 10 Mar 2017 18:07:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=IK6I38cDBGKKJS2e0qzxRbFOU+gl/JJEnD4NEseTm5Q=; b=nxOq+dW9kKvFABhDIl6NZx2SQTd0ABZ6WO5SUc9zx9+MIoNMkTVfDU9ClpFRk0GuCD 8X0aPhDq7p+Js6f6X20tc9ymD/JjX50vlWUCwHclUdr1qIA+sPdRW8Pf4gxruTGvTC6/ 85FpmM7IQfn/aEhpMwY4E4nZcEFz6yvadF5gs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=IK6I38cDBGKKJS2e0qzxRbFOU+gl/JJEnD4NEseTm5Q=; b=K6m8Quc9r/xemnP4WqAb/1210lOPCiMPBTyT7nsQ7rcStuXXOvNz+Z/MOYbaSifB7P Nep+zg+ryZk3h+W/xovp2pQtYTTEd7khtPsu8jJ2/RzDRrbjeLxvnlQiLfHmDGSpdAPR /ujyefdpWlmMefXlehc7+9Lle9icINBWv8ej/N39RIv/HAeQy0kPKoQWv0MsyilERL3W HR1rRRIaSXtOD6zlGwzZyez8Qk6mxyBeFuK9/sYWvk3Dl6U3B7qQyLNfl0vA4Ki1vzvt i4La5IZ5chsmnFDbHmmrNNXW1ayqvDfcQHFgWrGoY+kgCisQmxtenkVDYVoSplNRHESX tLgg==
X-Gm-Message-State: AFeK/H0IfAFFcYegJ2QabHOuO/OsbteEocUTX/tjV2x+FIfM9sbqI0BEW9ik4mw2li+5kpILrna9eP8PHwApbA==
X-Received: by with SMTP id 29mr20845023qkq.247.1489198024125; Fri, 10 Mar 2017 18:07:04 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Fri, 10 Mar 2017 18:07:03 -0800 (PST)
X-Originating-IP: [2001:470:1f07:121:103e:c9ff:fe51:acfa]
In-Reply-To: <>
References: <>
From: Kyle Rose <>
Date: Fri, 10 Mar 2017 21:07:03 -0500
Message-ID: <>
To: tcpinc <>
Content-Type: multipart/alternative; boundary="001a113adc6c3aa75b054a6aef15"
Archived-At: <>
Subject: Re: [tcpinc] Meeting session alternative: coding
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Working group mailing list for TCP Increased Security \(tcpinc\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 11 Mar 2017 02:07:06 -0000

I've also changed my flight and am arriving Saturday morning, so if
anyone's interested we can do the full hackathon in addition to time at the
tcpinc session.


On Thu, Mar 9, 2017 at 2:58 PM, Kyle Rose <> wrote:

> 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
> consideration.
> Thanks,
> Kyle (& David B.)