To go forward, I'd like to say here that the new draft are prepared now concerning the global communities. But the approach used was quite other. Such recommendations are useful only if a lot of ISP support it. And I prefer to start from 1 - 2 very simple, intuitively clean, and safe communities, and (may be) reserver some community numbers for the future use in the same purposes. The proposals made here was on the right way, but was a very, very complex and discussional by the form, and I prefer (from ISP point of view) to see 2 standard community NOW to having 20 standard communities in the few future. Remember - any extra control can violate existing policies, and if some proposals can't be realized withouth such violation, they have not a chance to became global ones. Alex. /hope this short proposals will be published here in a few days/ On Fri, 8 Oct 1999, Hayden, Robin wrote:

Date: Fri, 8 Oct 1999 12:49:30 +0200 From: "Hayden, Robin" <Robin.Hayden@cwe.cwplc.com> To: "'nanog@merit.edu'" <nanog@merit.edu> Subject: RE: Regarding global BGP community values

Aleks Suhonen wrote:

...

Here is a sketch of the new well-known communities I have come up with:

0xFFFn:arg ... n=0 Never announce to AS <arg>. ...

Not a bad idea but how would you strip out the "arg" portion of the community value for use in your route maps (on a cisco that is)? Is this currently possible, or are you proposing that vendors (who can't already do this) upgrade their implementation in newer code versions?

Robin Hayden

Aleksei Roudnev, Network Operations Center, Relcom, Moscow (+7 095) 194-19-95 (Network Operations Center Hot Line),(+7 095) 230-41-41, N 13729 (pager) (+7 095) 196-72-12 (Support), (+7 095) 194-33-28 (Fax)