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/dns-wg@ripe.net/
[dns-wg] APIs for accessing DNSMON data
- Previous message (by thread): [dns-wg] APIs for accessing DNSMON data
- Next message (by thread): [dns-wg] APIs for accessing DNSMON data
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Brett Carr
Brett.Carr at nominet.org.uk
Thu Mar 20 11:33:03 CET 2014
On 20 Mar 2014, at 10:21, Jim Reid <jim at rfc1035.com> wrote: > On 20 Mar 2014, at 08:49, Robert Kisteleki <robert at ripe.net> wrote: > >> There's a related discussion on the RIPE Atlas users' mailing list about an >> API to get to the *latest* results per measurement, which will come handy if >> you don't want to download gigs of results every time. > > It's a pity Robert that the discussion appears to be confined to that list. I expect many TLD and root operators would be interested in having some way of using DNSMON data to supplement their existing DNS monitoring arrangements. Not all of these will be paying customers for DNSMON or hosting Atlas probes. There may well be other fora too like CENTR or OARC who could have useful contributions to the development of this API. > > It would be nice if the DNS business could come up with a standard API/data format for this side of thing. OTOH, I can see why that could be considerably harder to achieve than cat-herding. > > Perhaps we can have the WG discuss this in Warsaw. > I think that this would be an excellent use of some time in Warsaw. Brett
- Previous message (by thread): [dns-wg] APIs for accessing DNSMON data
- Next message (by thread): [dns-wg] APIs for accessing DNSMON data
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]