[ALAC] KSK Rollover on today's ALAC Agenda

Satish Babu sb at inapp.com
Wed Mar 28 02:27:45 UTC 2018


The summary looks good.

In addition, it may be good to institutionalize mechanisms to track/trace
the usage of DNSSEC in resolvers on an ongoing basis, so that this
situation would not occur in future.






satish



On Wed, Mar 28, 2018 at 1:24 AM, Barrack Otieno <otieno.barrack at gmail.com>
wrote:

> Hi Alan,
>
> Great Summary , how about use of webinars to enhance the Internet Users
> knowledge of the KSK roll over?
>
> Best
>
> On Tue, Mar 27, 2018 at 10:20 PM, Javier Rua <javrua at gmail.com> wrote:
>
>> Good summary of sense of ALAC.
>>
>>
>>
>> Javier Rúa-Jovet
>>
>> 1-787-396-6511
>> skype: javier.rua1
>> https://www.linkedin.com/in/javrua
>>
>> CONFIDENTIALITY NOTE: This electronic transmission contains information
>> belonging to Javier Rúa-Jovet Esq., and/or JRJ Consultants & Legal
>> Advisors, LLC which is confidential or legally privileged. The information
>> is intended only for the use of the individual or entity named above. If
>> you are not the intended recipient, please immediately advise the sender by
>> reply e-mail or telephone that this message has been inadvertently
>> transmitted to you and delete this e-mail from your system. If you have
>> received this transmission in error, you are hereby notified that any
>> disclosure, copying, distribution or the taking of any action in reliance
>> on the contents of such information is strictly prohibited. Thank you.
>>
>>
>>
>> *From: *Alan Greenberg <alan.greenberg at mcgill.ca>
>> *Sent: *Tuesday, March 27, 2018 3:16 PM
>> *To: *ALAC <alac at atlarge-lists.icann.org>
>> *Subject: *[ALAC] KSK Rollover on today's ALAC Agenda
>>
>>
>>
>> Here is my last try at summarizing things.
>>
>> What is wrong or missing?
>>
>> -----------------
>>
>> What I am hearing (extrapolated) is:
>>
>>    - Our community understands the need to roll the KSK but is divided
>>    on which path to follow at this point.
>>    - We want an intense awareness campaign including targetting ISPs,
>>    Telcos, Major industries. Use RIRs where they can identify potential DNS
>>    providers.
>>    - Information packet we can send to our community (ALSes, Individual
>>    Members) to get them to prompt their local ISPs or others and which can be
>>    similarly used by other constituencies within ICANN.
>>    - A holistic review of the situation (including a risk assessment of
>>    alternatives) in time for further discussion at ICANN62, including the then
>>    current state of whatever data is available and forecast of Sentinal
>>    availability.
>>    - We would like to better understand under what conditions a rollover
>>    date change is possible to avoid doing it at the end of a week.
>>
>>
>>
>> _______________________________________________
>> ALAC mailing list
>> ALAC at atlarge-lists.icann.org
>> https://atlarge-lists.icann.org/mailman/listinfo/alac
>>
>> At-Large Online: http://www.atlarge.icann.org
>> ALAC Working Wiki: https://community.icann.org/di
>> splay/atlarge/At-Large+Advisory+Committee+(ALAC)
>>
>
>
>
> --
> Barrack O. Otieno
> +254721325277
> +254733206359
> Skype: barrack.otieno
> PGP ID: 0x2611D86A
>
>
>
>
>
> _______________________________________________
> ALAC mailing list
> ALAC at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/alac
>
> At-Large Online: http://www.atlarge.icann.org
> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+
> Advisory+Committee+(ALAC)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20180328/cd26a0d2/attachment.html>


More information about the ALAC mailing list