draft-ietf-i2rs-usecase-reqs-summary-02.txt | draft-ietf-i2rs-usecase-reqs-summary-03.txt | |||
---|---|---|---|---|
i2rs S. Hares | i2rs S. Hares | |||
Internet-Draft Huawei | Internet-Draft Huawei | |||
Intended status: Informational M. Chen | Intended status: Informational M. Chen | |||
Expires: September 16, 2016 Huawei Technologies | Expires: May 19, 2017 Huawei Technologies | |||
March 15, 2016 | November 15, 2016 | |||
Summary of I2RS Use Case Requirements | Summary of I2RS Use Case Requirements | |||
draft-ietf-i2rs-usecase-reqs-summary-02 | draft-ietf-i2rs-usecase-reqs-summary-03 | |||
Abstract | Abstract | |||
The I2RS Working Group (WG) has described a set of use cases that the | The I2RS Working Group (WG) has described a set of use cases that the | |||
I2RS systems could fulfil. This document summarizes these use cases. | I2RS systems could fulfil. This document summarizes these use cases. | |||
It is designed to provide requirements that will aid the design of | It is designed to provide requirements that will aid the design of | |||
the I2RS architecture, Information Models, Data Models, Security, and | the I2RS architecture, Information Models, Data Models, Security, and | |||
protocols. | protocols. | |||
Status of This Memo | Status of This Memo | |||
skipping to change at page 1, line 35 ¶ | skipping to change at page 1, line 35 ¶ | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | 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 Notice | |||
Copyright (c) 2016 IETF Trust and the persons identified as the | Copyright (c) 2016 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
skipping to change at page 28, line 35 ¶ | skipping to change at page 28, line 35 ¶ | |||
or ECMP group and readjusting the weights of the other members | or ECMP group and readjusting the weights of the other members | |||
to account for the large flow | to account for the large flow | |||
* In the case of DDoS mitigation, the action involves rate | * In the case of DDoS mitigation, the action involves rate | |||
limiting, remarking or potentially discarding the large flow in | limiting, remarking or potentially discarding the large flow in | |||
question. | question. | |||
13. Large Data Collection Systems | 13. Large Data Collection Systems | |||
The requirements from the Large Data Collection Systems Use cases | 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 | L-Data-REQ-01 (OC): I2rs must be able to collect large data set | |||
from the network with high frequency and resolution with minimal | from the network with high frequency and resolution with minimal | |||
impact to the device's CPU and memory. | impact to the device's CPU and memory. | |||
L-Data-REQ-02 (IC): I2RS must be able to use a database model | 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 | 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 | the I2RS exchange as the data plus the structure of the data. The | |||
I2RS management system consumes and understand the data only after | I2RS management system consumes and understand the data only after | |||
it consumes and understand the database model or has been trained | it consumes and understand the database model or has been trained | |||
skipping to change at page 32, line 29 ¶ | skipping to change at page 32, line 29 ¶ | |||
case-vn-vc-03 (work in progress), July 2014. | case-vn-vc-03 (work in progress), July 2014. | |||
[I-D.huang-i2rs-mpls-te-usecases] | [I-D.huang-i2rs-mpls-te-usecases] | |||
Huang, T., Li, Z., and S. Hares, "Use Cases for an | Huang, T., Li, Z., and S. Hares, "Use Cases for an | |||
Interface to MPLS TE", draft-huang-i2rs-mpls-te- | Interface to MPLS TE", draft-huang-i2rs-mpls-te- | |||
usecases-02 (work in progress), July 2014. | usecases-02 (work in progress), July 2014. | |||
[I-D.ietf-i2rs-architecture] | [I-D.ietf-i2rs-architecture] | |||
Atlas, A., Halpern, J., Hares, S., Ward, D., and T. | Atlas, A., Halpern, J., Hares, S., Ward, D., and T. | |||
Nadeau, "An Architecture for the Interface to the Routing | Nadeau, "An Architecture for the Interface to the Routing | |||
System", draft-ietf-i2rs-architecture-13 (work in | System", draft-ietf-i2rs-architecture-15 (work in | |||
progress), February 2016. | progress), April 2016. | |||
[I-D.ietf-i2rs-problem-statement] | [I-D.ietf-i2rs-problem-statement] | |||
Atlas, A., Nadeau, T., and D. Ward, "Interface to the | Atlas, A., Nadeau, T., and D. Ward, "Interface to the | |||
Routing System Problem Statement", draft-ietf-i2rs- | 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] | [I-D.ietf-i2rs-rib-info-model] | |||
Bahadur, N., Kini, S., and J. Medved, "Routing Information | Bahadur, N., Kini, S., and J. Medved, "Routing Information | |||
Base Info Model", draft-ietf-i2rs-rib-info-model-08 (work | Base Info Model", draft-ietf-i2rs-rib-info-model-09 (work | |||
in progress), October 2015. | in progress), July 2016. | |||
[I-D.ietf-sfc-problem-statement] | [I-D.ietf-sfc-problem-statement] | |||
Quinn, P. and T. Nadeau, "Service Function Chaining | Quinn, P. and T. Nadeau, "Service Function Chaining | |||
Problem Statement", draft-ietf-sfc-problem-statement-13 | Problem Statement", draft-ietf-sfc-problem-statement-13 | |||
(work in progress), February 2015. | (work in progress), February 2015. | |||
[I-D.ji-i2rs-usecases-ccne-service] | [I-D.ji-i2rs-usecases-ccne-service] | |||
Ji, X., Zhuang, S., Huang, T., and S. Hares, "I2RS Use | Ji, X., Zhuang, S., Huang, T., and S. Hares, "I2RS Use | |||
Cases for Control of Forwarding Path by Central Control | Cases for Control of Forwarding Path by Central Control | |||
Network Element (CCNE)", draft-ji-i2rs-usecases-ccne- | Network Element (CCNE)", draft-ji-i2rs-usecases-ccne- | |||
End of changes. 7 change blocks. | ||||
10 lines changed or deleted | 11 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |