about ATOMIC_AGGREGATE

Hwang Hyo Jung <jung@h2o.kotel.co.kr> Tue, 03 January 1995 05:49 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13735; 3 Jan 95 0:49 EST
Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa13731; 3 Jan 95 0:49 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa28903; 3 Jan 95 0:49 EST
Received: by interlock.ans.net id AA39526 (InterLock SMTP Gateway 1.1 for iwg-out@ans.net); Tue, 3 Jan 1995 00:37:20 -0500
Received: by interlock.ans.net (Internal Mail Agent-4); Tue, 3 Jan 1995 00:37:20 -0500
Received: by interlock.ans.net (Internal Mail Agent-3); Tue, 3 Jan 1995 00:37:20 -0500
Received: by interlock.ans.net (Internal Mail Agent-2); Tue, 3 Jan 1995 00:37:20 -0500
Received: by interlock.ans.net (Internal Mail Agent-1); Tue, 3 Jan 1995 00:37:20 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Hwang Hyo Jung <jung@h2o.kotel.co.kr>
Message-Id: <199501030538.OAA05015@h2o.kotel.co.kr>
Subject: about ATOMIC_AGGREGATE
To: bgp@ans.net
Date: Tue, 3 Jan 1995 14:38:06 +0900 (KST)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Content-Length: 693

I have a question on bgp4.
I wonder if when I need to select the less specific route
without selecting the more specific one.
Then, propagating this route cause to occur misrouting or failure though
the path to the destination which belongs to the less specific
is not reachable. So the useless traffic will be occurs.

When does this feature works useful?

Jung..
-- 
 
----------------------------------------------------------------------
  @@@   Hwang, Hyojung              [jung@h2o.kotel.co.kr]
 @^l^@  High Speed Networking Team, Korea Telecom Research Laboratory
@@ v @@ 17, U-myun-Dong, Seocho-Gu, Seoul, Korea               
  >o<   (Tel) 82-02-526-5235        (Fax) 82-02-526-6942