IETF Logo Mail Archive

Re: checking for empty AS_PATH

Yakov Rekhter <yakov@cisco.com> Fri, 18 July 1997 21:45 UTC

Received: from cnri by ietf.org id aa15826; 18 Jul 97 17:45 EDT
Received: from merit.edu (merit.edu [198.108.1.42]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid RAA17198 for <ietf-archive@cnri.reston.va.us>; Fri, 18 Jul 1997 17:44:28 -0400 (EDT)
Received: (from majordom@localhost) by merit.edu (8.8.5/8.8.5) id RAA14593 for idr-outgoing; Fri, 18 Jul 1997 17:17:21 -0400 (EDT)
Received: from interlock.ans.net (interlock.ans.net [147.225.5.5]) by merit.edu (8.8.5/8.8.5) with SMTP id RAA14582 for <bgp@merit.edu>; Fri, 18 Jul 1997 17:17:08 -0400 (EDT)
Received: by interlock.ans.net id AA01406 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Fri, 18 Jul 1997 17:17:06 -0400
Received: by interlock.ans.net (Internal Mail Agent-1); Fri, 18 Jul 1997 17:17:06 -0400
Message-Id: <199707182116.OAA20280@puli.cisco.com>
To: "John W. Stewart III" <jstewart@isi.edu>
Cc: Timothy O'Connor <toconnor@bbn.com>, bgp@ans.net
Subject: Re: checking for empty AS_PATH
In-Reply-To: Your message of "Fri, 18 Jul 97 17:07:21 EDT." <199707182107.RAA22994@central-services.east.isi.edu>
Date: Fri, 18 Jul 1997 14:16:58 -0700
From: Yakov Rekhter <yakov@cisco.com>
Sender: owner-idr@merit.edu
Precedence: bulk

John,
 
> are you assuming that the presence of a MP_REACH_NLRI
> attribute means that NLRI is present?  because if you
> mean to ignore the path attributes when the "standard"
> NLRI field is empty, then you could end up dropping
> legitimate multi-protocol NLRI on the floor
> 
> it's well possible that i'm being overly zealous in my
> interpretation of this thread, but given the novel use
> of attributes to carry NLRI, we've got to make sure
> that the base spec doesn't end up suggesting a way to
> implement that precludes them...

For a BGP speaker that supports multiprotocol extensions
the presence of a MP_REACH_NLRI attribute means that NLRI
is present.

Yakov.

v2.23.0 | Report a Bug | By Email