RFC 9317 on Operational Considerations for Streaming Media

rfc-editor@rfc-editor.org Sat, 29 October 2022 01:45 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 825F6C14F73F; Fri, 28 Oct 2022 18:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.959
X-Spam-Level:
X-Spam-Status: No, score=-3.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 d8TcW4OEo1Bt; Fri, 28 Oct 2022 18:44:57 -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 D3CEFC14F613; Fri, 28 Oct 2022 18:44:57 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 9FB8055D29; Fri, 28 Oct 2022 18:44:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9317 on Operational Considerations for Streaming Media
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mops@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20221029014457.9FB8055D29@rfcpa.amsl.com>
Date: Fri, 28 Oct 2022 18:44:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/kR_dsvPyLmWkhm4BKGHEUj5eaDQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Oct 2022 01:45:01 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9317

        Title:      Operational Considerations for Streaming Media 
        Author:     J. Holland,
                    A. Begen,
                    S. Dawkins
        Status:     Informational
        Stream:     IETF
        Date:       October 2022
        Mailbox:    jakeholland.net@gmail.com,
                    ali.begen@networked.media,
                    spencerdawkins.ietf@gmail.com
        Pages:      37
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mops-streaming-opcons-12.txt

        URL:        https://www.rfc-editor.org/info/rfc9317

        DOI:        10.17487/RFC9317

This document provides an overview of operational networking and
transport protocol issues that pertain to the quality of experience
(QoE) when streaming video and other high-bitrate media over the
Internet.

This document explains the characteristics of streaming media
delivery that have surprised network designers or transport experts
who lack specific media expertise, since streaming media highlights
key differences between common assumptions in existing networking
practices and observations of media delivery issues encountered when
streaming media over those existing networks.

This document is a product of the Media OPerationS Working Group of the IETF.


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