Happy to see this proposal! Fully in agreement with Nick that bogging down the policy with implementation details is a bad idea. It might be relevant to operators to tie down the "unable to discover" component. What is considered "reasonable efforts" in this context? -- Tom Strickx Principal Network Engineer AS13335 - Cloudflare
On Fri, Jun 6, 2025 at 1:05 PM David Farmer via routing-wg < [email protected]> wrote: > > On Fri, Jun 6, 2025 at 6:18 AM Nick Hilliard <[email protected]> wrote: > >> Radu Anghel via routing-wg wrote on 06/06/2025 11:33: >> >> nitpicking: to avoid CAs being deregistered at different intervals after >> short months like February the 3 months could be specified as 90 days. >> >> >> "more than three months" should give the RIPE NCC enough leeway not to be >> forced to take action on specific days which was a bad idea, for example, >> having a revocation happen on a public holiday and that sort of thing. >> >> The point is that the delegation is revoked after notice, and enough time >> for the operator in question to take action. The specific day is not that >> relevant, i.e. if it's + a couple of days, that's not that big a deal. >> > > +1 > > However, it might also be a good idea for revocations to occur only on a > regularly scheduled and published day and time rather than somewhat > randomly throughout the month. For example, revocations should occur at > noon UTC on the first Tuesday of the month, unless that is a > public holiday, then on the second Tuesday of the month. The point being to > avoid surprises to the extent possible. > > Thanks > > -- > =============================================== > David Farmer Email:[email protected] > Networking & Telecommunication Services > Office of Information Technology > University of Minnesota > 2218 University Ave SE Phone: 612-626-0815 > Minneapolis, MN 55414-3029 Cell: 612-812-9952 > =============================================== > ----- > To unsubscribe from this mailing list or change your subscription options, > please visit: https://mailman.ripe.net/mailman3/lists/routing-wg.ripe.net/ > As we have migrated to Mailman 3, you will need to create an account with > the email matching your subscription before you can change your settings. > More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/routing-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
