Summary of I2RS Use Case Requirements
draft-ietf-i2rs-usecase-reqs-summary-03

Document Type Active Internet-Draft (i2rs WG)
Last updated 2016-11-15
Replaces draft-hares-i2rs-usecase-reqs-summary
Stream IETF
Intended RFC status (None)
Formats plain text pdf xml html bibtex
Stream WG state WG Document Sep 2016
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
i2rs                                                            S. Hares
Internet-Draft                                                    Huawei
Intended status: Informational                                   M. Chen
Expires: May 19, 2017                                Huawei Technologies
                                                       November 15, 2016

                 Summary of I2RS Use Case Requirements
                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

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

Hares & Chen              Expires May 19, 2017                  [Page 1]
Internet-Draft             I2RS Use Cases Req              November 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Protocol Independent Use Case Requirements  . . . . . . . . .   4
   3.  BGP Use Case Requirements . . . . . . . . . . . . . . . . . .   6
   4.  IGP Use Cases . . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  CCNE Use Cases  . . . . . . . . . . . . . . . . . . . . . . .  10
   6.  Topology Related Use Cases  . . . . . . . . . . . . . . . . .  11
     6.1.  Virtual Connection Use Case Requirements  . . . . . . . .  11
     6.2.  Virtual Network Use Case Requirements . . . . . . . . . .  11
     6.3.  Topology Use Case . . . . . . . . . . . . . . . . . . . .  13
     6.4.  Virtual Topology Data Model . . . . . . . . . . . . . . .  17
     6.5.  Virtual Topology IP Data Model  . . . . . . . . . . . . .  19
     6.6.  Virtual Topology Network Element  . . . . . . . . . . . .  19
   7.  Requirements from SFC Use Cases . . . . . . . . . . . . . . .  20
   8.  Requirements from Traffic Steering Use Cases  . . . . . . . .  22
   9.  Requirements from MPLS TE Networks Use Cases  . . . . . . . .  22
   10. Requirements from MPLS LDP Networks Use Cases . . . . . . . .  24
   11. Requirements from Mobile Backhaul Ues Cases . . . . . . . . .  25
   12. Requirements from Large Data Flows are  . . . . . . . . . . .  27
   13. Large Data Collection Systems . . . . . . . . . . . . . . . .  28
   14. CDNI  . . . . . . . . . . . . . . . . . . . . . . . . . . . .  30
   15. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  31
   16. Security Considerations . . . . . . . . . . . . . . . . . . .  31
   17. References  . . . . . . . . . . . . . . . . . . . . . . . . .  31
     17.1.  Normative References . . . . . . . . . . . . . . . . . .  31
     17.2.  Informative References . . . . . . . . . . . . . . . . .  31
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  34

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:

   o  Protocol Independent described in [I-D.white-i2rs-use-case]

   o  BGP described in [I-D.keyupate-i2rs-bgp-usecases]

   o  IGP protocols as described in [draft-ietf-wu-i2rs-igp-usecases]
Show full document text