IETF Logo Mail Archive

Re: [Webtransport] Demultiplexing in case of unreliable datagrams

virat tara <virattara@gmail.com> Tue, 16 June 2020 18:47 UTC

Return-Path: <virattara@gmail.com>
X-Original-To: webtransport@ietfa.amsl.com
Delivered-To: webtransport@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D57F3A1230 for <webtransport@ietfa.amsl.com>; Tue, 16 Jun 2020 11:47:59 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mMJz9CTj7pkI for <webtransport@ietfa.amsl.com>; Tue, 16 Jun 2020 11:47:57 -0700 (PDT)
Received: from mail-ua1-x92b.google.com (mail-ua1-x92b.google.com [IPv6:2607:f8b0:4864:20::92b]) (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 830463A1231 for <webtransport@ietf.org>; Tue, 16 Jun 2020 11:47:57 -0700 (PDT)
Received: by mail-ua1-x92b.google.com with SMTP id v25so7271434uau.4 for <webtransport@ietf.org>; Tue, 16 Jun 2020 11:47:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kyuVyxT8V6w6MSJQCyM9VA0TkwuL5fUDe11zoIJQLX0=; b=W1/X4Yody8WfpVkoaVCUq15k7k6AnL4y1pDhCmiKBKATqh0fmgWION+6hH0rvVJ2KA F4u+4okPJsz6o+gGBnwuM41AfYaDp/RXE+4IlbIGJXukwmrGkB6pOv3UXn+ewltOCStu WaBzJyWXpsAmyRT3g1cYiMbSHqntZaFDKQ6SN8toLklH0tjXeIiXCNohH2ahrLphk5l2 R3KfMR3kk/Cpc+8OLyt30n0fGaRAdD0i4MB024Mn24meUKKyvnG3F6PVXMYOxyOyA33D bB7YRoQ91DGSnCAp2ogeG/JN7iDKVmBzZAt5/BLTzNEi00LbGX7ix9HcbeCgc4otDTmI TcxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kyuVyxT8V6w6MSJQCyM9VA0TkwuL5fUDe11zoIJQLX0=; b=pszs7CBnt8B2Nn6PUjm0B8HlaPTMzlcn5xC3yA1/KrwG/usQ2RXZMzqyKcdCo6pvDy KJcFhQIUT8tOtOhje92Vrm2vXVSUV1hJVPLwubEPdj6JFDCzUwFhuYBVMkzK7C1ebhFh lI0+hcjJBm//lM4hJHFcEjyhs3mp9n07q4/wXxdymhvrcMzeqeu4cPcyVE4uMG+kNUZ2 SwvL///6+oT8p4zUNVJNajZ0SMwbe7hokyW9TOQXrjpP+N+BUJ4AzIKe50hh+BvozbIy C+oQZouXxm4p8lamprRkn5HAYeFm9NUx27pvHpFcoMRWE9I700p+tHtUEN2onYmeIog4 r9Ig==
X-Gm-Message-State: AOAM531fZfRh7o4rVw9J7Jfxqh+a+tfy29nUySR51WbEwNwOFzhg2jPk aWDZ0lN/vonWbbm/R4/xlBDBIbp95qEKXUuYVAw=
X-Google-Smtp-Source: ABdhPJwa+Sb8ZSwou8qt2/ORwRV/sHk7l/CbgADvboQUGhhbSU9nCU8EQfd+l8vxf9taaJZwiUMf/pnBifbFmpzN19E=
X-Received: by 2002:a9f:22e1:: with SMTP id 88mr3241561uan.19.1592333276265; Tue, 16 Jun 2020 11:47:56 -0700 (PDT)
MIME-Version: 1.0
References: <CAD7QVt=WM_Hajp_UxM1=c=bEMncNfXABqDGkTsiMbfez35-FfA@mail.gmail.com> <CAPDSy+4V-dXbFxYkadyguwmKX7bmt5iH1S0Sf2ESosY_ENHQCg@mail.gmail.com>
In-Reply-To: <CAPDSy+4V-dXbFxYkadyguwmKX7bmt5iH1S0Sf2ESosY_ENHQCg@mail.gmail.com>
From: virat tara <virattara@gmail.com>
Date: Wed, 17 Jun 2020 00:17:43 +0530
Message-ID: <CAD7QVtnL8DMVHAk+-JSSYGaQXuQ12uXHWv_a0Eb5bVuuzEG2QA@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004bc6bb05a837fb30"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/T8SvLfJEQAaUb7Zy7b8mW4MCJ9A>
Subject: Re: [Webtransport] Demultiplexing in case of unreliable datagrams
X-BeenThere: webtransport@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <webtransport.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webtransport>, <mailto:webtransport-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webtransport/>
List-Post: <mailto:webtransport@ietf.org>
List-Help: <mailto:webtransport-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webtransport>, <mailto:webtransport-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jun 2020 18:47:59 -0000

Hi David,

Thanks for the reply, I was talking in the context of this draft
draft-ietf-webtrans-overview-00
<https://tools.ietf.org/html/draft-ietf-webtrans-overview-00> (sorry for
not mentioning it earlier) which mentions pooling as a property of the
WebTransport. Actually, I was studying the ongoing work in WebTransport but
didn't go through draft-vvv-webtransport-quic since it was expired. But
yeah I got it now.

I found 4 drafts related to this work.
1. draft-ietf-webtrans-overview-00
2. draft-vvv-webtransport-quic-01 / draft-vvv-webtransport-http3-01
3. draft-kinnear-webtransport-http2-00

Where drafts under 2nd point are up for discussion as to which one to keep.

Thanks,
Virat

On Tue, Jun 16, 2020 at 10:13 PM David Schinazi <dschinazi.ietf@gmail.com>
wrote:

> Hi Virat,
>
> What are you trying to demultiplex? draft-vvv-webtransport-quic  (as
> currently specified) will create a new QUIC connection per
> QuicTransport object, so there is no need to demultiplex between them. If
> you would like to demultiplex different flows of datagrams in your own
> application, then you can add a demultiplexing identifier of some kind at
> the start of your application payload.
>
> Hope this helps,
> David
>
> On Mon, Jun 15, 2020 at 10:52 AM virat tara <virattara@gmail.com> wrote:
>
>> Hi,
>>
>> In *Section 6* "Transport Properties" there is a point mentioning
>> Pooling Support. In case of unreliable datagrams, how will demultiplexing
>> be done on the receiver end? Streams, on the other hand, have a unique
>> stream ID. I found a draft (draft-schinazi-quic-h3-datagram-03
>> <https://tools.ietf.org/html/draft-schinazi-quic-h3-datagram-03>) that
>> accomplishes this on HTTP/3 but since WebTransport will have its own
>> dedicated connection as mentioned in *Section 1.1 *"Background" how will
>> this be taken forward?
>>
>> Thanks,
>> Virat
>> --
>> Webtransport mailing list
>> Webtransport@ietf.org
>> https://www.ietf.org/mailman/listinfo/webtransport
>>
>

v2.23.0 | Report a Bug | By Email