Re: IP backbone numbering/naming

[haesu () towardex com]

Hey,

Usually numbering backbone routers with a 10/8 is not a necessary practice. 
Any backbone routers communicating with the outside world are marked category 
three and should have globally unique IP numbers. Plus, if you are an ISP (in 
which it looks like you are..), it will help others on public internet to try 
to track down abuse a little deeper through traceroutes, which will may be 
help them identify the upstream provider of the offender.

You could also use RFC1918 numbers for your point-to-point /30 aggregation 
blocks with the customers.. But.. since that would have effect on customer's 
premise equipment, it would be better to give them globally unique space as 
well, who knows if your customer comes back and yells at you for not being 
able to get to his router's serial interface IP.


Quoting Steve Rude <steve () rudedogg com>:

> 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




----------------------------------------------------------------
This mail sent through TowardEX Webmail http://mail.towardex.com