< draft-ietf-rtgwg-lne-model-03.txt   draft-ietf-rtgwg-lne-model-04.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: January 4, 2018 Deutsche Telekom Expires: March 30, 2018 Deutsche Telekom
A. Lindem A. Lindem
Cisco Systems Cisco Systems
D. Bogdanovic D. Bogdanovic
X. Liu X. Liu
Jabil Jabil
July 3, 2017 September 26, 2017
YANG Logical Network Elements YANG Logical Network Elements
draft-ietf-rtgwg-lne-model-03 draft-ietf-rtgwg-lne-model-04
Abstract Abstract
This document defines a logical network element module. This module This document defines a logical network element module. This module
can be used to manage the logical resource partitioning that may be can be used to manage the logical resource partitioning that may be
present on a network device. Examples of common industry terms for present on a network device. Examples of common industry terms for
logical resource partitioning are Logical Systems or Logical Routers. logical resource partitioning are Logical Systems or Logical Routers.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 https://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 January 4, 2018. This Internet-Draft will expire on March 30, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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 (https://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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
skipping to change at page 2, line 25 skipping to change at page 2, line 25
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Logical Network Elements . . . . . . . . . . . . . . . . . . 5 3. Logical Network Elements . . . . . . . . . . . . . . . . . . 5
3.1. LNE Instantiation and Resource Assignment . . . . . . . . 6 3.1. LNE Instantiation and Resource Assignment . . . . . . . . 6
3.2. LNE Management - LNE View . . . . . . . . . . . . . . . . 7 3.2. LNE Management - LNE View . . . . . . . . . . . . . . . . 7
3.3. LNE Management - Host Network Device View . . . . . . . . 7 3.3. LNE Management - Host Network Device View . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Logical Network Element Model . . . . . . . . . . . . . . . . 9 6. Logical Network Element Model . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.1. Normative References . . . . . . . . . . . . . . . . . . 13 7.1. Normative References . . . . . . . . . . . . . . . . . . 13
7.2. Informative References . . . . . . . . . . . . . . . . . 13 7.2. Informative References . . . . . . . . . . . . . . . . . 14
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 14 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 14
Appendix B. Examples . . . . . . . . . . . . . . . . . . . . . . 15 Appendix B. Examples . . . . . . . . . . . . . . . . . . . . . . 15
B.1. Example: Host Device Managed LNE . . . . . . . . . . . . 15 B.1. Example: Host Device Managed LNE . . . . . . . . . . . . 15
B.1.1. Configuration Data . . . . . . . . . . . . . . . . . 19 B.1.1. Configuration Data . . . . . . . . . . . . . . . . . 19
B.1.2. State Data . . . . . . . . . . . . . . . . . . . . . 23 B.1.2. State Data . . . . . . . . . . . . . . . . . . . . . 23
B.2. Example: Self Managed LNE . . . . . . . . . . . . . . . . 32 B.2. Example: Self Managed LNE . . . . . . . . . . . . . . . . 32
B.2.1. Configuration Data . . . . . . . . . . . . . . . . . 35 B.2.1. Configuration Data . . . . . . . . . . . . . . . . . 35
B.2.2. State Data . . . . . . . . . . . . . . . . . . . . . 38 B.2.2. State Data . . . . . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 47 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 47
skipping to change at page 9, line 47 skipping to change at page 9, line 47
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@2017-06-30.yang" <CODE BEGINS> file "ietf-logical-network-element@2017-09-27.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
import ietf-interfaces { import ietf-interfaces {
skipping to change at page 11, line 7 skipping to change at page 11, line 7
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 XXXX; 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 // RFC Ed.: replace XXXX with actual RFC number and remove
// this note // this note
// RFC Ed.: please update TBD // RFC Ed.: please update TBD
revision 2017-03-13 { revision 2017-09-27 {
description description
"Initial revision."; "Initial revision.";
reference "RFC TBD"; reference "RFC TBD";
} }
// 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
skipping to change at page 11, line 31 skipping to change at page 11, line 31
description description
"List of logical network elements."; "List of logical network elements.";
leaf name { leaf name {
type string; type string;
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";
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."; my 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.";
} }
yangmnt:mount-point "root" { container "root" {
description description
"Root for models supported per logical "Container for mount point.";
network element. This mount point will yangmnt:mount-point "root" {
may or may not be inline based on the server description
implementation. It SHALL always contain a YANG "Root for models supported per logical
library and interfaces instance. network element. This mount point will
may or may not be inline based on the server
implementation. It SHALL always contain a YANG
library and interfaces 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 interfaces element associated with an interface. Applies to interfaces
skipping to change at page 13, line 27 skipping to change at page 13, line 31
} }
} }
<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-05 (work in progress), May 2017. ietf-netmod-schema-mount-06 (work in progress), July 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[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>. <https://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>. <https://www.rfc-editor.org/info/rfc6020>.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface [RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, Management", RFC 7223, DOI 10.17487/RFC7223, May 2014,
<http://www.rfc-editor.org/info/rfc7223>. <https://www.rfc-editor.org/info/rfc7223>.
7.2. Informative References 7.2. Informative References
[I-D.ietf-netmod-yang-tree-diagrams] [I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-01 (work in progress), June ietf-netmod-yang-tree-diagrams-01 (work in progress), June
2017. 2017.
[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 Logical Organization", draft-ietf- "Network Device YANG Logical Organization", draft-ietf-
rtgwg-device-model-02 (work in progress), March 2017. rtgwg-device-model-02 (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., Bogdanovic, D., and X.
"YANG Network Instances", draft-ietf-rtgwg-ni-model-02 Liu, "YANG Network Instances", draft-ietf-rtgwg-ni-
(work in progress), March 2017. model-03 (work in progress), July 2017.
[RFC7317] Bierman, A. and M. Bjorklund, "A YANG Data Model for [RFC7317] Bierman, A. and M. Bjorklund, "A YANG Data Model for
System Management", RFC 7317, DOI 10.17487/RFC7317, August System Management", RFC 7317, DOI 10.17487/RFC7317, August
2014, <http://www.rfc-editor.org/info/rfc7317>. 2014, <https://www.rfc-editor.org/info/rfc7317>.
[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>. <https://www.rfc-editor.org/info/rfc7895>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<http://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", RFC 8022, DOI 10.17487/RFC8022, November Management", RFC 8022, DOI 10.17487/RFC8022, November
2016, <http://www.rfc-editor.org/info/rfc8022>. 2016, <https://www.rfc-editor.org/info/rfc8022>.
Appendix A. Acknowledgments Appendix A. Acknowledgments
The Routing Area Yang Architecture design team members included Acee The Routing Area Yang Architecture design team members included Acee
Lindem, Anees Shaikh, Christian Hopps, Dean Bogdanovic, Lou Berger, Lindem, Anees Shaikh, Christian Hopps, Dean Bogdanovic, Lou Berger,
Qin Wu, Rob Shakir, Stephane Litkowski, and Yan Gang. Useful review Qin Wu, Rob Shakir, Stephane Litkowski, and Yan Gang. Useful review
comments were also received by Martin Bjorklund and John Scudder. comments were also received by Martin Bjorklund and John Scudder.
This document was motivated by, and derived from, This document was motivated by, and derived from,
[I-D.ietf-rtgwg-device-model]. [I-D.ietf-rtgwg-device-model].
 End of changes. 23 change blocks. 
32 lines changed or deleted 37 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/