| Davide Pesavento | 4d82692 | 2018-02-11 23:05:48 -0500 | [diff] [blame^] | 1 | .. _local-prefix-discovery: |
| 2 | |
| 3 | Local hub prefix discovery |
| 4 | ========================== |
| 5 | |
| 6 | Some applications need to discover the prefix(es) under which they can publish data |
| 7 | / which Interests the local hub will be able to forward down to the application. |
| 8 | In order to discover that, applications need to send an Interest for |
| 9 | ``/localhop/nfd/rib/routable-prefixes`` prefix. Response data to the |
| 10 | Interest contains a list of prefixes and should be encoded as follows: |
| 11 | |
| 12 | :: |
| 13 | |
| 14 | Response ::= DATA-TYPE TLV-LENGTH |
| 15 | Name (= /localhop/nfd/rib/routable-prefixes/[version]/[segment]) |
| 16 | MetaInfo (= ResponseMetaInfo) |
| 17 | Content (= ResponseContent) |
| 18 | Signature |
| 19 | |
| 20 | ResponseMetaInfo ::= META-INFO-TYPE TLV-LENGTH |
| 21 | ContentType (= BLOB) |
| 22 | FreshnessPeriod (= 5000) |
| 23 | |
| 24 | ResponseContent ::= Name+ |
| 25 | |
| 26 | .. note:: |
| 27 | ResponseContent should contain at least one ``Name``, which should be routable |
| 28 | towards the face from which the request has been received. The requester may |
| 29 | process the list of returned names and pick whichever it wants to use. |
| 30 | |
| 31 | For now, the ``/localhop/nfd/rib/routable-prefixes`` data is served by |
| 32 | :ref:`ndn-autoconfig-server`. |