886
Quel futur pour les options de routage ?
Kavé salamatian
Once Upon a time ..... in the Beginning....
"In the Beginning, ARPA created the ARPANET.
And the ARPANET was without form and void.
And darkness was upon the deep.
And the spirit of ARPA moved upon the face of the network andARPA said, 'Let there be a protocol,' and there was a protocol.
And ARPA saw that it was good.
And ARPA said, 'Let there be more protocols,' and it was so. And ARPA saw that it was good. And ARPA said, 'Let there be more networks,' and it was so."-- Danny Cohen
IP
TCP
WEB
P2P
SPAM
Social networks
Happy birthday !
Future ???
Various stakeholdershave have differing/conflicting requirementsEnd Users vs. Telecommunications Service Provider vs. RegulatorsProtocol Developers vs. Standardization Bodies vs. Hardware & SoftwareManufacturersApplication Developers vs. network designers Military & Security authorities vs. civil rights
What is wrong with IP?
Addressing goals: Identification = who Location = where Content = what Routing is a function that accepts Id, Loc, Con and generates a path to the goal Routing = find a way to destination Forwarding = send next hop on the way
«An IP address does not identify a specific computer. Instead, each IP Address identifies a connection between a computer and a network.» [Computer Networks, D. Comer]
BGP = Border Gateway Protocol Is a Policy-Based routing protocol Relatively simple protocol, but configuration is complex and the entire world can see, and be impacted by, your mistakes.
BGP filtering and InjectingHot potatoes routing Enforcing policiesCompetition playground Need for governance To avoid the pakistanese «mobilette»To fill the internet divide
What does an Internet Architecture hope to achieve?Interoperability across networks, Easier for applications to code to , Framework for providers to compete
What does an architecture do ?Choose ParadigmPacket/circuit/new(e.g. multihop radio)?Fundamentally is net a “graph”?Are protocols/services “layered”?Choose Functional DecompositionTrade between packet header and node Choose stateless or stateful (e2e v. hbh)Can do NAT, Header Compression and QoS/Flows)Are nodes different (host v. router)?Choose Packet Format(s)
Interoperability:No – not reallyUniform API: Bad thing: hides useful features of the underlying network., eg. cross layer optimisations
Provider framework:Has any tier-1 ISP ever made significant profit from offering IP service? Net Neutrality Debate etc.But ....It used to enable rapid innovationlack of attention to value flow & economics was a good thing!High commercial value blunts innovation (c.f. other industries)Disruption is bad for business
Future Internet architecture should be tailored such that it enables surprising things
Middle age: crisis
A wuideninng wait and a narrowing waist
a narrowing mind, a widening waist
Three anniversaries in 2009 20 years of Web30 years of USENET40 years of ARPANETapproaching middle age
It is hard to see the future .....but maybe we can say what future should not be !and even we would like it to be !
Requirements
Conclusion: No ”one-size-fits-all” solution
What to do? Would heterogeneity reign?Current Internet cannot afford yet another patch !Architecture will need to adapts to future (unknown) needs
What’s happens if the location/person/content changes Mobility, Hadopi, dynamic changes Solutions adopted so far : Patches, and patches over patches, in contradiction with the initial design paradigmsMobile IP, authentification, Google, etc.
Consensus in the research community that a next step beyond the Internet
Intra AS (IGP)OSPF, ISIS, RIPdistance based Intra-AS sets entries for internal destsRouting based on IP address
Inter ASBGPPolicy basedInter-AS & Intra-As sets entries for external dests Routing based on AS number and/or IP address mask
IST ANA project Premises
- Need to separate “mechanics” from “networking logic”Identify “universal” communication abstractionsAn “Axiomatic Basis of Communication”Stack becomes a tool box and framework populated by constantly changing protocol logic and autonomic steering logic (adaptivity, evolvability)
- Functional Block (FB): data processing entityInformation Dispatch Point (IDP): indirection/start-pointsCompartment: "wrappers" for networks and admin domains. + “technology agnostic" communication API