Applicability & Manageability consideration for SCONE

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 4 April 2026.¶

Copyright Notice

Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

The SCONE protocol is a signaling mechanism that enables on-path network elements to communicate the maximum allowable bit rate to application endpoints, with particular relevance to adaptive bit-rate applications. This document addresses the applicability and manageability considerations of deploying the SCONE protocol within telecommunications provider networks.¶

The SCONE protocol operates on the basis of a UDP 4-tuple. Network elements capable of rate limiting at this granularity can send notifications of the maximum allowable bit rate in each direction of the observed traffic. Such network elements may also drop or delay packets within the corresponding UDP 4-tuple flows. This implies an assumption that on-path network elements have certain capabilities: specifically, the ability to detect and maintain UDP 4-tuple flows, apply rate-limiting policies, and identify flows that include SCONE packets in order to insert throughput advice.¶

In this document, on-path network elements are generally considered within the access part of the telecommunications provider’s network. However, their behavior may differ across access technologies. For example, a wireless access network element may operate differently from one in a fixed broadband network. Wi-Fi access networks represent another case, where enforcement is often per user or per Service Set Identifier (SSID), but visibility into UDP 4-tuples may be limited. Among the different access networks considered, mobile networks offer the most fine-grained visibility into traffic flows and can act at the individual flow level. In mobile networks, the User Plane Function (UPF) in 5G and the Packet Data Network Gateway (P-GW) in 4G can generate throughput advice to guide adaptive applications on a per-flow basis. In wireline broadband networks, by contrast, rate limiting is typically applied at a centralized Broadband Network Gateway (BNG) or at aggregation points where multiple Customer Premises Equipment (CPE) devices connect.¶

Accordingly, applicability and manageability considerations must span a wide range of access-network scenarios, each of which handles per-flow rate limiting differently. This document first describes generic considerations for the SCONE protocol and then provides network-specific considerations where throughput advisory signaling can enhance both resource utilization and user experience.¶

2. Conventions and Definitions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶

3. Terminology

• 4G - Fourth Generation mobile network technology, also known as Long-Term Evolution (LTE), defined by the 3rd Generation Partnership Project (3GPP).¶

• 5G - Fifth Generation Mobile Networks The fifth generation of cellular mobile network technology defined by 3GPP.¶

• Adaptive Bit-Rate (ABR) Video Video streaming technology that adjusts video quality dynamically based on network conditions.¶

• BNG (Broadband Network Gateway) A network element that serves as the access point for subscribers in wireline broadband networks. It establishes and manages subscriber sessions, aggregates traffic from multiple subscriber access nodes, and routes this traffic to the service provider's core network. BNG functions include subscriber authentication, IP address assignment, policy enforcement, and quality of service management. It typically supports subscriber session protocols such as DHCP, PPPoE, or IPoE, and interacts with AAA and DHCP servers to enable secure and managed access to broadband services.¶

• Client App The user-facing application running on an operating system, which receives network throughput advice.¶

• Content Provider Entity or service that delivers media and data content accessed by end-users.¶

• CPE - Customer Premise Equipment CPE refers to networking hardware located at the customer's site and used to connect to a service provider’s network. Typical CPE includes routers, modems, or gateways that provide access and management for residential or enterprise services.¶

• DHCP - Dynamic Host Configuration Protocol A network management protocol used to dynamically assign IP addresses and other configuration parameters to devices on a network, enabling automatic and centralized network configuration.¶

• EPC - The Evolved Packet Core Is the all-IP core architecture for 4G/LTE, responsible for managing user sessions, mobility, and the integration of data and voice traffic over packet-switched networks.¶

• EPS Bearer - Evolved Packet System Bearer In 4G LTE networks, an EPS bearer is a virtual transmission path with specific Quality of Service (QoS) parameters that carries user data between the User Equipment (UE) and the Packet Data Network Gateway (P-GW). The EPS bearer ensures end-to-end delivery of IP packets with particular handling characteristics, such as priority, latency, and guaranteed bit rate. There are two main types: the Default EPS Bearer which provides always-on best-effort connectivity, and Dedicated EPS Bearers configured for services with specialized QoS requirements, such as voice or video.¶

• EPS Gateway In 4G LTE networks, the EPS Gateway primarily refers to the combination of the Serving Gateway (S-GW) and the Packet Data Network Gateway (P-GW). The Serving Gateway routes and forwards user data packets between the E-UTRAN access network and the Packet Data Network, acting as a mobility anchor during handovers. The Packet Data Network Gateway provides connectivity from the user equipment (UE) to external packet data networks, performing functions such as policy enforcement, charging, and lawful interception. Together, these gateways form the core user-plane interface of the Evolved Packet System (EPS).¶

• gNB - Next Generation Node B 5G radio access network node connecting user equipment to the 5G core network.¶

• IPoE IP over Ethernet A protocol that delivers IP packets directly over Ethernet without requiring a login or session establishment, commonly used in broadband networks in conjunction with DHCP for IP address assignment.¶

• LTE - Long-Term Evolution 4G wireless broadband technology and related network architecture.¶

• P-GW - Public Data Network Gateway Is the network function within the Evolved Packet Core (EPC) that provides connectivity between the user equipment and external packet data networks, such as the Internet.¶

• PDU - Protocol Data Unit In 3GPP terminology, a PDU is a unit of information at a given protocol layer, such as an IP packet at the network layer. Specifically in 5G, a PDU Session represents a logical connection that carries one or more PDUs between the User Equipment (UE) and a Data Network (DN) through the User Plane Function (UPF). PDU Sessions support multiple types of PDUs, including IPv4, IPv6, Ethernet frames, and unstructured data, and are associated with one or more QoS Flows that define handling and quality requirements. The PDU framework is essential for managing application data transport and quality of service within the 3GPP system architecture.¶

• PPP - Point-to-Point Protocol A data link layer communication protocol used to establish a direct connection between two nodes, commonly used for dial-up and broadband internet connections to provide authentication, encryption, and compression.¶

• SCONE - Standard Communication with Network Elements Protocol allowing throughput or rate advice signaling from the network to application endpoints.¶

• SMF - Session Management Function 5G network function that manages sessions and enforces policies.¶

• UE - User Equipment The mobile device or endpoint used by the subscriber to access the network.¶

• UPF - User Plane Function 5G core network element responsible for user-plane traffic routing and applying policy decisions.¶

• Wireline Network Broadband network based on fixed infrastructure (e.g., DSL, cable, fiber).¶

4. Generic Applicability and Manageability considerations

5. SCONE Usage in a 5G Network

5G systems are built on a cloud-native Service-Based Architecture (SBA), which provides flexibility for introducing new functions such as SCONE. The User Plane Function (UPF) serves as the natural anchor point for SCONE signaling because it handles packet forwarding, QoS enforcement, and interaction with the Session Management Function (SMF) and Policy Control Function (PCF).¶

+---------+
|   PCF   |
+---------+
     |
     v Policy Rules
+---------+
|   SMF   |
+----+----+
     | Policy Rules
     v
+--------+                 +------------------------+
| Client |<===============>|                        |
|   App  |     SCONE       |                        |
+--------+     Advice      |            UPF         |
|   OS   |                 |                        |
+--------+                 |                        |
|  Modem |                 |                        |
+----+---+                 +------------------------+
     |                             |      |
     |   +-----+                   |      |
     +---+ gNB +-------------------+      |
         +-----+                          |
              |                           v
              v                   +--------------+
     +-----------------+          |  Internet    |
     | Content Provider|          +--------------+
     +-----------------+

6. SCONE Usage in a 4G/LTE Network

In LTE/Evolved Packet Core (EPC) systems as defined by 3GPP [_4G-Arch], SCONE can be integrated at the PDN Gateway (P-GW) or the Serving Gateway (S-GW). Unlike 5G, traffic granularity is bearer-based rather than per flow.¶

Below is an example diagram illustrating SCONE integration within the P-GW:¶

+---------+
|  PCRF   |
+----+----+
     | Flow
     v Policy Rules
+--------+          +--------------+
| Client |<========>|  P-GW        |
|  App   |   SCONE  |              |
+--------+   advice +-------+------+
|   OS   |                  |
+--------+                  |
|  Modem |                  |
+----+---+                  |
     |                      |
     v                      v
  +--+---+              +---+---+
  |  eNB |--------------|  S-GW |
  +--+---+              +---+---+
                            |
                            v
                    +-------------+
                    |  Internet   |
                    +-------------+
                           |
                           v
                    +-----------------+
                    | Content Provider|
                    +-----------------+

7. SCONE usage in a Wireline Network

SCONE can be deployed in wireline broadband networks at key access aggregation points such as Broadband Network Gateways (BNGs) or equivalent subscriber access nodes. These network elements originate throughput advice, signaling maximum sustainable data rates to application endpoints for each subscriber session, typically identified by DHCP, PPP, or IPoE session contexts.¶

Session granularity is typically based on subscriber sessions using PPP, DHCP, or IPoE protocols. Below is a high-level view of SCONE within the wireline network:¶

+----------------+        +-----------------+        +------------------+
|  Subscriber    |<------>|       BNG       |<------>|  Content /       |
|  Session / UE  |  SCONE |                 |  SCONE |  Endpoint        |
+----------------+  Advice|                 |  Advice|                  |
                          |                 |        |                  |
                          +-----------------+        +------------------+

8. SCONE usage in a Wifi Networks

TBD¶

Editor's note : Home, enterprise and campus network have wifi access network. The SCONE client can be in the wifi network for the whole time of the session or there can be handover/offloading case where SCONE client can be moved from cellular network to wifi network or vice versa. The rate limit in such cases usually applied per user/device or SSIDs. This need to be covered in the considerations.¶

9. Security Considerations

Security considerations are included separately in the SCONE protocol documents.¶

10. IANA Considerations

This document has no IANA actions.¶

11. References

12. References

Appendix A. Appendix A. Additional Background details on role of UPF in 5G Mobile Packet Core

               +-----+  Nudm/Nudr  +---------+
               | PCF +-------------+ UDM/UDR |
               +--+--+             +----+----+
                   |                    |
              Npcf |      +-----+       |Nudm
                   +------+ SMF +-------+
                          +--+--+      ___  __
                             | N4     (   )(  )
   +----+   +--------+    +--+--+    (         )    +------------------+
   | UE |---| gNodeB |----| UPF |----( Internet )---| Content Provider |
   +----+   +--------+ N3 +- -+-+ N6  (        )    +------------------+
                              | N9     (__(___)
                            +-+---+
                            | UPF |
                            +-----+

                    +-----+
                    | HSS |
                    +-----+
                       |
                    +-----+          +------+
                    | MME |          | PCRF |
                   /+-----+\         +------+
                  /         \            |
                 /           \           |         ___  __
                /             \          |        /   )(  \
   +----+   +-----+        +------+  +------+    (         )    +----------+
   | UE |---| eNB |--------| S-GW |--| P-GW |----( Internet )---| Content  |
   +----+   +-----+   S1u  +------+  +------+ SGi (        _)   | Provider |
                                                   (__(___)     +----------+

Appendix B. Appendix B. Non-ASCII Characters

This document uses the following kramdown-rfc character escapes for common non-ASCII symbols:¶

• U+00A0 NO-BREAK SPACE → {nbsp}¶

• U+00AD SOFT HYPHEN → {shy}¶

• U+2011 NON-BREAKING HYPHEN → {nbhy}¶

• U+200B ZERO WIDTH SPACE → {zwsp}¶

• U+2060 WORD JOINER → {wj}¶

• U+2013 EN DASH → {ndash}¶

• U+2014 EM DASH → {mdash}¶

• U+201C LEFT DOUBLE QUOTATION MARK → {ldquo}¶

• U+201D RIGHT DOUBLE QUOTATION MARK → {rdquo}¶

• U+2018 LEFT SINGLE QUOTATION MARK → {lsquo}¶

• U+2019 RIGHT SINGLE QUOTATION MARK → {rsquo}¶

• U+20AC EURO SIGN → {euro}¶

Acknowledgments

This document represents collaboration, comments, and inputs from others, including:¶

• Wesley Eddy¶

• Renjie Tang¶

• Kevin Smith¶

• Tina Tsou¶

• Tianji Jiang¶

• Lucas Pardue¶

• Martin Thomson¶

Authors' Addresses