[Nfd-dev] review request: NDNLPv2 NACK, Fragmentation, LocalControlHeader

[Junxiao Shi]

Hi Dave

Enabled features can be set at compile time, in the configuration file, or
through management commands.

Defaults for NFD are:

   - Ethernet multicast and UDP multicast: indexed fragmentation, network
   NACK
   - UDP unicast: indexed fragmentation, network NACK
   - TCP: network NACK
   - TCP local and UNIX socket: network NACK, local cache policy
      - turn on with management command: consumer controlled forwarding,
      incoming face indication


There is no handshake because the receiver needs to know what NDNLPv2
features are enabled when processing the handshake packet.
However, since NDNLPv2 features can be controlled through management
commands, it's possible to determine an initial set of enabled features at
compile time or in the configuration file, and then change the features
during runtime. This has a similar effect of handshake, because a
management command can be sent from a remote node. For example, an end host
can send a command "on my face, disable indexed fragmentation and enable
B-E fragmentation" to the router, and the next packet will use the new
fragmentation feature; but those packets transmitted prior to the command
and received afterwards would be processed incorrectly and likely got
dropped.

Yours, Junxiao

On Thu, Jun 11, 2015 at 4:32 AM, Dave Oran (oran) <oran at cisco.com> wrote:

> > The protocol in charge is determined by the link, not determined by
> every packet.
> > Before an NDNLPv2 packet is processed, the receiver already knows what
> features are enabled.
> How? Not by hand on each end I hope? No initialization handshake?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150611/6a177f5c/attachment.html>