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

Randy Bush <randy@psg.com> Sun, 15 April 2018 14:38 UTC

Return-Path: <randy@psg.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 90E531242F5; Sun, 15 Apr 2018 07:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.501
X-Spam-Level:
X-Spam-Status: No, score=-5.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 lsR9gn-_imvQ; Sun, 15 Apr 2018 07:38:34 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 530C71200F1; Sun, 15 Apr 2018 07:38:31 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1f7inU-0002Me-VS; Sun, 15 Apr 2018 14:38:29 +0000
Date: Sun, 15 Apr 2018 07:38:28 -0700
Message-ID: <m2wox8o7q3.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Joel Halpern <jmh@joelhalpern.com>
Cc: <rtg-dir@ietf.org>, gen-art@ietf.org, draft-ietf-opsawg-ipfix-bgp-community.all@ietf.org, ietf@ietf.org, opsawg@ietf.org
In-Reply-To: <152363066886.26321.3212300538180273898@ietfa.amsl.com>
References: <152363066886.26321.3212300538180273898@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/OczRw11EQgsps0XHt4Jkw4MfKt0>
Subject: Re: [OPSAWG] 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 14:38:36 -0000

hi joel,

> The secondary problem is that this additional work is justified for
> the router by the claim that the unusual usage of applying community
> tags for geographical location of customers is a common practice.  It
> is a legal practice.  And I presume it is done somewhere or the
> authors would not be asking for it.  But it is not common.

actually, it is used.  not in the "this prefix originted in new
hampshire," sense, but for global isps, to tag the routing region of
origin, e.g. se asia, europe, noam, ...

randy