Re: 2 Points of First Implementation Draft we might clarify

Steven Valdez <svaldez@google.com> Wed, 28 June 2017 23:44 UTC

MIME-Version: 1.0
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> <CAOdDvNrH6NuFXa0P_kXsOM7+KhyP=pabN2y9nbCPdURgv2Ud1g@mail.gmail.com> <CABcZeBOviRK=-WK=WOOT7d92hJLMJNp2fWYZAYUiWoq-9qZ3Bw@mail.gmail.com> <CACdeXi+zPX54du9sM0iJ_Z=vEKkuiVjtbY6sfsyAhh1SbihOVg@mail.gmail.com>
In-Reply-To: <CACdeXi+zPX54du9sM0iJ_Z=vEKkuiVjtbY6sfsyAhh1SbihOVg@mail.gmail.com>
From: Steven Valdez <svaldez@google.com>
Date: Wed, 28 Jun 2017 23:44:45 +0000
Message-ID: <CANduzxDmEZoapZquGX1h_81ft-kcWmtrif-+sVTa=NcPkmpEjA@mail.gmail.com>
Subject: Re: 2 Points of First Implementation Draft we might clarify
To: Nick Harper <nharper@google.com>, Eric Rescorla <ekr@rtfm.com>
Cc: Ian Swett <ianswett@google.com>, IETF QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>, Patrick McManus <pmcmanus@mozilla.com>
Content-Type: multipart/alternative; boundary="f403045e86c4797ac905530dc56f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/CzmXCBKBohESntJH_CvmehEUrbE>
Precedence: list

While there was some work on draft 20 during the last IETF Hackathon, the
code is far from complete and still needs lots of tests and the
implementation of additional parts of the draft 20 changes, which
unfortunately won't happen for a while due to other issues*.

In general, it sounds like many TLS implementations at the very least have
a copy of the draft 18 code, from the previous IETF Hackathons (NSS,
OpenSSL, BoringSSL, etc) and it also sounds like at least other parties on
the TLS WG list (implementations and tools, Wireshark, Apple, etc) have
draft 18 reviewed in some form.

-Steven

* We've had a lot of issues actually deploying TLS 1.3 in the wild, and
most of our focus has been on gathering information on the ecosystem
intolerance and how to avoid it, and will likely continue prioritizing that
for the near future so we can give feedback to the TLS WG.

On Wed, Jun 28, 2017 at 6:50 PM Nick Harper <nharper@google.com> wrote:

> https://boringssl.googlesource.com/boringssl/+refs does not show a -20
> branch.
>
> On Wed, Jun 28, 2017 at 3:42 PM, Eric Rescorla <ekr@rtfm.com> wrote:
> > My understanding was that BoringSSL had a -20 branch, as NSS does. Is
> that
> > incorrect?
> >
> > -Ekr
> >
> >
> > On Wed, Jun 28, 2017 at 2:13 PM, Patrick McManus <pmcmanus@mozilla.com>
> > wrote:
> >>
> >> and now we see the reason we have a problem :)
> >>
> >> 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.
> >>
> >>
> >
>
>

2 Points of First Implementation Draft we might c… Patrick McManus
Re: 2 Points of First Implementation Draft we mig… Ian Swett
Re: 2 Points of First Implementation Draft we mig… Ian Swett
Re: 2 Points of First Implementation Draft we mig… Martin Thomson
Re: 2 Points of First Implementation Draft we mig… Patrick McManus
Re: 2 Points of First Implementation Draft we mig… Eric Rescorla
Re: 2 Points of First Implementation Draft we mig… Nick Harper
Re: 2 Points of First Implementation Draft we mig… Steven Valdez
Re: 2 Points of First Implementation Draft we mig… Jana Iyengar
RE: 2 Points of First Implementation Draft we mig… Salz, Rich
Re: 2 Points of First Implementation Draft we mig… Tatsuhiro Tsujikawa
Re: 2 Points of First Implementation Draft we mig… Eric Rescorla
RE: 2 Points of First Implementation Draft we mig… Salz, Rich
Re: 2 Points of First Implementation Draft we mig… Kazuho Oku