- rssac-caucus - lists.icann.org

[rssac-caucus] Ombudsman assessment
by Carlos Reyes April 21, 2017

April 21, 2017

Dear RSSAC Caucus, Please consider participating in this survey to contribute to the current Ombudsman assessment. This assessment of the ICANN Ombudsman Office was initiated in response to recommendations from the Second Accountability and Transparency Review and workstream 2 activities of the Cross-Community Working Group on Enhancing ICANN Accountability. Best, Carlos 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] New Caucus member
by Carlos Reyes April 13, 2017

April 13, 2017

Dear all, On its 6 April teleconference and at the recommendation of the Membership Committee, the RSSAC approved Geoff Huston as a new member of the Caucus. His statement of interest is available here. He has been added to this mailing list as well. Please join me in welcoming Geoff. Best, Carlos 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

2 1

[rssac-caucus] Monthly Update
by Carlos Reyes April 7, 2017

April 7, 2017

Hello, all. This is the Caucus monthly update. As always, we welcome your feedback on the content and format of these updates. Thank you, Carlos ADMINISTRATION Minutes/Notes from RSSAC and Caucus Meetings Minutes or notes from Caucus meetings are posted here. (This page is now current; apologies for the oversight.) As a reminder, minutes from RSSAC teleconferences are published here. Upcoming Caucus Meetings The next Caucus meeting will be held during ICANN60 | Annual General Meeting (28 October-3 November 2017) in Abu Dhabi, UAE. The exact date, time, and location will be confirmed as the meeting approaches. Per the cadence of Caucus meetings at IETF meetings, the Caucus will not convene at IETF99 in Prague, Czech Republic. The next Caucus meeting at an IETF meeting will be held during IETF100 (12-17 November 2017) in Singapore. The exact date, time, and location will be confirmed as the meeting approaches. WORK UPDATES Proposed Work Items On its 6 April teleconference, the RSSAC discussed recently proposed work items for the Caucus. The RSSAC encourages more discussion before statements of scope and work are drafted. Root Server Naming Scheme Work Party | John Bond, Work Party Leader The RSN document is almost complete however it was noted that we have drifted away from the initial statement of work. In an effort to get the document back on track, a small group from the work party met with some members from RSSAC to identify outstanding issues. The meeting was successful and we have a few more edits to perform on the document and a few more experiments to conduct. We have committed to producing a second draft of the document incorporating all updates by the beginning of May. Anycast Placement Work Party | Kaveh Ranjbar, Work Party Leader The work is aiming to answer or align understanding of a few questions that came out of the first two RSSAC workshops, the questions are formed around general theme of role of coordination between root server operators in terms of: Latency, DDOS, Physical placement of instances and Security. The work is on-going and so far we have a better understanding of the problem area and working towards documenting that. Next step would be converging on the answers and finalizing the results. RSSAC Tools Work Party | Wes Hardaker, Work Party Leader The RSSAC Tools work party was discussed at the RSSAC Caucus meeting at the Chicago IETF meeting. Wes Hardaker is working on finalizing the structure of the code repositories based on the discussion at the meeting.

1 0

[rssac-caucus] MADE IN USA. PCB. SPEICAL 75% OFF
by Newsletter April 5, 2017

April 5, 2017

Your email client cannot read this email. To view it online, please go here: http://bhvangebot.co/display.php?M=1915436&C=3dfbd9b50b4919248d02b8ba5c40ff… To stop receiving these emails:http://bhvangebot.co/unsubscribe.php?M=1915436&C=3dfbd9b50b4919248d02b8ba5c40ff5f&L=30&N=84

1 0

[rssac-caucus] Distribution of Anycast Instances of the Root Name Service workparty
by Kaveh Ranjbar April 4, 2017

April 4, 2017

Dear caucus members, In the last face to face meeting in Chicago, I promised to send an update on the progress of the work at “Distribution of Anycast Instances of the Root Name Service” workparty, please find my report below. If you are interested to join the work party and contribute to the this fundamental piece of work, please let me know, indicating which question(s) you are interested to contribute to and I will make sure you are added to the WP. All the best, Kaveh. —————— Distribution of Anycast Instances of the Root Name Service workparty update, as of end of March 2017: Executive summary: This work is aiming to answer or align understanding of a few questions that came out of the first two RSSAC workshops, the questions are formed around general theme of role of coordination between root server operators in terms of: Latency, DDOS, Physical placement of instances and Security. The work is on-going and so far we have a better understanding of the problem area and working towards documenting that. Details: The workparty has 20 members, divided in four groups so each group can focus on answering the relevant questions. — Group 1, 7 Members led by Suzanne Woolf: Question: Given the state of current internet technology, what is the maximum latency a relying party should experience when transacting with the DNS root service as opposed to with a single “root server”? The work is ongoing, the team has broken down the original question to multiple smaller ones and now is the time to converge on answering them. — Group 2, 14 members, led by Suresh Krishnaswamy: Question: Will adding more instances in more topologically diverse locations make the system more resilient to Denial of Service (DOS) attacks? The work is ongoing, the group has made good progress in defining DOS in the context of root server system as well as systematic resilience. Next step would be compiling current findings as an answer and making decisions on some of open questions, including the need for empirical evidence, etc. — Group 3, 12 members, led by John Bond: Question: If root operators were to coordinate their deployments of anycast instances, what considerations should be contemplated? The work is ongoing, the group has some solid content, including recognising some issues as well as some recommendations, needs to organise and compile the answers. — Group 4, 12 members, led by Russ Mundy: Question: What are the security considerations related to the distribution of anycast instances? The work is ongoing, the input is sparse and right now the main recommendation refers to RFC7706, it might be the conclusion that further work should be derived from that or other sources and no specific work related to the Root Server System is required here. — ——————

1 0

[rssac-caucus] Private Placement
by Mr. Ernest Pinto April 1, 2017

April 1, 2017

Good day, Welcome to our Private Placement Portfolio. I am a Staff of a Venture Capital Firm specializing in Growth Capital Investments/Loans.We seek to invest in Projects with Public and Private sectors in a broad range of areas including Real estate, Agriculture, Energy, Oil and Gas, emerging markets and high-technology. Within the technology sector, the firm focuses on communications, software, digital content and services. We have the capacity to invest a considerable amount of funds in any viable project(s) that your company requires funding for on an investment capacity/Loan Application. Upon the review of your company's Project Business Plan we shall determine on the project(s) possible funding. This will be form of a silent and Private Placement Investments. Endeavor to respond promptly if the investment proposal meets your company's approval. Kind Regards, Ernest Pinto

1 0

[rssac-caucus] RSSAC Caucus Meeting at IETF98 Notes
by Andrew Mcconachie March 30, 2017

March 30, 2017

Dear RSSAC Caucus Members, Please find the notes from the March 26 Caucus meeting at IETF 98 attached. Thanks, Andrew

4 5

[rssac-caucus] MTU, MSS and Frag
by George Michaelson March 27, 2017

March 27, 2017

I propose RSSAC caucus explore an understanding of the MTU, MSS and fragmentation behaviour of all instances of the roots, in IPv6 and IPv4. If we had this data, we would be able to understand if what we see with any given instance of query to a root was local, or more likely along the path. Some evidence from random query tests suggests both that there is no consistency between the root operators, and some inconsistency within a given root letter, depending on where you query goes, or what protocol you use. Because of the increase in TCP, and packetsizes in responses, this is of interest because of the exposure to fragmentation, or loss of pMTU signalling, or the variances in MSS/TCP against interface MTU and UDP. This question has a quality which goes to "only the root operators can say" which is why it feels to me like a well-formed question for the caucus to consider, which implies RSSAC taking it on board to ask the root operators about. -George

3 3

[rssac-caucus] aggressive NXDOMAIN in pDNS, and its effect on traffic to the root
by George Michaelson March 26, 2017

March 26, 2017

I would like to propose a study in rssac-caucus to collect information about the effects of the deployment of aggressive NSEC response, on the volume of query at the root. The work is late stage in DNSOP and I would expect to go to last-call and publication. This means that we can also expect deployment soon after, or even proceeding publication. DITL style infrequent capture would be useful but its possible a less costly mechanism to construct a measurement exists: I am unsure if the current RSAC002 captures this, certainly the RCODE-VOLUME measure would provide it in aggregate, but because it's dissociated from the resolver its hard to do any more qualified analysis except to say 'it dropped'. Because the change would herald a shift in the volume of undelegated (bogus) queries to the root and also reduce pressure in the known bad cases like .local, it has impacts on other policy questions under the oversight of the ICANN. It goes to that borderline between operations, and zone content. -George

4 4

[rssac-caucus] RSSAC Caucus Meeting at IETF98, Sunday, March 26 2017 from 2030-2200 UTC
by Andrew Mcconachie March 26, 2017

March 26, 2017

Dear RSSAC Caucus Members, The next RSSAC Caucus meeting will be held at IETF 98 in Chicago, USA. The meeting is scheduled for Sunday, March 26 2017 from 2030-2200 UTC/1530-1700 CDT. For other times: http://bit.ly/2nfHXWM Please find the agenda attached. Verizon US: +1 (866) 780-9216 (Dial in numbers for other countries listed in the bottom of email) Participant Passcode: Participant: 2111690 Adobe Connect: https://participate.icann.org/rssac Dial in numbers*: Country Local/Toll Number Freephone/Toll Free Number ARGENTINA 0800-777-0487 AUSTRALIA ADELAIDE: 61-8-8121-4859 1-800-880-484 AUSTRALIA BRISBANE: 61-7-3102-0961 1-800-880-484 AUSTRALIA CANBERRA: 61-2-6100-1961 1-800-880-484 AUSTRALIA MELBOURNE: 61-3-9010-7730 1-800-880-484 AUSTRALIA PERTH: 61-8-9467-5240 1-800-880-484 AUSTRALIA SYDNEY: 61-2-8211-1382 1-800-880-484 AUSTRIA 43-1-92-89-574 0800-999-850 BELGIUM 32-2-400-6717 0800-4-8474 BRAZIL 55-11-3958-0764 0800-7610666 CHILE 1230-020-0288 CHINA CHINA A: 86-400-810-4757 10800-712-1194 CHINA CHINA B: 86-400-810-4757 10800-120-1194 COLOMBIA 01800-9-156471 CROATIA 080-08-06-319 CZECH REPUBLIC 420-2-25-98-56-11 800-700-164 DENMARK 45-7014-0235 8088-5347 ESTONIA 800-011-1124 FINLAND 358-9-5424-7147 0-800-1-12418 FRANCE LYON: 33-4-26-69-12-72 080-511-1516 FRANCE MARSEILLE: 33-4-86-06-00-72 080-511-1516 FRANCE PARIS: 33-1-70-70-60-73 080-511-1516 GERMANY 49-69-2222-20267 0800-101-4259 GREECE 30-80-1-100-0635 00800-12-6136 HONG KONG 852-3001-3828 800-964-135 HUNGARY 36-1-700-8841 06-800-15442 INDIA INDIA B: 000-800-001-6249 INDIA INDIA C: 1800-300-00430 INDIA INDIA A: 000-800-852-1213 INDONESIA 001-803-011-3491 IRELAND 353-1-246-0095 1800-992-121 ISRAEL 1-80-9214002 ITALY MILAN: 39-02-3600-3564 800-985-429 ITALY ROME: 39-06-8751-6013 800-985-429 ITALY TORINO: 39-011-510-0113 800-985-429 JAPAN OSAKA: 81-6-7878-2653 00531-12-1150 JAPAN TOKYO: 81-3-6868-2653 00531-12-1150 LATVIA 8000-3168 LUXEMBOURG 352-27-000-1310 8002-9125 MALAYSIA 1-800-80-8105 MEXICO GUADALAJARA (JAL): 52-33-3208-7322 001-866-318-9747 MEXICO MEXICO CITY: 52-55-5062-9122 001-866-318-9747 MEXICO MONTERREY: 52-81-2482-0622 001-866-318-9747 NETHERLANDS 31-20-712-1372 0800-023-1492 NEW ZEALAND 64-9-970-4637 0800-443-823 NORWAY 47-21-59-00-10 800-12069 PANAMA 011-001-800-5072077 PERU 0800-53715 PHILIPPINES 63-2-858-3706 1800-111-42452 POLAND 00-800-1210160 PORTUGAL 8008-12108 ROMANIA 40-31-630-01-64 RUSSIA 8-10-8002-9913011 SAUDI ARABIA 800-8-110058 SINGAPORE 65-6883-9193 800-120-4060 SLOVAK REPUBLIC 421-2-322-422-12 0800-002032 SOUTH AFRICA 080-09-93392 SOUTH KOREA 82-2-6744-1048 00798-14800-6324 SPAIN 34-91-414-14-65 800-099-374 SWEDEN 46-8-566-10-474 0200-887-680 SWITZERLAND 41-44-580-3270 0800-000-246 TAIWAN 886-2-2795-7342 00801-137-568 THAILAND 001-800-1206-65076 TURKEY 00-800-151-1241 UNITED ARAB EMIRATES 8000-35702362 UNITED KINGDOM BIRMINGHAM: 44-121-210-9012 0800-279-9352 UNITED KINGDOM GLASGOW: 44-141-202-3212 0800-279-9352 UNITED KINGDOM LEEDS: 44-113-301-2112 0800-279-9352 UNITED KINGDOM LONDON: 44-20-7019-0830 0800-279-9352 UNITED KINGDOM MANCHESTER: 44-161-601-1412 0800-279-9352 URUGUAY 000-413-598-3452 USA 1-210-795-0469 866-780-9216 VENEZUELA 0800-1-00-2853

2 3