[137958] in North American Network Operators' Group
Re: Infrastructure addresses definition
daemon@ATHENA.MIT.EDU (Justin Wilson)
Thu Feb 24 11:58:01 2011
Date: Thu, 24 Feb 2011 11:57:54 -0500
From: Justin Wilson <lists@mtin.net>
To: <nanog@nanog.org>
In-Reply-To: <4D668399.70402@forthnet.gr>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I consider anything not facing the customer to be infrastructure. In
terms of CPE, routers, etc. If it's a point to point connection
(t1,wireless,etc) the address on the router on my end facing the customer
router is considered a customer address.
Justin
--=20
Justin Wilson <j2sw@mtin.net>
Aol & Yahoo IM: j2sw
http://www.mtin.net/blog =AD xISP News
http://www.twitter.com/j2sw =AD Follow me on Twitter
Wisp Consulting =AD Tower Climbing =AD Network Support
On 2/24/11 11:13 AM, "Tassos Chatzithomaoglou" <achatz@forthnet.gr> wrote:
>How do you define infrastructure addresses in your network?
>Ok, probably router loopbacks are some of them. Router LANs also.
>
>But what about addresses used on WAN (or LAN p2p) links that are used
>for interconnections with customers?
>What about addresses used for public servers (dns, mail, web, etc)?
>
>Do you consider these as infrastructure addresses?
>If yes, how do you define your iACLs with these included?
>
>Regards,
>Tassos
>
>
