From nobody Fri Sep 17 03:37:24 2021 Return-Path: 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 CEE0B3A1321 for ; Fri, 17 Sep 2021 03:37:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -18.097 X-Spam-Level: X-Spam-Status: No, score=-18.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 BE1CgDyg3MKE for ; Fri, 17 Sep 2021 03:37:17 -0700 (PDT) Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 E55893A131E for ; Fri, 17 Sep 2021 03:37:16 -0700 (PDT) Received: by mail-qk1-x734.google.com with SMTP id ay33so15880585qkb.10 for ; Fri, 17 Sep 2021 03:37:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=etHzBtbUOr+o21TI7dcn+WzqGccqF9VNcN1PQcfP9Rw=; b=UpCKkvPlo4PRZ+s/QVOis1KhFrwBXAb67TqIQ7RMbd8IJTX5F+5CD0f5hg3dwEQNSW tOnXTo1Z/YrZ/hO76+rRvbbULDJO/RQhKZ1M52H2xzYUHYJYrOBeH+F6uSlsfDGVpvAA 3xsugSYohUz82Qgf7FVX9MCSlp64ZsdMO2Jr4cjQObHaq6uqmso9kK8bkcx4u82fpoMR 7d4Y5TU+/nqhc7PsBIBMkE4TBOHbTrRS1TpaZ5VUKQ0IV0C20iQDPFw3BQ940BbWABC6 twmc64SC9gkGNOY+19TXMMxiPaHYHCAOpLgeF+AmHPv0h3un6OFHCMeiDDPyDhriaSrx HphQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=etHzBtbUOr+o21TI7dcn+WzqGccqF9VNcN1PQcfP9Rw=; b=wXMROyyX6EkjhkIEQBXL2y3i5XZy9nwOC/4LAiEtG18kt8eakufa+2x41cgIRtqHan zVh3zZdUzJ0tfJSKsyx8N/6AkC6LE/gL6YKQyptteg1KHxHsK956bDqknNZEo4KCPIBJ mgWBhwryPCOC43zeg+pW9fkv79Qf8Wj6oBMK7/1dMT+Vu8XW4VvZd7zCnNr+g1zotsXM QFvz6SH6zQUUm/QWtpc77dQaVHpKR8dA1Zm14VVhPYD/EsKY+0rWcg0OroFCUF1on0Ol ND8v8P+n6E85s5SQ00/Zg7xR60rxVA9EE7b4pQqhqM1aa6GFJjfpBHAQALM+j7E015XB TlLg== X-Gm-Message-State: AOAM530VntQi+kofDqx72Y4OQLbW/DRDYXIfE22LggbVDTmgItKzZ2dR PPUtYZB/2Cn5EGKVMV7UPwa0vd9ucxnKDTKTdREKRQ== X-Google-Smtp-Source: ABdhPJxK66l0X22/jYLXY1G5Q572eMleiKbDam/4RPjD8mhzmjtXNTrZZqDhEOgUnJzmze6IqoblPKGq494JjRaQALM= X-Received: by 2002:a25:4789:: with SMTP id u131mr12662680yba.531.1631875035390; Fri, 17 Sep 2021 03:37:15 -0700 (PDT) MIME-Version: 1.0 References: <75277e56-e02e-d530-3c0a-e5d604daf5ad@lear.ch> <8f8aef42-d7fd-7582-ea75-87ec80174f17@redbarn.org> In-Reply-To: From: Ian Swett Date: Fri, 17 Sep 2021 06:37:04 -0400 Message-ID: Subject: Re: WGLC for Datagram Extension To: Eliot Lear Cc: Paul Vixie , QUIC WG , Lucas Pardue , QUIC WG Chairs Content-Type: multipart/alternative; boundary="000000000000cdeee105cc2e831a" Archived-At: X-BeenThere: quic@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Main mailing list of the IETF QUIC working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Sep 2021 10:37:22 -0000 --000000000000cdeee105cc2e831a Content-Type: text/plain; charset="UTF-8" On Fri, Sep 17, 2021 at 5:55 AM Eliot Lear wrote: > Hi Paul, > > On 17.09.21 00:54, Paul Vixie wrote: > > > >> 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". > > > Thanks. I interpret it similarly, but perhaps there are conditions > under which the authors anticipated a DATAGRAM being associated with a > STREAM? I dunno. > > That's what H3-datagram does, but it's not in scope for this draft. > Eliot > > > --000000000000cdeee105cc2e831a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Sep 17, 2021 at 5:55 AM Eliot= Lear <lear@lear.ch> wrote:
Hi Paul,

On 17.09.21 00:54, Paul Vixie wrote:
>
>> What does "strongly associated" mean in this context?=C2= =A0 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".


Thanks.=C2=A0 I interpret it similarly, but perhaps there are conditions under which the authors anticipated a DATAGRAM being associated with a
STREAM?=C2=A0 I dunno.

That's what H3-datagram does, but it'= ;s not in scope for this draft.
=C2=A0
Eliot


--000000000000cdeee105cc2e831a--