Re: [karp] rt-dir review of draft-ietf-karp-crypto-table

[Stephen Kent <[e-mail]>]

Randy,

You're right that each BGPSEC router has a private key. However, the key 
table is
designed to manage key rollover for keys that are shared on a pairwise 
basis.
The private router key does not have that property, so it seems a bad fit.
I should have been more precise in my reply.

Steve

>> More importantly, the RPKI and BGPSEC are not relevant to the key
>> table design. The former requires no crypto operations on a
>> router. The latter deals with keys for routers, but management of
>> these keys is very different, precisely because they are public keys.
> that last clause is false.  in bgpsec, the router has at least one
> private key so that it can sign announcements.
>
> i am scratching my head on whether a karp table entry could be helpful
> in the use of bgpsec keys, and have not found a clear need.  but this
> could be my fault.
>
> randy
>