NFD

I'll write this section because I'm the primary designer of these features.

Implementors should contribute their experiences in different transports and link service features.

As I agreed in 20160106 conference call, I'll fill in the "static properties" paragraphs.

After that, this will be re-assigned to Eric for adding more details.

I've completed my edits. Eric's tasks are split to #3395 #3396 #3397.

From Alex's suggestions:

order of transports should be: internal, unix, ethernet, udp unicast, udp multicast, tcp, websocket, dummy

This is already completed, except that DummyTransport is moved to "testing" section.

Remove references to old face system
Finalize description of transports (udp unicast, udp multicast, ethernet, internal, dummy)
Generic link service description.
face system (2.3): ProtocolFactory, Channel, workflow(?)
remove old face system (section 3), moving elements to section 2: Protocol Factory, Channel

These are moved to one of the follow-up tasks.

Maybe we should not mention “planned” features and services

I disagree with this. Roadmap can be included in devguide.

“developing a new link service” section (2.3.3). Should be called “Extending NFD Face System”

No. Both LinkService and Transport can be extended, and they are in different sections.

moving elements to section 2: FaceUri

This is already covered in sections of each Transport. It's intentional not to have a big table, because a table with just the FaceUri but not other properties is incomplete.
Such a table already exists in FaceMgmt page and there's no reason to duplicate it.

tables (4.2, network regions table). We may need to add more details and references

This is unrelated to face system. Alex may reopen #3159 with a detailed suggestion on what is to be added.