**Session Date/Time:** 10 Apr 2025 14:00

# [CCAMP](../wg/ccamp.html)

## Summary

The CCAMP Working Group held its second interim meeting to discuss various drafts not covered during IETF 122. The session focused on updates and discussions for drafts related to performance management, autonomous networking (ANL4) scenarios, IPFIX for GPON, microwave radio link YANG models, fine-grain optical transport networks (FGOTN), and rich detail network management (RDNM). Several drafts were proposed for Working Group adoption. Liaison statements from ETSI and ITU were noted.

## Key Discussion Points

*   **Opening and Updates**:
    *   The chairs welcomed participants and reminded everyone of the IETF Notewell rules.
    *   An update was provided on the conclusion of the second Working Group Last Call for RFC 1993bis, with Daniela assigned as shepherd. The Optical Impairment Topology draft requires minor comments to be addressed, with Juan assigned as shepherd; both documents will move forward together.
    *   Working Group prioritization shifted, with WDM pluggable modeling now prioritized over WDM T-ANALYANG.
    *   Two liaison statements were noted: one from ETSI to CCAMP and PCE on Optical Cloud Networks (OCN), and another from ITU JCA IMT2020 inviting updated information on the IMT2020 and beyond roadmap.

*   **YANG Data Model of Performance Management Streaming (draft-ietf-ccamp-pm-streaming-yang)**:
    *   Ben presented updates, highlighting architectural changes that split the original PM streaming module into `pm-measurement` and `pm-parameters` for flexibility.
    *   The `pm-measurement` module defines periodic methods (count, snapshot, tide mark, threshold notifications), while `pm-parameters` defines three parameter groups (15 minutes, 24 hours, QoS).
    *   The model aligns with ITU-T G.7710 and focuses on device-level PM management via a southbound interface (SBI), aiming to minimize network management messages by offloading analytics to external applications.
    *   **Discussion**:
        *   A participant inquired about augmenting the parameters container for other technologies (e.g., optical, microwave) without altering the core draft. The author acknowledged this need for future use cases.
        *   A question was raised regarding the motivation and advantages compared to existing telemetry and notification mechanisms, particularly given a lack of vendor adoption of IETF models on the device southbound interface for this purpose. The author stated the primary focus is G.7710 requirements and emphasized minimizing measurement messages for device burden reduction.
        *   An editorial comment noted that G.7710 is referenced but not listed in the document's references.

*   **ANL4 Scenarios and Requirements in Transport Domain (draft-liu-ccamp-anl4-scenarios-reqs)**:
    *   Chowder presented on use cases, definitions, and requirements for Autonomous Network Level 4 (ANL4) in the transport domain, targeting domain controllers.
    *   The scope focuses on use case description and requirements, not new YANG models or interfaces. Applicable scenarios include disaggregation and IP pluggable.
    *   Initial ANL4 use cases summarized include service provisioning automation (e.g., wavelength, OTN service), CP plug-and-play, service assurance automation (latency, bandwidth, reliability), and transport network C-MAP.
    *   A detailed use case for service provisioning automation highlighted pain points like long time-to-market due to multi-departmental manual workflows (planning, design, supervision, network operations). Key requirements proposed include optical resource planning and validation, high reachability assurance (multi-layer path design), effective resource preoccupation, and top-down provisioning.
    *   **Discussion**:
        *   The chair commented that this work is needed, particularly for optical-specific ANL4, but emphasized the importance of coordinating with TMF, who owns the AN concept. The authors confirmed existing collaboration with TMF experts and planned engagement post-meeting.

*   **Export of GPON Encapsulation Mode in IPFIX (draft-thomas-ipfix-gpon-encaps)**:
    *   Thomas presented an IPFIX document providing data plane visibility for passive optical transport, specifically GPON.
    *   The draft defines IPFIX Information Elements for the GPON Encapsulation Method (GEM) Port ID and Payload Type Indicator (PTI), which are key for forwarding status visibility. PLI and HEC are considered less relevant for IPFIX aggregation.
    *   A use case showed how GEM Port ID, PTI, MAC addresses, and interface information provide insight into OM vs. user frames and packet forwarding status.
    *   **Discussion**:
        *   The author noted challenges with synchronizing an IPFIX registry with ITU-T's existing G.984.3 registry for PTI code points.
        *   A participant from CCAMP expressed interest in this work as an "important trial" for adapting IETF protocols to PON and other optical networks (OTN, WDM).
        *   Scott offered assistance with liaising with ITU-T Study Group 15 for registry synchronization and finding relevant ITU-T registry information.

*   **YANG Data Model for Microwave Radio Links (draft-ietf-ccamp-microwave-radio-link-yang)**:
    *   Scott provided an update on the draft, which has been in development since 2019 (republished Oct 2023) to align with ETSI plug tests and provide a standard model for microwave radio links.
    *   Updates include new functionalities, cleanup, common microwave properties to reduce duplication, adding missing configuration parameters (e.g., minimum nominal power, reference modulation), description of header compression, and definition of adaptive code modulation. The `radio-link-terminal-mode` definition is being deprecated for a new approach.
    *   Six current open issues are tracked on a private GitHub, covering band/carrier aggregation, coding modulations, radio signal identifier, and alignment with RFC 8407bis guidelines (especially security).
    *   **Discussion**:
        *   The authors meet weekly and utilize GitHub for collaborative development.
        *   The presenter requested Working Group adoption to move the draft to CCAMP's GitHub and increase engagement.

*   **Data Model for Fine Grain Optical Transport Networks (FGOTN) (draft-ietf-ccamp-fg-otn-yang)**:
    *   The presenter outlined control interface requirements for FGOTN and proposed two YANG models for FGOTN topology and FGOTN tunnel.
    *   Changes from version 1 to 3 included renaming and clarifying scenarios: "retrieve service channels" (previously "service provisioning"), "multi-layer path splicing" (previously "service protection"), and "inter-domain service resizing."
    *   **Open Issues Discussed**:
        *   **Generic structure for multi-layer path**: Two options proposed: extending `dependency-tunnel` structure (adding `index` and `working-rule`) or extending `path-element` (adding an `underlay-tunnel` structure).
        *   **Filtering TPs supporting FGOTN**: Solutions discussed included extending switching capability and encoding or defining a new ODU type, both potentially impacting PCE and GMPLS protocols.
        *   **Link bandwidth**: Agreement on bandwidth statement, but types (string with MPS units vs. integer for ODU0 count) still under discussion.
    *   **Discussion**:
        *   The authors plan to continue discussions on open issues, seeking correlation with PCE and GMPLS protocol experts, and addressing inter-domain resizing.
        *   The presenter indicated that the work is ready for Working Group adoption.

*   **Rich Detail Network Management (RDNM) for ACTN-based Transport Networks (draft-ietf-ccamp-actn-rdnm)**:
    *   Dan presented on this relatively recent document, which describes YANG models for granular network management below the Multi-Domain Service Coordinator (MDSC) in an ACTN environment.
    *   The document reuses existing CCAMP and potentially other WG (TE, I2NSF) YANG models to provide fine-detailed network management (e.g., topology, performance, security, function) from forwarding elements (microwave, optical, electrical).
    *   A key focus is harmonizing terminology across different standards organizations (TMF, ITU-T G.805/806, TAPPI, IETF ACTN), as objects like "element" or "component" have different names and nuances.
    *   The document will provide a lexicon (Rosetta Stone) of terms, RDNM-specific YANG extensions, and a list of applicable CCAMP/TE YANG models for solving specific examples (e.g., SLA monitoring for end-to-end connections).
    *   Future work includes exploring telemetry for performance monitoring/maintenance.
    *   **Discussion**:
        *   A participant suggested creating GitHub examples with instance data and scripts (e.g., Yang Lint) to validate the integration and functionality of the models. The author welcomed this idea.
        *   A participant asked if the work considers use cases where complexity is simplified by treating different artifacts as the same thing for operational ease, or if it solely focuses on differentiation. The author stated the priority is showing how to use existing IETF models for fine-detail management, focusing on key use cases (topology, inventory, security, performance monitoring) and avoiding boiling the ocean, while also supporting operators needing to integrate with existing OSS/MTOSI systems.

## Decisions and Action Items

*   **RFC 1993bis**: Second WG last call concluded. Daniela is assigned as shepherd.
*   **Optical Impairment Topology**: Authors to address minor comments and issue version 18. Juan is assigned as shepherd.
*   **WDM Pluggable Modeling**: Prioritization for Working Group Last Call shifted to WDM pluggable modeling.
*   **Liaison Statements**: Two liaison statements (ETSI on OCN, ITU JCA IMT2020 on roadmap) were noted by the Working Group.
*   **ANL4 Scenarios and Requirements**: Authors to coordinate with TMF on ANL4 use cases and requirements for the transport domain.
*   **Export of GPON Encapsulation Mode in IPFIX**: Scott volunteered to investigate ITU-T for existing registries similar to IANA for PTI code points and assist with liaison.
*   **YANG Data Model for Microwave Radio Links**: Chairs to consider initiating a Working Group adoption poll.
*   **Data Model for Fine Grain Optical Transport Networks (FGOTN)**: Chairs to consider initiating a Working Group adoption poll.

## Next Steps

*   **Performance Management Streaming YANG Model (draft-ietf-ccamp-pm-streaming-yang)**:
    *   Authors to align the document with ongoing revisions of ITU-T G.7710 (expected consent October 2025).
    *   Authors to add more use cases and harmonize with existing topology models.
*   **ANL4 Scenarios and Requirements in Transport Domain (draft-liu-ccamp-anl4-scenarios-reqs)**:
    *   Authors to continue discussing the service automation scenario, exploring potential new models or interfaces.
    *   Authors to further develop other ANL4 use cases like CP plug-and-play and transport C-MAP.
    *   Authors to call for interest and invite new contributors.
*   **Export of GPON Encapsulation Mode in IPFIX (draft-thomas-ipfix-gpon-encaps)**:
    *   Authors to consider formalizing a liaison with ITU-T Study Group 15 for registry synchronization.
    *   Authors to pursue adoption within the OPSAWG and solicit CCAMP review.
*   **YANG Data Model for Microwave Radio Links (draft-ietf-ccamp-microwave-radio-link-yang)**:
    *   The Working Group chairs will move forward with an adoption poll.
*   **Data Model for Fine Grain Optical Transport Networks (FGOTN) (draft-ietf-ccamp-fg-otn-yang)**:
    *   Authors to continue discussion on the three open issues, particularly seeking correlation with PCE and GMPLS protocol experts.
    *   Authors to begin detailed discussion on inter-domain resizing issues.
    *   The Working Group chairs will move forward with an adoption poll.
*   **Rich Detail Network Management (RDNM) for ACTN-based Transport Networks (draft-ietf-ccamp-actn-rdnm)**:
    *   Authors to continue the iterative process of harmonizing terminology across different SDOs.
    *   Authors to consider integrating automation and tooling for instance examples and model validation into their GitHub repository.
    *   Authors will use the CCAMP mailing list and normal WG process for substantive decisions.
*   **Working Group Chairs**: The chairs expressed satisfaction with the interim meeting format and invited participants to request future interim meetings for specific documents or topics as needed to expedite discussions.