ATOMIC AGGREGATE (section 9.1.4 of bgp 4-17)
Babu Prabesh <Babu.Prabesh@cosinecom.com> Tue, 15 January 2002 02:10 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 VAA05138 for <idr-archive@nic.merit.edu>; Mon, 14 Jan 2002 21:10:31 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id 9271491236; Mon, 14 Jan 2002 21:10:00 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id 4A29391238; Mon, 14 Jan 2002 21:10:00 -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 DEA8191236 for <idr@trapdoor.merit.edu>; Mon, 14 Jan 2002 21:09:58 -0500 (EST)
Received: by segue.merit.edu (Postfix) id B90445DF2D; Mon, 14 Jan 2002 21:09:58 -0500 (EST)
Delivered-To: idr@merit.edu
Received: from exchsrv2.cosinecom.com (proxy127.cosinecom.com [63.88.104.127]) by segue.merit.edu (Postfix) with ESMTP id 7036B5DF28 for <idr@merit.edu>; Mon, 14 Jan 2002 21:09:58 -0500 (EST)
Received: by exchsrv2.cosinecom.com with Internet Mail Service (5.5.2653.19) id <CYV8WWKG>; Mon, 14 Jan 2002 18:09:53 -0800
Received: from cosinecom.com (BPRABESH-NT [172.20.12.177]) by imchub1.cosinecom.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id CYWSMRQV; Mon, 14 Jan 2002 18:09:56 -0800
Message-ID: <3C439035.68CF936E@cosinecom.com>
From: Babu Prabesh <Babu.Prabesh@cosinecom.com>
Reply-To: Babu Prabesh <bprabesh@cosinecom.com>
To: idr@merit.edu
Subject: ATOMIC AGGREGATE (section 9.1.4 of bgp 4-17)
Date: Mon, 14 Jan 2002 18:13:09 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19D69.B9F43200"
Sender: owner-idr@merit.edu
Precedence: bulk
Section 9.1.4: overlapping routes states: "If a BGP speaker chooses to aggregate, then it MUST add ATOMIC_AGGREGATE attribute to the route. A route that carries ATOMIC_AGGREGATE attribute can not be de-aggregated. That is, the NLRI of this route can not be made more specific. Forwarding along such a route does not guarantee that IP packets will actually traverse only ASs listed in the AS_PATH attribute of the route". I was unsure of what de-aggregation means. Consider an example bgp bgp RTRA---------RTRB----------RTRC RTRA sends 5/8 with ATOMIC_AGGREGATE set to RTRB. RTRB has a 5/16 route (via static). Is the draft indicating that RTRB should only advertise 5/8 to RTRC and not advertise 5/16. Thanks Babu ############################################################################ ########################## This email communication may contain CONFIDENTIAL INFORMATION and is intended only for the use of the intended recipients identified above. If you are not the intended recipient of this communication, you must not use, disclose, distribute, copy or print this email. If you have received this communication in error, please immediately notify the sender by reply email, delete the communication and destroy all copies. ############################################################################ ##########################
- Re: ATOMIC AGGREGATE (section 9.1.4 of bgp 4-17) Yakov Rekhter
- RE: ATOMIC AGGREGATE (section 9.1.4 of bgp 4-17) Russ White
- Re: ATOMIC AGGREGATE (section 9.1.4 of bgp 4-17) Russ White
- ATOMIC AGGREGATE (section 9.1.4 of bgp 4-17) Babu Prabesh