draft-ietf-i2rs-usecase-reqs-summary-00.txt   draft-ietf-i2rs-usecase-reqs-summary-01.txt 
i2rs S. Hares i2rs S. Hares
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Informational M. Chen Intended status: Informational M. Chen
Expires: April 30, 2015 Huawei Technologies Expires: November 20, 2015 Huawei Technologies
October 27, 2014 May 19, 2015
Summary of I2RS Use Case Requirements Summary of I2RS Use Case Requirements
draft-ietf-i2rs-usecase-reqs-summary-00 draft-ietf-i2rs-usecase-reqs-summary-01
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 April 30, 2015. This Internet-Draft will expire on November 20, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 13, line 5 skipping to change at page 13, line 5
Models must be able to support Carriers using these MPLS Models must be able to support Carriers using these MPLS
technologies to support networks for Mobile BackHaul, on-demand technologies to support networks for Mobile BackHaul, on-demand
MPLS overlays, and on-demand video conferencing networkings. MPLS overlays, and on-demand video conferencing networkings.
6.3. Topology Use Case 6.3. Topology Use Case
The requirements in [I-D.amante-i2rs-topology-use-cases] topology use The requirements in [I-D.amante-i2rs-topology-use-cases] topology use
cases focus around the architecture of topology manager, cases focus around the architecture of topology manager,
orchestration manager, and policy in the figure below (IC): orchestration manager, and policy in the figure below (IC):
+---------------+ +---------------+
+----------------+ | +----------------+ |
| Applications |-+ | Applications |-+
+----------------+ +----------------+
^ Websockets, ReST, XMPP... ^ Websockets, ReST, XMPP...
+------------------------+-------------------------+ +------------------------+-------------------------+
| | | | | |
+------------+ +------------------------+ +-------------+ +------------+ +------------------------+ +-------------+
| Policy |<----| Topology Manager |---->|Orchestration| | Policy |<----| Topology Manager |---->|Orchestration|
| Manager | | +--------------------+ | | Manager | | Manager | | +--------------------+ | | Manager |
+------------+ | |Topology Information| | +-------------+ +------------+ | |Topology Information| | +-------------+
skipping to change at page 32, line 19 skipping to change at page 32, line 19
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-05 (work in System", draft-ietf-i2rs-architecture-09 (work in
progress), July 2014. progress), March 2015.
[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-04 (work in progress), June 2014. problem-statement-06 (work in progress), January 2015.
[I-D.ietf-i2rs-rib-info-model] [I-D.ietf-i2rs-rib-info-model]
Bahadur, N., Folkes, R., Kini, S., and J. Medved, "Routing Bahadur, N., Folkes, R., Kini, S., and J. Medved, "Routing
Information Base Info Model", draft-ietf-i2rs-rib-info- Information Base Info Model", draft-ietf-i2rs-rib-info-
model-03 (work in progress), May 2014. model-06 (work in progress), March 2015.
[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-10 Problem Statement", draft-ietf-sfc-problem-statement-13
(work in progress), August 2014. (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-
service-02 (work in progress), July 2014. service-02 (work in progress), July 2014.
[I-D.keyupate-i2rs-bgp-usecases] [I-D.keyupate-i2rs-bgp-usecases]
Patel, K., Fernando, R., Gredler, H., Amante, S., White, Patel, K., Fernando, R., Gredler, H., Amante, S., White,
R., and S. Hares, "Use Cases for an Interface to BGP R., and S. Hares, "Use Cases for an Interface to BGP
 End of changes. 9 change blocks. 
12 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/