Named Data Networking

  • View

  • Download

Embed Size (px)


Multimedia & Mobile Communications Lab. Taejoong Chung 2010-03-21 Named Data Networking. Contents. Introduction Vision Architecture Principle & Operation Architecture Details Name Security Routing and Forwarding Caching, PIT Transport Conclusion. - PowerPoint PPT Presentation

Text of Named Data Networking


Named Data NetworkingMultimedia & Mobile Communications Lab.Taejoong Chung & OperationArchitecture DetailsNameSecurityRouting and ForwardingCaching, PITTransportConclusionMMLAB3/18The Advent of NetworkNetworking was invented for sharing resources not for dataA user connects to server to use resources in machinesThe fundamental communication model is point-to-point (host-to-host) conversationBasically Who/Where Model

MMLABA user connect to server to uses resources in machine

3Evolution of NetworkHowever, overwhelming use of todays network is for a machine to acquire chunk (data)Acquire named chunks of data is not a conversationIts dissemination

Most of us need WHAT data are, dont care WHERE it comes fromMiddleware does it for us, the location of data is stored4/18MMLABNeed for New NetworkData communication today is about moving contentInternet was moving dozens of exabytes/month.IP datagram can only name communication endpoints Current network-architecture is not appropriate for current usagePropose an new internet architecture by removing this restriction: NDN5/18MMLABArchitecture PrincipleHourglass architecturethin waist has been a key enabler for internets explosive growthSecurity is built into the architectureBy signing all named datacf) current network supports secure containerTraffic must be self-regulatedFlow-control is moved into networkRouting and forwarding plane separationSimilar to current one


MMLABNDN ArchitectureComponentMessages InterestDataFIB (Forwarding Information Base)Similar to routing tablePIT (Pending Interest Table)Store interests for dataContent StoreSpace for cached data7/18MMLAB

NDN Basic Operation8/18Interest

8NDN SupportsAutomatically support various functionality without extra infrastructureContent DistributionMany users requesting the same data at different timeMulticastMany users requesting the same data at same timeMobilityUser request data at different locationDelay-Tolerant NetworkingData is cached close to user

9/18MMLABArchitecture 1) NameNames are opaque network Router doesnt know the meaning of the nameAllows each application to choose the name scheme that fits its needHierarchically structured nameDo not need to be globally uniqueTo retrieve dynamically generated data, it needsDeterministic algorithm between consumer and producerPartial name supportsmmlab/profile/tjchung -> mmlab/profile/tjchung/v0/1

10/18MMLABArchitecture 2) SecurityFunction of HOW rather than WHERESecurity is can not opt-out but mandatoryEvery data carries a signatureData publisher information enables provenanceCurrent internet security cares about container (e.g. IPSEC)


MMLABArchitecture3) Routing and ForwardingRoutes and forward packets on name, which eliminates1) Address space exhaustionUnbound namespaces2) NAT traversalHost doesnt expose its address3) MobilityNo longer breaks communication since data name remain same4) Scalable address managementAddress assignment & management is no longer required in local network12/18MMLAB12Architecture3) Routing and Forwarding (contd.)Routing can operates in same way as beforeInstead of IP prefix, using Named prefixLongest prefix matchBenefitsNo open-loop problemRandom number added method for interest, reverse path for dataEnable to send interest to multiple interface without worriesLoad balancingSecuritySigning all data prevents them from being spoofedmitigates prefix hijackingDifficult to send malicious packets to particular target

13/18MMLABArchitecture 4) CachingBoth IP & NDN router buffers data packetBut NDN router reuse dataBenefitsBoth of static and dynamic data could be got benefitsIn case of dynamic data, retransmission cost is easedAlleviation of privacy problem concerns In todays network, one can figure out WHAT data is, WHO wants data from by inspecting headerNDN router doesnt know who originates the request

14/18MMLABArchitecture 5) PIT (Pending Interest Table)Waiting list for requiring dataSupportsPIT can setup timer (application takes charge of retransmission)Natural support for multicastRepetitive interest can be served using one dataRate & Congestion control for incoming dataBy controlling PIT sizeCongestion control has been moved from transport layerMitigates DDoS attackNumber of PIT entries is an explicit indication of router loads

15/18MMLABArchitecture 6)TransportNDN doesnt have separate transport layerSupportsMultiplexing and demultiplexingDirectly done using namesData integrity and reliability checkedSignatureManagement of traffic loads by setting PIT sizeEliminates end-hosts congestion controlRetransmission is aided by cache16/18clientsservercongesteddataMMLAB16On-Going Projects originated from limitsRouting table managementUnbounded address rises scalability issues for routing table

Security issues about keyKey management and dissemination

Cache capacity Lots of cached space needed

17/18MMLABConclusionCurrent usage of network needs changed paradigm from host centric to data centric networkWe need data, not host information

NDN (Named Data Networking) supports many functionalities that is hardly or can not be done in current networkAddressing problemSecurity problemEtc..