[59006] in North American Network Operators' Group
Minimum prefix length?
daemon@ATHENA.MIT.EDU (Temkin, David)
Wed Jun 11 15:04:24 2003
From: "Temkin, David" <temkin@sig.com>
To: nanog@merit.edu
Date: Wed, 11 Jun 2003 15:03:43 -0400
Errors-To: owner-nanog-outgoing@merit.edu
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C3304C.2D635C40
Content-Type: text/plain
A few years ago I had an issue with a few of the larger carriers rejecting
my routes (from a natural Class B space) because their prefix length was too
short (at one point I simply had the /16 divided into two /17's and this
still got rejected in some places). I can't remember which carriers
exactly, but it may have been some larger transit providers like
AboveNet/etc.
Anyone know what the current attitude is by carriers about this? Nowadays
with ever-growing memory and CPU it doesn't seem like it's as much of an
issue. In an environment where we're all trying to conserve address space
watching natural boundries doesn't seem all that smart.
IMPORTANT:The information contained in this email and/or its attachments is
confidential. If you are not the intended recipient, please notify the
sender immediately by reply and immediately delete this message and all its
attachments. Any review, use, reproduction, disclosure or dissemination of
this message or any attachment by an unintended recipient is strictly
prohibited. Neither this message nor any attachment is intended as or
should be construed as an offer, solicitation or recommendation to buy or
sell any security or other financial instrument. Neither the sender, his or
her employer nor any of their respective affiliates makes any warranties as
to the completeness or accuracy of any of the information contained herein
or that this message or any of its attachments is free of viruses.
------_=_NextPart_001_01C3304C.2D635C40
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Minimum prefix length?</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2 FACE=3D"Arial">A few years ago I had an issue with a =
few of the larger carriers rejecting my routes (from a natural Class B =
space) because their prefix length was too short (at one point I simply =
had the /16 divided into two /17's and this still got rejected in some =
places). I can't remember which carriers exactly, but it may have =
been some larger transit providers like AboveNet/etc.</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Anyone know what the current attitude =
is by carriers about this? Nowadays with ever-growing memory and =
CPU it doesn't seem like it's as much of an issue. In an =
environment where we're all trying to conserve address space watching =
natural boundries doesn't seem all that smart.</FONT></P>
<BR>
<BR>
<BR>
<P><FONT SIZE=3D2 FACE=3D"Arial">IMPORTANT:The information contained in =
this email and/or its attachments is confidential. If you are not the =
intended recipient, please notify the sender immediately by reply and =
immediately delete this message and all its attachments. Any =
review, use, reproduction, disclosure or dissemination of this message =
or any attachment by an unintended recipient is strictly =
prohibited. Neither this message nor any attachment is intended =
as or should be construed as an offer, solicitation or recommendation =
to buy or sell any security or other financial instrument. =
Neither the sender, his or her employer nor any of their respective =
affiliates makes any warranties as to the completeness or accuracy of =
any of the information contained herein or that this message or any of =
its attachments is free of viruses.</FONT></P>
<BR>
</BODY>
</HTML>
------_=_NextPart_001_01C3304C.2D635C40--
