I won't be in Bangkok, so I won't be able to participate. In my view, there were two specific problems that dominated the rollover problem. The first was the inability to determine the configuration of querying resolver. The second was the in ability to notify resolver operators if it was evident their software was misconfigured.
Although these two problems became evident and important during the rollover, they also apply more generally, so if the IETF is going to work on improvements, it would be helpful if the improvements would be useful in the event of other configuration or operational issues. Ideally, every resolver that issues a query would provide configuration information, perhaps in a controlled fashion, and there should also be a way to notify the resolver operator of operational problems. We will need to do more rollovers in the future, driven at least in part by the need to change algorithms. I would hope we can work toward making these relatively straightforward. Thanks, Steve On Mon, Oct 29, 2018 at 12:36 PM Dave Lawrence <t...@dd.org> wrote: > Dave Lawrence writes: > > Count me as another, for that very reason. When I first saw Paul's > > message I thought, "oh that's a shame" but figured it to be fairly > > set. If there's flexibility for making the meeting happen earlier in > > the week, I'd be interested. > > Following up to my own message, since this was further down in my box > on another list... > > ------- start of forwarded message (RFC 934 encapsulation) ------- > From: Paul Hoffman <paul.hoff...@icann.org> > Subject: Re: [ksk-rollover] Informal meeting at IETF 103 > To: "ksk-rollo...@icann.org" <ksk-rollo...@icann.org> > > 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. > > [...] > ------- end ------- > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop >
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
