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] RIPE NCC RPKI Validator 3 API spec?
- Previous message (by thread): [routing-wg] Weekly Routing Table Report
- Next message (by thread): [routing-wg] Towards cleaning up RPKI INVALIDs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
nusenu
nusenu-lists at riseup.net
Fri Sep 14 00:39:00 CEST 2018
Hi, (I hope it is ok to ask validator questions on this WG ML, but feel free to point me to a more appropriate venue) I'm using RIPE NCC's RPKI validator 3 and was looking for some API specifications that would describe the functioning of every parameter. Currently I'm making certain assumptions which is ok for some proof-of-concept but would like to confirm them using some official documentation. Is there a detailed specification that goes beyond [2]? thanks, nusenu [1] https://github.com/RIPE-NCC/rpki-validator-3/wiki [2] https://rpki-validator.ripe.net/swagger-ui.html#!/bgp45preview45controller/listUsingGET https://www.ripe.net/support/documentation/developer-documentation/rpki-validator-api -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: </ripe/mail/archives/routing-wg/attachments/20180913/408c79e4/attachment.sig>
- Previous message (by thread): [routing-wg] Weekly Routing Table Report
- Next message (by thread): [routing-wg] Towards cleaning up RPKI INVALIDs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]