Nick Gordon | f3a9ecb | 2017-01-24 13:55:14 -0600 | [diff] [blame] | 1 | \documentclass[10pt]{article} |
| 2 | |
| 3 | \usepackage[margin=0.5in,bottom=.7in,top=.8in]{geometry} |
| 4 | \usepackage{graphicx}\graphicspath{{figures/}} |
| 5 | \usepackage[usenames,dvipsnames]{xcolor} |
| 6 | \usepackage[colorlinks=true,citecolor=Mahogany,linkcolor=Mahogany,urlcolor=Mahogany,filecolor=Mahogany]{hyperref} |
| 7 | \usepackage{breakurl} |
| 8 | \usepackage{url} |
| 9 | \usepackage[nocompress]{cite} |
| 10 | \usepackage{paralist} |
| 11 | \usepackage{authblk} |
| 12 | \usepackage{enumitem} |
| 13 | \usepackage{multirow} |
| 14 | |
| 15 | \title{NLSR Developer's Guide} |
Ashlesh Gawande | 6990347 | 2017-06-28 13:30:46 -0500 | [diff] [blame] | 16 | \author[1]{Vince Lehman, Muktadir Chowdhury, Nicholas Gordon, Ashlesh Gawande} |
Nick Gordon | f3a9ecb | 2017-01-24 13:55:14 -0600 | [diff] [blame] | 17 | |
| 18 | \affil[1]{University of Memphis} |
| 19 | |
| 20 | %\date{NFD Team} |
| 21 | |
| 22 | \usepackage{fancyhdr} |
| 23 | \pagestyle{fancy} |
| 24 | |
| 25 | |
| 26 | \usepackage{eso-pic,xcolor} |
| 27 | \makeatletter |
| 28 | \AddToShipoutPicture*{% |
| 29 | \setlength{\@tempdimb}{20pt}% |
| 30 | \setlength{\@tempdimc}{\paperheight}% |
| 31 | \setlength{\unitlength}{1pt}% |
| 32 | %\put(\strip@pt\@tempdimb,\strip@pt\@tempdimc){% |
| 33 | % \makebox(0,-60)[l]{\color{blue}% |
| 34 | %NDN, Technical Report NDN-0021. \url{http://named-data.net/techreports.html}} |
| 35 | % }% |
| 36 | } |
| 37 | \makeatother |
| 38 | |
| 39 | |
| 40 | \begin{document} |
| 41 | \maketitle |
| 42 | |
| 43 | \begin{abstract} |
| 44 | The Named Data Link-State Routing Protocol (NLSR) is a Named Data Networking (NDN) routing protocol that populates NDN Forwarding Daemon's (NFD) Routing Information Base (RIB). |
| 45 | The main design goal of NLSR is to provide a routing protocol to populate NFD's RIB and Forwarding Information Base (FIB). |
| 46 | NLSR calculates the routing table using link-state or hyperbolic routing and produces multiple faces for each reachable name prefix in a single authoritative domain. |
| 47 | NLSR will continue to evolve alongside the NDN protocol, NFD, and ndn-cxx. |
| 48 | This document is meant to explain the design of NLSR including major module and data structures descriptions and the interactions between those components. |
| 49 | |
| 50 | \end{abstract} |
| 51 | |
| 52 | \tableofcontents |
| 53 | \clearpage |
| 54 | |
| 55 | \input{intro} |
| 56 | \clearpage |
| 57 | \input{hello-protocol} |
| 58 | \clearpage |
| 59 | \input{sync-logic} |
| 60 | \clearpage |
| 61 | \input{lsas} |
| 62 | \clearpage |
| 63 | \input{lsdb} |
| 64 | \clearpage |
| 65 | \input{routing-table} |
| 66 | \clearpage |
| 67 | \input{npt} |
| 68 | \clearpage |
| 69 | \input{fib} |
| 70 | \clearpage |
Nick Gordon | 221531c | 2017-06-08 11:44:45 -0500 | [diff] [blame] | 71 | \input{prefix-update} |
| 72 | \clearpage |
| 73 | \input{nfd-rib-command-processor} |
| 74 | \clearpage |
| 75 | \input{lsdb-status-dataset} |
| 76 | \clearpage |
Nick Gordon | f3a9ecb | 2017-01-24 13:55:14 -0600 | [diff] [blame] | 77 | \input{security} |
| 78 | \clearpage |
| 79 | \input{configuration} |
| 80 | \clearpage |
| 81 | |
| 82 | \phantomsection |
| 83 | \addcontentsline{toc}{section}{References} |
| 84 | |
| 85 | \bibliographystyle{IEEEtran} |
| 86 | \bibliography{nlsr} |
| 87 | |
| 88 | \end{document} |