[Nfd-dev] NFD breaking change: TCP transport

[Junxiao Shi]

Dear folks

A breaking change is coming to NFD soon: LocalControlHeader is no longer
supported on TCP transport.
This change will merge after Nov 01 12:00 UTC.

If your application or library connects to the local NFD via TCP tunnel and
uses one of the LocalControlHeader feature, it will stop working after this
change.

To fix your application or library: use the equivalent NDNLPv2
<http://redmine.named-data.net/projects/nfd/wiki/NDNLPv2> feature.
For now, faces/enable-local-control ControlCommand is still supported, but
calling this command enables all LocalControlHeader-equivalent features
(i.e. all of IncomingFaceId, NextHopFaceId, CachePolicy), and the packet
format would be NDNLPv2 instead of LocalControlHeader.
Even if your application does not use LocalControlHeader previously, it may
start receiving NDNLPv2 packets if an Interest brings back a Nack packet.

You can test your projects with NFD Change http://gerrit.named-data.net/2495
and verify it works.

Yours, Junxiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20151027/44bcf91a/attachment.html>