From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.213.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id A9D6F20024C for ; Tue, 13 Mar 2012 08:22:19 -0700 (PDT) Received: by yenl11 with SMTP id l11so1039899yen.16 for ; Tue, 13 Mar 2012 08:22:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=D/1gii2OCTP8noTrRBgClQyPk5LkChle2SOxIxQZyIw=; b=YtoSUpAtZ3rOmKUAdv6QKOYLwPR/bTtEueE1jv1qNVgJTA3MECdCfJAsE7UUo78S4I kKsyIkoAEQtCI7+b/E4NzRPKeEyJiVrFhi6fYDnEPHykmZ30x8khsGup/LU8cqna16Sn 9GqQ9BiYX9cyvZlHAXfsLmxp60PbQcW0UrCCUprhDf7dz1oA45R7aso74LKhQbdDZHby OWyG+jvf8qcJtlhSDKVdTCF6ngGTdHlFQaZ11w7Y9qP49UkrcgmnJ5uL/NSv8BLTNEgG C25omI/9rUKnGedUZl6JprbROJpZpznlTHA53z3J3+wqASVFcsgQb3RU2FWsrpGNX5OR rPHQ== Received: by 10.182.119.98 with SMTP id kt2mr12466208obb.9.1331652138246; Tue, 13 Mar 2012 08:22:18 -0700 (PDT) MIME-Version: 1.0 Sender: tz2026@gmail.com Received: by 10.182.68.164 with HTTP; Tue, 13 Mar 2012 08:21:58 -0700 (PDT) In-Reply-To: References: From: tz Date: Tue, 13 Mar 2012 11:21:58 -0400 X-Google-Sender-Auth: 8BBEO0W_G-24Xe1ae_wX65aL0zY Message-ID: To: Dave Taht Content-Type: text/plain; charset=ISO-8859-1 Cc: thumbgps-devel@lists.bufferbloat.net Subject: Re: [Thumbgps-devel] data collection X-BeenThere: thumbgps-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 15:22:19 -0000 One thing to note - a traceroute or something similar might be necessary if we are measuring the network. I'm down the street from Level 3, but use Comcast, and a Verizon mifi, so packets are going to take different routes. The GPS location is one thing, but a backbone map would also be relevant if not required. One thing which might help is if a major backbone vendor (cisco, arbor networks) would adopt this technology into one of their high-end switches. They probably do something similar already to get somewhat accurate time, but perhaps without the precision and they typically aren't running stratum 1 servers on or a hop from the backbones which might be the most interesting. On Tue, Mar 13, 2012 at 10:55 AM, Dave Taht wrote: > But back to the network mapping front, one reason I'd chosen postgres > for a backend was the geography support, being able to calculate in > curves seemed like a good idea. I'm curious if anybody has other > thoughts for a backend to a global time slew database?