If the plan is indeed to employ connection-oriented TCP transport for rpki-rtr
signaling in order to establish prospectively volatile soft-state in router
control planes directly from RPKI-derived blobs -- i.e., beyond {prefix,origin}
bindings to include {ASN, public_key, & SKI} for each EE certificate in the
RPKI, as well as {ASN and associated IP prefixes} for each ROA in the RPKI then
I'm glad these changes were made and they address my _actionable concerns with
this document.
Thanks for resolving these specific issues,
-danny
On Jan 9, 2012, at 10:13 AM, Randy Bush wrote:
> the message does not include a nice bit the authors get
>
> Diff from previous version:
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-sidr-rpki-rtr-23
>
> randy
> _______________________________________________
> sidr mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/sidr
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
