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/ripe-atlas@ripe.net/
[atlas] Feature request for Validated Timestamps
- Previous message (by thread): [atlas] Feature request for Validated Timestamps
- Next message (by thread): [atlas] Feature request for Validated Timestamps
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Thu Apr 1 23:23:36 CEST 2021
> To expand on the immediate area of research, I'd like to have a distributed > system where nodes self-identify what location they're in. There are a > number of situations - be it operator misconfiguration or active attempts > to misreport where it is more concrete to instead have nodes report their > location based on time bounding their distance to known locations. The > atlas looks like a great existing set of known anchor points to base such > measurements on, but that attestation of location is very difficult to > construct without additional authenticity. > > (Nodes may be behind NATs make it seem difficult to measure outbound from > atlas probes to them) Candela, M., Gregori, E., Luconi, V., Vecchio, A. (2019). Using RIPE Atlas for geolocating IP infrastructure https://www.semanticscholar.org/paper/Using-RIPE-Atlas-for-Geolocating-IP-Infrastructure-Candela-Gregori/2bc71c0985d0b531da644335c1430060e3185cc3 randy --- randy at psg.com `gpg --locate-external-keys --auto-key-locate wkd randy at psg.com` signatures are back, thanks to dmarc header butchery
- Previous message (by thread): [atlas] Feature request for Validated Timestamps
- Next message (by thread): [atlas] Feature request for Validated Timestamps
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]