Skip to content

yc.o sync #1723

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
einarnn merged 1 commit into from
May 22, 2026
Merged

yc.o sync #1723

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
224 changes: 142 additions & 82 deletions ...etwork-inventory-topology@2026-02-28.yang → ...etwork-inventory-topology@2026-05-19.yang
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,21 +57,99 @@ module ietf-network-inventory-topology {
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";

revision 2026-02-28 {
revision 2026-05-19 {
description
"Initial revision.";
reference
"RFC XXXX: A Network Data Model for Inventory Topology
Mapping";
}

// Groupings
// Node Grouping with 1:1 mapping to NE
identity link-type {
description
"Base identity for classifying the physical media type of a
link at the inventory topology layer. Specialized inventory
models are expected to define derived identities for specific
media, e.g., fiber, copper, or wireless.";
}

identity copper {
base link-type;
description
"Copper-based physical link.";
}

identity fiber {
base link-type;
description
"Fiber-based physical link.";
}

identity coax {
base link-type;
description
"Coaxial cable-based physical link.";
}

identity microwave {
base link-type;
description
"Microwave-based wireless link.
Detailed microwave radio attributes are defined in the
microwave topology data model.";
reference
"RFC 9656: A YANG Data Model for Microwave Topology";
}

identity wlan {
base link-type;
description
"IEEE 802.11 wireless link.";
}

identity unknown {
base link-type;
description
"The link media type is unknown or could not be determined.
This identity is used as a fallback when the physical medium
cannot be classified into any of the other defined types.";
}

identity leased-fiber {
base fiber;
description
"Leased fiber link. The physical medium is fiber, but the link
is provided by a third-party operator. Detailed physical
attributes are typically not visible to the lessee.";
}

// Main blocks

augment "/nw:networks/nw:network/nw:network-types" {
description
"Introduces a new network type for inventory topology
mapping.";
container inventory-topology {
presence
"Indicates this is a bottom-most physical topology instance,
containing physical-layer attributes including inventory
mapping, port breakout capabilities, and link media types.";
description
"Container for the inventory-topology network type.
When present, it signals that the network contains
physical-layer augmentations as defined in this module.
This network type is intended to serve as the underlay
for logical network topologies (Layer 2, Layer 3,
Traffic Engineering (TE), etc.).";
}
}

grouping node-inventory-mapping-attributes {
augment "/nw:networks/nw:network/nw:node" {
when '../nw:network-types/nwit:inventory-topology';
description
"Attributes for mapping a topology node to a Network Element
(NE) in the physical inventory.";
"Augments the network topology node with inventory mapping
attributes. This enables correlation between the logical node
and its physical network element.";
container inventory-mapping-attributes {
description
"Container for inventory mapping attributes of a node.";
Expand All @@ -87,60 +165,11 @@ module ietf-network-inventory-topology {
}
}

// TP Grouping with 1:1 mapping to physical port

grouping tp-inventory-mapping-attributes {
description
"Attributes for mapping a topology termination point (TP)
to a physical port in the network inventory.";
container inventory-mapping-attributes {
description
"Container for inventory mapping attributes of a TP.";
uses nwi:port-ref {
refine "port-ref" {
description
"Reference to the physical port component in the
network inventory. This reference establishes a 1:1
mapping between the logical TP and its physical port
component.";
}
}
// breakout channels (lightweight, per physical port)
container port-breakout {
presence "Indicates the port supports channel breakout.";
config false;
description
"Breakout capability of the physical port represented by
this TP. One TP maps to one physical port; channels are
listed here. This container is present only when the
underlying hardware supports partitioning the port into
multiple independent channels (e.g., 400G to 4x100G).";
list breakout-channel {
key "channel-id";
description
"List of breakout channels available on this port.
Each entry represents an independent lane or sub-port
that can be used for channelized interfaces.";
leaf channel-id {
type uint16;
description
"Unique identifier for the breakout channel within the
scope of the parent port.";
}
} // breakout-channel
} // port-breakout
}
}

// Link Grouping with placeholder for future augumentation

grouping link-inventory-mapping-attributes {
augment "/nw:networks/nw:network/nt:link" {
when '../nw:network-types/nwit:inventory-topology';
description
"Attributes for classifying link media type.
Detailed inventory reference is intentionally omitted from
this model; implementations should use the appropriate
specialized inventory modules based on the indicated
link-type.";
"Augments the network topology link with inventory-related
attributes.";
container inventory-mapping-attributes {
description
"Container for inventory-related attributes of a link.
Expand All @@ -156,36 +185,67 @@ module ietf-network-inventory-topology {
Detailed inventory references may be added in future
modules.";
leaf link-type {
type string;
type identityref {
base link-type;
}
description
"Classification of the link media type at the topology
layer. Example values include 'copper', 'fiber',
'microwave', or 'wifi'.";
layer.

The base identity 'link-type' is extensible. Examples
of derived identities include 'copper', 'fiber',
'coax', 'microwave', and 'wlan'.

This leaf serves as a lightweight discriminator. When
the value is 'microwave', detailed microwave link
attributes are defined in the microwave topology data
model. Wired media (e.g., fiber, copper, or coax) may
be detailed in a passive network inventory data
model.";
}
}
}

// Main blocks

augment "/nw:networks/nw:network/nw:node" {
description
"Augments the network topology node with inventory mapping
attributes. This enables correlation between the logical node
and its physical network element.";
uses node-inventory-mapping-attributes;
}

augment "/nw:networks/nw:network/nt:link" {
description
"Augments the network topology link with inventory-related
attributes.";
uses link-inventory-mapping-attributes;
}

augment "/nw:networks/nw:network/nw:node/nt:termination-point" {
when '../../nw:network-types/nwit:inventory-topology';
description
"Augments the TP with inventory mapping attributes for
physical port correlation and breakout capability reporting.";
uses tp-inventory-mapping-attributes;
"Augments the TP with inventory mapping and port breakout.";
container inventory-mapping-attributes {
description
"Container for inventory mapping attributes of a TP.";
uses nwi:port-ref {
refine "port-ref" {
description
"Reference to the physical port component in the
network inventory. This reference establishes a 1:1
mapping between the logical TP and its physical port
component.";
}
}
}
// breakout channels (lightweight, per physical port)
container port-breakout {
presence "Indicates the port supports channel breakout.";
config false;
description
"Breakout capability of the physical port represented by
this TP. One TP maps to one physical port; channels are
listed here. This container is present only when the
underlying hardware supports partitioning the port into
multiple independent channels (e.g., 400G to 4x100G).";
list breakout-channel {
key "channel-id";
description
"List of breakout channels available on this port.
Each entry represents an independent lane or sub-port
that can be used for channelized interfaces.";
leaf channel-id {
type uint16;
description
"Unique identifier for the breakout channel within the
scope of the parent port.";
}
} // breakout-channel
} // port-breakout
}
}
17 changes: 7 additions & 10 deletions ...ules/ietf-te-packet-types@2026-01-15.yang → ...ules/ietf-te-packet-types@2026-05-08.yang
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ module ietf-te-packet-types {
<mailto:rgandhi@cisco.com>

Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net>
<mailto:vishnupavan.ietf@gmail.com>

Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com>
Expand All @@ -40,9 +40,6 @@ module ietf-te-packet-types {
data type definitions specific to Packet Traffic Engineering
(TE).

The model conforms to the Network Management Datastore
Architecture (NMDA).

The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as
Expand All @@ -59,14 +56,14 @@ module ietf-te-packet-types {
Relating to IETF Documents
(https://trustee.ietf.org/license-info).

This version of this YANG module is part of RFC XXXX
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
for full legal notices.";
All revisions of IETF published modules can be found
at the YANG Parameters registry group
(https://www.iana.org/assignments/yang-parameters).

// RFC Ed.: update the date below with the date of RFC publication
// and remove this note.
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";

revision 2026-01-15 {
revision 2026-05-08 {
description
"This revision adds the following new identities:
- bandwidth-profile-type;
Expand Down
12 changes: 9 additions & 3 deletions ...ANG-modules/ietf-te-types@2026-02-06.yang → ...ANG-modules/ietf-te-types@2026-05-08.yang
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ module ietf-te-types {
<mailto:rgandhi@cisco.com>

Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net>
<mailto:vishnupavan.ietf@gmail.com>

Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com>
Expand All @@ -70,14 +70,14 @@ module ietf-te-types {
Relating to IETF Documents
(https://trustee.ietf.org/license-info).

All revisions of IETF and IANA published modules can be found
All revisions of IETF published modules can be found
at the YANG Parameters registry group
(https://www.iana.org/assignments/yang-parameters).

This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";

revision 2026-02-06 {
revision 2026-05-08 {
description
"This revision adds the following new identities:
- lsp-provisioning-error-reason;
Expand Down Expand Up @@ -3168,6 +3168,12 @@ module ietf-te-types {
type te-types:performance-metrics-normality;
description
"The normality of the 'one-way-delay' metric.";
reference
"RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions
RFC 7823: Performance-Based Path Selection for Explicitly
Routed Label Switched Paths (LSPs) Using TE Metric
Extensions";
}
}

Expand Down
20 changes: 11 additions & 9 deletions ...ules/ietf-yp-notification@2025-12-24.yang → ...ules/ietf-yp-notification@2026-05-11.yang
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,12 @@ module ietf-yp-notification {
import ietf-yang-types {
prefix yang;
reference
"draft-ietf-netmod-rfc6991-bis-18: Common YANG Data Types";
"RFC 9911: Common YANG Data Types";
}
import ietf-inet-types {
prefix inet;
reference
"draft-ietf-netmod-rfc6991-bis-18: Common YANG Data Types";
"RFC 9911: Common YANG Data Types";
}
import ietf-subscribed-notifications {
prefix sn;
Expand Down Expand Up @@ -61,13 +61,14 @@ module ietf-yp-notification {
messages [RFC9254]. Refer to Section 3.1.2 of RFC XXXX for more
details.

Copyright (c) 2025 IETF Trust and the persons identified as
Copyright (c) 2026 IETF Trust and the persons identified as
authors of the code. All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, is permitted pursuant to, and subject to the license
terms contained in, the Revised BSD License set forth in Section
4.c of the IETF Trust's Legal Provisions Relating to IETF Documents
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).

All revisions of IETF and IANA published modules can be found
Expand All @@ -83,11 +84,12 @@ module ietf-yp-notification {
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.";

revision 2025-12-24 {
revision 2026-05-11 {
description
"Initial version.";
reference
"RFC XXXX: Extensible YANG Model for YANG-Push Notifications";
"RFC XXXX: Extensible YANG Model for YANG-Push
Notifications";
}

feature hostname-sequence-number {
Expand Down
Loading
Loading