Re: [quicwg/base-drafts] Invariant independent (#3684)

Gorry Fairhurst <notifications@github.com> Tue, 26 May 2020 10:45 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 036CB3A0AC3 for <quic-issues@ietfa.amsl.com>; Tue, 26 May 2020 03:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-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 (1024-bit key) header.d=github.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 mF4tA24VaKoY for <quic-issues@ietfa.amsl.com>; Tue, 26 May 2020 03:45:06 -0700 (PDT)
Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 333883A0AC2 for <quic-issues@ietf.org>; Tue, 26 May 2020 03:45:06 -0700 (PDT)
Received: from github-lowworker-0eea13f.ash1-iad.github.net (github-lowworker-0eea13f.ash1-iad.github.net [10.56.109.26]) by smtp.github.com (Postfix) with ESMTP id CEBDC260D70 for <quic-issues@ietf.org>; Tue, 26 May 2020 03:45:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1590489904; bh=5fOfoK/gW3FBbPqlWQkAMDMos2LzKVKzvKwvbvI8WIA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vvYCq4iTFM5fXc7x0vmqjiSTnCyLsov53yIIGxOw2gyOBQPxXqT67DYQa3MY61L3j JiIuslbhoUBMA6IphQ7wtUsm9e4EUIF8muumLNYvDbRiCdiMvyoa3lHaQkmotsd1hw DKgbNWCaZnKkurOpWga9FpN3d1c5UM+zuoAlxuH8=
Date: Tue, 26 May 2020 03:45:04 -0700
From: Gorry Fairhurst <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6E64CK4SBS627MDH543DKDBEVBNHHCKIHBQM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3684/review/418178595@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3684@github.com>
References: <quicwg/base-drafts/pull/3684@github.com>
Subject: Re: [quicwg/base-drafts] Invariant independent (#3684)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5eccf330872c5_45a3f86ef0cd9646659fc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gorryfair
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/5wlqMfzjyxdOiVzTK3kgIzk32ig>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 May 2020 10:45:08 -0000

@gorryfair commented on this pull request.



>  # QUIC Packet Headers
 
-A QUIC packet is the content of the UDP datagrams exchanged by QUIC endpoints.
-This document describes the contents of those datagrams.
+QUIC endpoints exchange UDP datagrams that contain one or more QUIC packets.
+This section describes the invariant characteristics of a QUIC packet.  A
+version of QUIC could permit multiple QUIC packets in a single UDP datagram, but
+the invariant properties only describe the first packet in a datagram.

So if we go down this path I think we need carefully to consider each transport mechanism. And the fate of multiplexed flows start to become entangled, such as when a sender chooses a smaller size or DSCP marking because that endpoint expects a characteristic treatment; the unit of loss can be different to the unit of retransmission; PMTUD will need tighter language; pacing may be impacted;  - basically it makes the transport more complex, if that's needed let's try and explain why and understand the constraints - e.g. do we need rules to say when not to multiplex multiple QUIC packets into one IP packet? 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3684#discussion_r430320716