OIF's Fabric Unification Isn't About the Fabric

If you're going to mash packet and OTN traffic together, why not make the line card do all the work?

Craig Matsumoto, Editor-in-Chief, Light Reading

December 8, 2011

2 Min Read
OIF's Fabric Unification Isn't About the Fabric

What's interesting about the Optical Internetworking Forum (OIF) 's unified packet/OTN switch fabric is that it doesn't actually create a new, unified switch fabric.

The implementation agreement for the OTN over Packet Fabric Protocol was published Wednesday morning on the OIF's website (PDF form). The idea is to use one switch fabric to handle packet and Optical Transport Network (OTN) traffic.

But the fabric in the specification is a normal packet fabric. The implementation puts all the work on the OTN line cards: They get modified to parcel OTN feeds into packets.

The whole idea is to save money for telecom equipment companies building transport gear, routers and switches. Systems can support OTN and packets without having two switch fabrics, says Winston Mok, the technical editor of the implementation agreement.

It seems this would also make the protocol easier to implement. The switch fabric is often the heart of a system design. It's easier to change out line cards (which are made to be interchangable) than it is to tweak a switch fabric.

The packetized OTN traffic would probably have to get some priority, because OTN expects to see a constant bit rate. "They don't like long delays," Mok says.

Along those lines, the protocol includes a way for the OTN cards to preserve the timing that's associated with a particular OTN flow. It's done in code: The line card sends out packets of varying sizes, and the proportion of sizes indicates the required rate of transmission. For example, if the switch fabric is optimized for 128-byte packets, and the transmitting card is sending lots of 126- and 127-byte packets, that means the OTN transmission rate isn't very high.

"Signaling -- the frequency -- is the bulk of what this implementation agreement is about," Mok says.

The protocol isn't meant for every system. OTN traffic that's very time-sensitive should still go through pure OTN switches, Mok says. (Packet switching is inherently slower than OTN switching.) But he thinks that would be a small fraction of cases.

And of course, someone building a system for OTN only, not packets, would have no use for the protocol.

Some equipment vendors are already offering a version of the OTN-over-packet fabric; the protocol is "definitely doable" in a field programmable gate array (FPGA), Mok says.

— Craig Matsumoto, West Coast Editor, Light Reading

About the Author(s)

Craig Matsumoto

Editor-in-Chief, Light Reading

Yes, THAT Craig Matsumoto – who used to be at Light Reading from 2002 until 2013 and then went away and did other stuff and now HE'S BACK! As Editor-in-Chief. Go Craig!!

Subscribe and receive the latest news from the industry.
Join 62,000+ members. Yes it's completely free.

You May Also Like