Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an IDR WG document
Jeffrey Haas <jhaas@nexthop.com> Fri, 23 July 2004 14:18 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 KAA26459; Fri, 23 Jul 2004 10:18:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bo0t0-0007R9-IG; Fri, 23 Jul 2004 10:18:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bo0iB-0002gO-IC; Fri, 23 Jul 2004 10:07:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bo0eE-00008J-7B for idr@megatron.ietf.org; Fri, 23 Jul 2004 10:03:42 -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 KAA24365 for <idr@ietf.org>; Fri, 23 Jul 2004 10:03:40 -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 1Bo0ex-00079O-Ft for idr@ietf.org; Fri, 23 Jul 2004 10:04:30 -0400
Received: from localhost (localhost [127.0.0.1]) by aa-mx1.nexthop.com (Postfix) with ESMTP id 414852D4B01; Fri, 23 Jul 2004 10:03:06 -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 25176-02-30; Fri, 23 Jul 2004 10:03:05 -0400 (EDT)
Received: from jhaas.nexthop.com (jhaas.nexthop.com [65.247.36.31]) by aa-mx1.nexthop.com (Postfix) with ESMTP id 236FA2D4B00; Fri, 23 Jul 2004 10:03:05 -0400 (EDT)
Received: (from jhaas@localhost) by jhaas.nexthop.com (8.11.6/8.11.6) id i6NE35h22429; Fri, 23 Jul 2004 10:03:05 -0400 (EDT)
Date: Fri, 23 Jul 2004 10:03:05 -0400
From: Jeffrey Haas <jhaas@nexthop.com>
To: Chandrashekhar Appanna <achandra@cisco.com>
Subject: Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an IDR WG document
Message-ID: <20040723140304.GA20535@nexthop.com>
References: <200407191542.i6JFgNe12536@merlot.juniper.net> <20040723023258.GA715@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20040723023258.GA715@cisco.com>
User-Agent: Mutt/1.4.2.1i
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: Yakov Rekhter <yakov@juniper.net>, 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: 52e1467c2184c31006318542db5614d5
On Thu, Jul 22, 2004 at 07:32:58PM -0700, Chandrashekhar Appanna wrote: > Yes, I think this should become a WG doc. I also think it should become a WG document (but still need to do a quick read-through of the current draft). > On the topic of merging the various ORF type docs, if there > was a clear consensus or need, I am sure the original authors > would have added them all in the base spec. To nitpick a little bit, ORFs, like extended communities, seem to strongly have come out of certain vendor's needs for certain technology to solve a specific problem. The fact that they were adaptable to a more generic tool speaks well of the authors of the specifications. However, I think that a more generic solution would have done us well in each case. ORFs are extremely coarse policy. Extended communities have already been criticized for not being flexibile enough. Yet each solves the problems for their original problem space well enough. Rough consensus and all that. :-) > Since they did not > and we are seeing the individual submissions, I would leave it > that way so that only the ones required will survive.... I'd generally agree. -- Jeff Haas NextHop Technologies _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr
- [Idr] draft-chen-bgp-prefix-orf-07.txt as an IDR … Yakov Rekhter
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Howard C. Berkowitz
- RE: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Susan Hares
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Robert Raszuk
- RE: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Kumar, Srivatsa
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Danny McPherson
- RE: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Michael Dell
- RE: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Susan Hares
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Enke Chen
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Robert Raszuk
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … John G. Scudder
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Howard C. Berkowitz
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Howard C. Berkowitz
- RE: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Susan Hares
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Danny McPherson
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Chandrashekhar Appanna
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Enke Chen
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Danny McPherson
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Jeffrey Haas
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Jeffrey Haas
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … john smith
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Howard C. Berkowitz
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … john smith
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Howard C. Berkowitz
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Jeffrey Haas
- Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an … Howard C. Berkowitz