i2rs S. Hares
Internet-Draft Huawei
Intended status: Informational M. Chen
Expires: September 16, 2016 Huawei Technologies
March 15, 2016

Summary of I2RS Use Case Requirements


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

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

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.

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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must 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

The Architecture for the Interface to the Routing System [I-D.ietf-i2rs-architecture] allows for a mechanism where the distributed control plane can be augmented by an outside control plane through an open, accessible interface. This document summarizes the use case requirements for theI2RS client-I2RS Agent exchange found in the following documents:

Each group of use cases is presented in its own document. Each use case is labeled with an identifier TTT-REQ-nn where TTT represents the type of use case. The abbreviations for TTT are:

Each use case is also augmented with a notation signifying whether it is in or out of scope with regard to the current I2RS charter:

In some cases a specific draft may be out of charter, but (sub)components of it's requirement set may be in charter. In charter. As such, (IC|OC|NA) designations may appear at the draft level, at the requirement level, or at the sub requirement level. In instances where designations do not appear at more specific level, the designation at the parent level should be considered to be inherited.

2. Protocol Independent Use Case Requirements

This is a summary of the I2RS requirements found in the Protocol Independent Use Cases described in: [I-D.white-i2rs-use-case] (IC):

3. BGP Use Case Requirements

This is a summary of the requirements listed in [I-D.keyupate-i2rs-bgp-usecases] are (IC):

4. IGP Use Cases

This is a summary of the requirements listed in (ietf-draft-wu-ir2s-igp-usecases-00.txt) (OC):

5. CCNE Use Cases

The use cases in I2RS Use Cases for Control of the Forwarding Path by a Central Control Network Element (CCNE) [I-D.ji-i2rs-usecases-ccne-service] indicate the following requirements for I2RS (OC):

6. Topology Related Use Cases

This section describes Topology or Virtual Topology related requirements the I2RS interface (protocol and information model (IM) included in the following types of use cases:

6.1. Virtual Connection Use Case Requirements

6.2. Virtual Network Use Case Requirements

The requirements for the Virtual Networks on Demand (VCoD) are:

6.3. Topology Use Case

                            +----------------+ |
                            |  Applications  |-+
                                    ^   Websockets, ReST, XMPP...
           |                        |                         |
     +------------+     +------------------------+     +-------------+
     |   Policy   |<----|    Topology Manager    |---->|Orchestration|
     |   Manager  |     | +--------------------+ |     |   Manager   |
     +------------+     | |Topology Information| |     +-------------+
                        | |       Model        | |
                        | +--------------------+ |
                                  ^ ^ ^
       Websockets, ReST, XMPP     # | *  Websockets, ReST, XMPP
            ####################### | ************************
            #                       |                        *
     +------------+                 |                  +------------+
     | Statistics |                 |                  | Inventory  |
     | Collection |                 |                  | Collection |
     +------------+                 |                  +------------+
           ^                        | I2RS, NETCONF, SNMP,   ^
           |                        | TL1 ...                |
           |                        |                        |
   +---------------+        +---------------+        +---------------+
   |Network Element|        |Network Element|        |Network Element|
   | +-----------+ |        | +-----------+ |        | +-----------+ |
   | |Information| |<-LLDP->| |Information| |<-LMP-->| |Information| |
   | |   Model   | |        | |   Model   | |        | |   Model   | |
   | +-----------+ |        | +-----------+ |        | +-----------+ |
   +---------------+        +---------------+        +---------------+

The requirements in [I-D.amante-i2rs-topology-use-cases] topology use cases focus around the architecture of topology manager, orchestration manager, and policy in the figure below (IC):

6.4. Virtual Topology Data Model

The [I-D.medved-i2rs-topology-requirements] specifies the following Topology Data Model requirements (IC):

6.5. Virtual Topology IP Data Model

The [I-D.medved-i2rs-topology-requirements] specifies the following requirements for the Virtual Topology IP Data Model's IP/MPLS links and topologies (IC):

6.6. Virtual Topology Network Element

The [I-D.medved-i2rs-topology-requirements] specifies the following requirements (IC):

7. Requirements from SFC Use Cases

The SFC use case document in [I-D.bitar-i2rs-service-chaining] suggests that the following requirements (OC):

SFC-Use-REQ01 (IC):Address

has the following address requirements:

SFC-Use-REQ02 (IC):Supported Service Types

SHOULD include: NAT, IP Firewall, Load balancer, DPI, and others
SFC-Use-REQ03 (IC):Virtual contexts

SHOULD include:
SFC-Use-REQ04 (IC): Customers currently on node

SFC-Use-REQ05 (IC): Customer Support Table (per customer ID)
SFC-Use-REQ06 (OC): Service Resource table

which includes:
SFC-Use-REQ07 (IC): Virtual Network Topology (VNT)

which includes:

8. Requirements from Traffic Steering Use Cases

The requirements from the Traffic Steering use case described in [I-D.chen-i2rs-ts-use-case] are (OC):

9. Requirements from MPLS TE Networks Use Cases

Theses are the requirements from the Traffic Steering use case described in [I-D.huang-i2rs-mpls-te-usecases] (OC):

10. Requirements from MPLS LDP Networks Use Cases

These are the I2RS requirements for the MPLS LDP use case described in [I-D.chen-i2rs-mpls-ldp-usecases]:

11. Requirements from Mobile Backhaul Ues Cases

Mobile BackHaul Use cases described in [draft-ietf-zhang-mbb-usecases-01] are:

12. Requirements from Large Data Flows are

Each of these requirements has been given an an ID number of L-Flow-nn for ease of reference.

The requirements from the Large Data Flows use case described in [I-D.krishnan-i2rs-large-flow-use-case] are (IC):

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):

14. CDNI

The requirements from the Content Delivery Network Interaction described in [I-D.shin-i2rs-usecases-cdni-request-routing] are (OC):

15. IANA Considerations

This document makes no request of IANA.

16. Security Considerations

Routing information is very critical and sensitive information for the operators. I2RS should provide strong security mechanism to protect the routing information that it could not be accessed by the un-authorised users. It should also protect the security and integrity protection of the routing data.

17. References

17.1. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.
[RFC3746] Yang, L., Dantu, R., Anderson, T. and R. Gopal, "Forwarding and Control Element Separation (ForCES) Framework", RFC 3746, DOI 10.17487/RFC3746, April 2004.

17.2. Informative References

[I-D.amante-i2rs-topology-use-cases] Medved, J., Previdi, S., Lopez, V. and S. Amante, "Topology API Use Cases", Internet-Draft draft-amante-i2rs-topology-use-cases-01, October 2013.
[I-D.bitar-i2rs-service-chaining] Bitar, N., Heron, G., Fang, L., ramki, r., Leymann, N., Shah, H. and W. Haddad, "Interface to the Routing System (I2RS) for Service Chaining: Use Cases and Requirements", Internet-Draft draft-bitar-i2rs-service-chaining-01, February 2014.
[I-D.chen-i2rs-mpls-ldp-usecases] Chen, X. and Z. Li, "Use Cases for an Interface to LDP Protocol", Internet-Draft draft-chen-i2rs-mpls-ldp-usecases-00, October 2013.
[I-D.chen-i2rs-ts-use-case] Chen, M. and S. Hares, "I2RS Traffic Steering Use Case", Internet-Draft draft-chen-i2rs-ts-use-case-01, July 2014.
[I-D.hares-i2rs-use-case-vn-vc] Hares, S. and M. Chen, "Use Cases for Virtual Connections on Demand (VCoD) and Virtual Network on Demand (VNoD) using Interface to Routing System", Internet-Draft draft-hares-i2rs-use-case-vn-vc-03, July 2014.
[I-D.huang-i2rs-mpls-te-usecases] Huang, T., Li, Z. and S. Hares, "Use Cases for an Interface to MPLS TE", Internet-Draft draft-huang-i2rs-mpls-te-usecases-02, 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", Internet-Draft draft-ietf-i2rs-architecture-13, February 2016.
[I-D.ietf-i2rs-problem-statement] Atlas, A., Nadeau, T. and D. Ward, "Interface to the Routing System Problem Statement", Internet-Draft draft-ietf-i2rs-problem-statement-10, February 2016.
[I-D.ietf-i2rs-rib-info-model] Bahadur, N., Kini, S. and J. Medved, "Routing Information Base Info Model", Internet-Draft draft-ietf-i2rs-rib-info-model-08, October 2015.
[I-D.ietf-sfc-problem-statement] Quinn, P. and T. Nadeau, "Service Function Chaining Problem Statement", Internet-Draft draft-ietf-sfc-problem-statement-13, 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)", Internet-Draft draft-ji-i2rs-usecases-ccne-service-02, July 2014.
[I-D.keyupate-i2rs-bgp-usecases] Patel, K., Fernando, R., Gredler, H., Amante, S., White, R. and S. Hares, "Use Cases for an Interface to BGP Protocol", Internet-Draft draft-keyupate-i2rs-bgp-usecases-04, July 2014.
[I-D.krishnan-i2rs-large-flow-use-case] ramki, r., Ghanwani, A., Kini, S., McDysan, D. and D. Lopez, "Large Flow Use Cases for I2RS PBR and QoS", Internet-Draft draft-krishnan-i2rs-large-flow-use-case-04, April 2014.
[I-D.lapukhov-bgp-routing-large-dc] Lapukhov, P., Premji, A. and J. Mitchell, "Use of BGP for routing in large-scale data centers", Internet-Draft draft-lapukhov-bgp-routing-large-dc-06, August 2013.
[I-D.medved-i2rs-topology-requirements] Medved, J., Previdi, S., Gredler, H., Nadeau, T. and S. Amante, "Topology API Requirements", Internet-Draft draft-medved-i2rs-topology-requirements-00, February 2013.
[I-D.shin-i2rs-usecases-cdni-request-routing] Shin, M. and S. Lee, "CDNI Request Routing with I2RS", Internet-Draft draft-shin-i2rs-usecases-cdni-request-routing-00, July 2014.
[I-D.swhyte-i2rs-data-collection-system] Whyte, S., Hines, M. and W. Kumari, "Bulk Network Data Collection System", Internet-Draft draft-swhyte-i2rs-data-collection-system-00, October 2013.
[I-D.white-i2rs-use-case] White, R., Hares, S. and A. Retana, "Protocol Independent Use Cases for an Interface to the Routing System", Internet-Draft draft-white-i2rs-use-case-06, July 2014.
[I-D.zhang-i2rs-mbb-usecases] Zhang, L., Li, Z., Liu, D. and S. Hares, "Use Cases of I2RS in Mobile Backhaul Network", Internet-Draft draft-zhang-i2rs-mbb-usecases-01, February 2014.
[RFC4655] Farrel, A., Vasseur, J. and J. Ash, "A Path Computation Element (PCE)-Based Architecture", RFC 4655, DOI 10.17487/RFC4655, August 2006.
[RFC5212] Shiomoto, K., Papadimitriou, D., Le Roux, JL., Vigoureux, M. and D. Brungard, "Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN)", RFC 5212, DOI 10.17487/RFC5212, July 2008.
[RFC5286] Atlas, A. and A. Zinin, "Basic Specification for IP Fast Reroute: Loop-Free Alternates", RFC 5286, DOI 10.17487/RFC5286, September 2008.
[RFC5623] Oki, E., Takeda, T., Le Roux, JL. and A. Farrel, "Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering", RFC 5623, DOI 10.17487/RFC5623, September 2009.
[RFC5693] Seedorf, J. and E. Burger, "Application-Layer Traffic Optimization (ALTO) Problem Statement", RFC 5693, DOI 10.17487/RFC5693, October 2009.

Authors' Addresses

Susan Hares Huawei EMail: shares@ndzh.com
Mach Chen Huawei Technologies Huawei Bld., No.156 Beiqing Rd. Beijing, 100095 China EMail: mach.chen@huawei.com