Open google doc issue 24: RSpec negociation #33
Description
Below is a literal copy of google doc issue 14:
- RSpec negociation -- simple mechanism, list of rspecs -> let the AM put them in the right order from most information to least information
Jordan: In the current GetVersion() metadata, a client cannot find enough information about the prefered RSpec format to choose, that will lead to the maximum amount of information. For example, let’s take the example of the IoTLAB testbed that has extended PlanetLab RSpecs to add x,y,z coordinates for its nodes. The AM will advertise support for both its own RSpecs and PLE RSpecs. A client might want to negociate the RSpec to use by first selecting the RSpecs both the client and the server can talk, then selecting among the common RSpecs the one that bring the maximum amount of information.