May seem like acronym mania but another possibility is: RCET (Router Cert Expire Time) method :)
We are basically imposing an expire time on BGPSEC announcements either by the router cert's expire time (RCET) or by an explicit Origin Signature Expire Time (OSET). Sriram ________________________________________ From: [email protected] [[email protected]] On Behalf Of Sriram, Kotikalapudi [[email protected]] Sent: Friday, March 09, 2012 8:32 AM To: Roque Gagliano (rogaglia) Cc: [email protected] Subject: Re: [sidr] Taxonomy suggestion (draft-rogaglia-sidr-bgpsec-rollover) Thanks. I am OK with either: "key rollover" or "router rekeying". It is just that were using "router rekeying" in the SIDR Interim meeting discussions, and Randy is also using it his documents: draft-ymbk-bgpsec-rtr-rekeying-00.txt Sriram ________________________________________ From: Roque Gagliano (rogaglia) [[email protected]] Sent: Friday, March 09, 2012 8:02 AM To: Sriram, Kotikalapudi Cc: [email protected] Subject: Re: Taxonomy suggestion (draft-rogaglia-sidr-bgpsec-rollover) Hi Sriram Thanks for your email. (snif) > > Considering all of the above, I think the following taxonomy would be > preferable: > Origin Signature Expire Time (OSET) method (for what is in the current -01 > spec draft), and > Router Re-keying (RR) method (proposed new method). > I am ok with your proposal for OSET. I used "key rollover" because I wanted to be consistent with RFC 6489 which uses the term "rollover" instead of "rekeying". What do you think? Roque > Sriram _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
