[59008] in North American Network Operators' Group
RE: Minimum prefix length?
daemon@ATHENA.MIT.EDU (Ejay Hire)
Wed Jun 11 16:02:41 2003
Date: Wed, 11 Jun 2003 14:58:16 -0500
From: "Ejay Hire" <ejay.hire@isdn.net>
To: "Temkin, David" <temkin@sig.com>, <nanog@merit.edu>
Errors-To: owner-nanog-outgoing@merit.edu
This is a multi-part message in MIME format.
------_=_NextPart_001_01C33053.CC4FBEE1
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
This doesn't seem to be much of a problem with prefixes less than or =
equal to /24. Domestically, Verio is the big exception. They seem to =
filter anything longer than a /20.
=20
-Ejay
=20
-----Original Message-----
From: Temkin, David [mailto:temkin@sig.com]
Sent: Wednesday, June 11, 2003 2:04 PM
To: nanog@merit.edu
Subject: Minimum prefix length?
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_01C33053.CC4FBEE1
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>Minimum prefix length?</TITLE>
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY>
<BLOCKQUOTE><FONT face=3DTahoma>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
size=3D2><SPAN=20
class=3D905535619-11062003>This doesn't seem to be much of a problem =
with=20
prefixes less than or equal to /24. Domestically, Verio is =
the big=20
exception. They seem to filter anything longer than a=20
/20.</SPAN></FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
size=3D2><SPAN=20
class=3D905535619-11062003></SPAN></FONT> </DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
size=3D2><SPAN=20
class=3D905535619-11062003>-Ejay</SPAN></FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
size=3D2><SPAN=20
class=3D905535619-11062003></SPAN></FONT> </DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
size=3D2><SPAN=20
class=3D905535619-11062003> </SPAN>-----Original=20
Message-----<BR><B>From:</B> Temkin, David=20
[mailto:temkin@sig.com]<BR><B>Sent:</B> Wednesday, June 11, 2003 2:04=20
PM<BR><B>To:</B> nanog@merit.edu<BR><B>Subject:</B> Minimum prefix=20
length?<BR><BR></DIV></FONT></FONT>
<P><FONT face=3DArial size=3D2>A few years ago I had an issue with a =
few of the=20
larger carriers rejecting my routes (from a natural Class B space) =
because=20
their prefix length was too short (at one point I simply had the /16 =
divided=20
into two /17's and this still got rejected in some places). I =
can't=20
remember which carriers exactly, but it may have been some larger =
transit=20
providers like AboveNet/etc.</FONT></P>
<P><FONT face=3DArial size=3D2>Anyone know what the current attitude =
is by=20
carriers about this? Nowadays with ever-growing memory and CPU =
it=20
doesn't seem like it's as much of an issue. In an environment =
where=20
we're all trying to conserve address space watching natural boundries =
doesn't=20
seem all that smart.</FONT></P><BR><BR><BR>
<P><FONT face=3DArial size=3D2>IMPORTANT:The information contained in =
this email=20
and/or its attachments is confidential. If you are not the intended =
recipient,=20
please notify the sender immediately by reply and immediately delete =
this=20
message and all its attachments. Any review, use, reproduction,=20
disclosure or dissemination of this message or any attachment by an =
unintended=20
recipient is strictly prohibited. Neither this message nor any=20
attachment is intended as or should be construed as an offer, =
solicitation or=20
recommendation to buy or sell any security or other financial=20
instrument. Neither the sender, his or her employer nor any of =
their=20
respective affiliates makes any warranties as to the completeness or =
accuracy=20
of any of the information contained herein or that this message or any =
of its=20
attachments is free of =
viruses.</FONT></P><BR></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C33053.CC4FBEE1--
