our schemes forgoes ip address entirely and instead uses hostnames as identifiers in packets. The scalability of routing in ensured by encapsulating these packets in highly aggregated routing allocator. We use autonomous system numbers (ANSs) and Here we are going to present data experiment which shows that a much simple and scalable routing future internet by using fewer identifiers for its entities.
20. Way of Forwarding of packets in the core of internet.Locator-identifier split proposals
21.
22. Router 1 forwards the packets by looking up 2000 in its forwarding table and exchanges ASN reachability rather than prefix reachability. Subsequent core routers, routers 2,3 and 4, repeat the forwarding table look-up.Architecture details
27. Packet header here contain source and destination host name and ASN locators
28.
29.
30.
31.
32.
33. Host name to subnet ID and MAC mapping is confined to the destination AS.This separation of mapping infrastructure allows DNS resolvers to perform extensive, a long-term caching for host name to AS mapping which are fairly static. This allows an authoritative name server to load balance a host name across systems.
34.
35. Second, the changes to ARP protocol are straight forward.Intra-domain protocols
36.
37. Since one records is maintained its thwarts statistical and related data attacks to poison the DNS cache.DNS issues
38.
39. And to avoid this multi-homing, in this architecture, an organization can simply rank each of its providers as primary and secondary etc.
41. Thus we can eliminate these unnecessary ASNs .Examining ASN as locators
42.
43. When it examined the impact of this factor on packet forwarding speed. We find that ASNs based packet forwarding makes look-up and update operations faster at the same time requires one third of the memory.
44. Modern software routers use the trie data structure to perform longest prefix matching on IP prefixes.
45. A trie must perform O(log(n)) memory references. Where n=no. of bits in IP address.
46. ASN-based routing yield performance of O(1),since ASNs are fixed length and exactly one match has to be found. Forwarding table look-up performance
47. Performance of ASN-based and IPv4 forwarding. Forwarding approach ASNs IPv4 Number of entries 101,310 288,685 Storage required (MBytes) 2.90 9.73 Lookup times (ns) Average 155 1129 Standard dev. 40 253 Minimum 133 543 Update times (ns) Average 157 4018
50. But here found the maximum of 67 character with a median of 15 character long. If hosts within domain follow a similar pattern then this median goes to 30 character.
51. Further there is a restriction on DNS character set 6 bit required to encode each character resulting in 23 bytes and one bytes to encode the name’s length. Thus total of 24 bytes.Examining host names as identifiers
52.
53. Further if subnet id and MAC are encoded 7 bytes more thus total of 31 bytes
56. A MAC address for transmitting the packet at the last router.
57. In this approach, this step is even less work: the servers would only store one record type, requiring only about 8 bytes(2 byte for subnet ID and 6 for MAC)
59. For 16 bit subnet ID direct array indexing can be used which require 384 kb for 65,536 entries. And for MAC routers must simply copy to link layer.Intra-domain routing scalability
60.
61. Both host names and autonomous system numbers (ASNs) were added later: host names were added to provide users with a mnemonic way of addressing machines and ASNs were added to make BGP loop free.
62. This topic explored a new Internet which breaks away from IP addresses and instead embraces names host as identifiers and ASNs as locators.
63. This design decouples routing from addressing, which IP addresses (inadvertently) entangled.
64. The outcome is a faster, expandable, and more scalable Internet.
65. We outlined the key features of this architecture and justified the choices using actual data sets from the Internet.
66. While there is still more work required to test the feasibility and to make the architecture practical, we hope that this topic will continue the discussion of the future of the Internet in the research community.Conclusion