From owner-grow@darkwing.uoregon.edu Mon Jun  2 23:35:14 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 h536ZEUA012408
	for <grow-outgoing@darkwing.uoregon.edu>; Mon, 2 Jun 2003 23:35:14 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h536ZElR012407
	for grow-outgoing; Mon, 2 Jun 2003 23:35:14 -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 h536ZCUA012253
	for <grow@lists.uoregon.edu>; Mon, 2 Jun 2003 23:35:13 -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 h536XTN9021021;
	Tue, 3 Jun 2003 08:33:30 +0200 (MET DST)
Subject: Re: grow: [GROW] Agenda Items for Vienna
From: Olivier Bonaventure <Bonaventure@info.ucl.ac.be>
To: David Meyer <dmm@1-4-5.net>
Cc: grow@lists.uoregon.edu, vijay@umbc.edu,
   Bruno Quoitin <bqu@infonet.fundp.ac.be>
In-Reply-To: <20030523103809.A11012@1-4-5.net>
References: <20030523103809.A11012@1-4-5.net>
Content-Type: text/plain
Organization: 
Message-Id: <1054587639.722.156.camel@pcobo>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 03 Jun 2003 08:34:24 +0200
Content-Transfer-Encoding: 7bit
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

David,
> 
> 	Its about time to start thinking about agenda items for
> 	the Vienna ITEF. Please forward any GROW agenda items
> 	you might have to me.

Last year, Bruno Quoitin and I wrote a survey of the utilization of the
BGP community attribute based on analysis of RPSL specifications in the
RIPE whois database and on routing tables collected by RouteViews and
the RIPE RIS project. This draft, draft-quoitin-bgp-comm-survey-00.txt,
has now expired.

Since the publication of RFC1998, the BGP Community attribute has been
used for various purposes that were not envisionned initially. We intend
to describe the most common usages of this attribute in a new draft that
should be ready within a few weeks and could serve as a BCP document to
describe those utilizations of the community attribute.

This draft might fit in the GROW WG.

Best regards,


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

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

From owner-grow@darkwing.uoregon.edu Tue Jun  3 08:17:18 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 h53FHInr025103
	for <grow-outgoing@darkwing.uoregon.edu>; Tue, 3 Jun 2003 08:17:18 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h53FHIwW025100
	for grow-outgoing; Tue, 3 Jun 2003 08:17:18 -0700 (PDT)
Message-Id: <200306031146.HAA27267@ietf.org>
To: grow@lists.uoregon.edu
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: grow: I-D ACTION:draft-ietf-grow-bgp-redistribution-00.txt
Date: Tue, 03 Jun 2003 07:46:37 -0400
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts
directories. This draft is a work item of the Global Routing Operations
Working Group of the IETF.

	Title		: Controlling the redistribution of BGP routes
	Author(s)	: O. Bonaventure et al.
	Filename	: draft-ietf-grow-bgp-redistribution-00.txt
	Pages		: 16
	Date		: 2003-6-2

This document proposes the redistribution extended community.  This
new extended community allows a router to influence how a specific
route should be redistributed towards a specified set of eBGP
speakers. Several types of redistribution communities are proposed.
The first type may be used to indicate that a specific route should
not be announced over a specified set of eBGP sessions. The second
type may be used to indicate that the attached route should only be
announced with the NO_EXPORT community over the specified set of eBGP
sessions and the third type may be used to indicate that the attached
route should be prepended n times when announced over a specified set
of eBGP sessions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-bgp-redistribution-00.txt

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-grow-bgp-redistribution-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-grow-bgp-redistribution-00.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-6-2145422.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-grow-bgp-redistribution-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-grow-bgp-redistribution-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-6-2145422.I-D@ietf.org>

--OtherAccess--

--NextPart--


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

From owner-grow@darkwing.uoregon.edu Wed Jun  4 09:54:54 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 h54Gssnr017895
	for <grow-outgoing@darkwing.uoregon.edu>; Wed, 4 Jun 2003 09:54:54 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h54Gss3t017887
	for grow-outgoing; Wed, 4 Jun 2003 09:54:54 -0700 (PDT)
Message-Id: <200306041157.HAA12845@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: grow@lists.uoregon.edu
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: grow: I-D ACTION:draft-grow-bounded-longest-match-00.txt
Date: Wed, 04 Jun 2003 07:57:12 -0400
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Global Routing Operations Working Group of the IETF.

	Title		: Bounding Longest Match Considered
	Author(s)	: T. Hardie, R. White
	Filename	: draft-grow-bounded-longest-match-00.txt
	Pages		: 8
	Date		: 2003-6-3

Some ASes currently use length-based filters to manage the size of
the routing table they use and propagate.  This draft explores an
alternative to length-based filters which allows for more automatic
configuration and which provides for better redundancy.
Rather than use a filter, this draft proposes a method of modifying
the BGP longest match algorithm by setting a bound on the prefix
lengths eligible for preference.  A bound would operate on long
prefixes when covering route announcements are available; in certain
circumstances it would cause a router to prefer an aggregate over a
more specific route announcement.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-grow-bounded-longest-match-00.txt

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-grow-bounded-longest-match-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-grow-bounded-longest-match-00.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-6-3151234.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-grow-bounded-longest-match-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-grow-bounded-longest-match-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-6-3151234.I-D@ietf.org>

--OtherAccess--

--NextPart--


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

From owner-grow@darkwing.uoregon.edu Mon Jun  9 21:25:37 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 h5A4Pbnr004213
	for <grow-outgoing@darkwing.uoregon.edu>; Mon, 9 Jun 2003 21:25:37 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h5A4PbFM004210
	for grow-outgoing; Mon, 9 Jun 2003 21:25:37 -0700 (PDT)
Received: from xoanon.mcwest.org (xoanon.Colorado.EDU [198.11.17.3])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h5A4PZnr003997
	for <grow@lists.uoregon.edu>; Mon, 9 Jun 2003 21:25:35 -0700 (PDT)
Received: from xoanon.mcwest.org (localhost [127.0.0.1])
	by xoanon.mcwest.org (8.11.6p2/8.11.6) with ESMTP id h5A4PUs71035;
	Mon, 9 Jun 2003 22:25:30 -0600 (MDT)
	(envelope-from mccreary@xoanon.mcwest.org)
Message-Id: <200306100425.h5A4PUs71035@xoanon.mcwest.org>
To: Olivier Bonaventure <Bonaventure@info.ucl.ac.be>
cc: grow@lists.uoregon.edu
From: "Sean McCreary" <mccreary@pch.net>
Subject: Re: grow: [GROW] Agenda Items for Vienna 
In-reply-to: Your message of "03 Jun 2003 08:34:24 +0200."
             <1054587639.722.156.camel@pcobo> 
Date: Mon, 09 Jun 2003 22:25:30 -0600
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

Olivier Bonaventure <Bonaventure@info.ucl.ac.be> wrote:
[...]
>Last year, Bruno Quoitin and I wrote a survey of the utilization of the
>BGP community attribute based on analysis of RPSL specifications in the
>RIPE whois database and on routing tables collected by RouteViews and
>the RIPE RIS project. This draft, draft-quoitin-bgp-comm-survey-00.txt,
>has now expired.
>
>Since the publication of RFC1998, the BGP Community attribute has been
>used for various purposes that were not envisionned initially. We intend
>to describe the most common usages of this attribute in a new draft that
>should be ready within a few weeks and could serve as a BCP document to
>describe those utilizations of the community attribute.

At NANOG28 there were questions raised during Phil Smith's tutorial that
might have been answered by your draft.  Have you resubmitted it, or can
you make a copy available elsewhere?
--
Sean McCreary                                                 mccreary@pch.net
____________________________________________________________
Web Archive:     http://darkwing.uoregon.edu/~llynch/grow/

From owner-grow@darkwing.uoregon.edu Tue Jun 10 00:20:13 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 h5A7KDnr003225
	for <grow-outgoing@darkwing.uoregon.edu>; Tue, 10 Jun 2003 00:20:13 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h5A7KDCc003224
	for grow-outgoing; Tue, 10 Jun 2003 00:20:13 -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 h5A7Junr003019
	for <grow@lists.uoregon.edu>; Tue, 10 Jun 2003 00:20:12 -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 h5A7IQN9017209;
	Tue, 10 Jun 2003 09:18:26 +0200 (MET DST)
Subject: Re: grow: [GROW] Agenda Items for Vienna
From: Olivier Bonaventure <Bonaventure@info.ucl.ac.be>
To: Sean McCreary <mccreary@pch.net>
Cc: grow@lists.uoregon.edu, Bruno Quoitin <bqu@infonet.fundp.ac.be>
In-Reply-To: <200306100425.h5A4PUs71035@xoanon.mcwest.org>
References: <200306100425.h5A4PUs71035@xoanon.mcwest.org>
Content-Type: text/plain
Organization: 
Message-Id: <1055229575.9204.205.camel@pcobo>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 10 Jun 2003 09:19:35 +0200
Content-Transfer-Encoding: 7bit
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

Sean, 

> >Last year, Bruno Quoitin and I wrote a survey of the utilization of the
> >BGP community attribute based on analysis of RPSL specifications in the
> >RIPE whois database and on routing tables collected by RouteViews and
> >the RIPE RIS project. This draft, draft-quoitin-bgp-comm-survey-00.txt,
> >has now expired.
> >
> >Since the publication of RFC1998, the BGP Community attribute has been
> >used for various purposes that were not envisionned initially. We intend
> >to describe the most common usages of this attribute in a new draft that
> >should be ready within a few weeks and could serve as a BCP document to
> >describe those utilizations of the community attribute.
> 
> At NANOG28 there were questions raised during Phil Smith's tutorial that
> might have been answered by your draft.  Have you resubmitted it, or can
> you make a copy available elsewhere?

We are finalizing the draft and it will be ready within one or two
weeks. The old version (March 2002) is still available from 
http://www.info.ucl.ac.be/people/OBO/biblio.html
The new version will contain more tutorial information. If you send some
of the questions raised during the NANOG tutorial, we could try to
address them in our draft.

Best regards,


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

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

From owner-grow@darkwing.uoregon.edu Tue Jun 10 01:27:41 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 h5A8Rfnr028264
	for <grow-outgoing@darkwing.uoregon.edu>; Tue, 10 Jun 2003 01:27:41 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h5A8Rfqw028263
	for grow-outgoing; Tue, 10 Jun 2003 01:27:41 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.74.5])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h5A8Rdnr028183
	for <grow@lists.uoregon.edu>; Tue, 10 Jun 2003 01:27:40 -0700 (PDT)
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 10 Jun 2003 10:26:35 +0100
Received: from philsmit-w2k01.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h5A8PMqv010132;
	Tue, 10 Jun 2003 10:25:26 +0200 (MET DST)
Message-Id: <5.1.0.14.2.20030610182255.079e9130@pfs-pc.cisco.com>
X-Sender: philip@pfs-pc.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 10 Jun 2003 18:26:47 +1000
To: Olivier Bonaventure <Bonaventure@info.ucl.ac.be>
From: Philip Smith <pfs@cisco.com>
Subject: grow: Re: [GROW] Agenda Items for Vienna
Cc: Sean McCreary <mccreary@pch.net>, grow@lists.uoregon.edu,
   Bruno Quoitin <bqu@infonet.fundp.ac.be>
In-Reply-To: <1055229575.9204.205.camel@pcobo>
References: <200306100425.h5A4PUs71035@xoanon.mcwest.org>
 <200306100425.h5A4PUs71035@xoanon.mcwest.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

At 09:19 10/06/2003 +0200, Olivier Bonaventure wrote:

>We are finalizing the draft and it will be ready within one or two
>weeks. The old version (March 2002) is still available from
>http://www.info.ucl.ac.be/people/OBO/biblio.html
>The new version will contain more tutorial information. If you send some
>of the questions raised during the NANOG tutorial, we could try to
>address them in our draft.

Olivier, the main thing people were asking me about, certainly after I gave 
the multihoming tutorial, was about the lack of documentation and 
coordination of community values in general use. I think folks were just 
looking for guidelines and examples of what they could use, what their 
peers and upstreams were using, and how to generally take advantage of the 
community attribute.

I'd promised for at least two years or so now to put some text around the 
Tiscali/Nacamar values (as now used by BT Ignite, for example), but thus 
far it has remained a promise. :-( Would love to see your new draft, 
especially if it goes some way to helping folks make greater use of 
communities within their own networks, and between themselves and their 
immediate peers.

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

From owner-grow@darkwing.uoregon.edu Tue Jun 10 06:39:11 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 h5ADdBnr023437
	for <grow-outgoing@darkwing.uoregon.edu>; Tue, 10 Jun 2003 06:39:11 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h5ADdBO9023435
	for grow-outgoing; Tue, 10 Jun 2003 06:39:11 -0700 (PDT)
Received: from presque.nexthop.com (dns.nexthop.com [65.247.36.216])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h5ADd8nr023379
	for <grow@lists.uoregon.edu>; Tue, 10 Jun 2003 06:39:09 -0700 (PDT)
Received: (from root@localhost)
	by presque.nexthop.com (8.12.8/8.11.1) id h5ADckQA012884;
	Tue, 10 Jun 2003 09:38:46 -0400 (EDT)
	(envelope-from jhaas@jhaas.nexthop.com)
Received: from jhaas.nexthop.com (jhaas.nexthop.com [65.247.36.31])
	by presque.nexthop.com (8.12.8/8.12.8) with ESMTP id h5ADcgiW012877;
	Tue, 10 Jun 2003 09:38:42 -0400 (EDT)
	(envelope-from jhaas@jhaas.nexthop.com)
Received: (from jhaas@localhost)
	by jhaas.nexthop.com (8.11.3nb1/8.11.3) id h5ADcbH02456;
	Tue, 10 Jun 2003 09:38:37 -0400 (EDT)
Date: Tue, 10 Jun 2003 09:38:37 -0400
From: Jeffrey Haas <jhaas@nexthop.com>
To: Philip Smith <pfs@cisco.com>
Cc: grow@lists.uoregon.edu
Subject: Re: grow: Re: [GROW] Agenda Items for Vienna
Message-ID: <20030610093836.A2439@nexthop.com>
References: <200306100425.h5A4PUs71035@xoanon.mcwest.org> <200306100425.h5A4PUs71035@xoanon.mcwest.org> <1055229575.9204.205.camel@pcobo> <5.1.0.14.2.20030610182255.079e9130@pfs-pc.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <5.1.0.14.2.20030610182255.079e9130@pfs-pc.cisco.com>; from pfs@cisco.com on Tue, Jun 10, 2003 at 06:26:47PM +1000
X-Virus-Scanned: by AMaViS perl-11
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

Philip,

On Tue, Jun 10, 2003 at 06:26:47PM +1000, Philip Smith wrote:
> Olivier, the main thing people were asking me about, certainly after I gave 
> the multihoming tutorial, was about the lack of documentation and 
> coordination of community values in general use. I think folks were just 
> looking for guidelines and examples of what they could use, what their 
> peers and upstreams were using, and how to generally take advantage of the 
> community attribute.

One of the motivations for the redistribution extended communities was
to take commonly implemented communities that affect redistribution
policy and make it easy for vendors to implement knobs that did the
common stuff. :-)

-- 
Jeff Haas 
NextHop Technologies
____________________________________________________________
Web Archive:     http://darkwing.uoregon.edu/~llynch/grow/

From owner-grow@darkwing.uoregon.edu Tue Jun 10 09:19:37 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 h5AGJbOG019762
	for <grow-outgoing@darkwing.uoregon.edu>; Tue, 10 Jun 2003 09:19:37 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h5AGJbmD019760
	for grow-outgoing; Tue, 10 Jun 2003 09:19:37 -0700 (PDT)
Received: from presque.nexthop.com (dns.nexthop.com [65.247.36.216])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h5AGJZOG019608
	for <grow@lists.uoregon.edu>; Tue, 10 Jun 2003 09:19:36 -0700 (PDT)
Received: (from root@localhost)
	by presque.nexthop.com (8.12.8/8.11.1) id h5AGJSIJ019294;
	Tue, 10 Jun 2003 12:19:28 -0400 (EDT)
	(envelope-from jhaas@jhaas.nexthop.com)
Received: from jhaas.nexthop.com (jhaas.nexthop.com [65.247.36.31])
	by presque.nexthop.com (8.12.8/8.12.8) with ESMTP id h5AGJLiW019262;
	Tue, 10 Jun 2003 12:19:21 -0400 (EDT)
	(envelope-from jhaas@jhaas.nexthop.com)
Received: (from jhaas@localhost)
	by jhaas.nexthop.com (8.11.3nb1/8.11.3) id h5AGJGH04333;
	Tue, 10 Jun 2003 12:19:16 -0400 (EDT)
Date: Tue, 10 Jun 2003 12:19:16 -0400
From: Jeffrey Haas <jhaas@nexthop.com>
To: john heasley <heas@shrubbery.net>
Cc: grow@lists.uoregon.edu
Subject: Re: grow: Re: [GROW] Agenda Items for Vienna
Message-ID: <20030610121916.E2439@nexthop.com>
References: <200306100425.h5A4PUs71035@xoanon.mcwest.org> <200306100425.h5A4PUs71035@xoanon.mcwest.org> <1055229575.9204.205.camel@pcobo> <5.1.0.14.2.20030610182255.079e9130@pfs-pc.cisco.com> <20030610093836.A2439@nexthop.com> <20030610161113.GA19938@shrubbery.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20030610161113.GA19938@shrubbery.net>; from heas@shrubbery.net on Tue, Jun 10, 2003 at 09:11:13AM -0700
X-Virus-Scanned: by AMaViS perl-11
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

On Tue, Jun 10, 2003 at 09:11:13AM -0700, john heasley wrote:
> hmm, do you really want vendors to do 'the common stuff', peer prepending
> for example?  i may have taken your comment too literally, but the social
> aspects of peering policy make such a proposition disagreable.

The most common knobs that customers are usually offered are roughly:
o prepend this route
o don't announce this route
o don't export this route outside of your AS.

Other knobs that are commonly offered are:
o prefer this route
o deprefer this route

The first set of things are what the redistribution draft is trying
to accomplish - provide a way for a provider to get these knobs without
needing to be in route-map hell.  The fact that you can implement
these communities softly without vendor cooperation is handy.

To address some of your possible issue with this, the knobs are
explicitly noted as something you may want to be able to shut off
with some neighbors.

Also note that I used "peering" in the "neighbor" sense, not the
financial sense.

> as far as i am concerned, the greatest and possibly only value of extended
> communities are the non-transitive bit and the ability to represent a 4
> octet AS.

Thats a biggy.  The fact that its structured has proved to be a boon
for a lot of IETF WG's that want to distribute stuff into BGP that
needs to be tagged.

> the remainder seems to be over complication of what has been a
> simple unsigned 4 octet value. :)

Arguably, while a boon, its a pain to have all this 
extended community parsing code.

-- 
Jeff Haas 
NextHop Technologies
____________________________________________________________
Web Archive:     http://darkwing.uoregon.edu/~llynch/grow/

From owner-grow@darkwing.uoregon.edu Tue Jun 10 09:11:18 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 h5AGBIOG009764
	for <grow-outgoing@darkwing.uoregon.edu>; Tue, 10 Jun 2003 09:11:18 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h5AGBIsN009763
	for grow-outgoing; Tue, 10 Jun 2003 09:11:18 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h5AGBHOG009695
	for <grow@lists.uoregon.edu>; Tue, 10 Jun 2003 09:11:17 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053)
	id D87D617D031; Tue, 10 Jun 2003 16:11:13 +0000 (UTC)
Date: Tue, 10 Jun 2003 09:11:13 -0700
From: john heasley <heas@shrubbery.net>
To: Jeffrey Haas <jhaas@nexthop.com>
Cc: Philip Smith <pfs@cisco.com>, grow@lists.uoregon.edu
Subject: Re: grow: Re: [GROW] Agenda Items for Vienna
Message-ID: <20030610161113.GA19938@shrubbery.net>
References: <200306100425.h5A4PUs71035@xoanon.mcwest.org> <200306100425.h5A4PUs71035@xoanon.mcwest.org> <1055229575.9204.205.camel@pcobo> <5.1.0.14.2.20030610182255.079e9130@pfs-pc.cisco.com> <20030610093836.A2439@nexthop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030610093836.A2439@nexthop.com>
User-Agent: Mutt/1.4i
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: awe, not the good cheek
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

Tue, Jun 10, 2003 at 09:38:37AM -0400, Jeffrey Haas:
> Philip,
> 
> On Tue, Jun 10, 2003 at 06:26:47PM +1000, Philip Smith wrote:
> > Olivier, the main thing people were asking me about, certainly after I gave 
> > the multihoming tutorial, was about the lack of documentation and 
> > coordination of community values in general use. I think folks were just 
> > looking for guidelines and examples of what they could use, what their 
> > peers and upstreams were using, and how to generally take advantage of the 
> > community attribute.
> 
> One of the motivations for the redistribution extended communities was
> to take commonly implemented communities that affect redistribution
> policy and make it easy for vendors to implement knobs that did the
> common stuff. :-)

hmm, do you really want vendors to do 'the common stuff', peer prepending
for example?  i may have taken your comment too literally, but the social
aspects of peering policy make such a proposition disagreable.

as far as i am concerned, the greatest and possibly only value of extended
communities are the non-transitive bit and the ability to represent a 4
octet AS.  the remainder seems to be over complication of what has been a
simple unsigned 4 octet value. :)

> -- 
> Jeff Haas 
> NextHop Technologies
> ____________________________________________________________
> Web Archive:     http://darkwing.uoregon.edu/~llynch/grow/
____________________________________________________________
Web Archive:     http://darkwing.uoregon.edu/~llynch/grow/

From owner-grow@darkwing.uoregon.edu Tue Jun 10 09:55:10 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 h5AGtAOG001856
	for <grow-outgoing@darkwing.uoregon.edu>; Tue, 10 Jun 2003 09:55:10 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h5AGtAB2001852
	for grow-outgoing; Tue, 10 Jun 2003 09:55:10 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h5AGt9OG001834
	for <grow@lists.uoregon.edu>; Tue, 10 Jun 2003 09:55:09 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053)
	id 3715217D031; Tue, 10 Jun 2003 16:55:09 +0000 (UTC)
Date: Tue, 10 Jun 2003 09:55:09 -0700
From: john heasley <heas@shrubbery.net>
To: Jeffrey Haas <jhaas@nexthop.com>
Cc: grow@lists.uoregon.edu
Subject: Re: grow: Re: [GROW] Agenda Items for Vienna
Message-ID: <20030610165509.GH19938@shrubbery.net>
References: <200306100425.h5A4PUs71035@xoanon.mcwest.org> <200306100425.h5A4PUs71035@xoanon.mcwest.org> <1055229575.9204.205.camel@pcobo> <5.1.0.14.2.20030610182255.079e9130@pfs-pc.cisco.com> <20030610093836.A2439@nexthop.com> <20030610161113.GA19938@shrubbery.net> <20030610121916.E2439@nexthop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030610121916.E2439@nexthop.com>
User-Agent: Mutt/1.4i
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: awe, not the good cheek
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

Tue, Jun 10, 2003 at 12:19:16PM -0400, Jeffrey Haas:
> On Tue, Jun 10, 2003 at 09:11:13AM -0700, john heasley wrote:
> > hmm, do you really want vendors to do 'the common stuff', peer prepending
> > for example?  i may have taken your comment too literally, but the social
> > aspects of peering policy make such a proposition disagreable.
> 
> The most common knobs that customers are usually offered are roughly:
> o prepend this route
> o don't announce this route
> o don't export this route outside of your AS.
> 
> Other knobs that are commonly offered are:
> o prefer this route
> o deprefer this route
> 
> The first set of things are what the redistribution draft is trying
> to accomplish - provide a way for a provider to get these knobs without
> needing to be in route-map hell.  The fact that you can implement

_route-maps_ are hell.  perhaps applying duct tape in the wrong place?

> these communities softly without vendor cooperation is handy.
> 
> To address some of your possible issue with this, the knobs are
> explicitly noted as something you may want to be able to shut off
> with some neighbors.

better be a MUST have .... :)  always seems easier when the vendor isnt
involved.

> Also note that I used "peering" in the "neighbor" sense, not the
> financial sense.
> 
> > as far as i am concerned, the greatest and possibly only value of extended
> > communities are the non-transitive bit and the ability to represent a 4
> > octet AS.
> 
> Thats a biggy.  The fact that its structured has proved to be a boon
> for a lot of IETF WG's that want to distribute stuff into BGP that
> needs to be tagged.
> 
> > the remainder seems to be over complication of what has been a
> > simple unsigned 4 octet value. :)
> 
> Arguably, while a boon, its a pain to have all this 
> extended community parsing code.

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

From owner-grow@darkwing.uoregon.edu Thu Jun 19 03:04:25 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 h5JA4PfD006896
	for <grow-outgoing@darkwing.uoregon.edu>; Thu, 19 Jun 2003 03:04:25 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h5JA4Pix006895
	for grow-outgoing; Thu, 19 Jun 2003 03:04:25 -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 h5JA4HfD006879
	for <grow@lists.uoregon.edu>; Thu, 19 Jun 2003 03:04:18 -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 h5JA2RBJ017441;
	Thu, 19 Jun 2003 12:02:28 +0200 (MET DST)
Subject: Re: grow: Re: [GROW] Agenda Items for Vienna
From: Olivier Bonaventure <Bonaventure@info.ucl.ac.be>
To: Philip Smith <pfs@cisco.com>
Cc: Sean McCreary <mccreary@pch.net>, grow@lists.uoregon.edu,
   Bruno Quoitin <bqu@infonet.fundp.ac.be>
In-Reply-To: <5.1.0.14.2.20030610182255.079e9130@pfs-pc.cisco.com>
References: <200306100425.h5A4PUs71035@xoanon.mcwest.org>
	 <200306100425.h5A4PUs71035@xoanon.mcwest.org>
	 <5.1.0.14.2.20030610182255.079e9130@pfs-pc.cisco.com>
Content-Type: text/plain
Organization: 
Message-Id: <1056017034.694.253.camel@pcobo>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 19 Jun 2003 12:03:54 +0200
Content-Transfer-Encoding: 7bit
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

Philip,
> 
> >We are finalizing the draft and it will be ready within one or two
> >weeks. The old version (March 2002) is still available from
> >http://www.info.ucl.ac.be/people/OBO/biblio.html
> >The new version will contain more tutorial information. If you send some
> >of the questions raised during the NANOG tutorial, we could try to
> >address them in our draft.
> 
> Olivier, the main thing people were asking me about, certainly after I gave 
> the multihoming tutorial, was about the lack of documentation and 
> coordination of community values in general use. I think folks were just 
> looking for guidelines and examples of what they could use, what their 
> peers and upstreams were using, and how to generally take advantage of the 
> community attribute.
> 

The draft has been sent to the IETF secretariat. It will appear within
several days on the IETF annoucements list. In the mean time, you can
retrieve it from
http://www.info.ucl.ac.be/people/OBO/papers/draft-bq-bgp-communities-00.txt

Comments are of course more than welcome

Best regards,


Olivier Bonaventure

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

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

From owner-grow@darkwing.uoregon.edu Fri Jun 20 10:19:46 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 h5KHJkfD017241
	for <grow-outgoing@darkwing.uoregon.edu>; Fri, 20 Jun 2003 10:19:46 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h5KHJkTV017237
	for grow-outgoing; Fri, 20 Jun 2003 10:19:46 -0700 (PDT)
Received: from smtp.uc3m.es (smtp02.uc3m.es [163.117.136.122])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h5KHJgfD017144
	for <grow@lists.uoregon.edu>; Fri, 20 Jun 2003 10:19:45 -0700 (PDT)
Received: from smtp02.uc3m.es (localhost [127.0.0.1])
	by smtp.uc3m.es (Postfix) with ESMTP id 77BD543163
	for <grow@lists.uoregon.edu>; Fri, 20 Jun 2003 19:19:36 +0200 (CEST)
Received: from varpa.it.uc3m.es (varpa.it.uc3m.es [163.117.139.253])
	by smtp02.uc3m.es (Postfix) with ESMTP id DDABD99F8F
	for <grow@lists.uoregon.edu>; Fri, 20 Jun 2003 19:19:35 +0200 (CEST)
Received: from localhost.localdomain (marcelo@presto.it.uc3m.es [163.117.139.134])
	by varpa.it.uc3m.es (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id TAA32540
	for <grow@lists.uoregon.edu>; Fri, 20 Jun 2003 19:19:35 +0200
X-Authentication-Warning: varpa.it.uc3m.es: Host marcelo@presto.it.uc3m.es [163.117.139.134] claimed to be localhost.localdomain
Subject: grow: a question about draft-grow-bounded-longest-match-00.txt
From: marcelo bagnulo <marcelo@it.uc3m.es>
To: grow@lists.uoregon.edu
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.5 
Date: 20 Jun 2003 19:19:16 +0200
Message-Id: <1056129557.563.68.camel@presto>
Mime-Version: 1.0
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

Hi,

I have a question about draft-grow-bounded-longest-match-00.txt

I do not understand how this mechanism works in a different scenario
than the one included in the draft.

For instance consider the following alternative scenario:

                      (   )
             /-------( AS2 )---( AS6 )-----\
      (   ) /         (   )              ( 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
        AS6

   o    AS3 is advertising 192.168.1.0/24 into AS4


If i understand the proposed mechanism correctly, AS6 advertises only
192.168.0.0/16 to AS4. Is this correct?

If this is so, then AS4 will always prefer forwarding traffic through
AS3 and it won't forward traffic through AS6 if the path through AS3 is
available.

So if my understanding is correct, the proposed mechanisms forward
traffic through both links only if the third AS is common to both paths
(just like in the scenario depicted in the draft) if this is not the
case, the resulting behavior is that one path is only used as a backup.

Is this correct? am i missing something?

This could be solved if the AS6 does not uses the mechanism, but the
question then is does a AS knows when it has to apply it.

Perhaps an AS should only apply the mechanisms if it receives an two
advertisements of overlapping prefixes AND it also receives the longest
prefix from another AS...however, this would rise the same problems when
the end site is multi-homed to 3 providers.

Thanks, marcelo


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

From owner-grow@darkwing.uoregon.edu Tue Jun 24 09:05:23 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 h5OG5MeX016239
	for <grow-outgoing@darkwing.uoregon.edu>; Tue, 24 Jun 2003 09:05:22 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.9/8.12.9/Submit) id h5OG5MPK016234
	for grow-outgoing; Tue, 24 Jun 2003 09:05:22 -0700 (PDT)
Received: from sith.maoz.com (sith.maoz.com [205.167.76.10])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h5OG5MeX016226
	for <grow@lists.uoregon.edu>; Tue, 24 Jun 2003 09:05:22 -0700 (PDT)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.9/8.12.9) id h5OG50YX022592;
	Tue, 24 Jun 2003 09:05:00 -0700
Date: Tue, 24 Jun 2003 09:05:00 -0700
From: David Meyer <dmm@1-4-5.net>
To: grow@lists.uoregon.edu
Cc: agenda@ietf.org, dmm@1-4-5.net, vijay@umbc.edu
Subject: grow: [GROW] Draft Agenda for 57 IETF
Message-ID: <20030624090500.A22574@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
X-public-key: http://www.maoz.com/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

	Please forward questions, comments, or additional agenda
	items to me. 

	Thanks,

	Dave

----

        Global Routing Operations WG (GROW)
        ===================================

        [Time: TBD]

        Draft Agenda
        ------------

        Agenda Bashing                                              5 minutes
        Meyer/All

        Generalizing the BGP TTL Hack                              10 minutes
        draft-gill-btsh-02.txt
        Meyer/all
        
        Controlling the redistribution of BGP routes               10 minutes
        draft-ietf-grow-bgp-redistribution-00.txt
        Olivier Bonaventure, et. al.

        Bidirectional Forwarding Detector: BFD
        draft-katz-ward-bfd-00.txt  
        Dave {Ward,Katz}                                           30 minutes

        Dissemination of flow specification rules
        draft-marques-idr-flow-spec-00.txt
        Pedro Roque Marques                                        15 minutes

        Other Drafts                                               10 minutes

          Configuring BGP to Block Denial-of-Service Attacks
          draft-turk-bgp-dos-04.txt
          D. Turk

          Bounding Longest Match Considered
          draft-grow-bounded-longest-match-04.txt
          Hardie/White

        Work Items                                                 10 minutes
        Meyer
____________________________________________________________
Web Archive:     http://darkwing.uoregon.edu/~llynch/grow/
