1 / 14

TinySec: Performance Characteristics

This presentation discusses the performance characteristics of TinySec, focusing on recent measurements conducted on Mica2 sensors (TOS 1.1.2). Key aspects include latency, bandwidth, and power utilization in TinySec's layer security mechanisms, emphasizing its hop-by-hop model rather than end-to-end. The talk highlights stress testing results, hardware crypto comparisons, and potential overheads associated with packet sizes. It concludes with suggestions for leveraging TinySec in future stack developments, ensuring low overhead security while maintaining integrity and access control.

lucas-barnett
Télécharger la présentation

TinySec: Performance Characteristics

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TinySec:Performance Characteristics Chris K :: Naveen S :: David W January 16, 2004

  2. This Talk • Recent results • Measurements on Mica2s (TOS 1.1.2) • Latency • Bandwidth • Power • Stress testing • Hardware crypto comparison & implications • 802.15.4 (e.g. CC2420)

  3. TinySec Review: How & Why • Link layer security mechanism • Hop-by-hop, not end-to-end • Better support for aggregation • Enables higher level keying protocols • Low overhead security in software • Cryptographic checksum (MAC) • Ensures integrity • Enforces access control • Optional encryption

  4. TinySec Performance • Characterize Overhead: Energy, Latency, Bandwidth. • Factors for TinySec overhead • Computation • Larger packet sizes • Can predict overhead caused by packet sizes • Measurement goal: Show computation overhead is minimal • Note: crypto HW only reduces computation overhead

  5. Packets & Predicted Overhead Old packet (CRC): +7 b Authentication Only (TinySec-Auth): +8 b Authentication, Encryption (TinySec-AE) : +12 b IV

  6. Latency Test Setup LM • Setup: • 4x9 grid in Woz of Mica2s • Landmark routing code from midterm demo • 200 measurements per hopcount B • Test purpose: • Measure latency at different hopcounts • Determine difficulty in adding TinySec to existing application • Integrate with SystemC • Successfully transmitted 70,000+ packets: Our stress test A BS

  7. Latency

  8. Latency: Byte Times

  9. Energy Test Setup • Single mote transmitting a packet • Measure voltage drop with oscilloscope

  10. Energy +3% +10%

  11. Bandwidth Test Setup • Vary number of senders • Each sender sends as fast as it can • Measure number of packets successfully received in a time period

  12. Bandwidth TinySec-Auth: same throughput TinySec-AE: 6% less throughput

  13. Performance Summary

  14. TinySec Status • New version working with 1.1.3 stack • To use: TINYSEC=true • Suggestion: base new stacks off of TinySec stack

More Related