This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[routing-wg] [ncc-announce] PI and Anycast space marked as INFRA eligible for Resource Certification (RPKI)
- Previous message (by thread): [routing-wg] [ncc-announce] PI and Anycast space marked as INFRA eligible for Resource Certification (RPKI)
- Next message (by thread): [routing-wg] RIPE NCC Training Courses April-June 2012 - IL, BE, IS, PL, RU, FI, NL, DE, ES, HR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alex Band
alexb at ripe.net
Thu Feb 9 11:50:26 CET 2012
Hello İbrahim, The Resource Certification (RPKI) service offers our members validatable proof that they are the registered holder of the Internet number resources listed on the Certificate. It is a different representation of our Registry data, and can be used for various applications. The practical use of Resource Certification right now is to use it for BGP Origin Validation, but other applications are possible, such as using a certificate to make the transfer of IP resources between two parties reliable and secure. When using the Certificate for BGP Origin Validation, you can make a validatable, cryptographic statement which ASs are authorised to originate your IP prefixes. Other network operators can base their routing decisions on this information. Resource Certification is part of a global industry effort is to help prevent (accidental) mis-announcements of your IP prefixes by someone else, i.e. a hijack. For detailed information, please have a look at http://ripe.net/certification If you have any additional questions, please do not hesitate to contact me. Kind regards, Alex Band RIPE NCC On 9 Feb 2012, at 10:05, İbrahim Selçuk wrote: > Hi, > We don’t use the certificate for BGP. What benefit for out company, this certificate. We use AS number and we dont complain. Thinking about AS Number to remove? > > What makes me an extra certificate? > > Thank you for your help, > > > İbrahim SELÇUK > Bilgi Teknolojileri > Teknik Müdürlük > Tel: (0212) 677 0 907 > <image001.gif> > > From: Birol Korkmaz > Sent: Wednesday, February 08, 2012 6:28 PM > To: İbrahim Selçuk > Subject: FW: [ncc-announce] PI and Anycast space marked as INFRA eligible for Resource Certification (RPKI) > > İbrahim bunun için ne yapmamız gerekiyor. > > > From: ncc-announce-bounces at ripe.net [mailto:ncc-announce-bounces at ripe.net] On Behalf Of Alex Band > Sent: Wednesday, February 08, 2012 2:07 PM > To: NCC Services WG; routing-wg at ripe.net; ncc-announce at ripe.net > Subject: [ncc-announce] PI and Anycast space marked as INFRA eligible for Resource Certification (RPKI) > > Dear colleagues, > > I am happy to announce that the following Independent Internet number resources are now eligible for Resource Certification (RPKI): > > - IPv4 and IPv6 Provider Independent, listed in your LIR Portal account as "INFRA" > - IPv4 and IPv6 Anycast, listed in your LIR Portal account as "INFRA" > > You can now create Route Origin Authorisations (ROAs) for the BGP announcements with this address space. Pay careful attention that *all* BGP announcements with your prefixes are RPKI VALID. You can verify this in the "My ROA Specifications" tab of the Resource Certification portal, under "Current BGP announcements". > > Please visit http://ripe.net/certification for more information. > > Kind regards, > > Alex Band > Product Manager > RIPE NCC -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20120209/834a20d4/attachment.html>
- Previous message (by thread): [routing-wg] [ncc-announce] PI and Anycast space marked as INFRA eligible for Resource Certification (RPKI)
- Next message (by thread): [routing-wg] RIPE NCC Training Courses April-June 2012 - IL, BE, IS, PL, RU, FI, NL, DE, ES, HR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]