



Network Working Group                                           C. Giese
Internet-Draft                                                   RtBrick
Updates: 6320 (if approved)                                      T. Haag
Intended status: Experimental                              B. Witschurke
Expires: 3 December 2026                             Deutsche Telekom AG
                                                             1 June 2026


                       Access Extensions for ANCP
             draft-lihawi-ancp-protocol-access-extension-14

Abstract

   This document specifies extensions to the Access Node Control
   Protocol (ANCP), defined in RFC6320, to support Passive Optical
   Networks (PON) and evolving DSL technologies such as G.fast.  To
   accommodate these diverse access environments, this document updates
   RFC6320 by modernizing existing terminologies, adapting message
   flows, and defining new Type-Length-Value (TLV) attributes.

About This Document

   This note is to be removed before publishing as an RFC.

   Status information for this document may be found at
   https://datatracker.ietf.org/doc/draft-lihawi-ancp-protocol-access-
   extension/.

   Source for this draft and an issue tracker can be found at
   https://github.com/GIC-de/draft-lihawi-ancp-protocol-access-
   extension.

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 3 December 2026.



Giese, et al.            Expires 3 December 2026                [Page 1]

Internet-Draft         Access Extensions for ANCP              June 2026


Copyright Notice

   Copyright (c) 2026 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  Modification to ANCP - General Aspects  . . . . . . . . . . .   4
   4.  Modification to DSL-Type TLV 0x0091 . . . . . . . . . . . . .   5
   5.  Extension to DSL Sub TLV  . . . . . . . . . . . . . . . . . .   5
     5.1.  Expected Throughput (ETR) TLV . . . . . . . . . . . . . .   6
     5.2.  Attainable Expected Throughput (ATTETR) TLV . . . . . . .   6
     5.3.  Gamma Data Rate (GDR) TLV . . . . . . . . . . . . . . . .   6
     5.4.  Attainable Gamma Data Rate (ATTGDR) TLV . . . . . . . . .   7
   6.  ANCP-Based PON Topology Discovery . . . . . . . . . . . . . .   7
     6.1.  ANCP Port Up and Port Down Event Message Descriptions . .   7
     6.2.  PON Access Line Identification  . . . . . . . . . . . . .   9
       6.2.1.  Access-Loop-Circuit-ID TLV  . . . . . . . . . . . . .   9
       6.2.2.  Access-Loop-Remote-ID TLV . . . . . . . . . . . . . .   9
       6.2.3.  PON-Access-Line-Attributes TLV  . . . . . . . . . . .  10
       6.2.4.  PON-Access-Type TLV . . . . . . . . . . . . . . . . .  10
       6.2.5.  ONT/ONU-Average-Data-Rate-Downstream TLV  . . . . . .  11
       6.2.6.  ONT/ONU-Peak-Data-Rate-Downstream TLV . . . . . . . .  11
       6.2.7.  ONT/ONU-Maximum-Data-Rate-Upstream TLV  . . . . . . .  11
       6.2.8.  ONT/ONU-Assured-Data-Rate-Upstream TLV  . . . . . . .  11
       6.2.9.  PON-Tree-Maximum-Data-Rate-Upstream TLV . . . . . . .  11
       6.2.10. PON-Tree-Maximum-Data-Rate-Downstream TLV . . . . . .  12
       6.2.11. Reserved TLV  . . . . . . . . . . . . . . . . . . . .  12
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  Early IANA Allocation Request . . . . . . . . . . . . . .  12
     8.2.  ANCP TLV Type Registry  . . . . . . . . . . . . . . . . .  12
     8.3.  Creation of the ANCP DSL-Type Registry  . . . . . . . . .  14
     8.4.  Creation of the ANCP PON-Access-Type Registry . . . . . .  15
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  17



Giese, et al.            Expires 3 December 2026                [Page 2]

Internet-Draft         Access Extensions for ANCP              June 2026


   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   While [RFC6934] outlines the application of ANCP to Passive Optical
   Networks (PON), the core ANCP specification ([RFC6320]) has not yet
   been updated to natively support these deployments.  Concurrently,
   DSL technology has continued to advance, introducing upgraded
   standards like G.fast, VDSL2 Vectoring, and VDSL2 Annex Q to deliver
   significantly higher bandwidths over the last mile.  To bridge this
   gap, this document updates the protocol to encompass these modern
   telecommunication access technologies by specifying the necessary new
   TLVs not currently supported by [RFC6320].

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.

   This section repeats some definitions from [RFC6320] and [RFC6934],
   but also updates some definitions where appropriate.

   Access Node (AN):
         Network device [RFC5851], usually located at a service provider
         central office or street cabinet that terminates access (local)
         loop connections from subscribers.  In case the access loop is
         a Digital Subscriber Line (DSL), the Access Node provides DSL
         signal termination and is referred to as a DSL Access
         Multiplexer (DSLAM).  In case the access loop is a Passive
         Optical Network (PON), the Access Node is referred to as an
         Optical Line Terminal (OLT).

   Optical Line Terminal (OLT):
         The OLT is located in the service provider's central office
         (CO) or street cabinet.  It terminates and aggregates multiple
         PONs (providing fiber access to multiple premises or
         neighborhoods) on the subscriber side and interfaces with the
         Network Access Server (NAS) that provides subscriber
         management.

   Optical Network Terminal (ONT):
         The ONT terminates PON on the network side and provides PON
         adaptation.  The subscriber side interface and the location of
         the ONT are dictated by the type of network deployment.  For an



Giese, et al.            Expires 3 December 2026                [Page 3]

Internet-Draft         Access Extensions for ANCP              June 2026


         FTTP deployment (with fiber all the way to the apartment or
         living unit), ONT has Ethernet (Fast Ethernet (FE) / Gigabit
         Ethernet (GE) / Multimedia over Coax Alliance (MoCA))
         connectivity with the Home Gateway (HGW) / Customer Premises
         Equipment (CPE).  In certain cases, one ONT may provide
         connections to more than one Home Gateway at the same time.

   Optical Network Unit (ONU):
         The ONU is a generic term denoting a device that terminates any
         one of the distributed (leaf) endpoints of an Optical
         Distribution Network (ODN), implements a PON protocol, and
         adapts PON PDUs to subscriber service interfaces.  In the case
         of a multi-dwelling unit (MDU) or multi-tenant unit (MTU), a
         multi-subscriber ONU typically resides in the basement or a
         wiring closet (FTTB case) and has FE/GE/Ethernet over native
         Ethernet link or over xDSL (typically VDSL2) connectivity with
         each CPE at the subscriber premises.  In the case where fiber
         is terminated outside the premises (neighborhood or curb side)
         on an ONT/ONU, the last-leg-premises connections could be via
         existing or new copper, with xDSL physical layer (typically
         VDSL2).  In this case, the ONU effectively is a "PON-fed
         DSLAM".  In new FTTdp based deployments the access node is
         named DPU (Distribution Point Unit).  Basically from ANCP
         perspective this node provides the same functionality.  Besides
         VDSL2, G.fast is mature and widely deployed.

3.  Modification to ANCP - General Aspects

   When applied to PON, ANCP message formats remain identical to those
   described in Section 3.5.1 of [RFC6320].  However, specific message
   descriptions must be updated to broaden their applicability beyond
   DSL deployments to include other access networks.

   Specifically, the ANCP Adjacency message is extended to support
   access technologies beyond DSL.  To achieve this, the following
   existing ANCP capabilities are updated to specify an Access
   Technology of "ANY":

   *  Capability Type: Access Topology Discovery = 0x01

      -  Access technology: ANY

      -  Length (in bytes): 0

      -  Capability Data: NULL

      -  For the detailed protocol specification of this capability, see
         Section 6 of [RFC6320].



Giese, et al.            Expires 3 December 2026                [Page 4]

Internet-Draft         Access Extensions for ANCP              June 2026


   *  Capability Type: Access Line Configuration = 0x02

      -  Access technology: ANY

      -  Length (in bytes): 0

      -  Capability Data: NULL

      -  For the detailed protocol specification of this capability, see
         Section 7 of [RFC6320].

   *  Capability Type: Access Remote Line Connectivity Testing = 0x04

      -  Access technology: ANY

      -  Length (in bytes): 0

      -  Capability Data: NULL

      -  For the detailed protocol specification of this capability, see
         Section 8 of [RFC6320].

4.  Modification to DSL-Type TLV 0x0091

   Add the following new DSL-Type values.

   Value: 32-bit unsigned integer

   *  G.fast = 8

   *  VDSL2 Annex Q = 9

   *  SDSL bonded = 10

   *  VDSL2 bonded = 11

   *  G.fast bonded = 12

   *  VDSL2 Annex Q bonded = 13

5.  Extension to DSL Sub TLV

   DSL sub TLVs are listed in Section 6.5 of [RFC6320].  G.fast requires
   beside existing TLVs the following new TLVs.







Giese, et al.            Expires 3 December 2026                [Page 5]

Internet-Draft         Access Extensions for ANCP              June 2026


5.1.  Expected Throughput (ETR) TLV

   *  Type: 0x009B Expected Throughput at L2 (ETR) upstream

      -  Length: 4 bytes

      -  Value: Rate in kbits/s as a 32-bit unsigned integer.

      -  Description: Reports the expected throughput upstream after
         retransmission (ITU-T G.997.2, clause 7.11.1.2).

   *  Type: 0x009C Expected Throughput at L2 (ETR) downstream

      -  Length: 4 bytes

      -  Value: Rate in kbits/s as a 32-bit unsigned integer.

      -  Description: Reports the expected throughput downstream after
         retransmission (ITU-T G.997.2, clause 7.11.1.2).

5.2.  Attainable Expected Throughput (ATTETR) TLV

   *  Type: 0x009D Attainable Expected Throughput (ATTETR) upstream

      -  Length: 4 bytes

      -  Value: Rate in kbits/s as a 32-bit unsigned integer.

      -  Description: Reports the attainable expected throughput
         upstream at L2 (ITU-T G.997.2, clause 7.11.2.2).

   *  Type: 0x009E Attainable Expected Throughput (ATTETR) downstream

      -  Length: 4 bytes

      -  Value: Rate in kbits/s as a 32-bit unsigned integer.

      -  Description: Reports the attainable expected throughput
         downstream at L2 (ITU-T G.997.2, clause 7.11.2.2).

5.3.  Gamma Data Rate (GDR) TLV

   *  Type: 0x009F Gamma data rate (GDR) upstream

      -  Length: 4 bytes

      -  Value: Rate in kbits/s as a 32-bit unsigned integer.




Giese, et al.            Expires 3 December 2026                [Page 6]

Internet-Draft         Access Extensions for ANCP              June 2026


      -  Description: Reports the Gamma data rate (GDR)

      -  upstream (ITU-T G.997.2, clause 7.11.1.3).

   *  Type: 0x00A0 Gamma Data Rate (GDR) downstream

      -  Length: 4 bytes

      -  Value: Rate in kbits/s as a 32-bit unsigned integer.

      -  Description: Reports the Gamma data rate (GDR)

      -  downstream (ITU-T G.997.2, clause 7.11.1.3).

5.4.  Attainable Gamma Data Rate (ATTGDR) TLV

   *  Type: 0x00A1 Attainable Gamma data rate (ATTGDR) upstream

      -  Length: 4 bytes

      -  Value: Rate in kbits/s as a 32-bit unsigned integer.

      -  Description: Reports the attainable Gamma data rate upstream
         (ATTGDR) (ITU-T G.997.2, clause 7.11.2.3).

   *  Type: 0x00A2 Attainable Gamma data rate (ATTGDR) downstream

      -  Length: 4 bytes

      -  Value: Rate in kbits/s as a 32-bit unsigned integer.

      -  Description: Reports the attainable Gamma data rate (ATTGDR)
         downstream (ITU-T G.997.2, clause 7.11.2.3).

6.  ANCP-Based PON Topology Discovery

   This section describes topology discovery messages applied for PON.
   TLVs not addressed here remain the same as applied for DSL.

6.1.  ANCP Port Up and Port Down Event Message Descriptions

   The format of the ANCP Port Up and Port Down Event messages is shown
   in Figure 1.  It has the same format as the one described in section
   6.3 of RFC6320.  The only difference is that DSL-Line-Attributes TLV
   is updated as Access-Line-Attributes TLV.






Giese, et al.            Expires 3 December 2026                [Page 7]

Internet-Draft         Access Extensions for ANCP              June 2026


       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |           TCP/IP Encapsulating Header (Section 3.2)           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                ANCP General Message Header                    |
      +                      (Section 3.6.1)                          +
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      ~                    Unused (20 bytes)                          ~
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |x|x|x|x|x|x|x|x| Message Type  |   Tech Type   |  Reserved     |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     # of TLVs                 | Extension Block length (bytes)|
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      ~                 Access line identifying TLV(s)                ~
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                ACCESS-Line-Attributes TLV                     |
      ~        (MANDATORY in Port Up, OPTIONAL in Port Down)          ~
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

     Figure 1: Format of the ANCP Port Up and Port Down Event Messages
                         for PON Topology Discovery

   NOTE: TLVs MAY be in a different order from what is shown in this
   figure.

   See Section 3.6.1 of [RFC6320] for a description of the ANCP general
   message header.  The Message Type field MUST be set to 80 for Port
   Up, 81 for Port Down.  It is applicable to both DSL and PON based
   access systems.  The 4-bit Result field MUST be set to zero
   (signifying Ignore).  The 12-bit Result Code field and the 24-bit
   Transaction Identifier field MUST also be set to zeroes.  Other
   fields in the general header MUST be set as described in Section 3.6
   of [RFC6320].

   The five-word Unused field is a historical leftover.  The handling of
   unused/reserved fields is described in Section 3.4 of [RFC6320].

   The remaining message fields belong to the "extension block", and are
   described as follows:





Giese, et al.            Expires 3 December 2026                [Page 8]

Internet-Draft         Access Extensions for ANCP              June 2026


   Extension Flags (8 bits): The flag bits denoted by 'x' are currently
   unspecified and reserved.

   Message Type (8 bits): Message Type has the same value as in the
   general header (i.e., 80 or 81).

   Tech Type (8 bits): MUST be set to 0x01 (PON).

   Reserved (8 bits): set as described in Section 3.4 of [RFC6320].

   # of TLVs (16 bits): The number of TLVs that follow, not counting
   TLVs encapsulated within other TLVs.

   Extension Block Length (16 bits): The total length of the TLVs
   carried in the extension block in bytes, including any padding within
   individual TLVs.

   TLVs: One or more TLVs to identify a PON Access line and zero or more
   TLVs to define its characteristics.

6.2.  PON Access Line Identification

   Most ANCP messages involve actions relating to a specific access
   line.  Thus, it is necessary to describe how PON access lines are
   identified within those messages.  This section defines four TLVs for
   that purpose and provides an informative description of how they are
   used in PON.  TLVs not addressed here remain unchanged as applied for
   DSL.

6.2.1.  Access-Loop-Circuit-ID TLV

   *  Type: 0x0001

   *  Description: A locally administered human-readable string
      generated by or configured on the Access Node, uniquely
      identifying the corresponding access loop logical port on the user
      side of the Access Node, as described in Section 5.7 of [TR156].

   *  Length: Up to 63 bytes

   *  Value: ASCII string

6.2.2.  Access-Loop-Remote-ID TLV

   *  Type: 0x0002






Giese, et al.            Expires 3 December 2026                [Page 9]

Internet-Draft         Access Extensions for ANCP              June 2026


   *  Description: An operator-configured string that uniquely
      identifies the user on the associated access line, as described in
      Section 5.7 of [TR156].

   *  Length: Up to 63 bytes

   *  Value: ASCII string

6.2.3.  PON-Access-Line-Attributes TLV

   *  Type: 0x0012

   *  Description: This TLV encapsulates attribute values of a PON
      access line serving a subscriber.

   *  Length: Variable (up to 1023 bytes)

   *  Value: One or more encapsulated TLVs corresponding to PON access
      line attributes.  The PON-Access-Line-Attributes TLV MUST contain
      at least one TLV when it is present in a Port Up or Port Down
      message.  The actual contents are determined by the AN control
      application.  Technology-independent attributes of [RFC6320], such
      as TLV0x0090, are valid for PON and not repeated here.

6.2.4.  PON-Access-Type TLV

   *  Type: 0x0097

   *  Description: Indicates the type of PON transmission system in use.

   *  Length: 4 bytes

   *  Value: 32-bit unsigned integer

      -  OTHER = 0

      -  GPON = 1

      -  XG-PON1 = 2

      -  TWDM-PON = 3

      -  XGS-PON = 4

      -  WDM-PON = 5

      -  Unknown = 7




Giese, et al.            Expires 3 December 2026               [Page 10]

Internet-Draft         Access Extensions for ANCP              June 2026


      -  25GS-PON = 8

      -  50G-PON = 9

6.2.5.  ONT/ONU-Average-Data-Rate-Downstream TLV

   *  Type: 0x00B0

   *  Description: ONT/ONU downstream average data rate L2

   *  Length: 4 bytes

   *  Value: Rate in kbits/s as a 32-bit unsigned integer

6.2.6.  ONT/ONU-Peak-Data-Rate-Downstream TLV

   *  Type: 0x00B1

   *  Description: ONT/ONU downstream peak data rate L2

   *  Length: 4 bytes

   *  Value: Rate in kbits/s as a 32-bit unsigned integer

6.2.7.  ONT/ONU-Maximum-Data-Rate-Upstream TLV

   *  Type: 0x00B2

   *  Description: ONT/ONU upstream maximum data rate L2

   *  Length: 4 bytes

   *  Value: Rate in kbits/s as a 32-bit unsigned integer

6.2.8.  ONT/ONU-Assured-Data-Rate-Upstream TLV

   *  Type: 0x00B3

   *  Description: ONT/ONU upstream assured data rate L2

   *  Length: 4 bytes

   *  Value: Rate in kbits/s as a 32-bit unsigned integer

6.2.9.  PON-Tree-Maximum-Data-Rate-Upstream TLV

   *  Type: 0x00B4




Giese, et al.            Expires 3 December 2026               [Page 11]

Internet-Draft         Access Extensions for ANCP              June 2026


   *  Description: PON Tree upstream maximum data rate L2

   *  Length: 4 bytes

   *  Value: Rate in kbits/s as a 32-bit unsigned integer

6.2.10.  PON-Tree-Maximum-Data-Rate-Downstream TLV

   *  Type: 0x00B5

   *  Description: PON Tree downstream maximum data rate L2

   *  Length: 4 bytes

   *  Value: Rate in kbits/s as a 32-bit unsigned integer

6.2.11.  Reserved TLV

   *  Type: 0x00B6 - 0x00B7

   *  Description: Reserved

   *  Length: tbd

   *  Value: tbd

7.  Security Considerations

   This document does not introduce additional security considerations
   beyond those discussed in [RFC6320] and [RFC6934].

8.  IANA Considerations

8.1.  Early IANA Allocation Request

   Note to the RFC Editor and IANA: Multiple vendors have already
   implemented the ANCP extensions described in this document, and the
   exact TLV Type values specified below are actively deployed in
   production networks.  To prevent severe breakage of backwards
   compatibility within this existing deployed base, the authors
   formally request the early allocation of these specific TLV Type
   values according to the procedures defined in [RFC7120].

8.2.  ANCP TLV Type Registry

   This document defines the following sets of new TLVs for PON and
   evolving DSL access technologies.  Some values previously defined by
   [RFC6320] are referenced here for completeness.



Giese, et al.            Expires 3 December 2026               [Page 12]

Internet-Draft         Access Extensions for ANCP              June 2026


   IANA is requested to allocate the specific code points listed below
   in the "ANCP TLV Type" registry.

     +===========+=======================================+===========+
     | Type Code | TLV Name                              | Reference |
     +===========+=======================================+===========+
     | 0x0000    | Reserved                              | RFC 6320  |
     +-----------+---------------------------------------+-----------+
     | 0x0001    | Access-Loop-Circuit-ID                | RFC 6320  |
     +-----------+---------------------------------------+-----------+
     | 0x0002    | Access-Loop-Remote-ID                 | RFC 6320  |
     +-----------+---------------------------------------+-----------+
     | 0x0003    | Access-Aggregation-Circuit-ID-ASCII   | RFC 6320  |
     +-----------+---------------------------------------+-----------+
     | 0x0005    | Service-Profile-Name                  | RFC 6320  |
     +-----------+---------------------------------------+-----------+
     | 0x0006    | Access-Aggregation-Circuit-ID-Binary  | RFC 6320  |
     +-----------+---------------------------------------+-----------+
     | 0x0011    | Command                               | RFC 6320  |
     +-----------+---------------------------------------+-----------+
     | 0x0012    | PON-Access-Line-Attributes            | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x0097    | PON-Access-Type                       | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x0098    | Reserved                              | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x0099    | Reserved                              | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x009A    | Reserved                              | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x009B    | Expected Throughput (ETR) upstream    | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x009C    | Expected Throughput (ETR) downstream  | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x009D    | Attainable Expected Throughput        | RFC TBD1  |
     |           | (ATTETR) upstream                     |           |
     +-----------+---------------------------------------+-----------+
     | 0x009E    | Attainable Expected Throughput        | RFC TBD1  |
     |           | (ATTETR) downstream                   |           |
     +-----------+---------------------------------------+-----------+
     | 0x009F    | Gamma Data Rate (GDR) upstream        | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x00A0    | Gamma Data Rate (GDR) downstream      | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x00A1    | Attainable Gamma Data Rate (ATTGDR)   | RFC TBD1  |
     |           | upstream                              |           |
     +-----------+---------------------------------------+-----------+
     | 0x00A2    | Attainable Gamma Data Rate (ATTGDR)   | RFC TBD1  |



Giese, et al.            Expires 3 December 2026               [Page 13]

Internet-Draft         Access Extensions for ANCP              June 2026


     |           | downstream                            |           |
     +-----------+---------------------------------------+-----------+
     | 0x00B0    | ONT/ONU-Average-Data-Rate-Downstream  | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x00B1    | ONT/ONU-Peak-Data-Rate-Downstream     | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x00B2    | ONT/ONU-Maximum-Data-Rate-Upstream    | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x00B3    | ONT/ONU-Assured-Data-Rate-Upstream    | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x00B4    | PON-Tree-Maximum-Data-Rate-Upstream   | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x00B5    | PON-Tree-Maximum-Data-Rate-Downstream | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x00B6    | Reserved                              | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x00B7    | Reserved                              | RFC TBD1  |
     +-----------+---------------------------------------+-----------+
     | 0x0106    | Status-Info                           | RFC 6320  |
     +-----------+---------------------------------------+-----------+
     | 0x1000    | Target (single access line variant)   | RFC 6320  |
     +-----------+---------------------------------------+-----------+
     | 0x1001 -  | Reserved for Target variants          | RFC 6320  |
     +-----------+---------------------------------------+-----------+

                                  Table 1

   Note to the RFC Editor: Please replace "TBD1" with the assigned RFC
   number prior to publication.

8.3.  Creation of the ANCP DSL-Type Registry

   This document requests that IANA create a new registry titled "ANCP
   DSL-Type" within the Access Node Control Protocol (ANCP).

   The registration procedure for this registry is "IETF Review" as
   defined in RFC 8126.

   The registry consists of 32-bit unsigned integers.  IANA is requested
   to populate this new registry with the initial values defined in RFC
   6320, as well as the new values defined in this document (which are
   subject to the early allocation request noted above).









Giese, et al.            Expires 3 December 2026               [Page 14]

Internet-Draft         Access Extensions for ANCP              June 2026


               +=======+======================+===========+
               | Value | Description          | Reference |
               +=======+======================+===========+
               | 1     | ADSL1                | RFC 6320  |
               +-------+----------------------+-----------+
               | 2     | ADSL2                | RFC 6320  |
               +-------+----------------------+-----------+
               | 3     | ADSL2+               | RFC 6320  |
               +-------+----------------------+-----------+
               | 4     | VDSL1                | RFC 6320  |
               +-------+----------------------+-----------+
               | 5     | VDSL2                | RFC 6320  |
               +-------+----------------------+-----------+
               | 6     | SDSL                 | RFC 6320  |
               +-------+----------------------+-----------+
               | 7     | Unknown              | RFC 6320  |
               +-------+----------------------+-----------+
               | 8     | G.fast               | TBD1      |
               +-------+----------------------+-----------+
               | 9     | VDSL2 Annex Q        | TBD1      |
               +-------+----------------------+-----------+
               | 10    | SDSL bonded          | TBD1      |
               +-------+----------------------+-----------+
               | 11    | VDSL2 bonded         | TBD1      |
               +-------+----------------------+-----------+
               | 12    | G.fast bonded        | TBD1      |
               +-------+----------------------+-----------+
               | 13    | VDSL2 Annex Q bonded | TBD1      |
               +-------+----------------------+-----------+

                                 Table 2

8.4.  Creation of the ANCP PON-Access-Type Registry

   This document requests that IANA create a new registry titled "ANCP
   PON-Access-Type" within the Access Node Control Protocol (ANCP)
   parameters.

   The registration procedure for this registry is "IETF Review" as
   defined in RFC 8126.

   The registry consists of 32-bit unsigned integers representing the
   type of PON transmission system in use.  IANA is requested to
   populate this new registry with the initial values defined in this
   document (which are subject to the early allocation request noted
   above).





Giese, et al.            Expires 3 December 2026               [Page 15]

Internet-Draft         Access Extensions for ANCP              June 2026


                    +=======+=============+===========+
                    | Value | Description | Reference |
                    +=======+=============+===========+
                    | 0     | OTHER       | TBD1      |
                    +-------+-------------+-----------+
                    | 1     | GPON        | TBD1      |
                    +-------+-------------+-----------+
                    | 2     | XG-PON1     | TBD1      |
                    +-------+-------------+-----------+
                    | 3     | TWDM-PON    | TBD1      |
                    +-------+-------------+-----------+
                    | 4     | XGS-PON     | TBD1      |
                    +-------+-------------+-----------+
                    | 5     | WDM-PON     | TBD1      |
                    +-------+-------------+-----------+
                    | 7     | Unknown     | TBD1      |
                    +-------+-------------+-----------+
                    | 8     | 25GS-PON    | TBD1      |
                    +-------+-------------+-----------+
                    | 9     | 50G-PON     | TBD1      |
                    +-------+-------------+-----------+

                                  Table 3

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, March 1997,
              <https://www.rfc-editor.org/rfc/rfc2119>.

   [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,
              October 2011, <https://www.rfc-editor.org/rfc/rfc6320>.

   [RFC6934]  Bitar, N., Ed., Wadhwa, S., Ed., Haag, T., and H. Li,
              "Applicability of the Access Node Control Mechanism to
              Broadband Networks Based on Passive Optical Networks
              (PONs)", RFC 6934, DOI 10.17487/RFC6934, June 2013,
              <https://www.rfc-editor.org/rfc/rfc6934>.

   [RFC7120]  Cotton, M., "Early IANA Allocation of Standards Track Code
              Points", BCP 100, RFC 7120, DOI 10.17487/RFC7120, January
              2014, <https://www.rfc-editor.org/rfc/rfc7120>.




Giese, et al.            Expires 3 December 2026               [Page 16]

Internet-Draft         Access Extensions for ANCP              June 2026


   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.

9.2.  Informative References

   [RFC5851]  Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S.
              Wadhwa, "Framework and Requirements for an Access Node
              Control Mechanism in Broadband Multi-Service Networks",
              RFC 5851, DOI 10.17487/RFC5851, May 2010,
              <https://www.rfc-editor.org/rfc/rfc5851>.

   [TR156]    Broadband Forum, "Using GPON Access in the context of TR-
              101", TR 156 Issue 3, November 2012.

Acknowledgments

   The authors would like to give special recognition to Hongyu Li, who
   served as a primary author on earlier versions of this draft.  His
   foundational efforts and significant technical contributions during
   his time at Huawei Technologies were instrumental in shaping this
   document.

   Many thanks to Norbert Voigt, John Gibbons, Sven Ooghe, Koen De
   Sagher and Sven Leimer for joint work reviewing the document and
   providing valuable comments to this document.

Authors' Addresses

   Christian Giese
   RtBrick
   Email: christian@rtbrick.com


   Thomas Haag
   Deutsche Telekom AG
   Email: haagt@telekom.de


   Birgit Witschurke
   Deutsche Telekom AG
   Email: b.witschurke@telekom.de









Giese, et al.            Expires 3 December 2026               [Page 17]
