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 ]
Will
willscott at gmail.com
Thu Apr 1 23:19:53 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) --Will On Thu, Apr 1, 2021 at 1:57 PM Randy Bush <randy at psg.com> wrote: > would you care to share reasons for suspicion which would warrant > raising the level of authenticity? > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20210401/59ea94b1/attachment.html>
- 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 ]