Apologies DNS Abuse in Africa * not is. Regards On Fri, 10 Jan 2020, 8:40 am Barrack Otieno, <otieno.barrack@gmail.com> wrote:

Dear Sarah and colleagues,

I would like to propose the following topic;

Building the Capacity of end users to curb DNS Abuse is Africa.

Regards

On Thu, 9 Jan 2020, 10:57 pm Robert Nkambwe via AFRI-Discuss, < afri-discuss@atlarge-lists.icann.org> wrote:

...

Thanks for sharing Sarah.

Robert

On Thursday, January 9, 2020, 10:41:47 PM GMT+3, Sarah Kiden < skiden@gmail.com> wrote:

Dear Colleagues,

I hope this email finds you well. The ICANN67 Meeting is scheduled for March 7 - 12, 2020 in Cancún, Mexico. As with previous ICANN meetings, we plan to hold the Joint AFRALO-AfrICANN meeting. We would like to invite you to submit topics for this session. Our previous statements have focused on issues like: evolving the ICANN Multistakeholder model, New gTLD Subsequent Procedures, enhancing ICANN accountability, etc. Please see our previous statements here <https://community.icann.org/display/AFRALO/Joint+AFRALO-AfrICANN+Statements+Workspace>.

Please see our proposed timeline: Call for topics: 9 - 16 January 2020 Topic announcement and call for drafting team: 17 - 22 January 2020 Drafting of Statement: 23 January - 13 February 2020 Send Statement to Staff for translation: 14 February 2020

Please send your suggested topics by *Thursday, 16 January 2020*, after which the drafting team will prepare a draft statement that will be shared with the rest of the members.

Looking forward to your contributions.

Kind regards,

Sarah Kiden AFRALO Secretariat _______________________________________________ AfrICANN mailing list AfrICANN@afrinic.net https://lists.afrinic.net/mailman/listinfo/africann _______________________________________________ AFRI-Discuss mailing list AFRI-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/afri-discuss

Homepage for the region: http://www.afralo.org

Posting guidelines to ensure machine translations of emails sent to this list are more accurate: http://www.funredes.org/mistica/english/emec/method_emec/presentation.html#a... _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

I also like the sound of Barrack's proposal. What exactly does "DNS Abuse" mean though? If it is to try and get all important Domains DNSSEC Signed and for all DNS Resolvers to become DNSSEC aware - that would be a winner in my book! Incidentally - about 50% of all DNS lookups in South Africa are DNSSEC aware. That's actually the easy bit. Just have the Internet Connection suppliers enable DNSSEC on their resolvers. Getting the bulk or at least the important Domains DNSSEC Signed will be a bit more challenging but is quite possible; e.g. any domain for a website which may involve a financial transaction or deal with personal information. On my Domain Registration and Hosting Platform, if I am running the Registrants DNS (Zone file), DNSSEC is simply an option the Registrant can switch on. I could change that and simply enable it for everyone. However, if the Domain is then moved to a Registrar that does not support DNSSEC - there would be issues for the new Registrar. On 2020/01/10 14:20, Gabdibé GAB-HINGONNE wrote:

Dear All, I support Barrack's proposal. Building the capacity of African end users on the general question related to the DNS is very important. Kind regards Gabdibé

Gabdibé GAB-HINGONNE Tel: (+235) 66 24 95 56/99 24 95 56 Skype: live:gabdibegabhingonne E-mail : gabdibegabhingonne@yahoo.fr <mailto:gabdibegabhingonne@yahoo.fr> gabdibegabhingonne@gmail.com <mailto:gabdibegabhingonne@gmail.com>

Le ven. 10 janv. 2020 13:15, Barrack Otieno <otieno.barrack@gmail.com <mailto:otieno.barrack@gmail.com>> a écrit :

Apologies DNS Abuse in Africa * not is.

Regards

On Fri, 10 Jan 2020, 8:40 am Barrack Otieno, <otieno.barrack@gmail.com <mailto:otieno.barrack@gmail.com>> wrote:

Dear Sarah and colleagues,

I would like to propose the following topic;

Building the Capacity of end users to curb DNS Abuse is Africa.

Regards

On Thu, 9 Jan 2020, 10:57 pm Robert Nkambwe via AFRI-Discuss, <afri-discuss@atlarge-lists.icann.org <mailto:afri-discuss@atlarge-lists.icann.org>> wrote:

Thanks for sharing Sarah.

Robert

On Thursday, January 9, 2020, 10:41:47 PM GMT+3, Sarah Kiden <skiden@gmail.com <mailto:skiden@gmail.com>> wrote:

Dear Colleagues,

I hope this email finds you well. The ICANN67 Meeting is scheduled for March 7 - 12, 2020 in Cancún, Mexico. As with previous ICANN meetings, we plan to hold the Joint AFRALO-AfrICANN meeting. We would like to invite you to submit topics for this session. Our previous statements have focused on issues like: evolving the ICANN Multistakeholder model, New gTLD Subsequent Procedures, enhancing ICANN accountability, etc. Please see our previous statements here <https://community.icann.org/display/AFRALO/Joint+AFRALO-AfrICANN+Statements+Workspace>.

Please see our proposed timeline: Call for topics: 9 - 16 January 2020 Topic announcement and call for drafting team: 17 - 22 January 2020 Drafting of Statement: 23 January - 13 February 2020 Send Statement to Staff for translation: 14 February 2020

Please send your suggested topics by *Thursday, 16 January 2020*, after which the drafting team will prepare a draft statement that will be shared with the rest of the members. * * Looking forward to your contributions.

Kind regards,

Sarah Kiden AFRALO Secretariat _______________________________________________ AfrICANN mailing list AfrICANN@afrinic.net <mailto:AfrICANN@afrinic.net> https://lists.afrinic.net/mailman/listinfo/africann _______________________________________________ AFRI-Discuss mailing list AFRI-Discuss@atlarge-lists.icann.org <mailto:AFRI-Discuss@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/afri-discuss

Homepage for the region: http://www.afralo.org

Posting guidelines to ensure machine translations of emails sent to this list are more accurate: http://www.funredes.org/mistica/english/emec/method_emec/presentation.html#a... _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

_______________________________________________ AFRI-Discuss mailing list AFRI-Discuss@atlarge-lists.icann.org <mailto:AFRI-Discuss@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/afri-discuss

Homepage for the region: http://www.afralo.org

Posting guidelines to ensure machine translations of emails sent to this list are more accurate: http://www.funredes.org/mistica/english/emec/method_emec/presentation.html#a... _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

_______________________________________________ AfrICANN mailing list AfrICANN@afrinic.net https://lists.afrinic.net/mailman/listinfo/africann --

Mark James ELKINS  -  Posix Systems - (South) Africa mje@posix.co.za       Tel: +27.826010496 <tel:+27826010496> For fast, reliable, low cost Internet in ZA: https://ftth.posix.co.za Posix SystemsVCARD for MJ Elkins

Good points Mark and El, I think the end user has been missing in the DNS Security conversation yet they are actually the ones who speak with their pockets, if i may use a Kenyan Proverb. An enlightened end user is an empowered end user. As we bring the next billion users online cases of DNS abuse will definately increase. If governments feel that industry players have not control they will definately step in and thats what we are avoiding. Regards On Fri, 10 Jan 2020, 4:55 pm Dr Eberhard W Lisse, <el@lisse.na> wrote:

Gabdibé,

drafting a resolution (beforehand), or even debating a resolution, is going to achieve absolutely nothing.

Mark,

50% lookups is actually almost worth than zero :-)-).

And how many of those hit infrastructure actually in South Africa? Does the figure include the public ones from Google and Cloudflare?

My view is that this only works All-or-Nothing, because noncompliant commercial resolver operators have a commercial advantage over complaint ones.

Financial incentives may work as may financial or other sanctions.

One could even make it part of the Accreditation that DNSSEC must be offered by the Registrars.

But while the Registrars are usually the entities operating the DNS and as such have control over the end-user's DNS anyway, the chain of trust should go up to the end user and not just the Registrar.

Talking to the banks has so far not been very effective, they are happy with HTTPS even though they forget to renew their certificate on a regular basis, never mind the expense.

I don't have the answer either.

If anyone has a technical "solution" or project going on, and is coming to Cancun, please feel free to propose a presentation at TechDay on the Monday.

greetings, el

On 10/01/2020 15:26, Mark Elkins wrote:

...

I also like the sound of Barrack's proposal. What exactly does "DNS Abuse" mean though?

If it is to try and get all important Domains DNSSEC Signed and for all DNS Resolvers to become DNSSEC aware - that would be a winner in my book!

Incidentally - about 50% of all DNS lookups in South Africa are DNSSEC aware. That's actually the easy bit. Just have the Internet Connection suppliers enable DNSSEC on their resolvers.

Getting the bulk or at least the important Domains DNSSEC Signed will be a bit more challenging but is quite possible; e.g. any domain for a website which may involve a financial transaction or deal with personal information.

On my Domain Registration and Hosting Platform, if I am running the Registrants DNS (Zone file), DNSSEC is simply an option the Registrant can switch on. I could change that and simply enable it for everyone. However, if the Domain is then moved to a Registrar that does not support DNSSEC - there would be issues for the new Registrar.

On 2020/01/10 14:20, Gabdibé GAB-HINGONNE wrote:

...

Dear All, I support Barrack's proposal. Building the capacity of African end users on the general question related to the DNS is very important. Kind regards Gabdibé

Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Sarah Kiden <skiden@gmail.com> Date: 14/01/2020 11:55 a.m. (GMT+00:00) To: Barrack Otieno <otieno.barrack@gmail.com> Cc: Afri-Discuss <afri-discuss@atlarge-lists.icann.org>, AfrICANN Community List <africann@afrinic.net> Subject: Re: [AfrICANN-discuss] [AFRI-Discuss] Call for topics: Joint AFRALO-AfrICANN meeting for ICANN67 Dear all, I would kindly like to remind you that the deadline to receive your suggestions for topics for our joint statement is Thursday, 16 January 2020. So far, we have received 2 suggestions: 1. Building the capacity of end users to curb DNS abuse in Africa (suggested by Barrack Otieno and supported by 3 members) 2. Core priority areas to focus on within the African ICANN Strategy (suggested by Poncelet Ileleji) If you have other suggestions or would like to support the suggested topics, please let us know before the deadline. Regards, Sarah On Fri, Jan 10, 2020 at 2:19 PM Barrack Otieno <otieno.barrack@gmail.com<mailto:otieno.barrack@gmail.com>> wrote: Good points Mark and El, I think the end user has been missing in the DNS Security conversation yet they are actually the ones who speak with their pockets, if i may use a Kenyan Proverb. An enlightened end user is an empowered end user. As we bring the next billion users online cases of DNS abuse will definately increase. If governments feel that industry players have not control they will definately step in and thats what we are avoiding. Regards On Fri, 10 Jan 2020, 4:55 pm Dr Eberhard W Lisse, <el@lisse.na<mailto:el@lisse.na>> wrote: Gabdibé, drafting a resolution (beforehand), or even debating a resolution, is going to achieve absolutely nothing. Mark, 50% lookups is actually almost worth than zero :-)-). And how many of those hit infrastructure actually in South Africa? Does the figure include the public ones from Google and Cloudflare? My view is that this only works All-or-Nothing, because noncompliant commercial resolver operators have a commercial advantage over complaint ones. Financial incentives may work as may financial or other sanctions. One could even make it part of the Accreditation that DNSSEC must be offered by the Registrars. But while the Registrars are usually the entities operating the DNS and as such have control over the end-user's DNS anyway, the chain of trust should go up to the end user and not just the Registrar. Talking to the banks has so far not been very effective, they are happy with HTTPS even though they forget to renew their certificate on a regular basis, never mind the expense. I don't have the answer either. If anyone has a technical "solution" or project going on, and is coming to Cancun, please feel free to propose a presentation at TechDay on the Monday. greetings, el On 10/01/2020 15:26, Mark Elkins wrote:

I also like the sound of Barrack's proposal. What exactly does "DNS Abuse" mean though?

If it is to try and get all important Domains DNSSEC Signed and for all DNS Resolvers to become DNSSEC aware - that would be a winner in my book!

Incidentally - about 50% of all DNS lookups in South Africa are DNSSEC aware. That's actually the easy bit. Just have the Internet Connection suppliers enable DNSSEC on their resolvers.

Getting the bulk or at least the important Domains DNSSEC Signed will be a bit more challenging but is quite possible; e.g. any domain for a website which may involve a financial transaction or deal with personal information.

On my Domain Registration and Hosting Platform, if I am running the Registrants DNS (Zone file), DNSSEC is simply an option the Registrant can switch on. I could change that and simply enable it for everyone. However, if the Domain is then moved to a Registrar that does not support DNSSEC - there would be issues for the new Registrar.

On 2020/01/10 14:20, Gabdibé GAB-HINGONNE wrote:

...

Dear All, I support Barrack's proposal. Building the capacity of African end users on the general question related to the DNS is very important. Kind regards Gabdibé

AFRI-Discuss mailing list AFRI-Discuss@atlarge-lists.icann.org<mailto:AFRI-Discuss@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/afri-discuss Homepage for the region: http://www.afralo.org Posting guidelines to ensure machine translations of emails sent to this list are more accurate: http://www.funredes.org/mistica/english/emec/method_emec/presentation.html#a... _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Sarah Kiden <skiden@gmail.com> Date: 14/01/2020 11:55 a.m. (GMT+00:00) To: Barrack Otieno <otieno.barrack@gmail.com> Cc: Afri-Discuss <afri-discuss@atlarge-lists.icann.org>, AfrICANN Community List <africann@afrinic.net> Subject: Re: [AfrICANN-discuss] [AFRI-Discuss] Call for topics: Joint AFRALO-AfrICANN meeting for ICANN67 Dear all, I would kindly like to remind you that the deadline to receive your suggestions for topics for our joint statement is Thursday, 16 January 2020. So far, we have received 2 suggestions: 1. Building the capacity of end users to curb DNS abuse in Africa (suggested by Barrack Otieno and supported by 3 members) 2. Core priority areas to focus on within the African ICANN Strategy (suggested by Poncelet Ileleji) If you have other suggestions or would like to support the suggested topics, please let us know before the deadline. Regards, Sarah On Fri, Jan 10, 2020 at 2:19 PM Barrack Otieno <otieno.barrack@gmail.com<mailto:otieno.barrack@gmail.com>> wrote: Good points Mark and El, I think the end user has been missing in the DNS Security conversation yet they are actually the ones who speak with their pockets, if i may use a Kenyan Proverb. An enlightened end user is an empowered end user. As we bring the next billion users online cases of DNS abuse will definately increase. If governments feel that industry players have not control they will definately step in and thats what we are avoiding. Regards On Fri, 10 Jan 2020, 4:55 pm Dr Eberhard W Lisse, <el@lisse.na<mailto:el@lisse.na>> wrote: Gabdibé, drafting a resolution (beforehand), or even debating a resolution, is going to achieve absolutely nothing. Mark, 50% lookups is actually almost worth than zero :-)-). And how many of those hit infrastructure actually in South Africa? Does the figure include the public ones from Google and Cloudflare? My view is that this only works All-or-Nothing, because noncompliant commercial resolver operators have a commercial advantage over complaint ones. Financial incentives may work as may financial or other sanctions. One could even make it part of the Accreditation that DNSSEC must be offered by the Registrars. But while the Registrars are usually the entities operating the DNS and as such have control over the end-user's DNS anyway, the chain of trust should go up to the end user and not just the Registrar. Talking to the banks has so far not been very effective, they are happy with HTTPS even though they forget to renew their certificate on a regular basis, never mind the expense. I don't have the answer either. If anyone has a technical "solution" or project going on, and is coming to Cancun, please feel free to propose a presentation at TechDay on the Monday. greetings, el On 10/01/2020 15:26, Mark Elkins wrote:

I also like the sound of Barrack's proposal. What exactly does "DNS Abuse" mean though?

If it is to try and get all important Domains DNSSEC Signed and for all DNS Resolvers to become DNSSEC aware - that would be a winner in my book!

Incidentally - about 50% of all DNS lookups in South Africa are DNSSEC aware. That's actually the easy bit. Just have the Internet Connection suppliers enable DNSSEC on their resolvers.

Getting the bulk or at least the important Domains DNSSEC Signed will be a bit more challenging but is quite possible; e.g. any domain for a website which may involve a financial transaction or deal with personal information.

On my Domain Registration and Hosting Platform, if I am running the Registrants DNS (Zone file), DNSSEC is simply an option the Registrant can switch on. I could change that and simply enable it for everyone. However, if the Domain is then moved to a Registrar that does not support DNSSEC - there would be issues for the new Registrar.

On 2020/01/10 14:20, Gabdibé GAB-HINGONNE wrote:

...

Dear All, I support Barrack's proposal. Building the capacity of African end users on the general question related to the DNS is very important. Kind regards Gabdibé

AFRI-Discuss mailing list AFRI-Discuss@atlarge-lists.icann.org<mailto:AFRI-Discuss@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/afri-discuss Homepage for the region: http://www.afralo.org Posting guidelines to ensure machine translations of emails sent to this list are more accurate: http://www.funredes.org/mistica/english/emec/method_emec/presentation.html#a... _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Sarah Kiden <skiden@gmail.com> Date: 14/01/2020 11:55 a.m. (GMT+00:00) To: Barrack Otieno <otieno.barrack@gmail.com> Cc: Afri-Discuss <afri-discuss@atlarge-lists.icann.org>, AfrICANN Community List <africann@afrinic.net> Subject: Re: [AfrICANN-discuss] [AFRI-Discuss] Call for topics: Joint AFRALO-AfrICANN meeting for ICANN67 Dear all, I would kindly like to remind you that the deadline to receive your suggestions for topics for our joint statement is Thursday, 16 January 2020. So far, we have received 2 suggestions: 1. Building the capacity of end users to curb DNS abuse in Africa (suggested by Barrack Otieno and supported by 3 members) 2. Core priority areas to focus on within the African ICANN Strategy (suggested by Poncelet Ileleji) If you have other suggestions or would like to support the suggested topics, please let us know before the deadline. Regards, Sarah On Fri, Jan 10, 2020 at 2:19 PM Barrack Otieno <otieno.barrack@gmail.com<mailto:otieno.barrack@gmail.com>> wrote: Good points Mark and El, I think the end user has been missing in the DNS Security conversation yet they are actually the ones who speak with their pockets, if i may use a Kenyan Proverb. An enlightened end user is an empowered end user. As we bring the next billion users online cases of DNS abuse will definately increase. If governments feel that industry players have not control they will definately step in and thats what we are avoiding. Regards On Fri, 10 Jan 2020, 4:55 pm Dr Eberhard W Lisse, <el@lisse.na<mailto:el@lisse.na>> wrote: Gabdibé, drafting a resolution (beforehand), or even debating a resolution, is going to achieve absolutely nothing. Mark, 50% lookups is actually almost worth than zero :-)-). And how many of those hit infrastructure actually in South Africa? Does the figure include the public ones from Google and Cloudflare? My view is that this only works All-or-Nothing, because noncompliant commercial resolver operators have a commercial advantage over complaint ones. Financial incentives may work as may financial or other sanctions. One could even make it part of the Accreditation that DNSSEC must be offered by the Registrars. But while the Registrars are usually the entities operating the DNS and as such have control over the end-user's DNS anyway, the chain of trust should go up to the end user and not just the Registrar. Talking to the banks has so far not been very effective, they are happy with HTTPS even though they forget to renew their certificate on a regular basis, never mind the expense. I don't have the answer either. If anyone has a technical "solution" or project going on, and is coming to Cancun, please feel free to propose a presentation at TechDay on the Monday. greetings, el On 10/01/2020 15:26, Mark Elkins wrote:

I also like the sound of Barrack's proposal. What exactly does "DNS Abuse" mean though?

If it is to try and get all important Domains DNSSEC Signed and for all DNS Resolvers to become DNSSEC aware - that would be a winner in my book!

Incidentally - about 50% of all DNS lookups in South Africa are DNSSEC aware. That's actually the easy bit. Just have the Internet Connection suppliers enable DNSSEC on their resolvers.

Getting the bulk or at least the important Domains DNSSEC Signed will be a bit more challenging but is quite possible; e.g. any domain for a website which may involve a financial transaction or deal with personal information.

On my Domain Registration and Hosting Platform, if I am running the Registrants DNS (Zone file), DNSSEC is simply an option the Registrant can switch on. I could change that and simply enable it for everyone. However, if the Domain is then moved to a Registrar that does not support DNSSEC - there would be issues for the new Registrar.

On 2020/01/10 14:20, Gabdibé GAB-HINGONNE wrote:

...

Dear All, I support Barrack's proposal. Building the capacity of African end users on the general question related to the DNS is very important. Kind regards Gabdibé

AFRI-Discuss mailing list AFRI-Discuss@atlarge-lists.icann.org<mailto:AFRI-Discuss@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/afri-discuss Homepage for the region: http://www.afralo.org Posting guidelines to ensure machine translations of emails sent to this list are more accurate: http://www.funredes.org/mistica/english/emec/method_emec/presentation.html#a... _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

Why would an “end user” care? Why would anyone want to make it more complicated and scary to get online? Surely this is an issue for industry and not the “end user”? Most of the DNS abuse issues at the moment are due to providers not looking after their own networks / devices or acting on abuse reports. It’s not a coincidence that we end up having to block entire countries from our network on a regular basis While the goal of Barrack’s proposal might be honourable I don’t think it’s particularly practical or realistic To use an analogy. You can train someone to check the oil in their car, which in the DNS space could be akin to making sure that software was kept up to date But pushing DNS abuse knowledge would be like expecting me to be able to strip my car down Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: Barrack Otieno <otieno.barrack@gmail.com> Reply to: "africann@afrinic.net" <africann@afrinic.net> Date: Friday 10 January 2020 at 14:21 To: "el@lisse.NA" <el@lisse.NA> Cc: Afri-Discuss <afri-discuss@atlarge-lists.icann.org>, "africann@afrinic.net" <africann@afrinic.net> Subject: Re: [AfrICANN-discuss] [AFRI-Discuss] Call for topics: Joint AFRALO-AfrICANN meeting for ICANN67 Good points Mark and El, I think the end user has been missing in the DNS Security conversation yet they are actually the ones who speak with their pockets, if i may use a Kenyan Proverb. An enlightened end user is an empowered end user. As we bring the next billion users online cases of DNS abuse will definately increase. If governments feel that industry players have not control they will definately step in and thats what we are avoiding. Regards On Fri, 10 Jan 2020, 4:55 pm Dr Eberhard W Lisse, <el@lisse.na<mailto:el@lisse.na>> wrote: Gabdibé, drafting a resolution (beforehand), or even debating a resolution, is going to achieve absolutely nothing. Mark, 50% lookups is actually almost worth than zero :-)-). And how many of those hit infrastructure actually in South Africa? Does the figure include the public ones from Google and Cloudflare? My view is that this only works All-or-Nothing, because noncompliant commercial resolver operators have a commercial advantage over complaint ones. Financial incentives may work as may financial or other sanctions. One could even make it part of the Accreditation that DNSSEC must be offered by the Registrars. But while the Registrars are usually the entities operating the DNS and as such have control over the end-user's DNS anyway, the chain of trust should go up to the end user and not just the Registrar. Talking to the banks has so far not been very effective, they are happy with HTTPS even though they forget to renew their certificate on a regular basis, never mind the expense. I don't have the answer either. If anyone has a technical "solution" or project going on, and is coming to Cancun, please feel free to propose a presentation at TechDay on the Monday. greetings, el On 10/01/2020 15:26, Mark Elkins wrote:

I also like the sound of Barrack's proposal. What exactly does "DNS Abuse" mean though?

If it is to try and get all important Domains DNSSEC Signed and for all DNS Resolvers to become DNSSEC aware - that would be a winner in my book!

Incidentally - about 50% of all DNS lookups in South Africa are DNSSEC aware. That's actually the easy bit. Just have the Internet Connection suppliers enable DNSSEC on their resolvers.

Getting the bulk or at least the important Domains DNSSEC Signed will be a bit more challenging but is quite possible; e.g. any domain for a website which may involve a financial transaction or deal with personal information.

On my Domain Registration and Hosting Platform, if I am running the Registrants DNS (Zone file), DNSSEC is simply an option the Registrant can switch on. I could change that and simply enable it for everyone. However, if the Domain is then moved to a Registrar that does not support DNSSEC - there would be issues for the new Registrar.

On 2020/01/10 14:20, Gabdibé GAB-HINGONNE wrote:

...

Dear All, I support Barrack's proposal. Building the capacity of African end users on the general question related to the DNS is very important. Kind regards Gabdibé

Thank you Sarah for starting us on this. With the spirit of the new year, new decade, I would suggest that we issue a statement on our areas of focus for 2020. This will give us a goal and a roadmap on what we want to achieve as Afralo moving forward. Otherwise the already suggested topics will also do. On Wed, Jan 15, 2020, 15:51 Dr Eberhard W Lisse <el@lisse.na> wrote:

Michele,

you are of course right (never mind the issues of scale), but remember, this is the AFRALO/AfrICAN waffle session, where prepared resolution is read, approved by whoever could get their trip funded to sit around there and then consigned to the trash bin.

el

On 15/01/2020 13:56, Michele Neylon - Blacknight wrote:

...

Why would an “end user” care? Why would anyone want to make it more complicated and scary to get online? Surely this is an issue for industry and not the “end user”?

Most of the DNS abuse issues at the moment are due to providers not looking after their own networks / devices or acting on abuse reports.

It’s not a coincidence that we end up having to block entire countries from our network on a regular basis

While the goal of Barrack’s proposal might be honourable I don’t think it’s particularly practical or realistic

To use an analogy.

You can train someone to check the oil in their car, which in the DNS space could be akin to making sure that software was kept up to date

But pushing DNS abuse knowledge would be like expecting me to be able to strip my car down

Regards

Michele [...]

-- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el@lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 \ / Bachbrecht 10007, Namibia ;____/

_______________________________________________ AfrICANN mailing list AfrICANN@afrinic.net https://lists.afrinic.net/mailman/listinfo/africann

Barrack You’re actually making a strong argument for NOT doing this. Now if you were to switch “DNS abuse” for “computer security” or something else then maybe you’d have a case, but in so doing you’d put it even further outside ICANN’s remit. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com https://blacknight.blog / http://ceo.hosting/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow, R93 X265 ,Ireland Company No.: 370845 From: Barrack Otieno <otieno.barrack@gmail.com> Reply to: "africann@afrinic.net" <africann@afrinic.net> Date: Wednesday 15 January 2020 at 13:49 To: "africann@afrinic.net" <africann@afrinic.net> Cc: Afri-Discuss <afri-discuss@atlarge-lists.icann.org> Subject: Re: [AfrICANN-discuss] [AFRI-Discuss] Call for topics: Joint AFRALO-AfrICANN meeting for ICANN67 Hi Michele, Interesting analogy. In the Global North consumers are encouraged to do things themselves mostly and demand value for their money. In the global South consumers (end users) have no say, they are encouraged to be happy with what they get. We have propagated 3 R models in which the R is fickle and silent hence the perpetual need of 'expertise' to sort out issues that can be fixed by simple equiping the end user with some knowhow. Many Registrars and Resellers are encouraging the use of Website Builders meaning there will be more cases of end users building their own websites and related applications for use on the Internet, shouldn't they have some basic awareness on DNS Abuse? Regards On Wed, 15 Jan 2020, 2:58 pm Michele Neylon - Blacknight, <michele@blacknight.com<mailto:michele@blacknight.com>> wrote: Why would an “end user” care? Why would anyone want to make it more complicated and scary to get online? Surely this is an issue for industry and not the “end user”? Most of the DNS abuse issues at the moment are due to providers not looking after their own networks / devices or acting on abuse reports. It’s not a coincidence that we end up having to block entire countries from our network on a regular basis While the goal of Barrack’s proposal might be honourable I don’t think it’s particularly practical or realistic To use an analogy. You can train someone to check the oil in their car, which in the DNS space could be akin to making sure that software was kept up to date But pushing DNS abuse knowledge would be like expecting me to be able to strip my car down Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: Barrack Otieno <otieno.barrack@gmail.com<mailto:otieno.barrack@gmail.com>> Reply to: "africann@afrinic.net<mailto:africann@afrinic.net>" <africann@afrinic.net<mailto:africann@afrinic.net>> Date: Friday 10 January 2020 at 14:21 To: "el@lisse.NA" <el@lisse.NA> Cc: Afri-Discuss <afri-discuss@atlarge-lists.icann.org<mailto:afri-discuss@atlarge-lists.icann.org>>, "africann@afrinic.net<mailto:africann@afrinic.net>" <africann@afrinic.net<mailto:africann@afrinic.net>> Subject: Re: [AfrICANN-discuss] [AFRI-Discuss] Call for topics: Joint AFRALO-AfrICANN meeting for ICANN67 Good points Mark and El, I think the end user has been missing in the DNS Security conversation yet they are actually the ones who speak with their pockets, if i may use a Kenyan Proverb. An enlightened end user is an empowered end user. As we bring the next billion users online cases of DNS abuse will definately increase. If governments feel that industry players have not control they will definately step in and thats what we are avoiding. Regards On Fri, 10 Jan 2020, 4:55 pm Dr Eberhard W Lisse, <el@lisse.na<mailto:el@lisse.na>> wrote: Gabdibé, drafting a resolution (beforehand), or even debating a resolution, is going to achieve absolutely nothing. Mark, 50% lookups is actually almost worth than zero :-)-). And how many of those hit infrastructure actually in South Africa? Does the figure include the public ones from Google and Cloudflare? My view is that this only works All-or-Nothing, because noncompliant commercial resolver operators have a commercial advantage over complaint ones. Financial incentives may work as may financial or other sanctions. One could even make it part of the Accreditation that DNSSEC must be offered by the Registrars. But while the Registrars are usually the entities operating the DNS and as such have control over the end-user's DNS anyway, the chain of trust should go up to the end user and not just the Registrar. Talking to the banks has so far not been very effective, they are happy with HTTPS even though they forget to renew their certificate on a regular basis, never mind the expense. I don't have the answer either. If anyone has a technical "solution" or project going on, and is coming to Cancun, please feel free to propose a presentation at TechDay on the Monday. greetings, el On 10/01/2020 15:26, Mark Elkins wrote:

I also like the sound of Barrack's proposal. What exactly does "DNS Abuse" mean though?

If it is to try and get all important Domains DNSSEC Signed and for all DNS Resolvers to become DNSSEC aware - that would be a winner in my book!

Incidentally - about 50% of all DNS lookups in South Africa are DNSSEC aware. That's actually the easy bit. Just have the Internet Connection suppliers enable DNSSEC on their resolvers.

Getting the bulk or at least the important Domains DNSSEC Signed will be a bit more challenging but is quite possible; e.g. any domain for a website which may involve a financial transaction or deal with personal information.

On my Domain Registration and Hosting Platform, if I am running the Registrants DNS (Zone file), DNSSEC is simply an option the Registrant can switch on. I could change that and simply enable it for everyone. However, if the Domain is then moved to a Registrar that does not support DNSSEC - there would be issues for the new Registrar.

On 2020/01/10 14:20, Gabdibé GAB-HINGONNE wrote:

...

Dear All, I support Barrack's proposal. Building the capacity of African end users on the general question related to the DNS is very important. Kind regards Gabdibé

AfrICANN mailing list AfrICANN@afrinic.net<mailto:AfrICANN@afrinic.net> https://lists.afrinic.net/mailman/listinfo/africann

+1 for Barracks proposal as issues on capacity building can never be over emphasized. Sent from Yahoo Mail on Android On Tue, Jan 14, 2020 at 20:05, Gabdibé GAB-HINGONNE<gabdibegabhingonne@gmail.com> wrote: _______________________________________________ AFRI-Discuss mailing list AFRI-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/afri-discuss Homepage for the region: http://www.afralo.org Posting guidelines to ensure machine translations of emails sent to this list are more accurate: http://www.funredes.org/mistica/english/emec/method_emec/presentation.html#a... _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

+1 to Barrack's proposal. *WISDOM DONKOR* President & CEO Africa Open Data and Internet Research Foundation P.O. Box CT 2439, Cantonments, Accra | www.aodirf.org / www.afrigeocon.org Tel: +233 20 812 8851 Skype: wisdom_dk | Facebook: kwasi wisdom | Twitter: @wisdom_dk __________________________________________________ Specialization: E-government Network Infrastructure and E-application, Internet Governance, Open Data policies platforms & Community Development, Cyber Security, Domain Name Systems, Software Engineering, Event Planning & Management, On Fri, Jan 10, 2020 at 5:42 AM Barrack Otieno <otieno.barrack@gmail.com> wrote:

Dear Sarah and colleagues,

I would like to propose the following topic;

Building the Capacity of end users to curb DNS Abuse is Africa.

Regards

On Thu, 9 Jan 2020, 10:57 pm Robert Nkambwe via AFRI-Discuss, < afri-discuss@atlarge-lists.icann.org> wrote:

...

Thanks for sharing Sarah.

Robert

On Thursday, January 9, 2020, 10:41:47 PM GMT+3, Sarah Kiden < skiden@gmail.com> wrote:

Dear Colleagues,

I hope this email finds you well. The ICANN67 Meeting is scheduled for March 7 - 12, 2020 in Cancún, Mexico. As with previous ICANN meetings, we plan to hold the Joint AFRALO-AfrICANN meeting. We would like to invite you to submit topics for this session. Our previous statements have focused on issues like: evolving the ICANN Multistakeholder model, New gTLD Subsequent Procedures, enhancing ICANN accountability, etc. Please see our previous statements here <https://community.icann.org/display/AFRALO/Joint+AFRALO-AfrICANN+Statements+Workspace>.

Please see our proposed timeline: Call for topics: 9 - 16 January 2020 Topic announcement and call for drafting team: 17 - 22 January 2020 Drafting of Statement: 23 January - 13 February 2020 Send Statement to Staff for translation: 14 February 2020

Please send your suggested topics by *Thursday, 16 January 2020*, after which the drafting team will prepare a draft statement that will be shared with the rest of the members.

Looking forward to your contributions.

Kind regards,

Sarah Kiden AFRALO Secretariat _______________________________________________ AfrICANN mailing list AfrICANN@afrinic.net https://lists.afrinic.net/mailman/listinfo/africann _______________________________________________ AFRI-Discuss mailing list AFRI-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/afri-discuss

Homepage for the region: http://www.afralo.org

Posting guidelines to ensure machine translations of emails sent to this list are more accurate: http://www.funredes.org/mistica/english/emec/method_emec/presentation.html#a... _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

_______________________________________________ AFRI-Discuss mailing list AFRI-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/afri-discuss

Homepage for the region: http://www.afralo.org

Posting guidelines to ensure machine translations of emails sent to this list are more accurate: http://www.funredes.org/mistica/english/emec/method_emec/presentation.html#a... _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.