Re: [Rescert] Notes from RPKI security review

[Randy Bush <randy@psg.com>]

>> The CMS certs are the "Business" certs that are exchanged as part of the
>> establishement of a business relationship between the parent and child.
>>
>> Can you elaborate on the TLS certs here?
> 
> They might come from the same business PKI that generated the CMS, or
> might not.  There's been a bit of follow-up discussion between me,
> Randy, and the security guys since NANOG on a few issues around TLS
> certs, this is one of them.

the cms certs are between the two *IRs which have an allocation business
relationship.  the tls certs are between two rpki service hosting
providers, who contracted to provide rpki services to the two *IRs.

> Note that the security guys told us to use TLS client certificates
> too, which is one of the reasons why I think we really might want the
> TLS certificates to tie into the same business PKI as the CMS
> certificates.

may not be able to.  see above and add restriction of one cert per
server (alt names are wobbly in my experience).

> Also note that we don't currently say anything about CRLs in the
> business PKI universe.

not our business.  can't have parent reaching through child's irbe to
biz key back end to check a crl.  irbes should check crls for the biz
certs in their back ends, innuendo intended.

>>> Russ noted that there's an optional seconds-since-epoch representation
>>> for timestamps in CMS which we might prefer over the default, but it
>>> may not be implemented in OpenSSL yet.  I may implement it if it's not
>>> a lot of work but it doesn't look like anything that's on our critical
>>> path.  The new timestamp format is in RFC 4049.
>> Given an understanding that in CMS the timestamp is optional

is not optional.  think audit

randy