[Lurk] Terrible solution

Martin Thomson <martin.thomson@gmail.com> Mon, 18 July 2016 17:39 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: lurk@ietfa.amsl.com
Delivered-To: lurk@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2005212D1DC for <lurk@ietfa.amsl.com>; Mon, 18 Jul 2016 10:39:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
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, FREEMAIL_FROM=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 (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 W1uwslNwk0R0 for <lurk@ietfa.amsl.com>; Mon, 18 Jul 2016 10:39:11 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 7C5A812D126 for <lurk@ietf.org>; Mon, 18 Jul 2016 10:39:11 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id o67so163948736qke.1 for <lurk@ietf.org>; Mon, 18 Jul 2016 10:39:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=9hhTROfDnj55wONPMnIbzsoW1W7ooTB3YepgMg4fwAQ=; b=cU+F31g4lIu0MIj0tfXOHtq6+Ghm0JvmPdNtR240otLuZ48WDGXlmY7SelRr9lnrNX s+FpD46He200LC0rPX/tHtXXBEP8/615MMDQiw+lSkluNWfSf5utzYumMQPzAZ3xCUQx cFwuvZpNhdVlgn1T7Z2VVbv2CAWGMkBtdaPh73ZspQCImoNZf6K2jlLYE5Ty+CpeRKYI yWZKfzJyg/G7kwlAZNmf8j7NMVRL6H1onddX76bElnk/D8iKx7PA/A0xbJjsRo10mugs /nFLpwOWX8iZyperJBHWZWN7GM6RKVIYdvNvP3zU9V8t0g7r90W0apjrPhS2ey13QyNc 8K5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=9hhTROfDnj55wONPMnIbzsoW1W7ooTB3YepgMg4fwAQ=; b=iWq3Jwpd1ugZlPQfK5LHyyMIheQDpsSAOtXDg/WkZYD2upOiAXm+qNHM72/diDr9e3 oKFAuVYI7rYqPATkJBVmVk/Q25Apr8WlmqO1DqSTL0bnceAbjSJDHLiRImeoiWrZ2ngV GWHlctkP68YP8m/FeaRkGsFfRVcckOtcsi9QxaYbgb3EEbaLeKvB4wmTYqQC2ArP83FE s0kcyx0G6USYkBMytrueEeO0KJdbm3gk7Np/UllEzKJ0Mv/tKJMxR65GrpCg1asRhUdm yLwSXA6/avcRNgb+zQc5KpqtU//wfgBK7SyzFSS+He04fBfHdhdbW8uKighWlXITiYB0 RDiA==
X-Gm-Message-State: ALyK8tI8+NlNKUOJCUjMMJz6hz9L8hE8lIES+wyXMMNbuj/pk5MCgLHcPE9ulpMXcdQnx6B9gbIaqFMtbNx2dg==
X-Received: by 10.55.203.156 with SMTP id u28mr46702986qkl.116.1468863550516; Mon, 18 Jul 2016 10:39:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.22.146 with HTTP; Mon, 18 Jul 2016 10:39:10 -0700 (PDT)
From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 18 Jul 2016 19:39:10 +0200
Message-ID: <CABkgnnWqt4xr2XJUXse+3XKN78HU6AY=L2KddVdP93W57t-+Pg@mail.gmail.com>
To: LURK BoF <lurk@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/lurk/noIcnQZmpyx9r5hLCWs_peJ7Eys>
Subject: [Lurk] Terrible solution
X-BeenThere: lurk@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Limited Use of Remote Keys <lurk.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lurk>, <mailto:lurk-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lurk/>
List-Post: <mailto:lurk@ietf.org>
List-Help: <mailto:lurk-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lurk>, <mailto:lurk-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2016 17:39:13 -0000

Here's the terrible solution that I shared privately with several others.

The premise here is that you are willing to pay a high price for
initial setup to get some later benefit.

1. Share ticket keys with edge servers.

2. On initial connection to the edge server, the edge server tunnels
the connection to the key owner, who terminates the connection and
sets a ticket.

3. The key owner breaks the connection before anything useful happens.

4. The client attempts to repair the connection, using resumption.

5. The edge server is able to resume the connection, thereafter
gaining the latency benefits.

p.s., I patented this and I will not be providing licences.

p.p.s., The patent thing is a joke.