From owner-grow@darkwing.uoregon.edu Tue Aug 12 08:55:56 2003
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h7CFtuGj012214
	for <grow-outgoing@darkwing.uoregon.edu>; Tue, 12 Aug 2003 08:55:56 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h7CFtuIC012213
	for grow-outgoing; Tue, 12 Aug 2003 08:55:56 -0700 (PDT)
Received: from ginseng.lcs.mit.edu (IDENT:CU9MW/xBMHcnRK4psLJA+WprvRhqJ1tR@ginseng.lcs.mit.edu [18.31.0.38])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h7CFtsGk012195
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <grow@lists.uoregon.edu>; Tue, 12 Aug 2003 08:55:55 -0700 (PDT)
Received: from ginseng.lcs.mit.edu (localhost.localdomain [127.0.0.1])
	by ginseng.lcs.mit.edu (8.12.9/8.12.5) with ESMTP id h7CFtsuo030032;
	Tue, 12 Aug 2003 11:55:54 -0400
Received: (from feamster@localhost)
	by ginseng.lcs.mit.edu (8.12.9/8.12.9/Submit) id h7CFts4i030030;
	Tue, 12 Aug 2003 11:55:54 -0400
Date: Tue, 12 Aug 2003 11:55:54 -0400
From: Nick Feamster <feamster@lcs.mit.edu>
To: grow@lists.uoregon.edu
Subject: grow: question about draft-grow-bounded-longest-match-04.txt
Message-ID: <20030812155554.GF29067@lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

Hello,

I have a couple of questions about the following example from section 2.2
in draft-grow-bounded-longest-match-00.txt, and about how the proposed
mechanism works in other scenarios.

                      (   )
             /-------( AS2 )--------\
      (   ) /         (   )         ( R1   )       (   )
     ( AS1 )                       ( AS4  R2)-----( AS5 )
      (   ) \         (   )         ( R3   )       (   )
             \-------( AS3 )--------/
                      (   )


   o    AS1 is advertising 192.168.1.0/24 to both AS2 and AS3.

   o    AS2 is advertising both 192.168.1.0/24 and 192.168.0.0/16 into
        AS4

   o    AS3 is advertising 192.168.1.0/24 into AS4

   When R1 receives both the 192.168.1.0/24 and the 192.168.0.0/16 pre-
   fixes, it will mark the 192.168.1.0/24 as NO_EXPORT, and set the
   local preference to a high value, as described in the section Setting
   the Local Preference, below, and will then propogate this through
   AS4.


Questions:

	1. How does R3 distinguish between a failure between AS2 and R1,
		(in which it will want to advertise the /24 it hears from
		AS 3), and a failure between R1 and R3 (in which it will
		probably not want to readvertise the /24 it learns
		locally...although, under the proposed scheme, it will)?

	   If R3 can't hear R1 for whatever reason, it won't know
	   whether the AS2-R1 link has failed.  However, just because R3
	   can't hear R1 doesn't mean that R1 wants to advertise the
	   more specific route.

	2. This example seems to assume that AS1's upstreams will
	   readvertise directly to a common AS (in this case, AS4), that
	   will hear the overlapping prefixes.  It seems that there are
	   two more general cases that could break this assumption.

		a. AS2 goes through an intermediate AS before reaching
		AS4, which aggregates and simply readvertises the /16.
		In this case, I think R3 will still readvertise the /24
		to AS5, right?

		(I notice someone else pointed this out in a previous
		message, but I couldn't find a reply in the archive.)

		b. AS2 and AS3 do not share a common upstream provider.  
		In this case, does the proposed method apply?  

	3. If AS1 had a third upstream provider (say AS6) that does not
           advertise to AS4, then AS5 and its providers would only see the /16, 	   but AS6's upstreams would see the /24.  This would seem to break the 	   load balance that AS1 may have intended, right?

Thanks for clarifying my understanding.

Thanks,
Nick
____________________________________________________________
Web Archive:     http://darkwing.uoregon.edu/~llynch/grow/

From owner-grow@darkwing.uoregon.edu Tue Aug 26 00:48:27 2003
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h7Q7mRLR016245
	for <grow-outgoing@darkwing.uoregon.edu>; Tue, 26 Aug 2003 00:48:27 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h7Q7mRvf016244
	for grow-outgoing; Tue, 26 Aug 2003 00:48:27 -0700 (PDT)
Received: from info.ucl.ac.be (astrolabe.info.ucl.ac.be [130.104.229.109])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h7Q7mHLR016225
	for <grow@lists.uoregon.edu>; Tue, 26 Aug 2003 00:48:26 -0700 (PDT)
Received: from [127.0.0.1] (astrolabe [130.104.229.109])
	by info.ucl.ac.be (8.12.9/8.12.8) with ESMTP id h7Q7jt9H021580
	for <grow@lists.uoregon.edu>; Tue, 26 Aug 2003 09:45:55 +0200 (MET DST)
Subject: grow: Common utilizations of the BGP community attribute
From: Olivier Bonaventure <Bonaventure@info.ucl.ac.be>
To: grow@lists.uoregon.edu
Content-Type: text/plain
Message-Id: <1061883942.19881.127.camel@pcobo>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.3 
Date: 26 Aug 2003 09:45:42 +0200
Content-Transfer-Encoding: 7bit
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

Dear All,

Since the definition of the BGP community attribute in RFC1997, many
service providers have used it to implement various types of routing
policies. Despite the widespread utilization of the community attribute,
there very few available descriptions of the main utilizations of this
attribute.

Based on discussions with various people at IETF and among service
providers, it seems that it would be very useful to document in an
information document how the community attribute is used and to provide
some guidelines applicable to service providers. 

We have written a short internet draft which could serve as a basis for
such an informational RFC and would appreciate comments. The draft was
distributed in June, but you might have missed it during the Vienna
rush... 

http://www.ietf.org/internet-drafts/draft-bonaventure-quoitin-bgp-communities-00.txt

Best regards,


Olivier Bonaventure
-- 
CSE Dept. UCL, Belgium - http://www.info.ucl.ac.be/people/OBO/

____________________________________________________________
Web Archive:     http://darkwing.uoregon.edu/~llynch/grow/
