IETF Logo Mail Archive

Re: When can NLRI and Withdrawn Route info be modified?

Paul Traina <pst@cisco.com> Sun, 05 May 1996 16:07 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13270; 5 May 96 12:07 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13266; 5 May 96 12:07 EDT
Received: from p-o.ans.net by CNRI.Reston.VA.US id aa08711; 5 May 96 12:07 EDT
Received: (from majordom@localhost) by p-o.ans.net (8.7.5/8.7.3) id QAA14954 for bgp-outgoing; Sun, 5 May 1996 16:00:08 GMT
X-Authentication-Warning: p-o.ans.net: majordom set sender to bgp-owner using -f
Message-Id: <199605051559.IAA13891@puli.cisco.com>
To: Ravi Chandra <rchandra@cisco.com>
Cc: bgp@ans.net
Subject: Re: When can NLRI and Withdrawn Route info be modified?
In-Reply-To: Your message of "Sat, 04 May 1996 23:04:46 PDT." <199605050604.XAA24488@greatdane.cisco.com>
Date: Sun, 05 May 1996 08:59:39 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Traina <pst@cisco.com>
X-Orig-Sender: bgp-owner@ans.net
Precedence: bulk
Reply-To: bgp@ans.net

But you should not rely on it.  The aggregator attribute may be omitted.

  From: Ravi Chandra <rchandra@cisco.com>
  Subject: Re: When can NLRI and Withdrawn Route info be modified? 
  > Ooops... I meant "AGGREGATOR".  The (short) section in the RFC describing
  > this says:
  > 
  >     AGGREGATOR is an optional transitive attribute which may be included
  >     in updates which are formed by aggregation (see Section 9.2.4.2).  A
  >     BGP speaker which performs route aggregation may add the AGGREGATOR
  >     attribute which shall contain its own AS number and IP address.
  > 
  > Is this also not widely implemented?
  
  
  I do not know about others.. cisco generates an aggregator attribute
  when an aggregate is generated.
  
  --ravi
  
  
  > 
  > Thanks,
  > 
  > Brad

v2.8.7 | Report a Bug | By Email