PrefixAnnouncement » History » Version 3
Junxiao Shi, 08/15/2018 06:17 PM
1 | 1 | Junxiao Shi | # Prefix Announcement Protocol |
---|---|---|---|
2 | |||
3 | The **prefix announcement protocol** allows registering prefixes using a *prefix announcement object*. It is an alternative to NFD [[RibMgmt|RIB Management protocol]]'s `rib/register` verb. |
||
4 | |||
5 | ## Prefix Announcement object |
||
6 | |||
7 | 2 | Davide Pesavento | The **prefix announcement object** is a Data packet that represents an application's intent of registering a prefix toward itself. A Data packet that satisfies the following requirements is a prefix announcement object: |
8 | 1 | Junxiao Shi | |
9 | 3 | Junxiao Shi | * Name starts with the announced prefix, followed by a fixed `prefix-announcement` generic name component, followed by a version component and a segment component as defined by the NDN Naming Conventions. In this specification revision, segment number is always zero. |
10 | 1 | Junxiao Shi | * ContentType is "prefix announcement". |
11 | 3 | Junxiao Shi | * Content contains a sequence of TLV elements, including at least an ExpirationPeriod element. Ordering of these TLV elements is insignificant. Unrecognized non-critical TLV elements are permitted and will be ignored. |
12 | 1 | Junxiao Shi | |
13 | 3 | Junxiao Shi | **Validity period** of a prefix announcement object is given in ExpirationPeriod and ValidityPeriod elements in its Content. |
14 | 1 | Junxiao Shi | |
15 | 3 | Junxiao Shi | * ExpirationPeriod gives the duration for which the prefix announcement remains valid. The duration begins when a node or program receives the prefix announcement. This element is required. |
16 | * ValidityPeriod gives the absolute time range in which the prefix announcement remains valid. It is ignored if the receiving node does not have a UnixTime clock. This element is optional. |
||
17 | * When both ValidityPeriod and ExpirationPeriod are present, the most restricted constraint applies. |
||
18 | 1 | Junxiao Shi | |
19 | Trust model of prefix announcement is to be defined by the application. |
||
20 | 3 | Junxiao Shi | |
21 | ### Example |
||
22 | |||
23 | ``` |
||
24 | Data |
||
25 | Name /net/example/prefix-announcement/%FD%01/%00%00 |
||
26 | MetaInfo |
||
27 | ContentType "prefix announcement" |
||
28 | Content |
||
29 | ValidityPeriod |
||
30 | NotBefore 20181030T000000Z |
||
31 | NotAfter 20181124T235959Z |
||
32 | ExpirationPeriod 3600000 |
||
33 | SignatureInfo |
||
34 | SignatureValue |
||
35 | ``` |
||
36 | |||
37 | This prefix announcement object announces the prefix `/net/example`. |
||
38 | It is valid for one hour since receipt, within the date range 30OCT2018 and 24NOV2018. |
||
39 | 1 | Junxiao Shi | |
40 | ## Command Verbs |
||
41 | |||
42 | ### 'announce' |
||
43 | |||
44 | This command announces a prefix using a prefix announcement object. |
||
45 | NFD-RIB accepts this command as a [[ndn-cxx:CommandInterest|Command Interest]] with the following syntax: |
||
46 | |||
47 | ``` |
||
48 | /localhost/nfd/rib/announce/<params-sha256>/<command-interest-components> |
||
49 | /localhop/nfd/rib/announce/<params-sha256>/<command-interest-components> |
||
50 | ``` |
||
51 | |||
52 | 2 | Davide Pesavento | The Interest's Parameters element carries the prefix announcement object. |
53 | 1 | Junxiao Shi | |
54 | NFD-RIB converts this command into an equivalent `rib/register` command. Route *origin* is set to "prefix announcement" (number 129). |
||
55 | 2 | Davide Pesavento | Response is the same as `rib/register` command. |
56 | 1 | Junxiao Shi | |
57 | ### 'unannounce' |
||
58 | 2 | Davide Pesavento | |
59 | 1 | Junxiao Shi | There is no 'unannounce' command. Instead, use `rib/unregister` command. |