--- 1/draft-ietf-i2rs-rib-data-model-13.txt	2018-05-06 20:13:36.217982011 -0700
+++ 2/draft-ietf-i2rs-rib-data-model-14.txt	2018-05-06 20:13:36.325984603 -0700
@@ -7,21 +7,21 @@
                                                                 Ericsson
                                                       H. Ananthakrishnan
                                                            Packet Design
                                                                  S. Kini
                                                               Individual
                                                               N. Bahadur
                                                        Bracket Computing
                                                              May 7, 2018
 
           A YANG Data Model for Routing Information Base (RIB)
-                   draft-ietf-i2rs-rib-data-model-13
+                   draft-ietf-i2rs-rib-data-model-14
 
 Abstract
 
    This document defines a YANG data model for the Routing Information
    Base (RIB) that aligns with the I2RS RIB information model.
 
 Requirements Language
 
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
@@ -3123,20 +3123,25 @@
 7.  Acknowledgements
 
    The authors would like to thank Chris Bowers, John Scudder, Tom
    Petch, Mike McBride and Ebben Aries for his review, suggestion and
    comments to this document.
 
 8.  References
 
 8.1.  Normative References
 
+   [I-D.ietf-i2rs-rib-info-model]
+              Bahadur, N., Kini, S., and J. Medved, "Routing Information
+              Base Info Model", draft-ietf-i2rs-rib-info-model-16 (work
+              in progress), May 2018.
+
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119,
               DOI 10.17487/RFC2119, March 1997,
               <https://www.rfc-editor.org/info/rfc2119>.
 
    [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
               DOI 10.17487/RFC3688, January 2004,
               <https://www.rfc-editor.org/info/rfc3688>.
 
    [RFC5246]  Dierks, T. and E. Rescorla, "The Transport Layer Security
@@ -3169,25 +3174,20 @@
               Access Control Model", STD 91, RFC 8341,
               DOI 10.17487/RFC8341, March 2018,
               <https://www.rfc-editor.org/info/rfc8341>.
 
    [RFC8344]  Bjorklund, M., "A YANG Data Model for IP Management",
               RFC 8344, DOI 10.17487/RFC8344, March 2018,
               <https://www.rfc-editor.org/info/rfc8344>.
 
 8.2.  Informative References
 
-   [I-D.ietf-i2rs-rib-info-model]
-              Bahadur, N., Kini, S., and J. Medved, "Routing Information
-              Base Info Model", draft-ietf-i2rs-rib-info-model-16 (work
-              in progress), May 2018.
-
    [I-D.ietf-i2rs-usecase-reqs-summary]
               Hares, S. and M. Chen, "Summary of I2RS Use Case
               Requirements", draft-ietf-i2rs-usecase-reqs-summary-03
               (work in progress), November 2016.
 
    [RFC2784]  Farinacci, D., Li, T., Hanks, S., Meyer, D., and P.
               Traina, "Generic Routing Encapsulation (GRE)", RFC 2784,
               DOI 10.17487/RFC2784, March 2000,
               <https://www.rfc-editor.org/info/rfc2784>.