Project

General

Profile

Actions

Feature #1216

closed

V2V communication

Added by Alex Afanasyev almost 11 years ago. Updated about 1 year ago.

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

100%

Estimated time:
(Total: 0.00 h)

Description

Develop modules specific to vehicular networks.

Related literature:

Previous implementation, now obsolete: https://github.com/named-data/vndn (see also the paper VANET via Named Data Networking)


Subtasks 3 (0 open3 closed)

Feature #1217: V2V WiFi faceAbandoned

Actions
Feature #1218: V2V LinkServiceAbandoned

Actions
Feature #1219: V2V Location ServicesAbandoned

Actions
Actions #1

Updated by Junxiao Shi almost 11 years ago

  • Subject changed from V2v face implementation to V2V communication
  • Description updated (diff)
  • Category set to Faces
  • Assignee set to Davide Pesavento
Actions #2

Updated by Junxiao Shi almost 11 years ago

I'm not quite sure whether different forwarding pipelines are required for vehicular networks, or it's just a strategy.

The difference is: strategy can make decision on Interest forwarding only, while forwarding pipelines have more flexibility (but it's also much more work).

Assignee of this parent task should present a design and discuss with team.

Actions #3

Updated by Alex Afanasyev almost 9 years ago

  • Description updated (diff)
Actions #4

Updated by Davide Pesavento almost 9 years ago

  • Description updated (diff)
Actions #5

Updated by Davide Pesavento almost 7 years ago

  • Category deleted (Faces)
  • Assignee deleted (Davide Pesavento)
Actions #6

Updated by Davide Pesavento about 1 year ago

  • Tracker changed from Task to Feature
  • Status changed from New to Abandoned
Actions

Also available in: Atom PDF