[Nfd-dev] NFD combine management protocols

[Alex Afanasyev]

On Mar 13, 2014, at 4:32 PM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:

> Dear folks
> 
> NFD is having too many protocols for management.
> This proposal is to combine most of these into a single "NFD Management protocol".
> 
> Changes
> "NFD Management protocol" only contains commands that can alter forwarder state.
> Every command is signed.
> Face Status protocol and FIB Enumeration protocol are not part of this protocol, and will be kept separate.
> The semantics of all commands are unchanged.
> The encoding of requests has a small change:
> FaceManagementOptions, FibManagementOptions, StrategyChoiceOptions are combined into one type
> Existing code just needs to use reassigned TLV-TYPE numbers
> LocalControlHeader enabling protocol has a syntax change: /localhost/nfd/control-header/enable|disable/<options>
> One or more control modules can be indicated in ControlCommandOptions block
> New documentation
> The documentation of "NFD Management protocol" would have the following sections:
> Control Command
> "Control Command" is used by commands that can alter forwarder state.
> request format: /localhost/nfd/<management-module>/<command-verb>/<options>/<timestamp>/<random-value>/<SignatureInfo>/<SignatureValue>
> authentication: a link to [[Command Interests]]
> options: definition of ControlCommandOptions block
> status dataset
> This section describes how to segment a collection of status blocks (FaceStatus blocks in Face Status protocol, FibEntry blocks in FIB Enumeration protocol), and how these segments are named
> Notification mechanism
> Forwarder Status protocol
> returns global counters
> Face Management protocol
> uses: Control Command, status dataset (for status), Notification mechanism (for status change notification)
> LocalControlHeader Enabling protocol
> uses: Control Command
> FIB Management protocol
> uses: Control Command, status dataset (for enumeration)
> Strategy Choice protocol
> uses: Control Command
> 
> Local Control Header will still have its own page which describes the format of the header. Enabling protocol is linked to the section in "NFD Management protocol".

Are you planning to have a huge page that describes all management protocols?  I'm not quite sure that it would be right... I prefer keeping specs as separate pages (with proper link to "parent"), not just sections in a big document (it is already quite challenging to navigate within each spec).

--
Alex


> 
> Please give your feedback.
> 
> Yours, Junxiao
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20140313/c38c74aa/attachment.html>