IETF Logo Mail Archive

Re: WGLC for Datagram Extension

Paul Vixie <paul@redbarn.org> Thu, 16 September 2021 22:54 UTC

Return-Path: <paul@redbarn.org>
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 694843A11D0; Thu, 16 Sep 2021 15:54:24 -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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=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 5Jh-lJEf3AkI; Thu, 16 Sep 2021 15:54:20 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B69F3A11CF; Thu, 16 Sep 2021 15:54:15 -0700 (PDT)
Received: from [192.168.1.51] (unknown [85.191.11.218]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 0C3027599C; Thu, 16 Sep 2021 22:54:11 +0000 (UTC)
Subject: Re: WGLC for Datagram Extension
To: Eliot Lear <lear@lear.ch>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, QUIC WG <quic@ietf.org>, QUIC WG Chairs <quic-chairs@ietf.org>
References: <CALGR9oaZ4L_yJPhm11Gym8Rxc0nq6H=mCpLGsH_eMGVHer0uEA@mail.gmail.com> <75277e56-e02e-d530-3c0a-e5d604daf5ad@lear.ch>
From: Paul Vixie <paul@redbarn.org>
Message-ID: <8f8aef42-d7fd-7582-ea75-87ec80174f17@redbarn.org>
Date: Thu, 16 Sep 2021 15:54:09 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 PostboxApp/7.0.49
MIME-Version: 1.0
In-Reply-To: <75277e56-e02e-d530-3c0a-e5d604daf5ad@lear.ch>
Content-Type: multipart/alternative; boundary="------------1648909E79A1CD5028A7ADF8"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qb3yVXWx735qJIQzgjXkHaZb63U>
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: Thu, 16 Sep 2021 22:54:25 -0000


Eliot Lear wrote on 9/16/2021 2:00 PM:
> Hi Lucas,
>
> I just have one question:
>
>> DATAGRAM frames belong to a QUIC connection as a whole, and are not 
>> strongly associated with any stream ID at the QUIC layer
>
> What does "strongly associated" mean in this context?  Apologies if 
> this is well trodden ground.

i'm pretty sure it's what in pre-QUIC times, would be called a "flow" or 
a "UDP 4-tuple".

vixie

-- 
Sent from Postbox <https://www.postbox-inc.com>

v2.23.0 | Report a Bug | By Email