Re: Attribute Length Error today
Didn't Akamai stop using the route servers? Therefore it wouldn't really matter. Jeremy LumbyMinnesota VoIP9217 17th Ave SSuite 216Bloomington MN 55425Main 612-355-7740Direct 612-392-6814EFax 952-873-7425jlumby@mnvoip.com <div> </div><div> </div><!-- originalMessage --><div>-------- Original message --------</div><div>From: Richard Laager <rlaager@WIKTEL.COM> </div><div>Date: 12/14/17 2:18 PM (GMT-06:00) </div><div>To: MICE-DISCUSS@LISTS.IPHOUSE.NET </div><div>Subject: Re: [MICE-DISCUSS] Attribute Length Error today </div><div> </div>-------- Original message --------From: Richard Laager <rlaager@WIKTEL.COM> Date: 12/14/17 2:18 PM (GMT-06:00) To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Attribute Length Error today At the last UG, we discussed IRR-based filtering. Does Akamai publish IRR records? -- Richard
On 12/14/2017 02:22 PM, Jeremy Lumby wrote:
Didn't Akamai stop using the route servers? Therefore it wouldn't really matter.
I'm not sure if they use the route servers. I'm still interested in their opinion, as well as anyone else's, on IRR. -- Richard
On Dec 14, 2017, at 4:22 PM, Richard Laager <rlaager@WIKTEL.COM> wrote:
I'm still interested in their opinion, as well as anyone else's, on IRR.
I’d fully support IRR based filtering on the route servers. Maintaining an AS-SET and associated route objects is pretty trivial. We’re already doing this today on a number of IX’s (Equinix, SIX, NWAX, etc) -- Andrew Hoyos hoyosa@gmail.com
participants (3)
-
Andrew Hoyos -
Jeremy Lumby -
Richard Laager