On Oct 10, 2016 5:16 PM, "Thiago Macieira" <thiago.macieira at intel.com> wrote: > > On ter?a-feira, 11 de outubro de 2016 00:10:45 CEST Thiago Macieira wrote: > > Again, I argue that there's no such thing as NONE. The network you describe > > is a network composed only of EP. There's no extra logic in the endpoints: > > all the logic must reside in the gateways alone. > > Sorry, let me clarify: that's how it should be, not how it is. > > There can be no extra logic in the EPs unless it is part of the OCF spec. > Given that the Bridging Spec decided to go in a different direction, we must > conclude that the current EP/GW feature's design is obsolete and needs to be > changed. > not sure, but I think that may be my point ;)
more generally I think there's room for more disussion of just what an internetworking bridge should look like. as I mentioned I think at the very least it should not be "core". consider the options: say, 2 networks NWA and NWB. each can have one or more gateway nodes. Maybe you want some of the other nodes to support internetworking, others not. should the other network itself be representable as a resources? or should bridging nodes be invisible? I guess I think this is a much larger hairball than the wiki proposals and current implementation allow. one rather obvious problem: client sends a discovery message with RM option ( i.e discover stuff on the other network cmd.) There are discovery options here that are not currently addressed: 1. disover locally only 2 discover remotely only 3 discover locally and remotely in other words, a discovery msg with RM option - what does it mean, really? the obvious answer to me is "only gateways should process this." but that's only the beginning. "remote" could mean multiple hops across heaven-knows-what kind of networking. Sayonara, security! and each local network could have its own ideas about security. g -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161010/bd9621fb/attachment.html>
