draft-ietf-netmod-rfc7277bis-02.txt   draft-ietf-netmod-rfc7277bis-03.txt 
Network Working Group M. Bjorklund Network Working Group M. Bjorklund
Internet-Draft Tail-f Systems Internet-Draft Tail-f Systems
Obsoletes: rfc7277 (if approved) January 9, 2018 Obsoletes: rfc7277 (if approved) January 11, 2018
Intended status: Standards Track Intended status: Standards Track
Expires: July 13, 2018 Expires: July 15, 2018
A YANG Data Model for IP Management A YANG Data Model for IP Management
draft-ietf-netmod-rfc7277bis-02 draft-ietf-netmod-rfc7277bis-03
Abstract Abstract
This document defines a YANG data model for management of IP This document defines a YANG data model for management of IP
implementations. The data model includes configuration and system implementations. The data model includes configuration and system
state. This document obsoletes RFC 7277. state.
The YANG model in this document conforms to the Network Management
Datastore Architecture defined in I-D.ietf-netmod-revised-datastores.
This document obsoletes RFC 7277.
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 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 July 13, 2018. This Internet-Draft will expire on July 15, 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
skipping to change at page 26, line 27 skipping to change at page 26, line 27
This document registers a YANG module in the "YANG Module Names" This document registers a YANG module in the "YANG Module Names"
registry [RFC6020]. registry [RFC6020].
Name: ietf-ip Name: ietf-ip
Namespace: urn:ietf:params:xml:ns:yang:ietf-ip Namespace: urn:ietf:params:xml:ns:yang:ietf-ip
Prefix: ip Prefix: ip
Reference: RFC 7277 Reference: RFC 7277
6. Security Considerations 6. Security Considerations
The YANG module defined in this document is designed to be accessed The YANG module specified in this document defines a schema for data
via network management protocols such as NETCONF [RFC6241] or that is designed to be accessed via network management protocols such
RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
layer, and the mandatory-to-implement secure transport is Secure is the secure transport layer, and the mandatory-to-implement secure
Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
mandatory-to-implement secure transport is TLS [RFC5246]. is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246].
The NETCONF access control model [RFC6536] provides the means to The NETCONF access control model [RFC6536] provides the means to
restrict access for particular NETCONF or RESTCONF users to a restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content. operations and content.
There are a number of data nodes defined in the YANG module which are There are a number of data nodes defined in the YANG module which are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations (e.g., edit-config)
skipping to change at page 31, line 31 skipping to change at page 31, line 31
<forwarding or:origin="or:default">false</forwarding> <forwarding or:origin="or:default">false</forwarding>
<mtu or:origin="or:system">1500</mtu> <mtu or:origin="or:system">1500</mtu>
<address> <address>
<ip>192.0.2.1</ip> <ip>192.0.2.1</ip>
<prefix-length>24</prefix-length> <prefix-length>24</prefix-length>
<origin>static</origin> <origin>static</origin>
</address> </address>
<neighbor or:origin="or:learned"> <neighbor or:origin="or:learned">
<ip>192.0.2.2</ip> <ip>192.0.2.2</ip>
<link-layer-address> <link-layer-address>
00:01:02:03:04:05 00:00:5E:00:53:AB
</link-layer-address> </link-layer-address>
</neighbor> </neighbor>
</ipv4> </ipv4>
<ipv6 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"> <ipv6 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
<enabled or:origin="or:default">true</enabled> <enabled or:origin="or:default">true</enabled>
<forwarding or:origin="or:default">false</forwarding> <forwarding or:origin="or:default">false</forwarding>
<mtu>1280</mtu> <mtu>1280</mtu>
<address> <address>
<ip>2001:db8::10</ip> <ip>2001:db8::10</ip>
<prefix-length>32</prefix-length> <prefix-length>32</prefix-length>
skipping to change at page 32, line 6 skipping to change at page 32, line 6
<address or:origin="or:learned"> <address or:origin="or:learned">
<ip>2001:db8::1:100</ip> <ip>2001:db8::1:100</ip>
<prefix-length>32</prefix-length> <prefix-length>32</prefix-length>
<origin>dhcp</origin> <origin>dhcp</origin>
<status>preferred</status> <status>preferred</status>
</address> </address>
<dup-addr-detect-transmits>0</dup-addr-detect-transmits> <dup-addr-detect-transmits>0</dup-addr-detect-transmits>
<neighbor or:origin="or:learned"> <neighbor or:origin="or:learned">
<ip>2001:db8::1</ip> <ip>2001:db8::1</ip>
<link-layer-address> <link-layer-address>
00:01:02:03:04:05 00:00:5E:00:53:AB
</link-layer-address> </link-layer-address>
<origin>dynamic</origin> <origin>dynamic</origin>
<is-router/> <is-router/>
<state>reachable</state> <state>reachable</state>
</neighbor> </neighbor>
<neighbor or:origin="or:learned"> <neighbor or:origin="or:learned">
<ip>2001:db8::4</ip> <ip>2001:db8::4</ip>
<origin>dynamic</origin> <origin>dynamic</origin>
<state>incomplete</state> <state>incomplete</state>
</neighbor> </neighbor>
 End of changes. 8 change blocks. 
13 lines changed or deleted 19 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/