Regarding timescale, I think we can refer to section 7 of RFC7810.
But I agree with your point on instantaneous bandwidth, I propose to remove
available and utilized bandwidth from draft-ietf-alto-performance-metrics,
Hope this address your comment.
-Qin
-邮件原件-
发件人: Brian Trammell (IETF)
Brian:
Apologize for late reply. Thanks for valuable review.
-邮件原件-
发件人: Brian Trammell [mailto:i...@trammell.ch]
发送时间: 2018年4月10日 0:36
收件人: tsv-...@ietf.org
抄送: alto@ietf.org; i...@ietf.org;
draft-ietf-alto-performance-metrics@ietf.org
主题: Tsvart early review of draft-ietf-alto-perfo
Hi Brian,
Thanks so much for your thorough review. We'll get back with answers and update
proposals asap.
Cheers,
Sabine
-Original Message-
From: Brian Trammell (IETF) [mailto:i...@trammell.ch]
Sent: Thursday, April 12, 2018 9:48 PM
To: TSV Area Review Team
Cc: draft-ietf-alto-perform
On further review, I have an additional question about the metrics specified in
the document:
Max reservable (sec 8.1) and residue (sec 8.2) bandwidth seem to be fairly
straightforward to calculate in a stable manner, as they are essentially
matters of router configuration, but I'm a little con
Reviewer: Brian Trammell
Review result: On the Right Track
I've performed a (late, apologies) early TSV-ART review of
draft-ietf-alto-performance-metrics-03.
The set of metrics chosen by the document seem broadly useful and sane, and the
integration into ALTO makes sense. However, there are a few
