Internet-Draft Agent-Accel-Framework July 2026
Li & Song Expires 20 January 2027 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-li-opsawg-agent-accel-framework-00
Published:
Intended Status:
Informational
Expires:
Authors:
J. Li
China Mobile
J. Song
China Mobile

A Framework for Agent-Aware Network Acceleration Services in Home Broadband Access

Abstract

This document describes a framework for providing AI agents with differentiated network acceleration services in home broadband access environments.

The framework introduces a Network Acceleration SKILL, provided by the network operator, through which agents subscribe to and request acceleration services directly from the Broadband Remote Access Server (Broadband Remote Access Server). The Broadband Remote Access Server, augmented with a control plane agent, processes acceleration requests, coordinates authorization with the Authentication, Authorization, and Accounting server, and applies per-agent Quality of Service policies on its data plane.

A key motivation is to evolve the currently rigid home broadband service model — where plans are fixed on monthly or yearly cycles with static rate limiting — toward a dynamic subscription model that supports on-demand purchase and management of acceleration resources such as time duration or traffic volume.

A fundamental design constraint is that existing broadband access procedures, including Customer Premises Equipment authentication, IPv6 prefix delegation, and subscriber billing, remain unmodified.

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 2 January 2027.

▲

Table of Contents

1. Introduction

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.

Home broadband access networks provide connectivity through a well-established architecture: the Customer Premises Equipment (Customer Premises Equipment) authenticates with a Broadband Remote Access Server (Broadband Remote Access Server) via IP over Ethernet, the Broadband Remote Access Server communicates with Authentication, Authorization, and Accounting servers for subscriber authentication and policy authorization, and IPv6 prefixes are delegated to the Customer Premises Equipment via DHCPv6 Prefix Delegation [RFC3633] for address allocation within the home network.

As AI agents become integral to home environments, they exhibit diverse network requirements that the current infrastructure cannot address. A video surveillance agent requires sustained uplink bandwidth; an interactive voice assistant demands low-latency paths; a general-purpose AI agent needs balanced throughput for multi-modal communication.

Moreover, the current home broadband service model is rigid. Subscribers purchase plans on monthly or yearly cycles, and network rate limiting is typically configured as static Committed Access Rate (Committed Access Rate) policies on the Broadband Remote Access Server. There is no mechanism for fine-grained, on-demand service differentiation — a subscriber cannot, for example, purchase two hours of premium acceleration for a specific agent, or buy a traffic-based acceleration package.

This document proposes a framework that addresses both needs:

The design is guided by the following principles:

Zero modification to existing infrastructure

The Customer Premises Equipment, DHCPv6 procedures, IP over Ethernet authentication, and subscriber billing flows are not modified.

Agent-initiated service request

Agents actively request acceleration through a standardized SKILL, rather than relying on the network to infer agent presence.

Compatibility with existing Authentication, Authorization, and Accounting

The framework leverages existing Authentication, Authorization, and Accounting infrastructure (RADIUS or Diameter) with incremental extensions.

1.1. Scope

This document defines the architectural framework, the service model, and the interaction flows among the participating entities. Detailed protocol specifications, byte-level formats, and Quality of Service implementation mechanisms are deferred to companion documents.

2. Terminology

Agent: A software entity within the home network that acts autonomously or semi-autonomously. Agents possess a pre-assigned Agent-ID and are capable of invoking the Network Acceleration SKILL.

Agent-ID: An opaque identifier that uniquely identifies an agent. Assumed to be assigned prior to the acceleration request.

Network Acceleration SKILL: An operator-provided interface that enables agents to subscribe to, request, and manage network acceleration services.

Acceleration Service Level: A defined tier of network service quality that an agent may request through the SKILL.

Broadband Remote Access Server Control Plane Agent: A software component within the Broadband Remote Access Server that processes acceleration requests, coordinates with the Authentication, Authorization, and Accounting server, and installs Quality of Service policies on the Broadband Remote Access Server data plane.

Dynamic Service Subscription: A service model where acceleration resources can be purchased and consumed on demand (by duration, volume, or event), as opposed to static monthly or yearly broadband plans.

3. Architecture

3.1. Overview

The architecture introduces a service overlay on the existing broadband access infrastructure. Four entities participate:

 ┌─────────────── Home Network ─────────────────┐
 │                                              │
 │  ┌─────────────────────┐      ┌──────────┐   │
 │  │       Agent         │      │   CPE    │   │
 │  │                     │      │          │   │
 │  │  ┌───────────────┐  │      │  (zero   │   │
 │  │  │ Network       │  │      │  change) │   │
 │  │  │ Acceleration  │  │      │          │   │
 │  │  │    SKILL      │  │      │          │   │
 │  │  │  (operator-   │  │      │          │   │
 │  │  │   provided)   │  │      │          │   │
 │  │  └───────────────┘  │      └─────┬────┘   │
 │  │  Agent-ID · Token   │            │        │
 │  └──────────┬──────────┘            │        │
 │             │                       │        │
 └─────────────┼───────────────────────┼────────┘
               │                       │
               │  1. Acceleration      │ IPv6 routing
               │    Request            │ (existing)
               │    (via SKILL)        │
               │                       │
               ▼                       │
  ┌─────────────────────────────────────────────┐
  │                    BRAS                     │
  │                                             │
  │  ┌───────────────────────────────────────┐  │
  │  │ Control Plane Agent                   │  │
  │  │                                       │  │
  │  │  1. Receive request, extract Agent-ID │  │
  │  │     + source IPv6                     │  │
  │  │  2. Determine subscriber from PD table│  │
  │  │  3. Request authorization ────────────┼──┼─►3
  │  │  5. Install QoS policy ◄──────────────┼──┼──4
  │  └──────────────┬────────────────────────┘  │  │
  │                 │                           │  │
  │  ┌──────────────▼────────────────────────┐  │  │
  │  │ Data Plane                            │  │  │
  │  │  6. Per-agent QoS enforcement         │  │  │
  │  │     (match src IPv6 → apply policy)   │  │  │
  │  └───────────────────────────────────────┘  │  │
  └─────────────────────────────────────────────┘  │
               │                                   │
               │        3. CoA-Request             │
               │           (Subscriber-ID,         │
               │            Agent-ID,              │
               │            Service-Level)         │
               │                                   │
               │        4. CoA-Ack                 │
               │           (Authorized QoS)        │
               │                                   │
               ▼                                   │
      ┌─────────────────────┐                      │
      │     AAA Server      │◄─────────────────────┘
      │                     │
      │  · Subscription mgmt│
      │  · Authorization    │
      │  · Accounting       │
      │  · Resource tracking│
      └─────────────────────┘
Figure 1: Architecture Overview

The core idea: the agent, after obtaining IP connectivity through standard procedures, uses the Network Acceleration SKILL to send an acceleration request directly to the Broadband Remote Access Server. The Broadband Remote Access Server Control Plane Agent processes this request, verifies the agent's credentials with the Authentication, Authorization, and Accounting server, and installs Quality of Service policies on the data plane. Subsequent traffic from the agent receives differentiated treatment.

3.2. Entity Roles

Agent: The service requester. Possesses an Agent-ID, integrates the SKILL, and holds a credential for authentication. Invokes the SKILL when acceleration is needed.

Customer Premises Equipment: Zero modification required. Continues existing functions: IP over Ethernet authentication, DHCPv6-PD client (toward Broadband Remote Access Server), DHCPv6 server (toward home devices), IPv6 routing. The agent's acceleration request traverses the Customer Premises Equipment as a regular IPv6 packet.

Broadband Remote Access Server: Extended with a Control Plane Agent (processes requests, manages policies) and data plane enhancement (per-agent Quality of Service entries keyed by IPv6 source address). Determines the subscriber by matching the agent's source IPv6 against the existing Prefix Delegation table.

Authentication, Authorization, and Accounting Server: Authorization and billing authority. Extended to support agent service subscriptions, per-agent authorization decisions, and per-agent usage accounting. Underlying RADIUS or Diameter infrastructure is reused with new attributes.

3.3. Compatibility with Existing Broadband

The acceleration service operates as a strict overlay:

  • Customer Premises Equipment IP over Ethernet authentication: unchanged.

  • DHCPv6 Prefix Delegation (Broadband Remote Access Server to Customer Premises Equipment): unchanged.

  • Customer Premises Equipment sub-delegation to home devices: unchanged.

  • Subscriber base billing: unchanged.

Only two new interactions are introduced: Agent-to-Broadband Remote Access Server (acceleration signaling) and an extension of Broadband Remote Access Server-to-Authentication, Authorization, and Accounting (agent authorization within the subscriber context).

4. Service Framework

4.1. SKILL-based Service Subscription

The Network Acceleration SKILL is a software component published by the network operator. It serves as the standardized interface between AI agents and the broadband acceleration service.

When an agent determines that its application requires enhanced network performance, it invokes the SKILL to subscribe to an acceleration service. The SKILL handles all protocol interactions with the Broadband Remote Access Server — message formatting, endpoint discovery, credential management, and error handling — so that the agent developer interacts only with a high-level API.

The SKILL exposes the following logical operations:

request_acceleration

Subscribe to a specific acceleration service level for a given duration or traffic volume. Returns a session handle and the granted Quality of Service parameters.

query_status

Query the status and remaining resources of an active acceleration session.

release_acceleration

Terminate an active acceleration session and release network resources.

list_service_levels

Discover available acceleration tiers and their descriptions.

Broadband Remote Access Server endpoint discovery (how the SKILL learns the Broadband Remote Access Server service address) MAY be accomplished through DNS SRV records, DHCPv6 options, or operator pre-configuration, depending on the deployment.

4.2. Dynamic Service Model

A key motivation for this framework is to evolve the home broadband service model beyond its current rigidity.

Current model

Subscribers purchase broadband plans on monthly or yearly cycles. Network rate limiting is configured as static Committed Access Rate (Committed Access Rate) policies on the Broadband Remote Access Server. All devices behind a subscriber's Customer Premises Equipment receive the same service level. There is no mechanism for per-device or per-application differentiation, and no way to purchase temporary or usage-based service upgrades.

Proposed model

The acceleration service introduces dynamic, on-demand subscription alongside the base broadband plan. Subscribers (or their agents) can purchase acceleration resources in flexible units:

  • Time-based: Purchase N hours of premium acceleration for a specific agent.

  • Volume-based: Purchase N gigabytes of accelerated traffic.

  • Event-driven: Activate acceleration for the duration of a specific event (e.g., a video conference).

This model enables personalized, differentiated services that are not possible with the current static plan structure. The Authentication, Authorization, and Accounting server tracks acceleration resource consumption per agent and enforces limits (time expiry, volume exhaustion), providing the foundation for flexible billing and service management.

5. Interaction Flows

This section describes the complete interaction sequences among the four entities. These flows are the core of the framework.

5.1. Acceleration Registration

The following sequence describes how an agent requests and obtains acceleration service.

Prerequisites: The agent has obtained an IPv6 address through standard DHCPv6 from the Customer Premises Equipment. The Customer Premises Equipment has completed IP over Ethernet authentication with the Broadband Remote Access Server. The subscriber session is active.

  Agent              CPE              BRAS              AAA Server
    |                 |                 |                    |
    |  [Prerequisites met:              |                    |
    |   Agent has IPv6 address,         |                    |
    |   CPE-BRAS session active]        |                    |
    |                 |                 |                    |
    |==================Step 1: Agent invokes SKILL===========|
    |                 |                 |                    |
    |  The SKILL constructs an acceleration request          |
    |  containing Agent-ID, credential, requested            |
    |  service level, Request De/Activation Action,          |
    |  and duration/volume parameters.                      |
    |                 |                 |                    |
    |                 |                 |                    |
    |===============Step 2: Request traverses home network===|
    |                 |                 |                    |
    |--Acceleration--►|----route-------►│                    |
    |  Request        |                 |                    |
    |  dst=BRAS       |  CPE forwards   |                    |
    |  src=Agent IPv6 |  as normal      |                    |
    |  {Agent-ID,     |  IPv6 packet,   |                    |
    |   Credential,   |  no special     |                    |
    |   Service-Level,|  processing     |                    |
    |   Action,       |                 |                    |
    |   Duration/     |                 |                    |
    |   Volume}       |                 |                    |
    |                 |                 |                    |
    |                 |                 |                    |
    |==================Step 3: BRAS Control Plane============|
    |                 |      Agent processes request ===     |
    |                 |                 |                    |
    |                 |                 | 3a. Extract source |
    |                 |                 |     IPv6 from      |
    |                 |                 |     packet header  |
    |                 |                 |                    |
    |                 |                 | 3b. Extract Agent- |
    |                 |                 |     ID and service |
    |                 |                 |     parameters from|
    |                 |                 |     payload        |
    |                 |                 |                    |
    |                 |                 | 3c. Match source   |
    |                 |                 |     IPv6 against   |
    |                 |                 |     PD table to    |
    |                 |                 |     determine      |
    |                 |                 |     Subscriber-ID  |
    |                 |                 |                    |
    |                 |                 | 3d. Verify         |
    |                 |                 |     credential     |
    |                 |                 |                    |
    |                 |                 |                    |
    |==================Step 4: Authorization=================|
    |                 |                 |                    |
    |                 |                 |--CoA-Request------►|
    |                 |                 |  {Subscriber-ID,   |
    |                 |                 |   Agent-ID,        |
    |                 |                 |   Service-Level,   |
    |                 |                 |   Action,          |
    |                 |                 |   Duration/Volume} |
    |                 |                 |                    |
    |                 |                 |  AAA checks:       |
    |                 |                 |  - Has subscriber  |
    |                 |                 |    purchased agent |
    |                 |                 |    acceleration?   |
    |                 |                 |  - Is Agent-ID     |
    |                 |                 |    authorized      |
    |                 |                 |    under this      |
    |                 |                 |    subscriber?     |
    |                 |                 |  - Is the requested|
    |                 |                 |    service level   |
    |                 |                 |    within the      |
    |                 |                 |    subscription?   |
    |                 |                 |  - Are resources   |
    |                 |                 |    (time/volume)   |
    |                 |                 |    available?      |
    |                 |                 |                    |
    |                 |                 |◄--CoA-Ack----------|
    |                 |                 |  {Authorized-Level,|
    |                 |                 |   QoS-Parameters,  |
    |                 |                 |   Resource-Limits} |
    |                 |                 |                    |
    |                 |                 |                    |
    |==================Step 5: Policy installation===========|
    |                 |                 |                    |
    |                 |                 | 5a. Install QoS    |
    |                 |                 |     policy on data |
    |                 |                 |     plane:         |
    |                 |                 |     {Agent IPv6 →  |
    |                 |                 |      priority,     |
    |                 |                 |      bandwidth,    |
    |                 |                 |      latency policy|
    |                 |                 |      scheduling}   |
    |                 |                 |                    |
    |                 |                 | 5b. Start resource |
    |                 |                 |     tracking       |
    |                 |                 |     (timer and/or  |
    |                 |                 |      counters)     |
    |                 |                 |                    |
    |                 |                 |                    |
    |==================Step 6: Confirmation==================|
    |                 |                 |                    |
    |◄────────────────Acceleration Ack--|                    |
    |  {Session-ID,   |                 |                    |
    |   Granted-QoS,  |                 |                    |
    |   Resource-     |                 |                    |
    |    Limits,      |                 |                    |
    |   Expires-At}   |                 |                    |
    |                 |                 |                    |
Figure 2: Acceleration Registration Flow

In Step 3c, the Broadband Remote Access Server determines the subscriber identity by matching the agent's source IPv6 address against the Prefix Delegation table. This table, already maintained by the Broadband Remote Access Server for standard operations, maps each delegated prefix to a subscriber session. Since the agent's IPv6 address falls within the subscriber's delegated prefix, this lookup yields the subscriber identity without any new mechanism.

In Step 4, if authorization fails (e.g., the subscriber has not purchased acceleration services, or the Agent-ID is not registered), the Authentication, Authorization, and Accounting server returns a negative response and the Broadband Remote Access Server informs the agent that the request is denied. The agent's traffic continues to receive the subscriber's default (non-accelerated) service.

5.2. Acceleration in Effect

Once the policy is installed, the agent's data traffic receives differentiated service as it traverses the Broadband Remote Access Server.

The Broadband Remote Access Server data plane may identify distinct Agents either via IPv6 addresses or via an IPv6 extension header carrying an Agent ID. The former approach has the benefit of requiring no modifications to the data plane, while the latter enables direct binding between Agent IDs and service policies.

Non-agent traffic (from devices that have not registered for acceleration) continues to receive the subscriber's default Quality of Service policy, unaffected by the acceleration service.

The Broadband Remote Access Server continuously tracks resource consumption (elapsed time, traffic volume) for each active acceleration session. When a resource limit is reached (time expires or volume exhausted), the Broadband Remote Access Server automatically removes the Quality of Service policy and notifies both the agent and the Authentication, Authorization, and Accounting server, as described in Section 5.3.

5.3. Acceleration Release

Acceleration service terminates through three mechanisms: agent-initiated release, resource exhaustion, and timeout. The following sequence describes the complete release flow.

  Agent              CPE              BRAS              AAA Server
    |                 |                 |                    |
    |  === Trigger: one of the following ===                 |
    |  - Agent invokes SKILL release_acceleration            |
    |  - Resource limit reached (time/volume exhausted)      |
    |  - Session timeout expired                             |
    |                 |                 |                    |
    |                 |                 |                    |
    |==================Step 1: Release request===============|
    |                 |                 |                    |
    |--Release-------►│-----route------►│                    |
    |  Request        |                 |                    |
    |  {Session-ID}   |  (If agent-     |                    |
    |                 |   initiated;    |                    |
    |                 |   for resource  |                    |
    |                 |   exhaustion,   |                    |
    |                 |   this step is  |                    |
    |                 |   internal)     |                    |
    |                 |                 |                    |
    |                 |                 |                    |
    |===Step 2: BRAS Control Plane Agent processes release ==|
    |                 |                 |                    |
    |                 |                 | 2a. Locate active  |
    |                 |                 |     acceleration   |
    |                 |                 |     session by     |
    |                 |                 |     Session-ID     |
    |                 |                 |                    |
    |                 |                 | 2b. Remove QoS     |
    |                 |                 |     policy from    |
    |                 |                 |     data plane     |
    |                 |                 |                    |
    |                 |                 | 2c. Collect final  |
    |                 |                 |     usage stats:   |
    |                 |                 |     - total bytes  |
    |                 |                 |     - session      |
    |                 |                 |     - release      |
    |                 |                 |                    |
    |==================Step 3: Accounting report=============|
    |                 |                 |                    |
    |                 |                 |--Accounting-Req---►|
    |                 |                 |                    |
    |                 |                 |◄-Accounting-Resp---|
    |                 |                 |  {Acknowledged}    |
    |                 |                 |                    |
    |                 |                 |                    |
    |==================Step 4: Cleanup=======================|
    |                 |                 |                    |
    |                 |                 | 4a. Remove agent   |
    |                 |                 |     entry from     |
    |                 |                 |     active table   |
    |                 |                 |                    |
    |                 |                 | 4b. Release all    |
    |                 |                 |     associated     |
    |                 |                 |     resources      |
    |                 |                 |                    |
    |                 |                 |                    |
    |==================Step 5: Confirmation==================|
    |                 |                 |                    |
    |◄────────────────Release Ack-------|                    |
    |  {Session-ID,   |                 |                    |
    |   Final-Stats,  |                 |                    |
    |   Release-      |                 |                    |
    |    Reason}      |                 |                    |
    |                 |                 |                    |
Figure 3: Acceleration Release Flow

Release triggers in detail:

Agent-initiated: The agent invokes the SKILL's release_acceleration function when it no longer needs acceleration (e.g., task completed). The SKILL sends a release request to the Broadband Remote Access Server, triggering the full flow above.

Resource exhaustion: The Broadband Remote Access Server data plane continuously updates resource counters. When the authorized duration expires or the authorized traffic volume is consumed, the Broadband Remote Access Server Control Plane Agent automatically initiates the release sequence internally (Step 1 is skipped; processing begins at Step 2). The agent is notified via the Release Ack with the release reason set to "resource exhausted".

Timeout: If the Broadband Remote Access Server observes no traffic from the agent for a configurable inactivity period AND has not received any update from the agent, the session is considered stale and is released. This prevents resource leakage from agents that disconnect abruptly.

In all cases, the Broadband Remote Access Server sends a final Accounting-Request to the Authentication, Authorization, and Accounting server (Step 3), ensuring that usage records are complete regardless of how the session was terminated.

6. BRAS-AAA Protocol Extension Considerations

Both RADIUS [RFC2865] and Diameter are deployed as Authentication, Authorization, and Accounting protocols in home broadband access networks. Different operators adopt different protocols based on their network architecture. The acceleration service requires incremental extensions to both.

Authorization: The CoA exchange [RFC5176] (RADIUS) or its Diameter equivalent requires new attributes to carry:

Accounting: Existing Accounting-Request messages require new attributes for per-agent usage:

These are additive attributes within existing message types. No new commands are defined. Authentication, Authorization, and Accounting servers that do not recognize the new attributes ignore them per standard protocol behavior.

7. Security Considerations

Security considerations for this framework are deferred to companion specifications. The following areas are identified for future analysis:

8. IANA Considerations

This document is a framework and does not define new protocol elements. Companion specifications will include appropriate IANA registration requests.

9. References

9.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.

9.2. Informative References

[RFC2865]
Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, DOI 10.17487/RFC2865, , <https://www.rfc-editor.org/info/rfc2865>.
[RFC5176]
Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B. Aboba, "Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)", RFC 5176, DOI 10.17487/RFC5176, , <https://www.rfc-editor.org/info/rfc5176>.
[RFC8415]
Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A., Richardson, M., Jiang, S., Lemon, T., and T. Winters, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 8415, DOI 10.17487/RFC8415, , <https://www.rfc-editor.org/info/rfc8415>.
[RFC3633]
Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6", RFC 3633, DOI 10.17487/RFC3633, , <https://www.rfc-editor.org/info/rfc3633>.

Index

A B C I Q

Authors' Addresses

Jinming Li
China Mobile
Beijing
China
Jian Song
China Mobile
Beijing
China