NLSR

NLSR Routing Status Page

========================

### System Overview

The system is consisted of the following components:

- Consumer (Browser)

- Producer (Websocket Proxy, NFD, NLSR)

### Interaction among components

Client's browser will send interest for NLSR status of a remote node over WebSocket connection to the WS Proxy that is running on remote node. Remote node's Websocket Proxy will receive the request on port 9696 and forward the decapsulated NDN packet to local NFD over TCP/UDP connection. NFD will, then, send the interest to local NLSR requesting status data. Upon receiving status data from NFD, WebSocket Proxy encodes the packet into WebSocket frame before forwarding it the to the Client (browser). The WebSocket proxy also takes care of NDN packet fragmentation and reassembly. This [**diagram**](http://redmine.named-data.net/attachments/download/390/NLSR%20Status%20diagram) shows the interaction among different components of the system:

### Data that will be displayed on Webpage

The current NLSR status page displays Name LSA and Adjacency LSA of [**LSDB Dataset**](http://redmine.named-data.net/projects/nlsr/wiki/LSDB_DataSet). In addition to that, Coordinate LSA information will also be displayed in the Webpage.

User will be able to request any of the Name LSA, Adjacent LSA, Coordinate LSA, and all LSAs in the LSDB of a particular node.

### Operations

All LSAs, Name, Adjacency and Coordinate, are published as [**LSDB Dataset**](http://redmine.named-data.net/projects/nlsr/wiki/LSDB_DataSet). LSDB datasets are published under the namespace ```ndn:/<router-name>/lsdb/```.

#### Consumer

1. If consumer wants to request Name LSA status dataset then it will send an Interest ```ndn:/<router-name>/lsdb/names```. 

2. Wait for a Data; if no Data arrives, fail.

#### Producer

1. Listen on prefix ```ndn:/<router-name>/lsdb/```

2. Upon receiving an Interest, send the data.