IETF Logo Mail Archive

Re: Hidden connection spawning

Ted Hardie <ted.ietf@gmail.com> Thu, 26 July 2018 22:08 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 285B0131240 for <quic@ietfa.amsl.com>; Thu, 26 Jul 2018 15:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Rw8BcAnUUOJf for <quic@ietfa.amsl.com>; Thu, 26 Jul 2018 15:08:30 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (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 53055131242 for <quic@ietf.org>; Thu, 26 Jul 2018 15:08:30 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id n84-v6so5724419oib.9 for <quic@ietf.org>; Thu, 26 Jul 2018 15:08:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DP/4JThFUQQ6QOLJ4htDvf65pOYtG5WmSvMJZRk27u4=; b=vdvdVMG48Y1BOcyPvqXod/nf1JRDPcSUjI4hiGd3Td2K4GnYFdNhFmGXVRySfzLGqI o8wIsNCYcBJZdBrKq4ZPufEjju3NCnvQhRZ2b23AwjB/4ysbTeb2nRv+XZrRpdf3N9vW rhhZQDQbKEpF4hNAXjIFcE666vc3hVtQweMT3EtIzXsvqtagkgScb1nKmJZszcclxCuc oTSeugFfF/eCCmsqnVY7i7BcUaJoDBoZr3qvXFN9VtM9XpVi99cVb1FQAjuj4rrgRQhF R4iE5cMs/BxpaYI5AfYbRVzd6YxWfv2H4cGHxXO520FEE8G6Q4Pt0kKdPdifd7s6jRKu BtEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DP/4JThFUQQ6QOLJ4htDvf65pOYtG5WmSvMJZRk27u4=; b=hz2wjLpJ+bVGIqf0szl9ouKSuX8tzdljgVdubwGmE/jmLBcNScm9IUb8jLtaz+jtJH RQ5pkz6cJlYJb2eTE8CyoFvEsDmF6kd9lzDmb51sLcIykikYIBWKgoB7e7YSeWfzcysx lSYTmCHDWesZYhtaFzCZFmXVtfuM1wF4oZI3G2nDAanjnS5Ot7y6QkB4fg4nSqFuy9oB +ZHc2wT6m012c8UH6U62J4k4bg7s2zYdy6VYsL9zRMt2YOitW4hnRIFpVfa14pPQ4Tip 5myDdwmAoNo53pZga5HnY9aWT1ymRFAjm5jJGzh3loSXEEqXNvAPxKu7Ac7WT11PZOIj 0qYA==
X-Gm-Message-State: AOUpUlEhWtf78zK2DbmTUyxkoKWHqx6zcMiDjOnQheYwT8vudypALPkW f2uSR4cPdAOT81ijqPKRv2hDr7zS09DbBJ49QZA=
X-Google-Smtp-Source: AAOMgpfo3Ae7Ob+CmyoJ4K/aSJLSnoJ/iayfRtHlbevIbuy9ihasrU7/9+TUEZE4HES4t77QDCJlxQTCuca1cLtWC10=
X-Received: by 2002:aca:c692:: with SMTP id w140-v6mr3792818oif.284.1532642909279; Thu, 26 Jul 2018 15:08:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:66d9:0:0:0:0:0 with HTTP; Thu, 26 Jul 2018 15:07:58 -0700 (PDT)
In-Reply-To: <e9404a58-febb-7f24-00ee-e11312afd22f@huitema.net>
References: <CAN1APdfRmLp9R8+3e+kfHusSppnrtyHNFC1mNt9Vt+5kiDf9rw@mail.gmail.com> <e9404a58-febb-7f24-00ee-e11312afd22f@huitema.net>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 26 Jul 2018 15:07:58 -0700
Message-ID: <CA+9kkMBPiu6d7fAnSos0Oo2+y_m2WmKrDQcXyGVLoOcVpNpBfA@mail.gmail.com>
Subject: Re: Hidden connection spawning
To: Christian Huitema <huitema@huitema.net>
Cc: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002cdb480571ee3c05"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3Ub2buCcyXArJao-Ni2DzkqfYUQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2018 22:08:35 -0000

On Thu, Jul 26, 2018 at 2:41 PM, Christian Huitema <huitema@huitema.net>
wrote:

>
> I have a related scenario in mind, something like "server-assisted
> peer-to-peer". Two peers first synchronize through a server -- each peer
> has a QUIC connection with the server. They exchange some messages to
> establish a peer-to-peer connection through the server, then use connection
> migration to establish a direct peer-to-peer connection. I think it will
> require the same type of extension frames that you are considering, plus
> something like ICE.
>

This seems like a generalization of the "QUIC as an RTCWEB datachannel"
use case.  In that, the web server providing the JavaScript is the initial
server, ICE messages provide rendezvous/consent, and you can have
peer-to-peer connections.

Other than the generalization from "web server" to "server" is there a
distinction here I'm missing?

Ted

v2.23.0 | Report a Bug | By Email