April 14, 2008

Ring vs Mesh topology in Carrier Ethernet networks


Network architects have debated over the best way to interconnect network elements.  The ring camp believes that the best way to recover from a failure is to have a simple topology where all nodes have a similar access to the bandwidth. The mesh camp believes that the most scalable and flexible way to interconnect network elements is in meshes.

Service Providers are familiar with SONET rings and they expect Ethernet based rings in Carrier Ethernet networks to perform similarly.  However, Ethernet rings are expected to behave like Ethernet networks with oversubscription, redundant access, node protection, link aggregation and so on. Thus, Ethernet ring requirements can be more complicated than SONET ring requirements.

Do we have to mandate a ring topology in Carrier Ethernet networks?

It will be very attractive if a protocol can support both ring and mesh topologies in Carrier Ethernet networks.

Rajiv Kapoor Posted by Rajiv Kapoor at 08:53AM PST

Permalink, Comments (0), Trackbacks (0)

Tags:

Post a comment

Join the conversation!

We encourage your comments, questions and suggestions. All comments are moderated and will appear as soon as they are approved by the moderator.

Please increase the validity of your comment by providing a valid first and last name. Spam, off-topic or offensive comments will not be posted.

Name:
Email:
URL:

Comments:

Notify me of follow-up comments?

Submit the word you see below:


Post a trackback

Ping this URL to post a trackback:
http://blogs.cisco.com/trackback/5049/hAulrnio/

More blog posts

Previous post:
Are today’s Service Provider SLAs good enough?

Next post:
Open Sesame

Recent posts:
November 2009 Archive