IETF Logo Mail Archive

Re: [Idr] Adoption of draft-l3vpn-legacy-rtc-00 as IDR WG document?

Robert Raszuk <robert@raszuk.net> Thu, 17 November 2011 02:47 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17AC11F0C54 for <idr@ietfa.amsl.com>; Wed, 16 Nov 2011 18:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.283
X-Spam-Level:
X-Spam-Status: No, score=-2.283 tagged_above=-999 required=5 tests=[AWL=0.316, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QiFGCXVzARrA for <idr@ietfa.amsl.com>; Wed, 16 Nov 2011 18:47:18 -0800 (PST)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 53BC521F8E88 for <idr@ietf.org>; Wed, 16 Nov 2011 18:47:18 -0800 (PST)
Received: (qmail 19166 invoked by uid 399); 17 Nov 2011 02:47:17 -0000
Received: from unknown (HELO ?130.129.19.9?) (130.129.19.9) by mail1310.opentransfer.com with ESMTP; 17 Nov 2011 02:47:17 -0000
X-Originating-IP: 130.129.19.9
Message-ID: <4EC475B5.8010009@raszuk.net>
Date: Thu, 17 Nov 2011 03:47:17 +0100
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "UTTARO, JAMES" <ju1738@att.com>
References: <B04EDD60-8998-4085-97CC-885A65AA47BA@juniper.net><CAMXVrt55AJ2b80_kTBQUJ1ZCo6ewm_NMfmhwUxH48kktLTTi6w@mail.gmail.com><B383DA80-7CF1-453A-AEDA-8D3F33A40E5B@rob.sh> <4EC440CA.9070904@raszuk.net> <96327EF53EF71A48806DE2DFC034D57F0FF73B13@xmb-sjc-22b.amer.cisco.com> <B17A6910EEDD1F45980687268941550FA32FA9@MISOUT7MSGUSR9I.ITServices.sbc.com>
In-Reply-To: <B17A6910EEDD1F45980687268941550FA32FA9@MISOUT7MSGUSR9I.ITServices.sbc.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] Adoption of draft-l3vpn-legacy-rtc-00 as IDR WG document?
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2011 02:47:19 -0000

I respectfully disagree. It all depends how one builds and uses network 
management tools in any size of the network.

If in some cases such management tools are not effective perhaps it 
would be a good idea to fix them rather then propose implementation 
hacks and protocol extensions to work around them.

Best regards,
R.

> Coupling customer provisioning and management of BGP infrastructure (
> RRs ) is not workable is a large scale network.
>
> Jim Uttaro

v2.23.0 | Report a Bug | By Email