there's a lot of chat about intent-oriented networking e.g. Nemo, - latest fad - seems to be a little bit like predicate routing - or declarative networking - where you way, in a very high-level way (e.g. legalease, c.f. recent microsoft paper on compliance) what you want to happen. Hopefully, this is 11 layers higher than open flow, and employs P4 at a minimum, as most of the intents that aren't just 5-tuple flowspec based, must necessarily employ DPI and application based content patterns.
however, where are the semantics? this seems to me to be a massive missing mole of an elephant in the room
Who (subject/object) wants What (packet, router, link, user) to be Where (in a jurisdiction, or not) When (before T, after T etc), and Why (profit, loss, legal link, fun) - the WWWWW (High 5 ?) of networking - it shouldn't be too hard to do a bit of deontic logic and denotational sugar to get this right...a suitable job for computer science, and possibly, the NaaS project, but possibly not...
however, where are the semantics? this seems to me to be a massive missing mole of an elephant in the room
Who (subject/object) wants What (packet, router, link, user) to be Where (in a jurisdiction, or not) When (before T, after T etc), and Why (profit, loss, legal link, fun) - the WWWWW (High 5 ?) of networking - it shouldn't be too hard to do a bit of deontic logic and denotational sugar to get this right...a suitable job for computer science, and possibly, the NaaS project, but possibly not...
No comments:
Post a Comment