< draft-ietf-rtgwg-lne-model-01.txt   draft-ietf-rtgwg-lne-model-02.txt >
Network Working Group L. Berger Network Working Group L. Berger
Internet-Draft LabN Consulting, L.L.C. Internet-Draft LabN Consulting, L.L.C.
Intended status: Standards Track C. Hopps Intended status: Standards Track C. Hopps
Expires: May 1, 2017 Deutsche Telekom Expires: September 14, 2017 Deutsche Telekom
A. Lindem A. Lindem
Cisco Systems Cisco Systems
D. Bogdanovic D. Bogdanovic
October 28, 2016 March 13, 2017
YANG Logical Network Elements YANG Logical Network Elements
draft-ietf-rtgwg-lne-model-01 draft-ietf-rtgwg-lne-model-02
Abstract Abstract
This document defines a logical network element module. This module This document defines a logical network element module. This module
along with the network instance module can be used to manage the along with the network instance module can be used to manage the
logical and virtual resource representations that may be present on a logical and virtual resource representations that may be present on a
network device. Examples of common industry terms for logical network device. Examples of common industry terms for logical
resource representations are Logical Systems or Logical Routers. resource representations are Logical Systems or Logical Routers.
Examples of of common industry terms for virtual resource Examples of of common industry terms for virtual resource
representations are Virtual Routing and Forwarding (VRF) instances representations are Virtual Routing and Forwarding (VRF) instances
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 1, 2017. This Internet-Draft will expire on September 14, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 9, line 18 skipping to change at page 9, line 18
name: ietf-logical-network-element name: ietf-logical-network-element
namespace: urn:ietf:params:xml:ns:yang:ietf-logical-network-element namespace: urn:ietf:params:xml:ns:yang:ietf-logical-network-element
prefix: lne prefix: lne
reference: RFC XXXX reference: RFC XXXX
6. Logical Network Element Model 6. Logical Network Element Model
The structure of the model defined in this document is described by The structure of the model defined in this document is described by
the YANG module below. the YANG module below.
<CODE BEGINS> file "ietf-logical-network-element@2016-10-21.yang" <CODE BEGINS> file "ietf-logical-network-element@2017-03-13.yang"
module ietf-logical-network-element { module ietf-logical-network-element {
yang-version 1.1; yang-version 1.1;
// namespace // namespace
namespace "urn:ietf:params:xml:ns:yang:ietf-logical-network-element"; namespace "urn:ietf:params:xml:ns:yang:ietf-logical-network-element";
prefix lne; prefix lne;
// import some basic types // import some basic types
skipping to change at page 9, line 47 skipping to change at page 9, line 47
// meta // meta
organization "IETF Routing Area Working Group (rtgwg)"; organization "IETF Routing Area Working Group (rtgwg)";
contact contact
"Routing Area Working Group - <rtgwg@ietf.org>"; "Routing Area Working Group - <rtgwg@ietf.org>";
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.";
revision "2016-10-21" { revision "2017-03-13" {
description description
"Initial revision."; "Initial revision.";
reference "RFC TBD"; reference "RFC TBD";
} }
// feature statements // feature statements
feature bind-lne-name { feature bind-lne-name {
description description
"Logical network element to which an interface is bound"; "Logical network element to which an interface is bound";
} }
skipping to change at page 10, line 34 skipping to change at page 10, line 34
type boolean; type boolean;
description description
"True if the host can manage the LNE using the root mount "True if the host can manage the LNE using the root mount
point"; point";
} }
leaf description { leaf description {
type string; type string;
description description
"Description of the logical network element"; "Description of the logical network element";
} }
anydata root { yangmnt:mount-point root {
yangmnt:mount-point "root";
description description
"Root for models supported per logical "Root for models supported per logical
network element"; network element. This mount point will
typically be of type inline. It shall
always contain a yang library instance.";
} }
} }
} }
// 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 interfaces element associated with an interface. Applies to interfaces
that can be assigned on a per logical network element basis. that can be assigned on a per logical network element basis.
skipping to change at page 11, line 25 skipping to change at page 11, line 25
} }
<CODE ENDS> <CODE ENDS>
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.ietf-netmod-schema-mount] [I-D.ietf-netmod-schema-mount]
Bjorklund, M. and L. Lhotka, "YANG Schema Mount", draft- Bjorklund, M. and L. Lhotka, "YANG Schema Mount", draft-
ietf-netmod-schema-mount-02 (work in progress), July 2016. ietf-netmod-schema-mount-04 (work in progress), March
2017.
[I-D.ietf-rtgwg-ni-model] [I-D.ietf-rtgwg-ni-model]
Berger, L., Hopps, C., Lindem, A., and D. Bogdanovic, Berger, L., Hopps, C., Lindem, A., and D. Bogdanovic,
"Network Instance Model", draft-ietf-rtgwg-ni-model-00 "YANG Network Instances", draft-ietf-rtgwg-ni-model-01
(work in progress), June 2016. (work in progress), October 2016.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>. <http://www.rfc-editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>. <http://www.rfc-editor.org/info/rfc6020>.
skipping to change at page 12, line 14 skipping to change at page 12, line 14
7.2. Informative References 7.2. Informative References
[I-D.ietf-netmod-opstate-reqs] [I-D.ietf-netmod-opstate-reqs]
Watsen, K. and T. Nadeau, "Terminology and Requirements Watsen, K. and T. Nadeau, "Terminology and Requirements
for Enhanced Handling of Operational State", draft-ietf- for Enhanced Handling of Operational State", draft-ietf-
netmod-opstate-reqs-04 (work in progress), January 2016. netmod-opstate-reqs-04 (work in progress), January 2016.
[I-D.ietf-netmod-routing-cfg] [I-D.ietf-netmod-routing-cfg]
Lhotka, L. and A. Lindem, "A YANG Data Model for Routing Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", draft-ietf-netmod-routing-cfg-24 (work in Management", draft-ietf-netmod-routing-cfg-25 (work in
progress), October 2016. progress), November 2016.
[I-D.ietf-rtgwg-device-model] [I-D.ietf-rtgwg-device-model]
Lindem, A., Berger, L., Bogdanovic, D., and C. Hopps, Lindem, A., Berger, L., Bogdanovic, D., and C. Hopps,
"Network Device YANG Organizational Models", draft-ietf- "Network Device YANG Organizational Models", draft-ietf-
rtgwg-device-model-00 (work in progress), August 2016. rtgwg-device-model-01 (work in progress), October 2016.
[I-D.openconfig-netmod-opstate] [I-D.openconfig-netmod-opstate]
Shakir, R., Shaikh, A., and M. Hines, "Consistent Modeling Shakir, R., Shaikh, A., and M. Hines, "Consistent Modeling
of Operational State Data in YANG", draft-openconfig- of Operational State Data in YANG", draft-openconfig-
netmod-opstate-01 (work in progress), July 2015. netmod-opstate-01 (work in progress), July 2015.
[RFC7895] Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module [RFC7895] Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module
Library", RFC 7895, DOI 10.17487/RFC7895, June 2016, Library", RFC 7895, DOI 10.17487/RFC7895, June 2016,
<http://www.rfc-editor.org/info/rfc7895>. <http://www.rfc-editor.org/info/rfc7895>.
 End of changes. 13 change blocks. 
16 lines changed or deleted 18 lines changed or added

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