Re: processing order of reach/unreach in rfc2858bis

Jeffrey Haas <jhaas@nexthop.com> Wed, 20 February 2002 20:31 UTC

Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id PAA01039 for <idr-archive@nic.merit.edu>; Wed, 20 Feb 2002 15:31:53 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id 73A51912AE; Wed, 20 Feb 2002 15:30:33 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id 28DF1912B0; Wed, 20 Feb 2002 15:30:33 -0500 (EST)
Delivered-To: idr@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id F08AA912AE for <idr@trapdoor.merit.edu>; Wed, 20 Feb 2002 15:30:31 -0500 (EST)
Received: by segue.merit.edu (Postfix) id D72E45DDAB; Wed, 20 Feb 2002 15:30:31 -0500 (EST)
Delivered-To: idr@merit.edu
Received: from presque.djinesys.com (presque.djinesys.com [198.108.88.2]) by segue.merit.edu (Postfix) with ESMTP id C654C5DD9C for <idr@merit.edu>; Wed, 20 Feb 2002 15:30:26 -0500 (EST)
Received: from jhaas.nexthop.com (jhaas.nexthop.com [64.211.218.31]) by presque.djinesys.com (8.11.3/8.11.1) with ESMTP id g1KKUN363953; Wed, 20 Feb 2002 15:30:23 -0500 (EST) (envelope-from jhaas@nexthop.com)
Received: (from jhaas@localhost) by jhaas.nexthop.com (8.11.0/8.11.0) id g1KKTqE23317; Wed, 20 Feb 2002 15:29:52 -0500 (EST)
Date: Wed, 20 Feb 2002 15:29:52 -0500
From: Jeffrey Haas <jhaas@nexthop.com>
To: Enke Chen <enke@redback.com>
Cc: idr@merit.edu
Subject: Re: processing order of reach/unreach in rfc2858bis
Message-ID: <20020220152952.S22759@nexthop.com>
References: <jhaas@nexthop.com> <20020220200541.30BA415D3C1@popserv1.redback.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20020220200541.30BA415D3C1@popserv1.redback.com>; from enke@redback.com on Wed, Feb 20, 2002 at 12:05:40PM -0800
X-NextHop-MailScanner: Found to be clean
Sender: owner-idr@merit.edu
Precedence: bulk

On Wed, Feb 20, 2002 at 12:05:40PM -0800, Enke Chen wrote:
> > MP_REACH_NLRI is enumerated before MP_UNREACH_NLRI in the path attributes.
> 
> It may not be the actual order in an update message.

Agreed.

> The deployed code
> processes the prefixes in the sequential order of their actual presence
> in an update message.  -- Enke

Well, we don't, for example.  But we're not the 800lb gorilla.

We also don't send updates that contain duplicate NLRI in multiple
inappropriate fields.  But we want to deal sanely with those that do.

-- 
Jeff Haas 
NextHop Technologies