1 / 7

SFC DC Use Cases draft-kumar-sfc-dc-use-cases IETF 89, London

SFC DC Use Cases draft-kumar-sfc-dc-use-cases IETF 89, London. Mudassir Tufail Citi. Surendra Kumar Cesar Obediente Cisco Systems, Inc. Objective Provide requirements for evolving SFC architecture in datacenters. Demonstrate via general DC use cases, the need for an SFC architecture that

brody
Download Presentation

SFC DC Use Cases draft-kumar-sfc-dc-use-cases IETF 89, London

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SFC DC Use Casesdraft-kumar-sfc-dc-use-casesIETF 89, London Mudassir Tufail Citi Surendra Kumar Cesar Obediente Cisco Systems, Inc.

  2. ObjectiveProvide requirements for evolving SFC architecture in datacenters • Demonstrate via general DC use cases, the need for an SFC architecture that • Supports hybrid datacenters • Frees SF deployment from topology • Enables end-to-end metadata passing thru SFC • Enables flexible multi-tenancy models • Allows for building composite SFCs from sub SFCs • Supports SF/C capacity scale-out IETF 89, London | SFC DC Use Cases

  3. TrafficTypes & TopologyEmerging DCs are designed for scale, performance and resilience • North-South traffic • Branch Office, Remote Worker • Tenant • East-West traffic - predominant traffic! • Three-tier: Web, App, DB • External storage access, VM migration • Mobile (Gi-LAN) • Subscriber IETF 89, London | SFC DC Use Cases

  4. Service Nodes/FunctionsEmerging Service Functions on commodity hardware & virtual form factor • Physical vs. Virtual Service Nodes • Service Nodes vs. Service Functions • FW: ACL, Inspection, VPN, NAT, … • SN Instances vs. SF Instances • Inspection@FW5 vs. Inspection5 • Build SFCs with static or dynamic selection • Need SF-type1 from FW-type3: resolve dynamically • Need SF-type1 from FW-type3-instance-pool • Need SF-type1@FW-type3-instance5 IETF 89, London | SFC DC Use Cases

  5. Typical Service Function ChainsShare the same service functions across different service chains WL • Access SFCs • Service traffic entering/exiting DC • One per tenant • Application SFCs • Service traffic destined to Apps • Many per tenant • Need a combination of SFCs • App SFCs alone for north-south ACCESS SFC RTR WOC eFW MON sFW APP SFC ADC ADC ADC MON MON MON aFW aFW aFW WL WL WL IETF 89, London | SFC DC Use Cases web app db

  6. Traditional Method InadequaciesStatic, rigid, complex methodologies can’t serve dynamic environments • VLAN stitching is no longer a Panacea • PBR does not help either • Source NAT need not be a requirement • Capacity scaling is non existent/complex • Tenant ID cannot be tied to topology • Absolutely no metadata capability • Mixing virtual and physical SFs is problematic IETF 89, London | SFC DC Use Cases

  7. Next StepsAdoption of this draft … • Authors would like to • Solicit feedback/comments • Add more use cases • See the requirements become architecture guides • Request a WG doc for DC Use Cases IETF 89, London | SFC DC Use Cases

More Related