example: circuit provisioning / WAN traffic engineering

[adferguson]

how would we even begin to think about circuit provisioning (which is inherently topology-oriented) or WAN traffic engineering in our current system? Flowlog's model is currently very tied to NetCore's "one big switch" abstraction.

for example, ESNet's OSCARS system:

• http://www.es.net/services/virtual-circuits-oscars/
• https://www.eiseverywhere.com/file_uploads/cfd4a3afb7c74c3a4abcd37c33e4a4f1_Ron_Milford.pdf
• https://code.google.com/p/nddi/wiki/README

[adferguson]

it probably makes sense to work on this in conjunction with a move to NetKAT since, if I remember correctly, NetKAT has a better model for handling topology than NetCore

[tnelson]

Almost certainly. We really do have just one "big switch" in the current
language.

The good news is that there's no foundational reason why we couldn't add
some constraint-based features. That's what LP is for! :-)

On Thu, Jan 2, 2014 at 10:08 PM, Andrew Ferguson
notifications@github.comwrote:

it probably makes sense to work on this in conjunction with a move to
NetKAT since, if I remember correctly, NetKAT has a better model for
handling topology than NetCore

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-31502852
.