[rssac-caucus] [Non-DoD Source] FOR REVIEW: DRAFT RSSAC002 Version 2

[Wessels, Duane]

> On Nov 19, 2015, at 4:24 AM, Kash, Howard M CIV USARMY RDECOM ARL (US) <howard.m.kash.civ at mail.mil> wrote:
> 
> Section 4.1, second paragraph, "The latency in the distribution system" needs
> to be changed to "Latency in publishing available data".

Yes.

> 
> Section 3, third bullet - is this still true?  If this was for NSD, it has
> been corrected.

Not sure if its still true.  We could poll the operators.  I see little harm
in leaving it as-is for now.

> 
> Section 2.1 - For v3 of the document I would like to see more details on how
> this value should be computed, for the sake of consistency.  For example, I
> have six servers that receive notifies directly from the distribution masters.
> Should the load-time value be computed on each server separately and then
> averaged (this is what I am currently doing)?  Or should the notify and load
> times from all servers be collected centrally and the value computed by
> subtracting the earliest (first received) notify time from the latest/last
> load time?  What if a notify is never received (by an individual server in
> the first case or by any of the servers in the second case)?

This sounds to me like more than a simple clarification and probably worthy
of a work party.  So as you say, a good item for "v3".


> 
> Section 2.1, second paragraph - "may present as anomalies in measurements",
> perhaps change to "may introduce anomalies"?

How would you feel about "may appear as anomalies"?  To me "introduce"
sounds just a little too much like blaming anycast for causing a problem.  Or 
maybe since this is the same section as the above item, it will likely all
get rewritten in v3 so we save it until then?

> 
> Section 4.1, "If not load-time metric is available...", change "not" to "no"

Yes.


> Section 5, make title plural (Recommendations)

Yes.

Thanks!