No subject



Sat Mar 29 11:22:02 2003
Return-Path: xorp-cvs-admin@icir.org
Delivery-Date: Sat, 29 Mar 2003 11:23:03 -0800
Received: from wyvern.icir.org (wyvern.icir.org [192.150.187.14])
	by tigger.icir.org (8.12.3/8.12.3) with ESMTP id h2TJN3lu027314
	for <atanu@tigger.icir.org>; Sat, 29 Mar 2003 11:23:03 -0800 (PST)
	(envelope-from xorp-cvs-admin@icir.org)
Received: from ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11])
	by wyvern.icir.org (8.12.3/8.12.3) with ESMTP id h2TJN3fh009942;
	Sat, 29 Mar 2003 11:23:03 -0800 (PST)
	(envelope-from xorp-cvs-admin@icir.org)
Received: from fruitcake.icsi.Berkeley.EDU (localhost [127.0.0.1])
	by ICSI.Berkeley.EDU (8.9.0/8.9.0) with ESMTP id LAA27663;
	Sat, 29 Mar 2003 11:23:03 -0800 (PST)
Received: from wyvern.icir.org (wyvern.icir.org [192.150.187.14])
	by ICSI.Berkeley.EDU (8.9.0/8.9.0) with ESMTP id LAA27650
	for <xorp-cvs@icsi.berkeley.edu>; Sat, 29 Mar 2003 11:22:03 -0800 (PST)
Received: from vulture.icir.org (adsl-67-117-79-130.dsl.sntc01.pacbell.net [67.117.79.130])
	by wyvern.icir.org (8.12.3/8.12.3) with ESMTP id h2TJM2fh009936;
	Sat, 29 Mar 2003 11:22:02 -0800 (PST)
	(envelope-from mjh@vulture.icir.org)
Received: from vulture.icir.org (localhost [127.0.0.1])
	by vulture.icir.org (8.12.3/8.12.3) with ESMTP id h2TJM2cF028737;
	Sat, 29 Mar 2003 11:22:02 -0800 (PST)
	(envelope-from mjh@vulture.icir.org)
From: Mark Handley <mjh@icir.org>
X-Organisation: ICIR
To: pavlin@icir.org
cc: xorp-cvs@icir.org
Subject: Re: [Xorp-cvs] XORP cvs commit: ...
In-reply-to: Your message of "Sat, 29 Mar 2003 11:03:14."
             <200303291903.h2TJ3ECN097552@xorpc.icir.org> 
Date: Sat, 29 Mar 2003 11:22:02 -0800
Message-ID: <28736.1048965722@vulture.icir.org>
Sender: xorp-cvs-admin@icir.org
Errors-To: xorp-cvs-admin@icir.org
X-BeenThere: xorp-cvs@icir.org
X-Mailman-Version: 2.0
Precedence: bulk
List-Help: <mailto:xorp-cvs-request@icir.org?subject=help>
List-Post: <mailto:xorp-cvs@icir.org>
List-Subscribe: <http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-cvs>,
	<mailto:xorp-cvs-request@icir.org?subject=subscribe>
List-Id: Mailing list for XORP CVS commit messages <xorp-cvs.icir.org>
List-Unsubscribe: <http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-cvs>,
	<mailto:xorp-cvs-request@icir.org?subject=unsubscribe>


>	Open question: when the RIB sends route_info_changed[4,6], it actually
>	sets field metric:u32 in the XRL to global_metric() which is
>	actually (_admin_distance << 16) | _metric).
>	Now that there are two fields in the XRL interface: metric and
>	admin_distance, shall we change the metric value in the XRL
>	to be set to the protocol-specific metric(), or shall we keep
>	it set to global_metric()?

There are two consistent choices:

 - have route_info_changed just report global_metric() (as it originally did)

 - have route_info_changed report the protocol-specific metric and 
   admin distance, but not global_metric().

I'm OK with either, but not with the hybrid.

Cheers,
	Mark
_______________________________________________
Xorp-cvs mailing list
Xorp-cvs@icir.org
http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-cvs