Re: [sidr] CP changes in response to WGLC comments
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sidr] CP changes in response to WGLC comments



On Nov 4, 2009, at 11:41 AM, Randy Bush wrote:
...
but, in that case, is not the largest part of the problem still getting
the grandparent(s) to swing the covering resource set(s) to new
parent(s)? is not the cp-compliance issue but one very small part of of
the criteria on which i and my grandparent(s) choose new parent(s)?

Use case:

1) New CP comes out and specifies minimum standards in the area of Facility, Management, And Operational Controls (rather the delegation of such to the CPS)

2) Existing RPKI service providers need to assess this and decide implications therein

3) If existing RPKI providers can't/won't meet the requirements, and exit the business, they want to do so within 1 month due to 9.12.2 (to prevent having non-CP compliant certs out there)

You've got the time left over, after the RPKI service provider exits the field, to scramble with the grandparent to select new service providers...

Hence, my suggestion that 30 days notice is rather short.
/John


Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.