>> 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
>
> I think you have taken the crown from Geoff, emitting the longest sentence
> on the SIDR list :-).
with a little work, i can usually understand geoff's. the above seems
to spend all of it's power budget on trying to appear erudite, and the
result is quite unintelligible to at least this st00pid geek.
but i think danny is happy with the changes. and if danny is happy, i
guess i am.
randy
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
