Last call for bgp-redistribution

andrewl at exodus.net andrewl at exodus.net
Mon Jul 1 20:43:21 UTC 2002


Greetings,

In going through this draft I have a couple of questions/concerns.

1) In the prefix/length community represented in Figure 6, how will
   IPv6 addresses be represented?

2) Given the (necessary) complexity of the community set, I believe most
   vendors will choose to implement the entire set in their code base.
   I can think of a number of issues that would come up with existing
   code that I'll need to discuss with specific vendors.  But, that
   aside, I think we need to add a section which encourages implementors
   to provide an efficent filtering/on/off syntax for this feature set.
   I can see things now, where this is on, and memory consumption and
   convergence time grows when every customer who can is sending us a
   whole mess of large, extended communities.  Perhaps a section like:

   Filtering and Precedence

   In order to allow operators maximum control over their policies, 
   implementations of this draft should provide a robust filtering
   syntax.  Filtering should include both type and action filters.
   For example: 
     Deny/Permit All Redistribution Communities
       Deny/Permit Action Type (Prepend|No_Export|Do not announce) 
         Deny/Permit/Limit Action Parameters (# of Prepends)
     Deny/Permit BGP Speakers_Filter Type (ASN|Prefix)

   Precendence of this community set in route processing should be
   adjustable.  An operator should be able to configure the router to
   interpret these well known community values at any point in the
   policy-processing order.  The default precedence should be processing
   these communities before processing other, manually configured, 
   policies.

3) As part of the implementation report, I would very much like to see
   a discussion on the impact a lot of these attributes have on 
   convergence times and router memory consumption, so operators know
   what to expect.

4) Section 2.2, end of first paragraph:
   
   ...and parameter should ignore all the redistribution communities
   concerning this action type and parameter.

   *change to*
  
   ...and parameter should ignore all the redistribution communities
   concerning this action type and parameter.  This ignore action MUST
   be logged.

Andrew

On Thu, Jun 20, 2002 at 06:44:06PM -0400, Mark Knopper wrote:
> User-Agent: Microsoft-Entourage/10.1.0.2006
> Date: Thu, 20 Jun 2002 18:44:06 -0400
> Subject: Last call for bgp-redistribution 
> From: Mark Knopper <mknopper at cisco.com>
> To: <ptomaine at shrubbery.net>
> Precedence: bulk
> X-OriginalArrivalTime: 20 Jun 2002 22:53:42.0085 (UTC) FILETIME=[53021750:01C218AD]
> 
> This is a Last Call for draft-ietf-ptomaine-bgp-redistribution-00.txt to be
> moved to Proposed Standard. The immediate reason is to cause the IANA to
> assign extended community type codes/values as specified in the draft.
> 
> The deadline for comments (2 weeks) is July 5.
> 
>     Mark
> 



More information about the Ptomaine mailing list