Hi Haibin, > On Nov 16, 2015, at 10:44 PM, Songhaibin (A) <[email protected]> wrote: > > Hi Alissa, > > I can accept the second suggestion. > > But for the first comment, I’m not sure. IMO, it does not distinguish the > bytes sent/rcvd to/from upstream or downstream peer, but only calculate that > in total.
Ok. Please answer the questions below, though. The answers are not evident from the draft. Thanks, Alissa > > Best Regards! > -Haibin > > From: Alissa Cooper [mailto:[email protected] <mailto:[email protected]>] > Sent: Thursday, November 12, 2015 7:10 AM > To: Songhaibin (A) > Cc: p2psip; [email protected] > <mailto:[email protected]> > Subject: Re: [P2PSIP] AD evaluation: draft-ietf-p2psip-diagnostics-17 > > Thanks Haibin. This looks good but there are still a few unresolved issues > from our earlier mail exchange: > > The definitions of EWMA_BYTES_SENT and EWMA_BYTES_RCVD seem problematic. > > sent = alpha x sent_present + (1 - alpha) x sent > rcvd = alpha x rcvd_present + (1 - alpha) x rcvd > > As written these equations are not right because sent/rcvd appear on both > sides. It would be clearer to use last_sent and last_rcvd or some such on the > right-hand side of these equations. But this begs some bigger questions: > > - Does this place a requirement on all nodes implementing this specification > to have to calculate these values every 5 seconds? > - How are the values calculated the first time? > - How was the value of 5 seconds chosen?
_______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
