Ask Your Question


asked 2014-10-02 13:04:53 -0800

vmetodiev gravatar image


My name is Varban and I am really glad to see this project coming to life!

Can you explain me how the development cycle will be conducted? How will this idea merge with the existing hardware architectures that can be exposed for packet processing, storage compression/encryption and signal processing (I mean DPDK, OpenCL, Tilera, FPGAs and so on)?

Also, it is possible to include "software defined radio" in some future time ?

And my last question - since I am a university student with no serious programming experience, what are my chances to become a contributor as software development is concerned?

Regards, Varban

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2014-10-05 22:25:25 -0800

Hi Varban,

The way one can see NFV would be as a framework governing the SDN components or even at the service levels [Network/ cloud/ Service Provider]. It might take a while for NFV itself to mature as it is still in its infancy.

I am unsure if s/w defined Radio would really materialize for the consumer market as radio is core hardware and the way I see it and would have a very high cost of implementation and specific skill sets. We have different radio frequencies for different kind of applications based on speed, distance, priority, etc. Currently ' The Internet' aims at providing the data in a unified approach substituting much for the s/w based radio definition.

Do check for the ETSI-NFV publications and check out your interest as this is a field expanded from and with the cloud for SDN among other pros.


edit flag offensive delete link more

answered 2014-10-06 07:30:25 -0800

vmetodiev gravatar image

Hello Praneeth,

Thank you for your answer and the ETSI-NFV reference. I have gone through the documentation and what I find interesting, according to the Use Cases paper, are the "network functions virtualisation IaaS" and "VNF forwarding graph" topics.

I am thinking of a high-level language for network topology programming (matches, actions, etc.) - something like the OpenFlow protocol, but with wider range of features . (from OSI L2 to L7 - for the telecoms)

Another feature would be a FUSE-based parallel filesystem, operating at the lower OSI levels for utilization of all the available ethernet links. (For the entreprise)

Regards, Varban

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

1 follower


Asked: 2014-10-02 13:04:53 -0800

Seen: 1,322 times

Last updated: Oct 06 '14