| Nick Gordon | f3a9ecb | 2017-01-24 13:55:14 -0600 | [diff] [blame] | 1 | \section{Prefix Update Processor} |
| 2 | \label{sec:prefix-update} |
| Nick Gordon | 221531c | 2017-06-08 11:44:45 -0500 | [diff] [blame^] | 3 | |
| 4 | The Prefix Update processor allows manipulation of NLSR's advertised |
| 5 | name prefixes with ordinary ControlCommands. Such commands may |
| 6 | originate from something like \texttt{nlsrc}, the command line tool |
| 7 | for manipulating NLSR. |
| 8 | |
| 9 | \subsection{Advertising and Withdrawing Routes} |
| 10 | The processor accepts valid ControlCommands that are signed by the site operator's key. Additionally, the commands must be received on the \texttt{/localhost/nlsr/prefix-update/} prefix. The full condition list is specified in the validator rules in the configuration file. |
| 11 | |
| 12 | The processor will send responses to commands. |
| 13 | |
| 14 | \subsection{Security} |
| 15 | Prefix Update commands are similar to NFD RIB commands, but with one |
| 16 | additional requirement, so they are more secure. In addition to being |
| 17 | on the root-only \texttt{/localhost/} prefix, Prefix Update commands |
| 18 | must be signed by the site operator's key. If the site operator's key |
| 19 | were compromised, an attacker could create any number of NLSRs that |
| 20 | impersonate the legitimate NLSR running at that site. |