- rssac-caucus - lists.icann.org

[rssac-caucus] Meeting Minutes | RSSAC Monthly Teleconference Call | Tuesday, 02 October 2018
by Mario Aleman Nov. 6, 2018

Nov. 6, 2018

Dear RSSAC Caucus Members, Please find attached the Meeting Minutes from our RSSAC Monthly Teleconference Call on Tuesday, 02 October 2018. Let us know if you have any questions or comments, Best Regards, --- Mario A. Aleman Support Staff for RSSAC and RZERC www.icann.org<http://www.icann.org>

1 0

[rssac-caucus] RESOLVER: First cut at a list of questions for the Resolver Work Party to answer
by Paul Hoffman Nov. 6, 2018

Nov. 6, 2018

Greetings again. I have created a document with what I think the derived questions from the SOW are. It is here: https://docs.google.com/document/d/1YRFhnJMdrXqpRnVtjZ8FkVUIyg_zEma_EqsuhM0… That document *should* be commentable by anyone who has the URL, but let me know if you have issues with that. We will discuss these at the face-to-face meeting in about 90 minutes, but the question list will likely be active throughout the lifetime of the Work Party. --Paul Hoffman

4 4

[rssac-caucus] Fwd: RESOLVER: [RSSAC-Caucus-Resolver-Study-WP] Reminder: RSSAC Caucus Resolver Study WP Meeting | IETF 103 | Tuesday 06 November 2018 | 05:45 - 06:45 UTC
by Fred Baker Nov. 5, 2018

Nov. 5, 2018

> Begin forwarded message: > > From: Mario Aleman via RSSAC-Caucus-Resolver-Study-WP <rssac-caucus-resolver-study-wp(a)icann.org> > Subject: [RSSAC-Caucus-Resolver-Study-WP] Reminder: RSSAC Caucus Resolver Study WP Meeting | IETF 103 | Tuesday 06 November 2018 | 05:45 - 06:45 UTC > Date: November 6, 2018 at 8:17:18 AM GMT+7 > To: RSSAC-Caucus-Resolver-Study-WP <rssac-caucus-resolver-study-wp(a)icann.org> > Reply-To: Mario Aleman <mario.aleman(a)icann.org> > > Dear All, > > In preparation for our Caucus Resolver Study Meeting during IETF today, please be advised that remote participation will be available for this session. > > Please feel free to contact Staff for any questions or requests, > > Best, > > ---------- > Dear RSSAC Caucus Resolver WP members, > > Our next meeting and Teleconference Call during IETF 103 is scheduled on Tuesday 06 November 2018 | 12:45 - 13:45 local time UTC+7 | 05:45 – 06:45 UTC. > > The room location is APT 7 on Floor 9th of Marriott Marquis Queen’s Park in Bangkok, Thailand > > For other times: https://tinyurl.com/y9dq7s7y <https://tinyurl.com/y9dq7s7y> > > Remote Participation: > > http://participate.icann.org/rssac-caucus <http://participate.icann.org/rssac-caucus> > > Phone bridge #: +1 866-780-9216 (Dial in numbers for other countries listed in the bottom of email) > > Participant passcode 4927450 > > To request a dial-out please e-mail mario.aleman(a)icann.org <mailto:mario.aleman@icann.org> > Thank you. > > ------------ > > Dial in numbers*: > > Country > > Local/Toll Number > > Free phone/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 > > > --- > Mario A. Aleman > Support Staff for RSSAC and RZERC > Internet Corporation for Assigned Names and Numbers (ICANN) > > Mobile: +1 612-245-7112 > www.icann.org <http://www.icann.org/> > > > _______________________________________________ > RSSAC-Caucus-Resolver-Study-WP mailing list > RSSAC-Caucus-Resolver-Study-WP(a)icann.org <mailto:RSSAC-Caucus-Resolver-Study-WP@icann.org> > https://mm.icann.org/mailman/listinfo/rssac-caucus-resolver-study-wp <https://mm.icann.org/mailman/listinfo/rssac-caucus-resolver-study-wp>

1 0

[rssac-caucus] RESOLVER WP: third meeting, at IETF 103
by Fred Baker Nov. 2, 2018

Nov. 2, 2018

I'm sending this following a change discussed in the RSSAC Caucus meeting at ICANN last week, and further discussed on the Work Party list. To enhance chances for participation, RSSAC would like to see Work Party email use the Caucus list rather than the one built for the Work Party itself, and I suggest that we include the work "RESOLVER" in the subject line to facilitate email filtering. The Work Party has met twice, once by Adobe Connect (3 October) and once f2f at an ICANN meeting (23 September) with some remote attendees. We plan a third meeting at IETF 103. Interested folks are welcome (it would be good if you could RSVP privately to me, so we have a head count and can ensure that we have adequate meeting space). Specifically welcome are resolver operators and folks that maintain software resolvers might use. The plan going forward looks like this: Phil Hoffman is the Work Party Leader I'm the shepherd Phil, Geoff Huston, and Jaap Akkerhuis are operating labs, and would appreciate questions that the Work Party wants to investigate. In general, documents we develop will be developed using Google tools - Google Docs, Google Sheets, and so on. As a general recommendation, when links are sent around, I'd suggest that we put them in "suggest" mode. That makes it clear what has been changed and by whom, and enables whoever is the primary for a document to resolve them as s/he finishes with them. I have attached four emails: the initial email containing a link to the Statement of Work, my notes on the Caucus Work Party meeting last week, Phil's comment on those notes, and Mario's email regarding the meeting at IETF (what room, when, what is the remote attendance URL, etc). I have also attached a .ics event for the meeting itself; I live by my calendar, especially at ICANN and IETF meetings, and I imagine that others do as well.

1 1

[rssac-caucus] Call for Volunteer
by Carlos Reyes Nov. 2, 2018

Nov. 2, 2018

Hello, RSSAC Caucus As part of the new approach to the ICANN Fellowship Program, each Supporting Organization and Advisory Committee may nominate one mentor. Learn more here: https://www.icann.org/news/announcement-2-2018-10-16-en The mentor would server for three consecutive ICANN Public Meetings. More information can be found here: https://www.icann.org/resources/pages/fellowship-mentoring-2018-10-15-en By 23:59 UTC on Monday, 12 November please email carlos.reyes(a)icann.org if you would like to be considered for this role. Please let me know if you have any questions. Thank you, Carlos Carlos Reyes Strategic Policy Planning Director Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 202 802 8019 Skype: carlos.reyes.icann www.icann.org

1 0

[rssac-caucus] RFC8483 and some thoughts
by Davey Song Nov. 1, 2018

Nov. 1, 2018

Hi Caucus members, I'm writing to let you konw that RFC8483 (Yeti DNS Testbed) is publised via ISE as informational document. I think it is relevent here. Hope you enjoy reading it. Generally it records the experiments and expereince we run a root testbed for past 3 years. We tried some changes and studied impacts with 25 root servers, pure ipv6 network, different naming scheme, more than one DM/signer, magic signing manipulations. I think some part of this document servers the purpose of ISE document like " 'We tried it; don't do it this way'” : ) As one of co-authors, one lesson I leant is that increasing the the letter of root from 13 to a larger number in existing root system is not a good idea even in pure IPv6. Because Large response in IPv6 are prone to failure due to IPv6 fragmentation issues (I struggled on it for quite a while). If scaling the root (in terms of the number of root name server or operators) make sense in future no matter what's the cause, new approaches should be proposed and prepared in advance. I think RSSAC Caucus is a good place to discuss it, and analysize the pros and cons. I know, it is controversial in many aspects for many years in this field. But during the years, I saw lots of effort in RSSAC with deliverables such as RSSAC024 and RSSAC037. I think may be it is time to discuss and propose possible apporaches to sacle the root and take them at ICANN's full disposal. At least we can try and tell other followers in future " 'We tried it; don't do it this way'”. I'm not sure it can form a work party in caucus or not. So I try to put some preliminary thought on it in my Github repo to see if any positive feadback I can receive: https://github.com/songlinjian/scaling-root . Comments are welcome. Best regards, Davey Song

1 0

[rssac-caucus] Discussion on ways to improve RSSAC Caucus engagement
by Renard, Kenneth D CTR USARMY RDECOM CERDEC (US) Oct. 24, 2018

Oct. 24, 2018

The RSSAC has been asked to "create a more effective and transparent process for defining Caucus projects, engage Caucus membership, and to manage and promote its work". The RSSAC relies on the expertise of the Caucus to produce recommendations to the ICANN board to improve and manage the Root Server System. Some recent efforts thus far to better engage the Caucus are: 1. Changing the discussion forum of work parties to include the entire Caucus mail list versus a small set of work party members (note: changing just this week). This allows more people observe and chime in on work party discussions at any time. 2. Including an RSSAC Shepard to assist in communication between the Caucus, its work parties and the RSSAC itself. We would like to start a discussion about other ways in which we could better ensure that Caucus members could participate in Caucus activities, work parties and discussions. Are there any other actions that you feel would be beneficial to improve the Caucus' ability to execute on and communicate about caucus work items. Please feel free to discuss on the Caucus mailing list (replying to this topic). Ken Renard kenneth.d.renard.ctr(a)mail.mil

1 0

[rssac-caucus] Fellowship Program Mentoring
by Mahdi Taghizadeh Oct. 23, 2018

Oct. 23, 2018

Hi everyone. I'd like to know if any discussion the RSSAC Caucus has had regarding this Fellowship Program Mentoring <https://www.icann.org/resources/pages/fellowship-mentoring-2018-10-15-en> and any candidate has been chosen by the RSSAC? *Mahdi Taghizadeh* *http://mahdi.ws <http://mahdi.ws>*

2 2

[rssac-caucus] RSSAC Caucus Meeting at ICANN 63
by Andrew McConachie Oct. 23, 2018

Oct. 23, 2018

Dear RSSAC Caucus Members, The RSSAC Caucus will hold its next meeting at ICANN 63 in Barcelona. The meeting will be held at 10:30 - 12:00 local time, and 8:30 - 10:00 UTC. Please find an agenda for the meeting attached. The meeting will be recorded. ICANN 63 RSSAC Caucus Meeting Information Page <https://63.schedule.icann.org/meetings/901724> Adobe Connect link. <https://participate.icann.org/bcn63-129> Thanks, Andrew

1 1

[rssac-caucus] RSSAC Caucus Meeting | ICANN 63 | Tuesday 23 October 2018
by Mario Aleman Oct. 22, 2018

Oct. 22, 2018

Dear RSSAC Caucus Members, The RSSAC Caucus Meeting is scheduled on Tuesday 23 October 2018 during the ICANN 63 Annual General Meeting in Barcelona. The session will have remote participation available and is open to observers. Please find more information below. Tuesday, 23 October 2018 Time Zone in Barcelona is UTC+2. RSSAC Information Session 09:00 - 10:15 CEST | 07:00 – 08:15 UTC | Room 113 https://participate.icann.org/bcn63-113 RSSAC Caucus Meeting 10:30 - 12:00 CEST | 08:30 - 10:00 UTC | Room 129/130 https://participate.icann.org/bcn63-129 Joint Meeting with OCTO 13:30 - 15:00 CEST | 11:30 – 13:00 UTC | Room 129/130 https://participate.icann.org/bcn63-129 RSSAC Work Session 5 15:15 - 16:45 CEST | 13:15 – 14:45 UTC | Room 134 https://participate.icann.org/bcn63-134 Joint Meeting with ICANN Board 18:00 - 19:00 CEST | 16:00 – 17:00 UTC | Room 111/112 https://participate.icann.org/bcn63-111 For more information regarding the RSSAC schedule and agendas during ICANN 63, please visit: https://community.icann.org/display/RSSAC/2018+Meetings RSSSAC Schedule at ICANN 63<https://docs.google.com/spreadsheets/d/1BHqhrGfA_6daEKNOVrIEhRRVk3-qXi_ItZ8…> Best Regards, --- Mario A. Aleman Support Staff for RSSAC and RZERC Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 612-245-7112 www.icann.org<http://www.icann.org>

1 0