This HTML5 document contains 104 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dbthttp://dbpedia.org/resource/Template:
n35http://www.ccnx.org/
n20https://www.theregister.co.uk/2014/09/05/named_data_networking_consortium_launches_to_replace_tcp_ip/
wikipedia-enhttp://en.wikipedia.org/wiki/
dbrhttp://dbpedia.org/resource/
n36http://named-data.net/publications/
n18http://minindn.memphis.edu/
n33http://named-data.net/codebase/platform/
n17https://web.archive.org/web/20140920173000/https:/buffy.eecs.berkeley.edu/PHP/resabs/
n29http://
n11http://commons.wikimedia.org/wiki/Special:FilePath/
dcthttp://purl.org/dc/terms/
rdfshttp://www.w3.org/2000/01/rdf-schema#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n12http://dbpedia.org/resource/File:
dbphttp://dbpedia.org/property/
xsdhhttp://www.w3.org/2001/XMLSchema#
n15https://github.com/named-data-iot/
n32http://ndnsim.net/current/
dbohttp://dbpedia.org/ontology/
n38https://web.archive.org/web/20170211155751/https:/www.gitbook.com/book/schwannden/ndn-on-galileo/
n30https://named-data.net/codebase/platform/ndn-ccl/
dbchttp://dbpedia.org/resource/Category:
n19https://named-data.net/ndn-testbed/
n10https://www.youtube.com/
wikidatahttp://www.wikidata.org/entity/
goldhttp://purl.org/linguistics/gold/
n22https://global.dbpedia.org/id/
n28https://www.nsf.gov/awardsearch/
provhttp://www.w3.org/ns/prov#
n27https://web.archive.org/web/20160305143858/http:/gregorio.stanford.edu/triad/
foafhttp://xmlns.com/foaf/0.1/
dbpedia-zhhttp://zh.dbpedia.org/resource/
n16https://github.com/named-data/
n34http://named-data.net/doc/ndn-tlv/
n14http://named-data.net/
freebasehttp://rdf.freebase.com/ns/
n9https://www.gitbook.com/book/schwannden/
owlhttp://www.w3.org/2002/07/owl#

Statements

Subject Item
dbr:NDN
dbo:wikiPageWikiLink
dbr:Named_data_networking
dbo:wikiPageDisambiguates
dbr:Named_data_networking
Subject Item
dbr:Named_data_networking
rdf:type
dbo:Company
rdfs:label
命名資料網路 Named data networking
rdfs:comment
命名資料網路（Named Data Networking，NDN）是一個未來的（Future Internet Architecture），靈感來自多年在網路使用上的實證研究，導致人們逐漸意識到，現今的互聯網架構中在舊有的 IP 協定上懸而未決的問題 。NDN根源於一個Van Jacobson在2006年首次公開展示的專案計畫「」(CCN)。NDN的目標在於檢視如何依據Jacobson的提議，從現今以主機為中心的網路架構IP演進到以資料為中心的網路架構NDN。一般相信這項概念上的簡單轉變，將對人們如何設計、開發、部署和使用網路以及應用程式產生深遠的影響。 網際網路目前主要用作信息散佈的平台，但這並非 IP 的強項。因此，未來互聯網的“瘦腰”（thin waist）架構應當基於命名資料，而非以數字定址的主機。基本原則是，通信網路應該允許用戶專注於他或她需要的資料，也就是所謂的「內容」（content），而不必指定資料要取自哪個實際位置，也就是所謂的「主機」（host）。由於當前的互聯網中，絕大多數（“高達流量的90％”）的網路使用方式都是由單一來源傳播到多個用戶, 命名資料網路的許多機制均具有廣泛的優勢潛力，例如內容快取，以減少擁塞並提高傳遞速度，簡化網路設備配置，以及在資料層級就直接內建網路安全性。 Named Data Networking (NDN) (related to content-centric networking (CCN), content-based networking, data-oriented networking or information-centric networking (ICN)) is a proposed Future Internet architecture inspired by years of empirical research into network usage and a growing awareness of unsolved problems in contemporary internet architectures like IP. NDN has its roots in an earlier project, Content-Centric Networking (CCN), which Van Jacobson first publicly presented in 2006. The NDN project is investigating Jacobson's proposed evolution from today's host-centric network architecture IP to a data-centric network architecture (NDN). The belief is that this conceptually simple shift will have far-reaching implications for how people design, develop, deploy, and use networks and appli
foaf:depiction
n11:NDN_Architecture_Stack.png n11:NDN_Packets.png
dct:subject
dbc:Network_layer_protocols dbc:Internet_protocols dbc:Computer_networking
dbo:wikiPageID
11092014
dbo:wikiPageRevisionID
1076845884
dbo:wikiPageWikiLink
dbr:Forwarding_information_base dbc:Network_layer_protocols dbr:Multicast dbc:Internet_protocols dbr:Internet dbr:Information_distribution dbc:Computer_networking dbr:E-commerce dbr:Trust_no_one_(Internet_security) dbr:Open_Shortest_Path_First dbr:Information-centric_networking_caching_policies dbr:Privacy dbr:Digital_media dbr:Named_Data_Networking n12:NDN_Architecture_Stack.png dbr:Smartphone_application dbr:IPv4_address_exhaustion dbr:End-to-end_principle dbr:Link-state_routing_protocol dbr:Social_networking dbr:Provenance dbr:Network_address_translation dbr:Future_Internet dbr:Future_Internet_Research_and_Experimentation dbr:Information-centric_networking dbr:Van_Jacobson dbr:Interest_Flooding_Attack dbr:Classless_Inter-Domain_Routing dbr:Content-centric_networking n12:NDN_Packets.png dbr:Public-key_cryptography dbr:Point-to-point_(telecommunications) dbr:PARC_(company) dbr:Distance-vector_routing_protocol dbr:Content_(media) dbr:Ted_Nelson dbr:Web_of_trust dbr:Internet_Protocol dbr:Internet_of_things dbr:Border_Gateway_Protocol dbr:GNU_General_Public_License
dbo:wikiPageExternalLink
n9:ndn-on-galileo n10:watch%3Fv=oCZMoY3q2uM&authuser=0 n14: n15:ndn-lite n16:NFD n17:resabs.php%3Ff_year=2007&f_submit=one&f_absid=101594 n18: n19: n20: n27:nbrp.html n28:showAward%3FAWD_ID=1040868 n28:showAward%3FAWD_ID=1345318 n29:www.named-function.net n30: n32: n33: n34: n35: n36: n38:details
owl:sameAs
n22:4sMq2 wikidata:Q6961556 freebase:m.02q_rtw dbpedia-zh:命名資料網路
dbp:wikiPageUsesTemplate
dbt:Reflist dbt:Advert
dbo:thumbnail
n11:NDN_Architecture_Stack.png?width=300
dbo:abstract
命名資料網路（Named Data Networking，NDN）是一個未來的（Future Internet Architecture），靈感來自多年在網路使用上的實證研究，導致人們逐漸意識到，現今的互聯網架構中在舊有的 IP 協定上懸而未決的問題 。NDN根源於一個Van Jacobson在2006年首次公開展示的專案計畫「」(CCN)。NDN的目標在於檢視如何依據Jacobson的提議，從現今以主機為中心的網路架構IP演進到以資料為中心的網路架構NDN。一般相信這項概念上的簡單轉變，將對人們如何設計、開發、部署和使用網路以及應用程式產生深遠的影響。 網際網路目前主要用作信息散佈的平台，但這並非 IP 的強項。因此，未來互聯網的“瘦腰”（thin waist）架構應當基於命名資料，而非以數字定址的主機。基本原則是，通信網路應該允許用戶專注於他或她需要的資料，也就是所謂的「內容」（content），而不必指定資料要取自哪個實際位置，也就是所謂的「主機」（host）。由於當前的互聯網中，絕大多數（“高達流量的90％”）的網路使用方式都是由單一來源傳播到多個用戶, 命名資料網路的許多機制均具有廣泛的優勢潛力，例如內容快取，以減少擁塞並提高傳遞速度，簡化網路設備配置，以及在資料層級就直接內建網路安全性。 Named Data Networking (NDN) (related to content-centric networking (CCN), content-based networking, data-oriented networking or information-centric networking (ICN)) is a proposed Future Internet architecture inspired by years of empirical research into network usage and a growing awareness of unsolved problems in contemporary internet architectures like IP. NDN has its roots in an earlier project, Content-Centric Networking (CCN), which Van Jacobson first publicly presented in 2006. The NDN project is investigating Jacobson's proposed evolution from today's host-centric network architecture IP to a data-centric network architecture (NDN). The belief is that this conceptually simple shift will have far-reaching implications for how people design, develop, deploy, and use networks and applications. NDN has three core concepts that distinguish NDN from other network architectures. First, applications name data and data names will directly be used in network packet forwarding; consumer applications request desired data by its name, so communications in NDN are consumer-driven. Second, NDN communications are secured in a data-centric manner, that is, each piece of data (called a Data packet) will be cryptographically signed by its producer and sensitive payload or name components can also be encrypted for the purpose of privacy; in this way, consumers can verify the packet regardless of how the packet is fetched. Third, NDN adopts a stateful forwarding plane where forwarders will keep a state for each data request (called an Interest packet) and erase the state when a corresponding Data packet comes back; NDN's stateful forwarding allows intelligent forwarding strategies and eliminates loops. Its premise is that the Internet is primarily used as an information distribution network, which is not a good match for IP, and that the future Internet's "thin waist" should be based on named data rather than numerically addressed hosts. The underlying principle is that a communication network should allow a user to focus on the data they need, named content, rather than having to reference a specific, physical location where that data is to be retrieved from, named hosts. The motivation for this is derived from the fact that the vast majority of current Internet usage (a "high 90% level of traffic") consists of data being disseminated from a source to a number of users. Named-data networking comes with potential for a wide range of benefits such as content caching to reduce congestion and improve delivery speed, simpler configuration of network devices, and building security into the network at the data level.
gold:hypernym
dbr:Architecture
prov:wasDerivedFrom
wikipedia-en:Named_data_networking?oldid=1076845884&ns=0
dbo:wikiPageLength
35139
foaf:isPrimaryTopicOf
wikipedia-en:Named_data_networking
Subject Item
dbr:Interest_Flooding_Attack
dbo:wikiPageWikiLink
dbr:Named_data_networking
Subject Item
dbr:Content_centric_networking
dbo:wikiPageWikiLink
dbr:Named_data_networking
Subject Item
dbr:Magnet_URI_scheme
dbo:wikiPageWikiLink
dbr:Named_data_networking
Subject Item
dbr:Future_Internet_Research_and_Experimentation
dbo:wikiPageWikiLink
dbr:Named_data_networking
Subject Item
dbr:Linear_network_coding
dbo:wikiPageWikiLink
dbr:Named_data_networking
Subject Item
dbr:Lixia_Zhang
dbo:wikiPageWikiLink
dbr:Named_data_networking
Subject Item
dbr:Ed2k_URI_scheme
dbo:wikiPageWikiLink
dbr:Named_data_networking
Subject Item
dbr:Named_Data_Networking
dbo:wikiPageWikiLink
dbr:Named_data_networking
dbo:wikiPageRedirects
dbr:Named_data_networking
Subject Item
dbr:Data-centric_networking
dbo:wikiPageWikiLink
dbr:Named_data_networking
dbo:wikiPageRedirects
dbr:Named_data_networking
Subject Item
dbr:Metalink
dbo:wikiPageWikiLink
dbr:Named_data_networking
Subject Item
dbr:Van_Jacobson
dbo:wikiPageWikiLink
dbr:Named_data_networking
Subject Item
dbr:Named_Data_Network
dbo:wikiPageWikiLink
dbr:Named_data_networking
dbo:wikiPageRedirects
dbr:Named_data_networking
Subject Item
wikipedia-en:Named_data_networking
foaf:primaryTopic
dbr:Named_data_networking