IETF Logo Mail Archive

Re: I-D Action: draft-ietf-quic-manageability-01.txt

"Brian Trammell (IETF)" <ietf@trammell.ch> Wed, 01 November 2017 15:27 UTC

Return-Path: <ietf@trammell.ch>
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 2078D13FDA2 for <quic@ietfa.amsl.com>; Wed, 1 Nov 2017 08:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 1_hN_GWzF3sL for <quic@ietfa.amsl.com>; Wed, 1 Nov 2017 08:27:45 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [IPv6:2001:8e0:40:325::36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C4C413FD88 for <quic@ietf.org>; Wed, 1 Nov 2017 08:27:45 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 069913407BA; Wed, 1 Nov 2017 16:27:44 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/18338.352); Wed, 1 Nov 2017 16:27:44 +0100 (CET)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Wed, 1 Nov 2017 16:27:43 +0100 (CET)
Received: from [161.23.247.65] (account ietf@trammell.ch [161.23.247.65] verified) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 34610886; Wed, 01 Nov 2017 16:27:43 +0100
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <A05591D6-B110-4092-B7F4-E6E88E52A0E3@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_DC9919C1-74D2-441C-A9F2-564C52B9B373"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: I-D Action: draft-ietf-quic-manageability-01.txt
Date: Wed, 01 Nov 2017 15:27:42 +0000
In-Reply-To: <CABcZeBPLddV_+=i4d8w_4y+YdYduviO15xP6Cw5Zt62gjwLzXg@mail.gmail.com>
Cc: "Philipp S. Tiesel" <phils@in-panik.de>, QUIC WG <quic@ietf.org>
To: Eric Rescorla <ekr@rtfm.com>
References: <150891911863.4826.10526078019068901313@ietfa.amsl.com> <6D868BC1-8BE5-4CAA-BEFC-79046C887505@in-panik.de> <F74DCF81-B6E2-426D-96A8-D8C81C61A93E@trammell.ch> <CABcZeBPLddV_+=i4d8w_4y+YdYduviO15xP6Cw5Zt62gjwLzXg@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zhj_s328gP2ryLZANZyxwfVq18g>
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: Wed, 01 Nov 2017 15:27:48 -0000

hi Ekr,

> On 1 Nov 2017, at 15:25, Eric Rescorla <ekr@rtfm.com> wrote:
> 
> 
> 
> On Wed, Nov 1, 2017 at 8:15 AM, Brian Trammell (IETF) <ietf@trammell.ch> wrote:
> 
> > On 26 Oct 2017, at 13:38, Philipp S. Tiesel <phils@in-panik.de> wrote:
> >
> > Hi,
> >
> > I really like the listing of which information QUIC exposes.
> > I have just one little question about it: Should Section 3 also state which information is exposed my the integrated TLS handshake?
> 
> Yes, it should.
> 
> > AFAIK, the TLS handshake exposes the application protocol and host name in clear.
> 
> As I understand it, TLS1.3 should fix this.
> 
> Not at present, though we are working on it for the future.

Thanks for the correction. I'll add this to the set of exposed information for QUIC at present in the working copy of the draft, then.

Cheers,

Brian

> 
> 
> > I am not sure whether it also exposes the initial QUIC connection parameters in clear.
> 
> As I read it, the cleartext packets only contain the TLS1.3 handshake.
> 
> Cheers,
> 
> Brian
> 
> > AVE!
> >   Philipp S. Tiesel / phils…
> >
> >> On 25. Oct 2017, at 10:11, internet-drafts@ietf.org wrote:
> >>
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> >> This draft is a work item of the QUIC WG of the IETF.
> >>
> >>        Title           : Manageability of the QUIC Transport Protocol
> >>        Authors         : Mirja Kuehlewind
> >>                          Brian Trammell
> >>      Filename        : draft-ietf-quic-manageability-01.txt
> >>      Pages           : 13
> >>      Date            : 2017-10-25
> >>
> >> Abstract:
> >>   This document discusses manageability of the QUIC transport protocol,
> >>   focusing on caveats impacting network operations involving QUIC
> >>   traffic.  Its intended audience is network operators, as well as
> >>   content providers that rely on the use of QUIC-aware middleboxes,
> >>   e.g. for load balancing.
> >>
> >>
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-ietf-quic-manageability/
> >>
> >> There are also htmlized versions available at:
> >> https://tools.ietf.org/html/draft-ietf-quic-manageability-01
> >> https://datatracker.ietf.org/doc/html/draft-ietf-quic-manageability-01
> >>
> >> A diff from the previous version is available at:
> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-manageability-01
> >>
> >>
> >> Please note that it may take a couple of minutes from the time of submission
> >> until the htmlized version and diff are available at tools.ietf.org.
> >>
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>
> >>
> >
> >
> 
>

v2.23.0 | Report a Bug | By Email