1 / 10

Software Driven Networks BoF

Software Driven Networks BoF. IETF 82 Taipei Lou Berger, Wes George – BoF chairs Adrian Farrel – Routing (that’s with an oo) AD Mailing list http://www.lucidvision.com/mailman/listinfo/sdnp. Note Well.

elwyn
Télécharger la présentation

Software Driven Networks BoF

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. Software Driven Networks BoF IETF 82 Taipei Lou Berger, Wes George – BoF chairs Adrian Farrel – Routing (that’s with an oo) AD Mailing list http://www.lucidvision.com/mailman/listinfo/sdnp

  2. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: • The IETF plenary session • The IESG, or any member thereof on behalf of the IESG • Any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices • Any IETF working group or portion thereof • Any Birds of a Feather (BOF) session • The IAB or any member thereof on behalf of the IAB • The RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879). Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice.  Please consult RFC 5378 and RFC 3979 for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.

  3. Agenda • Administrivia and Agenda Bash (Chairs) [10, 10/120] • Purpose of the meeting (AD) [5, 15/120] • SDN Problem Statement and Scenery (Tom/Ping/Dimitri) [15, 30/120]     draft-nadeau-sdn-problem-statement-01  • Relationship to other efforts - • ONF Introduction and Overview (Dave Ward) [10, 40/120]  • ONF & IETF (Dave Meyer) [10, 50/120]o • Use cases/Examples  • SDN: Use Cases and Framework  (DimitriStiliadis) [10, 60/120]     draft-stiliadis-sdnp-framework-use-cases-01   • SDN Use Case for Bandwidth on Demand Applications  (Shane Amante) [10, 70/120]     draft-pan-sdn-bod-problem-statement-and-use-case-01   • SDN Problem Statement and Use Cases for Data Center Applications  (Ping Pan) [10, 80/120]     draft-pan-sdn-dc-problem-statement-and-use-cases-01   • Cloud Bursting Use Case  (Dave McDysan) [10, 90/120]     draft-mcdysan-sdnp-cloudbursting-usecase-00

  4. Agenda • Use case / Scope discussion (Open) [15, 105/120] • Possible solutions/approaches  • Framework for Software Defined Networks  (Tom Nadeau) [0, 105/120]    draft-nadeau-sdn-framework-01  • Traffic classification, filtering and redirection for end-system IP VPNs.  (Pedro Marques) [0, 105/120]    draft-marques-sdnp-flow-spec-00  • A network operator's perspective (Shin Myung-Ki) [0, 105/120]  • Programmatic interface that can be used for VM virtualization  (Ping Pan) [0, 105/120]  • Identifying the work items (Open) [15, 120/120]  • Summary (Chairs/AD) [5, 125/120]

  5. BoF Objectives • Scope of SDN work within IETF • In scope • Out of scope • SDN vs SDN • Name change? • Gaps, existing solutions • Potential WG deliverables • Relationship with other groups

  6. Framing the Discussion(shamelessly stolen from L2VPN) • What is the problem? • Is the problem statement a good starting point? • What new work has to be done? • By “work” we don’t just mean create protocols • Do we agree IETF needs to work on this? • Not discussing which WG here and now! • Are we looking at a bottom-upor top-down problem? • xVPN up, or Net app down

  7. Where does SDN fit in? Network Applications SDN Controller Logic Plug-in #1 Plug-in #2 Plug-in #3 Network Resources Examples: IP/MPLS Control Plane, PBB/SPB, L2,L3VPN, OpenFlow, VXLAN NVO3 … Network Resources (VPN …) Network Resources (VPN …)

  8. SDN vs SDN • This is confusing • Name change is a good idea • Defined • Software/applications and interfaces whose sole purpose is to control a network's data plane • Driven • A software/applications interface for providing a network's control plane with the data plane (service) requirements and for receiving feedback on the service/treatment being delivered

  9. Scope In Scope • Your text goes here Out of Scope • And also here

  10. Potential WG Deliverables • This space for rent

More Related