IETF Logo Mail Archive

QUIC use with multicast

Gyan Mishra <hayabusagsm@gmail.com> Fri, 17 January 2020 02:05 UTC

Return-Path: <hayabusagsm@gmail.com>
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 9E30C1200B1 for <quic@ietfa.amsl.com>; Thu, 16 Jan 2020 18:05:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 eCcZJS0lYnz3 for <quic@ietfa.amsl.com>; Thu, 16 Jan 2020 18:05:44 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 521C3120099 for <quic@ietf.org>; Thu, 16 Jan 2020 18:05:44 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id x1so24240773iop.7 for <quic@ietf.org>; Thu, 16 Jan 2020 18:05:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=aJKKsy6uJd2rWonZco0Dv22QHHxo5z0Mnjlx/57pYxE=; b=oL8Jf+o+gZtd3vyBOrVx1uIsXpWYzzMzBpFcHwQb3FDXaomO8q6iX2D0jMcRScbQAE RUakRe4ojj6/t1QKUIn4FnLoV1MLOz5c8tmWdrpK1GcmvYULkRam0qlDRKlziAJL8xTb dqKnoQRv8eowBDSKzt6nEGuV23eAJzXYw1e6JOFcJO6LBO4kmTls45fBCvC3fGB0DObZ wSQ84gWJ+S6zTiKqDJ0FRrkI4gPQ4ZJZlQeSdcEnUg/eCN9IIiWDyHoThBjfujdV/G3O G5xE41W81m6wWwXbEwM6S6NnH2sob1+ef4YkQyBw3Wh7r/PgoNCSJaED238e959vej2v Xcyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=aJKKsy6uJd2rWonZco0Dv22QHHxo5z0Mnjlx/57pYxE=; b=Re6CfoFRrNfH0VkR6gQGyoqPgnGMCcfzxcBqbuVSkO8K9tNCxwbrC1DzxI59AR771U MLLdrYL/quYzRjl0cPANQdzDLPp7mwYRjojh1oXgdPLwes2e7l+BelF9pPbGIXHY1uNc I0e3FPgiMPHzIHA2L9rPzJm+8X8+T5F36eC4NWXqYQ45cBz1/yb9sa/A+F+Xgyqp4qvP 3C+k8g55+U+bzenfys76//H9KvHTVwYAbim/r5gwLxjlboqdWqkf6r7Kuq+Y/g2reMaU 9Hicjf8OdXWh5CMF5Kmvj7vzLwvO2cFMQ7DOiSGq/5fvKLbV6htWF81vIGKRRGFF2bCI XrLg==
X-Gm-Message-State: APjAAAXecEOF+ilfRQ8uKUSnhYx55KVi++Jsr+ZHKeRzHXnzPzuvZ9tl LF8X1OUfc2rkiIINLazZK+9r8jitSXO/D8bdtJ3/h2v1
X-Google-Smtp-Source: APXvYqwxwGktxDdR5Trx1kdt3xzPpxDbdRNpr79zWE8uv3BFkpA4MHG4P45nF6nh3Ak//cHAIBVf2O7qsAElWgRH8Vw=
X-Received: by 2002:a6b:7316:: with SMTP id e22mr30151492ioh.205.1579226743272; Thu, 16 Jan 2020 18:05:43 -0800 (PST)
MIME-Version: 1.0
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Thu, 16 Jan 2020 21:05:32 -0500
Message-ID: <CABNhwV38byx28ayEjw5YBJdQ6Oc4BSxnC++rAHMTjHJcLTn2JA@mail.gmail.com>
Subject: QUIC use with multicast
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000d7a5c059c4c616f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/e49B-rcYEjkB77-u92Zd5btlyPY>
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: Fri, 17 Jan 2020 02:05:50 -0000

QUIC WG

Has anyone ever tried using QUIC with multicast RTP UDP streamed using QUIC
transport.

Multicast has always been problematic with use on the internet MBONE and
even on intranets due the unreliable UDP RTP transport for MPEG4 MPEG-TS
and even newer protocols MPED-DASH abs and HLS multicast has struggled with
using UDP transport.

Multicast has thus required stringent end to end QOS in profile guaranteed
scheduling bandwidth hop by hop PHB to ensue no drops to avoid dropping of
I frame resulting in client frozen window and buffering.

Since QUIC is a secure reliable transport and supports unidirectional flows
it would be a perfect fit for multicast.

This would be a game changer for multicast as over the internet which you
don’t have any QOS guarantee.

Kind regards

Gyan


-- 

Gyan  Mishra

Network Engineering & Technology

Verizon

Silver Spring, MD 20904

Phone: 301 502-1347

Email: gyan.s.mishra@verizon.com

v2.23.0 | Report a Bug | By Email