To be fair, it's not entirely clear at this point. I have a slight bias towards a single call -- "what does *this machine precisely* need to know about networking" (implicitly including info about any networks it will need to set up for the use of its containers, with that info inline to the results) -- but I can see the value of handling hosted-network stuff via the container-provisioner, because then we don't need to worry about races in which the provisioner wants to deploy using a network the networker hasn't yet configure. Let it stand for now, I think.