BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
RFC 4456

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    idr mailing list <idr@ietf.org>, 
    idr chair <idr-chairs@tools.ietf.org>
Subject: Protocol Action: 'BGP Route Reflection - An Alternative 
         to Full Mesh IBGP' to Draft Standard 

The IESG has approved the following document:

- 'BGP Route Reflection - An Alternative to Full Mesh IBGP '
   <draft-ietf-idr-rfc2796bis-03.txt> as a Draft Standard

This document is the product of the Inter-Domain Routing Working Group. 

The IESG contact persons are Bill Fenner and Ross Callon.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-rfc2796bis-03.txt

Technical Summary

   This document describes the use and design of a method known as
   "Route Reflection" to alleviate the the need for "full mesh" IBGP.
   Route Reflection relaxes the rule that a route learned via IBGP
   must not be sent to another IBGP peer, for designated peers
   called "Route Reflectors".  It then replaces the full mesh among
   IBGP speakers with a single peering to a Route Reflector.
   This update adds an update to the BGP Decision Process.
 
Working Group Summary

   There was working group consensus to advance this
   specification to Draft Standard.
 
Protocol Quality
 
   Bill Fenner reviewed this specification for the IESG.  There are
   several known implementations, as described in the accompanying
   implementation report, available at the following URL:
   http://www.ietf.org/IESG/Implementations/RFC2796-implementations.txt