Skip to main content

SCONE-PROTOCL the topic formerly known as SADCDN
bofreq-joras-scone-protocl-the-topic-formerly-known-as-sadcdn-03

Document Type Approved BOF request
Title SCONE-PROTOCL the topic formerly known as SADCDN
Last updated 2024-02-08
State Approved
Editor Matt Joras
Responsible leadership Zaheduzzaman Sarker
Send notices to (None)
bofreq-joras-scone-protocl-the-topic-formerly-known-as-sadcdn-03

Name: SCONEPRO, the topic formerly known as SADCDN.

Description

This BOF is for the continuation of the SADCDN topic as "Securely COmmunicating NEtwork PROperties" (SCONEPRO). This topic was first discussed at DISPATCH at IETF 117, and subsequently at a side meeting at IETF 118, and a virtual side meeting on January 8th, 2024. The name is subject to further change if participants would prefer a new name.

Video traffic, currently constituting 70% of total internet traffic, is projected to increase to 80% by 2028. This growth is driven by new formats like short-form videos and the rise of mobile-first markets. Mobile network operators manage this load by shaping video traffic, but this can degrade the user experience. Video traffic uses Adaptive Bitrate (ABR) schemes to adjust video quality based on network conditions. However, detecting traffic shapers and estimating the shaping rate is complex and often inaccurate. A more effective solution would be for the network operator to signal the shaper rate to the application, allowing it to self-adapt its video traffic. Secure Communication with On-path Network Elements aims to develop a protocol for securely communicating network properties to clients, initially focusing on communicating the maximum achievable bandwidth for a video using QUIC connections.

Fill in the details below. Keep items in the order they appear here.

Required Details

Information for IAB/IESG

The proponents believe that a new working group is required, but our request is for a non-WG forming BOF. Despite this we are actively working on draft charter text and intend to nail down scoping and potential deliverables as much as possible before and at this BOF.

Agenda

  • TBD