[Nmc-wg] Transport protocol

Martin Swany swany at cis.udel.edu
Tue Feb 16 08:15:50 CST 2010


Hey Aaron,

> Port choice is also heavily dependent on the implementation, e.g. if a service were implemented as a single MA instance containing ping, bandwidth, latency and utilization data vs. 4 separate services each containing one of the data types, the ports would be different even though the data you can obtain is the same. Thinking in terms of the metrics, I'm not sure it makes sense to say "get ping data on port 8065" or "get snmp data on port 8075" or whatever.
> 
> All told, I'd rather get folks into the mindset of doing a lookup to find the location of information vs. assuming that  "There's ping data on host X, ergo I connect to port 8065 to get it".

I agree that's the right thing.  I was assuming that we wanted to
document as much as we could about what's going on -- in a
non-normative part of the doc.  As you say, the "right" answer is
"you look it up."

martin


More information about the Nmc-wg mailing list