Informal meeting at IETF 103
There will be an informal discussion of DNS root KSK futures at IETF 103 on Friday, November 9, at 0900 local (Bangkok) time in room Chitlada 3. The purpose is to allow IETF participants to ask questions and propose ideas for how the DNS root KSK should be maintained in the future. Suggestions from the mic lines at recent meeting include suggestions for fixed rollover schedules, suggestions for data collection before the next rollover, standby KSKs and how they would affect the rollover schedule, and how resolver software vendors' actions can be taken into account. The discussion is expected to last for one hour or less. Unfortunately, there is no remote participation for the Friday sessions, so the meeting will be limited to those in the room. However, I will make a recording to create notes on what is said. --Paul Hoffman
Hi all, I don't attend IETF103 in person, so I won't be in the room. Can someone kindly relay via some remote tools such as zoom, hangouts, skype, jabber and/or slack? I'd like to hear conversations in the room and give comment via chat if any. Best regards, -- Yoshiro YONEYA On Fri, 26 Oct 2018 19:48:23 +0000 Paul Hoffman <paul.hoffman@icann.org> wrote:
There will be an informal discussion of DNS root KSK futures at IETF 103 on Friday, November 9, at 0900 local (Bangkok) time in room Chitlada 3. The purpose is to allow IETF participants to ask questions and propose ideas for how the DNS root KSK should be maintained in the future. Suggestions from the mic lines at recent meeting include suggestions for fixed rollover schedules, suggestions for data collection before the next rollover, standby KSKs and how they would affect the rollover schedule, and how resolver software vendors' actions can be taken into account. The discussion is expected to last for one hour or less.
Unfortunately, there is no remote participation for the Friday sessions, so the meeting will be limited to those in the room. However, I will make a recording to create notes on what is said.
--Paul Hoffman
+1, if possible. Thanks! Eric
On Oct 29, 2018, at 12:43 AM, Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> wrote:
Hi all,
I don't attend IETF103 in person, so I won't be in the room. Can someone kindly relay via some remote tools such as zoom, hangouts, skype, jabber and/or slack? I'd like to hear conversations in the room and give comment via chat if any.
Best regards,
-- Yoshiro YONEYA
On Fri, 26 Oct 2018 19:48:23 +0000 Paul Hoffman <paul.hoffman@icann.org> wrote:
There will be an informal discussion of DNS root KSK futures at IETF 103 on Friday, November 9, at 0900 local (Bangkok) time in room Chitlada 3. The purpose is to allow IETF participants to ask questions and propose ideas for how the DNS root KSK should be maintained in the future. Suggestions from the mic lines at recent meeting include suggestions for fixed rollover schedules, suggestions for data collection before the next rollover, standby KSKs and how they would affect the rollover schedule, and how resolver software vendors' actions can be taken into account. The discussion is expected to last for one hour or less.
Unfortunately, there is no remote participation for the Friday sessions, so the meeting will be limited to those in the room. However, I will make a recording to create notes on what is said.
--Paul Hoffman
_______________________________________________ ksk-rollover mailing list ksk-rollover@icann.org https://mm.icann.org/mailman/listinfo/ksk-rollover
I’m not 100% certain about my Friday schedule yet as I am still waiting for details on some ISOC meetings. But if I am able to attend the KSK meeting I will be glad to share the session via Zoom. I should know my availability by later in this week. Dan -- Dan York Director, Content & Web Strategy, Internet Society york@isoc.org<mailto:york@isoc.org> +1-802-735-1624 Jabber: york@jabber.isoc.org<mailto:york@jabber.isoc.org> Skype: danyork http://twitter.com/danyork http://www.internetsociety.org/ On Oct 29, 2018, at 12:43 AM, Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp<mailto:yoshiro.yoneya@jprs.co.jp>> wrote: Hi all, I don't attend IETF103 in person, so I won't be in the room. Can someone kindly relay via some remote tools such as zoom, hangouts, skype, jabber and/or slack? I'd like to hear conversations in the room and give comment via chat if any. Best regards, -- Yoshiro YONEYA On Fri, 26 Oct 2018 19:48:23 +0000 Paul Hoffman <paul.hoffman@icann.org<mailto:paul.hoffman@icann.org>> wrote: There will be an informal discussion of DNS root KSK futures at IETF 103 on Friday, November 9, at 0900 local (Bangkok) time in room Chitlada 3. The purpose is to allow IETF participants to ask questions and propose ideas for how the DNS root KSK should be maintained in the future. Suggestions from the mic lines at recent meeting include suggestions for fixed rollover schedules, suggestions for data collection before the next rollover, standby KSKs and how they would affect the rollover schedule, and how resolver software vendors' actions can be taken into account. The discussion is expected to last for one hour or less. Unfortunately, there is no remote participation for the Friday sessions, so the meeting will be limited to those in the room. However, I will make a recording to create notes on what is said. --Paul Hoffman _______________________________________________ ksk-rollover mailing list ksk-rollover@icann.org<mailto:ksk-rollover@icann.org> https://mm.icann.org/mailman/listinfo/ksk-rollover
Based on some requests from folks who are leaving the IETF meeting early, I have also reserved a meeting room for 1600-1700 Wednesday afternoon (local time), Pagoda Room on the 4th floor. And just to emphasize: the purpose of this week's informal gatherings is to let folks in the IETF community chat about their ideas in front of other IETFers. This is similar to the KSK-related mic lines at the DNS-OARC and RIPE meetings a few weeks ago. These IETF side-meetings really are just slightly-better-organized hallway discussions. Given the wide range of proposals we have already heard, it is good to get a bit of face-to-face sharing going early. We won't start formal planning about the KSK futures until after the rollover process is complete*. When we do, we'll do it in discussion environments that are much more inclusive than these informal IETF side-meetings or the mic lines at other technical meetings. --Paul Hoffman * Y'all did remember that the rollover isn't complete until we revoke KSK-2010 on 11 January 2019, yes? See <https://www.icann.org/en/system/files/files/ksk-rollover-operational-impleme...>, with the dates modified by <https://www.icann.org/en/system/files/files/2018-ksk-roll-operational-implem...>.
There will be an informal discussion of DNS root KSK futures at IETF 103 on Friday, November 9, at 0900 local (Bangkok) time in room Chitlada 3. The purpose is to allow IETF participants to ask questions and propose ideas for how the DNS root KSK should be maintained in the future. Suggestions from the mic lines at recent meeting include suggestions for fixed rollover schedules, suggestions for data collection before the next rollover, standby KSKs and how they would affect the rollover schedule, and how resolver software vendors' actions can be taken into account. The discussion is expected to last for one hour or less.
On Oct 29 2018, Paul Hoffman wrote:
* Y'all did remember that the rollover isn't complete until we revoke KSK-2010 on 11 January 2019, yes?
Or maybe 70 days later (22 March) when the revoked KSK-2010 disappears from the root zone? -- Chris Thompson Email: cet1@cam.ac.uk
On Oct 29, 2018, at 9:08 AM, Chris Thompson <cet1@cam.ac.uk> wrote:
On Oct 29 2018, Paul Hoffman wrote:
* Y'all did remember that the rollover isn't complete until we revoke KSK-2010 on 11 January 2019, yes?
Or maybe 70 days later (22 March) when the revoked KSK-2010 disappears from the root zone?
Good catch! We know that some software that does DNSSEC validation doesn't implement RFC 5011. The fact that the REVOKE bit is turned on in the record for KSK-2010 in DNSKEY RRset won't mean anything to systems running that software unless they also update their trust anchor files to only include KSK-2017. --Paul Hoffman
On Mon, 29 Oct 2018 at 12:21, Paul Hoffman <paul.hoffman@icann.org> wrote:
On Oct 29, 2018, at 9:08 AM, Chris Thompson <cet1@cam.ac.uk> wrote:
On Oct 29 2018, Paul Hoffman wrote:
* Y'all did remember that the rollover isn't complete until we revoke KSK-2010 on 11 January 2019, yes?
Or maybe 70 days later (22 March) when the revoked KSK-2010 disappears from the root zone?
Good catch! We know that some software that does DNSSEC validation doesn't implement RFC 5011. The fact that the REVOKE bit is turned on in the record for KSK-2010 in DNSKEY RRset won't mean anything to systems running that software unless they also update their trust anchor files to only include KSK-2017.
Although anything that doesn't implement 5011 should already be experiencing problems since KSK-2010 is no longer being used to sign anything. Any of those systems that are not experiencing problems now must have had their trust anchor manually updated, and revocation or removal of KSK-2010 should be irrelevant to them. I would expect the only problems to be exposed by revocation or removal of KSK-2010 to be bugs in 5011 implementations.
On Oct 30 2018, Matthew Pounsett wrote:
On Mon, 29 Oct 2018 at 12:21, Paul Hoffman <paul.hoffman@icann.org> wrote:
On Oct 29, 2018, at 9:08 AM, Chris Thompson <cet1@cam.ac.uk> wrote:
On Oct 29 2018, Paul Hoffman wrote:
* Y'all did remember that the rollover isn't complete until we revoke KSK-2010 on 11 January 2019, yes?
Or maybe 70 days later (22 March) when the revoked KSK-2010 disappears from the root zone?
Good catch! We know that some software that does DNSSEC validation doesn't implement RFC 5011. The fact that the REVOKE bit is turned on in the record for KSK-2010 in DNSKEY RRset won't mean anything to systems running that software unless they also update their trust anchor files to only include KSK-2017.
Although anything that doesn't implement 5011 should already be experiencing problems since KSK-2010 is no longer being used to sign anything. Any of those systems that are not experiencing problems now must have had their trust anchor manually updated, and revocation or removal of KSK-2010 should be irrelevant to them. I would expect the only problems to be exposed by revocation or removal of KSK-2010 to be bugs in 5011 implementations.
This surely isn't right? Validators using statically configured trust anchors (e.g. using "trusted-keys" rather than "managed-keys" in BIND) and having both KSK-2010 and KSK-2017 configured as trust anchors will go on working just fine. If this wasn't the case, they would not have been able to add a trust anchor for KSK-2017 in advance of the rollover. At some point we will want to see some statistics about RFC 8145 signals that indicate trusting only KSK-2017. Maybe there is even some such data available already, even if it isn't shown in the graphs at http://root-trust-anchor-reports.research.icann.org/ ? (It is interesting, though, that those graphs show only a rather modest decrease in the KSK-2010-only signals during October.) -- Chris Thompson Email: cet1@cam.ac.uk
On Mon, 5 Nov 2018 at 10:23, Chris Thompson <cet1@cam.ac.uk> wrote:
On Oct 30 2018, Matthew Pounsett wrote:
On Mon, 29 Oct 2018 at 12:21, Paul Hoffman <paul.hoffman@icann.org> wrote:
On Oct 29, 2018, at 9:08 AM, Chris Thompson <cet1@cam.ac.uk> wrote:
On Oct 29 2018, Paul Hoffman wrote:
* Y'all did remember that the rollover isn't complete until we revoke KSK-2010 on 11 January 2019, yes?
Or maybe 70 days later (22 March) when the revoked KSK-2010 disappears from the root zone?
Good catch! We know that some software that does DNSSEC validation doesn't implement RFC 5011. The fact that the REVOKE bit is turned on in the record for KSK-2010 in DNSKEY RRset won't mean anything to systems running that software unless they also update their trust anchor files to only include KSK-2017.
Although anything that doesn't implement 5011 should already be experiencing problems since KSK-2010 is no longer being used to sign anything. Any of those systems that are not experiencing problems now must have had their trust anchor manually updated, and revocation or removal of KSK-2010 should be irrelevant to them. I would expect the only problems to be exposed by revocation or removal of KSK-2010 to be bugs in 5011 implementations.
This surely isn't right? Validators using statically configured trust anchors (e.g. using "trusted-keys" rather than "managed-keys" in BIND) and having both KSK-2010 and KSK-2017 configured as trust anchors will go on working just fine. If this wasn't the case, they would not have been able to add a trust anchor for KSK-2017 in advance of the rollover.
I thought that's what I said. :) Although I can see now how I may have assumed too much shared understanding in my first sentence. It should probably have read "Anything that doesn't implement 5011 and wasn't manually updated...". That is clarified in the very next sentence, though. Non-5011 systems that aren't already experiencing problems due to the key roll must have had their trust anchors updated manually (or by software update, or some other method). Revocation and removal of KSK-2010 from the root zone will (should?) be irrelevant to these systems. The only case I can think of where it would be a problem is if, for some reason, an implementation requires all configured trust anchors to be present in the zone. In that pathological case operators would need to take a second configuration step to remove KSK-2010 from their trust anchor list. It won't be entirely irrelevant to software that implements 5011 because they will react to revocation, but it shouldn't have an impact on their ability to validate using KSK-2017.. unless there are bugs (which is what I was getting at in the final sentence of that paragraph).
Likewise Sent from my V6 Engine! メデル ラミレズ On 29 Oct 2018, at 11:18 PM, Dan York <york@isoc.org> wrote: I’m not 100% certain about my Friday schedule yet as I am still waiting for details on some ISOC meetings. But if I am able to attend the KSK meeting I will be glad to share the session via Zoom. I should know my availability by later in this week. Dan -- Dan York Director, Content & Web Strategy, Internet Society york@isoc.org +1-802-735-1624 Jabber: york@jabber.isoc.org Skype: danyork http://twitter.com/danyork http://www.internetsociety.org/ On Oct 29, 2018, at 12:43 AM, Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> wrote: Hi all, I don't attend IETF103 in person, so I won't be in the room. Can someone kindly relay via some remote tools such as zoom, hangouts, skype, jabber and/or slack? I'd like to hear conversations in the room and give comment via chat if any. Best regards, -- Yoshiro YONEYA On Fri, 26 Oct 2018 19:48:23 +0000 Paul Hoffman <paul.hoffman@icann.org> wrote: There will be an informal discussion of DNS root KSK futures at IETF 103 on Friday, November 9, at 0900 local (Bangkok) time in room Chitlada 3. The purpose is to allow IETF participants to ask questions and propose ideas for how the DNS root KSK should be maintained in the future. Suggestions from the mic lines at recent meeting include suggestions for fixed rollover schedules, suggestions for data collection before the next rollover, standby KSKs and how they would affect the rollover schedule, and how resolver software vendors' actions can be taken into account. The discussion is expected to last for one hour or less. Unfortunately, there is no remote participation for the Friday sessions, so the meeting will be limited to those in the room. However, I will make a recording to create notes on what is said. --Paul Hoffman _______________________________________________ ksk-rollover mailing list ksk-rollover@icann.org https://mm.icann.org/mailman/listinfo/ksk-rollover _______________________________________________ ksk-rollover mailing list ksk-rollover@icann.org https://mm.icann.org/mailman/listinfo/ksk-rollover -- This e-mail message (including attachments, if any) is intended for the use of the individual or the entity to whom it is addressed and may contain information that is privileged, proprietary, confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and delete this E-mail message immediately.
Hi all, Is there any way for remote participation? If any, please let's know and it is very appreciated :-) -- Yoshiro YONEYA On Mon, 29 Oct 2018 15:18:21 +0000 Dan York <york@isoc.org> wrote:
I’m not 100% certain about my Friday schedule yet as I am still waiting for details on some ISOC meetings. But if I am able to attend the KSK meeting I will be glad to share the session via Zoom.
I should know my availability by later in this week.
Dan -- Dan York Director, Content & Web Strategy, Internet Society york@isoc.org<mailto:york@isoc.org> +1-802-735-1624 Jabber: york@jabber.isoc.org<mailto:york@jabber.isoc.org> Skype: danyork http://twitter.com/danyork
http://www.internetsociety.org/
On Oct 29, 2018, at 12:43 AM, Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp<mailto:yoshiro.yoneya@jprs.co.jp>> wrote:
Hi all,
I don't attend IETF103 in person, so I won't be in the room. Can someone kindly relay via some remote tools such as zoom, hangouts, skype, jabber and/or slack? I'd like to hear conversations in the room and give comment via chat if any.
Best regards,
-- Yoshiro YONEYA
On Fri, 26 Oct 2018 19:48:23 +0000 Paul Hoffman <paul.hoffman@icann.org<mailto:paul.hoffman@icann.org>> wrote:
There will be an informal discussion of DNS root KSK futures at IETF 103 on Friday, November 9, at 0900 local (Bangkok) time in room Chitlada 3. The purpose is to allow IETF participants to ask questions and propose ideas for how the DNS root KSK should be maintained in the future. Suggestions from the mic lines at recent meeting include suggestions for fixed rollover schedules, suggestions for data collection before the next rollover, standby KSKs and how they would affect the rollover schedule, and how resolver software vendors' actions can be taken into account. The discussion is expected to last for one hour or less.
Unfortunately, there is no remote participation for the Friday sessions, so the meeting will be limited to those in the room. However, I will make a recording to create notes on what is said.
--Paul Hoffman
_______________________________________________ ksk-rollover mailing list ksk-rollover@icann.org<mailto:ksk-rollover@icann.org> https://mm.icann.org/mailman/listinfo/ksk-rollover
Hi all, The Chitlada 3 room seems to have audio streaming devices. Cite from <http://ietf103.conf.meetecho.com/> RTSP: <http://chitlada3.conf.meetecho.com/audio/redirect/rtsp> MP3: <http://ietf103streaming.dnsalias.net/ietf/ietf1036.m3u> Can someone please turn on audio streaming devices? -- Yoshiro YONEYA On Fri, 9 Nov 2018 10:30:59 +0900 Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> wrote:
Hi all,
Is there any way for remote participation? If any, please let's know and it is very appreciated :-)
-- Yoshiro YONEYA
On Mon, 29 Oct 2018 15:18:21 +0000 Dan York <york@isoc.org> wrote:
I’m not 100% certain about my Friday schedule yet as I am still waiting for details on some ISOC meetings. But if I am able to attend the KSK meeting I will be glad to share the session via Zoom.
I should know my availability by later in this week.
Dan -- Dan York Director, Content & Web Strategy, Internet Society york@isoc.org<mailto:york@isoc.org> +1-802-735-1624 Jabber: york@jabber.isoc.org<mailto:york@jabber.isoc.org> Skype: danyork http://twitter.com/danyork
http://www.internetsociety.org/
On Oct 29, 2018, at 12:43 AM, Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp<mailto:yoshiro.yoneya@jprs.co.jp>> wrote:
Hi all,
I don't attend IETF103 in person, so I won't be in the room. Can someone kindly relay via some remote tools such as zoom, hangouts, skype, jabber and/or slack? I'd like to hear conversations in the room and give comment via chat if any.
Best regards,
-- Yoshiro YONEYA
On Fri, 26 Oct 2018 19:48:23 +0000 Paul Hoffman <paul.hoffman@icann.org<mailto:paul.hoffman@icann.org>> wrote:
There will be an informal discussion of DNS root KSK futures at IETF 103 on Friday, November 9, at 0900 local (Bangkok) time in room Chitlada 3. The purpose is to allow IETF participants to ask questions and propose ideas for how the DNS root KSK should be maintained in the future. Suggestions from the mic lines at recent meeting include suggestions for fixed rollover schedules, suggestions for data collection before the next rollover, standby KSKs and how they would affect the rollover schedule, and how resolver software vendors' actions can be taken into account. The discussion is expected to last for one hour or less.
Unfortunately, there is no remote participation for the Friday sessions, so the meeting will be limited to those in the room. However, I will make a recording to create notes on what is said.
--Paul Hoffman
_______________________________________________ ksk-rollover mailing list ksk-rollover@icann.org<mailto:ksk-rollover@icann.org> https://mm.icann.org/mailman/listinfo/ksk-rollover
_______________________________________________ ksk-rollover mailing list ksk-rollover@icann.org https://mm.icann.org/mailman/listinfo/ksk-rollover
Yoshiro,
On Nov 9, 2018, at 8:30 AM, Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> wrote:
Is there any way for remote participation? If any, please let's know and it is very appreciated :-)
I am NOT able to participate in the KSK Rollover discussion this morning (Internet Society Board meeting happening at the same time) and so I cannot provide remote participation. Regards, Dan -- Dan York Director, Content & Web Strategy, Internet Society york@isoc.org +1-802-735-1624 Jabber: york@jabber.isoc.org Skype: danyork http://twitter.com/danyork http://www.internetsociety.org/
I am wiling to scribe/ask questions on behalf of remote participants. However that depends on there being an appropriate tool available. On 9/11/18 8:51 am, Dan York wrote:
Yoshiro,
On Nov 9, 2018, at 8:30 AM, Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> wrote:
Is there any way for remote participation? If any, please let's know and it is very appreciated :-)
I am NOT able to participate in the KSK Rollover discussion this morning (Internet Society Board meeting happening at the same time) and so I cannot provide remote participation.
Regards, Dan
-- Dan York Director, Content & Web Strategy, Internet Society york@isoc.org +1-802-735-1624 Jabber: york@jabber.isoc.org Skype: danyork http://twitter.com/danyork
http://www.internetsociety.org/
_______________________________________________ ksk-rollover mailing list ksk-rollover@icann.org https://mm.icann.org/mailman/listinfo/ksk-rollover
-- Kal Feher Melbourne, Australia
Hi Kal, Thank you very much your offer! How about using dnsop WG's jabber room <xmpp:dnsop@jabber.ietf.org> ? -- Yoshiro YONEYA On Fri, 9 Nov 2018 08:54:02 +0700 Kal Feher <icann@feherfamily.org> wrote:
I am wiling to scribe/ask questions on behalf of remote participants. However that depends on there being an appropriate tool available.
On 9/11/18 8:51 am, Dan York wrote:
Yoshiro,
On Nov 9, 2018, at 8:30 AM, Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> wrote:
Is there any way for remote participation? If any, please let's know and it is very appreciated :-)
I am NOT able to participate in the KSK Rollover discussion this morning (Internet Society Board meeting happening at the same time) and so I cannot provide remote participation.
Regards, Dan
-- Dan York Director, Content & Web Strategy, Internet Society york@isoc.org +1-802-735-1624 Jabber: york@jabber.isoc.org Skype: danyork http://twitter.com/danyork
http://www.internetsociety.org/
_______________________________________________ ksk-rollover mailing list ksk-rollover@icann.org https://mm.icann.org/mailman/listinfo/ksk-rollover
-- Kal Feher Melbourne, Australia
Hi Dan, Thank you, please don't mind :-) -- Yoshiro YONEYA On Fri, 9 Nov 2018 01:51:20 +0000 Dan York <york@isoc.org> wrote:
Yoshiro,
On Nov 9, 2018, at 8:30 AM, Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> wrote:
Is there any way for remote participation? If any, please let's know and it is very appreciated :-)
I am NOT able to participate in the KSK Rollover discussion this morning (Internet Society Board meeting happening at the same time) and so I cannot provide remote participation.
Regards, Dan
-- Dan York Director, Content & Web Strategy, Internet Society york@isoc.org +1-802-735-1624 Jabber: york@jabber.isoc.org Skype: danyork http://twitter.com/danyork
How do I opt out of all of these emails? Personally Yours, Jan LLoyd President/CFO This message (and any attachments) contain confidential information and is intended only for the use of the person(s) named above. If you are not the intended recipient, any review, dissemination, distribution or duplication of this communication is strictly prohibited. In addition, please immediately contact the sender by reply e-mail and destroy all copies of the original message. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. Any views or opinions presented in the e-mail above are solely those of the author and do not necessarily represent those of Personally Yours, as such the company will not accept any liability as a result of such communication(s). Agreements entered into by company agents are not considered binding without separate documentation executed with an original non-electronic signature, unless otherwise approved by management. ________________________________________ From: ksk-rollover <ksk-rollover-bounces@icann.org> on behalf of Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp> Sent: Sunday, October 28, 2018 11:43 PM To: ksk-rollover@icann.org Subject: Re: [ksk-rollover] Informal meeting at IETF 103 Hi all, I don't attend IETF103 in person, so I won't be in the room. Can someone kindly relay via some remote tools such as zoom, hangouts, skype, jabber and/or slack? I'd like to hear conversations in the room and give comment via chat if any. Best regards, -- Yoshiro YONEYA On Fri, 26 Oct 2018 19:48:23 +0000 Paul Hoffman <paul.hoffman@icann.org> wrote:
There will be an informal discussion of DNS root KSK futures at IETF 103 on Friday, November 9, at 0900 local (Bangkok) time in room Chitlada 3. The purpose is to allow IETF participants to ask questions and propose ideas for how the DNS root KSK should be maintained in the future. Suggestions from the mic lines at recent meeting include suggestions for fixed rollover schedules, suggestions for data collection before the next rollover, standby KSKs and how they would affect the rollover schedule, and how resolver software vendors' actions can be taken into account. The discussion is expected to last for one hour or less.
Unfortunately, there is no remote participation for the Friday sessions, so the meeting will be limited to those in the room. However, I will make a recording to create notes on what is said.
--Paul Hoffman
_______________________________________________ ksk-rollover mailing list ksk-rollover@icann.org https://mm.icann.org/mailman/listinfo/ksk-rollover
Jan LLoyd writes:
How do I opt out of all of these emails?
Every message to the list, including yours, includes this footer with a link to the mailing list subscriber portal: ksk-rollover mailing list ksk-rollover@icann.org https://mm.icann.org/mailman/listinfo/ksk-rollover Visiting that page has an option to unsubscribe. It also has this in the headers: List-Unsubscribe: <https://mm.icann.org/mailman/options/ksk-rollover>, <mailto:ksk-rollover-request@icann.org?subject=unsubscribe> So sending a message to ksk-rollover-request@icann.org with the Subject header set to "unsubscribe" will also remove you.
Thank you sir. Personally Yours, Jan LLoyd President/CFO This message (and any attachments) contain confidential information and is intended only for the use of the person(s) named above. If you are not the intended recipient, any review, dissemination, distribution or duplication of this communication is strictly prohibited. In addition, please immediately contact the sender by reply e-mail and destroy all copies of the original message. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. Any views or opinions presented in the e-mail above are solely those of the author and do not necessarily represent those of Personally Yours, as such the company will not accept any liability as a result of such communication(s). Agreements entered into by company agents are not considered binding without separate documentation executed with an original non-electronic signature, unless otherwise approved by management. ________________________________________ From: Dave Lawrence <tale@dd.org> Sent: Tuesday, October 30, 2018 1:50 PM To: Jan LLoyd Cc: ksk-rollover@icann.org Subject: Re: [ksk-rollover] Informal meeting at IETF 103 Jan LLoyd writes:
How do I opt out of all of these emails?
Every message to the list, including yours, includes this footer with a link to the mailing list subscriber portal: ksk-rollover mailing list ksk-rollover@icann.org https://mm.icann.org/mailman/listinfo/ksk-rollover Visiting that page has an option to unsubscribe. It also has this in the headers: List-Unsubscribe: <https://mm.icann.org/mailman/options/ksk-rollover>, <mailto:ksk-rollover-request@icann.org?subject=unsubscribe> So sending a message to ksk-rollover-request@icann.org with the Subject header set to "unsubscribe" will also remove you.
Greetings again. The two very informal side-meetings at the IETF went well. The first had about 35 people, the second about 20. Recordings are here: https://www.proper.com/2018-11-07-dnssec-root-ksk-futures.mp3 https://www.proper.com/2018-11-09-dnssec-root-ksk-futures.mp3 (Those are stored on my personal web server, so they may disappear after a while...) Many thanks to Mukund Sivaraman for the first recording: I forgot to bring the recorder, and when I said so out loud at the beginning of the meeting, he quickly started recording from his own computer. As I emphasized at the meetings, this list is the perfect place for people to continue to have discussions about what they would like to see for the KSK in the future. At some point next year, ICANN will have a more formal way for the discussion to proceed. In the meantime, having this community bounce ideas off each other will certainly help prepare for the more formal discussions. --Paul Hoffman On Oct 26, 2018, at 12:48 PM, Paul Hoffman <paul.hoffman@icann.org> wrote:
There will be an informal discussion of DNS root KSK futures at IETF 103 on Friday, November 9, at 0900 local (Bangkok) time in room Chitlada 3. The purpose is to allow IETF participants to ask questions and propose ideas for how the DNS root KSK should be maintained in the future. Suggestions from the mic lines at recent meeting include suggestions for fixed rollover schedules, suggestions for data collection before the next rollover, standby KSKs and how they would affect the rollover schedule, and how resolver software vendors' actions can be taken into account. The discussion is expected to last for one hour or less.
Unfortunately, there is no remote participation for the Friday sessions, so the meeting will be limited to those in the room. However, I will make a recording to create notes on what is said.
participants (11)
-
Chris Thompson -
Dan York -
Dave Lawrence -
Eric Osterweil -
Jan LLoyd -
Kal Feher -
Mathias HOUNGBO -
Matthew Pounsett -
Medel Ramirez -
Paul Hoffman -
Yoshiro YONEYA