{ "modules": [ { "module": "/home/petejone/yang/git_802_3/yang_main/Modules/Approved/ieee802-ethernet-interface.yang", "module_sha256": "3093150267a0b1545f9f75e322ed5ff920665b275aede8e107b8f2fe9311c102", "findings": [ { "rule": "disabled-negotiation-status", "line": 221, "node": "ethernet/auto-negotiation/negotiation-status", "section": "30.6.1.1.4", "section_title": "aAutoNegAutoConfig", "printed_page_start": null, "summary": "Disabled negotiation cannot report no-negotiation", "detail": "The when condition hides this leaf when enable is false, although its no-negotiation enum describes a disabled function.", "rfc9907": [] }, { "rule": "parallel-detect-mapping", "line": 221, "node": "ethernet/auto-negotiation/negotiation-status", "section": "30.6.1.1.4", "section_title": "aAutoNegAutoConfig", "printed_page_start": null, "summary": "Parallel detect failure has no explicit mapping", "detail": "The referenced attribute distinguishes parallel detect failure; the leaf does not name that condition in an enum. Review the mapping to failed.", "rfc9907": [] }, { "rule": "pmd-mau-mapping", "line": 271, "node": "ethernet/pmd-type", "section": "30.5.1.1.2", "section_title": "aMAUType", "printed_page_start": null, "summary": "PMD to MAU mapping needs review", "detail": "The referenced MAU enumeration includes state and complete MAU distinctions. Confirm how these map to the imported PMD identities.", "rfc9907": [ { "id": "rfc9907-4.11.1-1", "section": "4.11.1", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.11.1", "text": "If the set of values is fixed and the data type contents are controlled by a single naming authority (e.g., IANA), then an \"enumeration\" data type SHOULD be used." }, { "id": "rfc9907-4.11.1-3", "section": "4.11.1", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.11.1", "text": "If distributed extensibility or hierarchical organization of enumerated values is required, then the \"identityref\" data type SHOULD be used instead of an \"enumeration\" or other built-in type." } ] }, { "rule": "duplex-config-state", "line": 282, "node": "ethernet/duplex", "section": "30.3.1.1.32", "section_title": "aDuplexStatus", "printed_page_start": null, "summary": "Operational duplex is modeled as configuration", "detail": "The description calls this operational state, but the leaf is writable by default. Clause 30 specifies both GET and SET behavior; clarify the configuration and state mapping.", "rfc9907": [ { "id": "rfc9907-4.23.1-1", "section": "4.23.1", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.23.1", "text": "If possible, operational state SHOULD be combined with its associated configuration data. This prevents duplication of key leafs and ancestor nodes. It also prevents race conditions for retrieval of dynamic entries and allows configuration and operational state to be retrieved together with minimal message overhead." } ] }, { "rule": "receive-direction", "line": 333, "node": "ethernet/flow-control/pause/statistics/in-frames-pause", "section": "30.3.4.3", "section_title": "aPAUSEMACCtrlFramesReceived", "printed_page_start": null, "summary": "Receive counter describes transmission", "detail": "The node and referenced attribute identify received events, while the node description says transmitted.", "rfc9907": [] }, { "rule": "unknown-frame-length", "line": 429, "node": "ethernet/max-frame-length", "section": "30.3.1.1.37", "section_title": "aMaxFrameLength", "printed_page_start": null, "summary": "Frame length has no explicit unknown value", "detail": "The numeric leaf has no documented representation for the unknown value in the referenced enumeration.", "rfc9907": [] }, { "rule": "extension-read-only", "line": 439, "node": "ethernet/mac-control-extension-control", "section": "30.3.8.3", "section_title": "aEXTENSIONMACCtrlStatus", "printed_page_start": null, "summary": "Extension status exposes only read access", "detail": "The referenced attribute supports reading and setting; this leaf is config false. Confirm whether the restricted mapping is intentional.", "rfc9907": [] }, { "rule": "receive-direction", "line": 534, "node": "ethernet/ethernet-pause/statistics/in-frames-pause", "section": "30.3.4.3", "section_title": "aPAUSEMACCtrlFramesReceived", "printed_page_start": null, "summary": "Receive counter describes transmission", "detail": "The node and referenced attribute identify received events, while the node description says transmitted.", "rfc9907": [] }, { "rule": "symbol-event-count", "line": 793, "node": "ethernet/statistics/phy/in-error-symbol", "section": "30.3.2.1.5", "section_title": "aSymbolErrorDuringCarrier", "printed_page_start": null, "summary": "Symbol-error summary suggests counting individual errors", "detail": "The referenced attribute counts qualifying carrier events with one or more errors, at most once per valid event and subject to collision conditions.", "rfc9907": [] } ], "references": [ { "line": 142, "node": "duplex-type", "kind": "typedef", "section": "30.3.1.1.32", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aDuplexStatus", "printed_page_start": null }, { "line": 256, "node": "negotiation-status", "kind": "leaf", "section": "30.6.1.1.4", "source": "ieee8023", "source_standard": "IEEE 802.3", "status": "found", "section_title": "aAutoNegAutoConfig", "printed_page_start": null }, { "line": 268, "node": "phy-type", "kind": "leaf", "section": "30.3.2.1.2", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aPhyType", "printed_page_start": null }, { "line": 279, "node": "pmd-type", "kind": "leaf", "section": "30.5.1.1.2", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aMAUType", "printed_page_start": null }, { "line": 286, "node": "duplex", "kind": "leaf", "section": "30.3.1.1.32", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aDuplexStatus", "printed_page_start": null }, { "line": 339, "node": "in-frames-pause", "kind": "leaf", "section": "30.3.4.3", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aPAUSEMACCtrlFramesReceived", "printed_page_start": null }, { "line": 349, "node": "out-frames-pause", "kind": "leaf", "section": "30.3.4.2", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aPAUSEMACCtrlFramesTransmitted", "printed_page_start": null }, { "line": 436, "node": "max-frame-length", "kind": "leaf", "section": "30.3.1.1.37", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aMaxFrameLength", "printed_page_start": null }, { "line": 446, "node": "mac-control-extension-control", "kind": "leaf", "section": "30.3.8.3", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aEXTENSIONMACCtrlStatus", "printed_page_start": null }, { "line": 460, "node": "frame-limit-slow-protocol", "kind": "leaf", "section": "30.3.1.1.38", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aSlowProtocolFrameLimit", "printed_page_start": null }, { "line": 485, "node": "ethernet-pause", "kind": "container", "section": "30.3.4", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "PAUSE entity managed object class", "printed_page_start": null }, { "line": 526, "node": "pfc-enable-status", "kind": "leaf", "section": "30.3.3.6", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aPFCEnableStatus", "printed_page_start": null }, { "line": 540, "node": "in-frames-pause", "kind": "leaf", "section": "30.3.4.3", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aPAUSEMACCtrlFramesReceived", "printed_page_start": null }, { "line": 550, "node": "out-frames-pause", "kind": "leaf", "section": "30.3.4.2", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aPAUSEMACCtrlFramesTransmitted", "printed_page_start": null }, { "line": 627, "node": "in-frames", "kind": "leaf", "section": "30.3.1.1.5", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aFramesReceivedOK", "printed_page_start": null }, { "line": 643, "node": "in-multicast-frames", "kind": "leaf", "section": "30.3.1.1.21", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aMulticastFramesReceivedOK", "printed_page_start": null }, { "line": 660, "node": "in-broadcast-frames", "kind": "leaf", "section": "30.3.1.1.22", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aBroadcastFramesReceivedOK", "printed_page_start": null }, { "line": 677, "node": "in-error-fcs-frames", "kind": "leaf", "section": "30.3.1.1.6", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aFrameCheckSequenceErrors", "printed_page_start": null }, { "line": 677, "node": "in-error-fcs-frames", "kind": "leaf", "section": "30.3.1.1.7", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aAlignmentErrors", "printed_page_start": null }, { "line": 708, "node": "in-error-oversize-frames", "kind": "leaf", "section": "30.3.1.1.25", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aFrameTooLongErrors", "printed_page_start": null }, { "line": 731, "node": "in-error-mac-internal-frames", "kind": "leaf", "section": "30.3.1.1.15", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aFramesLostDueToIntMACRcvError", "printed_page_start": null }, { "line": 742, "node": "out-frames", "kind": "leaf", "section": "30.3.1.1.2", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aFramesTransmittedOK", "printed_page_start": null }, { "line": 754, "node": "out-multicast-frames", "kind": "leaf", "section": "30.3.1.1.18", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aMulticastFramesXmittedOK", "printed_page_start": null }, { "line": 767, "node": "out-broadcast-frames", "kind": "leaf", "section": "30.3.1.1.19", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aBroadcastFramesXmittedOK", "printed_page_start": null }, { "line": 785, "node": "out-error-mac-internal-frames", "kind": "leaf", "section": "30.3.1.1.12", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aFramesLostDueToIntMACXmitError", "printed_page_start": null }, { "line": 804, "node": "in-error-symbol", "kind": "leaf", "section": "30.3.2.1.5", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aSymbolErrorDuringCarrier", "printed_page_start": null }, { "line": 823, "node": "in-lpi-transitions", "kind": "leaf", "section": "30.3.2.1.11", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aReceiveLPITransitions", "printed_page_start": null }, { "line": 835, "node": "in-lpi-time", "kind": "leaf", "section": "30.3.2.1.9", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aReceiveLPIMicroseconds", "printed_page_start": null }, { "line": 850, "node": "out-lpi-transitions", "kind": "leaf", "section": "30.3.2.1.10", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aTransmitLPITransitions", "printed_page_start": null }, { "line": 862, "node": "out-lpi-time", "kind": "leaf", "section": "30.3.2.1.8", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aTransmitLPIMicroseconds", "printed_page_start": null }, { "line": 884, "node": "in-frames-mac-control-unknown", "kind": "leaf", "section": "30.3.3.5", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aUnsupportedOpcodesReceived", "printed_page_start": null }, { "line": 894, "node": "in-frames-mac-control-extension", "kind": "leaf", "section": "30.3.8.2", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aEXTENSIONMACCtrlFramesReceived", "printed_page_start": null }, { "line": 904, "node": "out-frames-mac-control-extension", "kind": "leaf", "section": "30.3.8.1", "source": "ieee8023", "source_standard": "IEEE Std 802.3", "status": "found", "section_title": "aEXTENSIONMACCtrlFramesTransmitted", "printed_page_start": null } ], "prose_warnings": [ { "source": "clause30_extract", "line": 485, "section": "30.3.4", "statement": "PAUSE entity managed object class", "message": "description: spelling: 'behaviours'" }, { "source": "clause30_extract", "line": 526, "section": "30.3.3.6", "statement": "aPFCEnableStatus", "message": "description: spelling: 'enablement'" }, { "source": "clause30_extract", "line": 643, "section": "30.3.1.1.21", "statement": "aMulticastFramesReceivedOK", "message": "description: spelling: 'nonbroadcast'" } ], "mapping_guidance": [ { "line": 123, "node": "duplex-type", "section": "30.3.1.1.32", "rule": "attribute", "yang_type": "enumeration", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 123, "node": "duplex-type", "section": "30.3.1.1.32", "rule": "syntax-field", "yang_type": "enumeration", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 123, "node": "duplex-type", "section": "30.3.1.1.32", "rule": "behavior-field", "yang_type": "enumeration", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 123, "node": "duplex-type", "section": "30.3.1.1.32", "rule": "enumeration-syntax", "yang_type": "enumeration", "status": "guidance", "preferred_constructs": [ "enumeration", "identityref" ], "guidance": "enumeration or identityref", "context": "Enumeration is a candidate, not an automatic choice; verify extensibility, identifiers, values, and descriptions." }, { "line": 221, "node": "ethernet/auto-negotiation/negotiation-status", "section": "30.6.1.1.4", "rule": "attribute", "yang_type": "enumeration", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 221, "node": "ethernet/auto-negotiation/negotiation-status", "section": "30.6.1.1.4", "rule": "syntax-field", "yang_type": "enumeration", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 221, "node": "ethernet/auto-negotiation/negotiation-status", "section": "30.6.1.1.4", "rule": "behavior-field", "yang_type": "enumeration", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 221, "node": "ethernet/auto-negotiation/negotiation-status", "section": "30.6.1.1.4", "rule": "enumeration-syntax", "yang_type": "enumeration", "status": "guidance", "preferred_constructs": [ "enumeration", "identityref" ], "guidance": "enumeration or identityref", "context": "Enumeration is a candidate, not an automatic choice; verify extensibility, identifiers, values, and descriptions." }, { "line": 260, "node": "ethernet/phy-type", "section": "30.3.2.1.2", "rule": "attribute", "yang_type": "identityref", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 260, "node": "ethernet/phy-type", "section": "30.3.2.1.2", "rule": "syntax-field", "yang_type": "identityref", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 260, "node": "ethernet/phy-type", "section": "30.3.2.1.2", "rule": "behavior-field", "yang_type": "identityref", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 260, "node": "ethernet/phy-type", "section": "30.3.2.1.2", "rule": "access-semantics", "yang_type": "identityref", "status": "guidance", "preferred_constructs": [], "guidance": "assume read-only - state, Read/write - configuration based on definition", "context": "Read/write wording is a review signal. YANG config models configuration versus state, while datastore semantics and access control are separate; read-only wording alone does not prove config false." }, { "line": 271, "node": "ethernet/pmd-type", "section": "30.5.1.1.2", "rule": "attribute", "yang_type": "identityref", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 271, "node": "ethernet/pmd-type", "section": "30.5.1.1.2", "rule": "syntax-field", "yang_type": "identityref", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 271, "node": "ethernet/pmd-type", "section": "30.5.1.1.2", "rule": "behavior-field", "yang_type": "identityref", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 271, "node": "ethernet/pmd-type", "section": "30.5.1.1.2", "rule": "enumeration-syntax", "yang_type": "identityref", "status": "guidance", "preferred_constructs": [ "enumeration", "identityref" ], "guidance": "enumeration or identityref", "context": "Enumeration is a candidate, not an automatic choice; verify extensibility, identifiers, values, and descriptions." }, { "line": 271, "node": "ethernet/pmd-type", "section": "30.5.1.1.2", "rule": "access-semantics", "yang_type": "identityref", "status": "guidance", "preferred_constructs": [], "guidance": "assume read-only - state, Read/write - configuration based on definition", "context": "Read/write wording is a review signal. YANG config models configuration versus state, while datastore semantics and access control are separate; read-only wording alone does not prove config false." }, { "line": 282, "node": "ethernet/duplex", "section": "30.3.1.1.32", "rule": "attribute", "yang_type": "duplex-type", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 282, "node": "ethernet/duplex", "section": "30.3.1.1.32", "rule": "syntax-field", "yang_type": "duplex-type", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 282, "node": "ethernet/duplex", "section": "30.3.1.1.32", "rule": "behavior-field", "yang_type": "duplex-type", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 282, "node": "ethernet/duplex", "section": "30.3.1.1.32", "rule": "enumeration-syntax", "yang_type": "duplex-type", "status": "type_unresolved", "preferred_constructs": [ "enumeration", "identityref" ], "guidance": "enumeration or identityref", "context": "Enumeration is a candidate, not an automatic choice; verify extensibility, identifiers, values, and descriptions." }, { "line": 333, "node": "ethernet/flow-control/pause/statistics/in-frames-pause", "section": "30.3.4.3", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 333, "node": "ethernet/flow-control/pause/statistics/in-frames-pause", "section": "30.3.4.3", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 333, "node": "ethernet/flow-control/pause/statistics/in-frames-pause", "section": "30.3.4.3", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 333, "node": "ethernet/flow-control/pause/statistics/in-frames-pause", "section": "30.3.4.3", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 343, "node": "ethernet/flow-control/pause/statistics/out-frames-pause", "section": "30.3.4.2", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 343, "node": "ethernet/flow-control/pause/statistics/out-frames-pause", "section": "30.3.4.2", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 343, "node": "ethernet/flow-control/pause/statistics/out-frames-pause", "section": "30.3.4.2", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 343, "node": "ethernet/flow-control/pause/statistics/out-frames-pause", "section": "30.3.4.2", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 429, "node": "ethernet/max-frame-length", "section": "30.3.1.1.37", "rule": "attribute", "yang_type": "uint16", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 429, "node": "ethernet/max-frame-length", "section": "30.3.1.1.37", "rule": "syntax-field", "yang_type": "uint16", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 429, "node": "ethernet/max-frame-length", "section": "30.3.1.1.37", "rule": "behavior-field", "yang_type": "uint16", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 429, "node": "ethernet/max-frame-length", "section": "30.3.1.1.37", "rule": "enumeration-syntax", "yang_type": "uint16", "status": "review_mapping", "preferred_constructs": [ "enumeration", "identityref" ], "guidance": "enumeration or identityref", "context": "Enumeration is a candidate, not an automatic choice; verify extensibility, identifiers, values, and descriptions." }, { "line": 439, "node": "ethernet/mac-control-extension-control", "section": "30.3.8.3", "rule": "attribute", "yang_type": "boolean", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 439, "node": "ethernet/mac-control-extension-control", "section": "30.3.8.3", "rule": "syntax-field", "yang_type": "boolean", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 439, "node": "ethernet/mac-control-extension-control", "section": "30.3.8.3", "rule": "behavior-field", "yang_type": "boolean", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 439, "node": "ethernet/mac-control-extension-control", "section": "30.3.8.3", "rule": "enumeration-syntax", "yang_type": "boolean", "status": "review_mapping", "preferred_constructs": [ "enumeration", "identityref" ], "guidance": "enumeration or identityref", "context": "Enumeration is a candidate, not an automatic choice; verify extensibility, identifiers, values, and descriptions." }, { "line": 439, "node": "ethernet/mac-control-extension-control", "section": "30.3.8.3", "rule": "access-semantics", "yang_type": "boolean", "status": "guidance", "preferred_constructs": [], "guidance": "assume read-only - state, Read/write - configuration based on definition", "context": "Read/write wording is a review signal. YANG config models configuration versus state, while datastore semantics and access control are separate; read-only wording alone does not prove config false." }, { "line": 450, "node": "ethernet/frame-limit-slow-protocol", "section": "30.3.1.1.38", "rule": "attribute", "yang_type": "uint64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 450, "node": "ethernet/frame-limit-slow-protocol", "section": "30.3.1.1.38", "rule": "syntax-field", "yang_type": "uint64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 450, "node": "ethernet/frame-limit-slow-protocol", "section": "30.3.1.1.38", "rule": "behavior-field", "yang_type": "uint64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 450, "node": "ethernet/frame-limit-slow-protocol", "section": "30.3.1.1.38", "rule": "integer-syntax", "yang_type": "uint64", "status": "guidance", "preferred_constructs": [], "guidance": null, "context": "Choose signedness, width, range, and any derived type from the actual definition; INTEGER alone does not choose them." }, { "line": 474, "node": "ethernet/ethernet-pause", "section": "30.3.4", "rule": "managed-object-class", "yang_type": null, "status": "guidance", "preferred_constructs": [], "guidance": null, "context": "A class may be represented by a container or a list; instance multiplicity, keys, and placement must be established from the model." }, { "line": 519, "node": "ethernet/ethernet-pause/control-and-status/pfc-enable-status", "section": "30.3.3.6", "rule": "attribute", "yang_type": "boolean", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 519, "node": "ethernet/ethernet-pause/control-and-status/pfc-enable-status", "section": "30.3.3.6", "rule": "syntax-field", "yang_type": "boolean", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 519, "node": "ethernet/ethernet-pause/control-and-status/pfc-enable-status", "section": "30.3.3.6", "rule": "behavior-field", "yang_type": "boolean", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 519, "node": "ethernet/ethernet-pause/control-and-status/pfc-enable-status", "section": "30.3.3.6", "rule": "enumeration-syntax", "yang_type": "boolean", "status": "review_mapping", "preferred_constructs": [ "enumeration", "identityref" ], "guidance": "enumeration or identityref", "context": "Enumeration is a candidate, not an automatic choice; verify extensibility, identifiers, values, and descriptions." }, { "line": 519, "node": "ethernet/ethernet-pause/control-and-status/pfc-enable-status", "section": "30.3.3.6", "rule": "access-semantics", "yang_type": "boolean", "status": "guidance", "preferred_constructs": [], "guidance": "assume read-only - state, Read/write - configuration based on definition", "context": "Read/write wording is a review signal. YANG config models configuration versus state, while datastore semantics and access control are separate; read-only wording alone does not prove config false." }, { "line": 534, "node": "ethernet/ethernet-pause/statistics/in-frames-pause", "section": "30.3.4.3", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 534, "node": "ethernet/ethernet-pause/statistics/in-frames-pause", "section": "30.3.4.3", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 534, "node": "ethernet/ethernet-pause/statistics/in-frames-pause", "section": "30.3.4.3", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 534, "node": "ethernet/ethernet-pause/statistics/in-frames-pause", "section": "30.3.4.3", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 544, "node": "ethernet/ethernet-pause/statistics/out-frames-pause", "section": "30.3.4.2", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 544, "node": "ethernet/ethernet-pause/statistics/out-frames-pause", "section": "30.3.4.2", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 544, "node": "ethernet/ethernet-pause/statistics/out-frames-pause", "section": "30.3.4.2", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 544, "node": "ethernet/ethernet-pause/statistics/out-frames-pause", "section": "30.3.4.2", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 616, "node": "ethernet/statistics/frame/in-frames", "section": "30.3.1.1.5", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 616, "node": "ethernet/statistics/frame/in-frames", "section": "30.3.1.1.5", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 616, "node": "ethernet/statistics/frame/in-frames", "section": "30.3.1.1.5", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 616, "node": "ethernet/statistics/frame/in-frames", "section": "30.3.1.1.5", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 630, "node": "ethernet/statistics/frame/in-multicast-frames", "section": "30.3.1.1.21", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 630, "node": "ethernet/statistics/frame/in-multicast-frames", "section": "30.3.1.1.21", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 630, "node": "ethernet/statistics/frame/in-multicast-frames", "section": "30.3.1.1.21", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 630, "node": "ethernet/statistics/frame/in-multicast-frames", "section": "30.3.1.1.21", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 647, "node": "ethernet/statistics/frame/in-broadcast-frames", "section": "30.3.1.1.22", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 647, "node": "ethernet/statistics/frame/in-broadcast-frames", "section": "30.3.1.1.22", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 647, "node": "ethernet/statistics/frame/in-broadcast-frames", "section": "30.3.1.1.22", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 647, "node": "ethernet/statistics/frame/in-broadcast-frames", "section": "30.3.1.1.22", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 664, "node": "ethernet/statistics/frame/in-error-fcs-frames", "section": "30.3.1.1.6", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 664, "node": "ethernet/statistics/frame/in-error-fcs-frames", "section": "30.3.1.1.6", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 664, "node": "ethernet/statistics/frame/in-error-fcs-frames", "section": "30.3.1.1.6", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 664, "node": "ethernet/statistics/frame/in-error-fcs-frames", "section": "30.3.1.1.6", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 664, "node": "ethernet/statistics/frame/in-error-fcs-frames", "section": "30.3.1.1.7", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 664, "node": "ethernet/statistics/frame/in-error-fcs-frames", "section": "30.3.1.1.7", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 664, "node": "ethernet/statistics/frame/in-error-fcs-frames", "section": "30.3.1.1.7", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 664, "node": "ethernet/statistics/frame/in-error-fcs-frames", "section": "30.3.1.1.7", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 697, "node": "ethernet/statistics/frame/in-error-oversize-frames", "section": "30.3.1.1.25", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 697, "node": "ethernet/statistics/frame/in-error-oversize-frames", "section": "30.3.1.1.25", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 697, "node": "ethernet/statistics/frame/in-error-oversize-frames", "section": "30.3.1.1.25", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 697, "node": "ethernet/statistics/frame/in-error-oversize-frames", "section": "30.3.1.1.25", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 712, "node": "ethernet/statistics/frame/in-error-mac-internal-frames", "section": "30.3.1.1.15", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 712, "node": "ethernet/statistics/frame/in-error-mac-internal-frames", "section": "30.3.1.1.15", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 712, "node": "ethernet/statistics/frame/in-error-mac-internal-frames", "section": "30.3.1.1.15", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 712, "node": "ethernet/statistics/frame/in-error-mac-internal-frames", "section": "30.3.1.1.15", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 735, "node": "ethernet/statistics/frame/out-frames", "section": "30.3.1.1.2", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 735, "node": "ethernet/statistics/frame/out-frames", "section": "30.3.1.1.2", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 735, "node": "ethernet/statistics/frame/out-frames", "section": "30.3.1.1.2", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 735, "node": "ethernet/statistics/frame/out-frames", "section": "30.3.1.1.2", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 745, "node": "ethernet/statistics/frame/out-multicast-frames", "section": "30.3.1.1.18", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 745, "node": "ethernet/statistics/frame/out-multicast-frames", "section": "30.3.1.1.18", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 745, "node": "ethernet/statistics/frame/out-multicast-frames", "section": "30.3.1.1.18", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 745, "node": "ethernet/statistics/frame/out-multicast-frames", "section": "30.3.1.1.18", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 758, "node": "ethernet/statistics/frame/out-broadcast-frames", "section": "30.3.1.1.19", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 758, "node": "ethernet/statistics/frame/out-broadcast-frames", "section": "30.3.1.1.19", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 758, "node": "ethernet/statistics/frame/out-broadcast-frames", "section": "30.3.1.1.19", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 758, "node": "ethernet/statistics/frame/out-broadcast-frames", "section": "30.3.1.1.19", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 771, "node": "ethernet/statistics/frame/out-error-mac-internal-frames", "section": "30.3.1.1.12", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 771, "node": "ethernet/statistics/frame/out-error-mac-internal-frames", "section": "30.3.1.1.12", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 771, "node": "ethernet/statistics/frame/out-error-mac-internal-frames", "section": "30.3.1.1.12", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 771, "node": "ethernet/statistics/frame/out-error-mac-internal-frames", "section": "30.3.1.1.12", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 793, "node": "ethernet/statistics/phy/in-error-symbol", "section": "30.3.2.1.5", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 793, "node": "ethernet/statistics/phy/in-error-symbol", "section": "30.3.2.1.5", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 793, "node": "ethernet/statistics/phy/in-error-symbol", "section": "30.3.2.1.5", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 793, "node": "ethernet/statistics/phy/in-error-symbol", "section": "30.3.2.1.5", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 812, "node": "ethernet/statistics/phy/lpi/in-lpi-transitions", "section": "30.3.2.1.11", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 812, "node": "ethernet/statistics/phy/lpi/in-lpi-transitions", "section": "30.3.2.1.11", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 812, "node": "ethernet/statistics/phy/lpi/in-lpi-transitions", "section": "30.3.2.1.11", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 812, "node": "ethernet/statistics/phy/lpi/in-lpi-transitions", "section": "30.3.2.1.11", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 827, "node": "ethernet/statistics/phy/lpi/in-lpi-time", "section": "30.3.2.1.9", "rule": "attribute", "yang_type": "decimal64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 827, "node": "ethernet/statistics/phy/lpi/in-lpi-time", "section": "30.3.2.1.9", "rule": "syntax-field", "yang_type": "decimal64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 827, "node": "ethernet/statistics/phy/lpi/in-lpi-time", "section": "30.3.2.1.9", "rule": "behavior-field", "yang_type": "decimal64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 827, "node": "ethernet/statistics/phy/lpi/in-lpi-time", "section": "30.3.2.1.9", "rule": "counter-syntax", "yang_type": "decimal64", "status": "review_mapping", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 839, "node": "ethernet/statistics/phy/lpi/out-lpi-transitions", "section": "30.3.2.1.10", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 839, "node": "ethernet/statistics/phy/lpi/out-lpi-transitions", "section": "30.3.2.1.10", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 839, "node": "ethernet/statistics/phy/lpi/out-lpi-transitions", "section": "30.3.2.1.10", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 839, "node": "ethernet/statistics/phy/lpi/out-lpi-transitions", "section": "30.3.2.1.10", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 854, "node": "ethernet/statistics/phy/lpi/out-lpi-time", "section": "30.3.2.1.8", "rule": "attribute", "yang_type": "decimal64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 854, "node": "ethernet/statistics/phy/lpi/out-lpi-time", "section": "30.3.2.1.8", "rule": "syntax-field", "yang_type": "decimal64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 854, "node": "ethernet/statistics/phy/lpi/out-lpi-time", "section": "30.3.2.1.8", "rule": "behavior-field", "yang_type": "decimal64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 854, "node": "ethernet/statistics/phy/lpi/out-lpi-time", "section": "30.3.2.1.8", "rule": "counter-syntax", "yang_type": "decimal64", "status": "review_mapping", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 874, "node": "ethernet/statistics/mac-control/in-frames-mac-control-unknown", "section": "30.3.3.5", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 874, "node": "ethernet/statistics/mac-control/in-frames-mac-control-unknown", "section": "30.3.3.5", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 874, "node": "ethernet/statistics/mac-control/in-frames-mac-control-unknown", "section": "30.3.3.5", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 874, "node": "ethernet/statistics/mac-control/in-frames-mac-control-unknown", "section": "30.3.3.5", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 888, "node": "ethernet/statistics/mac-control/in-frames-mac-control-extension", "section": "30.3.8.2", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 888, "node": "ethernet/statistics/mac-control/in-frames-mac-control-extension", "section": "30.3.8.2", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 888, "node": "ethernet/statistics/mac-control/in-frames-mac-control-extension", "section": "30.3.8.2", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 888, "node": "ethernet/statistics/mac-control/in-frames-mac-control-extension", "section": "30.3.8.2", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." }, { "line": 898, "node": "ethernet/statistics/mac-control/out-frames-mac-control-extension", "section": "30.3.8.1", "rule": "attribute", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "leaf", "leaf-list", "list", "container" ], "guidance": "leaf, leaf-list, list, container", "context": "Scalar attributes are candidates for leaf; collections and structured values may require leaf-list, list, or container. Source access semantics do not by themselves select config true or false." }, { "line": 898, "node": "ethernet/statistics/mac-control/out-frames-mac-control-extension", "section": "30.3.8.1", "rule": "syntax-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [], "guidance": "map APPROPRIATE SYNTAX to YANG leaf or leaf-list for attribiutes, for an action, use it to identify parameters and types", "context": null }, { "line": 898, "node": "ethernet/statistics/mac-control/out-frames-mac-control-extension", "section": "30.3.8.1", "rule": "behavior-field", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "description", "reference" ], "guidance": "Use description for human-readable semantics and reference for the IEEE source", "context": null }, { "line": 898, "node": "ethernet/statistics/mac-control/out-frames-mac-control-extension", "section": "30.3.8.1", "rule": "counter-syntax", "yang_type": "yang:counter64", "status": "guidance", "preferred_constructs": [ "yang:counter64" ], "guidance": "prefer to yang:counter64", "context": "A counter is a state-data candidate, not an automatic type selection. Preserve increment, reset, width, discontinuity, and applicability semantics; these RFCs do not define a Clause 30 counter mapping." } ] } ], "unreferenced_attributes": [ { "subclause": "30.3.1.1", "section": "30.3.1.1.1", "attribute": "aMACID", "source_record": "30.3.1.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.3", "attribute": "aSingleCollisionFrames", "source_record": "30.3.1.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.4", "attribute": "aMultipleCollisionFrames", "source_record": "30.3.1.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.8", "attribute": "aOctetsTransmittedOK", "source_record": "30.3.1.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.9", "attribute": "aFramesWithDeferredXmissions", "source_record": "30.3.1.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.10", "attribute": "aLateCollisions", "source_record": "30.3.1.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.11", "attribute": "aFramesAbortedDueToXSColls", "source_record": "30.3.1.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.13", "attribute": "aCarrierSenseErrors", "source_record": "30.3.1.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.14", "attribute": "aOctetsReceivedOK", "source_record": "30.3.1.1.14", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.16", "attribute": "aPromiscuousStatus", "source_record": "30.3.1.1.16", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.17", "attribute": "aReadMulticastAddressList", "source_record": "30.3.1.1.17", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.20", "attribute": "aFramesWithExcessiveDeferral", "source_record": "30.3.1.1.20", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.23", "attribute": "aInRangeLengthErrors", "source_record": "30.3.1.1.23", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.24", "attribute": "aOutOfRangeLengthField", "source_record": "30.3.1.1.24", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.26", "attribute": "aMACEnableStatus", "source_record": "30.3.1.1.26", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.27", "attribute": "aTransmitEnableStatus", "source_record": "30.3.1.1.27", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.28", "attribute": "aMulticastReceiveStatus", "source_record": "30.3.1.1.28", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.29", "attribute": "aReadWriteMACAddress", "source_record": "30.3.1.1.29", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.30", "attribute": "aCollisionFrames", "source_record": "30.3.1.1.30", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.31", "attribute": "aMACCapabilities", "source_record": "30.3.1.1.31", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.33", "attribute": "aRateControlAbility", "source_record": "30.3.1.1.33", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.34", "attribute": "aRateControlStatus", "source_record": "30.3.1.1.34", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.35", "attribute": "aDeferControlAbility", "source_record": "30.3.1.1.35", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.1.1", "section": "30.3.1.1.36", "attribute": "aDeferControlStatus", "source_record": "30.3.1.1.36", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.2.1", "section": "30.3.2.1.1", "attribute": "aPHYID", "source_record": "30.3.2.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.2.1", "section": "30.3.2.1.3", "attribute": "aPhyTypeList", "source_record": "30.3.2.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.2.1", "section": "30.3.2.1.4", "attribute": "aSQETestErrors", "source_record": "30.3.2.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.2.1", "section": "30.3.2.1.6", "attribute": "aMIIDetect", "source_record": "30.3.2.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.2.1", "section": "30.3.2.1.7", "attribute": "aPhyAdminState", "source_record": "30.3.2.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.3", "section": "30.3.3.1", "attribute": "aMACControlID", "source_record": "30.3.3.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.3", "section": "30.3.3.2", "attribute": "aMACControlFunctionsSupported", "source_record": "30.3.3.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.3", "section": "30.3.3.3", "attribute": "aMACControlFramesTransmitted", "source_record": "30.3.3.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.3", "section": "30.3.3.4", "attribute": "aMACControlFramesReceived", "source_record": "30.3.3.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.4", "section": "30.3.4.1", "attribute": "aPAUSELinkDelayAllowance", "source_record": "30.3.4.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.1", "attribute": "aMPCPID", "source_record": "30.3.5.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.2", "attribute": "aMPCPAdminState", "source_record": "30.3.5.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.3", "attribute": "aMPCPMode", "source_record": "30.3.5.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.4", "attribute": "aMPCPLinkID", "source_record": "30.3.5.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.5", "attribute": "aMPCPRemoteMACAddress", "source_record": "30.3.5.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.6", "attribute": "aMPCPRegistrationState", "source_record": "30.3.5.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.7", "attribute": "aMPCPMACCtrlFramesTransmitted", "source_record": "30.3.5.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.8", "attribute": "aMPCPMACCtrlFramesReceived", "source_record": "30.3.5.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.9", "attribute": "aMPCPTxGate", "source_record": "30.3.5.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.10", "attribute": "aMPCPTxRegAck", "source_record": "30.3.5.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.11", "attribute": "aMPCPTxRegister", "source_record": "30.3.5.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.12", "attribute": "aMPCPTxRegRequest", "source_record": "30.3.5.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.13", "attribute": "aMPCPTxReport", "source_record": "30.3.5.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.14", "attribute": "aMPCPRxGate", "source_record": "30.3.5.1.14", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.15", "attribute": "aMPCPRxRegAck", "source_record": "30.3.5.1.15", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.16", "attribute": "aMPCPRxRegister", "source_record": "30.3.5.1.16", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.17", "attribute": "aMPCPRxRegRequest", "source_record": "30.3.5.1.17", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.18", "attribute": "aMPCPRxReport", "source_record": "30.3.5.1.18", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.19", "attribute": "aMPCPTransmitElapsed", "source_record": "30.3.5.1.19", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.20", "attribute": "aMPCPReceiveElapsed", "source_record": "30.3.5.1.20", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.21", "attribute": "aMPCPRoundTripTime", "source_record": "30.3.5.1.21", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.22", "attribute": "aMPCPDiscoveryWindowsSent", "source_record": "30.3.5.1.22", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.23", "attribute": "aMPCPDiscoveryTimeout", "source_record": "30.3.5.1.23", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.24", "attribute": "aMPCPMaximumPendingGrants", "source_record": "30.3.5.1.24", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.5.1", "section": "30.3.5.1.25", "attribute": "aMPCPRecognizedMulticastIDs", "source_record": "30.3.5.1.25", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.1", "attribute": "aOAMID", "source_record": "30.3.6.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.2", "attribute": "aOAMAdminState", "source_record": "30.3.6.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.3", "attribute": "aOAMMode", "source_record": "30.3.6.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.5", "attribute": "aOAMRemoteMACAddress", "source_record": "30.3.6.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.6", "attribute": "aOAMLocalConfiguration", "source_record": "30.3.6.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.7", "attribute": "aOAMRemoteConfiguration", "source_record": "30.3.6.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.8", "attribute": "aOAMLocalPDUConfiguration", "source_record": "30.3.6.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.9", "attribute": "aOAMRemotePDUConfiguration", "source_record": "30.3.6.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.10", "attribute": "aOAMLocalFlagsField", "source_record": "30.3.6.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.11", "attribute": "aOAMRemoteFlagsField", "source_record": "30.3.6.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.12", "attribute": "aOAMLocalRevision", "source_record": "30.3.6.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.13", "attribute": "aOAMRemoteRevision", "source_record": "30.3.6.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.14", "attribute": "aOAMLocalState", "source_record": "30.3.6.1.14", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.15", "attribute": "aOAMRemoteState", "source_record": "30.3.6.1.15", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.16", "attribute": "aOAMRemoteVendorOUI", "source_record": "30.3.6.1.16", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.17", "attribute": "aOAMRemoteVendorSpecificInfo", "source_record": "30.3.6.1.17", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.18", "attribute": "aOAMUnsupportedCodesTx", "source_record": "30.3.6.1.18", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.19", "attribute": "aOAMUnsupportedCodesRx", "source_record": "30.3.6.1.19", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.20", "attribute": "aOAMInformationTx", "source_record": "30.3.6.1.20", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.21", "attribute": "aOAMInformationRx", "source_record": "30.3.6.1.21", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.22", "attribute": "aOAMUniqueEventNotificationTx", "source_record": "30.3.6.1.22", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.23", "attribute": "aOAMDuplicateEventNotificationTx", "source_record": "30.3.6.1.23", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.24", "attribute": "aOAMUniqueEventNotificationRx", "source_record": "30.3.6.1.24", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.25", "attribute": "aOAMDuplicateEventNotificationRx", "source_record": "30.3.6.1.25", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.26", "attribute": "aOAMLoopbackControlTx", "source_record": "30.3.6.1.26", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.27", "attribute": "aOAMLoopbackControlRx", "source_record": "30.3.6.1.27", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.28", "attribute": "aOAMVariableRequestTx", "source_record": "30.3.6.1.28", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.29", "attribute": "aOAMVariableRequestRx", "source_record": "30.3.6.1.29", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.30", "attribute": "aOAMVariableResponseTx", "source_record": "30.3.6.1.30", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.31", "attribute": "aOAMVariableResponseRx", "source_record": "30.3.6.1.31", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.32", "attribute": "aOAMOrganizationSpecificTx", "source_record": "30.3.6.1.32", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.33", "attribute": "aOAMOrganizationSpecificRx", "source_record": "30.3.6.1.33", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.34", "attribute": "aOAMLocalErrSymPeriodConfig", "source_record": "30.3.6.1.34", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.35", "attribute": "aOAMLocalErrSymPeriodEvent", "source_record": "30.3.6.1.35", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.36", "attribute": "aOAMLocalErrFrameConfig", "source_record": "30.3.6.1.36", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.37", "attribute": "aOAMLocalErrFrameEvent", "source_record": "30.3.6.1.37", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.38", "attribute": "aOAMLocalErrFramePeriodConfig", "source_record": "30.3.6.1.38", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.39", "attribute": "aOAMLocalErrFramePeriodEvent", "source_record": "30.3.6.1.39", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.40", "attribute": "aOAMLocalErrFrameSecsSummaryConfig", "source_record": "30.3.6.1.40", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.41", "attribute": "aOAMLocalErrFrameSecsSummaryEvent", "source_record": "30.3.6.1.41", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.42", "attribute": "aOAMRemoteErrSymPeriodEvent", "source_record": "30.3.6.1.42", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.43", "attribute": "aOAMRemoteErrFrameEvent", "source_record": "30.3.6.1.43", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.44", "attribute": "aOAMRemoteErrFramePeriodEvent", "source_record": "30.3.6.1.44", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.45", "attribute": "aOAMRemoteErrFrameSecsSummaryEvent", "source_record": "30.3.6.1.45", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.6.1", "section": "30.3.6.1.46", "attribute": "aFramesLostDueToOAMError", "source_record": "30.3.6.1.46", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.3.7.1", "section": "30.3.7.1.1", "attribute": "aOMPEmulationID", "source_record": "30.3.7.1", "embedded_in_parent": true, "reference_status": "unreferenced" }, { "subclause": "30.3.7.1", "section": "30.3.7.1.2", "attribute": "aOMPEmulationType", "source_record": "30.3.7.1", "embedded_in_parent": true, "reference_status": "unreferenced" }, { "subclause": "30.3.7.1", "section": "30.3.7.1.3", "attribute": "aSLDErrors", "source_record": "30.3.7.1", "embedded_in_parent": true, "reference_status": "unreferenced" }, { "subclause": "30.3.7.1", "section": "30.3.7.1.4", "attribute": "aCRC8Errors", "source_record": "30.3.7.1", "embedded_in_parent": true, "reference_status": "unreferenced" }, { "subclause": "30.3.7.1", "section": "30.3.7.1.5", "attribute": "aGoodLLID", "source_record": "30.3.7.1", "embedded_in_parent": true, "reference_status": "unreferenced" }, { "subclause": "30.3.7.1", "section": "30.3.7.1.6", "attribute": "aONUPONcastLLID", "source_record": "30.3.7.1", "embedded_in_parent": true, "reference_status": "unreferenced" }, { "subclause": "30.3.7.1", "section": "30.3.7.1.7", "attribute": "aOLTPONcastLLID", "source_record": "30.3.7.1", "embedded_in_parent": true, "reference_status": "unreferenced" }, { "subclause": "30.3.7.1", "section": "30.3.7.1.8", "attribute": "aBadLLID", "source_record": "30.3.7.1", "embedded_in_parent": true, "reference_status": "unreferenced" }, { "subclause": "30.4.1.1", "section": "30.4.1.1.1", "attribute": "aRepeaterID", "source_record": "30.4.1.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.1.1", "section": "30.4.1.1.2", "attribute": "aRepeaterType", "source_record": "30.4.1.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.1.1", "section": "30.4.1.1.3", "attribute": "aRepeaterGroupCapacity", "source_record": "30.4.1.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.1.1", "section": "30.4.1.1.4", "attribute": "aGroupMap", "source_record": "30.4.1.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.1.1", "section": "30.4.1.1.5", "attribute": "aRepeaterHealthState", "source_record": "30.4.1.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.1.1", "section": "30.4.1.1.6", "attribute": "aRepeaterHealthText", "source_record": "30.4.1.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.1.1", "section": "30.4.1.1.7", "attribute": "aRepeaterHealthData", "source_record": "30.4.1.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.1.1", "section": "30.4.1.1.8", "attribute": "aTransmitCollisions", "source_record": "30.4.1.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.2.1", "section": "30.4.2.1.1", "attribute": "aGroupID", "source_record": "30.4.2.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.2.1", "section": "30.4.2.1.2", "attribute": "aGroupPortCapacity", "source_record": "30.4.2.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.2.1", "section": "30.4.2.1.3", "attribute": "aPortMap", "source_record": "30.4.2.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.1", "attribute": "aPortID", "source_record": "30.4.3.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.2", "attribute": "aPortAdminState", "source_record": "30.4.3.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.3", "attribute": "aAutoPartitionState", "source_record": "30.4.3.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.4", "attribute": "aReadableFrames", "source_record": "30.4.3.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.5", "attribute": "aReadableOctets", "source_record": "30.4.3.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.6", "attribute": "aFrameCheckSequenceErrors", "source_record": "30.4.3.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.7", "attribute": "aAlignmentErrors", "source_record": "30.4.3.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.8", "attribute": "aFramesTooLong", "source_record": "30.4.3.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.9", "attribute": "aShortEvents", "source_record": "30.4.3.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.10", "attribute": "aRunts", "source_record": "30.4.3.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.11", "attribute": "aCollisions", "source_record": "30.4.3.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.12", "attribute": "aLateEvents", "source_record": "30.4.3.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.13", "attribute": "aVeryLongEvents", "source_record": "30.4.3.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.14", "attribute": "aDataRateMismatches", "source_record": "30.4.3.1.14", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.15", "attribute": "aAutoPartitions", "source_record": "30.4.3.1.15", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.16", "attribute": "aIsolates", "source_record": "30.4.3.1.16", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.17", "attribute": "aSymbolErrorDuringPacket", "source_record": "30.4.3.1.17", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.18", "attribute": "aLastSourceAddress", "source_record": "30.4.3.1.18", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.19", "attribute": "aSourceAddressChanges", "source_record": "30.4.3.1.19", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.4.3.1", "section": "30.4.3.1.20", "attribute": "aBursts", "source_record": "30.4.3.1.20", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.1", "attribute": "aMAUID", "source_record": "30.5.1.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.3", "attribute": "aMAUTypeList", "source_record": "30.5.1.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.4", "attribute": "aMediaAvailable", "source_record": "30.5.1.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.5", "attribute": "aLoseMediaCounter", "source_record": "30.5.1.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.6", "attribute": "aJabber", "source_record": "30.5.1.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.7", "attribute": "aMAUAdminState", "source_record": "30.5.1.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.8", "attribute": "aBbMAUXmitRcvSplitType", "source_record": "30.5.1.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.9", "attribute": "aBroadbandFrequencies", "source_record": "30.5.1.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.10", "attribute": "aFalseCarriers", "source_record": "30.5.1.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.11", "attribute": "aBIPErrorCount", "source_record": "30.5.1.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.12", "attribute": "aLaneMapping", "source_record": "30.5.1.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.13", "attribute": "aIdleErrorCount", "source_record": "30.5.1.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.14", "attribute": "aPCSCodingViolation", "source_record": "30.5.1.1.14", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.15", "attribute": "aFECAbility", "source_record": "30.5.1.1.15", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.16", "attribute": "aFECmode", "source_record": "30.5.1.1.16", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.17", "attribute": "aFECCorrectedBlocks", "source_record": "30.5.1.1.17", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.18", "attribute": "aFECUncorrectableBlocks", "source_record": "30.5.1.1.18", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.19", "attribute": "aSNROpMarginChnlA", "source_record": "30.5.1.1.19", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.20", "attribute": "aSNROpMarginChnlB", "source_record": "30.5.1.1.20", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.21", "attribute": "aSNROpMarginChnlC", "source_record": "30.5.1.1.21", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.22", "attribute": "aSNROpMarginChnlD", "source_record": "30.5.1.1.22", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.23", "attribute": "aEEESupportList", "source_record": "30.5.1.1.23", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.24", "attribute": "aLDFastRetrainCount", "source_record": "30.5.1.1.24", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.25", "attribute": "aLPFastRetrainCount", "source_record": "30.5.1.1.25", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.26", "attribute": "aRSFECBIPErrorCount", "source_record": "30.5.1.1.26", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.27", "attribute": "aRSFECLaneMapping", "source_record": "30.5.1.1.27", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.28", "attribute": "aSCFECLaneMapping", "source_record": "30.5.1.1.28", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.29", "attribute": "aRSFECBypassAbility", "source_record": "30.5.1.1.29", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.30", "attribute": "aRSFECBypassIndicationAbility", "source_record": "30.5.1.1.30", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.31", "attribute": "aRSFECBypassEnable", "source_record": "30.5.1.1.31", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.32", "attribute": "aRSFECBypassIndicationEnable", "source_record": "30.5.1.1.32", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.33", "attribute": "aPCSFECBypassIndicationAbility", "source_record": "30.5.1.1.33", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.5.1.1", "section": "30.5.1.1.34", "attribute": "aPCSFECBypassIndicationEnable", "source_record": "30.5.1.1.34", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.6.1.1", "section": "30.6.1.1.1", "attribute": "aAutoNegID", "source_record": "30.6.1.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.6.1.1", "section": "30.6.1.1.2", "attribute": "aAutoNegAdminState", "source_record": "30.6.1.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.6.1.1", "section": "30.6.1.1.3", "attribute": "aAutoNegRemoteSignaling", "source_record": "30.6.1.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.6.1.1", "section": "30.6.1.1.5", "attribute": "aAutoNegLocalTechnologyAbility", "source_record": "30.6.1.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.6.1.1", "section": "30.6.1.1.6", "attribute": "aAutoNegAdvertisedTechnologyAbility", "source_record": "30.6.1.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.6.1.1", "section": "30.6.1.1.7", "attribute": "aAutoNegReceivedTechnologyAbility", "source_record": "30.6.1.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.6.1.1", "section": "30.6.1.1.8", "attribute": "aAutoNegLocalSelectorAbility", "source_record": "30.6.1.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.6.1.1", "section": "30.6.1.1.9", "attribute": "aAutoNegAdvertisedSelectorAbility", "source_record": "30.6.1.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.6.1.1", "section": "30.6.1.1.10", "attribute": "aAutoNegReceivedSelectorAbility", "source_record": "30.6.1.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.6.1.2", "section": "30.6.1.2.1", "attribute": "acAutoNegRestartAutoConfig", "source_record": "30.6.1.2.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.6.1.2", "section": "30.6.1.2.2", "attribute": "acAutoNegAdminControl", "source_record": "30.6.1.2.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.1", "attribute": "aAggID", "source_record": "30.7.1.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.2", "attribute": "aAggDescription", "source_record": "30.7.1.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.3", "attribute": "aAggName", "source_record": "30.7.1.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.4", "attribute": "aAggActorSystemID", "source_record": "30.7.1.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.5", "attribute": "aAggActorSystemPriority", "source_record": "30.7.1.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.6", "attribute": "aAggAggregateOrIndividual", "source_record": "30.7.1.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.7", "attribute": "aAggActorAdminKey", "source_record": "30.7.1.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.8", "attribute": "aAggActorOperKey", "source_record": "30.7.1.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.9", "attribute": "aAggMACAddress", "source_record": "30.7.1.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.10", "attribute": "aAggPartnerSystemID", "source_record": "30.7.1.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.11", "attribute": "aAggPartnerSystemPriority", "source_record": "30.7.1.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.12", "attribute": "aAggPartnerOperKey", "source_record": "30.7.1.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.13", "attribute": "aAggAdminState", "source_record": "30.7.1.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.14", "attribute": "aAggOperState", "source_record": "30.7.1.1.14", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.15", "attribute": "aAggTimeOfLastOperChange", "source_record": "30.7.1.1.15", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.16", "attribute": "aAggDataRate", "source_record": "30.7.1.1.16", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.17", "attribute": "aAggOctetsTxOK", "source_record": "30.7.1.1.17", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.18", "attribute": "aAggOctetsRxOK", "source_record": "30.7.1.1.18", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.19", "attribute": "aAggFramesTxOK", "source_record": "30.7.1.1.19", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.20", "attribute": "aAggFramesRxOK", "source_record": "30.7.1.1.20", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.21", "attribute": "aAggMulticastFramesTxOK", "source_record": "30.7.1.1.21", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.22", "attribute": "aAggMulticastFramesRxOK", "source_record": "30.7.1.1.22", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.23", "attribute": "aAggBroadcastFramesTxOK", "source_record": "30.7.1.1.23", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.24", "attribute": "aAggBroadcastFramesRxOK", "source_record": "30.7.1.1.24", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.25", "attribute": "aAggFramesDiscardedOnTx", "source_record": "30.7.1.1.25", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.26", "attribute": "aAggFramesDiscardedOnRx", "source_record": "30.7.1.1.26", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.27", "attribute": "aAggFramesWithTxErrors", "source_record": "30.7.1.1.27", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.28", "attribute": "aAggFramesWithRxErrors", "source_record": "30.7.1.1.28", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.29", "attribute": "aAggUnknownProtocolFrames", "source_record": "30.7.1.1.29", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.30", "attribute": "aAggPortList", "source_record": "30.7.1.1.30", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.31", "attribute": "aAggLinkUpDownNotificationEnable", "source_record": "30.7.1.1.31", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.1.1", "section": "30.7.1.1.32", "attribute": "aAggCollectorMaxDelay", "source_record": "30.7.1.1.32", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.1", "attribute": "aAggPortID", "source_record": "30.7.2.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.2", "attribute": "aAggPortActorSystemPriority", "source_record": "30.7.2.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.3", "attribute": "aAggPortActorSystemID", "source_record": "30.7.2.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.4", "attribute": "aAggPortActorAdminKey", "source_record": "30.7.2.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.5", "attribute": "aAggPortActorOperKey", "source_record": "30.7.2.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.6", "attribute": "aAggPortPartnerAdminSystemPriority", "source_record": "30.7.2.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.7", "attribute": "aAggPortPartnerOperSystemPriority", "source_record": "30.7.2.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.8", "attribute": "aAggPortPartnerAdminSystemID", "source_record": "30.7.2.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.9", "attribute": "aAggPortPartnerOperSystemID", "source_record": "30.7.2.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.10", "attribute": "aAggPortPartnerAdminKey", "source_record": "30.7.2.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.11", "attribute": "aAggPortPartnerOperKey", "source_record": "30.7.2.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.12", "attribute": "aAggPortSelectedAggID", "source_record": "30.7.2.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.13", "attribute": "aAggPortAttachedAggID", "source_record": "30.7.2.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.14", "attribute": "aAggPortActorPort", "source_record": "30.7.2.1.14", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.15", "attribute": "aAggPortActorPortPriority", "source_record": "30.7.2.1.15", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.16", "attribute": "aAggPortPartnerAdminPort", "source_record": "30.7.2.1.16", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.17", "attribute": "aAggPortPartnerOperPort", "source_record": "30.7.2.1.17", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.18", "attribute": "aAggPortPartnerAdminPortPriority", "source_record": "30.7.2.1.18", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.19", "attribute": "aAggPortPartnerOperPortPriority", "source_record": "30.7.2.1.19", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.20", "attribute": "aAggPortActorAdminState", "source_record": "30.7.2.1.20", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.21", "attribute": "aAggPortActorOperState", "source_record": "30.7.2.1.21", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.22", "attribute": "aAggPortPartnerAdminState", "source_record": "30.7.2.1.22", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.23", "attribute": "aAggPortPartnerOperState", "source_record": "30.7.2.1.23", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.2.1", "section": "30.7.2.1.24", "attribute": "aAggPortAggregateOrIndividual", "source_record": "30.7.2.1.24", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.3.1", "section": "30.7.3.1.1", "attribute": "aAggPortStatsID", "source_record": "30.7.3.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.3.1", "section": "30.7.3.1.2", "attribute": "aAggPortStatsLACPDUsRx", "source_record": "30.7.3.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.3.1", "section": "30.7.3.1.3", "attribute": "aAggPortStatsMarkerPDUsRx", "source_record": "30.7.3.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.3.1", "section": "30.7.3.1.4", "attribute": "aAggPortStatsMarkerResponsePDUsRx", "source_record": "30.7.3.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.3.1", "section": "30.7.3.1.5", "attribute": "aAggPortStatsUnknownRx", "source_record": "30.7.3.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.3.1", "section": "30.7.3.1.6", "attribute": "aAggPortStatsIllegalRx", "source_record": "30.7.3.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.3.1", "section": "30.7.3.1.7", "attribute": "aAggPortStatsLACPDUsTx", "source_record": "30.7.3.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.3.1", "section": "30.7.3.1.8", "attribute": "aAggPortStatsMarkerPDUsTx", "source_record": "30.7.3.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.3.1", "section": "30.7.3.1.9", "attribute": "aAggPortStatsMarkerResponsePDUsTx", "source_record": "30.7.3.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.1", "attribute": "aAggPortDebugInformationID", "source_record": "30.7.4.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.2", "attribute": "aAggPortDebugRxState", "source_record": "30.7.4.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.3", "attribute": "aAggPortDebugLastRxTime", "source_record": "30.7.4.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.4", "attribute": "aAggPortDebugMuxState", "source_record": "30.7.4.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.5", "attribute": "aAggPortDebugMuxReason", "source_record": "30.7.4.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.6", "attribute": "aAggPortDebugActorChurnState", "source_record": "30.7.4.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.7", "attribute": "aAggPortDebugPartnerChurnState", "source_record": "30.7.4.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.8", "attribute": "aAggPortDebugActorChurnCount", "source_record": "30.7.4.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.9", "attribute": "aAggPortDebugPartnerChurnCount", "source_record": "30.7.4.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.10", "attribute": "aAggPortDebugActorSyncTransitionCount", "source_record": "30.7.4.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.11", "attribute": "aAggPortDebugPartnerSyncTransitionCount", "source_record": "30.7.4.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.12", "attribute": "aAggPortDebugActorChangeCount", "source_record": "30.7.4.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.7.4.1", "section": "30.7.4.1.13", "attribute": "aAggPortDebugPartnerChangeCount", "source_record": "30.7.4.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.1", "attribute": "aWISID", "source_record": "30.8.1.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.2", "attribute": "aSectionStatus", "source_record": "30.8.1.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.3", "attribute": "aSectionSESThreshold", "source_record": "30.8.1.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.4", "attribute": "aSectionSESs", "source_record": "30.8.1.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.5", "attribute": "aSectionESs", "source_record": "30.8.1.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.6", "attribute": "aSectionSEFSs", "source_record": "30.8.1.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.7", "attribute": "aSectionCVs", "source_record": "30.8.1.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.8", "attribute": "aJ0ValueTX", "source_record": "30.8.1.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.9", "attribute": "aJ0ValueRX", "source_record": "30.8.1.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.10", "attribute": "aLineStatus", "source_record": "30.8.1.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.11", "attribute": "aLineSESThreshold", "source_record": "30.8.1.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.12", "attribute": "aLineSESs", "source_record": "30.8.1.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.13", "attribute": "aLineESs", "source_record": "30.8.1.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.14", "attribute": "aLineCVs", "source_record": "30.8.1.1.14", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.15", "attribute": "aFarEndLineSESs", "source_record": "30.8.1.1.15", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.16", "attribute": "aFarEndLineESs", "source_record": "30.8.1.1.16", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.17", "attribute": "aFarEndLineCVs", "source_record": "30.8.1.1.17", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.18", "attribute": "aPathStatus", "source_record": "30.8.1.1.18", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.19", "attribute": "aPathSESThreshold", "source_record": "30.8.1.1.19", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.20", "attribute": "aPathSESs", "source_record": "30.8.1.1.20", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.21", "attribute": "aPathESs", "source_record": "30.8.1.1.21", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.22", "attribute": "aPathCVs", "source_record": "30.8.1.1.22", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.23", "attribute": "aJ1ValueTX", "source_record": "30.8.1.1.23", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.24", "attribute": "aJ1ValueRX", "source_record": "30.8.1.1.24", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.25", "attribute": "aFarEndPathStatus", "source_record": "30.8.1.1.25", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.26", "attribute": "aFarEndPathSESs", "source_record": "30.8.1.1.26", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.27", "attribute": "aFarEndPathESs", "source_record": "30.8.1.1.27", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.8.1.1", "section": "30.8.1.1.28", "attribute": "aFarEndPathCVs", "source_record": "30.8.1.1.28", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.1", "attribute": "aPSEID", "source_record": "30.9.1.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.2", "attribute": "aPSEAdminState", "source_record": "30.9.1.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.3", "attribute": "aPSEPowerPairsControlAbility", "source_record": "30.9.1.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.4", "attribute": "aPSEPowerPairs", "source_record": "30.9.1.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.5", "attribute": "aPSEPowerDetectionStatus", "source_record": "30.9.1.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.6", "attribute": "aPSEPowerDetectionStatusA", "source_record": "30.9.1.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.7", "attribute": "aPSEPowerDetectionStatusB", "source_record": "30.9.1.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.8", "attribute": "aPSEPowerClassification", "source_record": "30.9.1.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.9", "attribute": "aPSEPowerClassificationA", "source_record": "30.9.1.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.10", "attribute": "aPSEPowerClassificationB", "source_record": "30.9.1.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.11", "attribute": "aPSEInvalidSignatureCounter", "source_record": "30.9.1.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.12", "attribute": "aPSEInvalidSignatureCounterA", "source_record": "30.9.1.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.13", "attribute": "aPSEInvalidSignatureCounterB", "source_record": "30.9.1.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.14", "attribute": "aPSEPowerDeniedCounter", "source_record": "30.9.1.1.14", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.15", "attribute": "aPSEPowerDeniedCounterA", "source_record": "30.9.1.1.15", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.16", "attribute": "aPSEPowerDeniedCounterB", "source_record": "30.9.1.1.16", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.17", "attribute": "aPSEOverLoadCounter", "source_record": "30.9.1.1.17", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.18", "attribute": "aPSEOverLoadCounterA", "source_record": "30.9.1.1.18", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.19", "attribute": "aPSEOverLoadCounterB", "source_record": "30.9.1.1.19", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.20", "attribute": "aPSEMPSAbsentCounter", "source_record": "30.9.1.1.20", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.21", "attribute": "aPSEMPSAbsentCounterA", "source_record": "30.9.1.1.21", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.22", "attribute": "aPSEMPSAbsentCounterB", "source_record": "30.9.1.1.22", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.23", "attribute": "aPSEActualPower", "source_record": "30.9.1.1.23", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.24", "attribute": "aPSEPowerAccuracy", "source_record": "30.9.1.1.24", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.9.1.1", "section": "30.9.1.1.25", "attribute": "aPSECumulativeEnergy", "source_record": "30.9.1.1.25", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.10.1.1", "section": "30.10.1.1.1", "attribute": "aMidSpanID", "source_record": "30.10.1.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.10.1.1", "section": "30.10.1.1.2", "attribute": "aMidSpanPSEGroupCapacity", "source_record": "30.10.1.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.10.1.1", "section": "30.10.1.1.3", "attribute": "aMidSpanPSEGroupMap", "source_record": "30.10.1.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.10.2.1", "section": "30.10.2.1.1", "attribute": "aPSEGroupID", "source_record": "30.10.2.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.10.2.1", "section": "30.10.2.1.2", "attribute": "aPSECapacity", "source_record": "30.10.2.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.10.2.1", "section": "30.10.2.1.3", "attribute": "aPSEMap", "source_record": "30.10.2.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.1.1", "section": "30.11.1.1.1", "attribute": "aPAFID", "source_record": "30.11.1.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.1.1", "section": "30.11.1.1.2", "attribute": "aPhyEnd", "source_record": "30.11.1.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.1.1", "section": "30.11.1.1.3", "attribute": "aPHYCurrentStatus", "source_record": "30.11.1.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.1.1", "section": "30.11.1.1.4", "attribute": "aPAFSupported", "source_record": "30.11.1.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.1.1", "section": "30.11.1.1.5", "attribute": "aPAFAdminState", "source_record": "30.11.1.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.1.1", "section": "30.11.1.1.6", "attribute": "aLocalPAFCapacity", "source_record": "30.11.1.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.1.1", "section": "30.11.1.1.7", "attribute": "aLocalPMEAvailable", "source_record": "30.11.1.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.1.1", "section": "30.11.1.1.8", "attribute": "aLocalPMEAggregate", "source_record": "30.11.1.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.1.1", "section": "30.11.1.1.9", "attribute": "aRemotePAFSupported", "source_record": "30.11.1.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.1.1", "section": "30.11.1.1.10", "attribute": "aRemotePAFCapacity", "source_record": "30.11.1.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.1.1", "section": "30.11.1.1.11", "attribute": "aRemotePMEAggregate", "source_record": "30.11.1.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.2.1", "section": "30.11.2.1.1", "attribute": "aPMEID", "source_record": "30.11.2.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.2.1", "section": "30.11.2.1.2", "attribute": "aPMEAdminState", "source_record": "30.11.2.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.2.1", "section": "30.11.2.1.3", "attribute": "aPMEStatus", "source_record": "30.11.2.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.2.1", "section": "30.11.2.1.4", "attribute": "aPMESNRMgn", "source_record": "30.11.2.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.2.1", "section": "30.11.2.1.5", "attribute": "aTCCodingViolations", "source_record": "30.11.2.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.2.1", "section": "30.11.2.1.6", "attribute": "aProfileSelect", "source_record": "30.11.2.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.2.1", "section": "30.11.2.1.7", "attribute": "aOperatingProfile", "source_record": "30.11.2.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.2.1", "section": "30.11.2.1.8", "attribute": "aPMEFECCorrectedBlocks", "source_record": "30.11.2.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.2.1", "section": "30.11.2.1.9", "attribute": "aPMEFECUncorrectableBlocks", "source_record": "30.11.2.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.11.2.1", "section": "30.11.2.1.10", "attribute": "aTCCRCErrors", "source_record": "30.11.2.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.1.1", "section": "30.12.1.1.1", "attribute": "aLldpXdot3PortConfigTLVsTxEnable", "source_record": "30.12.1.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.1", "attribute": "aLldpXdot3LocPortAutoNegSupported", "source_record": "30.12.2.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.2", "attribute": "aLldpXdot3LocPortAutoNegEnabled", "source_record": "30.12.2.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.3", "attribute": "aLldpXdot3LocPortAutoNegAdvertisedCap", "source_record": "30.12.2.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.4", "attribute": "aLldpXdot3LocPortOperMauType", "source_record": "30.12.2.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.5", "attribute": "aLldpXdot3LocPowerPortClass", "source_record": "30.12.2.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.6", "attribute": "aLldpXdot3LocPowerMDISupported", "source_record": "30.12.2.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.7", "attribute": "aLldpXdot3LocPowerMDIEnabled", "source_record": "30.12.2.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.8", "attribute": "aLldpXdot3LocPowerPairControllable", "source_record": "30.12.2.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.9", "attribute": "aLldpXdot3LocPowerPairs", "source_record": "30.12.2.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.10", "attribute": "aLldpXdot3LocPowerClass", "source_record": "30.12.2.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.11", "attribute": "aLldpXdot3LocLinkAggStatus", "source_record": "30.12.2.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.12", "attribute": "aLldpXdot3LocLinkAggPortId", "source_record": "30.12.2.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.13", "attribute": "aLldpXdot3LocMaxFrameSize", "source_record": "30.12.2.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.14", "attribute": "aLldpXdot3LocPowerType", "source_record": "30.12.2.1.14", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.15", "attribute": "aLldpXdot3LocPowerSource", "source_record": "30.12.2.1.15", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.16", "attribute": "aLldpXdot3LocPowerPriority", "source_record": "30.12.2.1.16", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.17", "attribute": "aLldpXdot3LocPDRequestedPowerValue", "source_record": "30.12.2.1.17", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.18", "attribute": "aLldpXdot3LocPDRequestedPowerValueA", "source_record": "30.12.2.1.18", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.19", "attribute": "aLldpXdot3LocPDRequestedPowerValueB", "source_record": "30.12.2.1.19", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.20", "attribute": "aLldpXdot3LocPSEAllocatedPowerValue", "source_record": "30.12.2.1.20", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.21", "attribute": "aLldpXdot3LocPSEAllocatedPowerValueA", "source_record": "30.12.2.1.21", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.22", "attribute": "aLldpXdot3LocPSEAllocatedPowerValueB", "source_record": "30.12.2.1.22", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.23", "attribute": "aLldpXdot3LocPSEPoweringStatus", "source_record": "30.12.2.1.23", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.24", "attribute": "aLldpXdot3LocPDPoweredStatus", "source_record": "30.12.2.1.24", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.25", "attribute": "aLldpXdot3LocPowerPairsExt", "source_record": "30.12.2.1.25", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.26", "attribute": "aLldpXdot3LocPowerClassExtA", "source_record": "30.12.2.1.26", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.27", "attribute": "aLldpXdot3LocPowerClassExtB", "source_record": "30.12.2.1.27", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.28", "attribute": "aLldpXdot3LocPowerClassExt", "source_record": "30.12.2.1.28", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.29", "attribute": "aLldpXdot3LocPowerTypeExt", "source_record": "30.12.2.1.29", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.30", "attribute": "aLldpXdot3LocPDLoad", "source_record": "30.12.2.1.30", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.31", "attribute": "aLldpXdot3LocPD4PID", "source_record": "30.12.2.1.31", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.32", "attribute": "aLldpXdot3LocPSEMaxAvailPower", "source_record": "30.12.2.1.32", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.33", "attribute": "aLldpXdot3LocPSEAutoclassSupport", "source_record": "30.12.2.1.33", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.34", "attribute": "aLldpXdot3LocAutoclassCompleted", "source_record": "30.12.2.1.34", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.35", "attribute": "aLldpXdot3LocAutoclassRequest", "source_record": "30.12.2.1.35", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.36", "attribute": "aLldpXdot3LocPowerDownRequest", "source_record": "30.12.2.1.36", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.37", "attribute": "aLldpXdot3LocPowerDownTime", "source_record": "30.12.2.1.37", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.38", "attribute": "aLldpXdot3LocMeasVoltageSupport", "source_record": "30.12.2.1.38", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.39", "attribute": "aLldpXdot3LocMeasCurrentSupport", "source_record": "30.12.2.1.39", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.40", "attribute": "aLldpXdot3LocMeasPowerSupport", "source_record": "30.12.2.1.40", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.41", "attribute": "aLldpXdot3LocMeasEnergySupport", "source_record": "30.12.2.1.41", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.42", "attribute": "aLldpXdot3LocMeasurementSource", "source_record": "30.12.2.1.42", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.43", "attribute": "aLldpXdot3LocMeasVoltageRequest", "source_record": "30.12.2.1.43", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.44", "attribute": "aLldpXdot3LocMeasCurrentRequest", "source_record": "30.12.2.1.44", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.45", "attribute": "aLldpXdot3LocMeasPowerRequest", "source_record": "30.12.2.1.45", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.46", "attribute": "aLldpXdot3LocMeasEnergyRequest", "source_record": "30.12.2.1.46", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.47", "attribute": "aLldpXdot3LocMeasVoltageValid", "source_record": "30.12.2.1.47", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.48", "attribute": "aLldpXdot3LocMeasCurrentValid", "source_record": "30.12.2.1.48", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.49", "attribute": "aLldpXdot3LocMeasPowerValid", "source_record": "30.12.2.1.49", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.50", "attribute": "aLldpXdot3LocMeasEnergyValid", "source_record": "30.12.2.1.50", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.51", "attribute": "aLldpXdot3LocMeasVoltageUncertainty", "source_record": "30.12.2.1.51", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.52", "attribute": "aLldpXdot3LocMeasCurrentUncertainty", "source_record": "30.12.2.1.52", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.53", "attribute": "aLldpXdot3LocMeasPowerUncertainty", "source_record": "30.12.2.1.53", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.54", "attribute": "aLldpXdot3LocMeasEnergyUncertainty", "source_record": "30.12.2.1.54", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.55", "attribute": "aLldpXdot3LocVoltageMeasurement", "source_record": "30.12.2.1.55", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.56", "attribute": "aLldpXdot3LocCurrentMeasurement", "source_record": "30.12.2.1.56", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.57", "attribute": "aLldpXdot3LocPowerMeasurement", "source_record": "30.12.2.1.57", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.58", "attribute": "aLldpXdot3LocEnergyMeasurement", "source_record": "30.12.2.1.58", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.59", "attribute": "aLldpXdot3LocPSEPowerPriceIndex", "source_record": "30.12.2.1.59", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.60", "attribute": "aLldpXdot3LocResponseTime", "source_record": "30.12.2.1.60", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.61", "attribute": "aLldpXdot3LocReady", "source_record": "30.12.2.1.61", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.62", "attribute": "aLldpXdot3LocTxTwSys", "source_record": "30.12.2.1.62", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.63", "attribute": "aLldpXdot3LocTxTwSysEcho", "source_record": "30.12.2.1.63", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.64", "attribute": "aLldpXdot3LocRxTwSys", "source_record": "30.12.2.1.64", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.65", "attribute": "aLldpXdot3LocRxTwSysEcho", "source_record": "30.12.2.1.65", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.66", "attribute": "aLldpXdot3LocFbTwSys", "source_record": "30.12.2.1.66", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.67", "attribute": "aLldpXdot3TxDllReady", "source_record": "30.12.2.1.67", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.68", "attribute": "aLldpXdot3RxDllReady", "source_record": "30.12.2.1.68", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.69", "attribute": "aLldpXdot3LocDllEnabled", "source_record": "30.12.2.1.69", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.70", "attribute": "aLldpXdot3LocTxFw", "source_record": "30.12.2.1.70", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.71", "attribute": "aLldpXdot3LocTxFwEcho", "source_record": "30.12.2.1.71", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.72", "attribute": "aLldpXdot3LocRxFw", "source_record": "30.12.2.1.72", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.73", "attribute": "aLldpXdot3LocRxFwEcho", "source_record": "30.12.2.1.73", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.74", "attribute": "aLldpXdot3LocPreemptSupported", "source_record": "30.12.2.1.74", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.75", "attribute": "aLldpXdot3LocPreemptEnabled", "source_record": "30.12.2.1.75", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.76", "attribute": "aLldpXdot3LocPreemptActive", "source_record": "30.12.2.1.76", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.2.1", "section": "30.12.2.1.77", "attribute": "aLldpXdot3LocAddFragSize", "source_record": "30.12.2.1.77", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.1", "attribute": "aLldpXdot3RemPortAutoNegSupported", "source_record": "30.12.3.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.2", "attribute": "aLldpXdot3RemPortAutoNegEnabled", "source_record": "30.12.3.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.3", "attribute": "aLldpXdot3RemPortAutoNegAdvertisedCap", "source_record": "30.12.3.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.4", "attribute": "aLldpXdot3RemPortOperMauType", "source_record": "30.12.3.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.5", "attribute": "aLldpXdot3RemPowerPortClass", "source_record": "30.12.3.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.6", "attribute": "aLldpXdot3RemPowerMDISupported", "source_record": "30.12.3.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.7", "attribute": "aLldpXdot3RemPowerMDIEnabled", "source_record": "30.12.3.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.8", "attribute": "aLldpXdot3RemPowerPairControllable", "source_record": "30.12.3.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.9", "attribute": "aLldpXdot3RemPowerPairs", "source_record": "30.12.3.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.10", "attribute": "aLldpXdot3RemPowerClass", "source_record": "30.12.3.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.11", "attribute": "aLldpXdot3RemLinkAggStatus", "source_record": "30.12.3.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.12", "attribute": "aLldpXdot3RemLinkAggPortId", "source_record": "30.12.3.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.13", "attribute": "aLldpXdot3RemMaxFrameSize", "source_record": "30.12.3.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.14", "attribute": "aLldpXdot3RemPowerType", "source_record": "30.12.3.1.14", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.15", "attribute": "aLldpXdot3RemPowerSource", "source_record": "30.12.3.1.15", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.16", "attribute": "aLldpXdot3RemPowerPriority", "source_record": "30.12.3.1.16", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.17", "attribute": "aLldpXdot3RemPDRequestedPowerValue", "source_record": "30.12.3.1.17", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.18", "attribute": "aLldpXdot3RemPDRequestedPowerValueA", "source_record": "30.12.3.1.18", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.19", "attribute": "aLldpXdot3RemPDRequestedPowerValueB", "source_record": "30.12.3.1.19", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.20", "attribute": "aLldpXdot3RemPSEAllocatedPowerValue", "source_record": "30.12.3.1.20", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.21", "attribute": "aLldpXdot3RemPSEAllocatedPowerValueA", "source_record": "30.12.3.1.21", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.22", "attribute": "aLldpXdot3RemPSEAllocatedPowerValueB", "source_record": "30.12.3.1.22", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.23", "attribute": "aLldpXdot3RemPSEPoweringStatus", "source_record": "30.12.3.1.23", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.24", "attribute": "aLldpXdot3RemPDPoweredStatus", "source_record": "30.12.3.1.24", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.25", "attribute": "aLldpXdot3RemPowerPairsExt", "source_record": "30.12.3.1.25", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.26", "attribute": "aLldpXdot3RemPowerClassExtA", "source_record": "30.12.3.1.26", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.27", "attribute": "aLldpXdot3RemPowerClassExtB", "source_record": "30.12.3.1.27", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.28", "attribute": "aLldpXdot3RemPowerClassExt", "source_record": "30.12.3.1.28", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.29", "attribute": "aLldpXdot3RemPowerTypeExt", "source_record": "30.12.3.1.29", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.30", "attribute": "aLldpXdot3RemPDLoad", "source_record": "30.12.3.1.30", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.31", "attribute": "aLldpXdot3RemPD4PID", "source_record": "30.12.3.1.31", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.32", "attribute": "aLldpXdot3RemPSEMaxAvailPower", "source_record": "30.12.3.1.32", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.33", "attribute": "aLldpXdot3RemPSEAutoclassSupport", "source_record": "30.12.3.1.33", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.34", "attribute": "aLldpXdot3RemAutoclassCompleted", "source_record": "30.12.3.1.34", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.35", "attribute": "aLldpXdot3RemAutoclassRequest", "source_record": "30.12.3.1.35", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.36", "attribute": "aLldpXdot3RemPowerDownRequest", "source_record": "30.12.3.1.36", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.37", "attribute": "aLldpXdot3RemPowerDownTime", "source_record": "30.12.3.1.37", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.38", "attribute": "aLldpXdot3RemMeasVoltageSupport", "source_record": "30.12.3.1.38", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.39", "attribute": "aLldpXdot3RemMeasCurrentSupport", "source_record": "30.12.3.1.39", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.40", "attribute": "aLldpXdot3RemMeasPowerSupport", "source_record": "30.12.3.1.40", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.41", "attribute": "aLldpXdot3RemMeasEnergySupport", "source_record": "30.12.3.1.41", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.42", "attribute": "aLldpXdot3RemMeasurementSource", "source_record": "30.12.3.1.42", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.43", "attribute": "aLldpXdot3RemMeasVoltageRequest", "source_record": "30.12.3.1.43", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.44", "attribute": "aLldpXdot3RemMeasCurrentRequest", "source_record": "30.12.3.1.44", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.45", "attribute": "aLldpXdot3RemMeasPowerRequest", "source_record": "30.12.3.1.45", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.46", "attribute": "aLldpXdot3RemMeasEnergyRequest", "source_record": "30.12.3.1.46", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.47", "attribute": "aLldpXdot3RemMeasVoltageValid", "source_record": "30.12.3.1.47", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.48", "attribute": "aLldpXdot3RemMeasCurrentValid", "source_record": "30.12.3.1.48", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.49", "attribute": "aLldpXdot3RemMeasPowerValid", "source_record": "30.12.3.1.49", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.50", "attribute": "aLldpXdot3RemMeasEnergyValid", "source_record": "30.12.3.1.50", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.51", "attribute": "aLldpXdot3RemMeasVoltageUncertainty", "source_record": "30.12.3.1.51", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.52", "attribute": "aLldpXdot3RemMeasCurrentUncertainty", "source_record": "30.12.3.1.52", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.53", "attribute": "aLldpXdot3RemMeasPowerUncertainty", "source_record": "30.12.3.1.53", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.54", "attribute": "aLldpXdot3RemMeasEnergyUncertainty", "source_record": "30.12.3.1.54", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.55", "attribute": "aLldpXdot3RemVoltageMeasurement", "source_record": "30.12.3.1.55", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.56", "attribute": "aLldpXdot3RemCurrentMeasurement", "source_record": "30.12.3.1.56", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.57", "attribute": "aLldpXdot3RemPowerMeasurement", "source_record": "30.12.3.1.57", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.58", "attribute": "aLldpXdot3RemEnergyMeasurement", "source_record": "30.12.3.1.58", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.59", "attribute": "aLldpXdot3RemPSEPowerPriceIndex", "source_record": "30.12.3.1.59", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.60", "attribute": "aLldpXdot3RemTxTwSys", "source_record": "30.12.3.1.60", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.61", "attribute": "aLldpXdot3RemTxTwSysEcho", "source_record": "30.12.3.1.61", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.62", "attribute": "aLldpXdot3RemRxTwSys", "source_record": "30.12.3.1.62", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.63", "attribute": "aLldpXdot3RemRxTwSysEcho", "source_record": "30.12.3.1.63", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.12.3.1", "section": "30.12.3.1.64", "attribute": "aLldpXdot3RemFbTwSys", "source_record": "30.12.3.1.64", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.13.1", "section": "30.13.1.1", "attribute": "aTimeSyncCapabilityTX", "source_record": "30.13.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.13.1", "section": "30.13.1.2", "attribute": "aTimeSyncCapabilityRX", "source_record": "30.13.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.13.1", "section": "30.13.1.3", "attribute": "aTimeSyncDelayTXmax", "source_record": "30.13.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.13.1", "section": "30.13.1.4", "attribute": "aTimeSyncDelayTXmin", "source_record": "30.13.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.13.1", "section": "30.13.1.5", "attribute": "aTimeSyncDelayRXmax", "source_record": "30.13.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.13.1", "section": "30.13.1.6", "attribute": "aTimeSyncDelayRXmin", "source_record": "30.13.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.1", "attribute": "aMACMergeSupport", "source_record": "30.14.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.2", "attribute": "aMACMergeStatusVerify", "source_record": "30.14.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.3", "attribute": "aMACMergeEnableTx", "source_record": "30.14.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.4", "attribute": "aMACMergeVerifyDisableTx", "source_record": "30.14.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.5", "attribute": "aMACMergeStatusTx", "source_record": "30.14.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.6", "attribute": "aMACMergeVerifyTime", "source_record": "30.14.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.7", "attribute": "aMACMergeAddFragSize", "source_record": "30.14.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.8", "attribute": "aMACMergeFrameAssErrorCount", "source_record": "30.14.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.9", "attribute": "aMACMergeFrameSmdErrorCount", "source_record": "30.14.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.10", "attribute": "aMACMergeFrameAssOkCount", "source_record": "30.14.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.11", "attribute": "aMACMergeFragCountRx", "source_record": "30.14.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.12", "attribute": "aMACMergeFragCountTx", "source_record": "30.14.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.14.1", "section": "30.14.1.13", "attribute": "aMACMergeHoldCount", "source_record": "30.14.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.1", "attribute": "aPoDLPSEID", "source_record": "30.15.1.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.2", "attribute": "aPoDLPSEAdminState", "source_record": "30.15.1.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.3", "attribute": "aPoDLPSEPowerDetectionStatus", "source_record": "30.15.1.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.4", "attribute": "aPoDLPSEType", "source_record": "30.15.1.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.5", "attribute": "aPoDLPSEDetectedPDType", "source_record": "30.15.1.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.6", "attribute": "aPoDLPSEDetectedPDPowerClass", "source_record": "30.15.1.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.7", "attribute": "aPoDLPSEInvalidSignatureCounter", "source_record": "30.15.1.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.8", "attribute": "aPoDLPSEInvalidClassCounter", "source_record": "30.15.1.1.8", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.9", "attribute": "aPoDLPSEPowerDeniedCounter", "source_record": "30.15.1.1.9", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.10", "attribute": "aPoDLPSEOverLoadCounter", "source_record": "30.15.1.1.10", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.11", "attribute": "aPoDLPSEMaintainFullVoltageSignatureAbsentCounter", "source_record": "30.15.1.1.11", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.12", "attribute": "aPoDLPSEActualPower", "source_record": "30.15.1.1.12", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.13", "attribute": "aPoDLPSEPowerAccuracy", "source_record": "30.15.1.1.13", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.15.1.1", "section": "30.15.1.1.14", "attribute": "aPoDLPSECumulativeEnergy", "source_record": "30.15.1.1.14", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.16.1.1", "section": "30.16.1.1.1", "attribute": "aPLCAAdminState", "source_record": "30.16.1.1.1", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.16.1.1", "section": "30.16.1.1.2", "attribute": "aPLCAStatus", "source_record": "30.16.1.1.2", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.16.1.1", "section": "30.16.1.1.3", "attribute": "aPLCANodeCount", "source_record": "30.16.1.1.3", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.16.1.1", "section": "30.16.1.1.4", "attribute": "aPLCALocalNodeID", "source_record": "30.16.1.1.4", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.16.1.1", "section": "30.16.1.1.5", "attribute": "aPLCATransmitOpportunityTimer", "source_record": "30.16.1.1.5", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.16.1.1", "section": "30.16.1.1.6", "attribute": "aPLCAMaxBurstCount", "source_record": "30.16.1.1.6", "embedded_in_parent": false, "reference_status": "unreferenced" }, { "subclause": "30.16.1.1", "section": "30.16.1.1.7", "attribute": "aPLCABurstTimer", "source_record": "30.16.1.1.7", "embedded_in_parent": false, "reference_status": "unreferenced" } ], "uncertain_attributes": [], "environment": { "generated_at_utc": "2026-11-06T21:51:36.745436+00:00", "python_version": "3.14.4", "python_executable": "/home/petejone/vpython/bin/python3", "platform": "Linux-6.18.54.1-microsoft-standard-WSL2-x86_64-with-glibc2.43", "openpyxl_version": "3.1.5", "python_docx_version": "1.2.0", "pyyaml_version": "6.0.3", "pyspellchecker_version": "0.9.1", "spelling_dictionary_source": "ieee8023_clause30-0.0.3+dirty.build20261106t034951316960z-py3-none-any.whl:ieee8023_clause30/802d3Clause30-approved-words.txt", "spelling_dictionary_sha256": "4f8314de4e938d88546461f8d9e1113e74651315b83d972e4705c87cded64701", "rfc9907_metadata_sha256": "11cdf6b56e9dfcbb8e8ae5dd56b9e7fc660779123bf9cc254419e3cd96bae46f", "rfc9907_schema_sha256": "80ae31c6f5a0d2f995c2767d8bff5492fd25657b186b74d2485ccd6cac04651e", "review_tool_sha256": "c49a2ba50570e989d35e8687408dde0afb3fa1f825ed43aa24a01ba3ef547a7c" }, "guidance": { "available": true, "filename": "802d3Clause30-YANG-mapping-guidance.yaml", "sha256": "177c58df9c4f989f55887f5197127631389ca133923aab3ead4249675db6e6fb", "overall": { "Object instances, lists, and keys": null, "Configuration, state, and datastore handling": "Treat read-write attributes as\ncandidates for YANG configuration data (`config true`). Treat read-only\nattributes as candidates for state data (`config false`); review each case.", "Data types, units, ranges, and counters": null, "Actions, RPCs, and notifications": null } }, "dictionary_spellcheck_available": true, "rfc9907": { "document": { "metadata_version": 1, "rfc": 9907, "source": { "filename": "rfc9907.txt", "path": "Local/rfc9907.txt", "sha256": "5dbd4eb775740eab2de4d019e25ff7dbd3472ac42eaf8406bf89651ec1494892", "url": "https://www.rfc-editor.org/rfc/rfc9907.txt" }, "processed_source": { "filename": "rfc9907.stripped.txt", "sha256": "0567dd04aaa0f26057f14ecaefb720d6d2ee6dadf4789972e5da6dfb6e9f3f6d", "pagination_stripped": false, "strip_operation": null, "strip_tool_version": null }, "classification": { "status": "unreviewed heuristic candidates", "description": "Only RFC 9907 sections 4.1 through 4.29 and their subsections are retained; candidate types are lexical indicators, not a complete or authoritative interpretation of RFC requirements. Example/code flags and keyword meanings require review. Paragraph whitespace is normalized." }, "sections": [ { "number": "4.1", "title": "Module Naming Conventions", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.1", "paragraphs": [ { "text": "Normative modules contained in Standards Track documents MUST be named according to the guidelines in the IANA Considerations section of [RFC6020].", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.1-1" }, { "text": "A distinctive word or abbreviation (e.g., protocol name or working group abbreviation) SHOULD be used in the module name. If new definitions are being defined to extend one or more existing modules, then the same word or abbreviation should be reused, instead of creating a new one.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.1-2" }, { "text": "All published module names MUST be unique. For a YANG module published in an RFC, this uniqueness is guaranteed by IANA (Section 14 of [RFC6020]). For unpublished modules, the authors need to check that no other work in progress is using the same module name.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.1-3" }, { "text": "Example modules are non-normative and SHOULD be named with the prefix \"example-\".", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.1-4" }, { "text": "It is suggested that a stable module name prefix be selected that represents the entire organization. All normative YANG modules published by the IETF MUST begin with the prefix \"ietf-\". All IANA- maintained YANG modules MUST begin with the prefix \"iana-\". Another standards organization, such as the IEEE, might use the prefix \"ieee-\" for all YANG modules.", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.1-5" }, { "text": "Once a module name is published, it MUST NOT be reused, even if the RFC containing the module is reclassified to \"Historic\" status. A module name cannot be changed in YANG, and this would be treated as a new module, not a name change.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST NOT" ], "example_or_code": false, "id": "rfc9907-4.1-6" } ] }, { "number": "4.2", "title": "Prefixes", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.2", "paragraphs": [ { "text": "All YANG definitions are scoped by the module containing the definition being referenced. This allows the same name to be used in multiple modules, even if the names are not unique. In the example below, the identifier \"foo\" is used in all three modules:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.2-1" }, { "text": "module example-foo { namespace \"tag:example.com,2017:example-foo\"; prefix f;", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.2-2" }, { "text": "container foo; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.2-3" }, { "text": "module example-bar { namespace \"tag:example.com,2017:example-bar\"; prefix b;", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.2-4" }, { "text": "typedef foo { type uint32; } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.2-5" }, { "text": "module example-one { namespace \"tag:example.com,2017:example-one\"; prefix one; import example-foo { prefix f; } import example-bar { prefix b; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.2-6" }, { "text": "augment \"/f:foo\" { leaf foo { type b:foo; } } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.2-7" }, { "text": "YANG defines the following rules for prefix usage:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.2-8" }, { "text": "* Prefixes are never used for built-in data types and YANG keywords.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.2-9" }, { "text": "* A prefix MUST be used for any external statement (i.e., a statement defined with the YANG \"extension\" statement).", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.2-10" }, { "text": "* The proper module prefix MUST be used for all identifiers imported from other modules.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.2-11" }, { "text": "* The proper module prefix MUST be used for all identifiers included from a submodule.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.2-12" }, { "text": "The following guidelines apply to prefix usage of the current (local) module:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.2-13" }, { "text": "* The local module prefix SHOULD be used instead of no prefix in all path expressions.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.2-14" }, { "text": "* The local module prefix MUST be used instead of no prefix in all \"default\" statements for an \"identityref\" or \"instance-identifier\" data type.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.2-15" }, { "text": "* The local module prefix MAY be used for references to typedefs, groupings, extensions, features, and identities defined in the module.", "candidate_types": [ "permission" ], "uppercase_requirement_words": [ "MAY" ], "example_or_code": false, "id": "rfc9907-4.2-16" }, { "text": "Consistent with Section 7.1.4 of [RFC7950], the prefix defined by a module SHOULD be used when the module is imported, unless there is a conflict.", "candidate_types": [ "definition", "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.2-17" }, { "text": "Prefix values SHOULD be short but meaningful to the intended user. Prefix values SHOULD NOT conflict with known modules that have been previously published.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.2-18" }, { "text": "For convenience, prefix values of example modules SHOULD be prefixed with \"ex\" or similar patterns. In doing so, readers of example modules or tree diagrams that mix both example and standard modules can easily identify example parts.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.2-19" } ] }, { "number": "4.3", "title": "Identifiers", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.3", "paragraphs": [ { "text": "All YANG identifiers in published modules MUST be between 1 and 64 characters in length. These include any construct specified as an \"identifier-arg-str\" token in the ABNF in Section 14 of [RFC7950].", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.3-1" } ] }, { "number": "4.3.1", "title": "Identifier Naming Conventions", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.3.1", "paragraphs": [ { "text": "Identifiers SHOULD follow a consistent naming pattern throughout the module. Only lowercase letters, numbers, and dashes SHOULD be used in identifier names. Uppercase characters, the period character, and the underscore character MAY be used if the identifier represents a well-known value that uses these characters. YANG does not permit any other characters in YANG identifiers.", "candidate_types": [ "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.3.1-1" }, { "text": "Identifiers SHOULD include complete words and/or well-known acronyms or abbreviations. Child nodes within a container or list SHOULD NOT replicate the parent identifier. YANG identifiers are hierarchical and are only meant to be unique within the set of sibling nodes defined in the same module namespace.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.3.1-2" }, { "text": "List identifiers SHOULD be singular with the surrounding container name plural. Similarly, \"leaf-list\" identifiers SHOULD be singular.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.3.1-3" }, { "text": "It is permissible to use common identifiers such as \"name\" or \"id\" in data definition statements, especially if these data nodes share a common data type.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.3.1-4" }, { "text": "Identifiers SHOULD NOT carry any special semantics that identify data modeling properties. Only YANG statements and YANG extension statements are designed to convey machine-readable data modeling properties. For example, naming an object \"config\" or \"state\" does not change whether it is configuration data or state data. Only defined YANG statements or YANG \"extension\" statements can be used to assign semantics in a machine-readable format in YANG.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.3.1-5" } ] }, { "number": "4.4", "title": "Defaults", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.4", "paragraphs": [ { "text": "In general, it is suggested that substatements containing very common default values SHOULD NOT be present. The substatements listed in Table 1 are commonly used with the default value, which would make the module difficult to read if used everywhere they are allowed.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.4-1" }, { "text": "+==============+===============+ | Statement | Default Value | +==============+===============+ | config | true | +--------------+---------------+ | mandatory | false | +--------------+---------------+ | max-elements | unbounded | +--------------+---------------+ | min-elements | 0 | +--------------+---------------+ | ordered-by | system | +--------------+---------------+ | status | current | +--------------+---------------+ | yin-element | false | +--------------+---------------+", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.4-2" }, { "text": "Table 1: Statement Defaults", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.4-3" } ] }, { "number": "4.5", "title": "Conditional Statements", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.5", "paragraphs": [ { "text": "A module may be conceptually partitioned in several ways using the \"if-feature\" and/or \"when\" statements.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.5-1" }, { "text": "Data model designers need to carefully consider all modularity aspects, including the use of YANG conditional statements.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.5-2" }, { "text": "If a data definition is optional, depending on server support for a NETCONF or RESTCONF protocol capability, then a YANG \"feature\" statement SHOULD be defined. The defined \"feature\" statement SHOULD then be used in the conditional \"if-feature\" statement referencing the optional data definition.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.5-3" }, { "text": "If any notification data, or any data definition, for a non- configuration data node is not mandatory, then the server may or may not be required to return an instance of this data node. If any conditional requirements exist for returning the data node in a notification payload or retrieval request, they MUST be documented somewhere. For example, a \"when\" or \"if-feature\" statement could apply to the data node or the conditional requirements could be explained in a \"description\" statement within the data node or one of its ancestors (if any).", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.5-4" }, { "text": "If any \"if-feature\" statements apply to a list node, then the same \"if-feature\" statements MUST apply to any key leaf nodes for the list. There MUST NOT be any \"if-feature\" statements applied to any key leafs that do not also apply to the parent list node.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST", "MUST NOT" ], "example_or_code": false, "id": "rfc9907-4.5-5" }, { "text": "There SHOULD NOT be any \"when\" statements applied to a key leaf node. It is possible that a \"when\" statement for an ancestor node of a key leaf will have the exact node-set result as the key leaf. In such a case, the \"when\" statement for the key leaf is redundant and SHOULD be avoided.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.5-6" }, { "text": "Some modules use a \"case + when\" construct but provide duplicated information (e.g., the \"when\" statements are constraining a single case in the choice as shown in the example below). Such constructs with duplicated information SHOULD NOT be used.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.5-7" }, { "text": "leaf type { type enumeration { enum a; enum b; enum c; } mandatory true; } choice type-choice { case b { container type-b { when \"../type = 'b'\"; leaf foo { type string; } } } case c { container type-c { when \"../type = 'c'\"; leaf bar { mandatory true; type string; } } } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.5-8" }, { "text": "The following example removes the duplicated information:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.5-9" }, { "text": "leaf type { type enumeration { enum a; enum b; enum c; } mandatory true; } container type-b { when \"../type = 'b'\"; leaf foo { type string; } } container type-c { when \"../type = 'c'\"; leaf bar { mandatory true; type string; } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.5-10" }, { "text": "Note that the use of \"case + when\" is still useful in cases where complementary modeling constraints should be expressed. See the example provided below:", "candidate_types": [ "advice" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.5-11" }, { "text": "leaf type { type enumeration { enum a; enum b; enum c; } } choice second-type { mandatory true; case foo { container foo { presence \"When present, indicates type foo\"; leaf foo-attribute { type string; } } } case b { container bar { when \"../type = 'a' or ../type = 'b'\"; presence \"When present, indicates type bar\"; leaf bar-attribute { type string; } } } case c { container baz { when \"../type = 'c'\"; leaf baz-attribute { mandatory true; type string; } } } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.5-12" }, { "text": "Section 8.1 of [RFC7950] includes provisions for defining constraints on state data and specifies that a constraint must be true in a valid state data tree. However, Section 5.3 of [RFC8342] softens that behavior by allowing semantic constraints to be violated under some circumstances to help to detect anomalies. Relaxing validation constraints on state data is meant to reveal deviations of the observed behavior versus intended behavior of a managed entity and hopefully trigger corrective actions by a management system. From that perspective, it is RECOMMENDED to avoid defining constraints on state data that would hinder the detection by a management system of abnormal behaviors of a managed entity.", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "RECOMMENDED" ], "example_or_code": false, "id": "rfc9907-4.5-13" } ] }, { "number": "4.6", "title": "XPath Usage", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.6", "paragraphs": [ { "text": "This section describes guidelines for using the XML Path Language (XPath) [W3C.REC-xpath] within YANG modules.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6-1" } ] }, { "number": "4.6.1", "title": "XPath Evaluation Contexts", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.6.1", "paragraphs": [ { "text": "YANG defines five separate contexts for evaluation of \"XPath\" statements:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.1-1" }, { "text": "1. The \"running\" datastore: collection of all YANG configuration data nodes. The document root is the conceptual container (e.g., \"config\" in the \"edit-config\" operation), which is the parent of all top-level data definition statements with a \"config\" statement value of \"true\".", "candidate_types": [ "definition" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.1-2" }, { "text": "2. State data + the \"running\" datastore: collection of all YANG data nodes. The document root is the conceptual container, parent of all top-level data definition statements.", "candidate_types": [ "definition" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.1-3" }, { "text": "3. Notification: an event notification document. The document root is the notification element.", "candidate_types": [ "definition" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.1-4" }, { "text": "4. RPC Input: The document root is the conceptual \"input\" node, which is the parent of all RPC input parameter definitions.", "candidate_types": [ "definition" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.1-5" }, { "text": "5. RPC Output: The document root is the conceptual \"output\" node, which is the parent of all RPC output parameter definitions.", "candidate_types": [ "definition" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.1-6" }, { "text": "Note that these XPath contexts cannot be mixed. For example, a \"when\" statement in a notification context cannot reference configuration data.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.1-7" }, { "text": "notification foo { leaf mtu { // NOT okay because when-stmt context is this notification when \"/if:interfaces/if:interface[name='eth0']\"; type leafref { // Okay because path-stmt has a different context path \"/if:interfaces/if:interface/if:mtu\"; } } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.1-8" }, { "text": "It is especially important to consider the XPath evaluation context for XPath expressions defined in groupings. An XPath expression defined in a grouping may not be portable, meaning it cannot be used in multiple contexts and produce proper results.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.1-9" }, { "text": "If the XPath expressions defined in a grouping are intended for a particular context, then this context SHOULD be identified in the \"description\" statement for the grouping.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.6.1-10" } ] }, { "number": "4.6.2", "title": "Function Library", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.6.2", "paragraphs": [ { "text": "The \"position\" and \"last\" functions SHOULD NOT be used. This applies to implicit use of the \"position\" function as well (e.g., '//chapter[42]'). A server is only required to maintain the relative XML document order of all instances of a particular user-ordered list or leaf-list. The \"position\" and \"last\" functions MAY be used if they are evaluated in a context where the context node is a user- ordered \"list\" or \"leaf-list\".", "candidate_types": [ "definition", "rule", "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.6.2-1" }, { "text": "The \"id\" function SHOULD NOT be used. The \"ID\" attribute is not present in YANG documents, so this function has no meaning. The XPath execution environment SHOULD return an empty string for this function.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.6.2-2" }, { "text": "The \"namespace-uri\" and \"name\" functions SHOULD NOT be used. Expanded names in XPath are different than YANG. A specific canonical representation of a YANG-expanded name does not exist.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.6.2-3" }, { "text": "The \"lang\" function SHOULD NOT be used. This function does not apply to YANG because there is no \"lang\" attribute set with the document. The XPath execution environment SHOULD return \"false\" for this function.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.6.2-4" }, { "text": "The \"local-name\", \"namespace-uri\", \"name\", \"string\", and \"number\" functions SHOULD NOT be used if the argument is a node-set. If so, the function result will be determined by the document order of the node-set. Since this order can be different on each server, the function results can also be different. Any function call that implicitly converts a node-set to a string will also have this issue.", "candidate_types": [ "definition", "advice" ], "uppercase_requirement_words": [ "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.6.2-5" }, { "text": "The \"local-name\" function SHOULD NOT be used to reference local names outside of the YANG module that defines the \"must\" or \"when\" statement containing the \"local-name\" function. Example of a \"local- name\" function that should not be used:", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.6.2-6" }, { "text": "/*[local-name()='foo']", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.2-7" }, { "text": "The \"derived-from-or-self\" function SHOULD be used instead of an equality expression for identityref values. This allows the identities to be conceptually augmented.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.6.2-8" }, { "text": "Example:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.2-9" }, { "text": "// assume \"ex\" is the prefix of the module where the identity // name-format-null is defined", "candidate_types": [ "definition" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.2-10" }, { "text": "// do not use when \"md-name-format = 'name-format-null'\";", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.2-11" }, { "text": "// this is preferred when \"derived-from-or-self(md-name-format, 'ex:name-format-null')\";", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.2-12" } ] }, { "number": "4.6.3", "title": "Axes", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.6.3", "paragraphs": [ { "text": "The \"attribute\" and \"namespace\" axes are not supported in YANG and MAY be empty in a NETCONF or RESTCONF server implementation.", "candidate_types": [ "permission" ], "uppercase_requirement_words": [ "MAY" ], "example_or_code": false, "id": "rfc9907-4.6.3-1" }, { "text": "The \"preceding\" and \"following\" axes SHOULD NOT be used. These constructs rely on XML document order within a NETCONF or RESTCONF server configuration database, which may not be supported consistently or produce reliable results across implementations. Predicate expressions based on static node properties (e.g., element name or value, and \"ancestor\" or \"descendant\" axes) SHOULD be used instead. The \"preceding\" and \"following\" axes MAY be used if document order is not relevant to the outcome of the expression (e.g., check for global uniqueness of a parameter value).", "candidate_types": [ "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.6.3-2" }, { "text": "The \"preceding-sibling\" and \"following-sibling\" axes SHOULD NOT be used; however, they MAY be used if document order is not relevant to the outcome of the expression.", "candidate_types": [ "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.6.3-3" }, { "text": "A server is only required to maintain the relative XML document order of all instances of a particular user-ordered list or leaf-list. The \"preceding-sibling\" and \"following-sibling\" axes MAY be used if they are evaluated in a context where the context node is a user-ordered \"list\" or \"leaf-list\".", "candidate_types": [ "definition", "rule", "permission" ], "uppercase_requirement_words": [ "MAY" ], "example_or_code": false, "id": "rfc9907-4.6.3-4" } ] }, { "number": "4.6.4", "title": "Types", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.6.4", "paragraphs": [ { "text": "Data nodes that use the \"int64\" and \"uint64\" built-in type SHOULD NOT be used within numeric or boolean expressions. There are boundary conditions in which the translation from the YANG 64-bit type to an XPath number can cause incorrect results. Specifically, an XPath \"double\" precision floating-point number cannot represent very large positive or negative 64-bit numbers because it only provides a total precision of 53 bits. The \"int64\" and \"uint64\" data types MAY be used in numeric expressions if the value can be represented with no more than 53 bits of precision.", "candidate_types": [ "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.6.4-1" }, { "text": "Data modelers need to be careful not to confuse the YANG value space and the XPath value space. The data types are not the same in both, and conversion between YANG and XPath data types SHOULD be considered carefully.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.6.4-2" }, { "text": "Explicit XPath data type conversions MAY be used (e.g., \"string\", \"boolean\", or \"number\" functions), instead of implicit XPath data type conversions.", "candidate_types": [ "permission" ], "uppercase_requirement_words": [ "MAY" ], "example_or_code": false, "id": "rfc9907-4.6.4-3" }, { "text": "XPath expressions that contain a literal value representing a YANG identity SHOULD always include the declared prefix of the module where the identity is defined.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.6.4-4" }, { "text": "XPath expressions for \"when\" statements SHOULD NOT reference the context node or any descendant nodes of the context node. They MAY reference descendant nodes if the \"when\" statement is contained within an \"augment\" statement and the referenced nodes are not defined within the \"augment\" statement.", "candidate_types": [ "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.6.4-5" }, { "text": "Example:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.4-6" }, { "text": "augment \"/rt:active-route/rt:input/rt:destination-address\" { when \"derived-from-or-self(rt:address-family, \" + \"'v4ur:ipv4-unicast')\" { description \"This augment is valid only for IPv4 unicast.\"; } // nodes defined here within the augment-stmt // cannot be referenced in the when-stmt }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.4-7" } ] }, { "number": "4.6.5", "title": "Wildcards", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.6.5", "paragraphs": [ { "text": "It is possible to construct XPath expressions that will evaluate differently when combined with several modules within a server implementation rather than when evaluated within the single module. This is due to augmenting nodes from other modules.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.5-1" }, { "text": "Wildcard expansion is done within a server against all the nodes from all namespaces, so it is possible for a \"must\" or \"when\" statement that uses the '*' operator to always evaluate to false if processed within a single YANG module. In such cases, the \"description\" statement SHOULD clarify that augmenting objects are expected to match the wildcard expansion.", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.6.5-2" }, { "text": "when /foo/services/*/active { description \"No services directly defined in this module. Matches objects that have augmented the services container.\"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.5-3" } ] }, { "number": "4.6.6", "title": "Boolean Expressions", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.6.6", "paragraphs": [ { "text": "The YANG \"must\" and \"when\" statements use an XPath boolean expression to define the test condition for the statement. It is important to specify these expressions in a way that will not cause inadvertent changes in the result if the objects referenced in the expression are updated in future revisions of the module.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.6-1" }, { "text": "For example, the leaf \"foo2\" must exist if the leaf \"foo1\" is equal to \"one\" or \"three\":", "candidate_types": [ "rule" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.6-2" }, { "text": "leaf foo1 { type enumeration { enum one; enum two; enum three; } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.6-3" }, { "text": "leaf foo2 { // INCORRECT must \"/f:foo1 != 'two'\"; type string; } leaf foo2 { // CORRECT must \"/f:foo1 = 'one' or /f:foo1 = 'three'\"; type string; }", "candidate_types": [ "rule" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.6-4" }, { "text": "In the next revision of the module, leaf \"foo1\" is extended with a new enum named \"four\":", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.6-5" }, { "text": "leaf foo1 { type enumeration { enum one; enum two; enum three; enum four; } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.6-6" }, { "text": "Now the first XPath expression will allow the enum \"four\" to be accepted in addition to the \"one\" and \"three\" enum values.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.6.6-7" } ] }, { "number": "4.7", "title": "YANG Definition Lifecycle Management", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.7", "paragraphs": [ { "text": "The YANG status statement MUST be present within a definition if its value is \"deprecated\" or \"obsolete\". The status SHOULD NOT be changed from \"current\" directly to \"obsolete\". An object SHOULD be available for at least one year after the publication date with a \"deprecated\" status before it is changed to \"obsolete\".", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "MUST", "SHOULD", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.7-1" }, { "text": "The module or submodule name MUST NOT be changed once the document containing the module or submodule is published.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST NOT" ], "example_or_code": false, "id": "rfc9907-4.7-2" }, { "text": "The module namespace URI value MUST NOT be changed once the document containing the module is published.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST NOT" ], "example_or_code": false, "id": "rfc9907-4.7-3" }, { "text": "The revision date substatement within the \"import\" statement SHOULD be present if any groupings are used from the external module.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.7-4" }, { "text": "The revision date substatement within the \"include\" statement SHOULD be present if any groupings are used from the external submodule.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.7-5" }, { "text": "If an \"import\" statement is for a module from a stable source (e.g., an RFC for an IETF module), then a reference-stmt SHOULD be present within an \"import\" statement.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.7-6" }, { "text": "import ietf-yang-types { prefix yang; reference \"RFC 9911: Common YANG Data Types\"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.7-7" }, { "text": "If submodules are used, then the document containing the main module MUST be updated so that the main module revision date is equal to or more recent than the revision date of any submodule that is (directly or indirectly) included by the main module.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.7-8" }, { "text": "Definitions for future use SHOULD NOT be specified in a module. Do not specify placeholder objects like the \"reserved\" example below:", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.7-9" }, { "text": "leaf reserved { type string; description \"This object has no purpose at this time, but a future revision of this module might define a purpose for this object.\"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.7-10" } ] }, { "number": "4.8", "title": "Module Header, Meta, and Revision Statements", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.8", "paragraphs": [ { "text": "For published modules, the namespace MUST be a globally unique URI, as defined in [RFC3986]. This value is usually assigned by the IANA.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.8-1" }, { "text": "The \"organization\" statement MUST be present. If the module is contained in a document intended for IETF Standards Track status, then the organization SHOULD be the IETF working group (WG) chartered to write the document. Exceptions include (but are not limited to): example modules, IANA-maintained YANG modules, or modules contained in AD-sponsored documents. For other standards organizations, a similar approach is also suggested.", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "MUST", "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.8-2" }, { "text": "The \"contact\" statement MUST be present. If the module is contained in a document intended for Standards Track status, then the WG web and mailing information SHOULD be present, and the main document author or editor contact information SHOULD be present. If additional authors or editors exist, their contact information MAY be present. There is no need to include the contact information for WG Chairs.", "candidate_types": [ "rule", "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "MUST", "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.8-3" }, { "text": "The \"description\" statement MUST be present. For modules published within IETF documents, the appropriate IETF Trust Copyright text MUST be present, as described in Section 3.1, and MUST contain the following statement:", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.8-4" }, { "text": "| All revisions of IETF and IANA published modules can be found at | the \"YANG Parameters\" registry group: | .", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.8-5" }, { "text": "If the module relies on information contained in other documents, which are not the same documents implied by the \"import\" statements present in the module, then these documents MUST be identified in the \"reference\" statement.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.8-6" }, { "text": "A \"revision\" statement MUST be present for each published version of the module. The \"revision\" statement MUST have a \"reference\" substatement. It MUST identify the published document that contains the module. Modules are often extracted from their original documents, and it is useful for developers and operators to know how to find the original source document in a consistent manner. The \"revision\" statement MAY have a \"description\" substatement. For convenience, the description text of a new published revision may summarize any changes made to a module compared to the previous published revision. Typically, that list is a YANG-specific subset of the summary of changes listing any changes made from the RFC being updated or obsoleted as per [ID-Guidelines].", "candidate_types": [ "definition", "rule", "permission" ], "uppercase_requirement_words": [ "MAY", "MUST" ], "example_or_code": false, "id": "rfc9907-4.8-7" }, { "text": "The following example shows the \"revision\" statement for a published YANG module:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.8-8" }, { "text": "revision 2010-09-24 { description \"Initial revision.\"; reference \"RFC 6021: Common YANG Data Types\"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.8-9" }, { "text": "The following example shows the \"revision\" statements for a published YANG module that updates a published module. The new \"revision\" statement summarizes the changes compared to the previous published revision.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.8-10" }, { "text": "revision 2013-07-15 { description \"This revision adds the following new data types: - yang:yang-identifier - yang:hex-string - yang:uuid - yang:dotted-quad\"; reference \"RFC 6991: Common YANG Data Types\"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.8-11" }, { "text": "revision 2010-09-24 { description \"Initial revision.\"; reference \"RFC 6021: Common YANG Data Types\"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.8-12" }, { "text": "For an unpublished module, a complete history of each unpublished module revision is not required. That is, within a sequence of draft versions, only the most recent revision need be recorded in the module. Do not remove or reuse a \"revision\" statement for a published module. A new revision date is not required unless the module contents have changed. If the module contents have changed, then the revision date of that new module version MUST be updated to a date later than that of the previous version.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.8-13" }, { "text": "The following example shows the \"revision\" statements for an unpublished update to a published YANG module. The latest \"revision\" statement of the unpublished module summarizes the changes compared to the previous revision.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.8-14" }, { "text": "revision 2025-12-22 { description \"This revision adds the following new data types: - yang:date - yang:date-no-zone - yang:time - yang:time-no-zone - yang:hours32 - yang:minutes32 - yang:seconds32 - yang:centiseconds32 - yang:milliseconds32 - yang:microseconds32 - yang:microseconds64 - yang:nanoseconds32 - yang:nanoseconds64 - yang:language-tag The yang-identifier definition has been aligned with YANG 1.1 and types representing time support the representation of leap seconds. The representation of time zone offsets has been aligned with RFC 9557. Several description and pattern statements have been improved.\"; reference \"RFC 9911: Common YANG Data Types\"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.8-15" }, { "text": "revision 2013-07-15 { description \"This revision adds the following new data types: - yang:yang-identifier - yang:hex-string - yang:uuid - yang:dotted-quad\"; reference \"RFC 6991: Common YANG Data Types\"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.8-16" }, { "text": "revision 2010-09-24 { description \"Initial revision.\"; reference \"RFC 6021: Common YANG Data Types\"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.8-17" } ] }, { "number": "4.9", "title": "Namespace Assignments", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.9", "paragraphs": [ { "text": "It is RECOMMENDED that only valid YANG modules be included in documents, whether or not the modules are published yet. This allows:", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "RECOMMENDED" ], "example_or_code": false, "id": "rfc9907-4.9-1" }, { "text": "* the module to compile correctly instead of generating disruptive fatal errors.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-2" }, { "text": "* early implementors to use the modules without picking a random value for the XML namespace.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-3" }, { "text": "* early interoperability testing since independent implementations will use the same XML namespace value.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-4" }, { "text": "Until a URI is assigned by the IANA, a proposed namespace URI MUST be provided for the \"namespace\" statement in a YANG module. A value SHOULD be selected that is not likely to collide with other YANG namespaces. Standard module names, prefixes, and URI strings already listed in the \"YANG Module Names\" registry group MUST NOT be used.", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "MUST", "MUST NOT", "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.9-5" }, { "text": "A standard \"namespace\" statement value SHOULD have the following form:", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.9-6" }, { "text": ":", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-7" }, { "text": "The following URN prefix string SHOULD be used for published and unpublished YANG modules:", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.9-8" }, { "text": "urn:ietf:params:xml:ns:yang", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-9" }, { "text": "The following example URNs would be valid \"namespace\" statement values for Standards Track modules:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-10" }, { "text": "urn:ietf:params:xml:ns:yang:ietf-netconf-partial-lock", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-11" }, { "text": "urn:ietf:params:xml:ns:yang:ietf-netconf-state", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-12" }, { "text": "urn:ietf:params:xml:ns:yang:ietf-netconf", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-13" }, { "text": "Note that a different URN prefix string SHOULD be used for modules that are not Standards Track. The string SHOULD be selected according to the guidelines in Section 5.3 of [RFC7950].", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.9-14" }, { "text": "The following URIs exemplify what might be used by modules that are not Standards Track. Note that the domain \"example.com\" SHOULD be used by example modules in I-Ds from the IETF Stream. These URIs are not intended to be dereferenced. They are used for module namespace identification only.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.9-15" }, { "text": "Example URIs using URLs per [RFC3986]:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-16" }, { "text": "https://example.com/ns/example-interfaces", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-17" }, { "text": "https://example.com/ns/example-system", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-18" }, { "text": "Example URIs using tags per [RFC4151]:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-19" }, { "text": "tag:example.com,2017:example-interfaces", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-20" }, { "text": "tag:example.com,2017:example-system", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.9-21" } ] }, { "number": "4.10", "title": "Top-Level Data Definitions", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.10", "paragraphs": [ { "text": "The top-level data organization SHOULD be considered carefully, in advance. Data model designers need to consider how the functionality for a given protocol or protocol family will grow over time.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.10-1" }, { "text": "The separation of configuration data and operational state SHOULD be considered carefully. It is sometimes useful to define separate top- level containers for configuration and non-configuration data. For some existing top-level data nodes, configuration data was not in scope, so only one container representing operational state was created. Refer to NMDA [RFC8342] for details.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.10-2" }, { "text": "The number of top-level data nodes within a module SHOULD be minimized. It is often useful to retrieve related information within a single subtree. If data is too distributed, it becomes difficult to retrieve all at once.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.10-3" }, { "text": "The names and data organization SHOULD reflect persistent information, such as the name of a protocol. The name of the working group SHOULD NOT be used because this may change over time.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.10-4" }, { "text": "A mandatory database data definition is defined as a node that a client must provide for the database to be valid. The server is not required to provide a value.", "candidate_types": [ "definition", "rule" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.10-5" }, { "text": "Top-level database data definitions MUST NOT be mandatory. If a mandatory node appears at the top level, it will immediately cause the database to be invalid. This can occur when the server boots or when a module is loaded dynamically at runtime.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST NOT" ], "example_or_code": false, "id": "rfc9907-4.10-6" } ] }, { "number": "4.11", "title": "Data Types", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.11", "paragraphs": [ { "text": "Selection of an appropriate data type (i.e., built-in type, existing derived type, or new derived type) is very subjective; therefore, few requirements can be specified on that subject.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11-1" }, { "text": "Data model designers SHOULD use the most appropriate built-in data type for the particular application.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.11-2" }, { "text": "The signed numeric data types (i.e., \"int8\", \"int16\", \"int32\", and \"int64\") SHOULD NOT be used unless negative values are allowed for the desired semantics.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.11-3" } ] }, { "number": "4.11.1", "title": "Fixed-Value Extensibility", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.11.1", "paragraphs": [ { "text": "If the set of values is fixed and the data type contents are controlled by a single naming authority (e.g., IANA), then an \"enumeration\" data type SHOULD be used.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.11.1-1" }, { "text": "leaf foo { type enumeration { enum one; enum two; } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.1-2" }, { "text": "If distributed extensibility or hierarchical organization of enumerated values is required, then the \"identityref\" data type SHOULD be used instead of an \"enumeration\" or other built-in type.", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.11.1-3" }, { "text": "identity foo-type { description \"Base for the extensible type\"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.1-4" }, { "text": "identity one { base f:foo-type; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.1-5" }, { "text": "identity two { base f:foo-type; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.1-6" }, { "text": "leaf foo { type identityref { base f:foo-type; } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.1-7" }, { "text": "Note that any module can declare an identity with base \"foo-type\" that is valid for the \"foo\" leaf. Identityref values are considered to be qualified names.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.1-8" } ] }, { "number": "4.11.2", "title": "Patterns and Ranges", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.11.2", "paragraphs": [ { "text": "For string data types, if a machine-readable pattern can be defined for the desired semantics, then one or more pattern statements SHOULD be present. A single-quoted string SHOULD be used to specify the pattern, since a double-quoted string can modify the content. If the patterns used in a type definition have known limitations such as false negative or false positive matches, then these limitations SHOULD be documented within the typedef or data definition.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.11.2-1" }, { "text": "The following typedef from [RFC9911] demonstrates the proper use of the \"pattern\" statement:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.2-2" }, { "text": "typedef ipv6-address-no-zone { type inet:ipv6-address { pattern '[0-9a-fA-F:\\.]*'; } ... }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.2-3" }, { "text": "For string data types, if the length of the string is required to be bounded in all implementations, then a \"length\" statement MUST be present.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.11.2-4" }, { "text": "The following typedef from [RFC9911] demonstrates the proper use of the \"length\" statement:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.2-5" }, { "text": "typedef yang-identifier { type string { length \"1..max\"; pattern '[a-zA-Z_][a-zA-Z0-9\\-_.]*'; pattern '.|..|[^xX].*|.[^mM].*|..[^lL].*'; } ... }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.2-6" }, { "text": "For numeric data types, if the values allowed by the intended semantics are different than those allowed by the unbounded intrinsic data type (e.g., \"int32\"), then a range statement SHOULD be present.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.11.2-7" }, { "text": "The following typedef from [RFC9911] demonstrates the proper use of the \"range\" statement:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.2-8" }, { "text": "typedef dscp { type uint8 { range \"0..63\"; } ... }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.2-9" } ] }, { "number": "4.11.3", "title": "Enumerations and Bits", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.11.3", "paragraphs": [ { "text": "For \"enumeration\" or \"bits\" data types, the semantics for each \"enum\" or \"bit\" SHOULD be documented. A separate \"description\" statement (within each \"enum\" or \"bit\" statement) SHOULD be present.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.11.3-1" }, { "text": "leaf foo { // INCORRECT type enumeration { enum one; enum two; } description \"The foo enum... one: The first enum two: The second enum\"; } leaf foo { // CORRECT type enumeration { enum one { description \"The first enum\"; } enum two { description \"The second enum\"; } } description \"The foo enum... \"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.3-2" } ] }, { "number": "4.11.4", "title": "Union Types", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.11.4", "paragraphs": [ { "text": "The YANG \"union\" type is evaluated by testing a value against each member type in the union. The first type definition that accepts a value as valid is the member type used. In general, member types SHOULD be ordered from most restrictive to least restrictive types.", "candidate_types": [ "definition", "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.11.4-1" }, { "text": "In the following example, the \"enumeration\" type will never be matched because the preceding \"string\" type will match everything.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.4-2" }, { "text": "Incorrect:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.4-3" }, { "text": "type union { type string; type enumeration { enum up; enum down; } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.4-4" }, { "text": "Correct:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.4-5" }, { "text": "type union { type enumeration { enum up; enum down; } type string; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.4-6" }, { "text": "It is possible for different member types to match, depending on the input encoding format. In XML, all values are passed as string nodes; but in JSON, there are different value types for numbers, booleans, and strings.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.4-7" }, { "text": "In the following example, a JSON numeric value will always be matched by the \"int32\" type, but in XML the string value representing a number will be matched by the \"string\" type. The second version will match the \"int32\" member type no matter how the input is encoded.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.4-8" }, { "text": "Incorrect:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.4-9" }, { "text": "type union { type string; type int32; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.4-10" }, { "text": "Correct:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.4-11" }, { "text": "type union { type int32; type string; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.4-12" } ] }, { "number": "4.11.5", "title": "Empty and Boolean", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.11.5", "paragraphs": [ { "text": "YANG provides an \"empty\" data type, which has one value (i.e., present). The default is \"not present\", which is not actually a value. When used within a list key, only one value can (and must) exist for this key leaf. The type \"empty\" SHOULD NOT be used for a key leaf since it is pointless.", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.11.5-1" }, { "text": "There is really no difference between a leaf of type \"empty\" and a leaf-list of type \"empty\". Both are limited to one instance. The type \"empty\" SHOULD NOT be used for a leaf-list.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.11.5-2" }, { "text": "The advantage of using type \"empty\" instead of type \"boolean\" is that the default (not present) does not take up any bytes in a representation. The disadvantage is that the client may not be sure if an empty leaf is missing because it was filtered somehow or not implemented. The client may not have a complete and accurate schema for the data returned by the server and may not be aware of the missing leaf.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.5-3" }, { "text": "The YANG \"boolean\" data type provides two values (\"true\" and \"false\"). When used within a list key, two entries can exist for this key leaf. Default values are ignored for key leafs, but a default statement is often used for plain boolean leafs. The advantage of the \"boolean\" type is that the leaf or leaf-list has a clear representation for both values. The default value is usually not returned unless explicitly requested by the client, so no bytes are used in a typical representation.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.5-4" }, { "text": "In general, the \"boolean\" data type SHOULD be used instead of the \"empty\" data type, as shown in the example below:", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.11.5-5" }, { "text": "Incorrect:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.5-6" }, { "text": "leaf flag1 { type empty; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.5-7" }, { "text": "Correct:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.5-8" }, { "text": "leaf flag2 { type boolean; default false; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.11.5-9" } ] }, { "number": "4.12", "title": "Reusable Type Definitions", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.12", "paragraphs": [ { "text": "If an appropriate derived type exists in any standard module, such as [RFC9911], then it SHOULD be used instead of defining a new derived type.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.12-1" }, { "text": "If an appropriate units identifier can be associated with the desired semantics, then a units statement SHOULD be present.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.12-2" }, { "text": "If an appropriate default value can be associated with the desired semantics, then a default statement SHOULD be present.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.12-3" }, { "text": "If a significant number of derived types are defined, and it is anticipated that these data types will be reused by multiple modules, then these derived types SHOULD be contained in a separate module or submodule to allow easier reuse without unnecessary coupling.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.12-4" }, { "text": "The \"description\" statement MUST be present.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.12-5" }, { "text": "If the type definition semantics are defined in an external document (other than another YANG module indicated by an \"import\" statement), then the \"reference\" statement MUST be present.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.12-6" } ] }, { "number": "4.13", "title": "Reusable Groupings", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.13", "paragraphs": [ { "text": "A reusable grouping is a YANG grouping that can be imported by another module and is intended for use by other modules. This is not the same as a grouping that is used within the module in which it is defined, but it happens to be exportable to another module because it is defined at the top level of the YANG module.", "candidate_types": [ "definition" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.13-1" }, { "text": "The following guidelines apply to reusable groupings, in order to make them as robust as possible:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.13-2" }, { "text": "* Clearly identify the purpose of the grouping in the \"description\" statement.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.13-3" }, { "text": "* There are five different XPath contexts in YANG (rpc/input, rpc/ output, notification, \"config true\" data nodes, and all data nodes). Clearly identify which XPath contexts are applicable or excluded for the grouping.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.13-4" }, { "text": "* Do not reference data outside the grouping in any \"path\", \"must\", or \"when\" statements.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.13-5" }, { "text": "* Do not include a \"default\" substatement on a leaf or choice unless the value applies on all possible contexts.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.13-6" }, { "text": "* Do not include a \"config\" substatement on a data node unless the value applies on all possible contexts.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.13-7" }, { "text": "* Clearly identify any external dependencies in the grouping \"description\" statement, such as nodes referenced by an absolute path from a \"path\", \"must\", or \"when\" statement.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.13-8" } ] }, { "number": "4.14", "title": "Data Definitions", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.14", "paragraphs": [ { "text": "The \"description\" statement MUST be present in the following YANG statements:", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.14-1" }, { "text": "* anydata", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-2" }, { "text": "* anyxml", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-3" }, { "text": "* augment", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-4" }, { "text": "* choice", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-5" }, { "text": "* container", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-6" }, { "text": "* extension", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-7" }, { "text": "* feature", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-8" }, { "text": "* grouping", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-9" }, { "text": "* identity", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-10" }, { "text": "* leaf", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-11" }, { "text": "* leaf-list", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-12" }, { "text": "* list", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-13" }, { "text": "* notification", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-14" }, { "text": "* rpc", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-15" }, { "text": "* typedef", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-16" }, { "text": "If the data definition semantics are defined in an external document, (other than another YANG module indicated by an \"import\" statement), then a \"reference\" statement MUST be present.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.14-17" }, { "text": "The \"anyxml\" construct may be useful to represent an HTML banner containing markup elements, such as \"\" and \"\", and MAY be used in such cases. However, this construct SHOULD NOT be used if other YANG data node types can be used instead to represent the desired syntax and semantics.", "candidate_types": [ "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.14-18" }, { "text": "It has been found that the \"anyxml\" statement is not implemented consistently across all servers. It is possible that mixed-mode XML will not be supported or that configuration anyxml nodes will not be supported.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-19" }, { "text": "If there are referential integrity constraints associated with the desired semantics that can be represented with XPath, then one or more \"must\" statements SHOULD be present.", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.14-20" }, { "text": "For list and leaf-list data definitions, if the number of possible instances is required to be bounded for all implementations, then the max-elements statements SHOULD be present.", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.14-21" }, { "text": "If any \"must\" or \"when\" statements are used within the data definition, then the data definition \"description\" statement SHOULD describe the purpose of each one.", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.14-22" }, { "text": "The \"choice\" statement is allowed to be directly present within a \"case\" statement in YANG 1.1. This needs to be considered carefully. Consider simply including the nested \"choice\" as additional \"case\" statements within the parent \"choice\" statement. Note that the \"mandatory\" and \"default\" statements within a nested \"choice\" statement only apply if the \"case\" containing the nested \"choice\" statement is first selected.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14-23" }, { "text": "If a list defines any key leafs, then these leafs SHOULD be defined in order, as the first child nodes within the list. The key leafs MAY be in a different order in some cases, e.g., they are defined in a grouping, and not inline in the list statement.", "candidate_types": [ "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.14-24" } ] }, { "number": "4.14.1", "title": "Non-Presence Containers", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.14.1", "paragraphs": [ { "text": "A non-presence container is used to organize data into specific subtrees. It is not intended to have semantics within the data model beyond this purpose, although YANG allows it (e.g., a \"must\" statement within the non-presence container).", "candidate_types": [ "definition", "rule" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14.1-1" }, { "text": "Example using container wrappers:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14.1-2" }, { "text": "container top { container foos { list foo { ... } } container bars { list bar { ... } } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14.1-3" }, { "text": "Example without container wrappers:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14.1-4" }, { "text": "container top { list foo { ... } list bar { ... } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14.1-5" }, { "text": "Use of non-presence containers to organize data is a subjective matter similar to use of subdirectories in a file system. Although these containers do not have any semantics, they can impact protocol operations for the descendant data nodes within a non-presence container, so use of these containers SHOULD be considered carefully.", "candidate_types": [ "definition", "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.14.1-6" }, { "text": "The NETCONF and RESTCONF protocols do not currently support the ability to delete all list (or leaf-list) entries at once. This deficiency is sometimes avoided by use of a parent container (i.e., deleting the container also removes all child entries).", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14.1-7" } ] }, { "number": "4.14.2", "title": "Top-Level Data Nodes", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.14.2", "paragraphs": [ { "text": "Use of top-level objects needs to be considered carefully:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14.2-1" }, { "text": "* top-level siblings are not ordered", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14.2-2" }, { "text": "* top-level siblings are not static and depend on the modules that are loaded", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14.2-3" }, { "text": "* for subtree filtering, retrieval of a top-level leaf-list will be treated as a content-match node for all top-level-siblings", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14.2-4" }, { "text": "* a top-level list with many instances may impact performance", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.14.2-5" } ] }, { "number": "4.15", "title": "Operation Definitions", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.15", "paragraphs": [ { "text": "If the operation semantics are defined in an external document (other than another YANG module indicated by an \"import\" statement), then a \"reference\" statement MUST be present.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.15-1" }, { "text": "If the operation impacts system behavior in some way, it SHOULD be mentioned in the \"description\" statement.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.15-2" }, { "text": "If the operation is potentially harmful to system behavior in some way, it MUST be mentioned in the Security Considerations section of the document.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.15-3" } ] }, { "number": "4.16", "title": "Notification Definitions", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.16", "paragraphs": [ { "text": "The \"description\" statement MUST be present.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.16-1" }, { "text": "If the notification semantics are defined in an external document (other than another YANG module indicated by an \"import\" statement), then a \"reference\" statement MUST be present.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.16-2" }, { "text": "If the notification refers to a specific resource instance, then this instance SHOULD be identified in the notification data. This is usually done by including \"leafref\" leaf nodes with the key leaf values for the resource instance. For example:", "candidate_types": [ "definition", "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.16-3" }, { "text": "notification interface-up { description \"Sent when an interface is activated.\"; leaf name { type leafref { path \"/if:interfaces/if:interface/if:name\"; } } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.16-4" }, { "text": "Note that there are no formal YANG statements to identify any data node resources associated with a notification. The \"description\" statement for the notification SHOULD specify if and how the notification identifies any data node resources associated with the specific event.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.16-5" } ] }, { "number": "4.17", "title": "Feature Definitions", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.17", "paragraphs": [ { "text": "The YANG \"feature\" statement is used to define a label for a set of optional functionality within a module. The \"if-feature\" statement is used in the YANG statements associated with a feature. The description-stmt within a feature-stmt MUST specify any interactions with other features.", "candidate_types": [ "definition", "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.17-1" }, { "text": "The set of YANG features defined in a module should be considered carefully. Very fine granular features increase interoperability complexity and should be avoided. A likely misuse of the feature mechanism is the tagging of individual leafs (e.g., counters) with separate features.", "candidate_types": [ "definition", "advice" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.17-2" }, { "text": "If there is a large set of objects associated with a YANG feature, then consider moving those objects to a separate module instead of using a YANG feature. Note that the set of features within a module is easily discovered by the reader, but the set of related modules within the entire YANG library is not as easy to identify. Module names with a common prefix can help readers identify the set of related modules, but this assumes the reader will have discovered and installed all the relevant modules.", "candidate_types": [ "definition" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.17-3" }, { "text": "Another consideration for deciding whether to create a new module or add a YANG feature is the stability of the module in question. It may be desirable to have a stable base module that is not changed frequently. If new functionality is placed in a separate module, then the base module does not need to be republished. If it is designed as a YANG feature, then the module will need to be republished.", "candidate_types": [ "definition" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.17-4" }, { "text": "If one feature requires implementation of another feature, then an \"if-feature\" statement SHOULD be used in the dependent \"feature\" statement.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.17-5" }, { "text": "For example, feature2 requires implementation of feature1:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.17-6" }, { "text": "feature feature1 { description \"Some protocol feature\"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.17-7" }, { "text": "feature feature2 { if-feature \"feature1\"; description \"Another protocol feature\"; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.17-8" } ] }, { "number": "4.18", "title": "YANG Data Node Constraints", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.18", "paragraphs": [] }, { "number": "4.18.1", "title": "Controlling Quantity", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.18.1", "paragraphs": [ { "text": "The \"min-elements\" and \"max-elements\" statements can be used to control how many list or leaf-list instances are required for a particular data node. YANG constraint statements SHOULD be used to identify conditions that apply to all implementations of the data model. If platform-specific limitations (e.g., the \"max-elements\" supported for a particular list) are relevant to operations, then a data model definition statement (e.g., \"max-ports\" leaf) SHOULD be used to identify the limit.", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.18.1-1" } ] }, { "number": "4.18.2", "title": "\"must\" versus \"when\"", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.18.2", "paragraphs": [ { "text": "\"must\" and \"when\" YANG statements are used to provide cross-object referential tests. They have very different behavior. The \"when\" statement causes data node instances to be silently deleted as soon as the condition becomes false. A false \"when\" statement is not considered to be an error.", "candidate_types": [ "definition", "rule" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.18.2-1" }, { "text": "The \"when\" statement SHOULD be used together with \"augment\" or \"uses\" statements to achieve conditional model composition. The condition SHOULD be based on static properties of the augmented entry (e.g., list key leafs).", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.18.2-2" }, { "text": "The \"must\" statement causes a datastore validation error if the condition is false. This statement SHOULD be used for enforcing parameter value restrictions that involve more than one data node (e.g., end-time parameter must be after the start-time parameter).", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.18.2-3" } ] }, { "number": "4.19", "title": "\"augment\" Statements", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.19", "paragraphs": [ { "text": "The YANG \"augment\" statement is used to define a set of data definition statements that will be added as child nodes of a target data node. The module namespace for these data nodes will be the augmenting module, not the augmented module.", "candidate_types": [ "definition" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19-1" }, { "text": "A top-level \"augment\" statement SHOULD NOT be used if the target data node is in the same module or submodule as the evaluated \"augment\" statement. The data definition statements SHOULD be added inline instead.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.19-2" } ] }, { "number": "4.19.1", "title": "Conditional Augment Statements", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.19.1", "paragraphs": [ { "text": "The \"augment\" statement is often used together with the \"when\" statement and/or \"if-feature\" statement to make the augmentation conditional on some portion of the data model.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.1-1" }, { "text": "The following example from [RFC8343] shows how a conditional container called \"ethernet\" is added to the \"interface\" list only for entries of the type \"ethernetCsmacd\".", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.1-2" }, { "text": "augment \"/if:interfaces/if:interface\" { when \"if:type = 'ianaift:ethernetCsmacd'\";", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.1-3" }, { "text": "container ethernet { leaf duplex { ... } } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.1-4" } ] }, { "number": "4.19.2", "title": "Conditionally Mandatory Data Definition Statements", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.19.2", "paragraphs": [ { "text": "YANG has very specific rules about how configuration data can be updated in new releases of a module. These rules allow an \"old client\" to continue interoperating with a \"new server\".", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.2-1" }, { "text": "If data nodes are added to an existing entry, the old client MUST NOT be required to provide any mandatory parameters that were not in the original module definition.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST NOT" ], "example_or_code": false, "id": "rfc9907-4.19.2-2" }, { "text": "It is possible to add conditional \"augment\" statements such that the old client would not know about the new condition and would not specify the new condition. The conditional \"augment\" statement can contain mandatory objects only if the condition is false, unless explicitly requested by the client.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.2-3" }, { "text": "Only a conditional \"augment\" statement that uses the \"when\" statement form of a condition can be used in this manner. The YANG features enabled on the server cannot be controlled by the client in any way, so it is not safe to add mandatory augmenting data nodes based on the \"if-feature\" statement.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.2-4" }, { "text": "The XPath \"when\" statement condition MUST NOT reference data outside of the target data node because the client does not have any control over this external data.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST NOT" ], "example_or_code": false, "id": "rfc9907-4.19.2-5" }, { "text": "In the following sample, it is okay to augment the \"interface\" entry with \"mandatory-leaf\" because the augmentation depends on support for \"some-new-iftype\". The old client does not know about this type, so it would never select this type; therefore, it would not add a mandatory data node.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.2-6" }, { "text": "module example-module {", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.2-7" }, { "text": "yang-version 1.1; namespace \"tag:example.com,2017:example-module\"; prefix mymod;", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.2-8" }, { "text": "import iana-if-type { prefix iana; } import ietf-interfaces { prefix if; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.2-9" }, { "text": "identity some-new-iftype { base iana:iana-interface-type; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.2-10" }, { "text": "augment \"/if:interfaces/if:interface\" { when \"if:type = 'mymod:some-new-iftype'\";", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.2-11" }, { "text": "leaf mandatory-leaf { type string; mandatory true; } } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.2-12" }, { "text": "Note that this practice is safe only for creating data resources. It is not safe for replacing or modifying resources if the client does not know about the new condition. The YANG data model MUST be packaged in a way that requires the client to be aware of the mandatory data nodes if it is aware of the condition for this data. In the example above, the \"some-new-iftype\" identity is defined in the same module as the \"mandatory-leaf\" data definition statement.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.19.2-13" }, { "text": "This practice is not safe for identities defined in a common module such as \"iana-if-type\" because the client is not required to know about \"my-module\" just because it knows about the \"iana-if-type\" module.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.19.2-14" } ] }, { "number": "4.20", "title": "Deviation Statements", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.20", "paragraphs": [ { "text": "Per Section 7.20.3 of [RFC7950], the YANG \"deviation\" statement is not allowed to appear in IETF YANG modules, but it can be useful for documenting server capabilities. Deviation statements are not reusable and typically not shared across all platforms.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.20-1" }, { "text": "There are several reasons that deviations might be needed in an implementation, e.g., an object cannot be supported on all platforms, or feature delivery is done in multiple development phases. Deviation statements can also be used to add annotations to a module, which does not affect the conformance requirements for the module.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.20-2" }, { "text": "It is suggested that deviation statements be defined in separate modules from regular YANG definitions. This allows the deviations to be platform specific and/or temporary.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.20-3" }, { "text": "The order that deviation statements are evaluated can affect the result. Therefore, multiple deviation statements in the same module, for the same target object, SHOULD NOT be used.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.20-4" }, { "text": "The \"max-elements\" statement is intended to describe an architectural limit to the number of list entries. It is not intended to describe platform limitations. It is better to use a \"deviation\" statement for the platforms that have a hard resource limit.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.20-5" }, { "text": "Example documenting platform resource limits:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.20-6" }, { "text": "Wrong: (max-elements in the list itself)", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.20-7" }, { "text": "container backups { list backup { ... max-elements 10; ... } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.20-8" }, { "text": "Correct: (max-elements in a deviation)", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.20-9" }, { "text": "deviation /bk:backups/bk:backup { deviate add { max-elements 10; } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.20-10" } ] }, { "number": "4.21", "title": "Extension Statements", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.21", "paragraphs": [ { "text": "The YANG \"extension\" statement is used to specify external definitions. This appears in the YANG syntax as an \"unknown- statement\". Usage of \"extension\" statements in a published module needs to be considered carefully.", "candidate_types": [ "definition" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.21-1" }, { "text": "The following guidelines apply to the usage of YANG extensions:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.21-2" }, { "text": "* The semantics of the extension MUST NOT contradict any YANG statements. Extensions can add semantics not covered by the normal YANG statements.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST NOT" ], "example_or_code": false, "id": "rfc9907-4.21-3" }, { "text": "* The module containing the \"extension\" statement MUST clearly identify the conformance requirements for the extension. It should be clear whether all implementations of the YANG module containing the extension need to also implement the extension. If not, identify what conditions apply that would require implementation of the extension.", "candidate_types": [ "rule", "advice" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.21-4" }, { "text": "* The extension MUST clearly identify where it can be used within other YANG statements.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.21-5" }, { "text": "* The extension MUST clearly identify if YANG statements or other extensions are allowed or required within the extension as substatements.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.21-6" } ] }, { "number": "4.22", "title": "Data Correlation", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.22", "paragraphs": [ { "text": "Data can be correlated in various ways, using common data types, common data naming, and common data organization. There are several ways to extend the functionality of a module, based on the degree of coupling between the old and new functionality:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.22-1" }, { "text": "inline: update the module with new protocol-accessible objects. The naming and data organization of the original objects is used. The new objects are in the original module namespace.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.22-2" }, { "text": "augment: create a new module with new protocol-accessible objects that augment the original data structure. The naming and data organization of the original objects is used. The new objects are in the new module namespace.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.22-3" }, { "text": "mirror: create new objects in a new module or the original module, except use a new naming scheme and data location. The naming can be coupled in different ways. Tight coupling is achieved with a \"leafref\" data type, with the \"require-instance\" substatement set to \"true\". This method SHOULD be used.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.22-4" }, { "text": "If the new data instances are not limited to the values in use in the original data structure, then the \"require-instance\" substatement MUST be set to \"false\". Loose coupling is achieved by using key leafs with the same data type as the original data structure. This has the same semantics as setting the \"require-instance\" substatement to \"false\".", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.22-5" }, { "text": "The relationship between configuration and operational state has been clarified in NMDA [RFC8342].", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.22-6" } ] }, { "number": "4.22.1", "title": "Use of \"leafref\" for Key Correlation", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.22.1", "paragraphs": [ { "text": "Sometimes it is not practical to augment a data structure. For example, the correlated data could have different keys or contain mandatory nodes.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.22.1-1" }, { "text": "The following example shows the use of the \"leafref\" data type for data correlation purposes:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.22.1-2" }, { "text": "Not preferred:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.22.1-3" }, { "text": "list foo { key name; leaf name { type string; } ... }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.22.1-4" }, { "text": "list foo-addon { key name; config false; leaf name { type string; } ... }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.22.1-5" }, { "text": "Preferred:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.22.1-6" }, { "text": "list foo { key name; leaf name { type string; } ... }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.22.1-7" }, { "text": "list foo-addon { key name; config false; leaf name { type leafref { path \"/foo/name\"; require-instance false; } } leaf addon { type string; mandatory true; } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.22.1-8" } ] }, { "number": "4.23", "title": "Operational State", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.23", "paragraphs": [ { "text": "The modeling of operational state with YANG has been refined over time. At first, only data that has a \"config\" statement value of \"false\" was considered to be operational state. This data was not considered to be part of any datastore, which made the YANG XPath definition much more complicated.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23-1" }, { "text": "Operational state is now modeled using YANG according to the NMDA [RFC8342] and conceptually contained in the operational state datastore, which also includes the operational values of configuration data. There is no longer any need to duplicate data structures to provide separate configuration and operational state sections.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23-2" }, { "text": "This section describes some data modeling issues related to operational state and guidelines for transitioning YANG data model design to be NMDA compatible.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23-3" } ] }, { "number": "4.23.1", "title": "Combining Operational State and Configuration Data", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.23.1", "paragraphs": [ { "text": "If possible, operational state SHOULD be combined with its associated configuration data. This prevents duplication of key leafs and ancestor nodes. It also prevents race conditions for retrieval of dynamic entries and allows configuration and operational state to be retrieved together with minimal message overhead.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.23.1-1" }, { "text": "container foo { ... // contains \"config true\" and \"config false\" nodes that have // no corresponding \"config true\" object (e.g., counters) }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23.1-2" } ] }, { "number": "4.23.2", "title": "Representing Operational Values of Configuration Data", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.23.2", "paragraphs": [ { "text": "If possible, the same data type SHOULD be used to represent the configured value and the operational value, for a given leaf or leaf- list object.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.23.2-1" }, { "text": "Sometimes the configured value set is different than the operational value set for that object, for example, the \"admin-status\" and \"oper- status\" leafs in [RFC8343]. In this case, a separate object MAY be used to represent the configured and operational values.", "candidate_types": [ "permission" ], "uppercase_requirement_words": [ "MAY" ], "example_or_code": false, "id": "rfc9907-4.23.2-2" }, { "text": "Sometimes the list keys are not identical for configuration data and the corresponding operational state. In this case, separate lists MAY be used to represent the configured and operational values.", "candidate_types": [ "permission" ], "uppercase_requirement_words": [ "MAY" ], "example_or_code": false, "id": "rfc9907-4.23.2-3" }, { "text": "If it is not possible to combine configuration and operational state, then the keys used to represent list entries SHOULD be the same type. The \"leafref\" data type SHOULD be used in operational state for key leafs that have corresponding configuration instances. The \"require- instance\" statement MAY be set to \"false\" (in YANG 1.1 modules only) to indicate instances are allowed in the operational state that do not exist in the associated configuration data.", "candidate_types": [ "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.23.2-4" }, { "text": "The need to replicate objects or define different operational state objects depends on the data model. It is not possible to define one approach that will be optimal for all data models.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23.2-5" }, { "text": "Designers SHOULD describe and justify any NMDA exceptions in detail, such as the use of separate subtrees and/or separate leafs. The \"description\" statements for both the configuration and the operational state SHOULD be used for this purpose.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.23.2-6" } ] }, { "number": "4.23.3", "title": "NMDA Transition Guidelines", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.23.3", "paragraphs": [ { "text": "YANG modules SHOULD be designed with the assumption that they will be used on servers supporting the operational state datastore. With this in mind, YANG modules SHOULD define \"config false\" nodes wherever they make sense to the data model. \"Config false\" nodes SHOULD NOT be defined to provide the operational value for configuration nodes, except when the value space of a configured and operational value may differ, in which case a distinct \"config false\" node SHOULD be defined to hold the operational value for the configured node.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.23.3-1" }, { "text": "The following guidelines are meant to help modelers develop YANG modules that will maximize the utility of the module with both current and new implementations.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23.3-2" }, { "text": "New modules and modules that are not concerned with the operational state of configuration information SHOULD immediately be structured to be NMDA compatible, as described in Section 4.23.1. This transition MAY be deferred if the module does not contain any configuration datastore objects.", "candidate_types": [ "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.23.3-3" }, { "text": "The remaining are options that MAY be followed during the time that NMDA mechanisms are being defined.", "candidate_types": [ "permission" ], "uppercase_requirement_words": [ "MAY" ], "example_or_code": false, "id": "rfc9907-4.23.3-4" }, { "text": "(a) Modules that require immediate support for the NMDA features SHOULD be structured for NMDA. A temporary non-NMDA version of this type of module MAY exist, as either an existing module or a module created by hand or with suitable tools that mirror the current modeling strategies. Both the NMDA and the non-NMDA modules SHOULD be published in the same document, with NMDA modules in the document main body and the non-NMDA modules in a non-normative appendix. The use of the non-NMDA module will allow temporary bridging of the time period until NMDA implementations are available.", "candidate_types": [ "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.23.3-5" }, { "text": "(b) For published modules, the module should be republished with an NMDA-compatible structure, deprecating non-NMDA constructs. For example, the \"ietf-interfaces\" module in [RFC7223] has been restructured as an NMDA-compatible module in [RFC8343] (which obsoletes [RFC7223]). The \"/interfaces-state\" hierarchy has been marked with \"status deprecated\". Modules that mark their \"/foo-state\" hierarchy with \"status deprecated\" will allow NMDA- capable implementations to avoid the cost of duplicating the state nodes, while enabling non-NMDA-capable implementations to utilize them for access to the operational values.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23.3-6" }, { "text": "(c) For modules that augment modules that have not been structured with the NMDA, the modeler will have to consider the structure of the base module and the guidelines listed above. Where possible, such modules should move to new revisions of the base module that are NMDA compatible. When that is not possible, augmenting \"state\" containers SHOULD be avoided, with the expectation that the base module will be re-released with the state containers marked as \"deprecated\". It is RECOMMENDED to augment only the \"/foo\" hierarchy of the base module. Where this recommendation cannot be followed, any new \"state\" elements SHOULD be included in their own module.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "RECOMMENDED", "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.23.3-7" } ] }, { "number": "4.23.3.1", "title": "Temporary Non-NMDA Modules", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.23.3.1", "paragraphs": [ { "text": "A temporary non-NMDA module allows a non-NMDA-aware client to access operational state from an NMDA-compliant server. It contains the top-level \"config false\" data nodes that would have been defined in a legacy YANG module (before NMDA).", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23.3.1-1" }, { "text": "A server that needs to support both NMDA and non-NMDA clients can advertise both the new NMDA module and the temporary non-NMDA module. A non-NMDA client can use separate \"foo\" and \"foo-state\" subtrees, except the \"foo-state\" subtree is located in a different (temporary) module. The NMDA module can be used by a non-NMDA client to access the conventional configuration datastores and the deprecated operation to access nested \"config false\" data nodes.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23.3.1-2" }, { "text": "To create the temporary non-NMDA module from an NMDA module, the following steps can be taken:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23.3.1-3" }, { "text": "* Change the module name by appending \"-state\" to the original module name.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23.3.1-4" }, { "text": "* Change the namespace by appending \"-state\" to the original namespace value.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23.3.1-5" }, { "text": "* Change the prefix by appending \"-s\" to the original prefix value.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23.3.1-6" }, { "text": "* Add an import to the original module (e.g., for typedef definitions).", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23.3.1-7" }, { "text": "* Retain or create only the top-level nodes that have a \"config\" statement value \"false\". These subtrees represent \"config false\" data nodes that were combined into the configuration subtree; therefore, they are not available to non-NMDA-aware clients. Set the \"status\" statement to \"deprecated\" for each new node.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.23.3.1-8" }, { "text": "* The module description SHOULD clearly identify the module as a temporary non-NMDA module.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.23.3.1-9" } ] }, { "number": "4.23.3.2", "title": "Example: Create a New NMDA Module", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.23.3.2", "paragraphs": [ { "text": "Create an NMDA-compliant module, using combined configuration and state subtrees, whenever possible.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.2-1" }, { "text": "module example-foo { namespace \"urn:example:params:xml:ns:yang:example-foo\"; prefix \"foo\";", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.2-2" }, { "text": "container foo { // configuration data child nodes // operational value in operational state datastore only // may contain \"config false\" nodes as needed } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.2-3" } ] }, { "number": "4.23.3.3", "title": "Example: Convert an Old Non-NMDA Module", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.23.3.3", "paragraphs": [ { "text": "Do not remove non-compliant objects from existing modules. Instead, change the status to \"deprecated\". At some point, usually after 1 year, the status MAY be changed to \"obsolete\".", "candidate_types": [], "uppercase_requirement_words": [ "MAY" ], "example_or_code": true, "id": "rfc9907-4.23.3.3-1" }, { "text": "Old Module:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.3-2" }, { "text": "module example-foo { namespace \"urn:example:params:xml:ns:yang:example-foo\"; prefix \"foo\";", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.3-3" }, { "text": "container foo { // configuration data child nodes }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.3-4" }, { "text": "container foo-state { config false; // operational state child nodes } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.3-5" }, { "text": "Converted NMDA Module:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.3-6" }, { "text": "module example-foo { namespace \"urn:example:params:xml:ns:yang:example-foo\"; prefix \"foo\";", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.3-7" }, { "text": "container foo { // configuration data child nodes // operational value in operational state datastore only // may contain \"config false\" nodes as needed // will contain any data nodes from old foo-state }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.3-8" }, { "text": "// keep original foo-state but change status to deprecated container foo-state { config false; status deprecated; // operational state child nodes } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.3-9" } ] }, { "number": "4.23.3.4", "title": "Example: Create a Temporary NMDA Module", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.23.3.4", "paragraphs": [ { "text": "Create a new module that contains the top-level operational state data nodes that would have been available before they were combined with configuration data nodes (to be NMDA compliant).", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.4-1" }, { "text": "module example-foo-state { namespace \"urn:example:params:xml:ns:yang:example-foo-state\"; prefix \"foo-s\";", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.4-2" }, { "text": "// import new or converted module; not used in this example import example-foo { prefix foo; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.4-3" }, { "text": "container foo-state { config false; status deprecated; // operational state child nodes } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": true, "id": "rfc9907-4.23.3.4-4" } ] }, { "number": "4.24", "title": "Performance Considerations", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.24", "paragraphs": [ { "text": "It is generally likely that certain YANG statements require more runtime resources than other statements. Although there are no performance requirements for YANG validation, the following information MAY be considered when designing YANG data models:", "candidate_types": [ "permission" ], "uppercase_requirement_words": [ "MAY" ], "example_or_code": false, "id": "rfc9907-4.24-1" }, { "text": "* Lists are generally more expensive than containers", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.24-2" }, { "text": "* \"when\" statement evaluation is generally more expensive than \"if- feature\" or \"choice\" statements", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.24-3" }, { "text": "* \"must\" statements are generally more expensive than \"min- elements\", \"max-elements\", \"mandatory\", or \"unique\" statements", "candidate_types": [ "rule" ], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.24-4" }, { "text": "* \"identityref\" leafs are generally more expensive than \"enumeration\" leafs", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.24-5" }, { "text": "* \"leafref\" and \"instance-identifier\" types with \"require-instance\" set to \"true\" are generally more expensive than if \"require- instance\" is set to \"false\"", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.24-6" } ] }, { "number": "4.25", "title": "Open Systems Considerations", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.25", "paragraphs": [ { "text": "Only the modules imported by a particular module can be assumed to be present in an implementation. An open system MAY include any combination of YANG modules.", "candidate_types": [ "permission" ], "uppercase_requirement_words": [ "MAY" ], "example_or_code": false, "id": "rfc9907-4.25-1" } ] }, { "number": "4.26", "title": "Guidelines for Constructs Specific to YANG 1.1", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.26", "paragraphs": [ { "text": "The set of guidelines for YANG 1.1 will grow as operational experience is gained with the new language features. This section contains an initial set of guidelines for YANG 1.1 language features.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.26-1" } ] }, { "number": "4.26.1", "title": "Importing Multiple Revisions", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.26.1", "paragraphs": [ { "text": "Standard modules SHOULD NOT import multiple revisions of the same module into a module. This MAY be done if independent definitions (e.g., \"enumeration\" typedefs) from specific revisions are needed in the importing module.", "candidate_types": [ "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD NOT" ], "example_or_code": false, "id": "rfc9907-4.26.1-1" } ] }, { "number": "4.26.2", "title": "Using Feature Logic", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.26.2", "paragraphs": [ { "text": "The YANG 1.1 feature logic is much more expressive than YANG 1.0. A \"description\" statement SHOULD describe the \"if-feature\" logic in text, to help readers understand the module.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.26.2-1" }, { "text": "YANG features SHOULD be used instead of the \"when\" statement, if possible. Features are advertised by the server, and objects conditional by the \"if-feature\" statement are conceptually grouped together. There is no such commonality supported for \"when\" statements.", "candidate_types": [ "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.26.2-2" }, { "text": "Features generally require less server implementation complexity and runtime resources than objects that use \"when\" statements. Features are generally static (i.e., set when a module is loaded and not changed at runtime). However, every client edit might cause a \"when\" statement result to change.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.26.2-3" } ] }, { "number": "4.26.3", "title": "\"anyxml\" versus \"anydata\"", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.26.3", "paragraphs": [ { "text": "The \"anyxml\" statement MUST NOT be used to represent a conceptual subtree of YANG data nodes. The \"anydata\" statement MUST be used for this purpose.", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST", "MUST NOT" ], "example_or_code": false, "id": "rfc9907-4.26.3-1" } ] }, { "number": "4.26.4", "title": "\"action\" versus \"rpc\"", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.26.4", "paragraphs": [ { "text": "The use of \"action\" statements or \"rpc\" statements is a subjective design decision. RPC operations are not associated with any particular data node. Actions are associated with a specific data node definition. An \"action\" statement SHOULD be used if the protocol operation is specific to a subset of all data nodes instead of all possible data nodes.", "candidate_types": [ "definition", "advice" ], "uppercase_requirement_words": [ "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.26.4-1" }, { "text": "The same action name MAY be used in different definitions within different data node. For example, a \"reset\" action defined with a data node definition for an interface might have different parameters than for a power supply or a VLAN. The same action name SHOULD be used to represent similar semantics.", "candidate_types": [ "advice", "permission" ], "uppercase_requirement_words": [ "MAY", "SHOULD" ], "example_or_code": false, "id": "rfc9907-4.26.4-2" }, { "text": "The NETCONF Access Control Model (NACM) [RFC8341] does not support parameter-based access control for RPC operations. The user is given permission (or not) to invoke the RPC operation with any parameters. For example, if each client is only allowed to reset their own interface, then NACM cannot be used.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.26.4-3" }, { "text": "For example, NACM cannot enforce access control based on the value of the \"interface\" parameter, only the \"reset\" operation itself:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.26.4-4" }, { "text": "rpc reset { input { leaf interface { type if:interface-ref; mandatory true; description \"The interface to reset.\"; } } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.26.4-5" }, { "text": "However, NACM can enforce access control for individual interface instances, using a \"reset\" action. If the user does not have read access to the specific \"interface\" instance, then it cannot invoke the \"reset\" action for that interface instance:", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.26.4-6" }, { "text": "container interfaces { list interface { ... action reset { } } }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.26.4-7" } ] }, { "number": "4.27", "title": "Updating YANG Modules (Published versus Unpublished)", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.27", "paragraphs": [ { "text": "YANG modules can change over time. Typically, new data model definitions are needed to support new features. YANG update rules defined in Section 11 of [RFC7950] MUST be followed for published modules. They MAY be followed for unpublished modules.", "candidate_types": [ "rule", "permission" ], "uppercase_requirement_words": [ "MAY", "MUST" ], "example_or_code": false, "id": "rfc9907-4.27-1" }, { "text": "The YANG update rules only apply to published module revisions. Each organization will have their own way to identify published work that is considered to be stable and unpublished work that is considered to be unstable. For example, in the IETF, an RFC is used for published work, and an I-D is used for unpublished work.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.27-2" } ] }, { "number": "4.28", "title": "Defining Standard Tags", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.28", "paragraphs": [ { "text": "[RFC8819] specifies a method for associating tags with YANG modules. Tags may be defined and associated at design time, at implementation time, or via user administrative control. Design-time tags are indicated using the module-tag \"extension\" statement.", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.28-1" }, { "text": "A module MAY indicate, using module-tag \"extension\" statements, a set of tags that are to be automatically associated with it (i.e., not added through configuration).", "candidate_types": [ "permission" ], "uppercase_requirement_words": [ "MAY" ], "example_or_code": false, "id": "rfc9907-4.28-2" }, { "text": "module example-module { namespace \"https://example.com/yang/example\"; prefix \"ex\"; //... import module-tags { prefix tags; }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.28-3" }, { "text": "tags:module-tag \"ietf:some-new-tag\"; tags:module-tag \"ietf:some-other-tag\"; // ... }", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.28-4" }, { "text": "Authors can use existing standard tags or use new tags defined in the model definition, as appropriate. For IETF modules, new tags MUST be assigned in the IANA \"IETF YANG Module Tags\" registry within the \"YANG Module Tags\" registry group [IANA-TAGS].", "candidate_types": [ "rule" ], "uppercase_requirement_words": [ "MUST" ], "example_or_code": false, "id": "rfc9907-4.28-5" } ] }, { "number": "4.29", "title": "Modeling Abstract Data Structures", "url": "https://www.rfc-editor.org/rfc/rfc9907.html#section-4.29", "paragraphs": [ { "text": "For contexts where YANG is used to model abstract data structures (e.g., protocol messages), the use of the \"structure\" extension statement [RFC8791] is RECOMMENDED compared to the \"yang-data\" extension statement [RFC8040]. Examples of modules that rely upon the \"structure\" extension statement from [RFC8791] can be found in [RFC9132] or [RFC9195].", "candidate_types": [ "definition", "advice" ], "uppercase_requirement_words": [ "RECOMMENDED" ], "example_or_code": false, "id": "rfc9907-4.29-1" }, { "text": "Abstract data structures can be augmented using the \"augment- structure\" statement [RFC8791]. Examples of modules that augment abstract data structures can be found in [RFC9244] and [RFC9362].", "candidate_types": [], "uppercase_requirement_words": [], "example_or_code": false, "id": "rfc9907-4.29-2" } ] } ], "scope": { "sections": [ "4.1-4.29" ] }, "copyright_notice": "Copyright Notice\n\n Copyright (c) 2026 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (https://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefully, as they describe your rights and restrictions with respect\n to this document. Code Components extracted from this document must\n include Revised BSD License text as described in Section 4.e of the\n Trust Legal Provisions and are provided without warranty as described\n in the Revised BSD License." }, "schema_sha256": "80ae31c6f5a0d2f995c2767d8bff5492fd25657b186b74d2485ccd6cac04651e", "metadata_sha256": "11cdf6b56e9dfcbb8e8ae5dd56b9e7fc660779123bf9cc254419e3cd96bae46f" }, "package": { "filename": "ieee8023_clause30-0.0.3+dirty.build20261106t034951316960z-py3-none-any.whl", "sha256": "0b2bc818465edba4f99e5145a9cc8a7178693e5b5d769f92104c15881cd53c1f", "distribution": "ieee8023-clause30", "version": "0.0.3+dirty.build20261106t034951316960z", "release": "v0.0.3", "source_commit": "bcc64bf06982bf95d8b4f2d2d4b226f7ec7090f1", "source_worktree_dirty": true, "source_pdf_sha256": "37ad6992cdbfad95b8452cf2e406cf81045c448c874866298ac8582a9fe7aba4" }, "limitations": [ "Rule-based review only; it does not establish semantic conformance or cover every model mapping.", "Unreferenced attributes have no explicit IEEE 802.3 section reference in the selected modules; implicit, inherited, name-only, and external mappings are not resolved. Unqualified references are uncertain; referenced duplicate section IDs are excluded from this inventory.", "Package mapping guidance consists of review candidates, not mandatory or approved mappings. Derived YANG types are not resolved.", "RFC 9907 candidate labels and uppercase terms are heuristic review aids, not applicability or conformance determinations; examples and context require review.", "Prose checks detect repeated words or phrases and possible spelling problems, not full grammar; technical terms and extracted text can cause false positives.", "The lightweight YANG statement reader does not validate syntax, resolve imports, expand groupings, or apply augments and deviations.", "Checks depend on extracted text; verify findings against the authoritative standard and related procedures.", "Package checksums establish consistency, not publisher authenticity." ] }