OK. So here's my take on this (and check out the proposal for the relay README too). How about simply:


This application is a showcase of the CCN capabilities in RIOT. 

The example consists in two parts: clients and relays.

This documents the client functionalities.

A client opens a shell to enable the following:

- start the CCN stack: The command "ccn X" starts the CCN stack and sets the content store size to X

- publishing content: Two alternative ways are defined to do that. 
      - Way 1: pre-provision the cache with X dummy chunks with the command "populate"
      - Way 2: start a server application with the command "appserver". This application starts a thread to answer to interests. When the server is started, it will register a prefix to the stack. The server will reply to interests for content with the name /riot/appserver/test.
      
- subscribing to receive content: the command "interest" fetches a remote file through the CCN network stack. This starts a user land application, which creates an interest message and routes this message hop by hop towards the publisher of the content using the CCN stack.