[1774] in North American Network Operators' Group
Re: Policy Statement on Address Space Allocations
daemon@ATHENA.MIT.EDU (Jon Zeeff)
Wed Jan 31 16:05:46 1996
From: jon@branch.com (Jon Zeeff)
To: jnc@ginger.lcs.mit.edu (Noel Chiappa)
Date: Wed, 31 Jan 1996 15:56:55 -0500 (EST)
Cc: G.Huston@aarnet.edu.au, asp@uunet.uu.net, cidrd@iepg.org, iesg@isi.edu,
jnc@ginger.lcs.mit.edu, local-ir@ripe.net, nanog@merit.edu
In-Reply-To: <9601312000.AA13981@ginger.lcs.mit.edu> from "Noel Chiappa" at Jan 31, 96 03:00:33 pm
All this discussion seems to be about work arounds for the real
problem. Namely, that the current hardware/software/protocols
can't handle what is actually a small number of routes.
Restricting announcements of new routes should be one of the last
things considered.
Here is one - for whatever reasons, we have a provider who can't seem
to correctly announce an aggregate and instead, announces several
specifics. Nobody says anything about this inefficiency - not to us or
to them. Some automated process watching for things like this and
sending an advisory email might help quite a bit.
--
(313) 741-4442 http://branch.com/
Jon Zeeff Branch Internet Services Inc. jon@branch.com
*** WWW Hosting Services, WWW Site Development and the Branch Malls ***
