Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an IDR WG document

Jeffrey Haas <jhaas@nexthop.com> Mon, 26 July 2004 00:04 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05202; Sun, 25 Jul 2004 20:04:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bot0D-00050l-L6; Sun, 25 Jul 2004 20:06:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bosx5-00082W-6I; Sun, 25 Jul 2004 20:02:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BoswG-0007uE-PD for idr@megatron.ietf.org; Sun, 25 Jul 2004 20:01:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05006 for <idr@ietf.org>; Sun, 25 Jul 2004 20:01:55 -0400 (EDT)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BosxW-0004ye-J3 for idr@ietf.org; Sun, 25 Jul 2004 20:03:16 -0400
Received: from localhost (localhost [127.0.0.1]) by aa-mx1.nexthop.com (Postfix) with ESMTP id 5B8732D497C; Sun, 25 Jul 2004 20:01:18 -0400 (EDT)
Received: from aa-mx1.nexthop.com ([127.0.0.1]) by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 64579-01-8; Sun, 25 Jul 2004 20:01:17 -0400 (EDT)
Received: from jhaas.nexthop.com (jhaas.nexthop.com [65.247.36.31]) by aa-mx1.nexthop.com (Postfix) with ESMTP id 402962D4941; Sun, 25 Jul 2004 20:01:17 -0400 (EDT)
Received: (from jhaas@localhost) by jhaas.nexthop.com (8.11.6/8.11.6) id i6Q01G428261; Sun, 25 Jul 2004 20:01:16 -0400 (EDT)
Date: Sun, 25 Jul 2004 20:01:16 -0400
From: Jeffrey Haas <jhaas@nexthop.com>
To: "Howard C. Berkowitz" <hcb@gettcomm.com>
Subject: Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an IDR WG document
Message-ID: <20040726000116.GA27886@nexthop.com>
References: <BAY17-F65I9EPQgzgfj0006fa8f@hotmail.com> <p05100314bd27415d4f10@[192.168.0.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <p05100314bd27415d4f10@[192.168.0.2]>
User-Agent: Mutt/1.4.2.1i
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

On Fri, Jul 23, 2004 at 06:31:46PM -0400, Howard C. Berkowitz wrote:
> Now, I may have egg on my face because I missed a 
> proposal, but I don't think I've seen a general proposal to put 
> prefix-limit-exceeded into the BGP MIB. Yes, I recognize the actual 
> (local) prefix limit functionality is implementation specific, but if 
> it's worth doing remotely, it's worth doing locally.

Speaking as MIB editor, IMO the MIB should reflect protocol elements.
If we put max prefix into some ORF, it will probably make it into
the extension MIB for that ORF.

But, to provide a counter example, the l3vpn group decided to
put in "water marks" to represent the prefix limits.  This was
outside of the protocol, but desired by the working group.  Similarly,
if there is WG consensus on having this in the MIB, we can add
it regardless of whether we choose to do such a thing for an ORF
MIB that carries prefix limits.  (Similar if we do a dynamic capability
extention MIB to accomodate the other major proposal.)

However, if we choose to put in our own "water marks", we risk
conflict with the l3vpn implementation of the same since we carry
2547 type reachability over BGP too.

-- 
Jeff Haas 
NextHop Technologies

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr