I can confirm that the official abbreviation is: Secured Origin Validate Cache
Kind Regards, Dominik Dobrowolski [Cisco White/Blue Both Lines] Dominik Dobrowolski Technical Consulting Engineer Global CX Centers – Enterprise Switching .:|:.:|:. Customer Experience dodob...@cisco.com<mailto:dodob...@cisco.com> Tel: +48 12 321 29 03 Cisco Systems Poland Sp. z o. o. Aleja Powstancow Wielkopolskich 13C Enterprise Park Krakow Krakow 30-707 Poland This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Update Profile<https://www.cisco.com/c/en/us/about/help/login-account-help.html#~profile> - Privacy<http://www.cisco.com/web/siteassets/legal/privacy.html> Please click here<http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html> for Company Registration ________________________________ From: NANOG on behalf of Sofia Silva Berenguer Sent: Thursday, February 1, 2024 12:15 AM To: Compton, Rich; Justin H.; NANOG list Subject: Re: SOVC - BGp RPKI How polite of it to apologize!! I asked Bing’s Copilot and it says SOVC stands for “Signed Object Validation Cache” but I wasn’t able to get a source for that either ☹ Oh these AI times… Warm regards, Sofía -- I am sending this email at a time that suits me and the time zone I work in. Please feel free to read, and act on or respond, at a time that suits you. ____________________________________________________________________ Sofía Silva Berenguer RPKI Program Manager, NRO / Process and Productivity Engineer, APNIC e: so...@apnic.net<mailto:so...@apnic.net> ____________________________________________________________________ From: NANOG <nanog-bounces+sofia=apnic....@nanog.org> on behalf of Compton, Rich via NANOG <nanog@nanog.org> Date: Thursday, 1 February 2024 at 9:10 am To: Justin H. <justindh...@gmail.com>, NANOG list <nanog@nanog.org> Subject: Re: SOVC - BGp RPKI I think it hallucinated. When asked to site its sources: “I apologize for the confusion, but my response about "SOVC" in the context of RPKI on Cisco routers was based on general knowledge of RPKI and networking principles, not from a specific source. The explanation combined standard practices and concepts in network security and routing, especially as they relate to RPKI and BGP. Since the acronym "SOVC" is not a standard or widely recognized term in the context of RPKI, it's possible that it might be specific to certain environments or proprietary to certain Cisco router models or software versions. For the most accurate and detailed information, it's always best to consult the official Cisco documentation or support resources, especially for terms that might be specific to their products.” From: NANOG <nanog-bounces+rich_compton=comcast....@nanog.org> on behalf of Justin H. <justindh...@gmail.com> Date: Wednesday, January 31, 2024 at 3:06 PM To: NANOG list <nanog@nanog.org> Subject: Re: SOVC - BGp RPKI I'd be curious to know why it thinks that the S is "Stale". I don't suppose it cites its sources? Compton, Rich via NANOG wrote: > > ChatGPT says: > > SOVC in the context of RPKI (Resource Public Key Infrastructure) on a > Cisco router stands for "Stale Origin Validation Cache". RPKI is a > security framework designed to secure the Internet's routing > infrastructure, primarily through route origin validation. It ensures > that the Internet number resources (like IP addresses and AS numbers) > are used by the legitimate owners or authorized AS (Autonomous System). > > In RPKI, Route Origin Authorizations (ROAs) are used to define which > AS is authorized to announce a specific IP address block. Network > devices, like Cisco routers, use these ROAs to validate the > authenticity of BGP (Border Gateway Protocol) route announcements. > > The term "stale" in SOVC refers to a situation where the router's > RPKI-to-Router protocol client has lost its connection to the RPKI > server, or when the RPKI cache data is outdated and not refreshed for > some reason. This can happen due to network issues, configuration > errors, or problems with the RPKI server itself. When the RPKI cache > is stale, the router cannot reliably validate BGP route announcements > against the latest ROA data, potentially affecting routing decisions. > > In a network security context, maintaining an up-to-date RPKI cache is > crucial for ensuring that the network only accepts legitimate routing > announcements, thereby reducing the risk of routing hijacks or > misconfigurations. As a network security engineer, managing and > monitoring the RPKI status on routers is an important aspect of > ensuring network security and integrity. > > I see it mentioned in this doc: > > https://urldefense.com/v3/__https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/15-s/irg-15-s-book/irg-origin-as.pdf__;!!CQl3mcHX2A!EB5iIYDDpnRMSM7Gjvy11sMoEsjEDlXtTpfipi4l735bx04IY-dD73vWGCbiDZvoRR6kTse35whqa8dH1cN_Ya9j$<https://urldefense.com/v3/__https:/www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/15-s/irg-15-s-book/irg-origin-as.pdf__;!!CQl3mcHX2A!EB5iIYDDpnRMSM7Gjvy11sMoEsjEDlXtTpfipi4l735bx04IY-dD73vWGCbiDZvoRR6kTse35whqa8dH1cN_Ya9j$> > > *From: *NANOG <nanog-bounces+rich_compton=comcast....@nanog.org> on > behalf of Mohammad Khalil <eng.m...@gmail.com> > *Date: *Wednesday, January 31, 2024 at 10:35 AM > *To: *NANOG list <nanog@nanog.org> > *Subject: *SOVC - BGp RPKI > > Greetings Am have tried to find out what is the abbreviation for SOVC > with no luck. #sh bgp ipv4 unicast rpki servers BGP SOVC neighbor is > X. X. X. 47/323 connected to port 323 Anyone have encountered this? > Thanks! > > Greetings > > Am have tried to find out what is the abbreviation for SOVC with no luck. > > #sh bgp ipv4 unicast rpki servers > > BGP SOVC neighbor is X.X.X.47/323 connected to port 323 > > Anyone have encountered this? > > Thanks! >
