ietf-logical-network-element@2018-03-20.yang   ietf-logical-network-element@2019-01-25.yang 
module ietf-logical-network-element { module ietf-logical-network-element {
yang-version 1.1; yang-version 1.1;
// namespace // namespace
namespace namespace "urn:ietf:params:xml:ns:yang:ietf-logical-network-element";
"urn:ietf:params:xml:ns:yang:ietf-logical-network-element";
prefix lne; prefix lne;
// import some basic types // import some basic types
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference "draft-ietf-netmod-rfc7223bis: reference
A YANG Data Model for Interface Management"; "RFC 8343: A YANG Data Model for Interface Management";
} }
import ietf-yang-schema-mount { import ietf-yang-schema-mount {
prefix yangmnt; prefix yangmnt;
reference "draft-ietf-netmod-schema-mount: YANG Schema Mount"; reference
// RFC Ed.: Please replace this draft name with the corresponding "RFC 8528: YANG Schema Mount";
// RFC number
} }
organization organization
"IETF Routing Area (rtgwg) Working Group"; "IETF Routing Area (rtgwg) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/rtgwg/> "WG Web: <https://datatracker.ietf.org/wg/rtgwg/>
WG List: <mailto:rtgwg@ietf.org> WG List: <mailto:rtgwg@ietf.org>
Author: Lou Berger Author: Lou Berger
<mailto:lberger@labn.net> <mailto:lberger@labn.net>
Author: Christan Hopps
Author: Christian Hopps
<mailto:chopps@chopps.org> <mailto:chopps@chopps.org>
Author: Acee Lindem Author: Acee Lindem
<mailto:acee@cisco.com> <mailto:acee@cisco.com>
Author: Dean Bogdanovic Author: Dean Bogdanovic
<mailto:ivandean@gmail.com>"; <mailto:ivandean@gmail.com>";
description description
"This module is used to support multiple logical network "This module is used to support multiple logical network
elements on a single physical or virtual system. elements on a single physical or virtual system.
Copyright (c) 2017 IETF Trust and the persons Copyright (c) 2019 IETF Trust and the persons identified as
identified as authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD License
License set forth in Section 4.c of the IETF Trust's Legal set forth in Section 4.c of the IETF Trust's Legal Provisions
Provisions Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC 8530; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove revision 2019-01-25 {
// this note
// RFC Ed.: please update TBD
revision 2018-03-20 {
description description
"Initial revision."; "Initial revision.";
reference "RFC XXXX"; reference
"RFC 8530: YANG Model for Logical Network Elements";
} }
// top level device definition statements // top level device definition statements
container logical-network-elements { container logical-network-elements {
description description
"Allows a network device to support multiple logical "Allows a network device to support multiple logical
network element (device) instances."; network element (device) instances.";
list logical-network-element { list logical-network-element {
key "name"; key "name";
skipping to change at line 87 skipping to change at line 85
description description
"Device-wide unique identifier for the "Device-wide unique identifier for the
logical network element."; logical network element.";
} }
leaf managed { leaf managed {
type boolean; type boolean;
default "true"; default "true";
description description
"True if the host can access LNE information "True if the host can access LNE information
using the root mount point. This value using the root mount point. This value
my not be modifiable in all implementations."; may not be modifiable in all implementations.";
} }
leaf description { leaf description {
type string; type string;
description description
"Description of the logical network element."; "Description of the logical network element.";
} }
container "root" { container root {
description description
"Container for mount point."; "Container for mount point.";
yangmnt:mount-point "root" { yangmnt:mount-point "root" {
description description
"Root for models supported per logical "Root for models supported per logical
network element. This mount point may or may not network element. This mount point may or may not
be inline based on the server implementation. It be inline based on the server implementation. It
SHALL always contain a YANG library and interfaces SHALL always contain a YANG library and interfaces
instance. instance.
When the associated 'managed' leaf is 'false' any When the associated 'managed' leaf is 'false', any
operation that attempts to access information below operation that attempts to access information below
the root SHALL fail with an error-tag of the root SHALL fail with an error-tag of
'access-denied' and an error-app-tag of 'access-denied' and an error-app-tag of
'lne-not-managed'."; 'lne-not-managed'.";
} }
} }
} }
} }
// augment statements // augment statements
augment "/if:interfaces/if:interface" { augment "/if:interfaces/if:interface" {
description description
"Add a node for the identification of the logical network "Add a node for the identification of the logical network
element associated with an interface. Applies to element associated with an interface. Applies to
interfaces that can be assigned on a per logical network interfaces that can be assigned on a per-logical-network-
element basis. element basis.
Note that a standard error will be returned if the Note that a standard error will be returned if the
identified leafref isn't present. If an interfaces identified leafref isn't present. If interfaces
cannot be assigned for any other reason, the operation cannot be assigned for any other reason, the operation
SHALL fail with an error-tag of 'operation-failed' and an SHALL fail with an error-tag of 'operation-failed' and an
error-app-tag of 'lne-assignment-failed'. A meaningful error-app-tag of 'lne-assignment-failed'. A meaningful
error-info that indicates the source of the assignment error-info that indicates the source of the assignment
failure SHOULD also be provided."; failure SHOULD also be provided.";
leaf bind-lne-name { leaf bind-lne-name {
type leafref { type leafref {
path path "/logical-network-elements/logical-network-element/name";
"/logical-network-elements/logical-network-element/name";
} }
description description
"Logical network element ID to which interface is bound."; "Logical network element ID to which the interface is
bound.";
} }
} }
// notification statements // notification statements
notification bind-lne-name-failed { notification bind-lne-name-failed {
description description
"Indicates an error in the association of an interface to an "Indicates an error in the association of an interface to an
LNE. Only generated after success is initially returned when LNE. Only generated after success is initially returned
bind-lne-name is set."; when bind-lne-name is set.";
leaf name { leaf name {
type leafref { type leafref {
path "/if:interfaces/if:interface/if:name"; path "/if:interfaces/if:interface/if:name";
} }
mandatory true; mandatory true;
description description
"Contains the interface name associated with the "Contains the interface name associated with the
failure."; failure.";
} }
leaf bind-lne-name { leaf bind-lne-name {
 End of changes. 20 change blocks. 
32 lines changed or deleted 30 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/