Project

General

Profile

Actions

Feature #3400

closed

NFD feature planning

Added by Alex Afanasyev almost 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
0.00 h

Description

This issue tracks the feature planning process for NFD and ndn-cxx version 0.5 and beyond.


Related issues 1 (0 open1 closed)

Related to NFD - Task #3385: Release 0.4.1ClosedAlex Afanasyev

Actions
Actions #1

Updated by Alex Afanasyev almost 9 years ago

Actions #2

Updated by Junxiao Shi almost 9 years ago

  • Subject changed from NFD feature planning to NFD 0.5 feature planning
  • Description updated (diff)
  • Target version set to v0.5
  • Estimated time set to 0.00 h

Original description posted by Alex:

Jan 7, 2016 call has discussed several direction for future features. These include:

  • Performance optimizations

    Primary target scenario: big data science

    • Understanding bottlenecks and planning on how to improve

      • table lookup
      • repo
      • congestion control
      • performance measurements of current code
    • white-box measurements of individual components

    • analysis of components, depending on traffic pattern

  • Expand (actively) supported platforms

    Mobile and embedded devices, such as home router (WRT), mobile phones

  • Strategy / forwarding related improvements

    Need to think how to make it more powerful / flexible

    one strategy (per router) that takes input from routing annotations

    How strategy makes decision, it is still up to the strategy (whether
    or not to probe, take or not input from routing, take or not and how
    input from data place, etc.). This is not something that routing
    annotations can help.

  • Link-level loss detection + recovery

    this feature can affect strategy (or effect may not be much)

  • Hop-by-hop congestion control

    • how it can work in overlay network
    • how to know bandwidth to use to control interest budget
Actions #3

Updated by Junxiao Shi almost 9 years ago

20160112 conference call puts more major issues in 0.5 timeline:

protocol

  • #3333 Interest digest
  • #2520 NDNLPv2 failure detection, reliability
  • #1285 tunnel authentication
  • #3408 mobility with Kite

Note: An issue in this category refers to protocol design. Implementation may be scheduled after 0.5.

core

  • #2513 multi-threaded logging

face

  • #3167 permanent TcpTransport
  • UP/DOWN semantics, after #2520 supplies the design for failure detection

management

  • #3274 #2182 InMemoryStorage for management
  • #1712 FaceManager whitelist+blacklist for multicast face creation

tables

  • performance benchmark in tables, design faster data structures

forwarding

  • #3161 #3163 put Link in CS index
  • #3162 put Link in PIT index; or reject this and switch to Interest digest, depending on outcome of #3333

integration tests

  • #3336 run integ in Mininet; later, trigger it from Jenkins
  • add more scenarios
Actions #4

Updated by Jeff Burke almost 9 years ago

It would be great to see congestion control support coordinated (for motivation, testing, etc.) with NDN-RTC, where it would be immediately useful.

Actions #5

Updated by Anonymous almost 9 years ago

Certificate format 2.0 planned for NFD 0.5?

Actions #6

Updated by Davide Pesavento almost 7 years ago

  • Subject changed from NFD 0.5 feature planning to NFD feature planning
  • Target version deleted (v0.5)
Actions #7

Updated by Junxiao Shi almost 7 years ago

  • Has duplicate Task #4395: Provide NFD Roadmap(s) added
Actions #8

Updated by Alex Afanasyev almost 7 years ago

  • Has duplicate deleted (Task #4395: Provide NFD Roadmap(s))
Actions #9

Updated by Davide Pesavento over 6 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF