3 namespace "urn:ietf:params:xml:ns:yang:ietf-network";
6 import ietf-inet-types {
9 "RFC 6991: Common YANG Data Types";
13 "IETF I2RS (Interface to the Routing System) Working Group";
16 "WG Web: <https://datatracker.ietf.org/wg/i2rs/>
17 WG List: <mailto:i2rs@ietf.org>
19 Editor: Alexander Clemm
20 <mailto:ludwig@clemm.org>
23 <mailto:jmedved@cisco.com>
26 <mailto:robert.varga@pantheon.tech>
29 <mailto:nitin_bahadur@yahoo.com>
31 Editor: Hariharan Ananthakrishnan
32 <mailto:hari@packetdesign.com>
35 <mailto:xufeng.liu.ietf@gmail.com>";
37 "This module defines a common base data model for a collection
38 of nodes in a network. Node definitions are further used
39 in network topologies and inventories.
41 Copyright (c) 2018 IETF Trust and the persons identified as
42 authors of the code. All rights reserved.
44 Redistribution and use in source and binary forms, with or
45 without modification, is permitted pursuant to, and subject
46 to the license terms contained in, the Simplified BSD License
47 set forth in Section 4.c of the IETF Trust's Legal Provisions
48 Relating to IETF Documents
49 (https://trustee.ietf.org/license-info).
51 This version of this YANG module is part of RFC 8345;
52 see the RFC itself for full legal notices.";
58 "RFC 8345: A YANG Data Model for Network Topologies";
64 "Identifier for a node. The precise structure of the node-id
65 will be up to the implementation. For example, some
66 implementations MAY pick a URI that includes the network-id
67 as part of the path. The identifier SHOULD be chosen
68 such that the same node in a real network topology will
69 always be identified through the same identifier, even if
70 the data model is instantiated in separate datastores. An
71 implementation MAY choose to capture semantics in the
72 identifier -- for example, to indicate the type of node.";
78 "Identifier for a network. The precise structure of the
79 network-id will be up to the implementation. The identifier
80 SHOULD be chosen such that the same network will always be
81 identified through the same identifier, even if the data model
82 is instantiated in separate datastores. An implementation MAY
83 choose to capture semantics in the identifier -- for example,
84 to indicate the type of network.";
87 grouping network-ref {
89 "Contains the information necessary to reference a network --
90 for example, an underlay network.";
93 path "/nw:networks/nw:network/nw:network-id";
94 require-instance false;
97 "Used to reference a network -- for example, an underlay
104 "Contains the information necessary to reference a node.";
107 path "/nw:networks/nw:network[nw:network-id=current()/../"+
108 "network-ref]/nw:node/nw:node-id";
109 require-instance false;
112 "Used to reference a node.
113 Nodes are identified relative to the network that
121 "Serves as a top-level container for a list of networks.";
125 "Describes a network.
126 A network typically contains an inventory of nodes,
127 topological information (augmented through the
128 network-topology data model), and layering information.";
132 "Identifies a network.";
134 container network-types {
136 "Serves as an augmentation target.
137 The network type is indicated through corresponding
138 presence containers augmented into this container.";
140 list supporting-network {
143 "An underlay network, used to represent layered network
147 path "/nw:networks/nw:network/nw:network-id";
148 require-instance false;
151 "References the underlay network.";
158 "The inventory of nodes of this network.";
162 "Uniquely identifies a node within the containing
165 list supporting-node {
166 key "network-ref node-ref";
168 "Represents another node that is in an underlay network
169 and that supports this node. Used to represent layering
173 path "../../../nw:supporting-network/nw:network-ref";
174 require-instance false;
177 "References the underlay network of which the
178 underlay node is a part.";
182 path "/nw:networks/nw:network/nw:node/nw:node-id";
183 require-instance false;
186 "References the underlay node itself.";