Re: [quicwg/base-drafts] WIP: Begin lightly abstracting over the use of UDP as the underlying transport (#4043)

Lucas Pardue <notifications@github.com> Fri, 21 August 2020 11:38 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 7F68A3A084B for <quic-issues@ietfa.amsl.com>; Fri, 21 Aug 2020 04:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Level:
X-Spam-Status: No, score=-1.483 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_24=1.618, 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 WXGMtUqVQ3M2 for <quic-issues@ietfa.amsl.com>; Fri, 21 Aug 2020 04:38:09 -0700 (PDT)
Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 568703A0842 for <quic-issues@ietf.org>; Fri, 21 Aug 2020 04:38:09 -0700 (PDT)
Received: from github-lowworker-0f7e7fd.ash1-iad.github.net (github-lowworker-0f7e7fd.ash1-iad.github.net [10.56.110.17]) by smtp.github.com (Postfix) with ESMTP id AB2C67A0074 for <quic-issues@ietf.org>; Fri, 21 Aug 2020 04:38:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1598009888; bh=UlFd67anJySdBUKFK3IkJgM219clpDjsMBGnycV1vlw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=akJfVkZbKHWeCJ0p4zNCrSMj2SN+m4TcXh/KtthTLkGwQamuxaC9bfDNEVaE67/ZH SqdjPOD9mEaLVkr+ilBiKDhtqHvVn+WnvMFyJQ4vSskooYb44jfECbK6ERcOUEEANB hSrxvl/p+FlQeGKYOvSfgMRUarmxG4WXpTA87NP4=
Date: Fri, 21 Aug 2020 04:38:08 -0700
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5KRIONK4QP5RCXE2N5JOJSBEVBNHHCROOLIU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/4043/review/472418488@github.com>
In-Reply-To: <quicwg/base-drafts/pull/4043@github.com>
References: <quicwg/base-drafts/pull/4043@github.com>
Subject: Re: [quicwg/base-drafts] WIP: Begin lightly abstracting over the use of UDP as the underlying transport (#4043)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f3fb220650a9_3af31964785c0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/UUm9UrdQpBSKOcnasSgwiWy81to>
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: Fri, 21 Aug 2020 11:38:11 -0000

@LPardue commented on this pull request.



> @@ -263,6 +266,17 @@ Application:
 
 : An entity that uses QUIC to send and receive data.
 
+Underlying transport protocol:
+
+: The underlying protocol with which QUIC packet are sent.  The underlying
+  transport protocol is conventionally UDP over IP.
+
+Underlying transport datagram:
+
+: A message of the underlying transport protocol, which when used by QUIC will
+  contain multiple QUIC packets. Calling this a "datagram" and not a "packet"
+  emphasizes the message-oriented nature of the underlying transport, and helps
+  distinguish these from QUIC packets.

Are you suggesting that that the underling transport has to be message based? That seems to be a large caveat that restricts the value of these changes.

-- 
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/4043#pullrequestreview-472418488