[rfc-dist] RFC 9223 on Real-Time Transport Object Delivery over Unidirectional Transport (ROUTE)
rfc-editor@rfc-editor.org Wed, 27 April 2022 18:55 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F6DFC1B26E4; Wed, 27 Apr 2022 11:55:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1651085711; bh=tflL34fyksS0WHCQva3auno6Ofig++AwoXTjSaTKPNQ=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=uT67E6GQVUHJQ+o+8GuyX24MLXXuQmf+nR79LA86RsYq6gSXpRRg1MT2WOelvJc4i QJY8l1MaLWDvXkJuWkQX9WKcJTck8vP5y1RQpm1MjI1jUxGcBOJlV3gM4vUxZZ24Zu C72bP6hGvEoQ3KxhNNMPbnre0U6BG0ILZ6XKw02g=
X-Mailbox-Line: From rfc-dist-bounces@rfc-editor.org Wed Apr 27 11:55:11 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF46C1B15E9; Wed, 27 Apr 2022 11:55:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1651085710; bh=tflL34fyksS0WHCQva3auno6Ofig++AwoXTjSaTKPNQ=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=JDcYtKgGpbmXkrcp/KYk0FlIaR/whpf6BHniOIs/IHr2rBTFkPknjyFrokcLDenNg P98NJ85nzVFinjGGS34IFwqe05NZG1xIVx773G5P3JkiyVGh7Kcu/ZlatDdraojgSa Wpnruq9fp1/lymwjofDZ2pqZZwdkbU3+q/LS/2Rg=
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF34C1363E4; Wed, 27 Apr 2022 11:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J5hWPpK2YMql; Wed, 27 Apr 2022 11:55:00 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4750C157B47; Wed, 27 Apr 2022 11:55:00 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id A27B910D60; Wed, 27 Apr 2022 11:55:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Message-Id: <20220427185500.A27B910D60@rfcpa.amsl.com>
Date: Wed, 27 Apr 2022 11:55:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/b-1-A06ASgsgpXLQo7ukiLK8qQQ>
Subject: [rfc-dist] RFC 9223 on Real-Time Transport Object Delivery over Unidirectional Transport (ROUTE)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9223
Title: Real-Time Transport Object Delivery over
Unidirectional Transport (ROUTE)
Author: W. Zia,
T. Stockhammer,
L. Chaponniere,
G. Mandyam,
M. Luby
Status: Informational
Stream: Independent
Date: April 2022
Mailbox: wzia@qti.qualcomm.com,
tsto@qti.qualcomm.com,
lguellec@qti.qualcomm.com,
mandyam@qti.qualcomm.com,
luby@bitripple.com
Pages: 35
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-zia-route-06.txt
URL: https://www.rfc-editor.org/info/rfc9223
DOI: 10.17487/RFC9223
The Real-time Transport Object delivery over Unidirectional Transport
(ROUTE) protocol is specified for robust delivery of Application
Objects, including Application Objects with real-time delivery
constraints, to receivers over a unidirectional transport.
Application Objects consist of data that has meaning to applications
that use the ROUTE protocol for delivery of data to receivers; for
example, it can be a file, a Dynamic Adaptive Streaming over HTTP
(DASH) or HTTP Live Streaming (HLS) segment, a WAV audio clip, etc.
The ROUTE protocol also supports low-latency streaming applications.
The ROUTE protocol is suitable for unicast, broadcast, and multicast
transport. Therefore, it can be run over UDP/IP, including multicast
IP. The ROUTE protocol can leverage the features of the underlying
protocol layer, e.g., to provide security, it can leverage IP
security protocols such as IPsec.
This document specifies the ROUTE protocol such that it could be used
by a variety of services for delivery of Application Objects by
specifying their own profiles of this protocol (e.g., by adding or
constraining some features).
This is not an IETF specification and does not have IETF consensus.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org