Virality based content caching in NFV framework: Difference between revisions
| Line 21: | Line 21: | ||
== PoC Proposal == | == PoC Proposal == | ||
[http://docbox.etsi.org/ISG/NFV/PER/05-CONTRIBUTIONS/2014/NFVPER(14)000075a1_Virality_based_content_caching_in_NFV_framework_-_v2.doc NFVPER(14)000075a1_Virality_based_content_caching_in_NFV_framework_-_v2.doc] | [http://docbox.etsi.org/ISG/NFV/PER/05-CONTRIBUTIONS/2014/NFVPER(14)000075a1_Virality_based_content_caching_in_NFV_framework_-_v2.doc NFVPER(14)000075a1_Virality_based_content_caching_in_NFV_framework_-_v2.doc] | ||
Updated proposal (23/10/2014): [http://docbox.etsi.org/ISG/NFV/PER/05-CONTRIBUTIONS/2014//NFVPER(14)000075a3_Virality_based_content_caching_in_NFV_framework.doc /NFVPER(14)000075a3_Virality_based_content_caching_in_NFV_framework.doc] | |||
Revision as of 09:04, 24 October 2014
PoC Team
BT
Telefonica
Brocade
IBM Research
AMD
Main Contact
Ram (Ramki) Krishnan, Brocade ramk@brocade.com
PoC Demo
Brocade Communications Systems, Inc. San Jose, California, USA (additionally in IBM Research Lab, India)
IETF 92, March 2015, Dallas, TX, USA
PoC Proposal
NFVPER(14)000075a1_Virality_based_content_caching_in_NFV_framework_-_v2.doc
Updated proposal (23/10/2014): /NFVPER(14)000075a3_Virality_based_content_caching_in_NFV_framework.doc