• Home
  • Who Am I ?
    • Contact
    • What does Ethereal Mind mean ?
  • Disclosure
    • Disclaimer
    • Comment Policy
    • Privacy Policy
  • Just Three
  • Archive

EtherealMind

Software Defined & Intent Based Networking

You are here: Home / Research: Fabric: A Retrospective on Evolving SDN – Rereading

Research: Fabric: A Retrospective on Evolving SDN – Rereading

12th April 2018 By Greg Ferro Filed Under: Blog Leave a Comment

I was rereading ‘Fabric: A Retrospective on Evolving SDN’ research paper by Martin Casado from 2012 which discusses the limitations of an SDN based on OpenFlow. This description of three network interfaces jumped out at me:

Like any system, networks can be thought of in terms of interfaces; here we use that term not to refer to a formal programmatic interface, but to mean more generally and informally places where control information must be passed between network entities. There are three relevant interfaces we consider here:

Host — Network: The first interface is how the hosts inform the network of their requirements; this is typically done in the packet header (for convenience, in the following we will focus on L3, but our comments apply more generally), which contains a destination address and (at least theoretically) some ToS bits. However, in some designs (such as IntServ), there is a more explicit interface for specifying service requirements.

Operator — Network: The second interface is how operators inform the network of their requirements; traditionally, this has been through per-box (and often manual) configuration, but SDN (as we discuss later) has introduced a programmatic interface.

Packet — Switch: The third interface is how a packet identifies itself to a switch. To forward a packet, a router uses some fields from the packet header as an index to its forwarding table; the third interface is the nature of this index.

I think I’ve forgotten the reality that host/network interface is key to network operation and that this three

This design structure is then used to highlight a key area of MPLS, namely the addition of yet another control plane that separates the core and network edge:

MPLS introduced an explicit distinction between the network edge and the network core. Edge routers inspect the incoming packet headers (which express the host’s requirements as to where to deliver the packet) and then attach a label onto the packet which is used for all forwarding within the core.

Fabric-network-using-mpls

However, MPLS did not formalize the interface by which operators specified their control requirements. Thus, MPLS distinguished between the Host-Network and Packet-Switch interfaces, but did not develop a general Operator-Network interface.

References

Fabric: A Retrospective on Evolving SDN – http://yuba.stanford.edu/~casado/fabric.pdf) – Retrieved 5 Sep, 2017

About Greg Ferro

Human Infrastructure for Data Networks. 25 year survivor of Corporate IT in many verticals, tens of employers working on a wide range of networking solutions and products.

Host of the Packet Pushers Podcast on data networking at http://packetpushers.net- now the largest networking podcast on the Internet.

My personal blog at http://gregferro.com

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Network Break Podcast

Network Break is round table podcast on news, views and industry events. Join Ethan, Drew and myself as we talk about what happened this week in networking. In the time it takes to have a coffee.

Packet Pushers Weekly

A podcast on Data Networking where we talk nerdy about technology, recent events, conduct interviews and more. We look at technology, the industry and our daily work lives every week.

Our motto: Too Much Networking Would Never Be Enough!

Find Me on Social Media

  • Facebook
  • Instagram
  • Linkedin
  • RSS
  • Twitter
  • YouTube

Return to top of page

Copyright Greg Ferro 2008-2017 - Thanks for reading my site, it's been good to have you here.

Opinions, Views and Ideas expressed here are my own and do not represent any employer, vendor or sponsor.Full disclosure