--- 1/draft-ietf-netmod-rfc8022bis-04.txt 2017-12-20 16:13:28.679953351 -0800 +++ 2/draft-ietf-netmod-rfc8022bis-05.txt 2017-12-20 16:13:28.811956503 -0800 @@ -1,21 +1,21 @@ NETMOD Working Group L. Lhotka Internet-Draft CZ.NIC Intended status: Standards Track A. Lindem -Expires: June 15, 2018 Cisco Systems +Expires: June 23, 2018 Cisco Systems Y. Qu - Futurewei Technologies, Inc. - December 12, 2017 + Huawei + December 20, 2017 A YANG Data Model for Routing Management (NDMA Version) - draft-ietf-netmod-rfc8022bis-04 + draft-ietf-netmod-rfc8022bis-05 Abstract This document contains a specification of three YANG modules and one submodule. Together they form the core routing data model that serves as a framework for configuring and managing a routing subsystem. It is expected that these modules will be augmented by additional YANG modules defining data models for control-plane protocols, route filters, and other functions. The core routing data model provides common building blocks for such extensions -- routes, @@ -33,21 +33,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on June 15, 2018. + This Internet-Draft will expire on June 23, 2018. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -57,65 +57,66 @@ the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology and Notation . . . . . . . . . . . . . . . . . . 3 2.1. Glossary of New Terms . . . . . . . . . . . . . . . . . . 4 2.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 5 - 3. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 6 + 3. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. The Design of the Core Routing Data Model . . . . . . . . . . 6 4.1. System-Controlled and User-Controlled List Entries . . . 7 5. Basic Building Blocks . . . . . . . . . . . . . . . . . . . . 8 5.1. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.2. Routing Information Base (RIB) . . . . . . . . . . . . . 9 - 5.3. Control-Plane Protocol . . . . . . . . . . . . . . . . . 10 + 5.3. Control-Plane Protocol . . . . . . . . . . . . . . . . . 9 5.3.1. Routing Pseudo-Protocols . . . . . . . . . . . . . . 10 5.3.2. Defining New Control-Plane Protocols . . . . . . . . 10 5.4. Parameters of IPv6 Router Advertisements . . . . . . . . 11 6. Interactions with Other YANG Modules . . . . . . . . . . . . 12 6.1. Module "ietf-interfaces" . . . . . . . . . . . . . . . . 12 - 6.2. Module "ietf-ip" . . . . . . . . . . . . . . . . . . . . 13 + 6.2. Module "ietf-ip" . . . . . . . . . . . . . . . . . . . . 12 7. Routing Management YANG Module . . . . . . . . . . . . . . . 13 8. IPv4 Unicast Routing Management YANG Module . . . . . . . . . 28 - 9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 35 - 9.1. IPv6 Router Advertisements Submodule . . . . . . . . . . 43 + 9. IPv6 Unicast Routing Management YANG Module . . . . . . . . . 36 + 9.1. IPv6 Router Advertisements Submodule . . . . . . . . . . 44 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54 - 11. Security Considerations . . . . . . . . . . . . . . . . . . . 54 - 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 55 - 12.1. Normative References . . . . . . . . . . . . . . . . . . 55 - 12.2. Informative References . . . . . . . . . . . . . . . . . 56 - Appendix A. The Complete Data Trees . . . . . . . . . . . . . . 58 - Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 61 - Appendix C. Example: Adding a New Control-Plane Protocol . . . . 61 - Appendix D. Data Tree Example . . . . . . . . . . . . . . . . . 64 - Appendix E. NETCONF Get Data Reply Example . . . . . . . . . . . 70 - Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 73 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 73 + 11. Security Considerations . . . . . . . . . . . . . . . . . . . 55 + 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 56 + 12.1. Normative References . . . . . . . . . . . . . . . . . . 56 + 12.2. Informative References . . . . . . . . . . . . . . . . . 57 + Appendix A. The Complete Schema Tree . . . . . . . . . . . . . . 59 + Appendix B. Minimum Implementation . . . . . . . . . . . . . . . 64 + Appendix C. Example: Adding a New Control-Plane Protocol . . . . 64 + Appendix D. Data Tree Example . . . . . . . . . . . . . . . . . 67 + Appendix E. NETCONF Get Data Reply Example . . . . . . . . . . . 73 + Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 76 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 76 1. Introduction This document contains a specification of the following YANG modules: o The "ietf-routing" module provides generic components of a routing data model. o The "ietf-ipv4-unicast-routing" module augments the "ietf-routing" module with additional data specific to IPv4 unicast. o The "ietf-ipv6-unicast-routing" module augments the "ietf-routing" module with additional data specific to IPv6 unicast. Its submodule "ietf-ipv6-router-advertisements" also augments the - "ietf-interfaces" [RFC7223] and "ietf-ip" [RFC7277] modules with - IPv6 router configuration variables required by [RFC4861]. + "ietf-interfaces" [I-D.ietf-netmod-rfc7223bis] and "ietf- + ip" [I-D.ietf-netmod-rfc7277bis] modules with IPv6 router + configuration variables required by [RFC4861]. These modules together define the so-called core routing data model, which is intended as a basis for future data model development covering more-sophisticated routing systems. While these three modules can be directly used for simple IP devices with static routing (see Appendix B), their main purpose is to provide essential building blocks for more-complicated data models involving multiple control-plane protocols, multicast routing, additional address families, and advanced functions such as route filtering or policy routing. To this end, it is expected that the core routing data @@ -126,37 +127,40 @@ conforms to the Network Management Datastore Architecture (NMDA) [I-D.ietf-netmod-revised-datastores]. Consequently, this document obsoletes RFC 8022 [RFC8022]. 2. Terminology and Notation The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. - The following terms are defined in [RFC6241]: + The following terms are defined in + [I-D.ietf-netmod-revised-datastores]: o client + o server - o message - o protocol operation + o configuration - o server + o system state + + o operational state + + o intended configuration The following terms are defined in [RFC7950]: o action o augment - o configuration data - o container o container with presence o data model o data node o feature @@ -190,61 +194,42 @@ ("config false") that is created by the system independently of what has been explicitly configured. See Section 4.1 for details. user-controlled entry: An entry of a list in operational state data ("config false") that is created and deleted as a direct consequence of certain configuration changes. See Section 4.1 for details. 2.2. Tree Diagrams - A simplified graphical representation of the complete data tree is - presented in Appendix A, and similar diagrams of its various subtrees - appear in the main text. - - o Brackets "[" and "]" enclose list keys. - - o Curly braces "{" and "}" contain names of optional features that - make the corresponding node conditional. - - o Abbreviations before data node names: "rw" means configuration - (read-write), "ro" state data (read-only), "-x" RPC operations or - actions, and "-n" notifications. - - o Symbols after data node names: "?" means an optional node, "!" a - container with presence, and "*" denotes a "list" or "leaf-list". - - o Parentheses enclose choice and case nodes, and case nodes are also - marked with a colon (":"). - - o Ellipsis ("...") stands for contents of subtrees that are not - shown. + Tree diagrams used in this document follow the notation defined in + [I-D.ietf-netmod-yang-tree-diagrams]. 2.3. Prefixes in Data Node Names In this document, names of data nodes, actions, and other data model objects are often used without a prefix, as long as it is clear from the context in which YANG module each name is defined. Otherwise, names are prefixed using the standard prefix associated with the corresponding YANG module, as shown in Table 1. - +--------+---------------------------+-----------+ + +--------+---------------------------+------------------------------+ | Prefix | YANG module | Reference | - +--------+---------------------------+-----------+ - | if | ietf-interfaces | [RFC7223] | - | ip | ietf-ip | [RFC7277] | + +--------+---------------------------+------------------------------+ + | if | ietf-interfaces | [I-D.ietf-netmod-rfc7223bis] | + | ip | ietf-ip | [I-D.ietf-netmod-rfc7277bis] | | rt | ietf-routing | Section 7 | | v4ur | ietf-ipv4-unicast-routing | Section 8 | | v6ur | ietf-ipv6-unicast-routing | Section 9 | | yang | ietf-yang-types | [RFC6991] | | inet | ietf-inet-types | [RFC6991] | - +--------+---------------------------+-----------+ + +--------+---------------------------+------------------------------+ Table 1: Prefixes and Corresponding YANG Modules 3. Objectives The initial design of the core routing data model was driven by the following objectives: o The data model should be suitable for the common address families -- in particular, IPv4 and IPv6 -- and for unicast and multicast @@ -267,23 +252,23 @@ 4. The Design of the Core Routing Data Model The core routing data model consists of three YANG modules and one submodule. The first module, "ietf-routing", defines the generic components of a routing system. The other two modules, "ietf-ipv4- unicast-routing" and "ietf-ipv6-unicast-routing", augment the "ietf- routing" module with additional data nodes that are needed for IPv4 and IPv6 unicast routing, respectively. The "ietf-ipv6-unicast- routing" module has a submodule, "ietf-ipv6-router-advertisements", - that augments the "ietf-interfaces" [RFC7223] and "ietf-ip" [RFC7277] - modules with configuration variables for IPv6 router advertisements - as required by [RFC4861]. + that augments the "ietf-interfaces" [I-D.ietf-netmod-rfc7223bis] and + "ietf-ip" [I-D.ietf-netmod-rfc7277bis] modules with configuration + variables for IPv6 router advertisements as required by [RFC4861]. Figure 1 shows abridged views of the hierarchies. See Appendix A for the complete data trees. +--rw routing +--rw router-id? yang:dotted-quad +--ro interfaces | +--ro interface* if:interface-ref +--rw control-plane-protocols | +--rw control-plane-protocol* [type name] @@ -306,56 +291,57 @@ +---x active-route | +---w input | | +---w v4ur:destination-address? inet:ipv4-address | | +---w v6ur:destination-address? inet:ipv6-address | +--ro output | ... +--rw description? string Figure 1: Data Hierarchy - As can be seen from Figures 1, the core routing data model introduces + As can be seen from Figure 1, the core routing data model introduces several generic components of a routing framework: routes, RIBs containing lists of routes, and control-plane protocols. Section 5 describes these components in more detail. 4.1. System-Controlled and User-Controlled List Entries The core routing data model defines several lists in the schema tree, such as "rib", that have to be populated with at least one entry in any properly functioning device, and additional entries may be configured by a client. In such a list, the server creates the required item as a so-called - system-controlled entry in state data in the operational datastore - [I-D.ietf-netmod-revised-datastores], i.e., inside read-only lists in - the "routing" container. + system-controlled entry in state data in the operational state + datastore [I-D.ietf-netmod-revised-datastores], i.e., inside read- + only lists in the "routing" container. An example can be seen in Appendix D: the "/routing/ribs/rib" list has two system-controlled entries named "ipv4-master" and "ipv6-master". Additional entries may be created in the configuration by a client, e.g., via the NETCONF protocol. These are so-called user-controlled entries. If the server accepts a configured user-controlled entry, then this entry also appears in the state data version of the list. Corresponding entries in both versions of the list (in operational - datastore and intended datastore [I-D.ietf-netmod-revised-datastores] - have the same value of the list key. + state datastore and intended datastore + [I-D.ietf-netmod-revised-datastores] have the same value of the list + key. A client may also provide supplemental configuration of system- controlled entries. To do so, the client creates a new entry in the configuration with the desired contents. In order to bind this entry to the corresponding entry in the state data list in the operational - datastore, the key of the configuration entry has to be set to the - same value as the key of the state entry. + state datastore, the key of the configuration entry has to be set to + the same value as the key of the state entry. Deleting a user-controlled entry from the configuration list results in the removal of the corresponding entry in the state data list. In contrast, if client delets a system-controlled entry from the configuration list in the intended datastore, only the extra configuration specified in that entry is removed but the corresponding state data entry remains in the list in the operational datastore. 5. Basic Building Blocks @@ -389,26 +375,26 @@ 5.2. Routing Information Base (RIB) Every implementation of the core routing data model manages one or more Routing Information Bases (RIBs). A RIB is a list of routes complemented with administrative data. Each RIB contains only routes of one address family. An address family is represented by an identity derived from the "rt:address-family" base identity. In the core routing data model, RIBs are state data represented as - entries of the list "/routing/ribs/rib" in the operational datastore - [I-D.ietf-netmod-revised-datastores]. The contents of RIBs are - controlled and manipulated by control-plane protocol operations that - may result in route additions, removals, and modifications. This - also includes manipulations via the "static" and/or "direct" pseudo- - protocols; see Section 5.3.1. + entries of the list "/routing/ribs/rib" in the operational state + datastore [I-D.ietf-netmod-revised-datastores]. The contents of RIBs + are controlled and manipulated by control-plane protocol operations + that may result in route additions, removals, and modifications. + This also includes manipulations via the "static" and/or "direct" + pseudo-protocols; see Section 5.3.1. For every supported address family, exactly one RIB MUST be marked as the so-called default RIB to which control-plane protocols place their routes by default. Simple router implementations that do not advertise the feature "multiple-ribs" will typically create one system-controlled RIB per supported address family and mark it as the default RIB. More-complex router implementations advertising the "multiple-ribs" @@ -524,53 +512,53 @@ * on-link-flag * preferred-lifetime * autonomous-flag NOTES: 1. The "IsRouter" flag, which is also required by [RFC4861], is - implemented in the "ietf-ip" module [RFC7277] (leaf - "ip:forwarding"). + implemented in the "ietf-ip" module [I-D.ietf-netmod-rfc7277bis] + (leaf "ip:forwarding"). 2. The original specification [RFC4861] allows the implementations to decide whether the "valid-lifetime" and "preferred-lifetime" parameters remain the same in consecutive advertisements or decrement in real time. However, the latter behavior seems problematic because the values might be reset again to the (higher) configured values after a configuration is reloaded. Moreover, no implementation is known to use the decrementing behavior. The "ietf-ipv6-router-advertisements" submodule therefore stipulates the former behavior with constant values. 6. Interactions with Other YANG Modules The semantics of the core routing data model also depends on several configuration parameters that are defined in other YANG modules. 6.1. Module "ietf-interfaces" The following boolean switch is defined in the "ietf-interfaces" YANG - module [RFC7223]: + module [I-D.ietf-netmod-rfc7223bis]: /if:interfaces/if:interface/if:enabled If this switch is set to "false" for a network-layer interface, then all routing and forwarding functions MUST be disabled on this interface. 6.2. Module "ietf-ip" The following boolean switches are defined in the "ietf-ip" YANG - module [RFC7277]: + module [I-D.ietf-netmod-rfc7277bis]: /if:interfaces/if:interface/ip:ipv4/ip:enabled If this switch is set to "false" for a network-layer interface, then all IPv4 routing and forwarding functions MUST be disabled on this interface. /if:interfaces/if:interface/ip:ipv4/ip:forwarding If this switch is set to "false" for a network-layer interface, @@ -594,66 +582,70 @@ In addition, the "ietf-ip" module allows for configuring IPv4 and IPv6 addresses and network prefixes or masks on network-layer interfaces. Configuration of these parameters on an enabled interface MUST result in an immediate creation of the corresponding direct route. The destination prefix of this route is set according to the configured IP address and network prefix/mask, and the interface is set as the outgoing interface for that route. 7. Routing Management YANG Module - file "ietf-routing@2017-12-11.yang" + file "ietf-routing@2017-12-20.yang" module ietf-routing { yang-version "1.1"; namespace "urn:ietf:params:xml:ns:yang:ietf-routing"; prefix "rt"; import ietf-yang-types { prefix "yang"; } import ietf-interfaces { prefix "if"; + description "A Network Management Datastore Architecture (NDMA) + compatible version of the ietf-interfaces module + is required."; } organization "IETF NETMOD - Networking Modeling Working Group"; contact "WG Web: WG List: Editor: Ladislav Lhotka Acee Lindem Yingzhen Qu "; description "This YANG module defines essential components for the management - of a routing subsystem. + of a routing subsystem. The model fully conforms to the Network + Management Datastore Architecture (NMDA). Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; reference "RFC XXXX"; - revision 2017-12-11 { + revision 2017-12-20 { description "Network Managment Datastore Architecture (NDMA) Revision"; reference "RFC XXXX: A YANG Data Model for Routing Management (NDMA Version)"; } revision 2016-11-04 { description "Initial revision."; @@ -687,73 +680,73 @@ /* Identities */ identity address-family { description "Base identity from which identities describing address families are derived."; } identity ipv4 { - base rt:address-family; + base address-family; description "This identity represents IPv4 address family."; } identity ipv6 { - base rt:address-family; + base address-family; description "This identity represents IPv6 address family."; } identity control-plane-protocol { description "Base identity from which control-plane protocol identities are derived."; } identity routing-protocol { - base rt:control-plane-protocol; + base control-plane-protocol; description "Identity from which Layer 3 routing protocol identities are derived."; } identity direct { - base rt:routing-protocol; + base routing-protocol; description "Routing pseudo-protocol that provides routes to directly connected networks."; } identity static { - base rt:routing-protocol; + base routing-protocol; description "Static routing pseudo-protocol."; } /* Type Definitions */ typedef route-preference { type uint32; description "This type is used for route preferences."; } /* Groupings */ grouping address-family { description "This grouping provides a leaf identifying an address family."; leaf address-family { type identityref { - base rt:address-family; + base address-family; } mandatory "true"; description "Address family."; } } grouping router-id { description @@ -907,21 +900,21 @@ } } } } grouping route-metadata { description "Common route metadata."; leaf source-protocol { type identityref { - base rt:routing-protocol; + base routing-protocol; } mandatory "true"; description "Type of the routing protocol from which the route originated."; } leaf active { type empty; description "Presence of this leaf indicates that the route is preferred @@ -930,21 +923,21 @@ } leaf last-updated { type yang:date-and-time; description "Time stamp of the last modification of the route. If the route was never modified, it is the time when the route was inserted into the RIB."; } } - /* Configuration Data */ + /* Data nodes */ container routing { description "Configuration parameters for the routing subsystem."; uses router-id { if-feature "router-id"; description "Configuration of the global router ID. Routing protocols that use router ID can use this parameter or override it with another value."; @@ -963,21 +956,21 @@ container control-plane-protocols { description "Configuration of control-plane protocol instances."; list control-plane-protocol { key "type name"; description "Each entry contains configuration of a control-plane protocol instance."; leaf type { type identityref { - base rt:control-plane-protocol; + base control-plane-protocol; } description "Type of the control-plane protocol - an identity derived from the 'control-plane-protocol' base identity."; } leaf name { type string; description "An arbitrary name of the control-plane protocol instance."; @@ -1141,21 +1134,21 @@ status obsolete; description "State data of a control-plane protocol instance. An implementation MUST provide exactly one system-controlled instance of the 'direct' pseudo-protocol. Instances of other control-plane protocols MAY be created by configuration."; leaf type { type identityref { - base rt:control-plane-protocol; + base control-plane-protocol; } status obsolete; description "Type of the control-plane protocol."; } leaf name { type string; status obsolete; description "The name of the control-plane protocol instance. @@ -1279,50 +1272,55 @@ } } } } } } 8. IPv4 Unicast Routing Management YANG Module - file "ietf-ipv4-unicast-routing@2017-12-11.yang" + file "ietf-ipv4-unicast-routing@2017-12-20.yang" module ietf-ipv4-unicast-routing { yang-version "1.1"; namespace "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"; prefix "v4ur"; import ietf-routing { prefix "rt"; + description "A Network Management Datastore Architecture (NDMA) + compatible version of the ietf-routing module + is required."; } import ietf-inet-types { prefix "inet"; } organization "IETF NETMOD - Networking Modeling Working Group"; contact "WG Web: WG List: Editor: Ladislav Lhotka Acee Lindem Yingzhen Qu "; description "This YANG module augments the 'ietf-routing' module with basic - configuration and state data for IPv4 unicast routing. + configuration and state data for IPv4 unicast routing. The + model fully conforms to the Network Management Datastore + Architecture (NMDA). Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). @@ -1319,26 +1317,25 @@ Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). - This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; reference "RFC XXXX"; - revision 2017-12-11 { + revision 2017-12-20 { description "Network Managment Datastore Architecture (NDMA) Revision"; reference "RFC XXXX: A YANG Data Model for Routing Management (NDMA Version)"; } revision 2016-11-04 { description "Initial revision."; @@ -1655,70 +1653,79 @@ status obsolete; description "IPv4 address of the next hop."; } } } 9. IPv6 Unicast Routing Management YANG Module - file "ietf-ipv6-unicast-routing@2017-12-11.yang" + file "ietf-ipv6-unicast-routing@2017-12-20.yang" module ietf-ipv6-unicast-routing { yang-version "1.1"; namespace "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing"; prefix "v6ur"; + import ietf-routing { prefix "rt"; + description "A Network Management Datastore Architecture (NDMA) + compatible version of the ietf-routing module + is required."; } import ietf-inet-types { prefix "inet"; + description "A Network Management Datastore Architecture (NDMA) + compatible version of the ietf-interfaces module + is required."; } include ietf-ipv6-router-advertisements { - revision-date 2017-12-11; + revision-date 2017-12-20; } organization "IETF NETMOD - Networking Modeling Working Group"; contact "WG Web: WG List: Editor: Ladislav Lhotka Acee Lindem Yingzhen Qu "; description "This YANG module augments the 'ietf-routing' module with basic - configuration and state data for IPv6 unicast routing. + configuration and state data for IPv6 unicast routing. The + model fully conforms to the Network Management Datastore + Architecture (NMDA). Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; reference "RFC XXXX"; - revision 2017-12-11 { + revision 2017-12-20 { description "Network Managment Datastore Architecture (NDMA) revision"; reference "RFC XXXX: A YANG Data Model for Routing Management (NDMA Version)"; } /* Identities */ revision 2016-11-04 { @@ -1845,21 +1853,21 @@ description "Augment 'next-hop-list' case in the reply to the 'active-route' action."; leaf next-hop-address { type inet:ipv6-address; description "IPv6 address of the next hop."; } } - /* Configuration data */ + /* Data node augmentations */ augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:static-routes" { description "This augment defines the configuration of the 'static' pseudo-protocol with data specific to IPv6 unicast."; container ipv6 { description "Configuration of a 'static' pseudo-protocol instance consists of a list of routes."; @@ -2028,27 +2037,28 @@ status obsolete; description "Augment 'next-hop-list' case in the reply to the 'active-route' action."; leaf next-hop-address { type inet:ipv6-address; status obsolete; description "IPv6 address of the next hop."; } + } } 9.1. IPv6 Router Advertisements Submodule - file "ietf-ipv6-router-advertisements@2017-12-11.yang" + file "ietf-ipv6-router-advertisements@2017-12-20.yang" submodule ietf-ipv6-router-advertisements { yang-version "1.1"; belongs-to ietf-ipv6-unicast-routing { prefix "v6ur"; } import ietf-inet-types { prefix "inet"; } @@ -2045,67 +2055,78 @@ submodule ietf-ipv6-router-advertisements { yang-version "1.1"; belongs-to ietf-ipv6-unicast-routing { prefix "v6ur"; } import ietf-inet-types { prefix "inet"; } + import ietf-interfaces { prefix "if"; + description "A Network Management Datastore Architecture (NDMA) + compatible version of the ietf-interfaces module + is required."; } import ietf-ip { prefix "ip"; + description "A Network Management Datastore Architecture (NDMA) + compatible version of the ietf-ip module is + required."; } organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: Editor: Ladislav Lhotka Acee Lindem Yingzhen Qu "; description "This YANG module augments the 'ietf-ip' module with configuration and state data of IPv6 router advertisements. + The model fully conforms to the Network Management Datastore + Architecture (NMDA). + Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; reference "RFC 4861: Neighbor Discovery for IP version 6 (IPv6)."; - revision 2017-12-11 { + revision 2017-12-20 { description "Network Managment Datastore Architecture (NDMA) Revision"; reference "RFC XXXX: A YANG Data Model for Routing Management (NDMA Version)"; } + revision 2016-11-04 { description "Initial revision."; reference "RFC 8022: A YANG Data Model for Routing Management"; } augment "/if:interfaces/if:interface/ip:ipv6" { description "Augment interface configuration with parameters of IPv6 @@ -2565,27 +2587,35 @@ This document registers the following YANG submodule in the "YANG Module Names" registry [RFC6020]: Name: ietf-ipv6-router-advertisements Module: ietf-ipv6-unicast-routing Reference: RFC 8022 11. Security Considerations - The YANG module defined in this memo is designed to be accessed via - the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the - secure transport layer and the mandatory-to-implement secure - transport is SSH [RFC6242]. + The YANG module specified in this document defines a schedma for data + that is designed to be accessed via network management protocols such + as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer + is the secure transport layer, and the mandatory-to-implement secure + transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer + is HTTPS, and the mandatory-to-implement secure transport is TLS + [RFC5246]. - There are a number of data nodes defined in this YANG module which - are writable/creatable/deletable (i.e., config true, which is the + The NETCONF access control model [RFC6536] provides the means to + restrict access for particular NETCONF or RESTCONF users to a + preconfigured subset of all available NETCONF or RESTCONF protocol + operations and content. + + There are a number of data nodes defined in this YANG module that are + writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability: /routing/control-plane-protocols/control-plane-protocol: This list specifies the control-plane protocols configured on a device. /routing/ribs/rib: This list specifies the RIBs configured for the @@ -2617,199 +2647,307 @@ [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, DOI 10.17487/RFC4861, September 2007, . + [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security + (TLS) Protocol Version 1.2", RFC 5246, + DOI 10.17487/RFC5246, August 2008, . + [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, . [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, . [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . + [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration + Protocol (NETCONF) Access Control Model", RFC 6536, + DOI 10.17487/RFC6536, March 2012, . + [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, July 2013, . - [RFC7223] Bjorklund, M., "A YANG Data Model for Interface - Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, - . + [I-D.ietf-netmod-rfc7223bis] + Bjorklund, M., "A YANG Data Model for Interface + Management", draft-ietf-netmod-rfc7223bis-01 (work in + progress), December 2017. - [RFC7277] Bjorklund, M., "A YANG Data Model for IP Management", - RFC 7277, DOI 10.17487/RFC7277, June 2014, - . + [I-D.ietf-netmod-rfc7277bis] + Bjorklund, M., "A YANG Data Model for IP Management", + draft-ietf-netmod-rfc7277bis-01 (work in progress), + December 2017. [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing Management", RFC 8022, DOI 10.17487/RFC8022, November 2016, . + [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF + Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, + . + + [I-D.ietf-netmod-revised-datastores] + Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., + and R. Wilton, "Network Management Datastore + Architecture", draft-ietf-netmod-revised-datastores-07 + (work in progress), November 2017. + 12.2. Informative References - [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG - Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, - January 2011, . + [I-D.ietf-netmod-rfc6087bis] + Bierman, A., "Guidelines for Authors and Reviewers of YANG + Data Model Documents", draft-ietf-netmod-rfc6087bis-15 + (work in progress), December 2017. [RFC7895] Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module Library", RFC 7895, DOI 10.17487/RFC7895, June 2016, . [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", RFC 7951, DOI 10.17487/RFC7951, August 2016, . - [I-D.ietf-netmod-revised-datastores] - Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., - and R. Wilton, "Network Management Datastore - Architecture", draft-ietf-netmod-revised-datastores-07 - (work in progress), November 2017. + [I-D.ietf-netmod-yang-tree-diagrams] + Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- + ietf-netmod-yang-tree-diagrams-02 (work in progress), + October 2017. -Appendix A. The Complete Data Trees +Appendix A. The Complete Schema Tree This appendix presents the complete tree of the core routing data model. See Section 2.2 for an explanation of the symbols used. The data type of every leaf node is shown near the right end of the corresponding line. module: ietf-routing +--rw routing - +--rw router-id? yang:dotted-quad - +--ro interfaces - | +--ro interface* if:interface-ref - +--rw control-plane-protocols - | +--rw control-plane-protocol* [type name] - | +--rw type identityref - | +--rw name string - | +--rw description? string - | +--rw static-routes - | +--rw v4ur:ipv4 - | | +--rw v4ur:route* [destination-prefix] - | | +--rw v4ur:destination-prefix inet:ipv4-prefix - | | +--rw v4ur:description? string - | | +--rw v4ur:next-hop - | | +--rw (v4ur:next-hop-options) - | | +--:(v4ur:simple-next-hop) + | +--rw router-id? yang:dotted-quad + | +--ro interfaces + | | +--ro interface* if:interface-ref + | +--rw control-plane-protocols + | | +--rw control-plane-protocol* [type name] + | | +--rw type identityref + | | +--rw name string + | | +--rw description? string + | | +--rw static-routes + | | +--rw v4ur:ipv4 + | | | +--rw v4ur:route* [destination-prefix] + | | | +--rw v4ur:destination-prefix + | | | | inet:ipv4-prefix + | | | +--rw v4ur:description? string + | | | +--rw v4ur:next-hop + | | | +--rw (v4ur:next-hop-options) + | | | +--:(v4ur:simple-next-hop) + | | | | +--rw v4ur:outgoing-interface? + | | | | | if:interface-ref + | | | | +--rw v4ur:next-hop-address? + | | | | inet:ipv4-address + | | | +--:(v4ur:special-next-hop) + | | | | +--rw v4ur:special-next-hop? + | | | | enumeration + | | | +--:(v4ur:next-hop-list) + | | | +--rw v4ur:next-hop-list + | | | +--rw v4ur:next-hop* [index] + | | | +--rw v4ur:index + | | | | string | | | +--rw v4ur:outgoing-interface? - | | | if:interface-ref + | | | | if:interface-ref | | | +--rw v4ur:next-hop-address? | | | inet:ipv4-address - | | +--:(v4ur:special-next-hop) - | | | +--rw v4ur:special-next-hop? enumeration - | | +--:(v4ur:next-hop-list) - | | +--rw v4ur:next-hop-list - | | +--rw v4ur:next-hop* [index] - | | +--rw v4ur:index string - | | +--rw v4ur:outgoing-interface? - | | if:interface-ref - | | +--rw v4ur:next-hop-address? - | | inet:ipv4-address - | +--rw v6ur:ipv6 - | +--rw v6ur:route* [destination-prefix] - | +--rw v6ur:destination-prefix inet:ipv6-prefix - | +--rw v6ur:description? string - | +--rw v6ur:next-hop - | +--rw (v6ur:next-hop-options) - | +--:(v6ur:simple-next-hop) + | | +--rw v6ur:ipv6 + | | +--rw v6ur:route* [destination-prefix] + | | +--rw v6ur:destination-prefix + | | | inet:ipv6-prefix + | | +--rw v6ur:description? string + | | +--rw v6ur:next-hop + | | +--rw (v6ur:next-hop-options) + | | +--:(v6ur:simple-next-hop) + | | | +--rw v6ur:outgoing-interface? + | | | | if:interface-ref + | | | +--rw v6ur:next-hop-address? + | | | inet:ipv6-address + | | +--:(v6ur:special-next-hop) + | | | +--rw v6ur:special-next-hop? + | | | enumeration + | | +--:(v6ur:next-hop-list) + | | +--rw v6ur:next-hop-list + | | +--rw v6ur:next-hop* [index] + | | +--rw v6ur:index + | | | string | | +--rw v6ur:outgoing-interface? - | | if:interface-ref + | | | if:interface-ref | | +--rw v6ur:next-hop-address? | | inet:ipv6-address - | +--:(v6ur:special-next-hop) - | | +--rw v6ur:special-next-hop? enumeration - | +--:(v6ur:next-hop-list) - | +--rw v6ur:next-hop-list - | +--rw v6ur:next-hop* [index] - | +--rw v6ur:index string - | +--rw v6ur:outgoing-interface? - | if:interface-ref - | +--rw v6ur:next-hop-address? - | inet:ipv6-address - +--rw ribs - +--rw rib* [name] - +--rw name string - +--rw address-family? identityref - +--ro default-rib? boolean {multiple-ribs}? - +--ro routes - | +--ro route* - | +--ro route-preference? route-preference - | +--ro next-hop - | | +--ro (next-hop-options) - | | +--:(simple-next-hop) + | +--rw ribs + | +--rw rib* [name] + | +--rw name string + | +--rw address-family identityref + | +--ro default-rib? boolean {multiple-ribs}? + | +--ro routes + | | +--ro route* + | | +--ro route-preference? route-preference + | | +--ro next-hop + | | | +--ro (next-hop-options) + | | | +--:(simple-next-hop) + | | | | +--ro outgoing-interface? + | | | | | if:interface-ref + | | | | +--ro v4ur:next-hop-address? + | | | | | inet:ipv4-address + | | | | +--ro v6ur:next-hop-address? + | | | | inet:ipv6-address + | | | +--:(special-next-hop) + | | | | +--ro special-next-hop? enumeration + | | | +--:(next-hop-list) + | | | +--ro next-hop-list + | | | +--ro next-hop* + | | | +--ro outgoing-interface? + | | | | if:interface-ref + | | | +--ro v4ur:address? + | | | | inet:ipv4-address + | | | +--ro v6ur:address? + | | | inet:ipv6-address + | | +--ro source-protocol identityref + | | +--ro active? empty + | | +--ro last-updated? yang:date-and-time + | | +--ro v4ur:destination-prefix? inet:ipv4-prefix + | | +--ro v6ur:destination-prefix? inet:ipv6-prefix + | +---x active-route + | | +---w input + | | | +---w v4ur:destination-address? inet:ipv4-address + | | | +---w v6ur:destination-address? inet:ipv6-address + | | +--ro output + | | +--ro route + | | +--ro next-hop + | | | +--ro (next-hop-options) + | | | +--:(simple-next-hop) + | | | | +--ro outgoing-interface? + | | | | | if:interface-ref + | | | | +--ro v4ur:next-hop-address? + | | | | | inet:ipv4-address + | | | | +--ro v6ur:next-hop-address? + | | | | inet:ipv6-address + | | | +--:(special-next-hop) + | | | | +--ro special-next-hop? + | | | | enumeration + | | | +--:(next-hop-list) + | | | +--ro next-hop-list + | | | +--ro next-hop* | | | +--ro outgoing-interface? | | | | if:interface-ref | | | +--ro v4ur:next-hop-address? | | | | inet:ipv4-address | | | +--ro v6ur:next-hop-address? | | | inet:ipv6-address - | | +--:(special-next-hop) - | | | +--ro special-next-hop? enumeration - | | +--:(next-hop-list) - | | +--ro next-hop-list - | | +--ro next-hop* - | | +--ro outgoing-interface? - | | | if:interface-ref - | | +--ro v4ur:address? - | | | inet:ipv4-address - | | +--ro v6ur:address? - | | inet:ipv6-address - | +--ro source-protocol identityref - | +--ro active? empty - | +--ro last-updated? yang:date-and-time - | +--ro v4ur:destination-prefix? inet:ipv4-prefix - | +--ro v6ur:destination-prefix? inet:ipv6-prefix - +---x active-route - | +---w input - | | +---w v4ur:destination-address? inet:ipv4-address - | | +---w v6ur:destination-address? inet:ipv6-address - | +--ro output - | +--ro route - | +--ro next-hop + | | +--ro source-protocol identityref + | | +--ro active? empty + | | +--ro last-updated? + | | | yang:date-and-time + | | +--ro v4ur:destination-prefix? + | | | inet:ipv4-prefix + | | +--ro v6ur:destination-prefix? + | | inet:ipv6-prefix + | +--rw description? string + o--ro routing-state + +--ro router-id? yang:dotted-quad + o--ro interfaces + | o--ro interface* if:interface-state-ref + o--ro control-plane-protocols + | o--ro control-plane-protocol* [type name] + | o--ro type identityref + | o--ro name string + o--ro ribs + o--ro rib* [name] + o--ro name string + +--ro address-family identityref + o--ro default-rib? boolean {multiple-ribs}? + o--ro routes + | o--ro route* + | o--ro route-preference? route-preference + | o--ro next-hop | | +--ro (next-hop-options) | | +--:(simple-next-hop) | | | +--ro outgoing-interface? | | | | if:interface-ref - | | | +--ro v4ur:next-hop-address? + | | | o--ro v4ur:next-hop-address? | | | | inet:ipv4-address - | | | +--ro v6ur:next-hop-address? + | | | o--ro v6ur:next-hop-address? | | | inet:ipv6-address | | +--:(special-next-hop) | | | +--ro special-next-hop? enumeration | | +--:(next-hop-list) | | +--ro next-hop-list | | +--ro next-hop* | | +--ro outgoing-interface? | | | if:interface-ref - | | +--ro v4ur:next-hop-address? + | | o--ro v4ur:address? | | | inet:ipv4-address - | | +--ro v6ur:next-hop-address? + | | o--ro v6ur:address? | | inet:ipv6-address | +--ro source-protocol identityref | +--ro active? empty | +--ro last-updated? yang:date-and-time - | +--ro v4ur:destination-prefix? inet:ipv4-prefix - | +--ro v6ur:destination-prefix? inet:ipv6-prefix - +--rw description? string + | o--ro v4ur:destination-prefix? inet:ipv4-prefix + | o--ro v6ur:destination-prefix? inet:ipv6-prefix + o---x active-route + +---w input + | o---w v4ur:destination-address? inet:ipv4-address + | o---w v6ur:destination-address? inet:ipv6-address + +--ro output + o--ro route + o--ro next-hop + | +--ro (next-hop-options) + | +--:(simple-next-hop) + | | +--ro outgoing-interface? + | | | if:interface-ref + | | o--ro v4ur:next-hop-address? + | | | inet:ipv4-address + | | o--ro v6ur:next-hop-address? + | | inet:ipv6-address + | +--:(special-next-hop) + | | +--ro special-next-hop? + | | enumeration + | +--:(next-hop-list) + | +--ro next-hop-list + | +--ro next-hop* + | +--ro outgoing-interface? + | | if:interface-ref + | o--ro v4ur:next-hop-address? + | | inet:ipv4-address + | o--ro v6ur:next-hop-address? + | inet:ipv6-address + +--ro source-protocol identityref + +--ro active? empty + +--ro last-updated? + | yang:date-and-time + o--ro v4ur:destination-prefix? + | inet:ipv4-prefix + o--ro v6ur:destination-prefix? + inet:ipv6-prefix module: ietf-ipv6-unicast-routing augment /if:interfaces/if:interface/ip:ipv6: +--rw ipv6-router-advertisements +--rw send-advertisements? boolean +--rw max-rtr-adv-interval? uint16 +--rw min-rtr-adv-interval? uint16 +--rw managed-flag? boolean +--rw other-config-flag? boolean +--rw link-mtu? uint32 +--rw reachable-time? uint32 @@ -2820,20 +2958,39 @@ +--rw prefix* [prefix-spec] +--rw prefix-spec inet:ipv6-prefix +--rw (control-adv-prefixes)? +--:(no-advertise) | +--rw no-advertise? empty +--:(advertise) +--rw valid-lifetime? uint32 +--rw on-link-flag? boolean +--rw preferred-lifetime? uint32 +--rw autonomous-flag? boolean + augment /if:interfaces-state/if:interface/ip:ipv6: + o--ro ipv6-router-advertisements + o--ro send-advertisements? boolean + o--ro max-rtr-adv-interval? uint16 + o--ro min-rtr-adv-interval? uint16 + o--ro managed-flag? boolean + o--ro other-config-flag? boolean + o--ro link-mtu? uint32 + o--ro reachable-time? uint32 + o--ro retrans-timer? uint32 + o--ro cur-hop-limit? uint8 + o--ro default-lifetime? uint16 + o--ro prefix-list + o--ro prefix* [prefix-spec] + o--ro prefix-spec inet:ipv6-prefix + o--ro valid-lifetime? uint32 + o--ro on-link-flag? boolean + o--ro preferred-lifetime? uint32 + o--ro autonomous-flag? boolean Appendix B. Minimum Implementation Some parts and options of the core routing model, such as user- defined RIBs, are intended only for advanced routers. This appendix gives basic non-normative guidelines for implementing a bare minimum of available functions. Such an implementation may be used for hosts or very simple routers. A minimum implementation does not support the feature @@ -2854,29 +3011,31 @@ restricting the data model, e.g., limiting the number of "static" control-plane protocol instances. Appendix C. Example: Adding a New Control-Plane Protocol This appendix demonstrates how the core routing data model can be extended to support a new control-plane protocol. The YANG module "example-rip" shown below is intended as an illustration rather than a real definition of a data model for the Routing Information Protocol (RIP). For the sake of brevity, this module does not obey - all the guidelines specified in [RFC6087]. See also Section 5.3.2. + all the guidelines specified in [I-D.ietf-netmod-rfc6087bis]. See + also Section 5.3.2. module example-rip { yang-version "1.1"; namespace "http://example.com/rip"; prefix "rip"; + import ietf-interfaces { prefix "if"; } import ietf-routing { prefix "rt"; } identity rip { base rt:routing-protocol; @@ -2978,45 +3136,46 @@ encoding [RFC7951], containing both configuration and state data. The data conforms to a data model that is defined by the following YANG library specification [RFC7895]: { "ietf-yang-library:modules-state": { "module-set-id": "c2e1f54169aa7f36e1a6e8d0865d441d3600f9c4", "module": [ { "name": "ietf-routing", - "revision": "2017-12-11", + "revision": "2017-12-20", "feature": [ "multiple-ribs", "router-id" ], "namespace": "urn:ietf:params:xml:ns:yang:ietf-routing", "conformance-type": "implement" }, { "name": "ietf-ipv4-unicast-routing", - "revision": "2017-12-11", + "revision": "2017-12-20", "namespace": "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing", "conformance-type": "implement" }, { "name": "ietf-ipv6-unicast-routing", - "revision": "2017-12-11", + "revision": "2017-12-20", "namespace": "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing-3", + "conformance-type": "implement" }, { "name": "ietf-interfaces", - "revision": "2017-08-17", + "revision": "2017-12-16", "namespace": "urn:ietf:params:xml:ns:yang:ietf-interfaces", "conformance-type": "implement" }, { "name": "ietf-inet-types", "namespace": "urn:ietf:params:xml:ns:yang:ietf-inet-types", "revision": "2013-07-15", "conformance-type": "import" }, { @@ -3026,21 +3185,21 @@ "conformance-type": "import" }, { "name": "iana-if-type", "namespace": "urn:ietf:params:xml:ns:yang:iana-if-type", "revision": "", "conformance-type": "implement" }, { "name": "ietf-ip", - "revision": "2014-06-16", + "revision": "2017-12-16", "namespace": "urn:ietf:params:xml:ns:yang:ietf-ip", "conformance-type": "implement" } ] } } A simple network setup as shown in Figure 2 is assumed: router "A" uses static default routes with the "ISP" router as the next hop. IPv6 router advertisements are configured only on the "eth1" @@ -3338,21 +3497,21 @@ eth0 0 ietf-routing:direct 2015-10-24T17:11:27+02:00 - 98.51.100.0/24 + 198.51.100.0/24 eth1 0 ietf-routing:direct 2015-10-24T17:11:27+02:00 0.0.0.0/0 @@ -3413,33 +3572,33 @@ Acknowledgments The authors wish to thank Nitin Bahadur, Martin Bjorklund, Dean Bogdanovic, Jeff Haas, Joel Halpern, Wes Hardaker, Sriganesh Kini, David Lamparter, Andrew McGregor, Jan Medved, Xiang Li, Stephane - Litkowski, Thomas Morin, Tom Petch, Yingzhen Qu, Bruno Rijsman, + Litkowski, Thomas Morin, Tom Petch, Bruno Rijsman, Juergen Schoenwaelder, Phil Shafer, Dave Thaler, Yi Yang, Derek Man-Kit Yeung, Jeffrey Zhang, Vladimir Vassilev, and Rob Wilton for their helpful comments and suggestions. Authors' Addresses Ladislav Lhotka CZ.NIC EMail: lhotka@nic.cz Acee Lindem Cisco Systems EMail: acee@cisco.com Yingzhen Qu - Futurewei Technologies, Inc. + Huawei 2330 Central Expressway Santa Clara CA 95050 USA EMail: yingzhen.qu@huawei.com