Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Introduction

Project CASTOR is a controller-based architecture for interconnections in data centres, specifically targeting

two market segments: (a) public peering between domains (Autonomous Systems) at an Internet Exchange

Point (IXP), and (b) private peering between enterprises and cloud service providers. The advantages for the

public peering use case, compared to a traditional model (based on a route server together with a L2 learning

switch) are: (a.i) better switch hygiene or IXP policy enforcement (e.g. enforcing a single router MAC

address per port, enforcing only the allowed traffic types, etc.), (a.ii) ARP flood management (ARP requests

can be sent only to the appropriate peer rather than broadcast over the fabric) and (a.iii) improved telemetry

(e.g. reporting traffic volume between every pair of peers). Advantages for the private peering use-case for

cloud-connectivity, compared to the current model that uses a fabric with distributed control, are: (b.i) scaleout

by adding data-plane elements all managed by a single logical controller, (b.ii) management of ondemand,

elastic bandwidth between peers, and (b.iii) web-based self-provisioning by customers.

  • No labels