ASN-FWD: Shrinking the IPv4 Share on the Forwarding Information Base

ASN-FWD: Shrinking the IPv4 Share on the Forwarding Information Base

Marta C. C. Lacerda (UFU)Marcos Siqueira (Unicamp)Paulo R. S. L. Coelho (UFU)

Luis F. Faina (UFU)Lásaro Camargos (UFU)

Christian E. Rotenberg (Unicamp)Rafael Pasquini (UFU)


Agenda

ù Introductionù Design Goalsù Filling the FIBù Preparing IPv4 Packets for ANS-FWD Operationù Experimental Resultsù On the ASN-FWD Deployment Time Windowù Conclusion and Future Work

Introduction


Foward Information Base


BGPRIBFIB

IPv4 PacketDSTIP

SourceDestination

Creates the packet

Longest Prefix Match

IPv4 to IPv6 Transition


Network Layer

IPv4 IPv6

Most of current high capacity routers present FIB

memory capacity up to 1M IPv4 entries

Default

512K IPv4 entries

+256K IPv6 entries

BGP Reports [1]


Last Decade

Main contributing factors

•Mobility

•Multi-homing

•IPv4 Provider Independent

Some Proposals

•HIP [4]

•LISP [5]

•Viaggre [6]

•Smalta [7]


Clean slate and evolutionary proposals.Lack of deployability in either cases

Routing architecture changesNew addressing schemesNew infrastructure devices

Autonomous Systems


AS1

AS3 AS4AS2

AS5

BGP sessions

AS Numbers of 32 bits

ASN-FWD


Autonomous System Number-based ForWarDing

FIBs use 32-bit-long ASN x IP Prefixes

Currently, the ASNs represents +/- 10% of total IPv4 Prefixes

Insertion of Adaptation-Boxes inside AS(carrier grade boxes)

Insertion of 8 bytes per IPv4 packet(optional header)

Design Goals

• No changes in the software of routers• No changes in routing protocols currently used in

Internet• No changes in the protocol stack of end hosts;• Compatible with current CDN• Seamless communication among AS with and

without support to ASN-FWD• Backward compatibility with all IPv4-based

applications


Design Goals

6. No need for a centralized solution;7. No dependence on DNS structure;8. Compatible with current CDNs; 9. Seamless communication among AS with and

without support to ASN-FWD;10.Backward compatibility with all IPv4-based

applications.


ASN-FWD Example Network Scenario


Filling the FIB


Filling the FIB


Use of 11/8 to disseminate ASNs.

Currently, there is no ASN higher than 224.

Preparing IPv4 Packets for ASN-FWD Operation


Experimental Results

• Prototype developed using libipq [15]• Intel Core2 Quad CPU Q9550 2.83GHz with 4GB of

RAM• Intel Core i7-2640M 2.8 GHz with 6GB of RAM• Open SuSE 12.2 with Linux Kernel 3.4.47• VirtualBox 4.2.12

• Considered TCP and UDP transmissions• wget• netcat


Experimental Results• Base box

• libapq + Linux• VirtualBox

• Client• wget (TCP) + netcat (UDP)

• ASN-FWD packets sent through the public Internet• Federal University of Uberlândia (RNP Backbone)

• ASN – 200.19.151.21• IPs – 200.19.151.32/30

• CPQD - Brazilian operator• ASN/IP – 189.15.69.57 (used a single IP)




End-to-end path of the experiments collected with traceroute.



TCP log using wget – From the operator network to the university.



TCP log using wget – From the university to the operator network.



UDP log using netcat – From the operator network to the university.



UDP log using netcat – From the university to the operator network.



On the ASN-FWD Deployment Time Window


Conclusions and Future Work

• Shrinks the IPv4 share on FIB

• Offers backward compatibility to legacy applications

• Minimally invasive

• Transparently developed on top of standardized mechanisms• Optional IP headers• BGP messages• FIB generation functions• Packets’ forwarding mechanisms


Conclusions and Future Work

• Requires IP-to-ASN mapping• Developed by using information currently available in

BGP

• Can also be adopted for IPv6 traffic forwarding

• SDN investigations• OpenFlow match + encap/re-write actions• Host-based approaches in data center scenarios


Questions


Lásaro J. [email protected]

Rafael [email protected]

Engineering

ASN-FWD: Shrinking the IPv4 Share on the Forwarding Information Base