Networking Of Information - ETSI

1y ago
17 Views
2 Downloads
1.90 MB
14 Pages
Last View : 2m ago
Last Download : 3m ago
Upload by : Karl Gosselin
Transcription

ETSI Workshop on Future Network TechnologiesNetworking of InformationAn information-centric approachto the network of the futureVinicio Vercellone - Telecom ItaliaBengt Ahlgren – SICS& 4WARD WP6 colleaguesSophia AntipolisMarch, 10th 2010

Network of InformationFutureInformation-centric NetworkToday’s InternetCommunication ModelFocuses onConversations between HostsCommunication ModelFocuses onDissemination of InformationobjectsHost-centric abstractionInformation-centric abstractionEvolutionIn today’s Internet,accessing information isthe dominating use case!2010-03-04FP7 4WARD Project - www.4ward-project.euSlide 2

Problems resulting from Host-centric view No common persistent naming scheme for information– URLs and IPs overloaded with locator and identifier functionality Moving information changing it‘s name („404 file not found“ errors) Use flat namespace for persistent identification No consistent representation of information (copy-independent)– No consistent way to keep track of identical copies– Different encodings (e.g., mp3, wav) worsen problem Information dissemination is inefficient– Can‘t benefit from existing copies (e.g. local copy on client) Also true for Content Delivery Networks (e.g. Akamai)– No “anycast”: e.g., get “nearest” copy– Problems like Flash-Crowd effect, Denial of Service, Security is host-centric– Mainly based on securing channels (encryption) and trusting servers (authentication)– Can’t trust a copy received from an untrusted serverProblems can be solved in a consistent mannervia an information-centric architecture10/03/2010FP7 4WARD Project - www.4ward-project.euSlide 3

NetInf Scenarios Content distribution–––VideoOnDemand, Live TV, Web pagesCaching can be built-in from the beginningInformation can be retrieved from the closestavailable sourceCommon dissemination infrastructure for allapplications, including network support–HP2PP2PP2PP2P P2P10/03/2010HHP2PDNNNetInf DissemniationDNNNetworkDNNDNNAPIHFP7 4WARD Project - www.4ward-project.euDNNHAPIHHAPIHSlide 4H

NetInf Scenarios Content distribution––––VideoOnDemand, Live TV, Web pagesCaching can be built-in from the beginningInformation can be retrieved from the closestavailable sourceCommon dissemination infrastructure for allapplications, including network support Augmented Internet – Real-world objects––10/03/2010Linking real world objects in the virtualinformation worldClicking on and bookmarking real world objectsFP7 4WARD Project - www.4ward-project.euEiffel Tower Historical Info Wikipedia Buy TicketSlide 5

Identifier and Information Modelling 1. Step: Persistently identify information via identifier/locator split– Location-independent identifiers– Represent multiple copies 2. Step: Representation of information via Information Objects (IOs)– Another level of indirection– Represent information independent of specific copy and encoding E.g. a text, a song– Contains information-specific metadata E.g. access rights, attributes Information Objects can do more:– Representation of: Streams Services Real-world objects(e.g., a book, person)– IOs can be used to organizeinformationAll l Entity EiffelIODataIOSong1.mp3 Song1.wavFilesSong1.mp3 Song1.wav Lyrics.txtEiffel.jpgSong1.mp3 Song1.wav Lyrics.txtEiffel.jpgLyrics.txtLyrics.txtEiffel.jpg Enables efficient information dissemination– System can automatically choose encoding and copy(e.g. based on metadata)– User can navigate information (e.g. choose encoding)10/03/2010FP7 4WARD Project - www.4ward-project.euSlide 6ServiceIOService1Service1Service1

NetInf Naming SchemeType Defines the format– e.g. Hash algorithm used (SHA1, MD5, )TypeA Hash(PKIO)L {identifier tags}Authenticator (A) Binds the ID of the IO to a public key PK– Hash function used to compress length of PKLabel (L) Identifying individual object published by Authenticator– contains a number of identifier attributes associatedwith an IO– (A, L) combination needs to be globally unique Supporting the combination of:––name persistence, self-certification, owner authentication, and owner identificationfor information objects that are static or dynamic, that change location, that change owner, andwhose owner change organisational affiliation– without need to trust the delivering hostPKorigPKnew1 Security metadata includePKnew1PKlatest– Cryptographic hash of the dataSKorigSKnew1– Certificate chain binding the IO key (PKIO) to owner key (PKowner)– Signature of the self-certified data with SKIO or any other authorised SK– All data needed for owner authentication and identification Separation of notion of publisher and owner, where the latter can stay anonymous10/03/2010FP7 4WARD Project - www.4ward-project.euSlide 7

Mapping Information Model toNetInf name resolutionIO ID:Type A hash(PK IO)L labelName resolution systemStorage/cachingname resolution nIOIO ID′BOlocator ABBOBOlocator B.2010-03-04FP7 4WARD Project - www.4ward-project.euSlide 8

NetInf Node ArchitectureApplicationsNetInf NodeAdditionalservicesNetInfStorage APIStorage engineResolutionand RoutingfunctionalityNetInfSearch APINetInf Additional ServicesStorage protocol(s)STORE(.)NetInf App. X protocolSearch engineNetInf APIINIResolution tLocalTransport controllerTCP/IP10/03/2010GPOther.Local storage engineCache engineFP7 4WARD Project - www.4ward-project.euName resolution protocol(s)PUT(.)GET(.).NetInf Transport controlprotocolSlide 9

Scalable Name Resolution System Combination of:– Hierarchical DHTs (Provider-based)– Topological embedding of DHTs– Name-based routingName Resolution SystemGlobalResolutionGet(X)HOST ALocalResolutionSource RegionLocalResolutionDestination RegionHOST BReturn dataXData Object10/03/2010FP7 4WARD Project - www.4ward-project.euSlide 10

Standardization issuesIssues to be considered forstandardization: NetInf interfaces– User-Network Interface– Inter-Provider InterfaceNetInfProvider XIINIIINIProvider 1Provider 3IINIINI Name resolution service betweendifferent domains– registration/query protocols– name resolution recordsProvider 2INIIINIIINIINI Information Network Interface Inter-Provider INI Transport and routing of messages Naming scheme NetInf APIs10/03/2010FP7 4WARD Project - www.4ward-project.euSlide 11

Standardization ITU Focus Group on Future Networks (FG FN)– NetInf and the information-centric approach presented at the firstmeeting of the focus group in Luleå, Sweden, July 2009 IETF DECADE– NetInf presented at the DECADE BoF at the 76th IETF meeting inHiroshima, Japan, November 2009– Internet-Draft submitted to the 77th IETF in Los Angeles draft-ohlman-decade-add-use-cases-reqs-00 , “Requirements foraccessing data in network storage” Proposes to widen the scope beyond P2P-based apps to also covervideo distribution applications (incl. IPTV, YouTube) and enumerates anumber of requirements to be addressed by the protocols10/03/2010FP7 4WARD Project - www.4ward-project.euSlide 12

Summary and Conclusion NetInf is about the design of a new network architecture based on aninformation-centric paradigm Some problems that are addressed by the NetInf––––Naming scheme for naming informationWorld-wide scalable Name Resolution mechanism for flat namesIOs as representation of informationEnable efficient information dissemination Benefit from available copies, anycast, caching, solve Flash-Crowd, – Secure information-centric architecture by embedding security into identifiers Some significant results up to date– Naming scheme with integrated security that is independent of hosts Detailed definition and security analysis– Design of a scalable integrated name resolution and routing scheme (MDHT)– Scalable solution for mobility of objects, hosts and networks (LLC)– Overall NetInf architecture prototype Demonstrated at international conferences10/03/2010FP7 4WARD Project - www.4ward-project.euSlide 13

Thank you !www.4ward-project.eu10/03/2010FP7 4WARD Project - www.4ward-project.euSlide 14

Networking of Information An information-centric approach to the network of the future . Focuses on Dissemination of Information objects Information -centric abstraction Today's Internet Communication Model Focuses on Conversations between Hosts Host -centric abstraction 2010-03-04 FP7 4WARD Project -www.4ward-project.eu Slide 2 Evolution .

Related Documents:

IEC 61326-2-6 EN 61326-2-6 JIS C 1806-1 Radio Communications (Excluding Protocol Testing) ETSI EN 300 086 ETSI EN 300 113 ETSI EN 300 220-1 ETSI EN 300 220-2 ETSI EN 300 220-3-1 ETSI EN 300 220-3-2 ETSI EN 300 220-4 ETSI EN

NEC Labs Europe GmbH ETSI ISG CIM Chairman (Industry Specification Group Context Information Management) ETSI Board Member ETSI Delegate for: CEN/CENELEC/ETSI SF-SSCC (Sector Forum on Smart and Sustainable Cities and Communities) CEN/CENELEC/ETSI CG-Smart Energy Grid CEN/CENELEC/ET

ETSI NFV, which detail REST APIs for management and orchestration, can be accessed by visiting the following links - ETSI GS NFV-SOL 002 and ETSI GS NFV-SOL 003. ETSI GS NFV-SOL 004, has also been completed, it specifies the format and structure of a VNF Package and is based on the OASIS TOSCA Cloud Service Archive (CSAR) format.

Dr. Lindsay Frost (NEC Labs Europe) Chairman of ETSI ISG CIM (Industry Specification Group . Context Information Management ) ETSI Board Member. CEN/CENELEC/ETSI SF -SSCC delegate (Sector Forum on Smart and Sustainable C

4 Final draft ETSI EN 303 645 V2.1.0 (2020-04) Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found

ETSI 2 ETSI GR SAI 004 V1.1.1 (2020-12) Reference DGR/SAI-004 Keywords artificial intelligence, security ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE

ETSI 2 ETSI GS NFV-SOL 003 V2.6.1 (2019-04) Reference RGS/NFV-SOL003ed261 Keywords API, NFV, protocol ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: 33 4 92 94 42 00 Fax: 33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la

ETSI 2 ETSI GS NFV-SOL 003 V2.4.1 (2018-02) Reference RGS/NFV-SOL003ed241 Keywords API, NFV, protocol ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: 33 4 92 94 42 00 Fax: 33 4 93 65 47 16