While looking this draft over, I was concerned about the relationship
between Network Function Virtualization (NFV) and SDN, and whether the
proposal meant that the IETF would be working on a regional model (ETSI
oriented) which overlapped with models being developed and implemented
by other organizations. Checking out the web for background information
(couldn't find the cited ETSI references), I found this nice comparison
table. I reproduce it from Prayson Pate's blog at
http://www.overturenetworks.com/blog/tags/network-function-virtualization
with kind permission of Overture. If it represents the general
understanding of the relationship between the two technologies, my
concerns are met.
As a general comment, the subject area proposed seems huge. I imagine
any charter items would be scoped much more narrowly, so it's a question
of figuring out priorities.
Tom Taylor
Basic Concept
SDN Separate control and data, centralize control
and programmability of network
NFV Relocate network functions from dedicated
appliances to generic servers
Target Location
SDN Campus, data center / cloud
NFV Service provider network
Target Device
SDN Commodity servers and switches
NFV Same
Initial Applications
SDN Cloud orchestration and networking
NFV Routers, Firewalls, gateways, CDN,
WAN accelerators, SLA assurance
New Protocols
SDN OpenFlow
NFV None
Formalization
SDN Open Networking Foundation (ONF)
NFV ETSI NFV Working Group
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
