- rssac-caucus - lists.icann.org

Re: [rssac-caucus] REMINDER FOR REVIEW: Version 3 of RSSAC002 - Measurements of Root Server System
by George Michaelson May 17, 2016

May 17, 2016

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(a)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(a)icann.org> on behalf of Steve Sheng < > steve.sheng(a)icann.org> > *Date: *Wednesday, May 11, 2016 at 2:59 AM > *To: *"rssac-caucus(a)icann.org" <rssac-caucus(a)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 > > >

1 0

[rssac-caucus] FOR REVIEW: Version 3 of RSSAC002 - Measurements of Root Server System
by Steve Sheng May 10, 2016

May 10, 2016

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

1 0

[rssac-caucus] RSSAC Caucus Meeting at IETF 96
by Carlos Reyes May 6, 2016

May 6, 2016

Dear RSSAC Caucus, As a reminder there will be an RSSAC Caucus meeting at IETF 96 in Berlin, Germany. This keeps with the schedule of convening the RSSAC Caucus at every other IETF meeting. More details about the agenda, exact date, time and room for the meeting will follow. Please do not hesitate to suggest potential agenda items on the mailing list as well. Regards, Carlos On Behalf of RSSAC Co-Chairs Tripti Sinha and Brad Verd Carlos Reyes | Policy and Community Engagement Manager carlos.reyes(a)icann.org | +1 (202) 802-8019 ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006

1 0

[rssac-caucus] Can we get the MTU/MSS for the roots?
by George Michaelson May 4, 2016

May 4, 2016

It would be informative to understand what interface MTU the hosts providing DNS use, in the roots. This is not to suggest there has to be a defined one, but it would help understand how people interact in the UDP/TCP shift under TC=1, because of the lack of ICMP/ICMPv6 signal (ICMP filters) and the effect of the server-side in TCP setting a lower MSS avoiding the problem. Could the caucus act as a channel to get this data? -George

1 0

[rssac-caucus] Meeting at Marrakeck & Adobe Connect
by Alejandro Acosta March 18, 2016

March 18, 2016

Hello, I don't know who I should report this. I believe there is something wrong with the Adobe Connect recording for our public meeting in Marrakech, if you try to access it from this link: https://meetings.icann.org/en/marrakech55/schedule/wed-nomcom then you go to the Adoble Connect room as if the meeting still alive; therefore, you are not able to see the session video. It does not happen with some other meetings I have checked. Regards, Alejandro,

2 1

[rssac-caucus] DNS Root Server System history - input
by Tripti Sinha March 9, 2016

March 9, 2016

Dear Caucus, In September 2015, the RSSAC held its first workshop to discuss issues related to the evolution of the root server system. The public report of the successful workshop is available on the RSSAC publications page <https://www.icann.org/resources/pages/rssac-publications-2014-05-12-en>. To prepare for the workshop, the RSSAC compiled a document outlining the history of the root server system. This document provided a foundation for informed discussions at the workshop. The RSSAC has further reviewed the document since the workshop. Before publication, the RSSAC would like to seek input from the Caucus on this document. The RSSAC would like to propose a process for Caucus review of the draft history of the root server system document. Through *04 March 2016*, the RSSAC invites Caucus members to review the draft for factual correctness. At the end of the 4 week review period, the RSSAC will determine if further Caucus review is necessary before proceeding with publication. Please send your input directly to *Steve Sheng at steve.sheng(a)icann.org <steve.sheng(a)icann.org>.* The RSSAC hopes robust Caucus review will strengthen this important document on the history of the root server system. Please do not hesitate to contact us with any question or concerns. We look forward to your contributions. Best regards, Tripti Sinha and Brad Verd RSSAC Co-Chairs

6 10

[rssac-caucus] How It Works: Root Server Operation | Adobe Connect: Full
by Alejandro Acosta March 8, 2016

March 8, 2016

Hello, Yesterday during ICANN was given a presentation called: "How It Works: Root Server Operation", it given by some folks of RSSAC The presentation is right here: https://meetings.icann.org/en/marrakech55/schedule/mon-how-root-server-ops/… Great presentation, thanks for it. Alejandro,

3 2

[rssac-caucus] Video: Serigrafía en sudaderas
by Peter March 1, 2016

March 1, 2016

[1]http://aspesite.com/ ¡ASPE's RapidTag hacer impresiones serigráficas sobre forro polar! Nuestras máquinas de serigrafía pueden tener múltiples accesorios que pueden ayudar con ciertos productos. Uno de estos es la paleta para capuchas, una paleta curvada especialmente diseñada para que las gorras y las correas no queden atrapados en el cabezal de impresión o queden en el camino de la impresión. [2]aspesite.com/pallet-custom-screen-printing-machine/ [3]https://www.youtube.com/watch?v=MXcinXN_99Q&list=PLIxGpEV3M_ZnlWFTwgp_5p II-gxtu6n71&index=6 ASPE's RapidTag se especializa en impresión de etiquetas y otras impresiones pequeñas, como logos y mangas. Nuestras pequeñas máquinas estan hechas para ayudarte a liberar tus máquinas serigraficas grandes y acelerar tu producción. Esta pequeña máquina puede adaptarse a cualquier velocidad humana, imprimiendo un promedio de 1500 piezas por hora. [4]Más sobre sudaderas [5]Construye la Tuya [6]Retorno de Inversión Visitas a trade shows: ISS Atlantic City Marzo 17 - 19 [7][Autounload-04_zpsg9vzgyap.png] [8][Autounload-05_zps791aomq0.png] [9][Autounload-06_zpspcyxj2jb.png] INGLÉS - (951).296.2595 ESPAÑOL - (664).134.4759 References 1. http://aspesite.com/ 2. http://aspesite.com/pallet-custom-screen-printing-machine/ 3. http://aspesite.com/pallet-custom-screen-printing-machine/ 4. http://aspesite.com/pallet-custom-screen-printing-machine/ 5. http://aspesite.com/build-your-custom-screen-printing-machine/ 6. http://aspesite.com/roi/ 7. https://www.facebook.com/pages/ASPE-Printing-Equipment/298253406928915?fref… 8. https://twitter.com/aspesite 9. https://www.youtube.com/user/asperevolution This message was sent by: Peter, peter(a)aspesite.com, ASPE, 42295 Avenida Alvarado Unit 5, Temecula, Ca 92590 Unsubscribe: http://app.icontact.com/icp/mmail-mprofile.pl?r=62295777&l=12026&s=77R3&m=4…

1 0

[rssac-caucus] Video: Texturizar guantes
by Peter Feb. 23, 2016

Feb. 23, 2016

[1]http://aspesite.com/ ASPE's RapidTag puede hacer impresiones de textura en guantes Nuestras máquinas de serigrafía RapidTag puede ser personalizadas para adaptarse a diferentes necesidades y diferentes productos. Por ejemplo, ¡Se puede utilizar para texturizar y marcar guantes! Esto se utiliza para crear una textura de agarre (gripping/non-slip) que también se puede aplicar a los calcetines y otros productos similares. [2]http://aspesite.com/screenprint-gloves-dotting-marking/ ASPE's RapidTag se especializa en impresión de etiquetas y otras impresiones pequeñas, como logos y mangas. Nuestras pequeñas máquinas estan hechas para ayudarte a liberar tus máquinas serigraficas grandes y acelerar tu producción. Esta pequeña máquina puede adaptarse a cualquier velocidad humana, imprimiendo un promedio de 1500 piezas por hora. [3]Más sobre Guantes [4]Construye la Tuya [5]Retorno de Inversión [6]https://www.youtube.com/watch?v=qiIOnfxNwbY&index=3&list=PLIxGpEV3M_ZlOg _6dXuYRv8-pfqTDn2I- Visitas a Trade shows: ISS Atlantic City Marzo 17 al 19 [7][Autounload-04_zpsg9vzgyap.png] [8][Autounload-05_zps791aomq0.png] [9][Autounload-06_zpspcyxj2jb.png] INGLÉS - (951).296.2595 ESPAÑOL - (664).134.4759 References 1. http://aspesite.com/ 2. http://aspesite.com/screenprint-gloves-dotting-marking/ 3. http://aspesite.com/screenprint-gloves-dotting-marking/ 4. http://aspesite.com/build-your-custom-screen-printing-machine/ 5. http://aspesite.com/roi/ 6. https://www.youtube.com/watch?v=qiIOnfxNwbY&index=3&list=PLIxGpEV3M_ZlOg_6d… 7. https://www.facebook.com/pages/ASPE-Printing-Equipment/298253406928915?fref… 8. https://twitter.com/aspesite 9. https://www.youtube.com/user/asperevolution This message was sent by: Peter, peter(a)aspesite.com, ASPE, 42295 Avenida Alvarado Unit 5, Temecula, Ca 92590 Unsubscribe: http://app.icontact.com/icp/mmail-mprofile.pl?r=62295777&l=12026&s=77R3&m=4…

1 0

[rssac-caucus] REMINDER: DNS Root Server System history - input
by Steve Sheng Feb. 18, 2016

Feb. 18, 2016

Dear RSSAC Caucus, Thank you to those who have submitted comments on the history document. If you have any additional comments, please let me know by 4 March 2016. For your convenience, the documents are attached in this email. Best Steve From: Tripti Sinha <tsinha(a)umd.edu<mailto:tsinha@umd.edu>> Date: Wednesday, February 3, 2016 at 4:59 PM To: "rssac-caucus(a)icann.org<mailto:rssac-caucus@icann.org>" <rssac-caucus(a)icann.org<mailto:rssac-caucus@icann.org>> Cc: "Verd, Brad" <bverd(a)verisign.com<mailto:bverd@verisign.com>>, Tripti Sinha <tsinha(a)umd.edu<mailto:tsinha@umd.edu>>, Steve Sheng <steve.sheng(a)icann.org<mailto:steve.sheng@icann.org>>, Carlos Reyes <carlos.reyes(a)icann.org<mailto:carlos.reyes@icann.org>> Subject: DNS Root Server System history - input Dear Caucus, In September 2015, the RSSAC held its first workshop to discuss issues related to the evolution of the root server system. The public report of the successful workshop is available on the RSSAC publications page<https://www.icann.org/resources/pages/rssac-publications-2014-05-12-en>. To prepare for the workshop, the RSSAC compiled a document outlining the history of the root server system. This document provided a foundation for informed discussions at the workshop. The RSSAC has further reviewed the document since the workshop. Before publication, the RSSAC would like to seek input from the Caucus on this document. The RSSAC would like to propose a process for Caucus review of the draft history of the root server system document. Through 04 March 2016, the RSSAC invites Caucus members to review the draft for factual correctness. At the end of the 4 week review period, the RSSAC will determine if further Caucus review is necessary before proceeding with publication. Please send your input directly to Steve Sheng at steve.sheng(a)icann.org<mailto:steve.sheng@icann.org>. The RSSAC hopes robust Caucus review will strengthen this important document on the history of the root server system. Please do not hesitate to contact us with any question or concerns. We look forward to your contributions. Best regards, Tripti Sinha and Brad Verd RSSAC Co-Chairs

1 0