![Page 1: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/1.jpg)
Contrace:TracerouteFacilityforContent-CentricNetwork
Hitoshi Asaeda (NICT) Xun Shao (NICT)
Thierry Turletti (Inria)
draft-asaeda-icnrg-contrace-02
98th IETF/IRTF, Mar. 2017, Chicago, USA
1
![Page 2: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/2.jpg)
Contrace Overview
n Protocol analysis tool Ø Caching point/publisher, path stretch Ø Hop count/RTT for content retrieval Ø Cache distribution, cache hit ratio
n Operations, Administration, and Maintenance (OAM) tool Ø Operation
p Cache lifetime or expiration time Ø Monitoring
p CS usage at router, num of rcvd interests per cache
p Multipath forwarding Ø Trouble shooting
p Availability of caching routers and publishers
98th IETF/IRTF, Mar. 2017, Chicago, USA 2
![Page 3: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/3.jpg)
Contrace Messages
n Contrace Request Message Ø Request message consists of a fixed header,
Request block TLV, Report block TLV(s), and Name TLV
n Contrace Reply Message Ø Reply message consists of a fixed header, Request
block TLV, Report block TLV(s), Name TLV, and and Reply block/sub-block TLV(s)
n Compatible with CCNx-1.0 TLV format
98th IETF/IRTF, Mar. 2017, Chicago, USA 3
![Page 4: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/4.jpg)
Contrace Basic Behaviorn Request message is initiated by Contrace user and forwarded
toward caching router or publisher based on the FIB in a hop-by-hop manner
n Request message includes Request block and Report block(s)
n Reply message is initiated by caching router or publisher and forwarded toward Contrace user based on the PIT entry
n Reply message includes Reply block and Reply sub-block(s)
98th IETF/IRTF, Mar. 2017, Chicago, USA 4
Consumer(Contraceuser)
PublisherRouterC(Cachingrouter)
RouterA
RouterB
RouterE
RouterD
RequestResponse
![Page 5: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/5.jpg)
Security Considerationsn Policy-Based Information Provisioning for Request
Ø Routers can reply the Contrace Reply with the ADMIN_PROHIB return code without appending any Reply (sub-)block TLV
Ø Permission, whether (1) All (all cache information is disclosed), (2) Partial (cache information with the particular name prefix can (or cannot) be disclosed), or (3) Deny (no cache information is disclosed), can be defined at routers
n Filtering of Contrace Users Located in Invalid Networks Ø Routers may support an access control mechanism
to filter out Requests from invalid Contrace users located in invalid networks
98th IETF/IRTF, Mar. 2017, Chicago, USA 5
![Page 6: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/6.jpg)
Security Considerations – cont’dn Topology Discovery
Ø If a network topology is a secret, Contrace Requests may be restricted at the border of the domain, using the ADMIN_PROHIB return code
n Characteristics of Content Ø If publisher or content information is secret,
Contrace Requests may be restricted at the border of the domain, using the ADMIN_PROHIB return code
n Shortening Contrace Reply Timeout Ø Routers may configure the shorter timeout value to
time out the Request n Limiting Request Rates
Ø Routers may rate-limit Contrace Requests by ignoring some of the consecutive messages.
98th IETF/IRTF, Mar. 2017, Chicago, USA 6
![Page 7: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/7.jpg)
Security Considerations – cont’dn Limiting Reply Rates
Ø Routers in the traced path may rate-limit Contrace Replies.
n Adjacency Verification Ø Forwarding Contrace messages given from
non-adjacent neighbor nodes/routers must be prohibited
Ø Defining the secure way to verify the adjacency cannot rely on the way specified in CCNx message format or semantics; therefore a new TLV for adjacency verification using hop-by-hop TLV header will be defined in a separate document.
98th IETF/IRTF, Mar. 2017, Chicago, USA 7
![Page 8: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/8.jpg)
Ex.1. contrace ccnx:/news/science
98th IETF/IRTF, Mar. 2017, Chicago, USA 8
c r1r2
r3 r4
p1p2
p3
![Page 9: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/9.jpg)
Ex.2. contrace –n ccnx:/video/video1
98th IETF/IRTF, Mar. 2017, Chicago, USA 9
c r1r2
r3 r4
p1
p3
p2
![Page 10: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/10.jpg)
Ex.3. contrace –o ccnx:/news/today
98th IETF/IRTF, Mar. 2017, Chicago, USA 10
c r1r2
r3 r4
p1
p3
p2
![Page 11: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/11.jpg)
Summaryn Contrace, which is compatible with CCNx-1.0 TLV format, is a
powerful network tool providing various information, e.g., Ø Caching point/publisher, path stretch Ø Hop count/RTT for content retrieval Ø Cache distribution, cache hit ratio Ø Cache lifetime or expiration time Ø CS usage, num of received interests
n Security considerations discussed n Experiments with a running code
Ø Contrace, IEEE ComMag, Mar. 2015. Ø New Contrace (proposed in this I-D) is also implemented
and tested
n On going Ø Contrace-NDN specification (in a separate document)
98th IETF/IRTF, Mar. 2017, Chicago, USA 11
![Page 12: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/12.jpg)
Backup
98th IETF/IRTF, Mar. 2017, Chicago, USA 12
![Page 13: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/13.jpg)
12301234567890123456789012345678901+---------------+---------------+---------------+---------------+|Version|PT_TRACE_REQ|PacketLength|+---------------+---------------+---------------+---------------+|HopLimit|ReturnCode|Reserved(MBZ)|HeaderLength|+===============+===============+===============+===============+||+RequestblockTLV+||+---------------+---------------+---------------+---------------+/ReportblockTLV1/+---------------+---------------+---------------+---------------+/ReportblockTLV2/+---------------+---------------+---------------+---------------+/.//./+---------------+---------------+---------------+---------------+/ReportblockTLVn/+===============+===============+===============+===============+|T_TRACE|MessageLength|+---------------+---------------+---------------+---------------+|T_NAME|Length|+---------------+---------------+---------------+---------------+/NamesegmentTLVs(nameprefixspecifiedbycontracecommand)/+---------------+---------------+---------------+---------------+
Request Message
1398th IETF/IRTF, Mar. 2017, Chicago, USA
![Page 14: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/14.jpg)
12301234567890123456789012345678901+---------------+---------------+---------------+---------------+|T_TRACE_REQ|Length|+---------------+---------------+---------------+---------------+
|SchemeName|SkipHopCount|Timeout|Reserved(MBZ)|+---------------+---------------+---------------+---------------+|RequestID|Flags|+---------------+---------------+---------------+---------------+
Request Block and Report Blockn Request block
n Report block
12301234567890123456789012345678901+---------------+---------------+---------------+---------------+|T_TRACE_REPORT|Length|+---------------+---------------+---------------+---------------+
|RequestArrivalTime|+---------------+---------------+---------------+---------------+/NodeIdentifier/+---------------+---------------+---------------+---------------+
98th IETF/IRTF, Mar. 2017, Chicago, USA 14
![Page 15: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/15.jpg)
Reply Message12301234567890123456789012345678901+---------------+---------------+---------------+---------------+|Version|PT_TRACE_REPLY|PacketLength|+---------------+---------------+---------------+---------------+|HopLimit|ReturnCode|Reserved(MBZ)|HeaderLength|+===============+===============+===============+===============+...+===============+===============+===============+===============+|T_TRACE|MessageLength|+---------------+---------------+---------------+---------------+|T_NAME|Length|+---------------+---------------+---------------+---------------+/NamesegmentTLVs(nameprefixspecifiedbycontracecommand)/+---------------+---------------+---------------+---------------+/ReplyblockTLV/+---------------+---------------+---------------+---------------+/Replysub-blockTLV1/+---------------+---------------+---------------+---------------+/Replysub-blockTLV2/+---------------+---------------+---------------+---------------+/.//./+---------------+---------------+---------------+---------------+/Replysub-blockTLVk/+---------------+---------------+---------------+---------------+
98th IETF/IRTF, Mar. 2017, Chicago, USA 15
![Page 16: Contrace: Traceroute Facility for Content- Centric Network · PDF fileContrace: Traceroute Facility for Content-Centric Network Hitoshi Asaeda (NICT) Xun Shao (NICT) Thierry Turletti](https://reader034.vdocuments.site/reader034/viewer/2022051405/5a74d62e7f8b9aea3e8c0848/html5/thumbnails/16.jpg)
12301234567890123456789012345678901+---------------+---------------+---------------+---------------+|Type|Length|+---------------+---------------+---------------+---------------+
|ContentSize|+---------------+---------------+---------------+---------------+|ObjectCount|+---------------+---------------+---------------+---------------+|#ReceivedInterest|+---------------+---------------+---------------+---------------+
|FirstSeqnum|+---------------+---------------+---------------+---------------+|LastSeqnum|+---------------+---------------+---------------+---------------+
|CacheLifetime|+---------------+---------------+---------------+---------------+|RemainCacheLifetime|+---------------+---------------+---------------+---------------+|T_NAME|Length|
+---------------+---------------+---------------+---------------+/NamesegmentTLVs(nameprefixpartially/exactlymatched)/+---------------+---------------+---------------+---------------+
Reply Sub-Block
1698th IETF/IRTF, Mar. 2017, Chicago, USA