Re: Last Call: NOPEER community for BGP route scope control to BCP
Iljitsch van Beijnum <iljitsch@muada.com> Sun, 03 November 2002 21:29 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15100; Sun, 3 Nov 2002 16:29:35 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id QAA18543 for ietf-outbound.09@loki.ietf.org; Sun, 3 Nov 2002 16:20:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id QAA18517 for <ietf-mainout@loki.ietf.org>; Sun, 3 Nov 2002 16:19:36 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14912 for ietf-mainout@loki.ietf.org; Sun, 3 Nov 2002 16:17:08 -0500 (EST)
X-Authentication-Warning: ietf.org: majordom set sender to owner-ietf@ietf.org using -f
Received: from sequoia.muada.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14907 for <ietf@ietf.org>; Sun, 3 Nov 2002 16:17:04 -0500 (EST)
Received: from localhost (iljitsch@localhost) by sequoia.muada.com (8.11.3/8.9.3) with ESMTP id gA3LJ8650709 for <ietf@ietf.org>; Sun, 3 Nov 2002 22:19:09 +0100 (CET) (envelope-from iljitsch@muada.com)
Date: Sun, 03 Nov 2002 22:19:08 +0100
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: ietf@ietf.org
Subject: Re: Last Call: NOPEER community for BGP route scope control to BCP
In-Reply-To: <200211031606.LAA09183@ietf.org>
Message-ID: <20021103221008.T43861-100000@sequoia.muada.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ietf@ietf.org
Precedence: bulk
X-Loop: ietf@ietf.org
On Sun, 3 Nov 2002, The IESG wrote: > The IESG has received a request from the Prefix Taxonomy Ongoing > Measurement & Inter Network Experiment Working Group to consider NOPEER > community for BGP route scope control > <draft-ietf-ptomaine-nopeer-00.txt> as a BCP. > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send any comments to the > iesg@ietf.org or ietf@ietf.org mailing lists by 2002-11-17. As someone who does BGP configurations for a reasonable number of different ASes, I can't say this is the most useful new well-known community I could have imagined: as a rule, operators are more careful about what they advertise to transit networks than what they advertise to peers. But never mind that. What I'm missing in this draft is how vendors should implement this community. All the other well-known communities trigger actions in BGP without further user configuration. From the text I gather that this is not to be the case with this new community. However, this is never explicitly stated.
- Re: Last Call: NOPEER community for BGP route sco… Iljitsch van Beijnum