[GROW] Comment on draft-manderson-grow-geomrt-00
Jeffrey Haas <jhaas@pfrc.org> Mon, 02 August 2010 21:55 UTC
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 39E983A65A5 for <grow@core3.amsl.com>; Mon, 2 Aug 2010 14:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.458
X-Spam-Level:
X-Spam-Status: No, score=-0.458 tagged_above=-999 required=5 tests=[AWL=-0.793, BAYES_50=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HFf+Aa4DueU3 for <grow@core3.amsl.com>; Mon, 2 Aug 2010 14:55:33 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by core3.amsl.com (Postfix) with ESMTP id 66A013A6407 for <grow@ietf.org>; Mon, 2 Aug 2010 14:55:33 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 770272240C6; Mon, 2 Aug 2010 21:56:01 +0000 (UTC)
Date: Mon, 02 Aug 2010 21:56:01 +0000
From: Jeffrey Haas <jhaas@pfrc.org>
To: grow@ietf.org
Message-ID: <20100802215601.GA17736@slice>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: [GROW] Comment on draft-manderson-grow-geomrt-00
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2010 21:55:34 -0000
I just got done re-reading this draft. Upon review, I'm wondering if instead of creating a new type that simply adding a new sub-type may be more appropriate. The current proposal effectively replaces the current PEER_INDEX_TABLE with a new one that has the WGS84 records. Consider instead that a new sub-type table is defined which has a similar structure to the PEER_INDEX_TABLE. It would simply provide a matching augmentation of the PEER_INDEX_TABLE by carrying the geo records. This has the advantage that it requires fewer changes to existing implementations. In particular, it permits older MRT file readers to be able to continue to parse the dump data. Only the new geoip information would be opaque. -- Jeff
- [GROW] Comment on draft-manderson-grow-geomrt-00 Jeffrey Haas
- Re: [GROW] Comment on draft-manderson-grow-geomrt… Terry Manderson