Re: Getting to a First Implementation Draft

Lucas Clemente <luke.clemente@gmail.com> Mon, 15 May 2017 08:07 UTC

Return-Path: <luke.clemente@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 E51EF126E64 for <quic@ietfa.amsl.com>; Mon, 15 May 2017 01:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
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, FREEMAIL_FROM=0.001, 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 (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 9p-Rhzd9Xutj for <quic@ietfa.amsl.com>; Mon, 15 May 2017 01:07:01 -0700 (PDT)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 DA0E3126D05 for <quic@ietf.org>; Mon, 15 May 2017 01:02:14 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id l14so33810322ywk.1 for <quic@ietf.org>; Mon, 15 May 2017 01:02:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tGoIq1Ue4FtnjVJLWGPFSbWWwr6FwY2HvE1N8pT0l8Q=; b=e1lmo9Z5jqPt5VUMrkVh3HOjQYWmUTKF50mIGDQahFFwMTYd/lD9fSY6yzmyNs8zN1 VOnCqtWO2nSxw6FMeTcuiOSdwsMG3VEY4EMHHz05UCbIz6ORz/kg4w1R/Fc9MZWTsJDS n93/35A2qo2mq/GklP1NytLkwAKQnXzEm7gbRzMGOh+WSuVQHteXES1AJ4aWfK+v47p2 BU1MP2FYtLrC04Wa+ZXOHp6+mV+drMlrTrqr6NLB15XDEvAvPMd53Gokp4aS8kpqOT04 L45QqRBr9MOVix6UsXpmyGRf2DEA6vhKu+E3fRbzzoiXQ4O0ynw5oQoyiJezC0V6tNey ApTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tGoIq1Ue4FtnjVJLWGPFSbWWwr6FwY2HvE1N8pT0l8Q=; b=ZqgsIQorWSCU8xFcjkhShexMXekx4nqmTrNDXh5XDDToqpK7C7WBbq20ZMY/MGPlWE wnBsCnoCDuNHXmBaOIfu3InwwKZXiwjzHr77+enNxqxvl2WzWPNcxRxboA9gZTqcsU+J k3stXeatdpt6sHWalXrSJwRaI2o5Y4A92LyrPT7+8oLCn9KqUvikRxUWALx2nXWcjWdR tm8FXJ1QPqmG3tDrBU1PfNFHi48f8BteTI/BYq87kXOuCKPjZBS/1HjpD/r5LNCsROPd DvfttAQ7aJ0SCZtZsxS/2npsa/rMNTFjIKVzhdrZ8cV28gWuvbdxVYGDeu3ebqqlorwk u3xA==
X-Gm-Message-State: AODbwcDXRDSqkM161S0P+60DwWJkgO0A1mEH9mnZb2zdo5dNzS7qydr1 2VVrPGnDZrWMC0xPurO7uDX01myiDw==
X-Received: by 10.129.97.195 with SMTP id v186mr4141888ywb.151.1494835334111; Mon, 15 May 2017 01:02:14 -0700 (PDT)
MIME-Version: 1.0
References: <20DB6018-3E7B-454F-8BEC-0F839D949AFE@mnot.net> <CABcZeBNqYE3e0M-zV-AWt33Q6vduXk5rgsvwXHVZLrXBU4XK=Q@mail.gmail.com> <CAOdDvNrp=WBvDju0tNu-DAreS1tSbFRJL1T9Ts16vZjDNGajqw@mail.gmail.com> <CAKcm_gNrT+XqgJCTmeCR2ayqqZa=m=nTRQwme5ZTaKCjtk3Egg@mail.gmail.com> <CAOdDvNpEj8wBbO=Y1jihgh1K9hAH5f-SYvmOs9YYWF2BKiGboA@mail.gmail.com> <CAGD1bZYxUapLhqteZuU3SkXxG+mGkctHwr4DWYNCBQfmH=1MYA@mail.gmail.com>
In-Reply-To: <CAGD1bZYxUapLhqteZuU3SkXxG+mGkctHwr4DWYNCBQfmH=1MYA@mail.gmail.com>
From: Lucas Clemente <luke.clemente@gmail.com>
Date: Mon, 15 May 2017 08:02:03 +0000
Message-ID: <CAFgJD_=LGGhGtRCuC36Aia8tFK+Q-_SecKskjza5u6mV=hSs9A@mail.gmail.com>
Subject: Re: Getting to a First Implementation Draft
To: Jana Iyengar <jri@google.com>, Patrick McManus <pmcmanus@mozilla.com>
Cc: Ian Swett <ianswett@google.com>, IETF QUIC WG <quic@ietf.org>, Lars Eggert <lars@netapp.com>, Mark Nottingham <mnot@mnot.net>, Eric Rescorla <ekr@rtfm.com>, Marten Seemann <martenseemann@gmail.com>
Content-Type: multipart/alternative; boundary="001a11490122166929054f8b798f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PUejy2CBqngxq9pYJReB3kz6i_0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 15 May 2017 08:07:03 -0000

Another idea would be to just have a single stream and "emulate" TCP+TLS
using that. We used something similar
<https://github.com/marten-seemann/quic-conn> in the past to refine our
API, and this gave us a lot of input for that.

This would probably add flow control to the scope, unless we just manually
set the window to something huge for these initial tests.

On Sun, 14 May 2017 at 23:47 Jana Iyengar <jri@google.com> wrote:

> Adding a PING frame + ACK seems like a good idea.
>
> On Sun, May 14, 2017 at 1:39 PM, Patrick McManus <pmcmanus@mozilla.com>
> wrote:
>
>>
>> On Sun, May 14, 2017 at 4:23 PM, Ian Swett <ianswett@google.com> wrote:
>>
>>> Or were you thinking something of simple like "ping" and "pong"?
>>>
>>
>>
>> yep.
>>
>
>