├── .gitignore ├── .mailmap ├── CNAME ├── LICENSE ├── OD-360 ├── 01-intro.md ├── 02-ietf.md ├── 03-bbf.md ├── 04-deviation.md ├── 05-units.md ├── NMDA │ └── 05-nmda.md └── images │ └── ecosystem.png ├── README.md ├── check.sh ├── docs ├── .nojekyll ├── CNAME ├── YANG-develop-105.pdf ├── bbf.css ├── bbflogo-bw.png ├── bbflogo-reverse-dark.png ├── bee.png ├── broadband-forum-logo.png ├── docx-defaults.yaml ├── extra.css ├── github.css ├── images │ └── ecosystem.png ├── index.docx ├── index.htm ├── index.html ├── index.json ├── index.md ├── index.pdf ├── index.typ ├── json-defaults.yaml ├── missing.png ├── pandoc-output.txt ├── pandoc-tests.xml ├── pdf-defaults.yaml ├── pencil.png ├── permalink.png ├── release.css ├── release.css.bak ├── right.png ├── tick.png ├── toc.css ├── typst-defaults.yaml ├── typst-stringify.typ ├── typst-template.typ ├── watermark-pdf.css └── watermark.css └── standard ├── application ├── bbf-d-olt-dhcpra.yang ├── bbf-d-olt-mgmd.yang ├── bbf-d-olt-onuauth-types.yang ├── bbf-d-olt-onuauth.yang ├── bbf-d-olt-pppoe-intermediate-agent.yang ├── bbf-ipfix-data-export.yang ├── bbf-olt-d-olt.yang ├── bbf-olt-vomci-grpc-client-tcp.yang ├── bbf-olt-vomci-grpc-client-tls.yang ├── bbf-olt-vomci-grpc-client.yang ├── bbf-olt-vomci-grpc-server-tcp.yang ├── bbf-olt-vomci-grpc-server-tls.yang ├── bbf-olt-vomci-grpc-server.yang ├── bbf-olt-vomci-state.yang ├── bbf-olt-vomci.yang ├── bbf-onu-management-proxy-grpc-client-tcp.yang ├── bbf-onu-management-proxy-grpc-client-tls.yang ├── bbf-onu-management-proxy-grpc-client.yang ├── bbf-onu-management-proxy-grpc-server-tcp.yang ├── bbf-onu-management-proxy-grpc-server-tls.yang ├── bbf-onu-management-proxy-grpc-server.yang ├── bbf-onu-management-proxy-kafka-agent-tcp.yang ├── bbf-onu-management-proxy-kafka-agent-tls.yang ├── bbf-onu-management-proxy-kafka-agent.yang ├── bbf-onu-management-proxy-state.yang ├── bbf-onu-management-proxy.yang ├── bbf-voltmf-grpc-client-tcp.yang ├── bbf-voltmf-grpc-client-tls.yang ├── bbf-voltmf-grpc-client.yang ├── bbf-voltmf-kafka-agent-tcp.yang ├── bbf-voltmf-kafka-agent-tls.yang ├── bbf-voltmf-kafka-agent.yang ├── bbf-voltmf-state.yang ├── bbf-voltmf.yang ├── bbf-vomci-function-grpc-client-tcp.yang ├── bbf-vomci-function-grpc-client-tls.yang ├── bbf-vomci-function-grpc-client.yang ├── bbf-vomci-function-grpc-server-tcp.yang ├── bbf-vomci-function-grpc-server-tls.yang ├── bbf-vomci-function-grpc-server.yang ├── bbf-vomci-function-kafka-agent-tcp.yang ├── bbf-vomci-function-kafka-agent-tls.yang ├── bbf-vomci-function-kafka-agent.yang ├── bbf-vomci-function.yang ├── bbf-vomci-proxy-grpc-client-tcp.yang ├── bbf-vomci-proxy-grpc-client-tls.yang ├── bbf-vomci-proxy-grpc-client.yang ├── bbf-vomci-proxy-grpc-server-tcp.yang ├── bbf-vomci-proxy-grpc-server-tls.yang ├── bbf-vomci-proxy-grpc-server.yang ├── bbf-vomci-proxy-kafka-agent-tcp.yang ├── bbf-vomci-proxy-kafka-agent-tls.yang ├── bbf-vomci-proxy-kafka-agent.yang └── bbf-vomci-proxy.yang ├── common ├── bbf-alarm-types.yang ├── bbf-availability.yang ├── bbf-baa-pan.yang ├── bbf-contact.yang ├── bbf-d-olt-message-monitor.yang ├── bbf-d-olt-network-function-types.yang ├── bbf-device-aggregation.yang ├── bbf-device-types.yang ├── bbf-device.yang ├── bbf-dot1q-types.yang ├── bbf-end-user.yang ├── bbf-frame-processing-types.yang ├── bbf-grpc-client.yang ├── bbf-grpc-server.yang ├── bbf-inet-types.yang ├── bbf-kafka-agent.yang ├── bbf-location-types.yang ├── bbf-location.yang ├── bbf-network-function-client.yang ├── bbf-network-function-server.yang ├── bbf-network-function-types.yang ├── bbf-network-function.yang ├── bbf-network-types.yang ├── bbf-node-types.yang ├── bbf-olt-relay-agent-sci.yang ├── bbf-omci-message-retransmission.yang ├── bbf-voltmf-common.yang ├── bbf-voltmf-message-monitor.yang ├── bbf-vomci-common.yang ├── bbf-vomci-grpc-common.yang ├── bbf-vomci-types.yang └── bbf-yang-types.yang ├── equipment ├── bbf-equipment-inventory.yang ├── bbf-hardware-cpu.yang ├── bbf-hardware-rpf-dpu-alarm-types.yang ├── bbf-hardware-rpf-dpu-state.yang ├── bbf-hardware-rpf-dpu.yang ├── bbf-hardware-storage-drives.yang ├── bbf-hardware-transceiver-alarm-types.yang ├── bbf-hardware-transceivers.yang ├── bbf-hardware-types.yang ├── bbf-hardware.yang ├── bbf-software-management-voice.yang └── bbf-software-management.yang ├── interface ├── bbf-ethernet-performance-management.yang ├── bbf-fast-alarm-types.yang ├── bbf-fast-availability.yang ├── bbf-fast-base.yang ├── bbf-fast-channel-performance-body.yang ├── bbf-fast-channel-status-body.yang ├── bbf-fast-channel-threshold-profile-body.yang ├── bbf-fast-data-rate-profile-body.yang ├── bbf-fast-fast-rate-adaptation-profile-body.yang ├── bbf-fast-fast-retrain-policy-profile-body.yang ├── bbf-fast-ftu-inventory-body.yang ├── bbf-fast-impulse-noise-monitoring-profile-body.yang ├── bbf-fast-inventory.yang ├── bbf-fast-line-performance-body.yang ├── bbf-fast-line-spectrum-profile-body.yang ├── bbf-fast-line-status-body.yang ├── bbf-fast-line-threshold-profile-body.yang ├── bbf-fast-link-state-body.yang ├── bbf-fast-noise-margin-profile-body.yang ├── bbf-fast-perf-types.yang ├── bbf-fast-performance-management.yang ├── bbf-fast-pointers.yang ├── bbf-fast-quality-profiles.yang ├── bbf-fast-read-test-body.yang ├── bbf-fast-retransmission-profile-body.yang ├── bbf-fast-rfi-profile-body.yang ├── bbf-fast-service-profiles.yang ├── bbf-fast-spectrum-profiles.yang ├── bbf-fast-status-monitoring.yang ├── bbf-fast-tdd-profile-body.yang ├── bbf-fast-tdd-profiles.yang ├── bbf-fast-test-diagnostics.yang ├── bbf-fast-test-mode-body.yang ├── bbf-fast-threshold-crossing-alert-body.yang ├── bbf-fast-threshold-management.yang ├── bbf-fast-update-test-body.yang ├── bbf-fast-upstream-power-back-off-profile-body.yang ├── bbf-fast-vectoring-profile-body.yang ├── bbf-fast.yang ├── bbf-fastdsl.yang ├── bbf-frame-classification.yang ├── bbf-frame-editing.yang ├── bbf-frame-processing-profiles.yang ├── bbf-frame-processing.yang ├── bbf-gbond-state.yang ├── bbf-gbond.yang ├── bbf-ghn-base.yang ├── bbf-ghn-channel-estimation-profile-body.yang ├── bbf-ghn-dba-profile-body.yang ├── bbf-ghn-domain-id-profile-body.yang ├── bbf-ghn-domain-profiles.yang ├── bbf-ghn-domain-state.yang ├── bbf-ghn-domain-status-body.yang ├── bbf-ghn-line-spectrum-profile-body.yang ├── bbf-ghn-link-performance-body.yang ├── bbf-ghn-link-profiles.yang ├── bbf-ghn-link-state.yang ├── bbf-ghn-link-status-body.yang ├── bbf-ghn-local-node-info-body.yang ├── bbf-ghn-local-node-info.yang ├── bbf-ghn-node-id-profile-body.yang ├── bbf-ghn-node-inventory-body.yang ├── bbf-ghn-node-performance-body.yang ├── bbf-ghn-node-profiles.yang ├── bbf-ghn-node-state.yang ├── bbf-ghn-node-status-body.yang ├── bbf-ghn-perf-types.yang ├── bbf-ghn-performance-management.yang ├── bbf-ghn-pointers.yang ├── bbf-ghn-scheduling-profile-body.yang ├── bbf-ghn-security-profile-body.yang ├── bbf-ghn-types.yang ├── bbf-ghn.yang ├── bbf-ghs-base.yang ├── bbf-ghs-handshake-profile-body.yang ├── bbf-ghs-handshake-profiles.yang ├── bbf-ghs-pointers.yang ├── bbf-ghs.yang ├── bbf-hardware-transceivers-xpon.yang ├── bbf-hardware-types-xpon.yang ├── bbf-if-type.yang ├── bbf-interface-usage.yang ├── bbf-interfaces-performance-management.yang ├── bbf-interfaces-remote-hardware-state.yang ├── bbf-interfaces-statistics-management.yang ├── bbf-ip-interfaces.yang ├── bbf-l2-terminations.yang ├── bbf-link-table.yang ├── bbf-melt-base.yang ├── bbf-melt-pmd-control-body.yang ├── bbf-melt-pmd-measurement-parameter-body.yang ├── bbf-melt-pmd-profile-body.yang ├── bbf-melt-pmd-profiles.yang ├── bbf-melt-pmd-reporting-parameter-body.yang ├── bbf-melt-pmd-status-body.yang ├── bbf-melt-pmd.yang ├── bbf-melt-pointers.yang ├── bbf-melt-processing-derived-parameter-body.yang ├── bbf-melt-processing-profile-body.yang ├── bbf-melt-processing-profiles.yang ├── bbf-melt-result-parameters.yang ├── bbf-melt.yang ├── bbf-ptm.yang ├── bbf-selt-base.yang ├── bbf-selt-pmd-control-body.yang ├── bbf-selt-pmd-measurement-parameter-body.yang ├── bbf-selt-pmd-profile-body.yang ├── bbf-selt-pmd-profiles.yang ├── bbf-selt-pmd-status-body.yang ├── bbf-selt-pmd.yang ├── bbf-selt-pointers.yang ├── bbf-selt-processing-derived-parameter-body.yang ├── bbf-selt-processing-profile-body.yang ├── bbf-selt-processing-profiles.yang ├── bbf-selt-result-parameters.yang ├── bbf-selt.yang ├── bbf-sub-interface-tagging.yang ├── bbf-sub-interfaces.yang ├── bbf-vdsl-alarm-types.yang ├── bbf-vdsl-availability.yang ├── bbf-vdsl-base-body.yang ├── bbf-vdsl-base.yang ├── bbf-vdsl-data-gathering-profile-body.yang ├── bbf-vdsl-data-rate-profile-body.yang ├── bbf-vdsl-downstream-power-back-off-profile-body.yang ├── bbf-vdsl-impulse-noise-monitoring-profile-body.yang ├── bbf-vdsl-impulse-noise-protection-delay-profile-body.yang ├── bbf-vdsl-inventory-body.yang ├── bbf-vdsl-line-spectrum-profile-body.yang ├── bbf-vdsl-line-status-body.yang ├── bbf-vdsl-line.yang ├── bbf-vdsl-mode-specific-psd-profile-body.yang ├── bbf-vdsl-noise-margin-profile-body.yang ├── bbf-vdsl-performance-management.yang ├── bbf-vdsl-pointers.yang ├── bbf-vdsl-quality-profiles.yang ├── bbf-vdsl-radio-frequency-interference-profile-body.yang ├── bbf-vdsl-re-initialization-policy-profile-body.yang ├── bbf-vdsl-service-profiles.yang ├── bbf-vdsl-sos-profile-body.yang ├── bbf-vdsl-spectrum-profiles.yang ├── bbf-vdsl-status-monitoring.yang ├── bbf-vdsl-test-diagnostics.yang ├── bbf-vdsl-test-mode-body.yang ├── bbf-vdsl-threshold-crossing-alert-body.yang ├── bbf-vdsl-threshold-management.yang ├── bbf-vdsl-upstream-power-back-off-profile-body.yang ├── bbf-vdsl-vectoring-profile-body.yang ├── bbf-vdsl-virtual-noise-profile-body.yang ├── bbf-vdsl-xtu-band-status-body.yang ├── bbf-vdsl-xtu-channel-performance-body.yang ├── bbf-vdsl-xtu-channel-status-body.yang ├── bbf-vdsl-xtu-channel-threshold-profile-body.yang ├── bbf-vdsl-xtu-data-gathering-report-body.yang ├── bbf-vdsl-xtu-line-performance-body.yang ├── bbf-vdsl-xtu-line-status-body.yang ├── bbf-vdsl-xtu-line-threshold-profile-body.yang ├── bbf-vdsl-xtu-sub-carrier-status-body.yang ├── bbf-vdsl-xtu.yang ├── bbf-vdsl.yang ├── bbf-vlan-sub-interface-profile-fp.yang ├── bbf-vlan-sub-interface-profile-usage.yang ├── bbf-vlan-sub-interface-profiles.yang ├── bbf-xpon-base.yang ├── bbf-xpon-burst-profiles.yang ├── bbf-xpon-channel-group-body.yang ├── bbf-xpon-channel-pair-body.yang ├── bbf-xpon-channel-partition-body.yang ├── bbf-xpon-channel-termination-body.yang ├── bbf-xpon-defects.yang ├── bbf-xpon-if-type.yang ├── bbf-xpon-multicast-distribution-set-body.yang ├── bbf-xpon-multicast-gemport-body.yang ├── bbf-xpon-onu-authentication-features.yang ├── bbf-xpon-onu-authentication-types.yang ├── bbf-xpon-onu-authentication.yang ├── bbf-xpon-onu-state.yang ├── bbf-xpon-onu-types.yang ├── bbf-xpon-performance-management.yang ├── bbf-xpon-power-management.yang ├── bbf-xpon-types.yang ├── bbf-xpon-wavelength-profile-body.yang ├── bbf-xpon.yang ├── bbf-xponani-ani-body.yang ├── bbf-xponani-base.yang ├── bbf-xponani-power-management.yang ├── bbf-xponani-v-enet-body.yang ├── bbf-xponani.yang ├── bbf-xpongemtcont-base.yang ├── bbf-xpongemtcont-gemport-body.yang ├── bbf-xpongemtcont-gemport-performance-management.yang ├── bbf-xpongemtcont-qos.yang ├── bbf-xpongemtcont-tcont-body.yang ├── bbf-xpongemtcont-traffic-descriptor-profile-body.yang ├── bbf-xpongemtcont.yang ├── bbf-xponvani-base.yang ├── bbf-xponvani-onu-authentication-groupings.yang ├── bbf-xponvani-onu-authentication.yang ├── bbf-xponvani-power-management.yang ├── bbf-xponvani-v-ani-body.yang ├── bbf-xponvani-v-enet-body.yang └── bbf-xponvani.yang └── networking ├── bbf-ancp-alarm-types.yang ├── bbf-ancp-fastdsl-access-extensions.yang ├── bbf-ancp-fastdsl-threshold.yang ├── bbf-ancp-interfaces.yang ├── bbf-ancp.yang ├── bbf-dot1q-cfm-alarm-types.yang ├── bbf-dot1q-cfm-interfaces-state.yang ├── bbf-dot1q-cfm-interfaces.yang ├── bbf-dot1q-cfm-l2-forwarding.yang ├── bbf-dot1q-cfm.yang ├── bbf-eth-oam-interfaces.yang ├── bbf-eth-oam.yang ├── bbf-icmpv6-forwarding.yang ├── bbf-icmpv6-profile-common.yang ├── bbf-icmpv6.yang ├── bbf-l2-dhcpv4-relay-forwarding.yang ├── bbf-l2-dhcpv4-relay-profile-common.yang ├── bbf-l2-dhcpv4-relay.yang ├── bbf-l2-forwarding-alarm-types.yang ├── bbf-l2-forwarding-base.yang ├── bbf-l2-forwarding-flooding-policies.yang ├── bbf-l2-forwarding-forwarders.yang ├── bbf-l2-forwarding-forwarding-databases.yang ├── bbf-l2-forwarding-mac-learning-control.yang ├── bbf-l2-forwarding-mac-learning.yang ├── bbf-l2-forwarding-shared-fdb.yang ├── bbf-l2-forwarding-split-horizon-profiles.yang ├── bbf-l2-forwarding.yang ├── bbf-ldra-profile-common.yang ├── bbf-ldra.yang ├── bbf-mgmd-common.yang ├── bbf-mgmd-mrd.yang ├── bbf-mgmd-types.yang ├── bbf-mgmd.yang ├── bbf-network-map.yang ├── bbf-pppoe-intermediate-agent-profile-common.yang ├── bbf-pppoe-intermediate-agent.yang ├── bbf-qos-classifiers.yang ├── bbf-qos-composite-filters.yang ├── bbf-qos-enhanced-scheduling-state.yang ├── bbf-qos-enhanced-scheduling.yang ├── bbf-qos-filters.yang ├── bbf-qos-policer-envelope-profiles.yang ├── bbf-qos-policies-state.yang ├── bbf-qos-policies-sub-interface-rewrite.yang ├── bbf-qos-policies-sub-interfaces.yang ├── bbf-qos-policies.yang ├── bbf-qos-policing-state.yang ├── bbf-qos-policing-types.yang ├── bbf-qos-policing.yang ├── bbf-qos-rate-control.yang ├── bbf-qos-shaping.yang ├── bbf-qos-traffic-mngt-state.yang ├── bbf-qos-traffic-mngt.yang ├── bbf-qos-types.yang ├── bbf-subscriber-profile-common.yang ├── bbf-subscriber-profiles.yang ├── bbf-subscriber-types.yang ├── bbf-vlan-sub-interface-profile-dhcpv4.yang ├── bbf-vlan-sub-interface-profile-dhcpv6.yang ├── bbf-vlan-sub-interface-profile-icmpv6.yang ├── bbf-vlan-sub-interface-profile-pppoe.yang └── bbf-vlan-sub-interface-profile-qos.yang /.gitignore: -------------------------------------------------------------------------------- 1 | 2 | # ensure that docs won't be ignored 3 | !docs/ 4 | -------------------------------------------------------------------------------- /.mailmap: -------------------------------------------------------------------------------- 1 | William Lupton 2 | William Lupton 3 | -------------------------------------------------------------------------------- /CNAME: -------------------------------------------------------------------------------- 1 | yang.broadband-forum.org 2 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Copyright (c) 2016-2020, Broadband Forum 2 | All rights reserved. 3 | 4 | Redistribution and use in source and binary forms, with or 5 | without modification, are permitted provided that the following 6 | conditions are met: 7 | 8 | 1. Redistributions of source code must retain the above copyright 9 | notice, this list of conditions and the following disclaimer. 10 | 11 | 2. Redistributions in binary form must reproduce the above 12 | copyright notice, this list of conditions and the following 13 | disclaimer in the documentation and/or other materials 14 | provided with the distribution. 15 | 16 | 3. Neither the name of the copyright holder nor the names of its 17 | contributors may be used to endorse or promote products 18 | derived from this software without specific prior written 19 | permission. 20 | 21 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 22 | CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, 23 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 24 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 25 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 26 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 27 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 28 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 29 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 30 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 31 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 32 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 33 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 34 | 35 | The above license is used as a license under copyright only. 36 | Please reference the Forum IPR Policy for patent licensing terms 37 | . 38 | 39 | Any moral rights which are necessary to exercise under the above 40 | license grant are also deemed granted under this license. 41 | -------------------------------------------------------------------------------- /OD-360/01-intro.md: -------------------------------------------------------------------------------- 1 | --- 2 | bbfNumber: OD-360 3 | bbfTitle: BBF YANG Best Current Practices 4 | bbfIssue: Issue 5 | bbfVersion: 1 Amendment 2 6 | bbfMonth: January 7 | bbfYear: 2024 8 | bbfType: document 9 | bbfStatus: 10 | bbfContrib: 11 | 12 | # information shown on each page header 13 | siteurl: index.html 14 | project: Broadband Forum YANG Modules 15 | tagline: A set of YANG modules for managing access networks 16 | 17 | # this removes the release number from the default subtitle 18 | subtitle: '%bbfIssue%: %bbfVersion% %bbfStatus%' 19 | 20 | # don't display these in the banner 21 | version: '' 22 | status: '' 23 | 24 | # information shown in the footer 25 | reponame: yang 26 | repodesc: '%project%' 27 | 28 | # don't number sections (guidelines are already numbered manually) 29 | numberSections: false 30 | 31 | buttons: 32 | - label: HTML 33 | title: OD-360 Single-file HTML 34 | url: index.htm 35 | - label: PDF 36 | title: OD-360 PDF 37 | url: index.pdf 38 | - label: YANG Modules 39 | title: YANG modules on GitHub 40 | url: https://github.com/BroadbandForum/%reponame% 41 | 42 | bbfRevisionHistory: 43 | - number: Issue 1 44 | approval: 15 February 2022 45 | publication: 15 February 2022 46 | editors: | 47 | Joey Boyd, Adtran 48 | changes: Original 49 | - number: Issue 1 Amendment 1 50 | approval: 15 March 2023 51 | publication: 15 March 2023 52 | editors: | 53 | Joey Boyd, Adtran 54 | changes: Add 'units' statement guidelines 55 | - number: Issue 1 Amendment 2 56 | approval: 19 January 2024 57 | publication: 19 January 2024 58 | editors: | 59 | Joey Boyd, Adtran 60 | changes: Add new IETF guidelines IETF-21 and IETF-22. 61 | Add new BBF guidelines BBF-21 through BBF-29. 62 | Address minor corrections to existing guidelines. 63 | ... 64 | 65 | !include cover-page.md 66 | 67 | !include od-notice.md 68 | 69 | !include front-matter.md 70 | 71 | # References 72 | 73 | ::: {#refs} ::: 74 | ::: 75 | 76 | # Overview 77 | 78 | OD-360 provides a set of Best Current Practices for development of YANG Data Models in the Broadband Forum (BBF). The approach taken in establishing a set of best current practices is to utilize existing practices where those are relevant to the work of the Forum. The guidelines put forth by this document not only provide guidance for authors of BBF YANG models but are also enforced prior to YANG model publication to ensure a high level of quality and consistency across BBF projects. 79 | 80 | ## YANG Language Version 81 | 82 | The BBF has adopted YANG 1.1 @RFC7950 for use in all BBF YANG Data Models. 83 | 84 | # YANG Guidelines 85 | 86 | These YANG guidelines are organized as follows: 87 | 88 | * Those based on IETF YANG Guidelines 89 | * Additional BBF-specific guidelines 90 | 91 | ## Terminology 92 | 93 | Throughout these guidelines, the term module can be used as a generic term for 94 | a YANG module or submodule. When describing properties that are specific to 95 | submodules, the term submodule is used instead. 96 | 97 | ## Template 98 | 99 | New YANG modules MAY be created from the BBF template as shown here: 100 | [bbf-template.yang](https://wiki.broadband-forum.org/display/BBF/OD-360%3A+YANG+Module+Template). 101 | This template is based on the IETF YANG module template defined in the IETF YANG 102 | Guidelines. 103 | -------------------------------------------------------------------------------- /OD-360/NMDA/05-nmda.md: -------------------------------------------------------------------------------- 1 | ## BBF NMDA Guidelines {.new-file} 2 | 3 | The following guidelines relate to the creation and maintenance of BBF YANG models as they relate to the concept of Network Management Datastore Architecture (NMDA) defined in RFC 8342 @RFC8342. 4 | 5 | ### NMDA-1: Separate configuration and state nodes 6 | 7 | When a new model is created using non-NMDA syntax (i.e. split configuration and state data) for use in a non-NMDA server, and if any attribute has both configuration and state data, one of which is conditional via a feature and/or a "when" statement, then the configuration and state data nodes should not be named the same. This will allow migration to NMDA servers using NMDA compliant syntax (i.e. configuration and state data merged into single nodes) at a later time, preserving both the conditional nature and the intended ability to support the same state data node in the NMDA model with just a change in namespace. 8 | 9 | Example model with configuration of 'id' dependent on the feature 'configurable-id' while the state node, 'id', is always valid. 10 | 11 | ``` 12 | module: bbf-things 13 | +--rw things 14 | | +--rw thing* [name] 15 | | +--rw name string 16 | | +--rw id uint32 {configurable-id} 17 | +--ro things-state 18 | | +--ro thing* [name] 19 | | +--ro name string 20 | | +--ro id uint32 21 | ``` 22 | 23 | The same example model with this guideline applied. 24 | 25 | ``` 26 | module: bbf-things 27 | +--rw things 28 | | +--rw thing* [name] 29 | | +--rw name string 30 | | +--rw id uint32 {configurable-id} 31 | +--ro things-state 32 | | +--ro thing* [name] 33 | | +--ro name string 34 | | +--ro actual-id uint32 35 | ``` 36 | 37 | ### NMDA-2: Configuration of a read-only node in an existing published model 38 | 39 | If a published standard NMDA syntax compliant model contains a read-only node which needs to now be configurable, a read-write node should be augmented into the published standard to allow for configuration. A side effect of this is there are now two methods to retrieve the same operational value. 40 | 41 | Example from *ietf-hardware @RFC8348*. 42 | 43 | ``` 44 | module: ietf-hardware 45 | +--rw hardware 46 | | +--rw component* [name] 47 | | +--rw name string 48 | | +--ro model-name? string 49 | ``` 50 | 51 | One possible method to augment a configurable 'model-name'. 52 | 53 | ``` 54 | module: ietf-hardware 55 | +--rw hardware 56 | | +--rw component* [name] 57 | | +--rw name string 58 | | +--ro model-name? string 59 | | +--rw configuration 60 | | +--rw model-name? string 61 | ``` 62 | -------------------------------------------------------------------------------- /OD-360/images/ecosystem.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/OD-360/images/ecosystem.png -------------------------------------------------------------------------------- /check.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # 3 | # BBF check script (loosely) based on the IETF one. 4 | # 5 | # Invoke without arguments from the top level of a YangModels/yang checkout. 6 | # 7 | # Invoke with the -h option to see command-line options. 8 | 9 | # remember the current directory 10 | cwd=`pwd` 11 | 12 | # process arguments 13 | bbf_dir="$cwd/standard/bbf" 14 | before_dir="$cwd/experimental" 15 | ietf_dir="$cwd/standard/ietf" 16 | after_dir="" 17 | ieee_dir="$cwd/standard/ieee" 18 | pyang="pyang" 19 | debug="" 20 | dryrun="" 21 | while getopts "b:e:i:E:I:p:dnh" option; do 22 | case "$option" in 23 | b) bbf_dir="$OPTARG";; 24 | e) before_dir="$OPTARG";; 25 | i) ietf_dir="$OPTARG";; 26 | E) after_dir="$OPTARG";; 27 | I) ieee_dir="$OPTARG";; 28 | p) pyang="$OPTARG";; 29 | d) debug="true";; 30 | n) dryrun="true";; 31 | h|*) cat <&1 echo "warning: $dir doesn't exist" 104 | else 105 | pyang_flags+=" --path=$dir" 106 | fi 107 | done 108 | 109 | if [ -n "$debug" ]; then 110 | pyang_flags+=" --verbose" 111 | fi 112 | 113 | # helper function for checking YANG files in a directory 114 | check_dir () { 115 | local dir="$bbf_dir/$1" 116 | printf "\n" 117 | echo Checking YANG files in $dir 118 | exit_status="" 119 | for f in `find $dir -name '*.yang'`; do 120 | if [ -n "$debug" ]; then 121 | echo "Checking $f" 122 | fi 123 | if [ -n "$dryrun" ]; then 124 | echo "$pyang $pyang_flags" 125 | else 126 | errors=`$pyang $pyang_flags $f 2>&1 | grep "error:"` 127 | if [ -n "$errors" ]; then 128 | echo "Errors in $f" 129 | printf "\n $errors \n" 130 | exit_status="failed!" 131 | fi 132 | fi 133 | done 134 | if [ -n "$exit_status" ]; then 135 | exit 1 136 | fi 137 | } 138 | 139 | echo "Checking modules with pyang command:" 140 | printf "\nPYTHONPATH=$PYTHONPATH $pyang $pyang_flags MODULE\n" 141 | 142 | for d in $to_check; do 143 | check_dir "$d" 144 | done 145 | -------------------------------------------------------------------------------- /docs/.nojekyll: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/.nojekyll -------------------------------------------------------------------------------- /docs/CNAME: -------------------------------------------------------------------------------- 1 | yang.broadband-forum.org 2 | -------------------------------------------------------------------------------- /docs/YANG-develop-105.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/YANG-develop-105.pdf -------------------------------------------------------------------------------- /docs/bbflogo-bw.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/bbflogo-bw.png -------------------------------------------------------------------------------- /docs/bbflogo-reverse-dark.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/bbflogo-reverse-dark.png -------------------------------------------------------------------------------- /docs/bee.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/bee.png -------------------------------------------------------------------------------- /docs/broadband-forum-logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/broadband-forum-logo.png -------------------------------------------------------------------------------- /docs/docx-defaults.yaml: -------------------------------------------------------------------------------- 1 | # DOCX (Word) pandoc defaults file (YAML) 2 | 3 | # XXX environment variable substitution only works for file paths, and doesn't 4 | # work for PDF engine options, so in fact we preprocess this file to 5 | # substitute ../../../install/pandoc/ etc. 6 | 7 | standalone: true 8 | 9 | # XXX this shouldn't be necessary, but the DOCX writer appears to fetch all 10 | # resources mentioned in the metadata regardless of whether they're used 11 | resource-path: 12 | - ../docs 13 | -------------------------------------------------------------------------------- /docs/images/ecosystem.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/images/ecosystem.png -------------------------------------------------------------------------------- /docs/index.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/index.docx -------------------------------------------------------------------------------- /docs/index.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/index.pdf -------------------------------------------------------------------------------- /docs/json-defaults.yaml: -------------------------------------------------------------------------------- 1 | # JSON pandoc defaults file (YAML) 2 | 3 | # XXX environment variable substitution only works for file paths, and doesn't 4 | # work for PDF engine options, so in fact we preprocess this file to 5 | # substitute ../../../install/pandoc/ etc. 6 | 7 | from: markdown-raw_html 8 | 9 | strip-comments: true 10 | 11 | metadata-files: 12 | - bbf-metadata.yaml 13 | 14 | # XXX the resource path includes the data directory but this is only intended 15 | # for bibliography files, which surely should be searched for in the data 16 | # directory? it also includes PROJECTYAMLTARGETDIR for PROJECT.yaml build 17 | # products and TARGETDIR for regular build products 18 | resource-path: 19 | - . 20 | - ../docs 21 | - ../docs 22 | - ../../../install/pandoc//csl 23 | - ../../../install/pandoc//css 24 | - ../../../install/pandoc//markdown 25 | 26 | filters: 27 | # XXX remove-toc-token.lua is barely worth it 28 | - remove-toc-token.lua 29 | - add-description.lua 30 | - expand-macros.lua 31 | - pandoc-include-basic.lua 32 | - expand-macros.lua 33 | - list-table.lua 34 | # XXX expand-divs.lua is obsolete and should be retired 35 | - expand-divs.lua 36 | - table-attrs.lua 37 | - code-block-filters.lua 38 | - auto-identifiers.lua 39 | - pandoc-crossref-basic.lua 40 | - special-headers.lua 41 | - fix-references.lua 42 | - auto-references.lua 43 | - citeproc 44 | - add-hyperlinks.lua 45 | # XXX is this still needed? 46 | # - save-metadata.lua 47 | 48 | # metadata values specified here are parsed as literal strings, not markdown 49 | metadata: 50 | 51 | bibliography: 52 | - all.bib 53 | - bbf-biblio-csl.json 54 | 55 | citation-style: bbf.csl 56 | 57 | # this can be passed to filters, which can add it to PYTHONPATH 58 | PYTHONDIR: ../../../install/pandoc//../python 59 | -------------------------------------------------------------------------------- /docs/missing.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/missing.png -------------------------------------------------------------------------------- /docs/pandoc-tests.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | -------------------------------------------------------------------------------- /docs/pdf-defaults.yaml: -------------------------------------------------------------------------------- 1 | # PDF pandoc defaults file (YAML) 2 | 3 | # XXX environment variable substitution only works for file paths, and doesn't 4 | # work for PDF engine options, so in fact we preprocess this file to 5 | # substitute ../../../install/pandoc/ etc. 6 | 7 | standalone: true 8 | 9 | # wkhtmltopdf PDF generation uses the default HTML template 10 | 11 | # PDF generation requires valid paths at build time 12 | # (the make rules copy CSS files to TARGETDIR but we don't assume this here) 13 | css: 14 | - ../../../install/pandoc//css/bbf.css 15 | - ../../../install/pandoc//css/extra.css 16 | - ../../../install/pandoc//css/release.css 17 | 18 | pdf-engine: wkhtmltopdf 19 | 20 | # wkhtmltopdf doesn't support --option=value, so each such is two options 21 | # (and all options have to be strings) 22 | pdf-engine-opts: 23 | - --print-media-type 24 | 25 | - --page-size 26 | - Letter 27 | 28 | - --minimum-font-size 29 | - '10' 30 | 31 | # XXX the built-in table of contents needs more work: 32 | # - need to honor the .unlisted class (unfortunately it's not supplied) 33 | # - --outline-depth 34 | # - '3' (needs to come from the PANDOCTOCDEPTH makefile variable) 35 | 36 | - --header-html 37 | - ../../../install/pandoc//css/pdf-header.html 38 | 39 | - --header-spacing 40 | - '4' 41 | 42 | - --footer-html 43 | - ../../../install/pandoc//css/pdf-footer.html 44 | 45 | - --footer-spacing 46 | - '4' 47 | 48 | # XXX on Bamboo, headers and footers can be missing from the first 10-20 49 | # pages; could this be fixed by --window-status or --javascript-delay? 50 | # see https://stackoverflow.com/questions/23649780 51 | # this is the delay in milliseconds 52 | # - --javascript-delay 53 | # - '5000' (needs to come from the PANDOCPDFENGINEDELAY makefile variable) 54 | 55 | # JavaScript debugging; enable this if something isn't working 56 | - --debug-javascript 57 | 58 | # XXX cover page needs more work: 59 | # - need to generate it (because it's not passed query parameters) 60 | # - need to honor the watermark background 61 | # - need to adjust page-1 header hiding? 62 | # - need to suppress the title and subtitle 63 | # - cover ../../../install/pandoc//css/pdf-cover.html 64 | 65 | # XXX see above for built-in table of contents notes 66 | # - toc 67 | # - --enable-toc-back-links 68 | -------------------------------------------------------------------------------- /docs/pencil.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/pencil.png -------------------------------------------------------------------------------- /docs/permalink.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/permalink.png -------------------------------------------------------------------------------- /docs/release.css: -------------------------------------------------------------------------------- 1 | /* values defined in this file can be updated when building or deploying */ 2 | span.release::before { content: "(TR-451-v1.1.0-105)"; } 3 | -------------------------------------------------------------------------------- /docs/release.css.bak: -------------------------------------------------------------------------------- 1 | /* values defined in this file can be updated when building or deploying */ 2 | span.release::before { content: "(develop-105)"; } 3 | -------------------------------------------------------------------------------- /docs/right.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/right.png -------------------------------------------------------------------------------- /docs/tick.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/BroadbandForum/yang/335a99ea68b17fad83a80250febb0ded053646d7/docs/tick.png -------------------------------------------------------------------------------- /docs/toc.css: -------------------------------------------------------------------------------- 1 | /* BBF ToC (table of contents) CSS */ 2 | 3 | :root { 4 | --toc-width: 15rem; 5 | --toc-padding-left-extra: 1rem; 6 | --toc-padding-left: calc(var(--toc-width) + var(--toc-padding-left-extra)); 7 | } 8 | 9 | /* these are pandoc's default ToC settings */ 10 | #TOC li { 11 | list-style: none; 12 | } 13 | 14 | #TOC ul { 15 | padding-left: 1.3em; 16 | } 17 | 18 | #TOC > ul { 19 | padding-left: 0; 20 | } 21 | 22 | #TOC a:not(:hover) { 23 | text-decoration: none; 24 | } 25 | 26 | @media screen and (min-width: 924px) { 27 | body { 28 | padding-left: var(--toc-padding-left); 29 | } 30 | 31 | #SIDEBAR::before { 32 | content: "Table of Contents"; 33 | font-weight: bold; 34 | } 35 | 36 | #SIDEBAR { 37 | position: fixed; 38 | margin: 0 0; 39 | top: 0px; 40 | left: 0px; 41 | width: var(--toc-width); 42 | height: 100vh; 43 | line-height: 1.4; 44 | font-size: smaller; 45 | overflow: auto; 46 | overscroll-behavior: contain; 47 | /* background-color: white; */ 48 | border: 1px solid #73AD21; 49 | } 50 | 51 | #SIDEBAR ul { 52 | margin: 0.35em 0; 53 | padding: 0 0 0 1em; 54 | list-style-type: none; 55 | } 56 | 57 | #SIDEBAR ul ul { 58 | margin: 0.25em 0; 59 | } 60 | 61 | #SIDEBAR ul ul ul { 62 | margin: 0.15em 0; 63 | } 64 | 65 | #SIDEBAR li p:last-child { 66 | margin-bottom: 0; 67 | } 68 | 69 | #SIDEBAR { 70 | z-index: 2; 71 | } 72 | 73 | #SIDEBAR a:not(:hover) { 74 | text-decoration: none; 75 | } 76 | } 77 | 78 | @media screen and (max-width: 923px) { 79 | #SIDEBAR { 80 | display: none; 81 | } 82 | } 83 | 84 | @media not screen { 85 | #SIDEBAR { 86 | display: none; 87 | } 88 | } 89 | -------------------------------------------------------------------------------- /docs/typst-defaults.yaml: -------------------------------------------------------------------------------- 1 | # Typst pandoc defaults file (YAML) 2 | 3 | # --columns defaults to 72 4 | # - tables might work better with a lower value, because pandoc uses it to 5 | # determine when a table occupies the full page width 6 | # - but too low a value might cause undesirable line splitting 7 | # - use PANDOCTYPSTFLAGS += --columns=N to override this 8 | 9 | standalone: true 10 | 11 | # XXX need the full path because it's used to find other lua modules 12 | to: ../../../install/pandoc//custom/typst-writer.lua-citations 13 | 14 | # this is the pandoc template 15 | template: extended-template.typ 16 | 17 | metadata: 18 | # this is included by the above pandoc template 19 | template: typst-template.typ 20 | 21 | filters: 22 | - typst-reorder.lua 23 | -------------------------------------------------------------------------------- /docs/typst-stringify.typ: -------------------------------------------------------------------------------- 1 | // copied from BBF PDF Template 2 | // XXX can you use local packages on the server? 3 | 4 | #let stringify(value, as_list: false) = { 5 | let comps = () 6 | if type(value) == "none" { 7 | // ignore 8 | } 9 | else if type(value) == "array" { 10 | for (i, item) in value.enumerate() { 11 | // XXX should this add a separator? this one? 12 | if i > 0 { 13 | comps.push(" " + sym.plus.circle + " ") 14 | } 15 | comps += stringify(item, as_list: true) 16 | } 17 | } 18 | else if type(value) == "dictionary" { 19 | for (i, pair) in value.pairs().enumerate() { 20 | // XXX should this add a separator? this one? 21 | if i > 0 { 22 | comps.push(" " + sym.plus.circle + " ") 23 | } 24 | // XXX shouldn't ignore the key? 25 | let (key, val) = pair 26 | comps += stringify(val, as_list: true) 27 | } 28 | } 29 | else if type(value) != "content" { 30 | // XXX might need to check some more types 31 | comps.push(str(value)) 32 | } else if repr(value.func()) in ("space", "linebreak", "parbreak") { 33 | // XXX using repr is rather naughty 34 | // XXX space and parbreak aren't documented? 35 | comps.push(" ") 36 | } else if value.has("text") { 37 | comps.push(value.text) 38 | } else if value.has("body") { 39 | comps += stringify(value.body, as_list: true) 40 | } else if value.has("children") { 41 | for child in value.children { 42 | comps += stringify(child, as_list: true) 43 | } 44 | } else { 45 | // XXX not yet handled 46 | comps.push("") 47 | } 48 | 49 | if as_list { 50 | return comps 51 | } else if comps.len() == 0 { 52 | // XXX joining an empty array returns none; is this a bug? 53 | return "" 54 | } else { 55 | return comps.join() 56 | } 57 | } 58 | 59 | // test 60 | #let test_stringify(content) = { 61 | [#repr(content) -> #stringify(content) \ ] 62 | } 63 | 64 | = Test stringify 65 | 66 | #for content in ( 67 | none, 68 | 1, 69 | "", 70 | "1 2 3", 71 | (), 72 | ((1,), (2, 3)), 73 | ([*a* b], [c]), 74 | (a: 1, b: 2) 75 | ){ 76 | test_stringify(content) 77 | } -------------------------------------------------------------------------------- /docs/watermark-pdf.css: -------------------------------------------------------------------------------- 1 | /* XXX a separate file is used for PDF because wkhtmltopdf doesn't seem to 2 | support media types for background images? */ 3 | 4 | body { 5 | background-image: url("watermark.png"); 6 | background-origin: content-box; 7 | background-repeat: repeat-y; 8 | background-size: 100%; 9 | } 10 | -------------------------------------------------------------------------------- /docs/watermark.css: -------------------------------------------------------------------------------- 1 | .main-content { 2 | background-image: url("watermark.png"); 3 | background-origin: content-box; 4 | background-repeat: repeat-y; 5 | background-size: 100%; 6 | } 7 | -------------------------------------------------------------------------------- /standard/application/bbf-d-olt-onuauth-types.yang: -------------------------------------------------------------------------------- 1 | module bbf-d-olt-onuauth-types { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-d-olt-onuauth-types"; 4 | prefix bbf-d-olt-onuautht; 5 | 6 | import bbf-xpon-onu-authentication-types { 7 | prefix bbf-xpon-onu-autht; 8 | } 9 | 10 | organization 11 | "Broadband Forum 12 | SDN/NFV Work Area"; 13 | contact 14 | "Comments or questions about this Broadband Forum YANG module 15 | should be directed to . 16 | 17 | Editor: Andre Brizido, Altice Labs 18 | 19 | Editor: Antonio Marsico, Reply 20 | 21 | PS Leader: Haomian Zheng, Huawei 22 | 23 | WA Director: Mengmeng Li, China Mobile 24 | 25 | WA Director: Bruno Cornaglia, Vodafone"; 26 | description 27 | "This module contains a collection of YANG definitions for 28 | supporting the Broadband Forum requirements for disaggregation 29 | of network functions from a physical OLT (pOLT) into a 30 | Disaggregated OLT instance (D-OLT) as described in TR-477. 31 | 32 | Specifically, this module defines YANG types used by the D-OLT 33 | Optical Network Unit (ONU) Authentication functionality. 34 | 35 | Copyright (c) 2024, Broadband Forum 36 | 37 | Redistribution and use in source and binary forms, with or 38 | without modification, are permitted provided that the following 39 | conditions are met: 40 | 41 | 1. Redistributions of source code must retain the above copyright 42 | notice, this list of conditions and the following disclaimer. 43 | 44 | 2. Redistributions in binary form must reproduce the above 45 | copyright notice, this list of conditions and the following 46 | disclaimer in the documentation and/or other materials 47 | provided with the distribution. 48 | 49 | 3. Neither the name of the copyright holder nor the names of its 50 | contributors may be used to endorse or promote products 51 | derived from this software without specific prior written 52 | permission. 53 | 54 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 55 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 56 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 57 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 58 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 59 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 60 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 61 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 62 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 63 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 64 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 65 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 66 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 67 | 68 | The above license is used as a license under copyright only. 69 | Please reference the Forum IPR Policy for patent licensing terms 70 | . 71 | 72 | Any moral rights which are necessary to exercise under the above 73 | license grant are also deemed granted under this license. 74 | 75 | This version of this YANG module is part of TR-477; see 76 | the TR itself for full legal notices."; 77 | 78 | revision 2024-01-19 { 79 | description 80 | "Issue 1. 81 | * Approval Date: 2024-01-19. 82 | * Publication Date: 2024-01-19."; 83 | reference 84 | "TR-477: Cloud CO Enhancement - Access Node Functional 85 | Disaggregation "; 87 | } 88 | 89 | identity onu-auth-successful-and-reported-to-polt { 90 | base bbf-xpon-onu-autht:onu-authentication-successful; 91 | description 92 | "The D-OLT matched the ONU credentials on a specific vANI and 93 | could successfully report the positive result of the 94 | authentication to the pOLT."; 95 | } 96 | 97 | identity onu-auth-successful-but-polt-report-failed { 98 | base bbf-xpon-onu-autht:onu-authentication-successful; 99 | description 100 | "The D-OLT matched the ONU credentials on a specific vANI but 101 | could not successfully report the positive result of the 102 | authentication to the pOLT."; 103 | } 104 | } 105 | -------------------------------------------------------------------------------- /standard/application/bbf-olt-vomci-grpc-client-tcp.yang: -------------------------------------------------------------------------------- 1 | module bbf-olt-vomci-grpc-client-tcp { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-olt-vomci-grpc-client-tcp"; 4 | prefix bbf-olt-vomci-grpcc-tcp; 5 | 6 | import bbf-olt-vomci { 7 | prefix bbf-olt-vomci; 8 | } 9 | import bbf-olt-vomci-grpc-client { 10 | prefix bbf-olt-vomci-grpcc; 11 | } 12 | import ietf-tcp-client { 13 | prefix tcpc; 14 | } 15 | import bbf-vomci-grpc-common { 16 | prefix bbf-vomci-grpc-c; 17 | } 18 | 19 | organization 20 | "Broadband Forum 21 | SDN/NFV Work Area"; 22 | contact 23 | "Comments or questions about this Broadband Forum YANG module 24 | should be directed to . 25 | 26 | Editor: Andre Brizido, Altice Labs 27 | 28 | PS Leader: Ken Kerpez, DZS 29 | 30 | WA Director: Mengmeng Li, China Mobile 31 | 32 | WA Director: Bruno Cornaglia, Vodafone 33 | 34 | WA Director: Haomian Zheng, Huawei"; 35 | description 36 | "This module contains a collection of YANG definitions for 37 | supporting the Broadband Forum requirements for gRPC client 38 | functionality over TCP transport as described in TR-451. 39 | 40 | Copyright (c) 2019-2025, Broadband Forum 41 | 42 | Redistribution and use in source and binary forms, with or 43 | without modification, are permitted provided that the following 44 | conditions are met: 45 | 46 | 1. Redistributions of source code must retain the above copyright 47 | notice, this list of conditions and the following disclaimer. 48 | 49 | 2. Redistributions in binary form must reproduce the above 50 | copyright notice, this list of conditions and the following 51 | disclaimer in the documentation and/or other materials 52 | provided with the distribution. 53 | 54 | 3. Neither the name of the copyright holder nor the names of its 55 | contributors may be used to endorse or promote products 56 | derived from this software without specific prior written 57 | permission. 58 | 59 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 60 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 61 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 62 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 63 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 64 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 65 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 66 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 67 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 68 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 69 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 70 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 71 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 72 | 73 | The above license is used as a license under copyright only. 74 | Please reference the Forum IPR Policy for patent licensing terms 75 | . 76 | 77 | Any moral rights which are necessary to exercise under the above 78 | license grant are also deemed granted under this license. 79 | 80 | This version of this YANG module is part of TR-451a1; see 81 | the TR itself for full legal notices."; 82 | 83 | revision 2025-02-03 { 84 | description 85 | "Amendment 1. 86 | * Approval Date: 2025-02-03. 87 | * Publication Date: 2025-02-03."; 88 | reference 89 | "TR-451a1: vOMCI Specification 90 | "; 92 | } 93 | 94 | augment "/bbf-olt-vomci:remote-nf" 95 | + "/bbf-olt-vomci:nf-client" 96 | + "/bbf-olt-vomci:initiate" 97 | + "/bbf-olt-vomci:remote-server" 98 | + "/bbf-olt-vomci:transport" 99 | + "/bbf-olt-vomci-grpcc:grpc" 100 | + "/bbf-olt-vomci-grpcc:grpc-client" 101 | + "/bbf-olt-vomci-grpcc:access-point" 102 | + "/bbf-olt-vomci-grpcc:grpc-transport-parameters" 103 | + "/bbf-olt-vomci-grpcc:tcp-client-options" { 104 | description 105 | "The gRPC connection parameters for TCP transport."; 106 | case tcp-transport { 107 | description 108 | "Selection for TCP transport."; 109 | container tcp-client-parameters { 110 | description 111 | "The TCP configuration."; 112 | uses tcpc:tcp-client-grouping; 113 | uses bbf-vomci-grpc-c:client-authentication; 114 | } 115 | } 116 | } 117 | } 118 | -------------------------------------------------------------------------------- /standard/application/bbf-olt-vomci-grpc-client.yang: -------------------------------------------------------------------------------- 1 | module bbf-olt-vomci-grpc-client { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-olt-vomci-grpc-client"; 4 | prefix bbf-olt-vomci-grpcc; 5 | 6 | import bbf-grpc-client { 7 | prefix bbf-grpcc; 8 | } 9 | import bbf-olt-vomci { 10 | prefix bbf-olt-vomci; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for gRPC client 30 | functionality as described in TR-451. 31 | 32 | Copyright (c) 2019-2022, Broadband Forum 33 | 34 | Redistribution and use in source and binary forms, with or 35 | without modification, are permitted provided that the following 36 | conditions are met: 37 | 38 | 1. Redistributions of source code must retain the above copyright 39 | notice, this list of conditions and the following disclaimer. 40 | 41 | 2. Redistributions in binary form must reproduce the above 42 | copyright notice, this list of conditions and the following 43 | disclaimer in the documentation and/or other materials 44 | provided with the distribution. 45 | 46 | 3. Neither the name of the copyright holder nor the names of its 47 | contributors may be used to endorse or promote products 48 | derived from this software without specific prior written 49 | permission. 50 | 51 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 52 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 53 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 54 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 55 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 56 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 57 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 58 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 59 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 60 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 61 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 62 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 63 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 64 | 65 | The above license is used as a license under copyright only. 66 | Please reference the Forum IPR Policy for patent licensing terms 67 | . 68 | 69 | Any moral rights which are necessary to exercise under the above 70 | license grant are also deemed granted under this license. 71 | 72 | This version of this YANG module is part of TR-451; see 73 | the TR itself for full legal notices."; 74 | 75 | revision 2022-06-07 { 76 | description 77 | "Issue 1. 78 | * Approval Date: 2022-06-07. 79 | * Publication Date: 2022-06-07."; 80 | reference 81 | "TR-451: vOMCI Specification 82 | "; 84 | } 85 | 86 | // gRPC client transport specific augment 87 | 88 | augment "/bbf-olt-vomci:remote-nf" 89 | + "/bbf-olt-vomci:nf-client" 90 | + "/bbf-olt-vomci:initiate" 91 | + "/bbf-olt-vomci:remote-server" 92 | + "/bbf-olt-vomci:transport" { 93 | description 94 | "The gRPC client transport."; 95 | case grpc { 96 | description 97 | "Selection for gRPC client transport."; 98 | uses bbf-grpcc:grpc-client-transport; 99 | } 100 | } 101 | } 102 | -------------------------------------------------------------------------------- /standard/application/bbf-olt-vomci-grpc-server-tcp.yang: -------------------------------------------------------------------------------- 1 | module bbf-olt-vomci-grpc-server-tcp { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-olt-vomci-grpc-server-tcp"; 4 | prefix bbf-olt-vomci-grpcs-tcp; 5 | 6 | import bbf-olt-vomci { 7 | prefix bbf-olt-vomci; 8 | } 9 | import bbf-olt-vomci-grpc-server { 10 | prefix bbf-olt-vomci-grpcs; 11 | } 12 | import ietf-tcp-server { 13 | prefix tcps; 14 | } 15 | import bbf-vomci-grpc-common { 16 | prefix bbf-vomci-grpc-c; 17 | } 18 | 19 | organization 20 | "Broadband Forum 21 | SDN/NFV Work Area"; 22 | contact 23 | "Comments or questions about this Broadband Forum YANG module 24 | should be directed to . 25 | 26 | Editor: Andre Brizido, Altice Labs 27 | 28 | PS Leader: Ken Kerpez, DZS 29 | 30 | WA Director: Mengmeng Li, China Mobile 31 | 32 | WA Director: Bruno Cornaglia, Vodafone 33 | 34 | WA Director: Haomian Zheng, Huawei"; 35 | description 36 | "This module contains a collection of YANG definitions for 37 | supporting the Broadband Forum requirements for gRPC server 38 | functionality over TCP transport as described in TR-451. 39 | 40 | Copyright (c) 2019-2025, Broadband Forum 41 | 42 | Redistribution and use in source and binary forms, with or 43 | without modification, are permitted provided that the following 44 | conditions are met: 45 | 46 | 1. Redistributions of source code must retain the above copyright 47 | notice, this list of conditions and the following disclaimer. 48 | 49 | 2. Redistributions in binary form must reproduce the above 50 | copyright notice, this list of conditions and the following 51 | disclaimer in the documentation and/or other materials 52 | provided with the distribution. 53 | 54 | 3. Neither the name of the copyright holder nor the names of its 55 | contributors may be used to endorse or promote products 56 | derived from this software without specific prior written 57 | permission. 58 | 59 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 60 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 61 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 62 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 63 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 64 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 65 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 66 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 67 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 68 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 69 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 70 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 71 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 72 | 73 | The above license is used as a license under copyright only. 74 | Please reference the Forum IPR Policy for patent licensing terms 75 | . 76 | 77 | Any moral rights which are necessary to exercise under the above 78 | license grant are also deemed granted under this license. 79 | 80 | This version of this YANG module is part of TR-451a1; see 81 | the TR itself for full legal notices."; 82 | 83 | revision 2025-02-03 { 84 | description 85 | "Amendment 1. 86 | * Approval Date: 2025-02-03. 87 | * Publication Date: 2025-02-03."; 88 | reference 89 | "TR-451a1: vOMCI Specification 90 | "; 92 | } 93 | 94 | augment "/bbf-olt-vomci:remote-nf" 95 | + "/bbf-olt-vomci:nf-server" 96 | + "/bbf-olt-vomci:listen" 97 | + "/bbf-olt-vomci:listen-endpoint" 98 | + "/bbf-olt-vomci:transport" 99 | + "/bbf-olt-vomci-grpcs:grpc" 100 | + "/bbf-olt-vomci-grpcs:grpc-server" 101 | + "/bbf-olt-vomci-grpcs:tcp-client-options" { 102 | description 103 | "The gRPC server connection parameters for TCP transport."; 104 | case tcp-transport { 105 | description 106 | "Select TCP transport."; 107 | container tcp-server-parameters { 108 | description 109 | "The TCP configuration."; 110 | uses tcps:tcp-server-grouping; 111 | uses bbf-vomci-grpc-c:server-authentication; 112 | } 113 | } 114 | } 115 | } 116 | -------------------------------------------------------------------------------- /standard/application/bbf-olt-vomci-grpc-server.yang: -------------------------------------------------------------------------------- 1 | module bbf-olt-vomci-grpc-server { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-olt-vomci-grpc-server"; 4 | prefix bbf-olt-vomci-grpcs; 5 | 6 | import bbf-grpc-server { 7 | prefix bbf-grpcs; 8 | } 9 | import bbf-olt-vomci { 10 | prefix bbf-olt-vomci; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for gRPC server 30 | functionality as described in TR-451. 31 | 32 | Copyright (c) 2019-2022, Broadband Forum 33 | 34 | Redistribution and use in source and binary forms, with or 35 | without modification, are permitted provided that the following 36 | conditions are met: 37 | 38 | 1. Redistributions of source code must retain the above copyright 39 | notice, this list of conditions and the following disclaimer. 40 | 41 | 2. Redistributions in binary form must reproduce the above 42 | copyright notice, this list of conditions and the following 43 | disclaimer in the documentation and/or other materials 44 | provided with the distribution. 45 | 46 | 3. Neither the name of the copyright holder nor the names of its 47 | contributors may be used to endorse or promote products 48 | derived from this software without specific prior written 49 | permission. 50 | 51 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 52 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 53 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 54 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 55 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 56 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 57 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 58 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 59 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 60 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 61 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 62 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 63 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 64 | 65 | The above license is used as a license under copyright only. 66 | Please reference the Forum IPR Policy for patent licensing terms 67 | . 68 | 69 | Any moral rights which are necessary to exercise under the above 70 | license grant are also deemed granted under this license. 71 | 72 | This version of this YANG module is part of TR-451; see 73 | the TR itself for full legal notices."; 74 | 75 | revision 2022-06-07 { 76 | description 77 | "Issue 1. 78 | * Approval Date: 2022-06-07. 79 | * Publication Date: 2022-06-07."; 80 | reference 81 | "TR-451: vOMCI Specification 82 | "; 84 | } 85 | 86 | // gRPC server transport specific augment 87 | 88 | augment "/bbf-olt-vomci:remote-nf" 89 | + "/bbf-olt-vomci:nf-server" 90 | + "/bbf-olt-vomci:listen" 91 | + "/bbf-olt-vomci:listen-endpoint" 92 | + "/bbf-olt-vomci:transport" { 93 | description 94 | "The gRPC server transport."; 95 | case grpc { 96 | description 97 | "Selection for gRPC server transport."; 98 | uses bbf-grpcs:grpc-server-transport; 99 | } 100 | } 101 | } 102 | -------------------------------------------------------------------------------- /standard/application/bbf-onu-management-proxy-grpc-client-tcp.yang: -------------------------------------------------------------------------------- 1 | module bbf-onu-management-proxy-grpc-client-tcp { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-onu-management-proxy-grpc-client-tcp"; 4 | prefix bbf-onu-mgmt-p-grpcc-tcp; 5 | 6 | import bbf-onu-management-proxy { 7 | prefix bbf-onu-mgmt-p; 8 | } 9 | import bbf-onu-management-proxy-grpc-client { 10 | prefix bbf-onu-mgmt-p-grpcc; 11 | } 12 | import ietf-tcp-client { 13 | prefix tcpc; 14 | } 15 | 16 | organization 17 | "Broadband Forum 18 | SDN/NFV Work Area"; 19 | contact 20 | "Comments or questions about this Broadband Forum YANG module 21 | should be directed to . 22 | 23 | Editor: Andre Brizido, Altice Labs 24 | 25 | PS Leader: Ken Kerpez, DZS 26 | 27 | WA Director: Mengmeng Li, China Mobile 28 | 29 | WA Director: Bruno Cornaglia, Vodafone 30 | 31 | WA Director: Haomian Zheng, Huawei"; 32 | description 33 | "This module contains a collection of YANG definitions for 34 | supporting the Broadband Forum requirements for gRPC client 35 | ONU Management-Proxy functionality over TCP transport as 36 | described in TR-451. 37 | 38 | Copyright (c) 2019-2025, Broadband Forum 39 | 40 | Redistribution and use in source and binary forms, with or 41 | without modification, are permitted provided that the following 42 | conditions are met: 43 | 44 | 1. Redistributions of source code must retain the above copyright 45 | notice, this list of conditions and the following disclaimer. 46 | 47 | 2. Redistributions in binary form must reproduce the above 48 | copyright notice, this list of conditions and the following 49 | disclaimer in the documentation and/or other materials 50 | provided with the distribution. 51 | 52 | 3. Neither the name of the copyright holder nor the names of its 53 | contributors may be used to endorse or promote products 54 | derived from this software without specific prior written 55 | permission. 56 | 57 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 58 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 59 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 60 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 61 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 62 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 63 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 64 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 65 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 66 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 67 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 68 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 69 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 70 | 71 | The above license is used as a license under copyright only. 72 | Please reference the Forum IPR Policy for patent licensing terms 73 | . 74 | 75 | Any moral rights which are necessary to exercise under the above 76 | license grant are also deemed granted under this license. 77 | 78 | This version of this YANG module is part of TR-451a1; see 79 | the TR itself for full legal notices."; 80 | 81 | revision 2025-02-03 { 82 | description 83 | "Amendment 1. 84 | * Approval Date: 2025-02-03. 85 | * Publication Date: 2025-02-03."; 86 | reference 87 | "TR-451a1: vOMCI Specification 88 | "; 90 | } 91 | 92 | augment "/bbf-onu-mgmt-p:onu-management-proxy" 93 | + "/bbf-onu-mgmt-p:remote-nf" 94 | + "/bbf-onu-mgmt-p:nf-client" 95 | + "/bbf-onu-mgmt-p:initiate" 96 | + "/bbf-onu-mgmt-p:remote-server" 97 | + "/bbf-onu-mgmt-p:transport" 98 | + "/bbf-onu-mgmt-p-grpcc:grpc" 99 | + "/bbf-onu-mgmt-p-grpcc:grpc-client" 100 | + "/bbf-onu-mgmt-p-grpcc:access-point" 101 | + "/bbf-onu-mgmt-p-grpcc:grpc-transport-parameters" 102 | + "/bbf-onu-mgmt-p-grpcc:tcp-client-options" { 103 | description 104 | "The gRPC connection parameters for TCP transport."; 105 | case tcp-transport { 106 | description 107 | "Select TCP transport."; 108 | container tcp-client-parameters { 109 | description 110 | "The TCP configuration."; 111 | uses tcpc:tcp-client-grouping; 112 | } 113 | } 114 | } 115 | } 116 | -------------------------------------------------------------------------------- /standard/application/bbf-onu-management-proxy-grpc-client.yang: -------------------------------------------------------------------------------- 1 | module bbf-onu-management-proxy-grpc-client { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-onu-management-proxy-grpc-client"; 4 | prefix bbf-onu-mgmt-p-grpcc; 5 | 6 | import bbf-grpc-client { 7 | prefix bbf-grpcc; 8 | } 9 | import bbf-onu-management-proxy { 10 | prefix bbf-onu-mgmt-p; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for ONU 30 | Management Proxy gRPC functionality as described in TR-451. 31 | 32 | Copyright (c) 2019-2022, Broadband Forum 33 | 34 | Redistribution and use in source and binary forms, with or 35 | without modification, are permitted provided that the following 36 | conditions are met: 37 | 38 | 1. Redistributions of source code must retain the above copyright 39 | notice, this list of conditions and the following disclaimer. 40 | 41 | 2. Redistributions in binary form must reproduce the above 42 | copyright notice, this list of conditions and the following 43 | disclaimer in the documentation and/or other materials 44 | provided with the distribution. 45 | 46 | 3. Neither the name of the copyright holder nor the names of its 47 | contributors may be used to endorse or promote products 48 | derived from this software without specific prior written 49 | permission. 50 | 51 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 52 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 53 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 54 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 55 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 56 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 57 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 58 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 59 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 60 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 61 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 62 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 63 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 64 | 65 | The above license is used as a license under copyright only. 66 | Please reference the Forum IPR Policy for patent licensing terms 67 | . 68 | 69 | Any moral rights which are necessary to exercise under the above 70 | license grant are also deemed granted under this license. 71 | 72 | This version of this YANG module is part of TR-451; see 73 | the TR itself for full legal notices."; 74 | 75 | revision 2022-06-07 { 76 | description 77 | "Issue 1. 78 | * Approval Date: 2022-06-07. 79 | * Publication Date: 2022-06-07."; 80 | reference 81 | "TR-451: vOMCI Specification 82 | "; 84 | } 85 | 86 | // gRPC client transport specific augment 87 | 88 | augment "/bbf-onu-mgmt-p:onu-management-proxy" 89 | + "/bbf-onu-mgmt-p:remote-nf" 90 | + "/bbf-onu-mgmt-p:nf-client" 91 | + "/bbf-onu-mgmt-p:initiate" 92 | + "/bbf-onu-mgmt-p:remote-server" 93 | + "/bbf-onu-mgmt-p:transport" { 94 | description 95 | "The gRPC client transport."; 96 | case grpc { 97 | description 98 | "Selection for gRPC client transport."; 99 | uses bbf-grpcc:grpc-client-transport; 100 | } 101 | } 102 | } 103 | -------------------------------------------------------------------------------- /standard/application/bbf-onu-management-proxy-grpc-server-tcp.yang: -------------------------------------------------------------------------------- 1 | module bbf-onu-management-proxy-grpc-server-tcp { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-onu-management-proxy-grpc-server-tcp"; 4 | prefix bbf-onu-mgmt-p-grpcs-tcp; 5 | 6 | import bbf-onu-management-proxy { 7 | prefix bbf-onu-mgmt-p; 8 | } 9 | import bbf-onu-management-proxy-grpc-server { 10 | prefix bbf-onu-mgmt-p-grpcs; 11 | } 12 | import ietf-tcp-server { 13 | prefix tcps; 14 | } 15 | 16 | organization 17 | "Broadband Forum 18 | SDN/NFV Work Area"; 19 | contact 20 | "Comments or questions about this Broadband Forum YANG module 21 | should be directed to . 22 | 23 | Editor: Andre Brizido, Altice Labs 24 | 25 | PS Leader: Ken Kerpez, DZS 26 | 27 | WA Director: Mengmeng Li, China Mobile 28 | 29 | WA Director: Bruno Cornaglia, Vodafone 30 | 31 | WA Director: Haomian Zheng, Huawei"; 32 | description 33 | "This module contains a collection of YANG definitions for 34 | supporting the Broadband Forum requirements for ONU 35 | Management Proxy gRPC functionality over TCP transport as 36 | described in TR-451. 37 | 38 | Copyright (c) 2019-2025, Broadband Forum 39 | 40 | Redistribution and use in source and binary forms, with or 41 | without modification, are permitted provided that the following 42 | conditions are met: 43 | 44 | 1. Redistributions of source code must retain the above copyright 45 | notice, this list of conditions and the following disclaimer. 46 | 47 | 2. Redistributions in binary form must reproduce the above 48 | copyright notice, this list of conditions and the following 49 | disclaimer in the documentation and/or other materials 50 | provided with the distribution. 51 | 52 | 3. Neither the name of the copyright holder nor the names of its 53 | contributors may be used to endorse or promote products 54 | derived from this software without specific prior written 55 | permission. 56 | 57 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 58 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 59 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 60 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 61 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 62 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 63 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 64 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 65 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 66 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 67 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 68 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 69 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 70 | 71 | The above license is used as a license under copyright only. 72 | Please reference the Forum IPR Policy for patent licensing terms 73 | . 74 | 75 | Any moral rights which are necessary to exercise under the above 76 | license grant are also deemed granted under this license. 77 | 78 | This version of this YANG module is part of TR-451a1; see 79 | the TR itself for full legal notices."; 80 | 81 | revision 2025-02-03 { 82 | description 83 | "Amendment 1. 84 | * Approval Date: 2025-02-03. 85 | * Publication Date: 2025-02-03."; 86 | reference 87 | "TR-451a1: vOMCI Specification 88 | "; 90 | } 91 | 92 | augment "/bbf-onu-mgmt-p:onu-management-proxy" 93 | + "/bbf-onu-mgmt-p:remote-nf" 94 | + "/bbf-onu-mgmt-p:nf-server" 95 | + "/bbf-onu-mgmt-p:listen" 96 | + "/bbf-onu-mgmt-p:listen-endpoint" 97 | + "/bbf-onu-mgmt-p:transport" 98 | + "/bbf-onu-mgmt-p-grpcs:grpc" 99 | + "/bbf-onu-mgmt-p-grpcs:grpc-server" 100 | + "/bbf-onu-mgmt-p-grpcs:tcp-client-options" { 101 | description 102 | "The gRPC server connection parameters for TCP transport."; 103 | case tcp-transport { 104 | description 105 | "Select TCP transport."; 106 | container tcp-server-parameters { 107 | description 108 | "The TCP configuration."; 109 | uses tcps:tcp-server-grouping; 110 | } 111 | } 112 | } 113 | } 114 | -------------------------------------------------------------------------------- /standard/application/bbf-onu-management-proxy-grpc-server.yang: -------------------------------------------------------------------------------- 1 | module bbf-onu-management-proxy-grpc-server { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-onu-management-proxy-grpc-server"; 4 | prefix bbf-onu-mgmt-p-grpcs; 5 | 6 | import bbf-grpc-server { 7 | prefix bbf-grpcs; 8 | } 9 | import bbf-onu-management-proxy { 10 | prefix bbf-onu-mgmt-p; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for ONU 30 | Management Proxy gRPC functionality as described in TR-451. 31 | 32 | Copyright (c) 2019-2022, Broadband Forum 33 | 34 | Redistribution and use in source and binary forms, with or 35 | without modification, are permitted provided that the following 36 | conditions are met: 37 | 38 | 1. Redistributions of source code must retain the above copyright 39 | notice, this list of conditions and the following disclaimer. 40 | 41 | 2. Redistributions in binary form must reproduce the above 42 | copyright notice, this list of conditions and the following 43 | disclaimer in the documentation and/or other materials 44 | provided with the distribution. 45 | 46 | 3. Neither the name of the copyright holder nor the names of its 47 | contributors may be used to endorse or promote products 48 | derived from this software without specific prior written 49 | permission. 50 | 51 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 52 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 53 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 54 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 55 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 56 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 57 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 58 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 59 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 60 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 61 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 62 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 63 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 64 | 65 | The above license is used as a license under copyright only. 66 | Please reference the Forum IPR Policy for patent licensing terms 67 | . 68 | 69 | Any moral rights which are necessary to exercise under the above 70 | license grant are also deemed granted under this license. 71 | 72 | This version of this YANG module is part of TR-451; see 73 | the TR itself for full legal notices."; 74 | 75 | revision 2022-06-07 { 76 | description 77 | "Issue 1. 78 | * Approval Date: 2022-06-07. 79 | * Publication Date: 2022-06-07."; 80 | reference 81 | "TR-451: vOMCI Specification 82 | "; 84 | } 85 | 86 | // gRPC server transport specific augment 87 | 88 | augment "/bbf-onu-mgmt-p:onu-management-proxy" 89 | + "/bbf-onu-mgmt-p:remote-nf" 90 | + "/bbf-onu-mgmt-p:nf-server" 91 | + "/bbf-onu-mgmt-p:listen" 92 | + "/bbf-onu-mgmt-p:listen-endpoint" 93 | + "/bbf-onu-mgmt-p:transport" { 94 | description 95 | "The gRPC server transport."; 96 | case grpc { 97 | description 98 | "Selection for gRPC server transport."; 99 | uses bbf-grpcs:grpc-server-transport; 100 | } 101 | } 102 | } 103 | -------------------------------------------------------------------------------- /standard/application/bbf-onu-management-proxy-kafka-agent-tcp.yang: -------------------------------------------------------------------------------- 1 | module bbf-onu-management-proxy-kafka-agent-tcp { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-onu-management-proxy-kafka-agent-tcp"; 4 | prefix bbf-onu-mgmt-p-ka-tcp; 5 | 6 | import bbf-onu-management-proxy { 7 | prefix bbf-onu-mgmt-p; 8 | } 9 | import bbf-onu-management-proxy-kafka-agent { 10 | prefix bbf-onu-mgmt-p-ka; 11 | } 12 | import ietf-tcp-client { 13 | prefix tcpc; 14 | } 15 | 16 | organization 17 | "Broadband Forum 18 | SDN/NFV Work Area"; 19 | contact 20 | "Comments or questions about this Broadband Forum YANG module 21 | should be directed to . 22 | 23 | Editor: Andre Brizido, Altice Labs 24 | 25 | PS Leader: Ken Kerpez, DZS 26 | 27 | WA Director: Mengmeng Li, China Mobile 28 | 29 | WA Director: Bruno Cornaglia, Vodafone 30 | 31 | WA Director: Haomian Zheng, Huawei"; 32 | description 33 | "This module contains a collection of YANG definitions for 34 | supporting the Broadband Forum requirements for ONU 35 | Management Proxy Kafka transport over TCP functionality as 36 | described in TR-451. 37 | 38 | Copyright (c) 2019-2025, Broadband Forum 39 | 40 | Redistribution and use in source and binary forms, with or 41 | without modification, are permitted provided that the following 42 | conditions are met: 43 | 44 | 1. Redistributions of source code must retain the above copyright 45 | notice, this list of conditions and the following disclaimer. 46 | 47 | 2. Redistributions in binary form must reproduce the above 48 | copyright notice, this list of conditions and the following 49 | disclaimer in the documentation and/or other materials 50 | provided with the distribution. 51 | 52 | 3. Neither the name of the copyright holder nor the names of its 53 | contributors may be used to endorse or promote products 54 | derived from this software without specific prior written 55 | permission. 56 | 57 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 58 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 59 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 60 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 61 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 62 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 63 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 64 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 65 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 66 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 67 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 68 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 69 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 70 | 71 | The above license is used as a license under copyright only. 72 | Please reference the Forum IPR Policy for patent licensing terms 73 | . 74 | 75 | Any moral rights which are necessary to exercise under the above 76 | license grant are also deemed granted under this license. 77 | 78 | This version of this YANG module is part of TR-451a1; see 79 | the TR itself for full legal notices."; 80 | 81 | revision 2025-02-03 { 82 | description 83 | "Amendment 1. 84 | * Approval Date: 2025-02-03. 85 | * Publication Date: 2025-02-03."; 86 | reference 87 | "TR-451a1: vOMCI Specification 88 | "; 90 | } 91 | 92 | augment "/bbf-onu-mgmt-p:onu-management-proxy" 93 | + "/bbf-onu-mgmt-p:remote-nf" 94 | + "/bbf-onu-mgmt-p:nf-client" 95 | + "/bbf-onu-mgmt-p:initiate" 96 | + "/bbf-onu-mgmt-p:remote-server" 97 | + "/bbf-onu-mgmt-p:transport" 98 | + "/bbf-onu-mgmt-p-ka:kafka" 99 | + "/bbf-onu-mgmt-p-ka:kafka-agent" 100 | + "/bbf-onu-mgmt-p-ka:access-point" 101 | + "/bbf-onu-mgmt-p-ka:kafka-agent-transport-parameters" 102 | + "/bbf-onu-mgmt-p-ka:tcp-client-options" { 103 | description 104 | "The Kafka connection parameters for TCP transport."; 105 | case tcp-transport { 106 | description 107 | "Selection for TCP transport."; 108 | container tcp-client-parameters { 109 | description 110 | "The TCP configuration."; 111 | uses tcpc:tcp-client-grouping; 112 | } 113 | } 114 | } 115 | } 116 | -------------------------------------------------------------------------------- /standard/application/bbf-onu-management-proxy-kafka-agent.yang: -------------------------------------------------------------------------------- 1 | module bbf-onu-management-proxy-kafka-agent { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-onu-management-proxy-kafka-agent"; 4 | prefix bbf-onu-mgmt-p-ka; 5 | 6 | import bbf-kafka-agent { 7 | prefix bbf-kafkaa; 8 | } 9 | import bbf-onu-management-proxy { 10 | prefix bbf-onu-mgmt-p; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for ONU 30 | Management Proxy Kafka functionality as described in TR-451. 31 | 32 | This module contains a collection of YANG definitions needed 33 | to use the Kafka agent as a transport protocol. 34 | 35 | Copyright (c) 2019-2022, Broadband Forum 36 | 37 | Redistribution and use in source and binary forms, with or 38 | without modification, are permitted provided that the following 39 | conditions are met: 40 | 41 | 1. Redistributions of source code must retain the above copyright 42 | notice, this list of conditions and the following disclaimer. 43 | 44 | 2. Redistributions in binary form must reproduce the above 45 | copyright notice, this list of conditions and the following 46 | disclaimer in the documentation and/or other materials 47 | provided with the distribution. 48 | 49 | 3. Neither the name of the copyright holder nor the names of its 50 | contributors may be used to endorse or promote products 51 | derived from this software without specific prior written 52 | permission. 53 | 54 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 55 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 56 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 57 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 58 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 59 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 60 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 61 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 62 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 63 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 64 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 65 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 66 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 67 | 68 | The above license is used as a license under copyright only. 69 | Please reference the Forum IPR Policy for patent licensing terms 70 | . 71 | 72 | Any moral rights which are necessary to exercise under the above 73 | license grant are also deemed granted under this license. 74 | 75 | This version of this YANG module is part of TR-451; see 76 | the TR itself for full legal notices."; 77 | 78 | revision 2022-06-07 { 79 | description 80 | "Issue 1. 81 | * Approval Date: 2022-06-07. 82 | * Publication Date: 2022-06-07."; 83 | reference 84 | "TR-451: vOMCI Specification 85 | "; 87 | } 88 | 89 | // Kafka Agent transport specific augment 90 | 91 | augment "/bbf-onu-mgmt-p:onu-management-proxy" 92 | + "/bbf-onu-mgmt-p:remote-nf" 93 | + "/bbf-onu-mgmt-p:nf-client" 94 | + "/bbf-onu-mgmt-p:initiate" 95 | + "/bbf-onu-mgmt-p:remote-server" 96 | + "/bbf-onu-mgmt-p:transport" { 97 | description 98 | "The Kafka client transport."; 99 | case kafka { 100 | description 101 | "Selection for Kafka client transport."; 102 | uses bbf-kafkaa:kafka-agent-transport; 103 | } 104 | } 105 | } 106 | -------------------------------------------------------------------------------- /standard/application/bbf-onu-management-proxy-state.yang: -------------------------------------------------------------------------------- 1 | module bbf-onu-management-proxy-state { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-onu-management-proxy-state"; 4 | prefix bbf-onu-mgmt-p-s; 5 | 6 | import bbf-voltmf-common { 7 | prefix bbf-voltmf-c; 8 | } 9 | 10 | organization 11 | "Broadband Forum 12 | SDN/NFV Work Area"; 13 | contact 14 | "Comments or questions about this Broadband Forum YANG module 15 | should be directed to . 16 | 17 | Editor: Tim Carey, Nokia 18 | 19 | Editor: Jeff Hartley, Commscope 20 | 21 | WA Director: Mengmeng Li, China Mobile 22 | 23 | WA Director: Bruno Cornaglia, Vodafone"; 24 | description 25 | "This module contains a collection of YANG definitions for 26 | supporting the Broadband Forum requirements for ONU 27 | Management Proxy state functionality as described in TR-451. 28 | 29 | This module is to be used along with 'bbf-onu-management-proxy' 30 | when the server does not support Network Management Datastore 31 | Architecture (NMDA) as defined in RFC 8342. 32 | 33 | Copyright (c) 2019-2022, Broadband Forum 34 | 35 | Redistribution and use in source and binary forms, with or 36 | without modification, are permitted provided that the following 37 | conditions are met: 38 | 39 | 1. Redistributions of source code must retain the above copyright 40 | notice, this list of conditions and the following disclaimer. 41 | 42 | 2. Redistributions in binary form must reproduce the above 43 | copyright notice, this list of conditions and the following 44 | disclaimer in the documentation and/or other materials 45 | provided with the distribution. 46 | 47 | 3. Neither the name of the copyright holder nor the names of its 48 | contributors may be used to endorse or promote products 49 | derived from this software without specific prior written 50 | permission. 51 | 52 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 53 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 54 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 55 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 56 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 57 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 58 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 59 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 60 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 61 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 62 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 63 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 64 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 65 | 66 | The above license is used as a license under copyright only. 67 | Please reference the Forum IPR Policy for patent licensing terms 68 | . 69 | 70 | Any moral rights which are necessary to exercise under the above 71 | license grant are also deemed granted under this license. 72 | 73 | This version of this YANG module is part of TR-451; see 74 | the TR itself for full legal notices."; 75 | 76 | revision 2022-06-07 { 77 | description 78 | "Issue 1. 79 | * Approval Date: 2022-06-07. 80 | * Publication Date: 2022-06-07."; 81 | reference 82 | "TR-451: vOMCI Specification 83 | "; 85 | } 86 | 87 | container onu-management-proxy { 88 | config false; 89 | description 90 | "State data associated with the ONU Management Proxy required 91 | to distinguish between instances of nodes in the running 92 | configuration and operational states when the server does not 93 | support NMDA."; 94 | container nf-topology { 95 | description 96 | "The VNFs, VNF instances and network function links known to 97 | this entity that depicts: 98 | VNFs: vOMCI Function, vOMCI Proxy, ONU Management Proxy 99 | VNF Instances and links of Network Functions: 100 | vOMCI Function, vOMCI Proxy, ONU Management Proxy."; 101 | uses bbf-voltmf-c:discovered-nf-topology; 102 | } 103 | } 104 | } 105 | -------------------------------------------------------------------------------- /standard/application/bbf-voltmf-grpc-client-tcp.yang: -------------------------------------------------------------------------------- 1 | module bbf-voltmf-grpc-client-tcp { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-voltmf-grpc-client-tcp"; 4 | prefix bbf-voltmf-grpcc-tcp; 5 | 6 | import bbf-voltmf { 7 | prefix bbf-voltmf; 8 | } 9 | import bbf-voltmf-grpc-client { 10 | prefix bbf-voltmf-grpcc; 11 | } 12 | import ietf-tcp-client { 13 | prefix tcpc; 14 | } 15 | 16 | organization 17 | "Broadband Forum 18 | SDN/NFV Work Area"; 19 | contact 20 | "Comments or questions about this Broadband Forum YANG module 21 | should be directed to . 22 | 23 | Editor: Andre Brizido, Altice Labs 24 | 25 | PS Leader: Ken Kerpez, DZS 26 | 27 | WA Director: Mengmeng Li, China Mobile 28 | 29 | WA Director: Bruno Cornaglia, Vodafone 30 | 31 | WA Director: Haomian Zheng, Huawei"; 32 | description 33 | "This module contains a collection of YANG definitions for 34 | supporting the Broadband Forum requirements for gRPC client 35 | vOLTMF functionality over TCP transport as described in TR-451. 36 | 37 | Copyright (c) 2019-2025, Broadband Forum 38 | 39 | Redistribution and use in source and binary forms, with or 40 | without modification, are permitted provided that the following 41 | conditions are met: 42 | 43 | 1. Redistributions of source code must retain the above copyright 44 | notice, this list of conditions and the following disclaimer. 45 | 46 | 2. Redistributions in binary form must reproduce the above 47 | copyright notice, this list of conditions and the following 48 | disclaimer in the documentation and/or other materials 49 | provided with the distribution. 50 | 51 | 3. Neither the name of the copyright holder nor the names of its 52 | contributors may be used to endorse or promote products 53 | derived from this software without specific prior written 54 | permission. 55 | 56 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 57 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 58 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 59 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 60 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 61 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 62 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 63 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 64 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 65 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 66 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 67 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 68 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 69 | 70 | The above license is used as a license under copyright only. 71 | Please reference the Forum IPR Policy for patent licensing terms 72 | . 73 | 74 | Any moral rights which are necessary to exercise under the above 75 | license grant are also deemed granted under this license. 76 | 77 | This version of this YANG module is part of TR-451a1; see 78 | the TR itself for full legal notices."; 79 | 80 | revision 2025-02-03 { 81 | description 82 | "Amendment 1. 83 | * Approval Date: 2025-02-03. 84 | * Publication Date: 2025-02-03."; 85 | reference 86 | "TR-451a1: vOMCI Specification 87 | "; 89 | } 90 | 91 | augment "/bbf-voltmf:voltmf" 92 | + "/bbf-voltmf:remote-nf" 93 | + "/bbf-voltmf:nf-client" 94 | + "/bbf-voltmf:initiate" 95 | + "/bbf-voltmf:remote-server" 96 | + "/bbf-voltmf:transport" 97 | + "/bbf-voltmf-grpcc:grpc" 98 | + "/bbf-voltmf-grpcc:grpc-client" 99 | + "/bbf-voltmf-grpcc:access-point" 100 | + "/bbf-voltmf-grpcc:grpc-transport-parameters" 101 | + "/bbf-voltmf-grpcc:tcp-client-options" { 102 | description 103 | "The gRPC connection parameters for TCP transport."; 104 | case tcp-transport { 105 | description 106 | "Select TCP transport."; 107 | container tcp-client-parameters { 108 | description 109 | "The TCP configuration."; 110 | uses tcpc:tcp-client-grouping; 111 | } 112 | } 113 | } 114 | } 115 | -------------------------------------------------------------------------------- /standard/application/bbf-voltmf-grpc-client.yang: -------------------------------------------------------------------------------- 1 | module bbf-voltmf-grpc-client { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-voltmf-grpc-client"; 4 | prefix bbf-voltmf-grpcc; 5 | 6 | import bbf-grpc-client { 7 | prefix bbf-grpcc; 8 | } 9 | import bbf-voltmf { 10 | prefix bbf-voltmf; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for gRPC client 30 | vOLTMF functionality as described in TR-451. 31 | 32 | Copyright (c) 2019-2022, Broadband Forum 33 | 34 | Redistribution and use in source and binary forms, with or 35 | without modification, are permitted provided that the following 36 | conditions are met: 37 | 38 | 1. Redistributions of source code must retain the above copyright 39 | notice, this list of conditions and the following disclaimer. 40 | 41 | 2. Redistributions in binary form must reproduce the above 42 | copyright notice, this list of conditions and the following 43 | disclaimer in the documentation and/or other materials 44 | provided with the distribution. 45 | 46 | 3. Neither the name of the copyright holder nor the names of its 47 | contributors may be used to endorse or promote products 48 | derived from this software without specific prior written 49 | permission. 50 | 51 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 52 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 53 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 54 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 55 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 56 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 57 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 58 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 59 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 60 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 61 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 62 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 63 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 64 | 65 | The above license is used as a license under copyright only. 66 | Please reference the Forum IPR Policy for patent licensing terms 67 | . 68 | 69 | Any moral rights which are necessary to exercise under the above 70 | license grant are also deemed granted under this license. 71 | 72 | This version of this YANG module is part of TR-451; see 73 | the TR itself for full legal notices."; 74 | 75 | revision 2022-06-07 { 76 | description 77 | "Issue 1. 78 | * Approval Date: 2022-06-07. 79 | * Publication Date: 2022-06-07."; 80 | reference 81 | "TR-451: vOMCI Specification 82 | "; 84 | } 85 | 86 | // gRPC client transport specific augment 87 | 88 | augment "/bbf-voltmf:voltmf" 89 | + "/bbf-voltmf:remote-nf" 90 | + "/bbf-voltmf:nf-client" 91 | + "/bbf-voltmf:initiate" 92 | + "/bbf-voltmf:remote-server" 93 | + "/bbf-voltmf:transport" { 94 | description 95 | "The gRPC client transport."; 96 | case grpc { 97 | description 98 | "Selection for gRPC client transport."; 99 | uses bbf-grpcc:grpc-client-transport; 100 | } 101 | } 102 | } 103 | -------------------------------------------------------------------------------- /standard/application/bbf-voltmf-kafka-agent-tcp.yang: -------------------------------------------------------------------------------- 1 | module bbf-voltmf-kafka-agent-tcp { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-voltmf-kafka-agent-tcp"; 4 | prefix bbf-voltmf-ka-tcp; 5 | 6 | import bbf-voltmf { 7 | prefix bbf-voltmf; 8 | } 9 | import bbf-voltmf-kafka-agent { 10 | prefix bbf-voltmf-ka; 11 | } 12 | import ietf-tcp-client { 13 | prefix tcpc; 14 | } 15 | 16 | organization 17 | "Broadband Forum 18 | SDN/NFV Work Area"; 19 | contact 20 | "Comments or questions about this Broadband Forum YANG module 21 | should be directed to . 22 | 23 | Editor: Andre Brizido, Altice Labs 24 | 25 | PS Leader: Ken Kerpez, DZS 26 | 27 | WA Director: Mengmeng Li, China Mobile 28 | 29 | WA Director: Bruno Cornaglia, Vodafone 30 | 31 | WA Director: Haomian Zheng, Huawei"; 32 | description 33 | "This module contains a collection of YANG definitions for 34 | supporting the Broadband Forum requirements for vOLTMF Kafka 35 | transport over TCP functionality as described in TR-451. 36 | 37 | Copyright (c) 2019-2025, Broadband Forum 38 | 39 | Redistribution and use in source and binary forms, with or 40 | without modification, are permitted provided that the following 41 | conditions are met: 42 | 43 | 1. Redistributions of source code must retain the above copyright 44 | notice, this list of conditions and the following disclaimer. 45 | 46 | 2. Redistributions in binary form must reproduce the above 47 | copyright notice, this list of conditions and the following 48 | disclaimer in the documentation and/or other materials 49 | provided with the distribution. 50 | 51 | 3. Neither the name of the copyright holder nor the names of its 52 | contributors may be used to endorse or promote products 53 | derived from this software without specific prior written 54 | permission. 55 | 56 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 57 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 58 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 59 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 60 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 61 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 62 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 63 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 64 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 65 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 66 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 67 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 68 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 69 | 70 | The above license is used as a license under copyright only. 71 | Please reference the Forum IPR Policy for patent licensing terms 72 | . 73 | 74 | Any moral rights which are necessary to exercise under the above 75 | license grant are also deemed granted under this license. 76 | 77 | This version of this YANG module is part of TR-451a1; see 78 | the TR itself for full legal notices."; 79 | 80 | revision 2025-02-03 { 81 | description 82 | "Amendment 1. 83 | * Approval Date: 2025-02-03. 84 | * Publication Date: 2025-02-03."; 85 | reference 86 | "TR-451a1: vOMCI Specification 87 | "; 89 | } 90 | 91 | augment "/bbf-voltmf:voltmf" 92 | + "/bbf-voltmf:remote-nf" 93 | + "/bbf-voltmf:nf-client" 94 | + "/bbf-voltmf:initiate" 95 | + "/bbf-voltmf:remote-server" 96 | + "/bbf-voltmf:transport" 97 | + "/bbf-voltmf-ka:kafka" 98 | + "/bbf-voltmf-ka:kafka-agent" 99 | + "/bbf-voltmf-ka:access-point" 100 | + "/bbf-voltmf-ka:kafka-agent-transport-parameters" 101 | + "/bbf-voltmf-ka:tcp-client-options" { 102 | description 103 | "The Kafka connection parameters for TCP transport."; 104 | case tcp-transport { 105 | description 106 | "Selection for TCP transport."; 107 | container tcp-client-parameters { 108 | description 109 | "The TCP configuration."; 110 | uses tcpc:tcp-client-grouping; 111 | } 112 | } 113 | } 114 | } 115 | -------------------------------------------------------------------------------- /standard/application/bbf-voltmf-kafka-agent-tls.yang: -------------------------------------------------------------------------------- 1 | module bbf-voltmf-kafka-agent-tls { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-voltmf-kafka-agent-tls"; 4 | prefix bbf-voltmf-ka-tls; 5 | 6 | import bbf-voltmf { 7 | prefix bbf-voltmf; 8 | } 9 | import bbf-voltmf-kafka-agent { 10 | prefix bbf-voltmf-ka; 11 | } 12 | import ietf-tcp-client { 13 | prefix tcpc; 14 | } 15 | import ietf-tls-client { 16 | prefix tlsc; 17 | } 18 | 19 | organization 20 | "Broadband Forum 21 | SDN/NFV Work Area"; 22 | contact 23 | "Comments or questions about this Broadband Forum YANG module 24 | should be directed to . 25 | 26 | Editor: Andre Brizido, Altice Labs 27 | 28 | PS Leader: Ken Kerpez, DZS 29 | 30 | WA Director: Mengmeng Li, China Mobile 31 | 32 | WA Director: Bruno Cornaglia, Vodafone 33 | 34 | WA Director: Haomian Zheng, Huawei"; 35 | description 36 | "This module contains a collection of YANG definitions for 37 | supporting the Broadband Forum requirements for vOLTMF Kafka 38 | transport over TLS functionality as described in TR-451. 39 | 40 | Copyright (c) 2019-2025, Broadband Forum 41 | 42 | Redistribution and use in source and binary forms, with or 43 | without modification, are permitted provided that the following 44 | conditions are met: 45 | 46 | 1. Redistributions of source code must retain the above copyright 47 | notice, this list of conditions and the following disclaimer. 48 | 49 | 2. Redistributions in binary form must reproduce the above 50 | copyright notice, this list of conditions and the following 51 | disclaimer in the documentation and/or other materials 52 | provided with the distribution. 53 | 54 | 3. Neither the name of the copyright holder nor the names of its 55 | contributors may be used to endorse or promote products 56 | derived from this software without specific prior written 57 | permission. 58 | 59 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 60 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 61 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 62 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 63 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 64 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 65 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 66 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 67 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 68 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 69 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 70 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 71 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 72 | 73 | The above license is used as a license under copyright only. 74 | Please reference the Forum IPR Policy for patent licensing terms 75 | . 76 | 77 | Any moral rights which are necessary to exercise under the above 78 | license grant are also deemed granted under this license. 79 | 80 | This version of this YANG module is part of TR-451a1; see 81 | the TR itself for full legal notices."; 82 | 83 | revision 2025-02-03 { 84 | description 85 | "Amendment 1. 86 | * Approval Date: 2025-02-03. 87 | * Publication Date: 2025-02-03."; 88 | reference 89 | "TR-451a1: vOMCI Specification 90 | "; 92 | } 93 | 94 | augment "/bbf-voltmf:voltmf" 95 | + "/bbf-voltmf:remote-nf" 96 | + "/bbf-voltmf:nf-client" 97 | + "/bbf-voltmf:initiate" 98 | + "/bbf-voltmf:remote-server" 99 | + "/bbf-voltmf:transport" 100 | + "/bbf-voltmf-ka:kafka" 101 | + "/bbf-voltmf-ka:kafka-agent" 102 | + "/bbf-voltmf-ka:access-point" 103 | + "/bbf-voltmf-ka:kafka-agent-transport-parameters" 104 | + "/bbf-voltmf-ka:tcp-client-options" { 105 | description 106 | "The Kafka connection parameters for TLS transport."; 107 | case tls-transport { 108 | description 109 | "Selection for TLS transport."; 110 | container tcp-client-parameters { 111 | description 112 | "The TCP configuration."; 113 | uses tcpc:tcp-client-grouping; 114 | } 115 | container tls-client-parameters { 116 | description 117 | "The TLS configuration."; 118 | uses tlsc:tls-client-grouping; 119 | } 120 | } 121 | } 122 | } 123 | -------------------------------------------------------------------------------- /standard/application/bbf-voltmf-kafka-agent.yang: -------------------------------------------------------------------------------- 1 | module bbf-voltmf-kafka-agent { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-voltmf-kafka-agent"; 4 | prefix bbf-voltmf-ka; 5 | 6 | import bbf-kafka-agent { 7 | prefix bbf-kafkaa; 8 | } 9 | import bbf-voltmf { 10 | prefix bbf-voltmf; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for vOLTMF kafka 30 | transport functionality as described in TR-451. 31 | 32 | Copyright (c) 2019-2022, Broadband Forum 33 | 34 | Redistribution and use in source and binary forms, with or 35 | without modification, are permitted provided that the following 36 | conditions are met: 37 | 38 | 1. Redistributions of source code must retain the above copyright 39 | notice, this list of conditions and the following disclaimer. 40 | 41 | 2. Redistributions in binary form must reproduce the above 42 | copyright notice, this list of conditions and the following 43 | disclaimer in the documentation and/or other materials 44 | provided with the distribution. 45 | 46 | 3. Neither the name of the copyright holder nor the names of its 47 | contributors may be used to endorse or promote products 48 | derived from this software without specific prior written 49 | permission. 50 | 51 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 52 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 53 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 54 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 55 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 56 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 57 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 58 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 59 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 60 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 61 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 62 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 63 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 64 | 65 | The above license is used as a license under copyright only. 66 | Please reference the Forum IPR Policy for patent licensing terms 67 | . 68 | 69 | Any moral rights which are necessary to exercise under the above 70 | license grant are also deemed granted under this license. 71 | 72 | This version of this YANG module is part of TR-451; see 73 | the TR itself for full legal notices."; 74 | 75 | revision 2022-06-07 { 76 | description 77 | "Issue 1. 78 | * Approval Date: 2022-06-07. 79 | * Publication Date: 2022-06-07."; 80 | reference 81 | "TR-451: vOMCI Specification 82 | "; 84 | } 85 | 86 | // Kafka Agent transport specific augment 87 | 88 | augment "/bbf-voltmf:voltmf" 89 | + "/bbf-voltmf:remote-nf" 90 | + "/bbf-voltmf:nf-client" 91 | + "/bbf-voltmf:initiate" 92 | + "/bbf-voltmf:remote-server" 93 | + "/bbf-voltmf:transport" { 94 | description 95 | "The Kafka client transport."; 96 | case kafka { 97 | description 98 | "Selection for Kafka client transport."; 99 | uses bbf-kafkaa:kafka-agent-transport; 100 | } 101 | } 102 | } 103 | -------------------------------------------------------------------------------- /standard/application/bbf-vomci-function-grpc-client.yang: -------------------------------------------------------------------------------- 1 | module bbf-vomci-function-grpc-client { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-vomci-function-grpc-client"; 4 | prefix bbf-vomci-func-grpcc; 5 | 6 | import bbf-grpc-client { 7 | prefix bbf-grpcc; 8 | } 9 | import bbf-vomci-function { 10 | prefix bbf-vomci-func; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for vOMCI gRPC 30 | client functionality as described in TR-451. 31 | 32 | Copyright (c) 2019-2022, Broadband Forum 33 | 34 | Redistribution and use in source and binary forms, with or 35 | without modification, are permitted provided that the following 36 | conditions are met: 37 | 38 | 1. Redistributions of source code must retain the above copyright 39 | notice, this list of conditions and the following disclaimer. 40 | 41 | 2. Redistributions in binary form must reproduce the above 42 | copyright notice, this list of conditions and the following 43 | disclaimer in the documentation and/or other materials 44 | provided with the distribution. 45 | 46 | 3. Neither the name of the copyright holder nor the names of its 47 | contributors may be used to endorse or promote products 48 | derived from this software without specific prior written 49 | permission. 50 | 51 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 52 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 53 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 54 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 55 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 56 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 57 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 58 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 59 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 60 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 61 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 62 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 63 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 64 | 65 | The above license is used as a license under copyright only. 66 | Please reference the Forum IPR Policy for patent licensing terms 67 | . 68 | 69 | Any moral rights which are necessary to exercise under the above 70 | license grant are also deemed granted under this license. 71 | 72 | This version of this YANG module is part of TR-451; see 73 | the TR itself for full legal notices."; 74 | 75 | revision 2022-06-07 { 76 | description 77 | "Issue 1. 78 | * Approval Date: 2022-06-07. 79 | * Publication Date: 2022-06-07."; 80 | reference 81 | "TR-451: vOMCI Specification 82 | "; 84 | } 85 | 86 | // gRPC client transport specific augment 87 | 88 | augment "/bbf-vomci-func:vomci" 89 | + "/bbf-vomci-func:remote-nf" 90 | + "/bbf-vomci-func:nf-client" 91 | + "/bbf-vomci-func:initiate" 92 | + "/bbf-vomci-func:remote-server" 93 | + "/bbf-vomci-func:transport" { 94 | description 95 | "The gRPC client transport."; 96 | case grpc { 97 | description 98 | "Selection for gRPC client transport."; 99 | uses bbf-grpcc:grpc-client-transport; 100 | } 101 | } 102 | } 103 | -------------------------------------------------------------------------------- /standard/application/bbf-vomci-function-grpc-server-tcp.yang: -------------------------------------------------------------------------------- 1 | module bbf-vomci-function-grpc-server-tcp { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-vomci-function-grpc-server-tcp"; 4 | prefix bbf-vomci-func-grpcs-tcp; 5 | 6 | import bbf-vomci-function { 7 | prefix bbf-vomci-func; 8 | } 9 | import bbf-vomci-function-grpc-server { 10 | prefix bbf-vomci-func-grpcs; 11 | } 12 | import ietf-tcp-server { 13 | prefix tcps; 14 | } 15 | import bbf-vomci-grpc-common { 16 | prefix bbf-vomci-grpc-c; 17 | } 18 | 19 | organization 20 | "Broadband Forum 21 | SDN/NFV Work Area"; 22 | contact 23 | "Comments or questions about this Broadband Forum YANG module 24 | should be directed to . 25 | 26 | Editor: Andre Brizido, Altice Labs 27 | 28 | PS Leader: Ken Kerpez, DZS 29 | 30 | WA Director: Mengmeng Li, China Mobile 31 | 32 | WA Director: Bruno Cornaglia, Vodafone 33 | 34 | WA Director: Haomian Zheng, Huawei"; 35 | description 36 | "This module contains a collection of YANG definitions for 37 | supporting the Broadband Forum requirements for vOMCI gRPC 38 | server functionality over TCP transport as described in TR-451. 39 | 40 | Copyright (c) 2019-2025, Broadband Forum 41 | 42 | Redistribution and use in source and binary forms, with or 43 | without modification, are permitted provided that the following 44 | conditions are met: 45 | 46 | 1. Redistributions of source code must retain the above copyright 47 | notice, this list of conditions and the following disclaimer. 48 | 49 | 2. Redistributions in binary form must reproduce the above 50 | copyright notice, this list of conditions and the following 51 | disclaimer in the documentation and/or other materials 52 | provided with the distribution. 53 | 54 | 3. Neither the name of the copyright holder nor the names of its 55 | contributors may be used to endorse or promote products 56 | derived from this software without specific prior written 57 | permission. 58 | 59 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 60 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 61 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 62 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 63 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 64 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 65 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 66 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 67 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 68 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 69 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 70 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 71 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 72 | 73 | The above license is used as a license under copyright only. 74 | Please reference the Forum IPR Policy for patent licensing terms 75 | . 76 | 77 | Any moral rights which are necessary to exercise under the above 78 | license grant are also deemed granted under this license. 79 | 80 | This version of this YANG module is part of TR-451a1; see 81 | the TR itself for full legal notices."; 82 | 83 | revision 2025-02-03 { 84 | description 85 | "Amendment 1. 86 | * Approval Date: 2025-02-03. 87 | * Publication Date: 2025-02-03."; 88 | reference 89 | "TR-451a1: vOMCI Specification 90 | "; 92 | } 93 | 94 | augment "/bbf-vomci-func:vomci" 95 | + "/bbf-vomci-func:remote-nf" 96 | + "/bbf-vomci-func:nf-server" 97 | + "/bbf-vomci-func:listen" 98 | + "/bbf-vomci-func:listen-endpoint" 99 | + "/bbf-vomci-func:transport" 100 | + "/bbf-vomci-func-grpcs:grpc" 101 | + "/bbf-vomci-func-grpcs:grpc-server" 102 | + "/bbf-vomci-func-grpcs:tcp-client-options" { 103 | description 104 | "The gRPC server connection parameters for TCP transport."; 105 | case tcp-transport { 106 | description 107 | "Select TCP transport."; 108 | container tcp-server-parameters { 109 | description 110 | "The TCP configuration."; 111 | uses tcps:tcp-server-grouping; 112 | uses bbf-vomci-grpc-c:server-authentication; 113 | } 114 | } 115 | } 116 | } 117 | -------------------------------------------------------------------------------- /standard/application/bbf-vomci-function-grpc-server.yang: -------------------------------------------------------------------------------- 1 | module bbf-vomci-function-grpc-server { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-vomci-function-grpc-server"; 4 | prefix bbf-vomci-func-grpcs; 5 | 6 | import bbf-grpc-server { 7 | prefix bbf-grpcs; 8 | } 9 | import bbf-vomci-function { 10 | prefix bbf-vomci-func; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for vOMCI gRPC 30 | server functionality as described in TR-451. 31 | 32 | Copyright (c) 2019-2022, Broadband Forum 33 | 34 | Redistribution and use in source and binary forms, with or 35 | without modification, are permitted provided that the following 36 | conditions are met: 37 | 38 | 1. Redistributions of source code must retain the above copyright 39 | notice, this list of conditions and the following disclaimer. 40 | 41 | 2. Redistributions in binary form must reproduce the above 42 | copyright notice, this list of conditions and the following 43 | disclaimer in the documentation and/or other materials 44 | provided with the distribution. 45 | 46 | 3. Neither the name of the copyright holder nor the names of its 47 | contributors may be used to endorse or promote products 48 | derived from this software without specific prior written 49 | permission. 50 | 51 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 52 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 53 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 54 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 55 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 56 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 57 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 58 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 59 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 60 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 61 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 62 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 63 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 64 | 65 | The above license is used as a license under copyright only. 66 | Please reference the Forum IPR Policy for patent licensing terms 67 | . 68 | 69 | Any moral rights which are necessary to exercise under the above 70 | license grant are also deemed granted under this license. 71 | 72 | This version of this YANG module is part of TR-451; see 73 | the TR itself for full legal notices."; 74 | 75 | revision 2022-06-07 { 76 | description 77 | "Issue 1. 78 | * Approval Date: 2022-06-07. 79 | * Publication Date: 2022-06-07."; 80 | reference 81 | "TR-451: vOMCI Specification 82 | "; 84 | } 85 | 86 | // gRPC server transport specific augment 87 | 88 | augment "/bbf-vomci-func:vomci" 89 | + "/bbf-vomci-func:remote-nf" 90 | + "/bbf-vomci-func:nf-server" 91 | + "/bbf-vomci-func:listen" 92 | + "/bbf-vomci-func:listen-endpoint" 93 | + "/bbf-vomci-func:transport" { 94 | description 95 | "The gRPC server transport."; 96 | case grpc { 97 | description 98 | "Selection for gRPC server transport."; 99 | uses bbf-grpcs:grpc-server-transport; 100 | } 101 | } 102 | } 103 | -------------------------------------------------------------------------------- /standard/application/bbf-vomci-function-kafka-agent-tcp.yang: -------------------------------------------------------------------------------- 1 | module bbf-vomci-function-kafka-agent-tcp { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-vomci-function-kafka-agent-tcp"; 4 | prefix bbf-vomci-func-ka-tcp; 5 | 6 | import bbf-vomci-function { 7 | prefix bbf-vomci-func; 8 | } 9 | import bbf-vomci-function-kafka-agent { 10 | prefix bbf-vomci-func-ka; 11 | } 12 | import ietf-tcp-client { 13 | prefix tcpc; 14 | } 15 | 16 | organization 17 | "Broadband Forum 18 | SDN/NFV Work Area"; 19 | contact 20 | "Comments or questions about this Broadband Forum YANG module 21 | should be directed to . 22 | 23 | Editor: Andre Brizido, Altice Labs 24 | 25 | PS Leader: Ken Kerpez, DZS 26 | 27 | WA Director: Mengmeng Li, China Mobile 28 | 29 | WA Director: Bruno Cornaglia, Vodafone 30 | 31 | WA Director: Haomian Zheng, Huawei"; 32 | description 33 | "This module contains a collection of YANG definitions for 34 | supporting the Broadband Forum requirements for vOMCI Kafka 35 | transport over TCP functionality as described in TR-451. 36 | 37 | Copyright (c) 2019-2025, Broadband Forum 38 | 39 | Redistribution and use in source and binary forms, with or 40 | without modification, are permitted provided that the following 41 | conditions are met: 42 | 43 | 1. Redistributions of source code must retain the above copyright 44 | notice, this list of conditions and the following disclaimer. 45 | 46 | 2. Redistributions in binary form must reproduce the above 47 | copyright notice, this list of conditions and the following 48 | disclaimer in the documentation and/or other materials 49 | provided with the distribution. 50 | 51 | 3. Neither the name of the copyright holder nor the names of its 52 | contributors may be used to endorse or promote products 53 | derived from this software without specific prior written 54 | permission. 55 | 56 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 57 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 58 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 59 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 60 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 61 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 62 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 63 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 64 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 65 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 66 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 67 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 68 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 69 | 70 | The above license is used as a license under copyright only. 71 | Please reference the Forum IPR Policy for patent licensing terms 72 | . 73 | 74 | Any moral rights which are necessary to exercise under the above 75 | license grant are also deemed granted under this license. 76 | 77 | This version of this YANG module is part of TR-451a1; see 78 | the TR itself for full legal notices."; 79 | 80 | revision 2025-02-03 { 81 | description 82 | "Amendment 1. 83 | * Approval Date: 2025-02-03. 84 | * Publication Date: 2025-02-03."; 85 | reference 86 | "TR-451a1: vOMCI Specification 87 | "; 89 | } 90 | 91 | augment "/bbf-vomci-func:vomci" 92 | + "/bbf-vomci-func:remote-nf" 93 | + "/bbf-vomci-func:nf-client" 94 | + "/bbf-vomci-func:initiate" 95 | + "/bbf-vomci-func:remote-server" 96 | + "/bbf-vomci-func:transport" 97 | + "/bbf-vomci-func-ka:kafka" 98 | + "/bbf-vomci-func-ka:kafka-agent" 99 | + "/bbf-vomci-func-ka:access-point" 100 | + "/bbf-vomci-func-ka:kafka-agent-transport-parameters" 101 | + "/bbf-vomci-func-ka:tcp-client-options" { 102 | description 103 | "The Kafka connection parameters for TCP transport."; 104 | case tcp-transport { 105 | description 106 | "Selection for TCP transport."; 107 | container tcp-client-parameters { 108 | description 109 | "The TCP configuration."; 110 | uses tcpc:tcp-client-grouping; 111 | } 112 | } 113 | } 114 | } 115 | -------------------------------------------------------------------------------- /standard/application/bbf-vomci-function-kafka-agent.yang: -------------------------------------------------------------------------------- 1 | module bbf-vomci-function-kafka-agent { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-vomci-function-kafka-agent"; 4 | prefix bbf-vomci-func-ka; 5 | 6 | import bbf-kafka-agent { 7 | prefix bbf-kafkaa; 8 | } 9 | import bbf-vomci-function { 10 | prefix bbf-vomci-func; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for vOMCI Kafka 30 | transport functionality as described in TR-451. 31 | 32 | Copyright (c) 2019-2022, Broadband Forum 33 | 34 | Redistribution and use in source and binary forms, with or 35 | without modification, are permitted provided that the following 36 | conditions are met: 37 | 38 | 1. Redistributions of source code must retain the above copyright 39 | notice, this list of conditions and the following disclaimer. 40 | 41 | 2. Redistributions in binary form must reproduce the above 42 | copyright notice, this list of conditions and the following 43 | disclaimer in the documentation and/or other materials 44 | provided with the distribution. 45 | 46 | 3. Neither the name of the copyright holder nor the names of its 47 | contributors may be used to endorse or promote products 48 | derived from this software without specific prior written 49 | permission. 50 | 51 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 52 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 53 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 54 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 55 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 56 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 57 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 58 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 59 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 60 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 61 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 62 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 63 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 64 | 65 | The above license is used as a license under copyright only. 66 | Please reference the Forum IPR Policy for patent licensing terms 67 | . 68 | 69 | Any moral rights which are necessary to exercise under the above 70 | license grant are also deemed granted under this license. 71 | 72 | This version of this YANG module is part of TR-451; see 73 | the TR itself for full legal notices."; 74 | 75 | revision 2022-06-07 { 76 | description 77 | "Issue 1. 78 | * Approval Date: 2022-06-07. 79 | * Publication Date: 2022-06-07."; 80 | reference 81 | "TR-451: vOMCI Specification 82 | "; 84 | } 85 | 86 | // Kafka Agent transport specific augment 87 | 88 | augment "/bbf-vomci-func:vomci" 89 | + "/bbf-vomci-func:remote-nf" 90 | + "/bbf-vomci-func:nf-client" 91 | + "/bbf-vomci-func:initiate" 92 | + "/bbf-vomci-func:remote-server" 93 | + "/bbf-vomci-func:transport" { 94 | description 95 | "The Kafka client transport."; 96 | case kafka { 97 | description 98 | "Selection for Kafka client transport."; 99 | uses bbf-kafkaa:kafka-agent-transport; 100 | } 101 | } 102 | } 103 | -------------------------------------------------------------------------------- /standard/application/bbf-vomci-proxy-grpc-client.yang: -------------------------------------------------------------------------------- 1 | module bbf-vomci-proxy-grpc-client { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-vomci-proxy-grpc-client"; 4 | prefix bbf-vomci-proxy-grpcc; 5 | 6 | import bbf-grpc-client { 7 | prefix bbf-grpcc; 8 | } 9 | import bbf-vomci-proxy { 10 | prefix bbf-vomci-proxy; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for vOMCI gRPC 30 | client functionality as described in TR-451. 31 | 32 | Copyright (c) 2019-2022, Broadband Forum 33 | 34 | Redistribution and use in source and binary forms, with or 35 | without modification, are permitted provided that the following 36 | conditions are met: 37 | 38 | 1. Redistributions of source code must retain the above copyright 39 | notice, this list of conditions and the following disclaimer. 40 | 41 | 2. Redistributions in binary form must reproduce the above 42 | copyright notice, this list of conditions and the following 43 | disclaimer in the documentation and/or other materials 44 | provided with the distribution. 45 | 46 | 3. Neither the name of the copyright holder nor the names of its 47 | contributors may be used to endorse or promote products 48 | derived from this software without specific prior written 49 | permission. 50 | 51 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 52 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 53 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 54 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 55 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 56 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 57 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 58 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 59 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 60 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 61 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 62 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 63 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 64 | 65 | The above license is used as a license under copyright only. 66 | Please reference the Forum IPR Policy for patent licensing terms 67 | . 68 | 69 | Any moral rights which are necessary to exercise under the above 70 | license grant are also deemed granted under this license. 71 | 72 | This version of this YANG module is part of TR-451; see 73 | the TR itself for full legal notices."; 74 | 75 | revision 2022-06-07 { 76 | description 77 | "Issue 1. 78 | * Approval Date: 2022-06-07. 79 | * Publication Date: 2022-06-07."; 80 | reference 81 | "TR-451: vOMCI Specification 82 | "; 84 | } 85 | 86 | // gRPC client transport specific augment 87 | 88 | augment "/bbf-vomci-proxy:vomci" 89 | + "/bbf-vomci-proxy:remote-nf" 90 | + "/bbf-vomci-proxy:nf-client" 91 | + "/bbf-vomci-proxy:initiate" 92 | + "/bbf-vomci-proxy:remote-server" 93 | + "/bbf-vomci-proxy:transport" { 94 | description 95 | "The gRPC client transport."; 96 | case grpc { 97 | description 98 | "Selection for gRPC client transport."; 99 | uses bbf-grpcc:grpc-client-transport; 100 | } 101 | } 102 | } 103 | -------------------------------------------------------------------------------- /standard/application/bbf-vomci-proxy-grpc-server-tcp.yang: -------------------------------------------------------------------------------- 1 | module bbf-vomci-proxy-grpc-server-tcp { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-vomci-proxy-grpc-server-tcp"; 4 | prefix bbf-vomci-proxy-grpcs-tcp; 5 | 6 | import bbf-vomci-proxy { 7 | prefix bbf-vomci-proxy; 8 | } 9 | import bbf-vomci-proxy-grpc-server { 10 | prefix bbf-vomci-proxy-grpcs; 11 | } 12 | import ietf-tcp-server { 13 | prefix tcps; 14 | } 15 | import bbf-vomci-grpc-common { 16 | prefix bbf-vomci-grpc-c; 17 | } 18 | 19 | organization 20 | "Broadband Forum 21 | SDN/NFV Work Area"; 22 | contact 23 | "Comments or questions about this Broadband Forum YANG module 24 | should be directed to . 25 | 26 | Editor: Andre Brizido, Altice Labs 27 | 28 | PS Leader: Ken Kerpez, DZS 29 | 30 | WA Director: Mengmeng Li, China Mobile 31 | 32 | WA Director: Bruno Cornaglia, Vodafone 33 | 34 | WA Director: Haomian Zheng, Huawei"; 35 | description 36 | "This module contains a collection of YANG definitions for 37 | supporting the Broadband Forum requirements for vOMCI gRPC 38 | server functionality over TCP transport as described in TR-451. 39 | 40 | Copyright (c) 2019-2025, Broadband Forum 41 | 42 | Redistribution and use in source and binary forms, with or 43 | without modification, are permitted provided that the following 44 | conditions are met: 45 | 46 | 1. Redistributions of source code must retain the above copyright 47 | notice, this list of conditions and the following disclaimer. 48 | 49 | 2. Redistributions in binary form must reproduce the above 50 | copyright notice, this list of conditions and the following 51 | disclaimer in the documentation and/or other materials 52 | provided with the distribution. 53 | 54 | 3. Neither the name of the copyright holder nor the names of its 55 | contributors may be used to endorse or promote products 56 | derived from this software without specific prior written 57 | permission. 58 | 59 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 60 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 61 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 62 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 63 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 64 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 65 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 66 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 67 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 68 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 69 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 70 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 71 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 72 | 73 | The above license is used as a license under copyright only. 74 | Please reference the Forum IPR Policy for patent licensing terms 75 | . 76 | 77 | Any moral rights which are necessary to exercise under the above 78 | license grant are also deemed granted under this license. 79 | 80 | This version of this YANG module is part of TR-451a1; see 81 | the TR itself for full legal notices."; 82 | 83 | revision 2025-02-03 { 84 | description 85 | "Amendment 1. 86 | * Approval Date: 2025-02-03. 87 | * Publication Date: 2025-02-03."; 88 | reference 89 | "TR-451a1: vOMCI Specification 90 | "; 92 | } 93 | 94 | augment "/bbf-vomci-proxy:vomci" 95 | + "/bbf-vomci-proxy:remote-nf" 96 | + "/bbf-vomci-proxy:nf-server" 97 | + "/bbf-vomci-proxy:listen" 98 | + "/bbf-vomci-proxy:listen-endpoint" 99 | + "/bbf-vomci-proxy:transport" 100 | + "/bbf-vomci-proxy-grpcs:grpc" 101 | + "/bbf-vomci-proxy-grpcs:grpc-server" 102 | + "/bbf-vomci-proxy-grpcs:tcp-client-options" { 103 | description 104 | "The gRPC server connection parameters for TCP transport."; 105 | case tcp-transport { 106 | description 107 | "Select TCP transport."; 108 | container tcp-server-parameters { 109 | description 110 | "The TCP configuration."; 111 | uses tcps:tcp-server-grouping; 112 | uses bbf-vomci-grpc-c:server-authentication; 113 | } 114 | } 115 | } 116 | } 117 | -------------------------------------------------------------------------------- /standard/application/bbf-vomci-proxy-grpc-server.yang: -------------------------------------------------------------------------------- 1 | module bbf-vomci-proxy-grpc-server { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-vomci-proxy-grpc-server"; 4 | prefix bbf-vomci-proxy-grpcs; 5 | 6 | import bbf-grpc-server { 7 | prefix bbf-grpcs; 8 | } 9 | import bbf-vomci-proxy { 10 | prefix bbf-vomci-proxy; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for vOMCI gRPC 30 | server transport functionality as described in TR-451. 31 | 32 | Copyright (c) 2019-2022, Broadband Forum 33 | 34 | Redistribution and use in source and binary forms, with or 35 | without modification, are permitted provided that the following 36 | conditions are met: 37 | 38 | 1. Redistributions of source code must retain the above copyright 39 | notice, this list of conditions and the following disclaimer. 40 | 41 | 2. Redistributions in binary form must reproduce the above 42 | copyright notice, this list of conditions and the following 43 | disclaimer in the documentation and/or other materials 44 | provided with the distribution. 45 | 46 | 3. Neither the name of the copyright holder nor the names of its 47 | contributors may be used to endorse or promote products 48 | derived from this software without specific prior written 49 | permission. 50 | 51 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 52 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 53 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 54 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 55 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 56 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 57 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 58 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 59 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 60 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 61 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 62 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 63 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 64 | 65 | The above license is used as a license under copyright only. 66 | Please reference the Forum IPR Policy for patent licensing terms 67 | . 68 | 69 | Any moral rights which are necessary to exercise under the above 70 | license grant are also deemed granted under this license. 71 | 72 | This version of this YANG module is part of TR-451; see 73 | the TR itself for full legal notices."; 74 | 75 | revision 2022-06-07 { 76 | description 77 | "Issue 1. 78 | * Approval Date: 2022-06-07. 79 | * Publication Date: 2022-06-07."; 80 | reference 81 | "TR-451: vOMCI Specification 82 | "; 84 | } 85 | 86 | // gRPC server transport specific augment 87 | 88 | augment "/bbf-vomci-proxy:vomci" 89 | + "/bbf-vomci-proxy:remote-nf" 90 | + "/bbf-vomci-proxy:nf-server" 91 | + "/bbf-vomci-proxy:listen" 92 | + "/bbf-vomci-proxy:listen-endpoint" 93 | + "/bbf-vomci-proxy:transport" { 94 | description 95 | "The gRPC server transport."; 96 | case grpc { 97 | description 98 | "Selection for gRPC server transport."; 99 | uses bbf-grpcs:grpc-server-transport; 100 | } 101 | } 102 | } 103 | -------------------------------------------------------------------------------- /standard/application/bbf-vomci-proxy-kafka-agent-tcp.yang: -------------------------------------------------------------------------------- 1 | module bbf-vomci-proxy-kafka-agent-tcp { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-vomci-proxy-kafka-agent-tcp"; 4 | prefix bbf-vomci-proxy-ka-tcp; 5 | 6 | import bbf-vomci-proxy { 7 | prefix bbf-vomci-proxy; 8 | } 9 | import bbf-vomci-proxy-kafka-agent { 10 | prefix bbf-vomci-proxy-ka; 11 | } 12 | import ietf-tcp-client { 13 | prefix tcpc; 14 | } 15 | 16 | organization 17 | "Broadband Forum 18 | SDN/NFV Work Area"; 19 | contact 20 | "Comments or questions about this Broadband Forum YANG module 21 | should be directed to . 22 | 23 | Editor: Andre Brizido, Altice Labs 24 | 25 | PS Leader: Ken Kerpez, DZS 26 | 27 | WA Director: Mengmeng Li, China Mobile 28 | 29 | WA Director: Bruno Cornaglia, Vodafone 30 | 31 | WA Director: Haomian Zheng, Huawei"; 32 | description 33 | "This module contains a collection of YANG definitions for 34 | supporting the Broadband Forum requirements for vOMCI Kafka 35 | transport over TCP functionality as described in TR-451. 36 | 37 | Copyright (c) 2019-2025, Broadband Forum 38 | 39 | Redistribution and use in source and binary forms, with or 40 | without modification, are permitted provided that the following 41 | conditions are met: 42 | 43 | 1. Redistributions of source code must retain the above copyright 44 | notice, this list of conditions and the following disclaimer. 45 | 46 | 2. Redistributions in binary form must reproduce the above 47 | copyright notice, this list of conditions and the following 48 | disclaimer in the documentation and/or other materials 49 | provided with the distribution. 50 | 51 | 3. Neither the name of the copyright holder nor the names of its 52 | contributors may be used to endorse or promote products 53 | derived from this software without specific prior written 54 | permission. 55 | 56 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 57 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 58 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 59 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 60 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 61 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 62 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 63 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 64 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 65 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 66 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 67 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 68 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 69 | 70 | The above license is used as a license under copyright only. 71 | Please reference the Forum IPR Policy for patent licensing terms 72 | . 73 | 74 | Any moral rights which are necessary to exercise under the above 75 | license grant are also deemed granted under this license. 76 | 77 | This version of this YANG module is part of TR-451a1; see 78 | the TR itself for full legal notices."; 79 | 80 | revision 2025-02-03 { 81 | description 82 | "Amendment 1. 83 | * Approval Date: 2025-02-03. 84 | * Publication Date: 2025-02-03."; 85 | reference 86 | "TR-451a1: vOMCI Specification 87 | "; 89 | } 90 | 91 | augment "/bbf-vomci-proxy:vomci" 92 | + "/bbf-vomci-proxy:remote-nf" 93 | + "/bbf-vomci-proxy:nf-client" 94 | + "/bbf-vomci-proxy:initiate" 95 | + "/bbf-vomci-proxy:remote-server" 96 | + "/bbf-vomci-proxy:transport" 97 | + "/bbf-vomci-proxy-ka:kafka" 98 | + "/bbf-vomci-proxy-ka:kafka-agent" 99 | + "/bbf-vomci-proxy-ka:access-point" 100 | + "/bbf-vomci-proxy-ka:kafka-agent-transport-parameters" 101 | + "/bbf-vomci-proxy-ka:tcp-client-options" { 102 | description 103 | "The Kafka connection parameters for TCP transport."; 104 | case tcp-transport { 105 | description 106 | "Selection for TCP transport."; 107 | container tcp-client-parameters { 108 | description 109 | "The TCP configuration."; 110 | uses tcpc:tcp-client-grouping; 111 | } 112 | } 113 | } 114 | } 115 | -------------------------------------------------------------------------------- /standard/application/bbf-vomci-proxy-kafka-agent.yang: -------------------------------------------------------------------------------- 1 | module bbf-vomci-proxy-kafka-agent { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-vomci-proxy-kafka-agent"; 4 | prefix bbf-vomci-proxy-ka; 5 | 6 | import bbf-kafka-agent { 7 | prefix bbf-kafkaa; 8 | } 9 | import bbf-vomci-proxy { 10 | prefix bbf-vomci-proxy; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | SDN/NFV Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Tim Carey, Nokia 21 | 22 | Editor: Jeff Hartley, Commscope 23 | 24 | WA Director: Mengmeng Li, China Mobile 25 | 26 | WA Director: Bruno Cornaglia, Vodafone"; 27 | description 28 | "This module contains a collection of YANG definitions for 29 | supporting the Broadband Forum requirements for vOMCI Proxy 30 | Kafka functionality as described in TR-451. 31 | 32 | Copyright (c) 2019-2022, Broadband Forum 33 | 34 | Redistribution and use in source and binary forms, with or 35 | without modification, are permitted provided that the following 36 | conditions are met: 37 | 38 | 1. Redistributions of source code must retain the above copyright 39 | notice, this list of conditions and the following disclaimer. 40 | 41 | 2. Redistributions in binary form must reproduce the above 42 | copyright notice, this list of conditions and the following 43 | disclaimer in the documentation and/or other materials 44 | provided with the distribution. 45 | 46 | 3. Neither the name of the copyright holder nor the names of its 47 | contributors may be used to endorse or promote products 48 | derived from this software without specific prior written 49 | permission. 50 | 51 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 52 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 53 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 54 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 55 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 56 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 57 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 58 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 59 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 60 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 61 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 62 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 63 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 64 | 65 | The above license is used as a license under copyright only. 66 | Please reference the Forum IPR Policy for patent licensing terms 67 | . 68 | 69 | Any moral rights which are necessary to exercise under the above 70 | license grant are also deemed granted under this license. 71 | 72 | This version of this YANG module is part of TR-451; see 73 | the TR itself for full legal notices."; 74 | 75 | revision 2022-06-07 { 76 | description 77 | "Issue 1. 78 | * Approval Date: 2022-06-07. 79 | * Publication Date: 2022-06-07."; 80 | reference 81 | "TR-451: vOMCI Specification 82 | "; 84 | } 85 | 86 | // Kafka Agent transport specific augment 87 | 88 | augment "/bbf-vomci-proxy:vomci" 89 | + "/bbf-vomci-proxy:remote-nf" 90 | + "/bbf-vomci-proxy:nf-client" 91 | + "/bbf-vomci-proxy:initiate" 92 | + "/bbf-vomci-proxy:remote-server" 93 | + "/bbf-vomci-proxy:transport" { 94 | description 95 | "The Kafka client transport."; 96 | case kafka { 97 | description 98 | "Selection for Kafka client transport."; 99 | uses bbf-kafkaa:kafka-agent-transport; 100 | } 101 | } 102 | } 103 | -------------------------------------------------------------------------------- /standard/common/bbf-d-olt-message-monitor.yang: -------------------------------------------------------------------------------- 1 | module bbf-d-olt-message-monitor { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-d-olt-message-monitor"; 4 | prefix bbf-d-olt-msg-mon; 5 | 6 | import ietf-yang-types { 7 | prefix yang; 8 | } 9 | 10 | organization 11 | "Broadband Forum 12 | SDN/NFV Work Area"; 13 | contact 14 | "Comments or questions about this Broadband Forum YANG module 15 | should be directed to . 16 | 17 | Editor: Andre Brizido, Altice Labs 18 | 19 | Editor: Antonio Marsico, Reply 20 | 21 | PS Leader: Haomian Zheng, Huawei 22 | 23 | WA Director: Mengmeng Li, China Mobile 24 | 25 | WA Director: Bruno Cornaglia, Vodafone"; 26 | description 27 | "This module contains a collection of YANG definitions for 28 | supporting the Broadband Forum requirements for monitoring 29 | the Disaggregated OLT (D-OLT) message interactions between the 30 | D-OLT and physical OLT (pOLT) Management flow control (Mfc) 31 | interfaces as described in TR-477. 32 | 33 | Copyright (c) 2024, Broadband Forum 34 | 35 | Redistribution and use in source and binary forms, with or 36 | without modification, are permitted provided that the following 37 | conditions are met: 38 | 39 | 1. Redistributions of source code must retain the above copyright 40 | notice, this list of conditions and the following disclaimer. 41 | 42 | 2. Redistributions in binary form must reproduce the above 43 | copyright notice, this list of conditions and the following 44 | disclaimer in the documentation and/or other materials 45 | provided with the distribution. 46 | 47 | 3. Neither the name of the copyright holder nor the names of its 48 | contributors may be used to endorse or promote products 49 | derived from this software without specific prior written 50 | permission. 51 | 52 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 53 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 54 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 55 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 56 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 57 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 58 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 59 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 60 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 61 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 62 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 63 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 64 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 65 | 66 | The above license is used as a license under copyright only. 67 | Please reference the Forum IPR Policy for patent licensing terms 68 | . 69 | 70 | Any moral rights which are necessary to exercise under the above 71 | license grant are also deemed granted under this license. 72 | 73 | This version of this YANG module is part of TR-477; see 74 | the TR itself for full legal notices."; 75 | 76 | revision 2024-01-19 { 77 | description 78 | "Issue 1. 79 | * Approval Date: 2024-01-19. 80 | * Publication Date: 2024-01-19."; 81 | reference 82 | "TR-477: Cloud CO Enhancement - Access Node Functional 83 | Disaggregation "; 85 | } 86 | 87 | grouping d-olt-message-statistics { 88 | description 89 | "Statistics for monitoring Mfc messages between D-OLT 90 | and the pOLT."; 91 | leaf in-messages { 92 | type yang:counter64; 93 | units "messages"; 94 | config false; 95 | description 96 | "The number of messages that have been received by the 97 | entity."; 98 | } 99 | leaf out-messages { 100 | type yang:counter64; 101 | units "messages"; 102 | config false; 103 | description 104 | "The number of messages that have been transmitted by the 105 | entity."; 106 | } 107 | leaf in-errored-messages { 108 | type yang:counter64; 109 | units "messages"; 110 | config false; 111 | description 112 | "The number of messages received by the entity that contain 113 | errors."; 114 | } 115 | } 116 | } 117 | -------------------------------------------------------------------------------- /standard/common/bbf-end-user.yang: -------------------------------------------------------------------------------- 1 | module bbf-end-user { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-end-user"; 4 | prefix bbf-eu; 5 | 6 | import bbf-yang-types { 7 | prefix bbf-yang; 8 | } 9 | import bbf-contact { 10 | prefix bbf-contact; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | Common YANG Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Nick Hancock, Adtran 21 | 22 | Editor: Ludwig Pauwels, Nokia 23 | 24 | PS Leader: Joey Boyd, Adtran 25 | 26 | WA Director: Joey Boyd, Adtran 27 | 28 | WA Director: Sven Ooghe, Nokia"; 29 | description 30 | "This module contains a collection of YANG definitions for 31 | supporting the Broadband Forum requirements on providing 32 | information for end users of network functions. 33 | 34 | Copyright (c) 2017-2023, Broadband Forum 35 | 36 | Redistribution and use in source and binary forms, with or 37 | without modification, are permitted provided that the following 38 | conditions are met: 39 | 40 | 1. Redistributions of source code must retain the above copyright 41 | notice, this list of conditions and the following disclaimer. 42 | 43 | 2. Redistributions in binary form must reproduce the above 44 | copyright notice, this list of conditions and the following 45 | disclaimer in the documentation and/or other materials 46 | provided with the distribution. 47 | 48 | 3. Neither the name of the copyright holder nor the names of its 49 | contributors may be used to endorse or promote products 50 | derived from this software without specific prior written 51 | permission. 52 | 53 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 54 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 55 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 56 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 57 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 58 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 59 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 60 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 61 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 62 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 63 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 64 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 65 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 66 | 67 | The above license is used as a license under copyright only. 68 | Please reference the Forum IPR Policy for patent licensing terms 69 | . 70 | 71 | Any moral rights which are necessary to exercise under the above 72 | license grant are also deemed granted under this license. 73 | 74 | This version of this YANG module is part of TR-383a7; see 75 | the TR itself for full legal notices."; 76 | 77 | revision 2023-12-15 { 78 | description 79 | "Amendment 7. 80 | * Approval Date: 2023-12-15. 81 | * Publication Date: 2023-12-15."; 82 | reference 83 | "TR-383a7: Common YANG Modules 84 | "; 86 | } 87 | revision 2021-06-02 { 88 | description 89 | "Amendment 4. 90 | * Approval Date: 2021-06-02. 91 | * Publication Date: 2021-06-02."; 92 | reference 93 | "TR-383a4: Common YANG Modules 94 | "; 96 | } 97 | 98 | // Groupings 99 | // End users management information 100 | 101 | grouping end-users { 102 | description 103 | "The management information that identifies the end users for a 104 | resource."; 105 | list end-user { 106 | key "end-user-id"; 107 | description 108 | "The management information related to an end user."; 109 | leaf end-user-id { 110 | type bbf-yang:string-ascii64; 111 | description 112 | "The identifier of the end user."; 113 | } 114 | uses bbf-contact:contact-information; 115 | } 116 | } 117 | } 118 | -------------------------------------------------------------------------------- /standard/interface/bbf-ghn-channel-estimation-profile-body.yang: -------------------------------------------------------------------------------- 1 | submodule bbf-ghn-channel-estimation-profile-body { 2 | yang-version 1.1; 3 | belongs-to bbf-ghn { 4 | prefix bbf-ghn; 5 | } 6 | 7 | include bbf-ghn-types; 8 | 9 | organization 10 | "Broadband Forum 11 | Common YANG Work Area"; 12 | 13 | contact 14 | "Comments or questions about this Broadband Forum YANG module 15 | should be directed to . 16 | 17 | Editor: Marcos Martinez, Marvell Semiconductor Inc. 18 | 19 | PS Leader: Joey Boyd, ADTRAN 20 | 21 | PS Leader: Ken Kerpez, ASSIA 22 | 23 | WA Director: Joey Boyd, ADTRAN 24 | 25 | WA Director: Sven Ooghe, Nokia"; 26 | 27 | description 28 | "This module contains a collection of YANG definitions for 29 | managing channel-estimation aspects of the G.hn line. 30 | 31 | Copyright (c) 2018, Broadband Forum 32 | 33 | Redistribution and use in source and binary forms, with or 34 | without modification, are permitted provided that the following 35 | conditions are met: 36 | 37 | 1. Redistributions of source code must retain the above copyright 38 | notice, this list of conditions and the following disclaimer. 39 | 40 | 2. Redistributions in binary form must reproduce the above 41 | copyright notice, this list of conditions and the following 42 | disclaimer in the documentation and/or other materials 43 | provided with the distribution. 44 | 45 | 3. Neither the name of the copyright holder nor the names of its 46 | contributors may be used to endorse or promote products 47 | derived from this software without specific prior written 48 | permission. 49 | 50 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 51 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 52 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 53 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 54 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 55 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 56 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 57 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 58 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 59 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 60 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 61 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 62 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 63 | 64 | The above license is used as a license under copyright only. 65 | Please reference the Forum IPR Policy for patent licensing terms 66 | . 67 | 68 | Any moral rights which are necessary to exercise under the above 69 | license grant are also deemed granted under this license. 70 | 71 | This version of this YANG module is part of TR-374; see 72 | the TR itself for full legal notices."; 73 | 74 | revision 2018-07-13 { 75 | description 76 | "Initial revision. 77 | * Approval Date: 2018-06-04. 78 | * Publication Date: see revision date above."; 79 | reference 80 | "TR-374: Yang Modules for Management of G.hn Systems in FTTdp 81 | Architecture "; 83 | } 84 | 85 | grouping channel-estimation-parameters { 86 | description 87 | "Channel estimation configuration parameters."; 88 | reference 89 | "ITU-T G.9961 clause 8.11"; 90 | leaf minimum-grouping-size { 91 | type group-size; 92 | description 93 | "Minimum grouping to be used during channel estimation 94 | process."; 95 | reference 96 | "ITU-T G.9961 clause 8.11"; 97 | } 98 | } 99 | 100 | 101 | grouping channel-estimation-profile-group { 102 | description 103 | "Defines the parameters contained in a channel 104 | estimation profile."; 105 | 106 | uses channel-estimation-parameters; 107 | } 108 | } 109 | -------------------------------------------------------------------------------- /standard/interface/bbf-ghn-dba-profile-body.yang: -------------------------------------------------------------------------------- 1 | submodule bbf-ghn-dba-profile-body { 2 | yang-version 1.1; 3 | belongs-to bbf-ghn { 4 | prefix bbf-ghn; 5 | } 6 | include bbf-ghn-types; 7 | 8 | organization 9 | "Broadband Forum 10 | Common YANG Work Area"; 11 | 12 | contact 13 | "Comments or questions about this Broadband Forum YANG module 14 | should be directed to . 15 | 16 | Editor: Marcos Martinez, Marvell Semiconductor Inc. 17 | 18 | PS Leader: Joey Boyd, ADTRAN 19 | 20 | PS Leader: Ken Kerpez, ASSIA 21 | 22 | WA Director: Joey Boyd, ADTRAN 23 | 24 | WA Director: Sven Ooghe, Nokia"; 25 | 26 | description 27 | "This module contains a collection of YANG definitions for 28 | managing DBA aspects of the G.hn line. 29 | 30 | Copyright (c) 2018, Broadband Forum 31 | 32 | Redistribution and use in source and binary forms, with or 33 | without modification, are permitted provided that the following 34 | conditions are met: 35 | 36 | 1. Redistributions of source code must retain the above copyright 37 | notice, this list of conditions and the following disclaimer. 38 | 39 | 2. Redistributions in binary form must reproduce the above 40 | copyright notice, this list of conditions and the following 41 | disclaimer in the documentation and/or other materials 42 | provided with the distribution. 43 | 44 | 3. Neither the name of the copyright holder nor the names of its 45 | contributors may be used to endorse or promote products 46 | derived from this software without specific prior written 47 | permission. 48 | 49 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 50 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 51 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 52 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 53 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 54 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 55 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 56 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 57 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 58 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 59 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 60 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 61 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 62 | 63 | The above license is used as a license under copyright only. 64 | Please reference the Forum IPR Policy for patent licensing terms 65 | . 66 | 67 | Any moral rights which are necessary to exercise under the above 68 | license grant are also deemed granted under this license. 69 | 70 | This version of this YANG module is part of TR-374; see 71 | the TR itself for full legal notices."; 72 | 73 | revision 2018-07-13 { 74 | description 75 | "Initial revision. 76 | * Approval Date: 2018-06-04. 77 | * Publication Date: see revision date above."; 78 | reference 79 | "TR-374: Yang Modules for Management of G.hn Systems in FTTdp 80 | Architecture "; 82 | } 83 | 84 | grouping dba-parameters { 85 | description 86 | "Dynamic Bandwidth Allocation (DBA) configuration parameters."; 87 | 88 | leaf split-ratio { 89 | type percentage-or-inactive; 90 | description 91 | "Split ratio between downstream and upstream directions 92 | for this prorofile. It is represented as an integer value 93 | between 0 and 100. when set to inactive, the split ratio is 94 | not used and the domain master us free to allocate 95 | resources following its own criteria."; 96 | } 97 | } 98 | 99 | 100 | grouping dba-profile-group { 101 | description 102 | "Defines the parameters contained in a DBA profile."; 103 | 104 | uses dba-parameters; 105 | } 106 | } 107 | -------------------------------------------------------------------------------- /standard/interface/bbf-ghn-domain-id-profile-body.yang: -------------------------------------------------------------------------------- 1 | submodule bbf-ghn-domain-id-profile-body { 2 | yang-version 1.1; 3 | belongs-to bbf-ghn { 4 | prefix bbf-ghn; 5 | } 6 | 7 | include bbf-ghn-types; 8 | 9 | organization 10 | "Broadband Forum 11 | Common YANG Work Area"; 12 | 13 | contact 14 | "Comments or questions about this Broadband Forum YANG module 15 | should be directed to . 16 | 17 | Editor: Marcos Martinez, Marvell Semiconductor Inc. 18 | 19 | PS Leader: Joey Boyd, ADTRAN 20 | 21 | PS Leader: Ken Kerpez, ASSIA 22 | 23 | WA Director: Joey Boyd, ADTRAN 24 | 25 | WA Director: Sven Ooghe, Nokia"; 26 | 27 | description 28 | "This module contains a collection of YANG definitions for 29 | managing domain-id aspects of the G.hn line. 30 | 31 | Copyright (c) 2018, Broadband Forum 32 | 33 | Redistribution and use in source and binary forms, with or 34 | without modification, are permitted provided that the following 35 | conditions are met: 36 | 37 | 1. Redistributions of source code must retain the above copyright 38 | notice, this list of conditions and the following disclaimer. 39 | 40 | 2. Redistributions in binary form must reproduce the above 41 | copyright notice, this list of conditions and the following 42 | disclaimer in the documentation and/or other materials 43 | provided with the distribution. 44 | 45 | 3. Neither the name of the copyright holder nor the names of its 46 | contributors may be used to endorse or promote products 47 | derived from this software without specific prior written 48 | permission. 49 | 50 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 51 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 52 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 53 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 54 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 55 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 56 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 57 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 58 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 59 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 60 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 61 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 62 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 63 | 64 | The above license is used as a license under copyright only. 65 | Please reference the Forum IPR Policy for patent licensing terms 66 | . 67 | 68 | Any moral rights which are necessary to exercise under the above 69 | license grant are also deemed granted under this license. 70 | 71 | This version of this YANG module is part of TR-374; see 72 | the TR itself for full legal notices."; 73 | 74 | revision 2018-07-13 { 75 | description 76 | "Initial revision. 77 | * Approval Date: 2018-06-04. 78 | * Publication Date: see revision date above."; 79 | reference 80 | "TR-374: Yang Modules for Management of G.hn Systems in FTTdp 81 | Architecture "; 83 | } 84 | 85 | 86 | grouping domain-id-parameters { 87 | description 88 | "Domain identification configuration parameters."; 89 | 90 | leaf domain-name { 91 | type bbf-ghn:domain-name; 92 | description 93 | "The domain name of the domain connected through 94 | this G.hn interface."; 95 | reference 96 | "ITU-T G.9961 clause 8.8.5.2"; 97 | } 98 | 99 | leaf minimum-supported-bandplan { 100 | type bbf-ghn:bandplan; 101 | description 102 | "Minimum bandplan to be able to enter the domain."; 103 | reference 104 | "ITU-T G.9960 clause 6"; 105 | } 106 | 107 | leaf maximum-supported-bandplan { 108 | type bbf-ghn:bandplan; 109 | description 110 | "Maximum bandplan to be able to enter the domain."; 111 | reference 112 | "ITU-T G.9960 clause 6"; 113 | } 114 | } 115 | 116 | 117 | grouping domain-id-profile-group { 118 | description 119 | "Defines the parameters contained in a domain-id profile."; 120 | 121 | uses domain-id-parameters; 122 | } 123 | } 124 | -------------------------------------------------------------------------------- /standard/interface/bbf-ghn-domain-state.yang: -------------------------------------------------------------------------------- 1 | submodule bbf-ghn-domain-state { 2 | yang-version 1.1; 3 | belongs-to bbf-ghn { 4 | prefix bbf-ghn; 5 | } 6 | 7 | import ietf-interfaces { 8 | prefix if; 9 | } 10 | 11 | include bbf-ghn-base; 12 | 13 | include bbf-ghn-domain-status-body; 14 | 15 | organization 16 | "Broadband Forum 17 | Common YANG Work Area"; 18 | 19 | contact 20 | "Comments or questions about this Broadband Forum YANG module 21 | should be directed to . 22 | 23 | Editor: Marcos Martinez, Marvell Semiconductor Inc. 24 | 25 | PS Leader: Joey Boyd, ADTRAN 26 | 27 | PS Leader: Ken Kerpez, ASSIA 28 | 29 | WA Director: Joey Boyd, ADTRAN 30 | 31 | WA Director: Sven Ooghe, Nokia"; 32 | 33 | description 34 | "This module contains a collection of YANG definitions for 35 | managing domain state data of G.hn interface. 36 | 37 | Copyright (c) 2018, Broadband Forum 38 | 39 | Redistribution and use in source and binary forms, with or 40 | without modification, are permitted provided that the following 41 | conditions are met: 42 | 43 | 1. Redistributions of source code must retain the above copyright 44 | notice, this list of conditions and the following disclaimer. 45 | 46 | 2. Redistributions in binary form must reproduce the above 47 | copyright notice, this list of conditions and the following 48 | disclaimer in the documentation and/or other materials 49 | provided with the distribution. 50 | 51 | 3. Neither the name of the copyright holder nor the names of its 52 | contributors may be used to endorse or promote products 53 | derived from this software without specific prior written 54 | permission. 55 | 56 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 57 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 58 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 59 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 60 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 61 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 62 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 63 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 64 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 65 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 66 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 67 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 68 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 69 | 70 | The above license is used as a license under copyright only. 71 | Please reference the Forum IPR Policy for patent licensing terms 72 | . 73 | 74 | Any moral rights which are necessary to exercise under the above 75 | license grant are also deemed granted under this license. 76 | 77 | This version of this YANG module is part of TR-374; see 78 | the TR itself for full legal notices."; 79 | 80 | revision 2018-07-13 { 81 | description 82 | "Initial revision. 83 | * Approval Date: 2018-06-04. 84 | * Publication Date: see revision date above."; 85 | reference 86 | "TR-374: Yang Modules for Management of G.hn Systems in FTTdp 87 | Architecture "; 89 | } 90 | 91 | grouping domain-state-group { 92 | description 93 | "Grouping of the domain state categories of parameters."; 94 | 95 | container status { 96 | description 97 | "Status state data for domain-wide parameters of the 98 | G.hn network connected through the G.hn interface."; 99 | 100 | uses domain-status-parameters; 101 | } 102 | } 103 | 104 | 105 | augment '/if:interfaces-state/if:interface/bbf-ghn:ghn-interface/' 106 | + 'bbf-ghn:domain' { 107 | description 108 | "Domain-wide state data."; 109 | 110 | uses domain-state-group; 111 | } 112 | } 113 | -------------------------------------------------------------------------------- /standard/interface/bbf-ghn-link-state.yang: -------------------------------------------------------------------------------- 1 | submodule bbf-ghn-link-state { 2 | yang-version 1.1; 3 | belongs-to bbf-ghn { 4 | prefix bbf-ghn; 5 | } 6 | 7 | include bbf-ghn-base; 8 | include bbf-ghn-types; 9 | include bbf-ghn-link-status-body; 10 | 11 | organization 12 | "Broadband Forum 13 | Common YANG Work Area"; 14 | 15 | contact 16 | "Comments or questions about this Broadband Forum YANG module 17 | should be directed to . 18 | 19 | Editor: Marcos Martinez, Marvell Semiconductor Inc. 20 | 21 | PS Leader: Joey Boyd, ADTRAN 22 | 23 | PS Leader: Ken Kerpez, ASSIA 24 | 25 | WA Director: Joey Boyd, ADTRAN 26 | 27 | WA Director: Sven Ooghe, Nokia"; 28 | 29 | description 30 | "This module contains a collection of YANG definitions for 31 | managing node state data of G.hn interface. 32 | 33 | Copyright (c) 2018, Broadband Forum 34 | 35 | Redistribution and use in source and binary forms, with or 36 | without modification, are permitted provided that the following 37 | conditions are met: 38 | 39 | 1. Redistributions of source code must retain the above copyright 40 | notice, this list of conditions and the following disclaimer. 41 | 42 | 2. Redistributions in binary form must reproduce the above 43 | copyright notice, this list of conditions and the following 44 | disclaimer in the documentation and/or other materials 45 | provided with the distribution. 46 | 47 | 3. Neither the name of the copyright holder nor the names of its 48 | contributors may be used to endorse or promote products 49 | derived from this software without specific prior written 50 | permission. 51 | 52 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 53 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 54 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 55 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 56 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 57 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 58 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 59 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 60 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 61 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 62 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 63 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 64 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 65 | 66 | The above license is used as a license under copyright only. 67 | Please reference the Forum IPR Policy for patent licensing terms 68 | . 69 | 70 | Any moral rights which are necessary to exercise under the above 71 | license grant are also deemed granted under this license. 72 | 73 | This version of this YANG module is part of TR-374; see 74 | the TR itself for full legal notices."; 75 | 76 | revision 2018-07-13 { 77 | description 78 | "Initial revision. 79 | * Approval Date: 2018-06-04. 80 | * Publication Date: see revision date above."; 81 | reference 82 | "TR-374: Yang Modules for Management of G.hn Systems in FTTdp 83 | Architecture "; 85 | } 86 | 87 | grouping link-state-group { 88 | description 89 | "Grouping of the link state categories of parameters."; 90 | 91 | container status { 92 | description 93 | "Status state data for link-wide parameters of the 94 | G.hn network connected through the G.hn interface."; 95 | 96 | uses link-status-parameters; 97 | } 98 | } 99 | } 100 | -------------------------------------------------------------------------------- /standard/interface/bbf-ghn-local-node-info-body.yang: -------------------------------------------------------------------------------- 1 | submodule bbf-ghn-local-node-info-body { 2 | yang-version 1.1; 3 | belongs-to bbf-ghn { 4 | prefix bbf-ghn; 5 | } 6 | 7 | import ietf-yang-types { 8 | prefix yang; 9 | } 10 | 11 | include bbf-ghn-types; 12 | 13 | organization 14 | "Broadband Forum 15 | Common YANG Work Area"; 16 | 17 | contact 18 | "Comments or questions about this Broadband Forum YANG module 19 | should be directed to . 20 | 21 | Editor: Marcos Martinez, Marvell Semiconductor Inc. 22 | 23 | PS Leader: Joey Boyd, ADTRAN 24 | 25 | PS Leader: Ken Kerpez, ASSIA 26 | 27 | WA Director: Joey Boyd, ADTRAN 28 | 29 | WA Director: Sven Ooghe, Nokia"; 30 | 31 | description 32 | "This module contains a collection of domain status-related 33 | state data 34 | 35 | Copyright (c) 2018, Broadband Forum 36 | 37 | Redistribution and use in source and binary forms, with or 38 | without modification, are permitted provided that the following 39 | conditions are met: 40 | 41 | 1. Redistributions of source code must retain the above copyright 42 | notice, this list of conditions and the following disclaimer. 43 | 44 | 2. Redistributions in binary form must reproduce the above 45 | copyright notice, this list of conditions and the following 46 | disclaimer in the documentation and/or other materials 47 | provided with the distribution. 48 | 49 | 3. Neither the name of the copyright holder nor the names of its 50 | contributors may be used to endorse or promote products 51 | derived from this software without specific prior written 52 | permission. 53 | 54 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 55 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 56 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 57 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 58 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 59 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 60 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 61 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 62 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 63 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 64 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 65 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 66 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 67 | 68 | The above license is used as a license under copyright only. 69 | Please reference the Forum IPR Policy for patent licensing terms 70 | . 71 | 72 | Any moral rights which are necessary to exercise under the above 73 | license grant are also deemed granted under this license. 74 | 75 | This version of this YANG module is part of TR-374; see 76 | the TR itself for full legal notices."; 77 | 78 | revision 2018-07-13 { 79 | description 80 | "Initial revision. 81 | * Approval Date: 2018-06-04. 82 | * Publication Date: see revision date above."; 83 | reference 84 | "TR-374: Yang Modules for Management of G.hn Systems in FTTdp 85 | Architecture "; 87 | } 88 | 89 | grouping local-node-info-parameters { 90 | description 91 | "Local node identification"; 92 | 93 | leaf local-node-mac { 94 | type yang:mac-address; 95 | description 96 | "Medium Access Control (MAC) address of the local node."; 97 | } 98 | } 99 | } 100 | -------------------------------------------------------------------------------- /standard/interface/bbf-ghn-local-node-info.yang: -------------------------------------------------------------------------------- 1 | submodule bbf-ghn-local-node-info { 2 | yang-version 1.1; 3 | belongs-to bbf-ghn { 4 | prefix bbf-ghn; 5 | } 6 | 7 | import ietf-interfaces { 8 | prefix if; 9 | } 10 | 11 | include bbf-ghn-base; 12 | 13 | include bbf-ghn-local-node-info-body; 14 | 15 | organization 16 | "Broadband Forum 17 | Common YANG Work Area"; 18 | 19 | contact 20 | "Comments or questions about this Broadband Forum YANG module 21 | should be directed to . 22 | 23 | Editor: Marcos Martinez, Marvell Semiconductor Inc. 24 | 25 | PS Leader: Joey Boyd, ADTRAN 26 | 27 | PS Leader: Ken Kerpez, ASSIA 28 | 29 | WA Director: Joey Boyd, ADTRAN 30 | 31 | WA Director: Sven Ooghe, Nokia"; 32 | 33 | description 34 | "This module contains a collection of YANG definitions for 35 | managing domain state data of G.hn interface. 36 | 37 | Copyright (c) 2018, Broadband Forum 38 | 39 | Redistribution and use in source and binary forms, with or 40 | without modification, are permitted provided that the following 41 | conditions are met: 42 | 43 | 1. Redistributions of source code must retain the above copyright 44 | notice, this list of conditions and the following disclaimer. 45 | 46 | 2. Redistributions in binary form must reproduce the above 47 | copyright notice, this list of conditions and the following 48 | disclaimer in the documentation and/or other materials 49 | provided with the distribution. 50 | 51 | 3. Neither the name of the copyright holder nor the names of its 52 | contributors may be used to endorse or promote products 53 | derived from this software without specific prior written 54 | permission. 55 | 56 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 57 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 58 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 59 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 60 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 61 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 62 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 63 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 64 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 65 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 66 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 67 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 68 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 69 | 70 | The above license is used as a license under copyright only. 71 | Please reference the Forum IPR Policy for patent licensing terms 72 | . 73 | 74 | Any moral rights which are necessary to exercise under the above 75 | license grant are also deemed granted under this license. 76 | 77 | This version of this YANG module is part of TR-374; see 78 | the TR itself for full legal notices."; 79 | 80 | revision 2018-07-13 { 81 | description 82 | "Initial revision. 83 | * Approval Date: 2018-06-04. 84 | * Publication Date: see revision date above."; 85 | reference 86 | "TR-374: Yang Modules for Management of G.hn Systems in FTTdp 87 | Architecture "; 89 | } 90 | 91 | augment '/if:interfaces-state/if:interface/bbf-ghn:ghn-interface/' 92 | + 'local-node-info' { 93 | description 94 | "Local node identification."; 95 | 96 | uses local-node-info-parameters; 97 | } 98 | } 99 | -------------------------------------------------------------------------------- /standard/interface/bbf-ghn-node-profiles.yang: -------------------------------------------------------------------------------- 1 | submodule bbf-ghn-node-profiles { 2 | yang-version 1.1; 3 | belongs-to bbf-ghn { 4 | prefix bbf-ghn; 5 | } 6 | 7 | include bbf-ghn-base; 8 | 9 | /* Profile bodies */ 10 | include bbf-ghn-node-id-profile-body; 11 | 12 | organization 13 | "Broadband Forum 14 | Common YANG Work Area"; 15 | 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Marcos Martinez, Marvell Semiconductor Inc. 21 | 22 | PS Leader: Joey Boyd, ADTRAN 23 | 24 | PS Leader: Ken Kerpez, ASSIA 25 | 26 | WA Director: Joey Boyd, ADTRAN 27 | 28 | WA Director: Sven Ooghe, Nokia"; 29 | 30 | description 31 | "This module contains a collection of YANG definitions for 32 | managing G.hn node profiles. 33 | 34 | Copyright (c) 2018, Broadband Forum 35 | 36 | Redistribution and use in source and binary forms, with or 37 | without modification, are permitted provided that the following 38 | conditions are met: 39 | 40 | 1. Redistributions of source code must retain the above copyright 41 | notice, this list of conditions and the following disclaimer. 42 | 43 | 2. Redistributions in binary form must reproduce the above 44 | copyright notice, this list of conditions and the following 45 | disclaimer in the documentation and/or other materials 46 | provided with the distribution. 47 | 48 | 3. Neither the name of the copyright holder nor the names of its 49 | contributors may be used to endorse or promote products 50 | derived from this software without specific prior written 51 | permission. 52 | 53 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 54 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 55 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 56 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 57 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 58 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 59 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 60 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 61 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 62 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 63 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 64 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 65 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 66 | 67 | The above license is used as a license under copyright only. 68 | Please reference the Forum IPR Policy for patent licensing terms 69 | . 70 | 71 | Any moral rights which are necessary to exercise under the above 72 | license grant are also deemed granted under this license. 73 | 74 | This version of this YANG module is part of TR-374; see 75 | the TR itself for full legal notices."; 76 | 77 | revision 2018-07-13 { 78 | description 79 | "Initial revision. 80 | * Approval Date: 2018-06-04. 81 | * Publication Date: see revision date above."; 82 | reference 83 | "TR-374: Yang Modules for Management of G.hn Systems in FTTdp 84 | Architecture "; 86 | } 87 | 88 | 89 | typedef node-id-profile-ref { 90 | type leafref { 91 | path '/bbf-ghn:ghn/bbf-ghn:node/bbf-ghn:node-id-profile/bbf-' 92 | + 'ghn:name'; 93 | } 94 | description 95 | "Used to reference a node-id profile."; 96 | } 97 | 98 | augment '/bbf-ghn:ghn/bbf-ghn:node' { 99 | description 100 | "Data nodes for scheduling configuration 101 | profiles."; 102 | 103 | list node-id-profile { 104 | key "name"; 105 | description 106 | "A list of node-id profiles."; 107 | 108 | leaf name { 109 | type string; 110 | description 111 | "A name that uniquely identifies the 112 | profile."; 113 | } 114 | 115 | uses node-id-profile-group; 116 | } 117 | } 118 | } 119 | -------------------------------------------------------------------------------- /standard/interface/bbf-ghn-performance-management.yang: -------------------------------------------------------------------------------- 1 | submodule bbf-ghn-performance-management { 2 | yang-version 1.1; 3 | belongs-to bbf-ghn { 4 | prefix bbf-ghn; 5 | } 6 | 7 | import ietf-interfaces { 8 | prefix if; 9 | } 10 | 11 | include bbf-ghn-base; 12 | include bbf-ghn-node-state; 13 | 14 | /* Performance bodies */ 15 | include bbf-ghn-node-performance-body; 16 | include bbf-ghn-link-performance-body; 17 | 18 | 19 | organization 20 | "Broadband Forum 21 | Common YANG Work Area"; 22 | 23 | contact 24 | "Comments or questions about this Broadband Forum YANG module 25 | should be directed to . 26 | 27 | Editor: Marcos Martinez, Marvell Semiconductor Inc. 28 | 29 | PS Leader: Joey Boyd, ADTRAN 30 | 31 | PS Leader: Ken Kerpez, ASSIA 32 | 33 | WA Director: Joey Boyd, ADTRAN 34 | 35 | WA Director: Sven Ooghe, Nokia"; 36 | 37 | description 38 | "This module contains a collection of YANG definitions for 39 | managing Vector of Profiles (VoP) on G.hn interfaces. 40 | 41 | Copyright (c) 2018, Broadband Forum 42 | 43 | Redistribution and use in source and binary forms, with or 44 | without modification, are permitted provided that the following 45 | conditions are met: 46 | 47 | 1. Redistributions of source code must retain the above copyright 48 | notice, this list of conditions and the following disclaimer. 49 | 50 | 2. Redistributions in binary form must reproduce the above 51 | copyright notice, this list of conditions and the following 52 | disclaimer in the documentation and/or other materials 53 | provided with the distribution. 54 | 55 | 3. Neither the name of the copyright holder nor the names of its 56 | contributors may be used to endorse or promote products 57 | derived from this software without specific prior written 58 | permission. 59 | 60 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 61 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 62 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 63 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 64 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 65 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 66 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 67 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 68 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 69 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 70 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 71 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 72 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 73 | 74 | The above license is used as a license under copyright only. 75 | Please reference the Forum IPR Policy for patent licensing terms 76 | . 77 | 78 | Any moral rights which are necessary to exercise under the above 79 | license grant are also deemed granted under this license. 80 | 81 | This version of this YANG module is part of TR-374; see 82 | the TR itself for full legal notices."; 83 | 84 | revision 2018-07-13 { 85 | description 86 | "Initial revision. 87 | * Approval Date: 2018-06-04. 88 | * Publication Date: see revision date above."; 89 | reference 90 | "TR-374: Yang Modules for Management of G.hn Systems in FTTdp 91 | Architecture "; 93 | } 94 | 95 | augment '/if:interfaces-state/if:interface/bbf-ghn:ghn-interface/' 96 | + 'bbf-ghn:node/node' { 97 | description 98 | "Data nodes for the performance status parameters of G.hn 99 | nodes."; 100 | 101 | uses node-performance; 102 | } 103 | 104 | augment '/if:interfaces-state/if:interface/bbf-ghn:ghn-interface/' 105 | + 'bbf-ghn:node/bbf-ghn:link' { 106 | description 107 | "Data nodes for the performance status parameters of 108 | G.hn links."; 109 | 110 | uses link-performance; 111 | } 112 | } 113 | -------------------------------------------------------------------------------- /standard/interface/bbf-ghn-scheduling-profile-body.yang: -------------------------------------------------------------------------------- 1 | submodule bbf-ghn-scheduling-profile-body { 2 | yang-version 1.1; 3 | belongs-to bbf-ghn { 4 | prefix bbf-ghn; 5 | } 6 | 7 | include bbf-ghn-types; 8 | 9 | organization 10 | "Broadband Forum 11 | Common YANG Work Area"; 12 | 13 | contact 14 | "Comments or questions about this Broadband Forum YANG module 15 | should be directed to . 16 | 17 | Editor: Marcos Martinez, Marvell Semiconductor Inc. 18 | 19 | PS Leader: Joey Boyd, ADTRAN 20 | 21 | PS Leader: Ken Kerpez, ASSIA 22 | 23 | WA Director: Joey Boyd, ADTRAN 24 | 25 | WA Director: Sven Ooghe, Nokia"; 26 | 27 | description 28 | "This module contains a collection of YANG definitions for 29 | managing scheduling profiles. 30 | 31 | Copyright (c) 2018, Broadband Forum 32 | 33 | Redistribution and use in source and binary forms, with or 34 | without modification, are permitted provided that the following 35 | conditions are met: 36 | 37 | 1. Redistributions of source code must retain the above copyright 38 | notice, this list of conditions and the following disclaimer. 39 | 40 | 2. Redistributions in binary form must reproduce the above 41 | copyright notice, this list of conditions and the following 42 | disclaimer in the documentation and/or other materials 43 | provided with the distribution. 44 | 45 | 3. Neither the name of the copyright holder nor the names of its 46 | contributors may be used to endorse or promote products 47 | derived from this software without specific prior written 48 | permission. 49 | 50 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 51 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 52 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 53 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 54 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 55 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 56 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 57 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 58 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 59 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 60 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 61 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 62 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 63 | 64 | The above license is used as a license under copyright only. 65 | Please reference the Forum IPR Policy for patent licensing terms 66 | . 67 | 68 | Any moral rights which are necessary to exercise under the above 69 | license grant are also deemed granted under this license. 70 | 71 | This version of this YANG module is part of TR-374; see 72 | the TR itself for full legal notices."; 73 | 74 | revision 2018-07-13 { 75 | description 76 | "Initial revision. 77 | * Approval Date: 2018-06-04. 78 | * Publication Date: see revision date above."; 79 | reference 80 | "TR-374: Yang Modules for Management of G.hn Systems in FTTdp 81 | Architecture "; 83 | } 84 | 85 | grouping scheduling-parameters-group { 86 | description 87 | "Scheduling configuration parameters."; 88 | 89 | leaf mac-cycle-duration { 90 | type bbf-ghn:cycle-duration; 91 | default "40"; 92 | description 93 | "Medium Access Control (MAC) cycle duration."; 94 | reference 95 | "ITU-T G.9961 clause 8.2.2"; 96 | } 97 | 98 | leaf split-ratio { 99 | type uint8 { 100 | range "0..100"; 101 | } 102 | units "%"; 103 | default "50"; 104 | description 105 | "Split ratio of the DS/US system. This figure represents 106 | the percentage of the time allocated to DS. The percentage 107 | of the time allocated to US is 100 minus this number."; 108 | } 109 | 110 | leaf topology-update-interval { 111 | type uint8; 112 | units "0.1s"; 113 | description 114 | "Topology update interval for the nodes of a G.hn domain"; 115 | reference 116 | "ITU-T G.9961 clause 8.8.5.8.1"; 117 | } 118 | } 119 | 120 | grouping scheduling-profile-group { 121 | description 122 | "Defines the contents of a scheduling Profile."; 123 | 124 | uses scheduling-parameters-group; 125 | } 126 | } 127 | -------------------------------------------------------------------------------- /standard/interface/bbf-ghn.yang: -------------------------------------------------------------------------------- 1 | module bbf-ghn { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-ghn"; 4 | prefix bbf-ghn; 5 | 6 | include bbf-ghn-base; 7 | include bbf-ghn-pointers; 8 | 9 | /* types */ 10 | include bbf-ghn-types; 11 | include bbf-ghn-perf-types; 12 | 13 | /* Node Profiles */ 14 | include bbf-ghn-node-profiles; 15 | include bbf-ghn-node-id-profile-body; 16 | 17 | /* domain Profiles */ 18 | include bbf-ghn-domain-profiles; 19 | include bbf-ghn-scheduling-profile-body; 20 | include bbf-ghn-security-profile-body; 21 | include bbf-ghn-dba-profile-body; 22 | include bbf-ghn-domain-id-profile-body; 23 | 24 | /* Link Profiles */ 25 | include bbf-ghn-link-profiles; 26 | include bbf-ghn-line-spectrum-profile-body; 27 | include bbf-ghn-channel-estimation-profile-body; 28 | 29 | /* interface state */ 30 | include bbf-ghn-domain-state; 31 | include bbf-ghn-domain-status-body; 32 | include bbf-ghn-local-node-info; 33 | include bbf-ghn-local-node-info-body; 34 | include bbf-ghn-node-state; 35 | include bbf-ghn-node-inventory-body; 36 | include bbf-ghn-node-status-body; 37 | include bbf-ghn-link-state; 38 | include bbf-ghn-link-status-body; 39 | 40 | /* Performance */ 41 | include bbf-ghn-performance-management; 42 | include bbf-ghn-node-performance-body; 43 | include bbf-ghn-link-performance-body; 44 | 45 | organization 46 | "Broadband Forum 47 | Common YANG Work Area"; 48 | 49 | contact 50 | "Comments or questions about this Broadband Forum YANG module 51 | should be directed to . 52 | 53 | Editor: Marcos Martinez, Marvell Semiconductor Inc. 54 | 55 | PS Leader: Joey Boyd, ADTRAN 56 | 57 | PS Leader: Ken Kerpez, ASSIA 58 | 59 | WA Director: Joey Boyd, ADTRAN 60 | 61 | WA Director: Sven Ooghe, Nokia"; 62 | 63 | description 64 | "An experimental YANG module supporting Vector of Profiles 65 | for G.hn lines. 66 | 67 | Copyright (c) 2018, Broadband Forum 68 | 69 | Redistribution and use in source and binary forms, with or 70 | without modification, are permitted provided that the following 71 | conditions are met: 72 | 73 | 1. Redistributions of source code must retain the above copyright 74 | notice, this list of conditions and the following disclaimer. 75 | 76 | 2. Redistributions in binary form must reproduce the above 77 | copyright notice, this list of conditions and the following 78 | disclaimer in the documentation and/or other materials 79 | provided with the distribution. 80 | 81 | 3. Neither the name of the copyright holder nor the names of its 82 | contributors may be used to endorse or promote products 83 | derived from this software without specific prior written 84 | permission. 85 | 86 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 87 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 88 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 89 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 90 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 91 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 92 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 93 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 94 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 95 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 96 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 97 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 98 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 99 | 100 | The above license is used as a license under copyright only. 101 | Please reference the Forum IPR Policy for patent licensing terms 102 | . 103 | 104 | Any moral rights which are necessary to exercise under the above 105 | license grant are also deemed granted under this license. 106 | 107 | This version of this YANG module is part of TR-374; see 108 | the TR itself for full legal notices."; 109 | 110 | revision 2018-07-13 { 111 | description 112 | "Initial revision. 113 | * Approval Date: 2018-06-04. 114 | * Publication Date: see revision date above."; 115 | reference 116 | "TR-374: Yang Modules for Management of G.hn Systems in FTTdp 117 | Architecture "; 119 | } 120 | } 121 | -------------------------------------------------------------------------------- /standard/interface/bbf-hardware-types-xpon.yang: -------------------------------------------------------------------------------- 1 | module bbf-hardware-types-xpon { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-hardware-types-xpon"; 4 | prefix bbf-hwt-xpon; 5 | 6 | import bbf-hardware-types { 7 | prefix bbf-hwt; 8 | } 9 | 10 | organization 11 | "Broadband Forum 12 | Fiber Access Networks Work Area"; 13 | contact 14 | "Comments or questions about this Broadband Forum YANG module 15 | should be directed to . 16 | 17 | Editor: Robert Peschi, Nokia 18 | 19 | PS Leader: Joey Boyd, Adtran 20 | 21 | WA Director: Marta Seda, Calix"; 22 | description 23 | "This module contains a collection of YANG definitions for 24 | supporting the Broadband Forum requirements on management of 25 | ITU-T Passive Optical Network (PON) interfaces as defined in 26 | ITU-T G.984.x, G.987.x, ITU-T G.989.x and ITU-T G.9807.x. As 27 | such, this module is specific to access network equipment (e.g., 28 | BBF-specified Access Nodes and FTTdp DPUs). 29 | 30 | Specifically, this module defines specialization of transceiver 31 | links per xPON types. 32 | 33 | Copyright (c) 2018-2024, Broadband Forum 34 | 35 | Redistribution and use in source and binary forms, with or 36 | without modification, are permitted provided that the following 37 | conditions are met: 38 | 39 | 1. Redistributions of source code must retain the above copyright 40 | notice, this list of conditions and the following disclaimer. 41 | 42 | 2. Redistributions in binary form must reproduce the above 43 | copyright notice, this list of conditions and the following 44 | disclaimer in the documentation and/or other materials 45 | provided with the distribution. 46 | 47 | 3. Neither the name of the copyright holder nor the names of its 48 | contributors may be used to endorse or promote products 49 | derived from this software without specific prior written 50 | permission. 51 | 52 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 53 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 54 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 55 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 56 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 57 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 58 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 59 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 60 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 61 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 62 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 63 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 64 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 65 | 66 | The above license is used as a license under copyright only. 67 | Please reference the Forum IPR Policy for patent licensing terms 68 | . 69 | 70 | Any moral rights which are necessary to exercise under the above 71 | license grant are also deemed granted under this license. 72 | 73 | This version of this YANG module is part of TR-385i3; see 74 | the TR itself for full legal notices."; 75 | 76 | revision 2024-04-23 { 77 | description 78 | "Issue 3. 79 | * Approval Date: 2024-04-23. 80 | * Publication Date: 2024-04-23."; 81 | reference 82 | "TR-385i3: YANG Modules for PON Management 83 | "; 85 | } 86 | 87 | identity transceiver-link-gpon { 88 | base bbf-hwt:transceiver-link; 89 | description 90 | "A transceiver link that terminates a G-PON optical signal."; 91 | } 92 | 93 | identity transceiver-link-xgs { 94 | base bbf-hwt:transceiver-link; 95 | description 96 | "A transceiver link that terminates an XGS-PON optical 97 | signal."; 98 | } 99 | 100 | identity transceiver-link-twentyfivegspon { 101 | base bbf-hwt:transceiver-link; 102 | description 103 | "A transceiver link that terminates a 25GS-PON optical 104 | signal."; 105 | } 106 | } 107 | -------------------------------------------------------------------------------- /standard/interface/bbf-vlan-sub-interface-profile-usage.yang: -------------------------------------------------------------------------------- 1 | module bbf-vlan-sub-interface-profile-usage { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-vlan-sub-interface-profile-usage"; 4 | prefix bbf-vsi-prof-usg; 5 | 6 | import bbf-vlan-sub-interface-profiles { 7 | prefix bbf-vsi-prof; 8 | } 9 | import bbf-interface-usage { 10 | prefix bbf-if-usg; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | Common YANG Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Nick Hancock, Adtran 21 | 22 | Editor: Ludwig Pauwels, Nokia 23 | 24 | PS Leader: Joey Boyd, Adtran 25 | 26 | WA Director: Joey Boyd, Adtran 27 | 28 | WA Director: Sven Ooghe, Nokia"; 29 | description 30 | "This module contains a collection of YANG definitions for 31 | supporting the Broadband Forum requirements on the management of 32 | sub-interfaces as applicable to access network equipment. As 33 | such, this module is specific to access network equipment (e.g., 34 | BBF-specified Access Nodes and FTTdp DPUs). 35 | 36 | Specifically, this module extends the VLAN sub-interface profile 37 | with interface usage data nodes. 38 | 39 | Copyright (c) 2017-2023, Broadband Forum 40 | 41 | Redistribution and use in source and binary forms, with or 42 | without modification, are permitted provided that the following 43 | conditions are met: 44 | 45 | 1. Redistributions of source code must retain the above copyright 46 | notice, this list of conditions and the following disclaimer. 47 | 48 | 2. Redistributions in binary form must reproduce the above 49 | copyright notice, this list of conditions and the following 50 | disclaimer in the documentation and/or other materials 51 | provided with the distribution. 52 | 53 | 3. Neither the name of the copyright holder nor the names of its 54 | contributors may be used to endorse or promote products 55 | derived from this software without specific prior written 56 | permission. 57 | 58 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 59 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 60 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 61 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 62 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 63 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 64 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 65 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 66 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 67 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 68 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 69 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 70 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 71 | 72 | The above license is used as a license under copyright only. 73 | Please reference the Forum IPR Policy for patent licensing terms 74 | . 75 | 76 | Any moral rights which are necessary to exercise under the above 77 | license grant are also deemed granted under this license. 78 | 79 | This version of this YANG module is part of TR-383a6; see 80 | the TR itself for full legal notices."; 81 | 82 | revision 2023-03-07 { 83 | description 84 | "Amendment 6. 85 | * Approval Date: 2023-03-07. 86 | * Publication Date: 2023-03-07."; 87 | reference 88 | "TR-383a6: Common YANG Modules 89 | "; 91 | } 92 | 93 | augment "/bbf-vsi-prof:vsi-profiles" 94 | + "/bbf-vsi-prof:vsi-profile" { 95 | description 96 | "Augments the VLAN sub-interface profile with interface usage 97 | data nodes."; 98 | container interface-usage { 99 | presence 100 | "Presence of this container indicates the interface usage to 101 | be assigned to interfaces referencing this profile."; 102 | description 103 | "Provides an interface usage."; 104 | uses bbf-if-usg:interface-usage { 105 | refine "interface-usage" { 106 | mandatory true; 107 | } 108 | } 109 | } 110 | } 111 | } 112 | -------------------------------------------------------------------------------- /standard/interface/bbf-xpongemtcont-qos.yang: -------------------------------------------------------------------------------- 1 | module bbf-xpongemtcont-qos { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-xpongemtcont-qos"; 4 | prefix bbf-xpongemtcont-qos; 5 | 6 | import bbf-xpongemtcont { 7 | prefix bbf-xpongemtcont; 8 | } 9 | import bbf-qos-traffic-mngt { 10 | prefix bbf-qos-tm; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | Fiber Access Networks Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Joey Boyd, ADTRAN 21 | 22 | Editor: Igor Ternovsky, Broadcom 23 | 24 | Editor: Robert Peschi, Nokia 25 | 26 | WA Director: Marta Seda, Calix 27 | 28 | WA Director: Samuel Chen, Broadcom"; 29 | description 30 | "This module contains a collection of YANG definitions for 31 | supporting the Broadband Forum requirements on management of 32 | ITU-T Passive Optical Network (PON) interfaces as defined in 33 | ITU-T G.984.x, G.987.x, ITU-T G.989.x and ITU-T G.9807.x. As 34 | such, this module is specific to access network equipment (e.g., 35 | BBF-specified Access Nodes and FTTdp DPUs). 36 | 37 | Specifically, this module defines the management of Quality of 38 | Service (QoS) as it relates to Transmission Containers (T-CONT). 39 | 40 | Copyright (c) 2018-2020, Broadband Forum 41 | 42 | Redistribution and use in source and binary forms, with or 43 | without modification, are permitted provided that the following 44 | conditions are met: 45 | 46 | 1. Redistributions of source code must retain the above copyright 47 | notice, this list of conditions and the following disclaimer. 48 | 49 | 2. Redistributions in binary form must reproduce the above 50 | copyright notice, this list of conditions and the following 51 | disclaimer in the documentation and/or other materials 52 | provided with the distribution. 53 | 54 | 3. Neither the name of the copyright holder nor the names of its 55 | contributors may be used to endorse or promote products 56 | derived from this software without specific prior written 57 | permission. 58 | 59 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 60 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 61 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 62 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 63 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 64 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 65 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 66 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 67 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 68 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 69 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 70 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 71 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 72 | 73 | The above license is used as a license under copyright only. 74 | Please reference the Forum IPR Policy for patent licensing terms 75 | . 76 | 77 | Any moral rights which are necessary to exercise under the above 78 | license grant are also deemed granted under this license. 79 | 80 | This version of this YANG module is part of TR-385i2; see 81 | the TR itself for full legal notices."; 82 | 83 | revision 2020-10-13 { 84 | description 85 | "Issue 2. 86 | * Approval Date: 2020-10-13. 87 | * Publication Date: 2020-10-13."; 88 | reference 89 | "TR-385i2: ITU-T PON YANG Modules 90 | "; 92 | } 93 | revision 2019-02-25 { 94 | description 95 | "Initial revision. 96 | * Approval Date: 2019-02-25. 97 | * Publication Date: 2019-02-25."; 98 | reference 99 | "TR-385: ITU-T PON YANG Modules 100 | "; 102 | } 103 | 104 | augment "/bbf-xpongemtcont:xpongemtcont/bbf-xpongemtcont:tconts/" 105 | + "bbf-xpongemtcont:tcont" { 106 | description 107 | "Augment the Transmission Container (T-CONT) configuration with 108 | Quality of Service (QoS) configuration."; 109 | uses bbf-qos-tm:tm-root; 110 | } 111 | } 112 | -------------------------------------------------------------------------------- /standard/networking/bbf-vlan-sub-interface-profile-qos.yang: -------------------------------------------------------------------------------- 1 | module bbf-vlan-sub-interface-profile-qos { 2 | yang-version 1.1; 3 | namespace "urn:bbf:yang:bbf-vlan-sub-interface-profile-qos"; 4 | prefix bbf-vsi-prof-qos; 5 | 6 | import bbf-vlan-sub-interface-profiles { 7 | prefix bbf-vsi-prof; 8 | } 9 | import bbf-qos-policies { 10 | prefix bbf-qos-pol; 11 | } 12 | 13 | organization 14 | "Broadband Forum 15 | Common YANG Work Area"; 16 | contact 17 | "Comments or questions about this Broadband Forum YANG module 18 | should be directed to . 19 | 20 | Editor: Nick Hancock, Adtran 21 | 22 | Editor: Ludwig Pauwels, Nokia 23 | 24 | PS Leader: Joey Boyd, Adtran 25 | 26 | WA Director: Joey Boyd, Adtran 27 | 28 | WA Director: Sven Ooghe, Nokia"; 29 | description 30 | "This module contains a collection of YANG definitions for 31 | supporting the Broadband Forum requirements on the management of 32 | sub-interfaces as applicable to access network equipment. As 33 | such, this module is specific to access network equipment (e.g., 34 | BBF-specified Access Nodes and FTTdp DPUs). 35 | 36 | Specifically, this module extends the VLAN sub-interface profile 37 | with QoS data nodes. 38 | 39 | Copyright (c) 2017-2023, Broadband Forum 40 | 41 | Redistribution and use in source and binary forms, with or 42 | without modification, are permitted provided that the following 43 | conditions are met: 44 | 45 | 1. Redistributions of source code must retain the above copyright 46 | notice, this list of conditions and the following disclaimer. 47 | 48 | 2. Redistributions in binary form must reproduce the above 49 | copyright notice, this list of conditions and the following 50 | disclaimer in the documentation and/or other materials 51 | provided with the distribution. 52 | 53 | 3. Neither the name of the copyright holder nor the names of its 54 | contributors may be used to endorse or promote products 55 | derived from this software without specific prior written 56 | permission. 57 | 58 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 59 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, 60 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 61 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 62 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR 63 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 64 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 65 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 66 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 67 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 68 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 69 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 70 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 71 | 72 | The above license is used as a license under copyright only. 73 | Please reference the Forum IPR Policy for patent licensing terms 74 | . 75 | 76 | Any moral rights which are necessary to exercise under the above 77 | license grant are also deemed granted under this license. 78 | 79 | This version of this YANG module is part of TR-383a6; see 80 | the TR itself for full legal notices."; 81 | 82 | revision 2023-03-07 { 83 | description 84 | "Amendment 6. 85 | * Approval Date: 2023-03-07. 86 | * Publication Date: 2023-03-07."; 87 | reference 88 | "TR-383a6: Common YANG Modules 89 | "; 91 | } 92 | 93 | augment "/bbf-vsi-prof:vsi-profiles" 94 | + "/bbf-vsi-prof:vsi-profile" { 95 | description 96 | "Augments the VLAN sub-interface profile with QoS data nodes."; 97 | container qos { 98 | presence 99 | "Presence of this container indicates QoS functionality is 100 | enabled."; 101 | description 102 | "QoS configuration parameters."; 103 | uses bbf-qos-pol:qos-policy-profiles; 104 | } 105 | } 106 | } 107 | --------------------------------------------------------------------------------