"The modern service provider and data center networks demand cloud delivery model for agile and cost-effective rollout of services for revenue generation. There are some proposals to incorporate service insertion in the emerging SDN and NFV environments. However, the current methods are sub-optimal, complex and inflexible in delivering automated end-to-end service delivery.
In a virtualized cloud environment, service delivery requires intelligence in the network for policy-based traffic handling and differentiated services. Dynamic service chaining is a fundamental component in building an on-demand and scalable model for policy enforcement. This session will cover following topics:
1. NFV & Service chaining use cases
2. Challenges with existing solutions
3. Opportunities with dynamic service chaining
4. Policy Enforcement model in SDN/NFV environment
5. Dynamic Service Chaining Architecture & Design considerations
6. Benefits of Dynamic Service Chaining"
See more at: https://www.nanog.org/meetings/abstract?id=2595#sthash.a7BOBUqX.dpuf
Notes:
Need a "Service Plane" along with Data, Control, Mgmt planes
Proposes service abstraction from OpenDaylight or OpenStack
Policy Identifier / Subscriber ID is carried as metadata in yet another packet header.
Three mechanisms being discussed:
1. labeling with TCP options extensions (limited, not much uptake)
2. Network Service Header (NSH) (getting traction with big vendors)
3. Application-specific header (HTTP header extensions) (easier to deploy and happening first)
Create this policy-based service overlay, but how is it forwarded?
VXLAN, BGP community - various ideas being debated
Can use "Segment routing" - steering traffic to an ordered set of routers
No comments:
Post a Comment