--- 1/draft-ietf-netmod-routing-cfg-07.txt	2013-02-11 17:03:43.763708416 +0100
+++ 2/draft-ietf-netmod-routing-cfg-08.txt	2013-02-11 17:03:43.851709370 +0100
@@ -1,18 +1,18 @@
 
 NETMOD                                                         L. Lhotka
 Internet-Draft                                                    CZ.NIC
 Intended status: Standards Track                       February 11, 2013
 Expires: August 15, 2013
 
                 A YANG Data Model for Routing Management
-                    draft-ietf-netmod-routing-cfg-07
+                    draft-ietf-netmod-routing-cfg-08
 
 Abstract
 
    This document contains a specification of three YANG modules.
    Together they form the core routing data model which 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 individual routing protocols and
    other related functions.  The core routing data model provides common
    building blocks for such extensions - router instances, routes,
@@ -204,23 +204,23 @@
            | if     | ietf-interfaces           | [YANG-IF]    |
            |        |                           |              |
            | ip     | ietf-ip                   | [YANG-IP]    |
            |        |                           |              |
            | rt     | ietf-routing              | Section 6    |
            |        |                           |              |
            | v4ur   | ietf-ipv4-unicast-routing | Section 7    |
            |        |                           |              |
            | v6ur   | ietf-ipv6-unicast-routing | Section 8    |
            |        |                           |              |
-           | yang   | ietf-yang-types           | [RFC6021]    |
+           | yang   | ietf-yang-types           | [RFC6021bis] |
            |        |                           |              |
-           | inet   | ietf-inet-types           | [RFC6021]    |
+           | inet   | ietf-inet-types           | [RFC6021bis] |
            +--------+---------------------------+--------------+
 
              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,
@@ -2122,34 +2122,36 @@
               January 2004.
 
    [RFC4861]  Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
               "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
               September 2007.
 
    [RFC6020]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
               Network Configuration Protocol (NETCONF)", RFC 6020,
               September 2010.
 
-   [RFC6021]  Schoenwaelder, J., Ed., "Common YANG Data Types",
-              RFC 6021, September 2010.
+   [RFC6021bis]
+              Schoenwaelder, J., Ed., "Common YANG Data Types",
+              draft-ietf-netmod-rfc6021-bis-00 (work in progress),
+              February 2013.
 
    [RFC6241]  Enns, R., Bjorklund, M., Schoenwaelder, J., and A.
               Bierman, "NETCONF Configuration Protocol", RFC 6241,
               June 2011.
 
    [YANG-IF]  Bjorklund, M., "A YANG Data Model for Interface
-              Configuration", draft-ietf-netmod-interfaces-cfg-08 (work
-              in progress), November 2012.
+              Configuration", draft-ietf-netmod-interfaces-cfg-09 (work
+              in progress), February 2013.
 
    [YANG-IP]  Bjorklund, M., "A YANG Data Model for IP Configuration",
-              draft-ietf-netmod-ip-cfg-07 (work in progress),
-              November 2012.
+              draft-ietf-netmod-ip-cfg-09 (work in progress),
+              February 2012.
 
 12.2.  Informative References
 
    [RFC6087]  Bierman, A., "Guidelines for Authors and Reviewers of YANG
               Data Model Documents", RFC 6087, January 2011.
 
    [RFC6242]  Wasserman, M., "Using the NETCONF Protocol over Secure
               Shell (SSH)", RFC 6242, June 2011.
 
 Appendix A.  The Complete Data Tree
@@ -2567,39 +2569,41 @@
     </rt:routing>
    </data>
   </rpc-reply>
 
 Appendix D.  Change Log
 
    RFC Editor: remove this section upon publication as an RFC.
 
 D.1.  Changes Between Versions -07 and -08
 
-   o  Type of "rt:router-id" changed to "yang:dotted-quad".
-
-   o  Fixed missing prefixes in XPath expressions.
+   o  Changed reference from RFC6021 to RFC6021bis.
 
 D.2.  Changes Between Versions -06 and -07
 
    o  The contents of <get-reply> in Appendix C was updated: "eth[01]"
       is used as the value of "location", and "forwarding" is on for
       both interfaces and both IPv4 and IPv6.
 
    o  The "must" expression for "main-routing-table" was modified to
       avoid redundant error messages reporting address family mismatch
       when "name" points to a non-existent routing table.
 
    o  The default behavior for IPv6 RA prefix advertisements was
       clarified.
 
    o  Changed type of "rt:router-id" to "ip:dotted-quad".
 
+   o  Type of "rt:router-id" changed to "yang:dotted-quad".
+
+   o  Fixed missing prefixes in XPath expressions.
+
 D.3.  Changes Between Versions -05 and -06
 
    o  Document title changed: "Configuration" was replaced by
       "Management".
 
    o  New typedefs "routing-table-ref" and "route-filter-ref".
 
    o  Double slashes "//" were removed from XPath expressions and
       replaced with the single "/".