IETF Logo Mail Archive

[tcpm] using SACK info for RTTM?

Yoshifumi Nishida <nsd.ietf@gmail.com> Mon, 03 June 2024 15:01 UTC

Return-Path: <nsd.ietf@gmail.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7419AC1D4CEB for <tcpm@ietfa.amsl.com>; Mon, 3 Jun 2024 08:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L91pIfDIgwBV for <tcpm@ietfa.amsl.com>; Mon, 3 Jun 2024 08:01:46 -0700 (PDT)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BD34C1D4A7E for <tcpm@ietf.org>; Mon, 3 Jun 2024 08:01:46 -0700 (PDT)
Received: by mail-wr1-x429.google.com with SMTP id ffacd0b85a97d-35dc36b107fso3424108f8f.1 for <tcpm@ietf.org>; Mon, 03 Jun 2024 08:01:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717426904; x=1718031704; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=enocrHxjDAlQ0LTPM45Ai8aNzT/SXd/hVjCBZwyU1M4=; b=KHJqAdWAMIpbfNedqCzmQbgsCSzVghtcWQpMzRwAalONTFDHsTK8FRMIPnksBcOc8P vXJRDxIFqEXgKWXIlP9xwbjfhuUk7aqevjsA3Sui27N5WVk2mNEHH/EJr33vpFZiudTn 9w+dpQL20tutgYLiE7Cekz/mAqroKJQA0mCL216F1q+nKwh8oq8eZYz4i1xqPXoZpJG8 pa8VQZBYj0yjXYzqpKXzIbrl7zOUQJUoqXos9ppaIH3PrcIGpOrGxdTHmo4yW/xk34Kv TDOrcKZLV54mzC2xQWOUdM+yJdeeTgfYUNoZRnXz7o5A6dGR0E9gz8U/+uHVCYU1n+cK TZWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717426904; x=1718031704; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=enocrHxjDAlQ0LTPM45Ai8aNzT/SXd/hVjCBZwyU1M4=; b=eYUI9+pCWXKO1oTJO0odGop+aNxDHPiRkv5FcT0+qY+4NSCvSmKa45soBbvptseMWO r8IglLq1+HKoD7WgStn/FgkShsCWpzdZo9CX4N6C2vnR9WlffSlGYAu9Pqpo6GYu500l WGQTAcdwGb000Fu9CA4Fyb1YBRd7dWH65bsywLV0994TN/9gJfAF1uu+BxT8mkgFq/re eU1H2YPNe8JTGOa8DE+G9UoOHqG0X8dvgC+CR8y6HRBPsV3k291NE9rx50IGzUHWgtju mjCVbN3x6pBYPYZ0wCTEEnGFOoCSvaQcYc9jnObrVcFxE2hLX6E1b8HAlLLAwwKpgPbo xQsQ==
X-Gm-Message-State: AOJu0YyPZX/2bVdYNc27WcYyhNLK4hRmSICrtlb25pkvkfNzK10a7Fl5 TwCydKAu7RCuibG7rD/c4DhWKM15QgHLNMfdrvCHC8ZsnIktaA/wFrYEjkEMDlde0fN6I4e5YA6 l09/UJ3iLD6KrVPR/nKa7ow4hKt+hFTDZ
X-Google-Smtp-Source: AGHT+IFuqOPCieIUdg4Sk4oPwAyTZY3Iu7RQW5b6jWT2jy9Kjrcyb49/Lpcy4CZBl2W8J8O6FAhzcD9U5SWAxTrhPpw=
X-Received: by 2002:a5d:6d05:0:b0:356:4cfa:b4b9 with SMTP id ffacd0b85a97d-35e0f25e190mr8427144f8f.2.1717426904154; Mon, 03 Jun 2024 08:01:44 -0700 (PDT)
MIME-Version: 1.0
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Mon, 03 Jun 2024 08:00:00 -0700
Message-ID: <CAAK044QOLRucPZBzeTRBj=m83aXVsFq83zJQgmvYuVVwKTHzFA@mail.gmail.com>
To: "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008cc8c70619fd9c86"
Message-ID-Hash: ARPT63F3F6BVF27XN6RBIM3VTR3IID2F
X-Message-ID-Hash: ARPT63F3F6BVF27XN6RBIM3VTR3IID2F
X-MailFrom: nsd.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tcpm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [tcpm] using SACK info for RTTM?
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/N19Ojy7GrGNusayQ-JIxa0frlT0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Owner: <mailto:tcpm-owner@ietf.org>
List-Post: <mailto:tcpm@ietf.org>
List-Subscribe: <mailto:tcpm-join@ietf.org>
List-Unsubscribe: <mailto:tcpm-leave@ietf.org>

Hi folks,

While I was checking RFC7323, I found the following sentence.

RTTM update processing explicitly excludes segments not updating
SND.UNA.  The original text could be interpreted to allow taking
RTT samples when SACK acknowledges some new, non-continuous
data.

I am a bit curious about the rationale of this sentence.
It seems to me that we cannot measure RTT when we have a gap in packet
sequence with this rule.

Thanks,
--
Yoshi

v2.37.1 | Report a Bug | By Email | System Status