WG last call

[Yakov Rekhter <[e-mail]>]

Folks,

This is to start the WG Last Call on draft-ietf-idr-route-damp-03.txt,.ps.
The end of the last call is on June 5. 

Yakov.
------- Forwarded Message

Return-Path: [e-mail]
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42]) by puli.cisco.com (8.6.12/8.6.5) with ESMTP id HAA05334; Mon, 18 May 1998 07:13:01 -0700
Received: from proxy3.cisco.com (proxy3.cisco.com [192.31.7.90]) by kickme.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.GATE.1.1) with ESMTP id HAA01783; Mon, 18 May 1998 07:12:59 -0700 (PDT)
Received: (from smap@localhost)
	by proxy3.cisco.com (8.8.7/8.8.5) id HAA08569;
	Mon, 18 May 1998 07:12:56 -0700 (PDT)
Received: from merit.edu(198.108.1.42) by proxy3.cisco.com via smap (V2.0)
	id xma008554; Mon, 18 May 98 14:12:53 GMT
X-SMAP-Received-From: outside
Received: (from majordom@localhost)
	by merit.edu (8.8.7/8.8.5) id KAA18870
	for idr-outgoing; Mon, 18 May 1998 10:04:17 -0400 (EDT)
Received: from ietf.org (ietf.org [132.151.1.19])
	by merit.edu (8.8.7/8.8.5) with ESMTP id KAA18866
	for <[e-mail]>; Mon, 18 May 1998 10:04:13 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA23151;
	Mon, 18 May 1998 10:03:36 -0400 (EDT)
Message-Id: <[e-mail]>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: [e-mail]
From: [e-mail]
Reply-to: [e-mail]
Subject: I-D ACTION:draft-ietf-idr-route-damp-03.txt,.ps
Date: Mon, 18 May 1998 10:03:36 -0400
Sender: [e-mail]
Precedence: bulk

- --NextPart

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

	Title		: BGP Route Flap Damping
	Author(s)	: C. Villamizar, R. Govindan, R. Chandra
	Filename	: draft-ietf-idr-route-damp-03.txt,.ps
	Pages		: 33
	Date		: 15-May-98
	
  A usage of the BGP routing protocol is described which is capable of
  reducing the routing traffic passed on to routing peers and therefore
  the load on these peers without adversely affecting route convergence
  time for relatively stable routes.  This technique has been
  implemented in commercial products supporting BGP. The technique is
  also applicable to IDRP.
 
  The overall goals are:
 
     o  to provide a mechanism capable of reducing router processing load
        caused by instability
 
     o  in doing so prevent sustained routing oscillations
 
     o  to do so without sacrificing route convergence time for generally
        well behaved routes.

  This must be accomplished keeping other goals of BGP in mind:
 
     o  pack changes into a small number of updates
 
     o  preserve consistent routing
 
     o  minimal addition space and computational overhead
  
  An excessive rate of update to the advertised reachability of a subset
  of Internet prefixes has been widespread in the Internet.  This
  observation was made in the early 1990s by many people involved in
  Internet operations and remains the case.  These excessive updates are
  not necessarily periodic so route oscillation would be a misleading
  term.  The informal term used to describe this effect is ``route
  flap''.  The techniques described here are now widely deployed and are
  commonly referred to as ``route flap damping''.

Internet-Drafts are 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-idr-route-damp-03.txt".
A URL for the Internet-Draft is:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-idr-route-damp-03.txt

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za
	
	Europe: ftp.nordu.net
		ftp.nis.garr.it
			
	Pacific Rim: munnari.oz.au
	
	US East Coast: ftp.ietf.org
	
	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	[e-mail].  In the body type:
	"FILE /internet-drafts/draft-ietf-idr-route-damp-03.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="[e-mail]"

Content-Type: text/plain
Content-ID:	<[e-mail]>

ENCODING mime
FILE /internet-drafts/draft-ietf-idr-route-damp-03.txt

- --OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idr-route-damp-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[e-mail]>

- --OtherAccess--

- --NextPart--



------- End of Forwarded Message