Re: [OPSAWG] [Gen-art] Rtgdir early review of draft-ietf-opsawg-ipfix-bgp-community-06

"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 15 April 2018 22:46 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2666B1272E1; Sun, 15 Apr 2018 15:46:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 lYTROVNrFd7w; Sun, 15 Apr 2018 15:46:44 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 647B61250B8; Sun, 15 Apr 2018 15:46:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4BBE24E004E; Sun, 15 Apr 2018 15:46:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1523832404; bh=ydLFmaVDNlvVr4StRbJ5RCgPEpnlKi6+CEaysQUwM1s=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Ym9JPKL10SlxhCMucRwcn/WreSnJBGywWcFTSuGhairPeRGcyuYLQs+RAjpgOWLVK nyYIIINlu/9X4MX+8xihstHVwFoCrs5L1e2GDZmC1AW8v7g6o1Vd7f4hIAGW2esb0o M26vb3F80xi6YPssS9WV0VIHDbkaAvscrs6itBiI=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [50.225.209.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 2970A1C0B99; Sun, 15 Apr 2018 15:46:41 -0700 (PDT)
To: Randy Bush <randy@psg.com>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, heasley <heas@shrubbery.net>, opsawg <opsawg@ietf.org>, "draft-ietf-opsawg-ipfix-bgp-community.all@ietf.org" <draft-ietf-opsawg-ipfix-bgp-community.all@ietf.org>, li zhenqiang <li_zhenqiang@hotmail.com>
References: <152363066886.26321.3212300538180273898@ietfa.amsl.com> <HKXPR0601MB1799868866AF89F9699EAF28FCB10@HKXPR0601MB1799.apcprd06.prod.outlook.com> <20180415160956.GC66082@shrubbery.net> <ace47a71-0e9d-6a0d-ae37-1f4bc48ada0b@stevecrocker.com> <m2muy4nlz0.wl-randy@psg.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <62aa2b28-05c6-37a3-d4cc-142395b28fe0@joelhalpern.com>
Date: Sun, 15 Apr 2018 18:46:40 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <m2muy4nlz0.wl-randy@psg.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/7OB75gC9u-C4wHZUPfI0HCk0jyw>
Subject: Re: [OPSAWG] [Gen-art] Rtgdir early review of draft-ietf-opsawg-ipfix-bgp-community-06
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Apr 2018 22:46:46 -0000

Randy, I did suggest that one would update the offline data.
My point was that the draft claims taht extreme timliness is needed. 
For IP block geolocation, timeliness on the order of a day (much shorter 
than the several days before the IETF when the IETF block gets turned on 
somewhere.)

Thus, again, you are not making a case for why the existing techniques 
which are easier to implement and deploy are not sufficie3nt for the 
problem.

Yours,
Joel

On 4/15/18 6:28 PM, Randy Bush wrote:
>> I fone has geo-information, it is unlikely to change.
> 
> i guess you have never noticed when you are at ietf praha and your phone
> says you are in seoul or whatever.  it takes non-trivial ops pain to get
> ietf attendees geoloc to work; and sometimes we can't.
> 
> when you find yourself in a hole, first thing is to stop digging.
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
>