NAIPR Message

US CODE: Title 15, Chapter 1, Section 2.

Giving an end-system an arbitrary length prefix just to ensure
'routability' is a recipe for disaster, if that's what you're
recommending. I suggest that ARIN play no role in this regard;
there is simply no way that they can effectively ensure routability,
and something that might be routable today, may not be routable
tomorrow (and vice versa). This is not practical.

- paul

At 02:18 AM 2/1/97 -0800, Karl Auerbach wrote:

>My use of the term "routability" was ment in the prospective sense -- that
>once a block was actually given topological significance -- i.e. that it's
>exchange points with the rest of the world were determined -- then there
>would be no artificial limits on the acceptance of that new block.  (By
>artificial I mean things like "ISP X won't accept your advertisements
>because your block is too small.")