Draft: draft-ietf-mops-streaming-opcons

Commentary: Also move some expansions and references to first use . 
 From - 
 Hi , - We 've been focused on what endpoints could do to improve streaming media performance , but it does seem helpful to point that out more clearly . Please see if is helpful .
Paragraph (version B):
"Over the Internet" means that a single operator does not have
control of the entire path between media servers and media
clients, so not a "walled garden".
Paragraph (version A):
generalized network performance techniques; while things like
datacenter design and transit network design can be crucial
dependencies for a performant streaming media service, these are
considered independent topics better addressed by other documents.
Paragraph (version B):
generalized network performance techniques; while considerations
such as datacenter design, transit network design, and "walled
garden" optimizations can be crucial components of a performant
streaming media service, these are considered independent topics
better addressed by other documents.
Paragraph (version A):
Implementation of a low-latency live video service can be achieved
with the use of low-latency extensions of HLS (called LL-HLS) I-
D.draft-pantos-hls-rfc8216bis and DASH (called LL-DASH) LL-DASH.
These extensions use the Common Media Application Format (CMAF)
standard MPEG-CMAF that allows the media to be packaged into and
transmitted in units smaller than segments, which are called chunks
in CMAF language.  This way, the latency can be decoupled from the
duration of the media segments.  Without a CMAF-like packaging, lower
latencies can only be achieved by using very short segment durations.
However, using shorter segments means using more frequent intra-coded
frames and that is detrimental to video encoding quality.  CMAF
allows us to still use longer segments (improving encoding quality)
without penalizing latency.
Paragraph (version B):
Implementation of a low-latency live video service can be achieved
with the use of "HTTP Live Streaming (HLS)" RFC8216 by using its low-
latency extension (called LL-HLS) I-D.draft-pantos-hls-rfc8216bis or
with "Dynamic Adaptive Streaming over HTTP (DASH)" MPEG-DASH by using
its low-latency extension (called LL-DASH) LL-DASH.  These extensions
use the Common Media Application Format (CMAF) standard MPEG-CMAF
that allows the media to be packaged into and transmitted in units
smaller than segments, which are called chunks in CMAF language.
This way, the latency can be decoupled from the duration of the media
segments.  Without a CMAF-like packaging, lower latencies can only be
achieved by using very short segment durations.  However, using
shorter segments means using more frequent intra-coded frames and
that is detrimental to video encoding quality.  CMAF allows us to
still use longer segments (improving encoding quality) without
penalizing latency.
Paragraph (version A):
This level of latency is the historically common case for segmented
video delivery using HLS RFC8216 and DASH MPEG-DASH.  This level of
latency is often considered adequate for content like news or pre-
recorded content.  This level of latency is also sometimes achieved
as a fallback state when some part of the delivery system or the
client-side players do not have the necessary support for the
features necessary to support low-latency live streaming.
Paragraph (version B):
This level of latency is the historically common case for segmented
video delivery using HLS and DASH.  This level of latency is often
considered adequate for content like news or pre-recorded content.
This level of latency is also sometimes achieved as a fallback state
when some part of the delivery system or the client-side players do
not have the necessary support for the features necessary to support
low-latency live streaming.
Paragraph (version A):
A simple model of video playback can be described as a video stream
consumer, a buffer, and a transport mechanism that fills the buffer.
The consumption rate is fairly static and is represented by the
content bitrate.  The size of the buffer is also commonly a fixed
size.  The fill process needs to be at least fast enough to ensure
that the buffer is never empty, however, it also can have significant
complexity when things like personalization or advertising insertion
workflows are introduced.
Paragraph (version B):
A simple model of video playback can be described as a video stream
consumer, a buffer, and a transport mechanism that fills the buffer.
The consumption rate is fairly static and is represented by the
content bitrate.  The size of the buffer is also commonly a fixed
size.  The buffer fill process needs to be at least fast enough to
ensure that the buffer is never empty, however, it also can have
significant complexity when things like personalization or
advertising insertion workflows are introduced.
Paragraph (version A):
ABR playback is commonly implemented by streaming clients using HLS
RFC8216 or DASH MPEG-DASH to perform a reliable segmented delivery of
media over HTTP.  Different implementations use different strategies
ABRSurvey, often relying on proprietary algorithms (called rate
adaptation or bitrate selection algorithms) to perform available
bandwidth estimation/prediction and the bitrate selection.
Paragraph (version B):
Adaptive Segmented Delivery attempts to optimize its own use of the
path between a media server and a media client.  ABR playback is
commonly implemented by streaming clients using HLS RFC8216 or DASH
MPEG-DASH to perform a reliable segmented delivery of media over
HTTP.  Different implementations use different strategies ABRSurvey,
often relying on proprietary algorithms (called rate adaptation or
bitrate selection algorithms) to perform available bandwidth
estimation/prediction and the bitrate selection.