未来互联网――Named Data Networking (NDN) Project

NamedDataNetworking(NDN)ProjectNDN-0001October31,2010LixiaZhang,DeborahEstrin,andJeffreyBurkeUniversityofCalifornia,LosAngelesVanJacobson,JamesD.Thornton,andDianaK.SmettersPaloAltoResearchCenter(PARC)BeichuanZhangUniversityofArizonaGeneTsudikUniversityofCalifornia,IrvinekcclaffyandDmitriKrioukovUniversityofCalifornia,SanDiegoDanMasseyandChristosPapadopoulosColoradoStateUniversityTarekAbdelzaherUniversityofIllinoisatUrbana-ChampaignLanWangUniversityofMemphisPatrickCrowleyWashingtonUniversityEdmundYehYaleUniversityContents1Vision12Architecture22.1ArchitecturalPrinciples........................................22.2TheNDNArchitecture........................................32.2.1Names............................................32.2.2Data-CentricSecurity....................................42.2.3RoutingandForwarding...................................52.2.4Caching............................................52.2.5PendingInterestTable(PIT).................................62.2.6Transport...........................................62.3HowNDNAdherestoArchitecturalPrinciplesandBenefitsSociety...............72.4Comparison..............................................73ResearchAgenda83.1Routing................................................83.1.1InitialDeployment:ExtendingExistingRoutingProtocols................83.1.2Long-TermDeployment:AchievingRoutingScalability..................83.2Forwarding..............................................93.2.1FastNameLookup......................................103.2.2ForwardingStrategy.....................................113.2.3CachingPolicyandStorageManagement.........................113.3DriverApplications..........................................123.3.1Mainstreamor“traditional”applications..........................123.3.2Media-richinstrumentedenvironments...........................123.3.3Participatorysensing.....................................133.4SecurityandPrivacy.........................................143.4.1EfficiencyofSignatures...................................143.4.2UsableTrustManagement..................................143.4.3NetworkSecurityandDefense...............................153.4.4ContentProtectionandPrivacy...............................153.5FundamentaltheoryforNDN....................................163.6ImplementationandDeployment..................................163.7EvaluationandAssessment.....................................174Education185RelatedWork186Summary19i1VisionInthe1960sand70swhenthecoreideasunderlyingtheInternetweredeveloped,telephonywastheonlyexampleofsuccessful,effective,global-scalecommunications.ThuswhilethecommunicationsolutionofferedbyTCP/IPwasuniqueandgroundbreaking,theproblemitsolvedwastelephony’s:apoint-to-pointconversationbetweentwoentities.Theworldhaschangeddramaticallysincethen.•Information-intensivebusinessliketravel,banksandfinancialserviceslongagomovedontotheIn-ternet.TodayalmostanythingisavailableonlineastheInternetbecomestheworld’sstorefront.•Digitalcodingadvanceshaveturnednotjusttextbutvoice,imagesandvideointostringsofbitssoaneverincreasingrangeofcontentcanbedistributeddigitally.•TheWebhasmadeiteasyforanyonetocreate,discoverandconsumecontentwiththeresultthatexabytesofnewcontentareproducedyearly.•Moore’s-Law-drivenhardwareadvanceshavemadeitfeasibletoconnecteverythingtotheInternet:notjustsupercomputersandworkstationsbutalsofactories,municipalinfrastructure,phones,cars,appliances,evenlightswitches.WhileIPhasexceededallexpectationsforfacilitatingubiquitousinterconnectivity,itwasdesignedforcon-versationsbetweencommunicationsendpointsbutisoverwhelminglyusedforcontentdistribution.JustasthetelephonesystemwouldbeapoorvehicleforthebroadcastcontentdistributiondonebyTVandradio,theInternetarchitectureisapoormatchtoitsprimaryusetoday.The‘conversational’natureofIPisembodiedinitsdatagramformat:IPdatagramscanonlynamecommunicationendpoints(theIPdestinationandsourceaddresses).Asourprojecttitlesuggests,weproposetogeneralizetheInternetarchitecturebyremovingthisrestriction:thenamesinanNDNdatagramarehierarchicallystructuredbutotherwisearbitraryidentifiers.Theycanbeusedtonameachunkofdatainaconversation,astheTCP/IPtransportsignatureplussequencenumberdoestoday,buttheycanalsonameachunkofdatafromaYouTubevideodirectly,ratherthanforcingittobeembeddedinaconversationbetweentheconsuminghostandyoutube.com.Thissimplechangetothehourglassmodel,allowingthethinwaisttousedatanamesinsteadofIPaddressesfordatadelivery,makesdataratherthanitscontainersafirst-classcitizenintheInternetarchitecture.Thischangecreatesanabundanceofnewopportunities:•Today’sapplicationsaretypicallywrittenintermsofwhatinformationtheywantratherthanwhereitislocated,thenapplication-specificmiddlewareisusedtomapbetweentheapplicationmodelandtheInternet’s.WithNDNtheapplication’swhatmodelcanbeimplementeddirectly,removingallthemiddlewareanditsassociatedconfigurationandcommunicationinefficiencies.•Sinceconversationsareephemeralandcanbeaboutanything,thecurrentsecurityapproachistheone-size-fits-allmodelofarmoringthechannelb