Re: RTT sampling on retransmissions

Ian Swett <ianswett@google.com> Sat, 21 July 2018 16:45 UTC

Return-Path: <ianswett@google.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 212AB130DFF for <quic@ietfa.amsl.com>; Sat, 21 Jul 2018 09:45:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.51
X-Spam-Level:
X-Spam-Status: No, score=-17.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 eCTH1238wy_4 for <quic@ietfa.amsl.com>; Sat, 21 Jul 2018 09:45:10 -0700 (PDT)
Received: from mail-yb0-x231.google.com (mail-yb0-x231.google.com [IPv6:2607:f8b0:4002:c09::231]) (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 CC88A130DC4 for <quic@ietf.org>; Sat, 21 Jul 2018 09:45:09 -0700 (PDT)
Received: by mail-yb0-x231.google.com with SMTP id s1-v6so5791124ybk.3 for <quic@ietf.org>; Sat, 21 Jul 2018 09:45:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Hs4pgO7NsInNe7RbsmpqLJqsTdJfgKGbtHeS+Qj2EUM=; b=sOKQyGwwBnznNFWcNjh559S7De1GqOJ9lZWSFUcIG8JZ/62ugqa9ZcQudQ5Y15Jje/ QPT/tUWdzZWl3y/PWkEtkWua058TKZQfMkwrFhLZh82n6c0L5yFp4Aoxv75xTmnFBphX rxrycOB+bstPPGPElw1R5jIAY/jmGHqK4aq8R4xz9wHI5HdOrZPxCnugeH+LsM0TwZUE SKautyRjdK8xdg1Vo2nEElwVPuwWnB/yRnTfO/6r+U01i5SqjkuJYfuhaIn9aJd57CTY a70q5kxxvoca12pclPuf+SIDrZ+vjnpro6E/sjCpfjvJk7AKJrMrakmgM+KCHMsl/Jmj G6tw==
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=Hs4pgO7NsInNe7RbsmpqLJqsTdJfgKGbtHeS+Qj2EUM=; b=ItzlrexPG3kXeC8epC4shZ3ZW/XyLV8/1q1pIDXdKuXpbkhlNrybFIcgYF0NMtZF1F 6A2nK3eHOD8LQODMzTmbJyRXy/wcsv9Ru7x0u6Y2Z/KhH3YPwnodqT2A+wwTkSj5gXjy PIJB+IqX3FDFLbq+mXRRYha14WbMFY3cJWQ0nDMZTQdPYSJ4id+DuUVppurf6ds56Wnx WKLzIQ1jYEW+C9FvtZB2T/n8sL1RjBbxq86D2z6blU0Xp1Hwg7I4uIYe8pfsyEix+uCp +L3UhztrfdUeVpjUf/1/kwHhKz4qFN9LdV8/oDDgveEMxtXmXyDPNLiIwVKbZjtGjH2t r8bA==
X-Gm-Message-State: AOUpUlEuUXLxkpBhqrwIVJUZREl5P1veUOakR69iLhXl/FXyvG7Qmpq5 M5KKMV3Pxs6mgkN5VTcSUK50LcvTfB87iyBurp2zTnBZyrE=
X-Google-Smtp-Source: AAOMgpdBJPoO7VhgkiZVv1Bo3KmKO7tY5yjRpPnkmp8BB7H+On/f1FBgyPjxr/v1fFJEoUXuXRTXZeOL7ULYnZuDZ0Q=
X-Received: by 2002:a5b:3cd:: with SMTP id t13-v6mr3444424ybp.206.1532191508687; Sat, 21 Jul 2018 09:45:08 -0700 (PDT)
MIME-Version: 1.0
References: <CACD9L=AnVqsLjoifoz-qyKQS+MKKh=V5BjWVOE38zEO+rd9jiw@mail.gmail.com>
In-Reply-To: <CACD9L=AnVqsLjoifoz-qyKQS+MKKh=V5BjWVOE38zEO+rd9jiw@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Sat, 21 Jul 2018 12:44:56 -0400
Message-ID: <CAKcm_gMt5ezBHSHkCBp+QBjQZgkdwXg3puwY9+ZBx_seY2h0Hg@mail.gmail.com>
Subject: Re: RTT sampling on retransmissions
To: aep@exys.org
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009b440105718522cb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2N6PAvzUGs2HOnukMx6z9-Eoc_A>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.27
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: Sat, 21 Jul 2018 16:45:12 -0000

QUIC doesn't retransmits packets.  If data needs to be retransmitted
because it's lost, it's sent in a new packet with a new packet number.  The
new packet number prevents issues with ambiguity.

See recovery section 2(particularly 2.1.2) for more details:
https://tools.ietf.org/html/draft-ietf-quic-recovery-13#section-2



On Sat, Jul 21, 2018 at 10:23 AM Arvid Picciani <aep@exys.org> wrote:

> Hi,
>
> UpdateRtt in
> https://tools.ietf.org/html/draft-ietf-quic-recovery-13#section-3.5.5
> does seem to calculate the RTT from an ack on any packet, even if the
> packet was resent.
>
> 1. In a TLP event The oldest packet is resent and the sent_time reset
> to the current time.
> 2. Eventually that packet is acked, because the network was just slow.
> 3. RTT is calculated from the last sent_time (which was the time it was
> resent).
> 4. RTT is way too small now, leading to lots of timeouts.
>
>
> what am i missing here?
>
> https://tools.ietf.org/html/rfc6298 section 2 specifically says that
> RTT must NOT be calculated from retransmissions. Is a "retransmitted"
> bit in the quic-recovery left as exercise to the reader or should
> retransmissions actually never be passed to OnPacketSent?
>
> /b/
>
>