--- 1/draft-ietf-i2rs-usecase-reqs-summary-02.txt	2016-11-15 12:13:16.665255342 -0800
+++ 2/draft-ietf-i2rs-usecase-reqs-summary-03.txt	2016-11-15 12:13:16.733257010 -0800
@@ -1,19 +1,19 @@
 
 i2rs                                                            S. Hares
 Internet-Draft                                                    Huawei
 Intended status: Informational                                   M. Chen
-Expires: September 16, 2016                          Huawei Technologies
-                                                          March 15, 2016
+Expires: May 19, 2017                                Huawei Technologies
+                                                       November 15, 2016
 
                  Summary of I2RS Use Case Requirements
-                draft-ietf-i2rs-usecase-reqs-summary-02
+                draft-ietf-i2rs-usecase-reqs-summary-03
 
 Abstract
 
    The I2RS Working Group (WG) has described a set of use cases that the
    I2RS systems could fulfil.  This document summarizes these use cases.
    It is designed to provide requirements that will aid the design of
    the I2RS architecture, Information Models, Data Models, Security, and
    protocols.
 
 Status of This Memo
@@ -24,21 +24,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 September 16, 2016.
+   This Internet-Draft will expire on May 19, 2017.
 
 Copyright Notice
 
    Copyright (c) 2016 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
@@ -1306,21 +1306,22 @@
          or ECMP group and readjusting the weights of the other members
          to account for the large flow
 
       *  In the case of DDoS mitigation, the action involves rate
          limiting, remarking or potentially discarding the large flow in
          question.
 
 13.  Large Data Collection Systems
 
    The requirements from the Large Data Collection Systems Use cases
-   described in [draft-swhyte-i2rs-data-collection-system] are (OC):
+   described in [draft-swhyte-i2rs-data-collection-system] are (OC) and
+   (IC):
 
       L-Data-REQ-01 (OC): I2rs must be able to collect large data set
       from the network with high frequency and resolution with minimal
       impact to the device's CPU and memory.
 
       L-Data-REQ-02 (IC): I2RS must be able to use a database model
       where the data on the network node must be able to be described in
       the I2RS exchange as the data plus the structure of the data.  The
       I2RS management system consumes and understand the data only after
       it consumes and understand the database model or has been trained
@@ -1487,32 +1488,32 @@
               case-vn-vc-03 (work in progress), July 2014.
 
    [I-D.huang-i2rs-mpls-te-usecases]
               Huang, T., Li, Z., and S. Hares, "Use Cases for an
               Interface to MPLS TE", draft-huang-i2rs-mpls-te-
               usecases-02 (work in progress), July 2014.
 
    [I-D.ietf-i2rs-architecture]
               Atlas, A., Halpern, J., Hares, S., Ward, D., and T.
               Nadeau, "An Architecture for the Interface to the Routing
-              System", draft-ietf-i2rs-architecture-13 (work in
-              progress), February 2016.
+              System", draft-ietf-i2rs-architecture-15 (work in
+              progress), April 2016.
 
    [I-D.ietf-i2rs-problem-statement]
               Atlas, A., Nadeau, T., and D. Ward, "Interface to the
               Routing System Problem Statement", draft-ietf-i2rs-
-              problem-statement-10 (work in progress), February 2016.
+              problem-statement-11 (work in progress), May 2016.
 
    [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-08 (work
-              in progress), October 2015.
+              Base Info Model", draft-ietf-i2rs-rib-info-model-09 (work
+              in progress), July 2016.
 
    [I-D.ietf-sfc-problem-statement]
               Quinn, P. and T. Nadeau, "Service Function Chaining
               Problem Statement", draft-ietf-sfc-problem-statement-13
               (work in progress), February 2015.
 
    [I-D.ji-i2rs-usecases-ccne-service]
               Ji, X., Zhuang, S., Huang, T., and S. Hares, "I2RS Use
               Cases for Control of Forwarding Path by Central Control
               Network Element (CCNE)", draft-ji-i2rs-usecases-ccne-