%% You should probably cite draft-ietf-idr-rtc-hierarchical-rr-04 instead of this revision.
@techreport{ietf-idr-rtc-hierarchical-rr-03,
    number =    {draft-ietf-idr-rtc-hierarchical-rr-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-idr-rtc-hierarchical-rr/03/},
    author =    {Jie Dong and Mach Chen and Robert Raszuk},
    title =     {{Extensions to RT-Constrain in Hierarchical Route Reflection Scenarios}},
    pagetotal = 6,
    year =      2017,
    month =     jul,
    day =       3,
    abstract =  {The Route Target (RT) Constrain mechanism specified in RFC 4684 is used to build a route distribution graph in order to restrict the propagation of Virtual Private Network (VPN) routes. In network scenarios where hierarchical route reflection (RR) is used, the existing RT-Constrain mechanism cannot guarantee a correct route distribution graph. This document describes the problem scenario and proposes a solution to address the RT-Constrain issue in hierarchical RR scenarios.},
}