draft-ietf-rtgwg-ni-model-08.txt   draft-ietf-rtgwg-ni-model-09.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: August 7, 2018 Deutsche Telekom Expires: August 9, 2018 Deutsche Telekom
A. Lindem A. Lindem
Cisco Systems Cisco Systems
D. Bogdanovic D. Bogdanovic
X. Liu X. Liu
Jabil Jabil
February 3, 2018 February 5, 2018
YANG Network Instances YANG Network Instances
draft-ietf-rtgwg-ni-model-08 draft-ietf-rtgwg-ni-model-09
Abstract Abstract
This document defines a network instance module. This module can be This document defines a network instance module. This module can be
used to manage the virtual resource partitioning that may be present used to manage the virtual resource partitioning that may be present
on a network device. Examples of common industry terms for virtual on a network device. Examples of common industry terms for virtual
resource partitioning are Virtual Routing and Forwarding (VRF) resource partitioning are Virtual Routing and Forwarding (VRF)
instances and Virtual Switch Instances (VSIs). instances and Virtual Switch Instances (VSIs).
Status of This Memo Status of This Memo
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 August 7, 2018. This Internet-Draft will expire on August 9, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Status of Work and Open Issues . . . . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Network Instances . . . . . . . . . . . . . . . . . . . . . . 5 3. Network Instances . . . . . . . . . . . . . . . . . . . . . . 5
3.1. NI Types and Mount Points . . . . . . . . . . . . . . . . 6 3.1. NI Types and Mount Points . . . . . . . . . . . . . . . . 6
3.1.1. Well Known Mount Points . . . . . . . . . . . . . . . 7 3.1.1. Well Known Mount Points . . . . . . . . . . . . . . . 7
3.1.2. NI Type Example . . . . . . . . . . . . . . . . . . . 8 3.1.2. NI Type Example . . . . . . . . . . . . . . . . . . . 8
3.2. NIs and Interfaces . . . . . . . . . . . . . . . . . . . 9 3.2. NIs and Interfaces . . . . . . . . . . . . . . . . . . . 9
3.3. Network Instance Management . . . . . . . . . . . . . . . 10 3.3. Network Instance Management . . . . . . . . . . . . . . . 10
3.4. Network Instance Instantiation . . . . . . . . . . . . . 12 3.4. Network Instance Instantiation . . . . . . . . . . . . . 12
4. Security Considerations . . . . . . . . . . . . . . . . . . . 13 4. Security Considerations . . . . . . . . . . . . . . . . . . . 13
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
6. Network Instance Model . . . . . . . . . . . . . . . . . . . 14 6. Network Instance Model . . . . . . . . . . . . . . . . . . . 14
skipping to change at page 3, line 44 skipping to change at page 3, line 42
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
Readers are expected to be familiar with terms and concepts of YANG Readers are expected to be familiar with terms and concepts of YANG
[RFC7950] and YANG Schema Mount [I-D.ietf-netmod-schema-mount]. [RFC7950] and YANG Schema Mount [I-D.ietf-netmod-schema-mount].
This document uses the graphical representation of data models This document uses the graphical representation of data models
defined in [I-D.ietf-netmod-yang-tree-diagrams]. defined in [I-D.ietf-netmod-yang-tree-diagrams].
1.2. Status of Work and Open Issues
The top open issues are:
1. Schema mount currently doesn't allow parent-reference filtering
on the instance of the mount point, but rather just the schema.
This means it is not possible to filter based on actual data,
e.g., bind-network-instance-name="green". In the schema mount
definition, the text and examples should be updated to cover this
case.
2. Overview 2. Overview
In this document, we consider network devices that support protocols In this document, we consider network devices that support protocols
and functions defined within the IETF Routing Area, e.g, routers, and functions defined within the IETF, e.g, routers, firewalls, and
firewalls, and hosts. Such devices may be physical or virtual, e.g., hosts. Such devices may be physical or virtual, e.g., a classic
a classic router with custom hardware or one residing within a router with custom hardware or one residing within a server-based
server-based virtual machine implementing a virtual network function virtual machine implementing a virtual network function (VNF). Each
(VNF). Each device may sub-divide their resources into logical device may sub-divide their resources into logical network elements
network elements (LNEs) each of which provides a managed logical (LNEs) each of which provides a managed logical device. Examples of
device. Examples of vendor terminology for an LNE include logical vendor terminology for an LNE include logical system or logical
system or logical router, and virtual switch, chassis, or fabric. router, and virtual switch, chassis, or fabric. Each LNE may also
Each LNE may also support virtual routing and forwarding (VRF) and support virtual routing and forwarding (VRF) and virtual switching
virtual switching instance (VSI) functions, which are referred to instance (VSI) functions, which are referred to below as a network
below as a network instances (NIs). This breakdown is represented in instances (NIs). This breakdown is represented in Figure 1.
Figure 1.
,''''''''''''''''''''''''''''''''''''''''''''''`. ,''''''''''''''''''''''''''''''''''''''''''''''`.
| Network Device (Physical or Virtual) | | Network Device (Physical or Virtual) |
| ..................... ..................... | | ..................... ..................... |
| : Logical Network : : Logical Network : | | : Logical Network : : Logical Network : |
| : Element : : Element : | | : Element : : Element : |
| :+-----+-----+-----+: :+-----+-----+-----+: | | :+-----+-----+-----+: :+-----+-----+-----+: |
| :| Net | Net | Net |: :| Net | Net | Net |: | | :| Net | Net | Net |: :| Net | Net | Net |: |
| :|Inst.|Inst.|Inst.|: :|Inst.|Inst.|Inst.|: | | :|Inst.|Inst.|Inst.|: :|Inst.|Inst.|Inst.|: |
| :+-----+-----+-----+: :+-----+-----+-----+: | | :+-----+-----+-----+: :+-----+-----+-----+: |
 End of changes. 7 change blocks. 
29 lines changed or deleted 16 lines changed or added

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