Internet-Draft ANCP Use Cases November 2026
Yang & Song Expires 20 May 2027 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-yang-ancp-home-app-usecase-00
Published:
Intended Status:
Informational
Expires:
Authors:
F. Yang
China Mobile
J. Song
China Mobile

Use Cases & Requirements for ANCP

Abstract

This document describes use cases for the Access Node Control Protocol in home applications, where a Broadband Network Gateway (BNG/BRAS) exchanges home-application policy with a Home Gateway (HGW). ANCP may operate either between BNG and OLT, or directly between BNG and HGW. When ANCP runs only between BNG and OLT, additional configuration via OMCI is required to reach the HGW. The use cases in this document are illustrated in the mode where ANCP runs directly between BNG and HGW.

The use cases cover three primary scenarios: managed access to operator-hosted large model services, application-aware QoS, and controlled remote access to home LAN resources.

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 20 May 2027.

▲

Table of Contents

1. Introduction

RFC 6320 defines the Access Node Control Protocol (ANCP) between a Broadband Access Server (BNG/BRAS) and an Access Node (AN, e.g., OLT, DSLAM). Standard ANCP is used for line state reporting, port configuration, and QoS coordination at the access node.

In residential PON deployments, ANCP may operate in two operational modes:

The HGW terminates the PPPoE session and acts as the policy enforcement point for home-side applications. Operators wish to provide services for home application without heavyweight device management workflows or static VLAN stitching across HGW, OLT, and BNG.

This document describes the use cases in which the BNG exchanges application policy with the HGW in Mode B, and identifies the protocol areas that may need enhancement to support them. The key motivations are:

1.1. Requirements Language

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.

2. Terminology

ANCP: Access Node Control Protocol, defined in RFC 6320.

BNG/BRAS: Broadband Network Gateway / Broadband Remote Access Server, the NAS in ANCP terminology.

HGW: Home Gateway, the residential gateway terminating the subscriber PPPoE session.

OLT: Optical Line Terminal in the PON access network.

ONU: Optical Network Unit, located at the subscriber side; in many deployments the HGW and ONU are integrated.

OMCI: ONU Management and Control Interface (ITU-T G.988), used for OLT-to-ONU/HGW configuration in PON systems.

Home Agent: Local AI application running on home devices (smart speaker, local PC agent, home panel).

Home LAN: The private subscriber-side network behind the HGW.

3. Scope and Design Principles

  1. ANCP supports two peering topologies: BNG-to-OLT, or BNG-to-HGW. When ANCP peering is BNG-to-OLT only, HGW-targeted policy requires additional OMCI provisioning; ANCP itself does not reach the HGW in this mode. For the use cases of this document, ANCP peering is BNG-to-HGW; the OLT performs transparent TCP forwarding and is not a policy endpoint for these extensions.
  2. Application policy is decoupled from the underlying forwarding path. New services do not require VLAN re-provisioning or end-to-end forwarding changes. Policy is subscriber-session bound and follows the PPPoE session lifecycle. Policy identifiers are address-agnostic. Identification of the application service is independent of IP prefix, destination address, or VLAN assignment.
  3. The HGW is the enforcement point for home-side application policy. Extensions are additive TLVs. Legacy ANCP implementations (BNG-to-OLT) continue to operate unaffected.

4. Use Cases

All use cases in this section are illustrated under Mode B: ANCP runs directly between BNG and HGW, and the OLT transparently relays the ANCP TCP session. In the diagrams, [RFC6320] denotes the ANCP control-plane channel; ---> denotes the user data-plane traffic.

4.1. Managed Large Model Access for Home Agents

Home Agents running on residential devices request access to large model services. The HGW centrally manages model service credentials for home applications. The operator-controlled policy delivered via ANCP instructs the HGW to steer home-agent model requests to the operator-hosted large model platform. The operator retains control over service access without requiring each home agent to maintain independent model endpoint configuration.

  [ANCP: model steering policy + credential reference]
+----------------+                    +----------------+
|      BNG       | <----------------> |      HGW       |
+-------+--------+                    +--------+-------+
        |                                      |
        |      OLT (transparent forward)       |
        +-------<---> OLT <---> ONU <--->------+
                                               |
Operator Large Model Platform  <---------------+
                                               |
Home Agent (Speaker / Home Panel) <------------+

Figure 1: Use Case 1: LLM Access

4.2. Differentiated Service in Application Granularity

Traditional residential value-added services such as remote education and online games often rely on dedicated VLANs. This requires end-to-end VLAN planning and configuration across HGW, OLT, and BNG, which slows service activation. This use case deploys traffic classification on HGW to distinguish applications and uses overlay tunnel to carry traffic. It is not tied to a fixed VLAN or destination prefix. New services can be activated by pushing policy via ANCP without modifying the underlying forwarding path.

  [ANCP: model steering policy + credential reference]
+----------------+                    +----------------+
|      BNG       | <----------------> |      HGW       |
+-------+--------+                    +--------+-------+
        |                                      |
        |      OLT (transparent forward)       |
        +--------<---> OLT <---> ONU <--->-----+
                                               |
Remote Education / Online Game / Home App <----+

Figure 2: Use Case 2: Differentiated Services

4.3. Authorized Remote Access to Home LAN (Person-to-Home Connectivity)

A subscriber's mobile device (outside the home network) accesses authorized home LAN resources such as NAS or cameras. Authorization scope, allowed sources, permitted home destinations, time windows, and bandwidth limits are defined at the BNG and delivered to the HGW via ANCP. The HGW enforces the access control policy. Access is only permitted for authorized sessions; unauthorized probes are rejected. The policy can be revoked on demand.

  [ANCP: access ACL / whitelist / time-window policy]
+----------------+                   +----------------+
|      BNG       | <---------------> |      HGW       |
+-------+--------+                   +--------+-------+
        |                                     |
        |     OLT (transparent forward)       |
        +------<---> OLT <---> ONU <--->------+

Mobile Phone <-------------> NAS / IP Camera / Home LAN

Figure 3: Use Case 3: Remote Access to Home LAN

5. Protocol Requirement Overview

This section identifies the aspects in which the baseline ANCP protocol (RFC 6320) does not yet cover the use cases above, and the directions in which protocol enhancement is expected. RFC 6320 was originally designed for line and port management between a NAS and an access node; its existing TLV space and session model do not directly express home-application policy. The items below are open enhancement topics rather than finalized protocol mechanics; detailed TLV semantics, encoding, and state machines are reserved for a future revision of this document.

5.1. New Peering Model: BNG-to-HGW ANCP

Baseline ANCP defines the peering relationship between NAS and AN (OLT/DSLAM). The ANCP extensions are required to define how an ANCP session can be established and maintained directly between BNG and HGW, including:

  • Session discovery and association between a BNG ANCP peer and the HGW behind a given PPPoE session;
  • Session establishment, keep-alive, and teardown lifecycle aligned with the PPPoE session;
  • Behavior when the ANCP session to the HGW is lost, and the relationship to any parallel BNG-to-OLT ANCP session.

5.2. Home Application Policy TLV Set

Baseline ANCP TLVs carry line rate, port status, and basic configuration parameters. The following policy categories require new TLV definitions:

  • Application Policies: classification rules, tunnels;
  • Service Steering Policy: endpoint and steering instructions for model services;
  • Credential Reference: an opaque reference to model account credentials managed by the HGW;
  • QoS Profile: priority, shaper, and scheduler treatment associated with a service identifier;
  • Remote Access Policy: source whitelist, allowed home destinations, port constraints, time window, and bandwidth limit;
  • Policy Lifecycle: activate, refresh, revoke, and policy versioning.

5.3. Policy State Synchronization and Reporting

Baseline ANCP supports limited status reporting. To support on-demand service activation and revocation, the protocol needs enhancement for:

  • Per-policy installation result (success, partial success, failure with reason) reported from HGW to BNG;
  • Active session and resource state reporting for home services, including remote-access session state;
  • Policy revision synchronization so the BNG and HGW can detect and recover from stale or mismatched policy state.

5.4. Interaction with OMCI in the BNG-to-OLT Mode

When ANCP runs only between BNG and OLT (Mode A), policy reaching the HGW is out of ANCP's scope and relies on OMCI. The enhancement work needs to define the boundary clearly: which policy categories can be mapped onto OMCI configuration, which cannot, and how the two control channels relate. It should be stated explicitly that this document's BNG-to-HGW extensions are not required to be carried over OMCI.

5.5. Interaction with Existing Management Protocols

The relationship between the proposed ANCP policy channel and existing HGW management mechanisms (e.g., [TR-069] CWMP) needs to be scoped: which functions remain under device management, and which are session-bound policy delivered over ANCP. A clear division avoids overlapping or conflicting configuration.

5.6. Open Encoding and Interoperability Issues

The following items remain open and will be addressed in later revisions: - Allocation of TLV type codes and sub-TLV structures within the ANCP TLV registry; - Error and rejection message formats; - Compatibility with existing ANCP implementations that do not recognize the new TLVs.

6. Security Considerations

ANCP sessions between BNG and HGW MUST be authenticated and integrity protected. An attacker must not be able to inject or modify policy messages.

Remote access policy is sensitive. The HGW MUST enforce the least-privilege rules delivered by the BNG. Policy revocation MUST take effect immediately. The HGW MUST log policy installation and remote access events for operator audit. Model credential references are opaque identifiers. The ANCP channel MUST NOT carry raw secrets. Credential material is provisioned separately by secure operator channels.

The address-agnostic service identifier mechanism MUST NOT be used to bypass existing access control or subscriber authorization.

When OMCI is used as an alternate delivery path, OMCI security and authentication requirements also apply. Privacy Considerations Remote access policy and home application policy are subscriber-specific data. Operators MUST handle policy data in compliance with applicable privacy regulations. Logging of home LAN access events MUST be limited to what is required for security and service operation.

7. IANA

TBD.

8. References

8.1. Normative References

[RFC6320]
Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T. Taylor, Ed., "Protocol for Access Node Control Mechanism in Broadband Networks", RFC 6320, DOI 10.17487/RFC6320, , <https://www.rfc-editor.org/rfc/rfc6320>.
[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/rfc/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/rfc/rfc8174>.

8.2. Informative References

[TR-069]
Broadband Forum, "CPE WAN Management Protocol", Broadband Forum TR-069, , <https://www.broadband-forum.org/pdfs/tr-069-1-6-1.pdf>.
[ITU-T-G.988]
ITU-T, "ONU management and control interface (OMCI) specification", ITU-T Recommendation G.988, , <https://www.itu.int/rec/T-REC-G.988-202211-I/en>.

Authors' Addresses

Feng Yang
China Mobile
Xuanwumen West Street
Beijing
China
Jian Song
China Mobile
Xuanwumen West Street
Beijing
China