From a Cogent support ticket: "Hello,
Please see the attached LOA. Regarding the RPKI ROA, for now, we don't create ROA for our prefixes nor for prefixes that we assign to our customers and we don't plan to do it. Unfortunately, this is not an option." Someone that poses as a Tier-1 and doesn't even plan to sign their announcements ? How much more depeering will make them reconsider ? Rubens
It won't get them depeered, nor should it. I don't currently based much value in RPKI for BGP. On Mon., Aug. 9, 2021, 8:43 a.m. Rubens Kuhl, <rubensk@gmail.com> wrote:
From a Cogent support ticket: "Hello,
Please see the attached LOA.
Regarding the RPKI ROA, for now, we don't create ROA for our prefixes nor for prefixes that we assign to our customers and we don't plan to do it. Unfortunately, this is not an option."
Someone that poses as a Tier-1 and doesn't even plan to sign their announcements ? How much more depeering will make them reconsider ?
Rubens
Dear Rubens, On Mon, Aug 09, 2021 at 08:41:48AM -0300, Rubens Kuhl wrote:
From a Cogent support ticket:
Please see the attached LOA.
Regarding the RPKI ROA, for now, we don't create ROA for our prefixes nor for prefixes that we assign to our customers and we don't plan to do it. Unfortunately, this is not an option."
Someone that poses as a Tier-1 and doesn't even plan to sign their announcements ? How much more depeering will make them reconsider ?
Please keep in mind that sound technical, administrative, or financial reasons can exist that hamper one's ability to create RPKI ROAs. For example, if the IP space is LEGACY, and not covered by a 'LRSA' (ARIN) or 'Legacy Agreement' (RIPE), then RPKI certificate issuance services simply are not available for that IP space. Without an agreement with a RIR to arrange RPKI services, logically, one cannot create ROAs. Perhaps in your case, if RPKI is a requirement, you are better off bringing your own (RPKI capable) IP space? Kind regards, Job
Someone that poses as a Tier-1 and doesn't even plan to sign their announcements ? How much more depeering will make them reconsider ?
Please keep in mind that sound technical, administrative, or financial reasons can exist that hamper one's ability to create RPKI ROAs.
For example, if the IP space is LEGACY, and not covered by a 'LRSA' (ARIN) or 'Legacy Agreement' (RIPE), then RPKI certificate issuance services simply are not available for that IP space. Without an agreement with a RIR to arrange RPKI services, logically, one cannot create ROAs.
In the case at hand, the IP block is not legacy, it was an ARIN allocation from the start. Cogent does have a number of legacy blocks but AFAIK they wouldn't need to bring them to an LRSA in order to issue ROAs for the non-legacy blocks.
Perhaps in your case, if RPKI is a requirement, you are better off bringing your own (RPKI capable) IP space?
With IPv4 depleted at most RIRs, getting someone's own IPv4 space is not happening anytime soon. Rubens
participants (3)
-
jim deleskie -
Job Snijders -
Rubens Kuhl