Usecases

1. Use Cases of I2RS in Mobile Backhaul Network

Publication: IETF Individual Draft

Publication History: 2014-07

Publication URL: https://tools.ietf.org/html/draft-zhang-i2rs-mbh-usecases-00

Description:

In a mobile backhaul network, traditional configuration and diagnoses mechanisms based on device-level management tools and manual processing are ill-suited to meet the requirements of today’s scalable, flexible, and complex network. Thanks to the new innovation of Interface to the Routing System’s (I2RS) programmatic interfaces, as defined in [I-D.ietf-i2rs-architecture], an alternative way is available to control the configuration and diagnose the operational results. This document discusses the use case for I2RS in mobile backhaul network.

2. Use Cases for an Interface to LDP Protocol

Publication: IETF Individual Draft

Publication History: 2013-10

Publication URL: https://tools.ietf.org/html/draft-chen-i2rs-mpls-ldp-usecases-00

Description:

The Label Distribution Protocol (LDP) [RFC5036] is a protocol defined for distributing labels in MPLS domain. Traditionally LDP protocol may be managed via CLI, SNMP or NETCONF. Interface to the Routing System’s (I2RS) Programmatic interfaces, as defined in [I-D.ward-i2rs-framework], provides an alternate way to control the configuration and diagnose the operation of the LDP protocol. This document describes requirement and use cases for which I2RS can be used for LDP protocol.

3. Use Cases for an Interface to MPLS TE

Publication: IETF Individual Draft

Publication History: 2014-07

Publication URL: https://tools.ietf.org/html/draft-huang-i2rs-mpls-te-usecases-02

Description:

Network services based on Virtual Networks (VN) or Virtual Circuits (VC) may be run over MPLS-TE links, and support network configurations such as hub-spoke, service routing, or on-demand networks. An MPLS Traffic Engineering(TE) network is typically configured and the results of its operation analyzed through network management interfaces (CLI, SNMP or NETCONF). These interactions control each of the MPLS TE links, and diagnose operations issues concerning link configuration, MPLS TE protection, and traffic switching-over. The network management functions also monitor MPLS TE links and provide fault detection.

The Interface to the Routing System (I2RS) (draft-ietf-i2rs- architecture) programmatic interface to the routing system provides an alternative way to control the configuration and diagnose the operation of MPLS links. I2RS may be used for the configuration, manipulation, polling, or analyzing MPLS TE. This document describes a set of use cases for which I2RS can be used for MPLS TE. It is intended to provide a base for a solution draft describing I2RS information models and protocol functions that will support virtual networks that utilize MPLS TE.

4. Use Cases for an Interface to IGP Protocol

Publication: IETF Individual Draft

Publication History: 2014-07

Publication URL: https://tools.ietf.org/html/draft-wu-i2rs-igp-usecases-00

Description:

A link-state routing protocol such as OSPF or IS-IS is an essential component for a routing system. With substantial effort on the IGP protocols, the infrastructure of the network has achieved high reliability. During past years they have been operated and maintained through typical CLI, SNMP and NETCONF. As modern networks become larger and more complex, the IGP protocol may require a programmatic interface which is able to facilitate additional control and observation in such networks. Interface to the Routing System’s (I2RS) is a standards-based interface which provides a programmatic way to control and observe the IGP protocol. I2RS can be used to operate, maintain and monitor the routing-related state. This document describes set of use cases for which I2RS can be used for IGP protocol. It is intended to provide a base for the solution draft describing information models and a set of interfaces to the IGP protocol.

SBI

1. I2RS Information Model for MPLS LDP

Publication: IETF Individual Draft

Publication History: 2014-10

Publication URL: https://tools.ietf.org/html/draft-chen-i2rs-mpls-ldp-info-model-00

Description:

The Label Distribution Protocol (LDP) ([RFC5036]) is a protocol defined for distributing labels in MPLS domain. Traditionally LDP protocol may be managed via CLI, SNMP or NETCONF. The Interface to the Routing System’s (I2RS) Programmatic interface (draft-ietf-i2rs- architecture) provides an alternate way to control the configuration and diagnose the operation of the LDP protocol. This document specifies an information model for the LDP protocol to facilitate the definition of a standardized data model, which can be used to define interfaces to the LDP from an entity that may even be external to the routing system. Based on standardized data model and interfaces, use cases of I2RS interface to LDP protocol (draft-chen- i2rs-mpls-ldp-usecases) can be supported.

2. I2RS Information Model for MPLS TE

Publication: IETF Individual Draft

Publication History: 2014-10

Publication URL: https://tools.ietf.org/html/draft-chen-i2rs-mpls-te-info-model-00

Description:

Traditionally MPLS TE networks may be managed via CLI, SNMP or NETCONF. There are two types of TE LSP: static CR-LSP and dynamic TE LSP created by protocol of RSVP-TE. Static CR-LSP is configured with forwarding items such as interface, label and bandwidth, etc. node by node. Dynamic TE LSP is configured with MPLS TE parameters which are used to calculate path and set up TE LSP by protocol. Both configurations are complex. The Interface to the Routing System’s (I2RS) Programmatic interface (draft-ietf-i2rs-architecture) provides an alternate way to control the configuration and diagnose the operation of MPLS TE. These interactions to control MPLS TE links and diagnose their operation include: MPLS TE configuration, MPLS TE protection, traffic switching-over, traffic detection, and fault detection. This document specifies an information model for MPLS TE to facilitate the definition of a standardized data model which can be used to define interfaces to the MPLS TE from an entity that may even be external to the routing system. Based on standardized data model and interfaces, use cases of MPLS TE defined by draft-huang-i2rs- mpls-te-usecases can be supported.

3. Yang Model for MPLS LDP

Publication: IETF Individual Draft

Publication History: 2014-08

Publication URL: https://tools.ietf.org/html/draft-chen-mpls-ldp-yang-cfg-00

Description:

This document defines a YANG data model that can be used to configure and manage MPLS LDP.

4. Yang Model for MPLS Traffic Engineering(TE)

Publication: IETF Individual Draft

Publication History: 2014-08

Publication URL: https://tools.ietf.org/html/draft-chen-mpls-te-yang-cfg-00

Description:

This document defines a YANG data model that can be used to configure and manage MPLS TE.

5. Yang Data Model for BGP/MPLS IP VPNs

Publication: IETF Individual Draft

Publication History: 2014-08

Publication URL: https://tools.ietf.org/html/draft-zhuang-l3vpn-yang-cfg-00

Description:

This document defines a YANG data model that can be used to configure and manage L3VPN (BGP/MPLS IP VPN).

6. Yang Model for L2VPN

Publication: IETF Individual Draft

Publication History: 2014-08

Publication URL: https://tools.ietf.org/html/draft-zhuang-l2vpn-yang-cfg-00

Description:

This document defines a YANG data model that can be used to configure and manage L2VPN. Both VPWS and VPLS are supported.

7. Yang Model for Ethernet VPN

Publication: IETF Individual Draft

Publication History: 2014-08

Publication URL: https://tools.ietf.org/html/draft-zhuang-l2vpn-evpn-yang-cfg-00

Description:

This document defines a YANG data model that can be used to configure and manage Ethernet VPN.

8. Yang Data Model for Tunnel Policy

Publication: IETF Individual Draft

Publication History: 2015-03

Publication URL: https://tools.ietf.org/html/draft-li-rtgwg-tunnel-policy-yang-00

Description:

This document defines a YANG data model that can be used to configure and manage tunnel policy.

9. Yang Data Model for Unified Tunnel

Publication: IETF Individual Draft

Publication History: 2015-12

Publication URL: https://tools.ietf.org/html/draft-li-rtgwg-utunnel-yang-01

Description:

This document defines a YANG data model for the unified tunnel. The data model includes the operational state of tunnels.

10. Yang Data Model for Resource Management

Publication: IETF Individual Draft

Publication History: 2015-12

Publication URL: https://tools.ietf.org/html/draft-chen-rtgwg-resource-management-yang-00

Description:

This document describes a YANG data model for resource management. The resource includes mpls label etc. The data model defines the configuration and operational state for resource management.