since interface MTU is a fundamental driver of the response size, and the TC=1 outcome, I repeat a request I sent in a direct mail: can we get a formalized response from the operators of the MTU setting they use, so that we can understand the resulting impact on IPv4 and IPv6 fragmentation, and on implied UDP sizes, and TC=1 outcomes. -G On 18 May 2016 at 06:16, Steve Sheng <steve.sheng@icann.org> wrote:
Dear RSSAC Caucus,
This is a reminder to submit your review of this document by close of business *27 May 2016. *
Best
Steve
*From: *<rssac-caucus-bounces@icann.org> on behalf of Steve Sheng < steve.sheng@icann.org> *Date: *Wednesday, May 11, 2016 at 2:59 AM *To: *"rssac-caucus@icann.org" <rssac-caucus@icann.org> *Subject: *[rssac-caucus] FOR REVIEW: Version 3 of RSSAC002 - Measurements of Root Server System
Dear RSSAC Caucus,
On behalf of the work party to revise RSSAC002, attached please find v3 of RSSAC002 – Measurements of the Root Server System.
The work party was created by RSSAC on 4 February 2016 with the following scope of work: https://www.icann.org/en/system/files/files/rssac-002-scope-04feb16-en.pdf .
The work party met every other week for the last three months and revised RSSAC002. The major changes are:
- Added section 2 "Scope of Measurements" and tried to improve scope and rationales throughout the document. - 'load-time' is now defined as a strict 95th percentile. - although 'load-time' is reported as seconds, we note that it should not be assumed to have such accuracy. - for 'zone-size' metric, now only the Root Zone Maintainer should report this. - clarified definitions of responses in traffic-volume metric - for traffic-volume, included some discussion on why queries and responses might differ - clarified definition of RCODE measurements. In particular it is only for responses sent FROM the root server (not TO the server). - for 'num-sources' only count messages sent TO the server. - in section 4 rewrote the paragraph stating that TCP reassembly is non-trivial and therefore including data from DNS-over-TCP is optional. - removed 'end-period' from YAML. All measurements cover a 24 hour period and the start time is sufficient. - Added a version keyword to YAML files. - Described a YAML format that allows operators to publish custom metrics - Updated examples to be real operator statistics
The work party invites you to review this document and provide your feedback by close of business *27 May 2016. *
Feedbacks should be sent to the caucus list directly.
Best
Steve