It looked amatuerish for a Microsoft initiative.  On the networking side, after long cliched tripelike observations about traditional IPv4 annoyances, which seemed to badly miss the issue of the side the connection is originated from (albiet later addressed indirectly when a cleint P2P program initiates a connection into a mesh,) the issue of resource locators got mauled, and seemingly by a poorly experienced team, though  I did not stick aorund for the entire clip.I dropped out on the issue of mesh names resource location.  As described, first, as a mesh based technology, a routing based names resolution protocol similar to what OSPF is to IP routing would be needed, ESPECIALLY to be highly scalable.  It is specificaly because of the hiegherachical nature of DNS that its recursive queries work so effectively.  A mesh protocol without sohpisticated routing topology and even distributed P2P servers which knowledge of the topology, becomes a cluster (I need to watch my language) of resource location.And on that point, yes, btw, P2P does not mean there are no servers.  It means that EVERYONE is both a server and a client.  The idea of a client app registering into a distrubted non-heiarchical flat naming structure negotiated among low power client machines, often of limmitted bandwidth, has long been Microsoft's downfall it has over and over again had to rectify by moving flat technologies to heigherachical ones for the purpose of scaling.Whether NetBEUI, the network protocal originaly favord for lan segments that did not scale to networks (unroutable/flat,) to browser based SAP network advertising directory services that always failed unless bouyed by a scaled OS/2 Net Bios Name Server or Windows Name Server, even at that it took massive work to evolve that into DDCHP and X.500 directory services such as Active Directory because the peer to peer meshes of the WINS/DNS services of Microsoft did not scale and were flat among themselves, thus PDC's and directory servers.And here comes some developer from Microsoft reinventing "scalable" flat technologies that can support "thousands," forget it, build on scaled hiegherical resource locator servers to find local P2P or pure serversto guide connection/resource requests.  This is they way it has always been found to work over and over again at every layer of the OSI.Rookie mistakes..