Download presentation
Presentation is loading. Please wait.
Published byJeffry Walton Modified over 9 years ago
1
A Common ICN API A discussion starter IRTF ICNRG Vancouver, Nov 2013 Börje Ohlman Alina Quereilhac
2
Disclaimers This should not be regarded as a proposal. This is a thought experiments to better understand the key components of ICN APIs and interfaces In these slides I use CCN to represent CCN/NDN
3
Background ICN is now where packet networking was in the late 70’s, early 80’s We then had SNA, OSI, DecNet, AppleTalk, IP, IPx, etc. Some of you will remember multi-service routers… I’m not saying that I long back to those days… ;-)
4
Slide title 44 pt Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt Characters for Embedded font: !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRSTUV WXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª« ¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛ ÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċ ČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐőŒ œŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛ ˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚ ĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞ ŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻ−≤≥fifl ΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰα βγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏ ЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХ ЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧ ШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏ ѢѢѲѲѴѴ ҐҐәǽẀẁ ẂẃẄẅỲỳ№ Do not add objects or text in the footer area NetInf| Ericsson Internal | 2013-09-30 | Page 4 Application independent API for accessing any object, regardless of location ICN API getObject(objectID) getObject(attr1, attr2, attr3) Internet Mobile networks Broadcast TV/Radio Real world sensorperson App 1 App 2 person App 3 person App 4 CDN P2P
5
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area Information-centric inter-networking interface (ICiNi) and ICN API ICN ICN App1 ICN App2 ICN App3 ICN API ICN ICN App1 ICN App2 ICN App3 ICN API ICiNi
6
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area Information-centric inter-networking interface (ICiNi) and API NetInf ICN App1 ICN App2 ICN App3 ICN API CCN ICN App1 ICN App2 ICN App3 ICN API ICiNi
7
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area ICN API NetInf CCN ICiNi Adaption layer functions –Mappings of ›primitives ›names ›object representations NetInf ICN App1 ICN App2 ICN App3 ICN API Common format NetInf adaptation layer CCN ICN App1 ICN App2 ICN App3 ICN API Common format CCN adaptation layer Motivation –Applications can be reused, interworked and evaluated Research challenges –Define common › primitives, e.g. -PUBLISH, PUT, GET, SEARCH, … ›naming format ›content object representation
8
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area API and network interfaces are the same in ICN ›The primitives used in the API are the same as the messages sent over network interfaces in both CCN and NetInf –CCN messages are ›INTEREST ›DATA –NetInf messages are ›GET ›RESPONSE.
9
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area Requirements for a Common ICN API ›The API/interface should be RESTFUL –Which seems reasonable as we are not dealing with e2e connections –This is important if we should be able to build gateways that does not get overly complex and/or gets into scalability issues ›The common API needs a common naming format –One proposal could be to use the ni naming format (RFC 6920) in a way that unifies CCN and NetInf naming ›the Authority part is a CCN name (if known) ›the Digest Value is the NetInf name (if known)
10
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area Possible Common ICN name format for the ICN API ›Possible common name format –cf://[Authority part ala CCN]/[NetInf name (hash)] ›CCN could include the Digest Value of the objects in the CCN name –That would ease the translations –Could be beneficial for CCN ›could be used as a hash value when doing cache and PIT lookups.
11
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area Information-centric inter-networking interface (ICiNi) NetInf ICN App1 ICN App2 ICN App3 ICN API CCN ICN App1 ICN App2 ICN App3 ICN API ICiNi ›Motivation –Unlikely there will be only one ICN network protocol (at least initially) –Give us understanding of what are the critical issues for ICN inter- networking ›Research challenges –Define inter-networking protocol –Mapping of names
12
CCN Gateway NetInf Common App Gateway (a) Gateway (b) CCN Common App Common App CCN publisher replica Topology Common App Common App Common App 1 2 1 3 4 5 6 7 15 14 16 12 13 8 9 10 11
13
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area Content object representation, metadata NetInf ICN App1 ICN App2 ICN App3 ICN API CCN ICN App1 ICN App2 ICN App3 ICN API ICiNi ›Content objects retrieved through the API should be understood by the destination ICN implementation regardless of where it comes from ›Possibilities: a)Define common content object format b)Keep all native ICN formats CCN Object?? CCN
14
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area Common object format ›The ICN API should be capable of constructing/parsing content objects with common format –Still, a way of deciding whether a ‘common format object’ or a ‘native object’ should be sent back is needed NetInf CCN ICN App1 ICN App2 ICN App3 ICN API ICiNi Request Send CCN or common format? tag:common
15
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area Information-centric inter-networking interface (ICiNi) – using common object store NetInf CCN ›Motivation –Having one common (virtual) object store avoids n 2 problem ›Research challenges –Common name and object format for the common store Common object store (ICiNi) ICN App1 ICN App2 ICN App3 ICN API Common format CCN adaptation layer ICN App1 ICN App2 ICN App3 ICN API Common format NetInf adaptation layer CCN adaptation layer
16
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area Conclusions ›The basic CCN/CCN and NetInf APIs have strong similarities –The new ICN API will look very different from today’s socket API –We should try to define it in a way that can be stable over a long time and allow for evolution of the underlying ICN approach(s) ›Potentially there are three common things that could be defined –Common API primitives –Common Naming format –Common Object/Transfer format, especially for metadata ›There more things we need to define, among them: –How would routing work? –How would pub/sub work? –What about Search and Attribute requests?
17
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area Backup slides
18
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area NetInf use of a Common ICN API ›A NetInf node receiving a CCN name –Ask NRS for a locator to where it can send a GET/HTTP request to reach the publisher (in this case a CCN gateway or directly to the CCN publisher) of the requested object –The CCN gateway or publisher could then either return the object directly or calculate a Digest Value to be sent back to the NetInf node that then could make a new request and possibly find the object in a NetInf cache.
19
Slide title minimum 32 pt (32 pt makes 2 rows) Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt ›!"# $%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNO PQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv wxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄ ÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäå æçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČ ĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇ ňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™−≤≥fifl Do not add objects or text in the footer area CCN use of a Common ICN API ›A CCN node receiving a NetInf name –Merge the Authority part (which in these scenarios would have to be mandatory) and the Digest Value into a CCN name –Forward an interest with that name towards what should be a NetInf gateway which easily could reconstruct the NetInf name –Find the object in the NetInf part of the network and return it ›Possible name formats –/[Authority part]/[NetInf name] ›Used for direct routing in the CCN network –/netinf/[Authority part]/[NetInf name] ›Used to find a NetInf GW
20
Slide title 44 pt Text and bullet level 1 minimum 24 pt Bullets level 2-5 minimum 20 pt Characters for Embedded font: !"#$%&'()*+,-./0123456789:; ?@ABCDEFGHIJKLMNOPQRSTUV WXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª« ¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛ ÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċ ČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐőŒ œŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒˆˇ˘˙˚˛ ˜˝ẀẁẃẄẅỲỳ–— ‘’‚“”„†‡…‰‹›⁄€™ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚ ĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞ ŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻ−≤≥fifl ΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰα βγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏ ЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХ ЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧ ШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏ ѢѢѲѲѴѴ ҐҐәǽẀẁ ẂẃẄẅỲỳ№ Do not add objects or text in the footer area NetInf| Ericsson Internal | 2013-09-30 | Page 20 ni:///sha-256;B_K97zTtFuOhug27fke4_Z… application/json Object management data multipart/mixed Named data object application/steam-meta+xml application/binary Application-specific meta data Actual object bits Object Name Object in Message SHA-256 hash coverage SHA-256 Hash (Base64) NDO Structure RFC 6920: Naming Things with Hashes
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.