Re: Route Aggregation
Paul Traina <pst@cisco.com> Wed, 24 May 1995 18:16 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07198;
24 May 95 14:16 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07192;
24 May 95 14:16 EDT
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa12336;
24 May 95 14:16 EDT
Received: by interlock.ans.net id AA64859
(InterLock SMTP Gateway 3.0 for iwg-out@ans.net);
Wed, 24 May 1995 13:40:33 -0400
Message-Id: <199505241740.AA64859@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2);
Wed, 24 May 1995 13:40:33 -0400
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1);
Wed, 24 May 1995 13:40:33 -0400
X-Authentication-Warning: feta.cisco.com: Host localhost.cisco.com didn't use
HELO protocol
To: Radha Gowda <rxg@joplin.proteon.com>
Cc: bgp@ans.net
Subject: Re: Route Aggregation
In-Reply-To: Your message of "Wed, 24 May 1995 10:43:09 EDT."
<199505241443.AA33468@interlock.ans.net>
Date: Wed, 24 May 1995 10:40:28 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Traina <pst@cisco.com>
From: Radha Gowda <rxg@joplin.proteon.com> Subject: Route Aggregation Can anybody tell me if my understanding of the AS_PATH aggregation rules are correct? 1. The following two AS paths need to be aggregated by say AS 1. (AS-5) [SEQ #1 0005] (AS-1) ==> [SEQ #1 0001] [SET #2 0003 0005] [SEQ #1 0003] (AS-3) yes 2. [SEQ #3 0002 0005 0004] ==> [SEQ #3 0001 0004 0002] [SET #2 0003 0005] [SEQ #3 0002 0003 0004] no 1 2 { 3 4 5 } is the best you can do. 1 { 2 3 4 5 } is also acceptable. You should not do what you wrote since 4 is out of order.
- Route Aggregation Radha Gowda
- Re: Route Aggregation John Krawczyk
- Re: Route Aggregation Paul Traina