%% You should probably cite draft-bitar-i2rs-service-chaining-01 instead of this revision.
@techreport{bitar-i2rs-service-chaining-00,
    number =    {draft-bitar-i2rs-service-chaining-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-bitar-i2rs-service-chaining/00/},
    author =    {Dr. Nabil N. Bitar and Giles Heron and Luyuan Fang and Ramki Krishnan and Nicolai Leymann and Himanshu C. Shah and Wassim Haddad},
    title =     {{Interface to the Routing System (I2RS) for Service Chaining: Use Cases and Requirements}},
    pagetotal = 1,
    year =      2013,
    month =     jul,
    day =       15,
    abstract =  {Service chaining is the concept of applying an ordered set of services to a packet or a flow. Services in the chain may include network services such as load-balancing, firewalling, intrusion prevention, and routing among others. Criteria for applying a service chain to a packet or flow can be based on packet/flow attributes that span the OSI layers (e.g., physical port, Ethernet MAC header information, IP header information, Transport and application layer information). This document describes use cases and I2RS (Information to the Rousting System) requirements for the discovery and maintenance of services topology and resources. It also describes use cases and I2RS requirements for controlling the forwarding of a packet/flow along a service chain based on packet/flow attributes.},
}