[53487] in North American Network Operators' Group
Re: IP backbone numbering/naming
daemon@ATHENA.MIT.EDU (Owen DeLong)
Fri Nov 15 18:57:39 2002
Date: Fri, 15 Nov 2002 15:57:08 -0800
From: Owen DeLong <owen@delong.com>
To: Steve Rude <steve@rudedogg.com>, nanog@merit.edu
In-Reply-To: <Pine.LNX.4.33.0211151525350.26770-100000@lamb.coreis.net>
Errors-To: owner-nanog-outgoing@merit.edu
Generally it is not prohibited by the RFC, but it is bad form if you send
out ICMP that originates from 10space to places outside your network.
As such, it's generally bad form to use these numbers on intefaces in the
backbone, since those interfaces are likely to show up in ICMP time exceeded
messages unless you completely block traceroute through your backbone, which
is generally regarded as far worse form.
Owen
--On Friday, November 15, 2002 15:33 -0800 Steve Rude <steve@rudedogg.com>
wrote:
>
> Hi All,
>
> I am trying to collect information about using RFC 1918 space on an ISP
> backbone. I have read the RFC several times, and I don't see where it
> says that you cannot use 10/8 space to number your backbone links (/30s).
>
>
> I know this is an old thread that has been rehashed several times, but
> can anyone please send me links or information that I can use to
> convince my boss that we should use our arin alloc'd space on our
> backbone instead of using private space.
>
> Also if anyone has opinions on naming conventions for backbone such as
> why to or why not to even have dns resolution for your backbone and some
> conventions please let me know.
>
> TIA!
>
> --
> Steve Rude
> steve@rudedogg.com
>
