@techreport{cui-softwire-va-based-softwire-00,
    number =    {draft-cui-softwire-va-based-softwire-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-cui-softwire-va-based-softwire/00/},
    author =    {Yong Cui and Peng Wu and Shengling Wang and Mingwei Xu and Jianping Wu and Xing Li and Lixia Zhang and Chris Metz},
    title =     {{VA-Based Softwire}},
    pagetotal = 21,
    year =      2009,
    month =     jul,
    day =       6,
    abstract =  {The increasing deployment of IPv6 networks in both customer networks and ISP networks leads to two common traversing transition scenarios: in the first scenario, an IPv6-only backbone network needs to provide IP connectivity between IPv4 networks, we call it IPv4-over-IPv6 scenario; In the second scenario, IPv6 networks need to be interconnected over an IPv4 transit network, we call it IPv6-over- IPv4 scenario. In both scenarios, the ISP operating the transit network of one address family must offer transit services for attached client networks of the other address family. The Softwire WG has defined softwire mesh mechanism {[}RFC5565{]} for the two traversing scenarios. Softwire mesh uses automatic softwire tunnels employing multi-protocol BGP extensions for distributing E-IP routes, where both BGP peers and tunnels between PEs forms a full-mesh architecture. Inspired by the Virtual Aggregation approach {[}I-D.ietf-grow-va{]} to IPv4 routing scalability, in this draft we proposed a scalable mechanism for distributing E-IP routes over the transit network. Our solution can significantly reduce the forwarding information base (FIB) size at Address Family Border Routers (AFBRs) as well as the total amount of routing updates, and offers the ISP an easy way to manage the transit service.},
}