IETF Logo Mail Archive

Question about 0-RTT

William Herrin <bill@herrin.us> Wed, 03 July 2019 22:29 UTC

Return-Path: <bill@herrin.us>
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 93378120677 for <quic@ietfa.amsl.com>; Wed, 3 Jul 2019 15:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, 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 TZO3FqfQRE8R for <quic@ietfa.amsl.com>; Wed, 3 Jul 2019 15:29:06 -0700 (PDT)
Received: from magic.dirtside.com (magic.dirtside.com [199.33.225.25]) by ietfa.amsl.com (Postfix) with ESMTP id 28441120672 for <quic@ietf.org>; Wed, 3 Jul 2019 15:29:06 -0700 (PDT)
Received: from minoc.dirtside.com ([199.33.225.53]) by magic.dirtside.com (8.14.3/) with ESMTP id x63MSowJ014790 for <quic@ietf.org>; Wed, 3 Jul 2019 15:28:50 -0700
X-Really-To: <quic@ietf.org>
Received: from mail-pl1-f174.google.com (mail-pl1-f174.google.com [209.85.214.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by minoc.dirtside.com (Postfix) with ESMTPSA id DF577EBDB5 for <quic@ietf.org>; Wed, 3 Jul 2019 15:28:49 -0700 (PDT)
Received: by mail-pl1-f174.google.com with SMTP id a93so1972455pla.7 for <quic@ietf.org>; Wed, 03 Jul 2019 15:28:49 -0700 (PDT)
X-Gm-Message-State: APjAAAV72czWVf5eTYPkuOnfKiyzMDiTItk6VsfzPVJRAzRVz4/7JQv4 Pu1MXoJLjsFRViwirnJJVnGuFhWsDPw1SEF/8H8=
X-Google-Smtp-Source: APXvYqy4JQE5L9qeUBZvpSxBjUVOe7fjTdV9IwgpgGoexWBIBblTEs6AgTTU9b3vQFJc7yqhbVJqAg7AhzVDbkJEpns=
X-Received: by 2002:a17:902:aa5:: with SMTP id 34mr46637117plp.166.1562192929639; Wed, 03 Jul 2019 15:28:49 -0700 (PDT)
MIME-Version: 1.0
From: William Herrin <bill@herrin.us>
Date: Wed, 03 Jul 2019 15:28:38 -0700
X-Gmail-Original-Message-ID: <CAP-guGUW9cfBVWGYkqLFZWmjuiUjAhTnYN=zcjJL=em5MXHjsQ@mail.gmail.com>
Message-ID: <CAP-guGUW9cfBVWGYkqLFZWmjuiUjAhTnYN=zcjJL=em5MXHjsQ@mail.gmail.com>
Subject: Question about 0-RTT
To: quic@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a4550b058cce62b0"
X-Spam-Checker: magic.dirtside.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/mxPhYOTxo1y6f3U3yc1kWUqQ308>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Jul 2019 22:29:15 -0000

Hi folks,

Reading https://tools.ietf.org/html/draft-ietf-quic-transport-20, I have a
question about 0-RTT: What is it?

The draft talks a lot about it, but I didn't see anywhere that clearly
defined what it is. When I see "RTT" without a definition I tend to think
"round trip time," but the explanation of 0-RTT seems to have more to do
with encryption setup during connection initialization than any tie to
which round trip completes the setup. I find this confusing.

Would someone comment and either show me the definition I missed or add one
to the next draft?

Thanks,
Bill Herrin

-- 
William Herrin
bill@herrin.us
https://bill.herrin.us/

v2.23.0 | Report a Bug | By Email