I have been wrestling with a question that I thought I would bring out to the rest of the world.  In PNRP today, we have three scopes in which you can register or resolve a name; the global scope which includes all machines in the world, the site scope which mirrors the IPv6 concept of local site (usually within a company) and the link-local scope which represents all machines connected on a link.  We have heard from a lot of developers that the link scope is very hard to use as every machine has a different link-cloud name (since the clouds are named after the interface) and because it is confusing regarding which one to use if there are multiple interfaces.  Furthermore, IPv6 has deprecated their concept of site-scope, so it is unclear what should be done with that scope.  Thus my question for the PNRP users out there is what scopes would be useful to you?

My current favorite idea is that site goes away (it never seemed to be used much anyways), individual link clouds remain for power users, but that we add a new keyword that can be used in place of a cloud name called something like 'ALL-LINK.'  It would mean to perform the register or resolve in all of the link clouds.  This would probably simplify life for 95% of use cases.

Does that sound helpful?