IETF Logo Mail Archive

Re: 2 Points of First Implementation Draft we might clarify

Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com> Thu, 29 June 2017 00:54 UTC

Return-Path: <tatsuhiro.t@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 215B1126D85 for <quic@ietfa.amsl.com>; Wed, 28 Jun 2017 17:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] 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 iV5HGYugzQFN for <quic@ietfa.amsl.com>; Wed, 28 Jun 2017 17:54:35 -0700 (PDT)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (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 8027D1200ED for <quic@ietf.org>; Wed, 28 Jun 2017 17:54:35 -0700 (PDT)
Received: by mail-qt0-x236.google.com with SMTP id i2so63231663qta.3 for <quic@ietf.org>; Wed, 28 Jun 2017 17:54:35 -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=vICbCJZHfYksDwjLXVfZJAB7ZSR8vxrCBF8h8QwELso=; b=KMXBta3EPj+RJaPnisZsdiEy5JmiL2uSMfLMDnaZ2P06h5x9nrKHKuTrPN9T6Diqsy p50DaYRrHfwaZ8ET9AZrIXVBE83DrBZAyDq6cVpG4nb+lR6UP25n74UVZjHpJXSmFlgt FpLvTWhLDwkCMceyoaBnMFZFFCDYqvp4LeE1sKS4nY1E4KGEK4qkD6+n2EdQGoP0nO+r J0HocNMmXwmff16N8he2/NHepk9lnNEKZ0jFeNMwOoVI5HpbrI2gL1r2+PWrFAFPqIES t+OKHR6YriPWCUHoo8MOuQA0dZ6QOjt+iVXyqLINJx8oOzXejYdJ661StXIA1pnkggQi dnEw==
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=vICbCJZHfYksDwjLXVfZJAB7ZSR8vxrCBF8h8QwELso=; b=idVv7bz2NSAS+XrXHbmJQgUHcCuiVPzfK5STbKJJTg1E4fVE18saLt20xZh9mpO76x /IdHzYE3XwGN1Da14FN2EpRH8rvCh6zJlpPudy2AOH1YbrQiLGIstqhWwmKIqsI+to18 5Uqiytc9XbXpGLsNwk0IMD+nzuhWowtrQNrZoQ9uQhLfTQk+M2YTCjt2TxqknjREoqiS R054NTcRHy8Llqnf6QjWn68EOs4DtFGWDodyEUr4D5XapVtrtPL5maRwwd1bIbfZCUHt pPDYdfsukZay4mSxkvpB8yC+uezLdYD4/PFVKpXwVPsp/PNt2RdzIG70ty4gjYHdiXfd reBg==
X-Gm-Message-State: AKS2vOxH4OaKDXgVyKs5ZlfEqKssYrja91Z3tfqfhsCCwgjhPlxd+7+i ooL83nE+yWo5KAygdfvhHQGWxn6zeY0b
X-Received: by 10.237.43.134 with SMTP id e6mr16023235qtd.131.1498697674718; Wed, 28 Jun 2017 17:54:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.48.148 with HTTP; Wed, 28 Jun 2017 17:54:14 -0700 (PDT)
In-Reply-To: <CAGD1bZZRGKdxV=Bx1Qb1t9XER_UsdmFBtC+mmy4qoOey5BvMrQ@mail.gmail.com>
References: <CAOdDvNreiyrk1bpGc5Cu0OXyO1KDGk25USYM7jz5GpXQCdUpfQ@mail.gmail.com> <CAKcm_gMat+zRrBG1WxiE0O7owDqksR8-JAujPxPOT89p3TgtQw@mail.gmail.com> <CAKcm_gNALLfD7fbpLs=bjFP9oOpx_efJndNtsKT21S5ADDYn1w@mail.gmail.com> <CABkgnnUD3tRdci95TgGqg4xPZeV=knCug=EoNw-S+3oatx_G8Q@mail.gmail.com> <CAGD1bZZRGKdxV=Bx1Qb1t9XER_UsdmFBtC+mmy4qoOey5BvMrQ@mail.gmail.com>
From: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Date: Thu, 29 Jun 2017 09:54:14 +0900
Message-ID: <CAPyZ6=K6BDwR4inuukpZ2M4tED5x_=cR=30dPPzbcco1yozDQA@mail.gmail.com>
Subject: Re: 2 Points of First Implementation Draft we might clarify
To: Jana Iyengar <jri@google.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, Ian Swett <ianswett@google.com>, IETF QUIC WG <quic@ietf.org>, Patrick McManus <pmcmanus@mozilla.com>
Content-Type: multipart/alternative; boundary="001a114ecf0087029f05530ebedf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/kZz9fVBZRxiE5Mpgqk_4YuiS8WQ>
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: Thu, 29 Jun 2017 00:54:37 -0000

On Thu, Jun 29, 2017 at 9:00 AM, Jana Iyengar <jri@google.com> wrote:

> On Wed, Jun 28, 2017 at 2:12 PM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>
>> On 28 June 2017 at 14:10, Ian Swett <ianswett@google.com> wrote:
>> > Would only supporting 18 cause problems for anyone?
>>
>>
>> Anyone using OpenSSL would have a real hard time.
>>
>
> Is anyone planning to use OpenSSL for the interop?
>
>
​I originally planed to use OpenSSL, but it turns out that it does not have
TLSv1.3 exporter yet.
I can live with boringssl (-18) for the first implementation draft.

Best regards,
Tatsuhiro Tsujikawa​

v2.23.0 | Report a Bug | By Email