It's ok to use the parameters to further "refine" your action, but
just make sure that your custom action shouldn't really be a standard
action of another resource. It could very well be that although your
"network" action seems to be needed on a user resource, perhaps you're
really stumbling upon a discovery of a new resource entirely.
What does the network action try to do? And if you *had* to stick to
the seven RESTful actions, what action would "network" be and for what
Those are the kinds of questions I ask myself whenever I feel like
adding a custom action, and about half the time, I'm able to just
declare a new resource and remove the custom action.