[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

best practice for advertising peering fabric routes

Subject: best practice for advertising peering fabric routes
From: niels=nanog at bakker.net (Niels Bakker)
Date: Wed, 15 Jan 2014 18:54:02 +0100
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>

* nanog at shankland.org (Jim Shankland) [Wed 15 Jan 2014, 18:04 CET]:
>So ... RFC1918 addresses for the IXP fabric, then?
>
>(Half kidding, but still ....)

They need to be globally unique.


	-- Niels.

-- 
"It's amazing what people will do to get their name on the internet, 
  which is odd, because all you really need is a Blogspot account."
			-- roy edroso, alicublog.blogspot.com

Follow-Ups:
- best practice for advertising peering fabric routes
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- best practice for advertising peering fabric routes
  - From: bill at herrin.us (William Herrin)

References:
- best practice for advertising peering fabric routes
  - From: elouie at yahoo.com (Eric A Louie)
- best practice for advertising peering fabric routes
  - From: bicknell at ufp.org (Leo Bicknell)
- best practice for advertising peering fabric routes
  - From: patrick at ianai.net (Patrick W. Gilmore)
- best practice for advertising peering fabric routes
  - From: bicknell at ufp.org (Leo Bicknell)
- best practice for advertising peering fabric routes
  - From: patrick at ianai.net (Patrick W. Gilmore)
- best practice for advertising peering fabric routes
  - From: nanog at shankland.org (Jim Shankland)

Prev by Date: Amazon AWS Engineer
Next by Date: best practice for advertising peering fabric routes
Previous by thread: best practice for advertising peering fabric routes
Next by thread: best practice for advertising peering fabric routes
Index(es):
- Date
- Thread