Re: [Isis-wg] draft-amante-isis-reverse-metric-01

mike shand <mshand@cisco.com> Mon, 06 December 2010 16:56 UTC

Return-Path: <mshand@cisco.com>
X-Original-To: isis-wg@core3.amsl.com
Delivered-To: isis-wg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 417563A6832 for <isis-wg@core3.amsl.com>; Mon, 6 Dec 2010 08:56:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level:
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_111=0.6, RCVD_IN_DNSWL_HI=-8]
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 U9Z5tA8xutzq for <isis-wg@core3.amsl.com>; Mon, 6 Dec 2010 08:56:34 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 19AAD3A681F for <isis-wg@ietf.org>; Mon, 6 Dec 2010 08:56:33 -0800 (PST)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApAFAKuk/EyQ/khLgWdsb2JhbACVJo4WFQEBFiIiomSad4VJBIpugxM
X-IronPort-AV: E=Sophos;i="4.59,306,1288569600"; d="scan'208";a="14726612"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 06 Dec 2010 16:57:57 +0000
Received: from [10.61.82.140] (ams3-vpn-dhcp4749.cisco.com [10.61.82.140]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id oB6Gvv2h012367 for <isis-wg@ietf.org>; Mon, 6 Dec 2010 16:57:57 GMT
Message-ID: <4CFD1615.1080701@cisco.com>
Date: Mon, 06 Dec 2010 16:57:57 +0000
From: mike shand <mshand@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: isis-wg@ietf.org
References: <C9F49613-1F78-484A-B7D3-7E4028E0B9C3@castlepoint.net> <AE36820147909644AD2A7CA014B1FB520CBA0665@xmb-sjc-222.amer.cisco.com> <2EEE5586-CD41-4C13-8D13-FC69ED126A1F@castlepoint.net> <AE36820147909644AD2A7CA014B1FB520CBA0737@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520CBA0737@xmb-sjc-222.amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Isis-wg] draft-amante-isis-reverse-metric-01
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Dec 2010 16:56:35 -0000

On 06/12/2010 16:51, Les Ginsberg (ginsberg) wrote:
> Shane -
>
> I am not arguing syntax. My point is that using Reverse Metric TLV one
> has to make a configuration change (whether one command or two) on a
> router which:
>
> a)Temporarily changes the metric advertised by the local router
> b)Temporarily generates the Reverse Metric TLV requesting the peer to
> also change the metric it advertsies.
>
> That said, I am guilty of poor exposition - which is perhaps why Tony
> and I were not able to reach agreement. Let me provide a revised summary
> of the differences between the available solutions:
>
> P2P
> ---
>
> Without Reverse Metric TLV: Must temporarily alter metric configuration
> on both neighbors
>
> With Reverse Metric TLV: On one neighbor temporarily change the local
> metric AND
> configure the reverse metric TLV to be sent to the other neighbor
>
> The difference is then one config change on two neighbors vs two
> (conceptual) config
> changes on one neighbor.


But presumably, there is no reason why these two conceptual actions 
could not be triggered by a single CLI command.

Mike