%% You should probably cite draft-farrel-spring-sr-domain-interconnect-06 instead of this revision.
@techreport{farrel-spring-sr-domain-interconnect-01,
    number =    {draft-farrel-spring-sr-domain-interconnect-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-farrel-spring-sr-domain-interconnect/01/},
    author =    {Adrian Farrel and John Drake},
    title =     {{Interconnection of Segment Routing Domains - Problem Statement and Solution Landscape}},
    pagetotal = 33,
    year =      2017,
    month =     oct,
    day =       29,
    abstract =  {Segment Routing (SR) is now a popular forwarding paradigm for use in MPLS and IPv6 networks. It is typically deployed in discrete domains that may be data centers, access networks, or other networks that are under the control of a single operator and that can easily be upgraded to support this new technology. Traffic originating in one SR domain often terminates in another SR domain, but must transit a backbone network that provides interconnection between those domains. This document describes a mechanism for providing connectivity between SR domains to enable end-to-end or domain-to-domain traffic engineering. The approach described: allows connectivity between SR domains, utilizes traffic engineering mechanisms (RSVP-TE or Segment Routing) across the backbone network, makes heavy use of pre-existing technologies requiring the specifications of very few additional mechanisms. This document some background and a problem statement, explains the solution mechanism, and provides examples. It does not define any new protocol mechanisms.},
}