Randy,

Thanks for the quick feedback. I'll reply on,y to what appear to be the remaining, unresolved issues:

 > Randy, can you elaborate on the nature of current IANA allocations
 made to non-RIRs? Legacy allocations are not addressed in this
 paragraph, just the current allocation system.

we're talking about certs.  iana will be issuing certs for those
allocations, whether legacy, strawberry, or cowboy junkies.

I don't mean to seem dense, but I still don't see a characterization here
that I could cite in  the CP.

 > The intent is to help ensure that each CA (as amended below, in 2.2)
 has a CPS

nice intent.  i am not sure it will be met and not sure it MUST be for
the internet to keep working.  maybe a SHOULD is more realistic.

We'll change this to a SHOULD, which also is consistent with Andrei's most recent message as well.

> NEW: When generating subject names, CAs SHOULD use a mechanism (such as
        those described [cert-profile]) to minimize the likelihood that
        the subject name is a trademark, service mark, etc.

why not stick to has no meaning?  mentioning trade/service marks is an
unnecessary invitation to people we would rather not have to talk to
about this stuff.

Sean asked us to add the trademark text, because it is common in CPs. I agree that it is inappropriate to impose a burden of this sort on the orgs that we are asking to act as CAs here. Not mentioning this issue does not provide "cover" for these orgs. Saying that a CA that employs the recommended name gen technique, or an analogous mechanism, gets a pass, may provide cover, so I think it is worthwhile. But, if most WG members are more comfortable with deleting this, let us know, and we'll remove it.


 NEW:   It is RECOMMENDED that the renewed certificate be issued and
        published at least 24 hours prior to the expiration of the
        certificate that it replaces.

and hopefully considerably earlier.

if i am four down the chain, and someone a hop or two up has a cert soon
to expire, that 24 hour window is a great cause of unnecessary
adrenaline.  if you have a time there, i would prefer a week, especially
considering long processing cycles discussed by rirs.

At first I though this interacted with the key rollover doc, but this text talks about cert renewal, so we can make the recommended renewal interval "at least 1 week" instead of "at lest 24 hours."


 NEW:   Each CA MUST maintain procedural security controls that are
        commensurate with those employed by the organization in the
        management of INR distribution. The procedural security controls
        employed for CA operation MUST be specified in its CPS. Possible
        topics to be covered in the CPS include:

 - 5.4.1: I think Sean addressed Randy's question here.

not to my satisfaction

You asked about the requirement to audit clock adjustments, and mentioned ntpd. Sean said:


I don't think you have to go that far. If you look in the logs of say a mac (because I've got one), you can see that I tweaked the time this morning:

Oct  3 09:49:54 computername SecurityAgent[2165]:
                 system.preferences|2010-10-03 09:49:54 -0400
Oct  3 08:50:48 computername SecurityAgent[2165]:
                 system.preferences|2010-10-03 09:50:48 -0400

That's pretty much what you need.

So, what would you like to see here re this topic? Are you saying that it's too hard to log clock adjustments on a machine acting as a CA, and that we should omit this item, or are you asking for more guidance re how to perform the logging?


 > - 6.3.2: Randy and Geoff do not agree on whether/how to change this.

hmmm, i honestly do not remember.  but i must be right because geoff is
more jet lagged.  :)

 NEW:   The INRs held by a CA may periodically change when it receives
        new distributions. To minimize disruption, the CA key MUST NOT
        change when INRs are added to it's certificate.

i do not have enough coffee (and it is dishwater here in the icnp conf
hotel) to think this through.  but isn't my parent the one who adds the
new resources to my cert?  so you are telling me that i need to
coordinate submitting a req to change my key with an unknown time when
my parent decides to give me resources?  as i said, need caffeine.

Yes, it is your parent that inserts new INRs into your cert. This text says that when this operation is done, your key stays the same, so that all of the objects that you signed do NOT have to be re-signed. So, the effect is the opposite of what you are worried about, i.e., when your parent adds resources to your cert, you do not have to do anything, until you decide to issue ROAs (or subordinate CA certs) that make use of the newly added resources. Are we OK on this?

Steve
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to