@techreport{bashandy-bgp-frr-mirror-table-00,
    number =    {draft-bashandy-bgp-frr-mirror-table-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-bashandy-bgp-frr-mirror-table/00/},
    author =    {Ahmed Bashandy and Maciek Konstantynowicz and Nagendra Kumar Nainar},
    title =     {{BGP FRR Protection against Edge Node Failure Using Table Mirroring with Context Labels}},
    pagetotal = 25,
    year =      2012,
    month =     oct,
    day =       8,
    abstract =  {Consider a BGP free core scenario. Suppose the edge BGP speakers PE1, PE2,..., PEn know about a prefix P/m via the external routers CE1, CE2,..., CEm. If the edge router PEi crashes or becomes totally disconnected from the core, it is desirable for a core router "P" carrying traffic to the failed edge router PEi to immediately restore traffic by re-tunneling packets originally tunneled to PEi and destined to the prefix P/m to one of the other edge routers that advertised P/m, say PEj, until BGP re-converges. This draft proposes a BGP FRR scheme that relies on having the repairing edge router mirror the protected edge router forwarding table. The repairing edge router uses a locally allocated context label to identify the correct mirrored table.},
}