Re: [100attendees] Incorrect GeoIP for IETF network addresses
Jim Martin <jim@daedelus.com> Mon, 13 November 2017 03:48 UTC
Return-Path: <jim@daedelus.com>
X-Original-To: 100attendees@ietfa.amsl.com
Delivered-To: 100attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id EB8F71293F2
for <100attendees@ietfa.amsl.com>; Sun, 12 Nov 2017 19:48:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id lTQXRxZdLiYg for <100attendees@ietfa.amsl.com>;
Sun, 12 Nov 2017 19:48:56 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 2949C128B8F
for <100attendees@ietf.org>; Sun, 12 Nov 2017 19:48:53 -0800 (PST)
Received: from imladris.daedelus.com (imladris.daedelus.com [206.197.161.143])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by uillean.fuaim.com (Postfix) with ESMTP id C75D5880E2;
Sun, 12 Nov 2017 19:48:50 -0800 (PST)
Received: from [IPv6:2001:67c:370::6d20:7c15:3c3c:c70e] (unknown
[IPv6:2001:67c:370:0:6d20:7c15:3c3c:c70e])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by imladris.daedelus.com (Postfix) with ESMTP id 2DB8E1308395;
Sun, 12 Nov 2017 19:48:47 -0800 (PST)
From: Jim Martin <jim@daedelus.com>
Message-Id: <EBA4F7E7-4DD7-45E3-887E-687D104A7BCC@daedelus.com>
Content-Type: multipart/signed;
boundary="Apple-Mail=_4516439B-7B57-49CC-ACA6-C024D567E11E";
protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.11\))
Date: Mon, 13 Nov 2017 11:48:38 +0800
In-Reply-To: <204af427-f50a-8d4e-7919-f52d7a23d83a@cea.fr>
Cc: Chris Morrow <morrowc@google.com>,
100attendees@ietf.org
To: Alexandre PETRESCU <alexandre.petrescu@cea.fr>
References: <180DB1B1-98A6-4505-8B30-80959DCBC1F2@cablelabs.com>
<CAMeF8nB4WaMwi0LV8WwBHNaMTyomBExv0=M9TFNGzm-3bWNHWw@mail.gmail.com>
<dccbfa53-45dc-44df-e2dc-34ab18af17b5@cea.fr>
<CAMeF8nBHd-OrmDMZo6qUmoMGNc5MfPj0cjJnkQbCypni5xpuMA@mail.gmail.com>
<204af427-f50a-8d4e-7919-f52d7a23d83a@cea.fr>
X-Mailer: Apple Mail (2.3445.5.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/100attendees/S8rofdtL49_CZB0bVGR4xusFOVs>
Subject: Re: [100attendees] Incorrect GeoIP for IETF network addresses
X-BeenThere: 100attendees@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Mailing list of IETF 100 attendees that have opted in on this list."
<100attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/100attendees>,
<mailto:100attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/100attendees/>
List-Post: <mailto:100attendees@ietf.org>
List-Help: <mailto:100attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/100attendees>,
<mailto:100attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Nov 2017 03:48:58 -0000
> On Nov 13, 2017, at 11:39 AM, Alexandre PETRESCU <alexandre.petrescu@cea.fr> wrote: > >> Is the IPv6 DNS resolver address constant at IETF meetings? >> >> >> the resolvers are the same, yes. > > Ah, that could be part of the reasons then. I suppose then there is tunnelling between Singapore and the home of these constant IP addreses. There’s no tunneling as part of the infrastructure of the IETF network. We have the several address blocks that we advertise from our own AS each time, this time via 4 upstream providers. The servers are at the same addresses for each meeting. -Jim
- [100attendees] Incorrect GeoIP for IETF network a… Darshak Thakore
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Carlos M. Martinez
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Jim Martin
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Chris Morrow
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Warren Kumari
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Bob Hinden
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Mike Bishop
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Darshak Thakore
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Michal Krsek
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Chris Morrow
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Chris Morrow
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Alexandre PETRESCU
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Chris Morrow
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Alexandre PETRESCU
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Darshak Thakore
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Michal Krsek
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Alexandre PETRESCU
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Jim Martin
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Alexandre PETRESCU
- Re: [100attendees] Incorrect GeoIP for IETF netwo… Michal Krsek
- Re: [100attendees] Incorrect GeoIP for IETF netwo… joel jaeggli