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] some probes not returning NSID
- Previous message (by thread): [atlas] some probes not returning NSID
- Next message (by thread): [atlas] some probes not returning NSID
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Wed Feb 25 00:21:48 CET 2015
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015/02/24 18:23 , Alan Clegg wrote: > On 2/24/15 11:14 AM, Mark Delany wrote: >>>> Well, to get packet size option sure, but what about the >>>> others? For example when edns-client-subnet standardizes? >>> >>> When there is interest from the community then we can just add >>> that option. > >> Color me intersted. > > I'm interested as well. (is there a better way to show interest > than to spam the mailing list?) Mailing MCB(Vesna). I'm curious what the measurement should do. Just measure propagation or does the contents matter as well? And how should in that case the prefix be set? And why Atlas? I assumed that this was an option between big resolvers, like Google's, and authoritative nameservers. Philip -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlTtB4wACgkQ23LKRM64egIZMQCeLeFaMnDb2M911ETCNWcKEFhr sVMAnRU9Yn5RXK81g/Fh8ue2S+TsYUsC =OC3T -----END PGP SIGNATURE-----
- Previous message (by thread): [atlas] some probes not returning NSID
- Next message (by thread): [atlas] some probes not returning NSID
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]