--- 1/draft-ietf-i2rs-problem-statement-05.txt	2015-01-07 14:14:51.220951996 -0800
+++ 2/draft-ietf-i2rs-problem-statement-06.txt	2015-01-07 14:14:51.244952585 -0800
@@ -1,21 +1,21 @@
 
 Network Working Group                                      A. Atlas, Ed.
 Internet-Draft                                          Juniper Networks
 Intended status: Informational                            T. Nadeau, Ed.
-Expires: July 10, 2015                                           Brocade
+Expires: July 11, 2015                                           Brocade
                                                                  D. Ward
                                                            Cisco Systems
-                                                         January 6, 2015
+                                                         January 7, 2015
 
            Interface to the Routing System Problem Statement
-                  draft-ietf-i2rs-problem-statement-05
+                  draft-ietf-i2rs-problem-statement-06
 
 Abstract
 
    As modern networks grow in scale and complexity, the need for rapid
    and dynamic control increases.  With scale, the need to automate even
    the simplest operations is important, but even more critical is the
    ability to quickly interact with more complex operations such as
    policy-based controls.
 
    In order to enable network applications to have access to and control
@@ -38,21 +38,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 July 10, 2015.
+   This Internet-Draft will expire on July 11, 2015.
 
 Copyright Notice
 
    Copyright (c) 2015 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
@@ -61,35 +61,37 @@
    include Simplified BSD License text as described in Section 4.e of
    the Trust Legal Provisions and are provided without warranty as
    described in the Simplified BSD License.
 
 Table of Contents
 
    1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
    2.  I2RS Model and Problem Area for The IETF  . . . . . . . . . .   3
    3.  Standard Data-Models of Routing State for Installation  . . .   5
    4.  Learning Router Information . . . . . . . . . . . . . . . . .   6
-   5.  Aspects to be Considered for an I2RS Protocol . . . . . . . .   6
+   5.  Aspects to be Considered for an I2RS Protocol . . . . . . . .   7
    6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
    7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
    8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
-   9.  Informative References  . . . . . . . . . . . . . . . . . . .   8
+   9.  Informative References  . . . . . . . . . . . . . . . . . . .   9
    Appendix A.  Existing Management Interfaces . . . . . . . . . . .   9
    Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10
 
 1.  Introduction
 
    As modern networks grow in scale and complexity, the need for rapid,
-   flexible and dynamic control increases.  With scale, the need to
-   automate even the simplest operation is important, but even more
-   critical is the ability for network operators to quickly interact
-   with these operations using mechanisms such as policy-based controls.
+   flexible and dynamic control increases.
+
+   With scale, the need to automate even the simplest operation is
+   important, but even more critical is the ability for network
+   operators to quickly interact with these operations using mechanisms
+   such as policy-based controls.
 
    With complexity comes the need for more sophisticated automated
    network applications and orchestration software that can process
    large quantities of data, run complex algorithms, and adjust the
    routing state as required in order to support the network
    applications, their computations and their policies.  Changes made to
    the routing state of a network by external applications must be
    verifiable by those applications to ensure that the correct state has
    been installed in the correct places.