%% You should probably cite draft-ietf-bess-datacenter-gateway instead of this I-D.
@techreport{drake-bess-datacenter-gateway-02,
    number =    {draft-drake-bess-datacenter-gateway-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-drake-bess-datacenter-gateway/02/},
    author =    {John Drake and Adrian Farrel and Eric C. Rosen and Keyur Patel and Luay Jalil},
    title =     {{Gateway Auto-Discovery and Route Advertisement for Segment Routing Enabled Data Center Interconnection}},
    pagetotal = 9,
    year =      2016,
    month =     oct,
    day =       16,
    abstract =  {Data centers have become critical components of the infrastructure used by network operators to provide services to their customers. Data centers are attached to the Internet or a backbone network by gateway routers. One data center typically has more than one gateway for commercial, load balancing, and resiliency reasons. Segment routing is a popular protocol mechanism for operating within a data center, but also for steering traffic that flows between two data center sites. In order that one data center site may load balance the traffic it sends to another data center site it needs to know the complete set of gateway routers at the remote data center, the points of connection from those gateways to the backbone network, and the connectivity across the backbone network. This document defines a mechanism using the BGP Tunnel Encapsulation attribute to allow each gateway router to advertise the routes to the prefixes in the data center site to which it provides access, and also to advertise on behalf of each other gateway to the same data center site.},
}