From mknopper at cisco.com  Sat Feb  9 19:47:41 2002
From: mknopper at cisco.com (Mark Knopper)
Date: Sat, 09 Feb 2002 14:47:41 -0500
Subject: ptomaine reboot - call for agenda items
Message-ID: <B88AE70D.75B%mknopper@cisco.com>

Please send suggestions on agenda items for the ptomaine WG. The group has
not had much of a life yet--a BOF and one meeting. There is a charter and a
couple of drafts have been proposed.

The charter (http://www.ietf.org/html.charters/ptomaine-charter.html) deals
with routing table size growth and scalability. It may be reasonable to
focus on routing convergence in general as well. Are there any comments on
the charter?

So far I have received the following as possibilities. Please comment on
what you would like to see this group do.


- I-BGP replacement (or improvements? experimental results to determine what
is broken?)

- IGP link convergence improvement - how to improve multipoint link failure
detection time?

- stop using MinRoute Advertisement Interval

- new inter-domain TE mechanisms which don't rely on CIDR abuse

- mechanisms which mitigate the damage caused by CIDR abuse (e.g.
   geoff's nopeer draft, Abley's eppc draft, see below).



- 3 drafts proposed on mailing list:

http://www.ietf.org/internet-drafts/draft-hardie-bounded-longest-match-02.tx
t

draft-huston-nopeer-00.txt

http://buffoon.automagic.org/dist/draft-jabley-edge-policy-propagation-contr
ol-02.txt [soon to be draft-jabley-eppc-00.txt]


Thanks,
    Mark



From mknopper at cisco.com  Wed Feb 13 15:41:41 2002
From: mknopper at cisco.com (Mark Knopper)
Date: Wed, 13 Feb 2002 10:41:41 -0500
Subject: FW: ptomaine reboot - call for agenda items
In-Reply-To: <Pine.GSO.4.21.0202130601400.9856-100000@ruwhite-u10.cisco.com>
Message-ID: <B88FF365.C97%mknopper@cisco.com>

Here is another proposed agenda item. Keep those cards and letters coming
in.
    Mark



------ Forwarded Message
> From: Russ White <ruwhite at cisco.com>
> Reply-To: Russ White <riw at cisco.com>
> Date: Wed, 13 Feb 2002 06:01:56 -0500 (EST)
> To: Mark Knopper <mknopper at cisco.com>
> Subject: Re: ptomaine reboot - call for agenda items (fwd)
> 
> 
> This is the other draft I was talking about....
> 
> :-)
> 
> Russ
> 
>

http://www.info.fundp.ac.be/~obo/private/draf-bonaventure-bgp-redistribution
-02.txt



From Olivier.Bonaventure at info.fundp.ac.be  Wed Feb 13 17:32:08 2002
From: Olivier.Bonaventure at info.fundp.ac.be (Olivier Bonaventure)
Date: Wed, 13 Feb 2002 18:32:08 +0100
Subject: FW: ptomaine reboot - call for agenda items
References: <B88FF365.C97%mknopper@cisco.com>
Message-ID: <3C6AA318.56227669@info.fundp.ac.be>

Mark and All,

> Here is another proposed agenda item. Keep those cards and letters coming
> in.

> 
> http://www.info.fundp.ac.be/~obo/private/draf-bonaventure-bgp-redistribution-02.txt


Please not that the draft is being updated and is still in a very rough format.
An updated version will appear within one or two weeks. Comments are welcome as usual.


Best regards,


Olivier Bonaventure
-- 
http://www.infonet.fundp.ac.be


From Olivier.Bonaventure at info.fundp.ac.be  Fri Feb 22 20:49:55 2002
From: Olivier.Bonaventure at info.fundp.ac.be (Olivier Bonaventure)
Date: Fri, 22 Feb 2002 21:49:55 +0100
Subject: [Fwd: Submission of draft-quoitin-bgp-comm-survey-00.txt]
Message-ID: <3C76AEF3.58C20C06@info.fundp.ac.be>

FYI

This draft will appear within the next few days on the IETF mirror
sites. 

-------- Original Message --------
Subject: Submission of draft-quoitin-bgp-comm-survey-00.txt
Date: Wed, 20 Feb 2002 15:46:50 +0100
From: Olivier Bonaventure <Olivier.Bonaventure at info.fundp.ac.be>
Reply-To: Olivier.Bonaventure at info.fundp.ac.be
To: internet-drafts at ietf.org
CC: bqu at info.fundp.ac.be

Hello,

Please find below all the required information for a new Internet draft.
This draft is an individual submission, but is targeted at the ptomaine 
and idr working groups.

        Title           : A survey of the utilization of the BGP community  attribute
        Author(s)       : B. Quoitin, O. Bonaventure
        Filename        : draft-quoitin-bgp-comm-survey-00.txt
        Pages           : 16
        Date            : 20-Feb-02
        
   In this document, we describe the two most common utilizations of the
   BGP community attribute, namely to tag routes and indicate how a
   route should be redistributed by external peers. We then discuss how
   often these two types of community attribute are used on the basis of
   the RIPE whois database and of BGP table dumps.

This internet draft is available in text format (without figures) from
http://www.infonet.fundp.ac.be/doc/reports/draft-quoitin-bgp-comm-survey-00.txt

and in postscript format (with figures) from the following URL
http://www.infonet.fundp.ac.be/doc/reports/draft-quoitin-bgp-comm-survey-00.ps

Please let us know if you have any problems with the draft.

Best regards,


Olivier Bonaventure and Bruno Quoitin

-- 
http://www.infonet.fundp.ac.be


From Olivier.Bonaventure at info.fundp.ac.be  Tue Feb 26 20:13:20 2002
From: Olivier.Bonaventure at info.fundp.ac.be (Olivier Bonaventure)
Date: Tue, 26 Feb 2002 21:13:20 +0100
Subject: Submission of new draft 
References: <B88FF365.C97%mknopper@cisco.com>
Message-ID: <3C7BEC60.451CBFD4@info.fundp.ac.be>

Dear All,

An updated version of the draft announced by two weeks ago has
been submitted to IETF. It will appear in some days
on the usual sites.


         Title           : Controlling the redistribution of BGP routes
         Author(s)       : O. Bonaventure et al.
         Filename        : draft-bonaventure-bgp-redistribution-02.txt
         Pages           : 13
         Date            : 27-Feb-02

Summary

   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 to the specified set of eBGP speakers. The second
   type may be used to indicate that the attached route should only be
   announced with the NO_EXPORT community to the specified set of eBGP
   speakers and the third type may be used to indicate that the attached
   route should be prepended n times when announced to the specified set
   of eBGP speakers.


In the mean time, you can obtain it from the following URL :

http://www.infonet.fundp.ac.be/doc/reports/draft-bonaventure-bgp-redistribution-02.txt


Best regards,


Olivier Bonaventure

-- 
http://www.infonet.fundp.ac.be