IETF Logo Mail Archive

When can NLRI and Withdrawn Route info be modified?

Brad Smith <brad@cse.ucsc.edu> Fri, 03 May 1996 06:58 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09919; 3 May 96 2:58 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09915; 3 May 96 2:58 EDT
Received: from p-o.ans.net by CNRI.Reston.VA.US id aa03844; 3 May 96 2:58 EDT
Received: (from majordom@localhost) by p-o.ans.net (8.7.5/8.7.3) id GAA41211 for bgp-outgoing; Fri, 3 May 1996 06:46:10 GMT
X-Authentication-Warning: p-o.ans.net: majordom set sender to bgp-owner using -f
Date: Thu, 2 May 1996 23:45:59 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Brad Smith <brad@cse.ucsc.edu>
Message-Id: <199605030645.XAA03220@toltec.cse.ucsc.edu>
To: bgp@ans.net
Subject: When can NLRI and Withdrawn Route info be modified?
Cc: brad@cse.ucsc.edu
X-Orig-Sender: bgp-owner@ans.net
Precedence: bulk
Reply-To: bgp@ans.net

Hello,

I have been attempting to gain an understanding of how BGP works from
the RFC (1771), and am confused on two related aspects of the protocol
processing; specifically, when can the NLRI and Withdrawn Route
information be modified?

A clear example of modifying the NLRI is when route aggregation is
performed; it is not discussed in the RFC (1771), but I assume that
the Withdrawn Route information must be also modified at this time
(corresponding to the changes in the NLRI)..?

Are there other times this can occur?

A related question is under what circumstances are ATOMIC_AGGREGATOR
path attributes generated?

Thanks in advance,

Brad Smith
Computer Sciences, UCSC
brad@cs.ucsc.edu

v2.8.7 | Report a Bug | By Email