On 11/01/2015 15:31, Jim Reid wrote:
Though I'd prefer "once a year" to "every second RIPE meeting" in case the number of RIPE meetings per year changes or one of them gets cancelled say because the Kras catches fire. And while the selection process may well be aligned with a RIPE meeting, I would be very uncomfortable if that gave the impression that the meeting took precedence over the mailing list when it came to making the consensus decision.
I put some thought into this before committing to email. "Once a year" doesn't work either because if you have variations in the RIPE meeting dates (e.g. RIPE67 in mid-oct, RIPE69 in mid-nov), then "once a year" means that half of the time, you will need to move forward the selection slot at the DNS WG session to the previous RIPE meeting if you want to stay consistent with the selection procedure. There are many other ways to say this which will get around the problem, e.g. "at least once every 15 months" or "once in every calendar year, at a RIPE meeting, and in the second half of the year", and the qualify them by saying that if there were problems, that the selection process be held in the next scheduled RIPE meeting anyway. But it was fewer words and simpler to say "every second RIPE meeting". If the number of RIPE meeting changes, the protocol can be changed. If a RIPE meeting is unexpectedly cancelled or postponed, there will be bigger problems to deal with than this. Nick