> Note that cut/copy and paste operations over a SSH-proected CLI session
> for keys over a certain sizes is error-prone; a less error process is to
^-prone
> use a USB or CF device to copy the key to and then insert the device in
> to the router.
way too detailed. you noted that pure text copy/paste is error prone.
that's enough. do you really want to get into the 42 other ways of
doing it? how about copy/paste of a checksummed package containing the
credential? or xmodem? and don't forget paper tape! :)
> The PKCS#10 request, which includes the public key the router wants
> certified, can be directly transferred to the RPKI CA over the network
> if the router supports protocols such as FTP and HTTP [RFC2585] using
> the application/pkcs10 media type [RFC5967] or EST (Enrollment over
> Secure Transport) [I-D.ietf-pkix-est]; direct transfer assumes that the
> router has direct connectivity to the CA.
what's "direct?" are you trying to say in the same pop? on the same
lan segment? or do you merely mean e2e over the intertubes?
> The operator off-loads the PKCS#10 and uploads the request to their RPKI
> software management tools; external network connectivity is not required
> if the operator acts as CA.
external to what? s/external/global/?
randy
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
