- rssac-caucus - lists.icann.org

[rssac-caucus] Resolver Study WP | Meeting Notes | Teleconference on 6 December 2018
by Mario Aleman Dec. 10, 2018

Dec. 10, 2018

Dear Caucus Members, Since some of you joined the previous Resolver Study WP teleconference, please find attached the Meeting Notes. For more information regarding the Resolver Study, please visit https://community.icann.org/display/RSSAC/RSSAC+Caucus+Resolver+Study+Work+… Best, --- Mario From: Mario Aleman <mario.aleman(a)icann.org> Date: Thursday, December 6, 2018 at 2:12 PM To: RSSAC-Caucus-Resolver-Study-WP <rssac-caucus-resolver-study-wp(a)icann.org> Subject: Resolver Study WP | Meeting Notes | Teleconference on 6 December 2018 Dear Resolver Study Members, For your review, please find attached the meeting notes from today’s teleconference. Let us know if you have any comments or questions, Best, --- 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

[rssac-caucus] DNSCAP Anonymization Tools now available from DNS-OARC
by Keith Mitchell Dec. 10, 2018

Dec. 10, 2018

DNSCAP v1.10.0 + IP (pseudo-)anonymization & RSSAC040 ----------------------------------------------------- Thanks to funding from Verisign, DNS-OARC is releasing 5 new plugins for the open-source DNSCAP tool that implement various IP anonymization/ deanonymization techniques. The methods to do (pseudo-)anonymization have been taken from: RSSAC040 "Major Proposals for Methods of Anonymizing IP Addresses": https://www.icann.org/en/system/files/files/rssac-040-07aug18-en.pdf OARC hopes these features will help compliance with privacy requirements, and welcomes feedback on them from the RSSAC Community. - anonaes128: Anonymize IP addresses by encrypting them with AES128 (RSSAC040 4.1/4.3). Since AES128 works on 128 bit blocks the IPv4 addresses (32 bits) are padded by copying itself to fill the 128 bits (IPv4*4) and then the output is truncated to 32 bits which means that it can't be deanonymized. No modifications are needed for IPv6 since the output length is the same. Thanks to help from Jim Hague (Sinodun) we have successfully tested interoperability with anonymization features of compactor/inspector and this plugin. - anonmask: Pseudo-anonymize IP addresses by masking them as you do with netmasks (RSSAC040 4.4). The default is a /24 for IPv4 and /48 for IPv6 but it can be changed by command line options to the plugin. - cryptopan: Anonymize IP addresses using an extension to Crypto-PAn (College of Computing, Georgia Tech) made by David Stott (Lucent) (RSSAC040 4.2). The extension was picked instead of the reference implementation because it provided a deanonymization function, handled endian and hopefully gives better randomness in the resulting anonymized addresses. https://www.cc.gatech.edu/computing/Networking/projects/cryptopan/lucent.sh… - cryptopant: Anonymize IP addresses using the library cryptopANT, a different implementation of Crypto-PAn, made by the ANT project at USC/ISI (RSSAC040 4.2). https://ant.isi.edu/software/cryptopANT/index.html - ipcrypt: Anonymize IP addresses using ipcrypt create by Jean-Philippe Aumasson (RSSAC040 4.3). Although the method was designed for IPv4 addresses, the plugin can handle IPv6 addresses too. It does this with a command line option, treating IPv6 addresses as four IPv4 addresses, encrypting/decrypting them separately. https://github.com/veorq/ipcrypt All of this is now available in release v1.10.0. The full list of changes, links to tar-ball and packages can be found here: https://github.com/DNS-OARC/dnscap/releases/tag/v1.10.0 Please report any bugs or issues via the above github page, or more general queries can be addressed to <jerry(a)dns-oarc.net>.

1 0

[rssac-caucus] Call For Presentations - DNS-OARC Workshop, Thailand, Bangkok, 12th/13th May 2019
by Anand Buddhdev Dec. 7, 2018

Dec. 7, 2018

The 30th DNS-OARC Workshop will take place at the Shangri-La Hotel, Bangkok, Thailand, on May 12th and 13th 2019, hosted by ICANN. (Note that several co-located meetings are taking place immediately prior to the DNS-OARC Workshop, including the GDD Industry Summit, May 6th-9th, the Registrations Operations Workshop, May 9th, and the ICANN DNS Symposium, May 10th-11th.) The Workshop's Program Committee is now requesting proposals for presentations. All DNS-related subjects are welcome. A timeslot will also be available for lightning talks (5-10 minutes) on day two of the workshop for which submissions will be accepted until the start of the morning session on day two. There will be a Members-only session during the workshop, which will include reports on DNS-OARC's activities. If you are an OARC member and have a sensitive topic that you wish to present during that session those can be accommodated. Workshop Milestones: 05 Dec 2018 - Submissions open via Indico 22 Feb 2019 - Deadline for submission 01 Mar 2019 - Initial Contribution list published 22 Mar 2019 - Full agenda published 03 May 2019 - Deadline for slideset submission 12 May 2019 - Workshop Details for presentation submission are published here: <https://indico.dns-oarc.net/event/31/call-for-abstracts/> The workshop presentations will be organized by common themes, depending on the topics and the timing of each presentation. There are 30-minute and 15-minute slots, let us know your preference in your submission. To allow the Programme Committee to make objective assessments of submissions, so as to ensure the quality of the workshop, submissions SHOULD include slides. Draft slides are acceptable on submission. If you have questions or concerns you can contact the Programme Committee: https://www.dns-oarc.net/oarc/programme via <submissions(a)dns-oarc.net> Anand Buddhdev, for the DNS-OARC Programme Committee OARC depends on sponsorship to fund its workshops and associated social events. Please contact <sponsor(a)dns-oarc.net> if your organization is interested in becoming a sponsor. (Please note that OARC is run on a non-profit basis, and is not in a position to reimburse expenses or time for speakers at its meetings.)

1 0

[rssac-caucus] RSSAC Teleconference Minutes | 24 October 2018
by Mario Aleman Dec. 4, 2018

Dec. 4, 2018

Dear RSSAC Caucus Members, Please find attached the approved RSSAC Meeting Minutes from our 24 October 2018 teleconference. Let us know if you have any questions or comments, Best --- 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

[rssac-caucus] Fwd: [RSSAC-Caucus-Resolver-Study-WP] RESOLVER Study WP | RSSAC Caucus Teleconference Call | Thursday, 06 December 2018 | 18:00 UTC
by Fred Baker Nov. 28, 2018

Nov. 28, 2018

Passing along information about a conference call next week for this work party. In the meeting at IETF 103, we had several people attend that were not formally on the Work Party list but were interested. As then, if you're interested, please join us. > Begin forwarded message: > > From: Mario Aleman via RSSAC-Caucus-Resolver-Study-WP <rssac-caucus-resolver-study-wp(a)icann.org <mailto:rssac-caucus-resolver-study-wp@icann.org>> > Subject: [RSSAC-Caucus-Resolver-Study-WP] Resolver Study WP | RSSAC Caucus Teleconference Call | Thursday, 06 December 2018 | 18:00 UTC > Date: November 26, 2018 at 6:01:16 AM PST > To: RSSAC-Caucus-Resolver-Study-WP <rssac-caucus-resolver-study-wp(a)icann.org <mailto:rssac-caucus-resolver-study-wp@icann.org>> > Reply-To: Mario Aleman <mario.aleman(a)icann.org <mailto:mario.aleman@icann.org>> > > Dear Resolver Study WP Members, > > Following the Doodle selection date, our next RSSAC Caucus Resolver Study Work Party Teleconference Call is scheduled on Thursday 06 December 2018 from 18:00–19:00 UTC. For other times: https://tinyurl.com/ycdrq7zk <https://tinyurl.com/ycdrq7zk> > > 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> > ------------ > > 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 > > > Best, > > -- > Mario A. Aleman > mario.aleman(a)icann.org <mailto:mario.aleman@icann.org> > ICANN – Policy Development Support > _______________________________________________ > 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] Fwd: [RSSAC-Caucus-Resolver-Study-WP] RESOLVER Study WP | RSSAC Caucus Teleconference Call | Thursday, 06 December 2018 | 18:00 UTC
by Fred Baker Nov. 28, 2018

Nov. 28, 2018

Passing along information about a conference call next week for this work party. In the meeting at IETF 103, we had several people attend that were not formally on the Work Party list but were interested. As then, if you're interested, please join us. > 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] Resolver Study WP | RSSAC Caucus Teleconference Call | Thursday, 06 December 2018 | 18:00 UTC > Date: November 26, 2018 at 6:01:16 AM PST > To: RSSAC-Caucus-Resolver-Study-WP <rssac-caucus-resolver-study-wp(a)icann.org> > Reply-To: Mario Aleman <mario.aleman(a)icann.org> > > Dear Resolver Study WP Members, > > Following the Doodle selection date, our next RSSAC Caucus Resolver Study Work Party Teleconference Call is scheduled on Thursday 06 December 2018 from 18:00–19:00 UTC. For other times: https://tinyurl.com/ycdrq7zk <https://tinyurl.com/ycdrq7zk> > > 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> > ------------ > > 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 > > > Best, > > -- > Mario A. Aleman > mario.aleman(a)icann.org <mailto:mario.aleman@icann.org> > ICANN – Policy Development Support > _______________________________________________ > 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: Re: [RSSAC-Caucus-Resolver-Study-WP] Resolver Study WP: Some observations/suggestions
by Shinta Sato Nov. 28, 2018

Nov. 28, 2018

I've posted below comment to Resolver Study WP ML, but realized that this should be sent to RSSAC Caucus ML with "RESOLVER" in the subject line. Regards, Shinta Sato <shinta(a)jprs.co.jp> Japan Registry Services Co., Ltd. Forwarded by Shinta Sato <shinta(a)jprs.co.jp> ----------------------- Original Message ----------------------- From: Shinta Sato via RSSAC-Caucus-Resolver-Study-WP <rssac-caucus-resolver-study-wp(a)icann.org> To: Mohit Batra <mohit(a)mohitbatra.in> Cc: rssac-caucus-resolver-study-wp(a)icann.org Date: Tue, 27 Nov 2018 17:40:10 +0900 Subject: Re: [RSSAC-Caucus-Resolver-Study-WP] Resolver Study WP: Some observations/suggestions ---- Dear Mohit and all, On Mon, 12 Nov 2018 22:07:40 +0530 Mohit Batra via RSSAC-Caucus-Resolver-Study-WP <rssac-caucus-resolver-study-wp(a)icann.org> wrote: > Dear All, > > Please find below my observations/suggestions. > > I hope they make sense, and add some value to work/discussions of Resolver Study WP. > > Thanks, > Mohit > > 1. Most popular and vastly used public DNS resolver service like > “Google Public DNS” (8.8.8.8) uses a custom-designed implementation > by Google, rather than using popular recursive DNS server softwares > like BIND and Unbound. > > However, for our testbed(s) I think we need to at least utilize a > combination of commonly used DNS server software (recursive as well > as authoritative) which are used most out there in the wild on > Internet. Examples are BIND, Unbound, NSD, Knot DNS etc. I agree with this. In addition, to clarify the scope, I think we need to determine more about the target of the resolvers we study about. The questions listed in the Googld Doc says "code bases and configurations", but no further information there. Deciding the explicit target or at least listing them should be done, I beleive. - target of "code bases" - BIND, Unbound, Knot Resolver, PowerDNS Recursor, etc. - any commercial products, appliance servers (eg. Nominum, Infoblox) * the code may not be available, but we can still ask for the information to the vendors. - target of versions - current versions - old major versions (not modern?) - any versions with characteristic changes (if known?) - modified versions, delivered via major OS distributions - ... - target of "configurations" - which configurations? These were mostly mentioned during the meeting, but not described in the document. Regards, Shinta Sato <shinta(a)jprs.co.jp> Japan Registry Services Co., Ltd. > 2. Further, it would be useful to create a list of ready-reference study > material that Resolver Study WP members (and RSSAC Caucus members) > can refer to while performing tests and simulations, and > exploring/proposing new use cases. This ready-reference study > material may include, but is not limited to: > a. RFCs, STDs, BCPs and Internet drafts related to DNS/DNSSEC, that > fit into the scope of this WP. One Example is RFC 8109 (BCP 209) > -Initializing a DNS Resolver with Priming Queries. Another > example is RFC 8483 (Yeti DNS Testbed). > b. Research/Academic papers that fit into the scope of this WP. I > believe it is already being worked upon by Wes. > c. non-IETF but reputed DNS/DNSSEC deployment guides, that fit into > the scope of this WP. One example is: Secure DNS Deployment Guide > - NIST Special Publication 800-81-2 > https://nvlpubs.nist.gov/nistpubs/specialpublications/nist.sp.800-81-2.pdf > <https://nvlpubs.nist.gov/nistpubs/specialpublications/nist.sp.800-81-2.pdf> > > 3. Finally, while referring to DNS/DNSSEC specific BCPs in our > ready-reference study material above, we may test/check on our > testbed(s) whether Resolvers are conforming to these BCPs. _______________________________________________ RSSAC-Caucus-Resolver-Study-WP mailing list RSSAC-Caucus-Resolver-Study-WP(a)icann.org https://mm.icann.org/mailman/listinfo/rssac-caucus-resolver-study-wp --------------------- Original Message Ends --------------------

1 0

[rssac-caucus] RSSAC Caucus Service Coverage Work Party
by ryan stephenson Nov. 27, 2018

Nov. 27, 2018

I'm sending this following a change discussed in the RSSAC Caucus meeting at ICANN63. 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 words "SERVICE COVERAGE" in the subject line to facilitate email filtering. The Work Party has had two meetings, one teleconference on 1 October and one in person meeting on 21 October at ICANN63. The Work Party is still looking for a leader. Interested persons are welcome to contribute and review documents. The plan going forward, here are the work party Shepherd, Leader, and pertaining documents. Work Party Shepherd : Lars-Johan Liman Work party Leader - still available Google Document with Work Party information: https://docs.google.com/document/d/1rK7JB1G0DdrbhcTdsR0tkfv7fro_uHb6z0GyZ0U… 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 the Statement of Work.

1 0

[rssac-caucus] RSSAC Caucus Service Coverage Work Party
by ryan stephenson Nov. 26, 2018

Nov. 26, 2018

I'm sending this following a change discussed in the RSSAC Caucus meeting at ICANN63. 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 words "SERVICE COVERAGE" in the subject line to facilitate email filtering. The Work Party has had two meetings, one teleconference on 1 October and one in person meeting on 21 October at ICANN63. The Work Party is still looking for a leader. Interested persons are welcome to contribute and review documents. The plan going forward, here are the work party Shepherd, Leader, and pertaining documents. Work Party Shepherd : Lars-Johan Liman Work party Leader - still available Google Document with Work Party information: https://docs.google.com/document/d/1rK7JB1G0DdrbhcTdsR0tkfv7fro_uHb6z0GyZ0U… 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 the Statement of Work.

1 0

[rssac-caucus] [SPAM] AN INVESTMENT OFFER.
by Charles Mayiga Nov. 20, 2018

Nov. 20, 2018

Greetings, We are international project financiers and we specialize in both start up projects and existing businesses needing funding or Loan for expansion. We are committed to helping businesses develop and succeed. We will like to partner with you/your company should you be interested or may require funding for the expansion of your business. We will be glad to receiving your terms and condition before proceeding further. We are currently seeking means of expanding and relocating our business interest and we are open for discussion to any lucrative investments you can recommend to us which will be implemented under a blind trust investment venture. Looking forward to hear from you. Sincere regards, Charles Mayiga.

1 0