From smace at intt.net  Sat Nov 17 04:40:18 2007
From: smace at intt.net (Scott Mace)
Date: Fri, 16 Nov 2007 22:40:18 -0600
Subject: [as112-ops] AS112 node via AS5408
Message-ID: <473E70B2.2050606@intt.net>

Oddly enough at some point in the past (who knows how long) an AS112
node started being announced to research networks in the US.   AS11537,
for example:   302 4557 14085 11537 20965 5408 112

The only problem is that many of the end sites connected to 11537
prefer all paths via 11537 blindly over other paths.
So as a result this particular AS112 node might get more than it expected.
It is currently responding with timeouts.

	Scott

From wmaton at ryouko.imsb.nrc.ca  Sat Nov 17 21:11:44 2007
From: wmaton at ryouko.imsb.nrc.ca (William F. Maton Sotomayor)
Date: Sat, 17 Nov 2007 16:11:44 -0500 (EST)
Subject: [as112-ops] AS112 node via AS5408
In-Reply-To: <473E70B2.2050606@intt.net>
References: <473E70B2.2050606@intt.net>
Message-ID: <Pine.LNX.4.64.0711171605070.10059@ryouko.imsb.nrc.ca>

On Fri, 16 Nov 2007, Scott Mace wrote:

> Oddly enough at some point in the past (who knows how long) an AS112
> node started being announced to research networks in the US.   AS11537,
> for example:   302 4557 14085 11537 20965 5408 112
>
> The only problem is that many of the end sites connected to 11537
> prefer all paths via 11537 blindly over other paths.
> So as a result this particular AS112 node might get more than it expected.
> It is currently responding with timeouts.

Interesting, I wonder if we have a contact here for GRNet.  In any case, 
I'll see if I can contact them about.

FWIW, my AS112 node is back online, and may help with timeouts.  Testing 
appreciated.  I'm coming in from behind AS path 6509 2884 and you can give 
this a shot:

dig @prisoner.iana.org hostname.as112.net txt +short +norec

This might come back with:

"Federal GigaPOP" "Ottawa, Canada"
"See http://as112.net/ for more information."

Provided we're 'closer' to you than others.

wfms

P.S. I have asked AS6509 to peer direct with them instead of the route 
servers.

From smace at intt.net  Sun Nov 18 17:49:03 2007
From: smace at intt.net (Scott Mace)
Date: Sun, 18 Nov 2007 11:49:03 -0600
Subject: [as112-ops] AS112 node via AS5408
In-Reply-To: <Pine.LNX.4.64.0711171605070.10059@ryouko.imsb.nrc.ca>
References: <473E70B2.2050606@intt.net>
	<Pine.LNX.4.64.0711171605070.10059@ryouko.imsb.nrc.ca>
Message-ID: <47407B0F.4080409@intt.net>

I'm not seeing the prefix via your 6509 2884 path, still only the
geant2 path.  I tested that server coming from 5408 again last
night and it was still giving timeouts.

	Scott

William F. Maton Sotomayor wrote:
> On Fri, 16 Nov 2007, Scott Mace wrote:
> 
>> Oddly enough at some point in the past (who knows how long) an AS112
>> node started being announced to research networks in the US.   AS11537,
>> for example:   302 4557 14085 11537 20965 5408 112
>>
>> The only problem is that many of the end sites connected to 11537
>> prefer all paths via 11537 blindly over other paths.
>> So as a result this particular AS112 node might get more than it 
>> expected.
>> It is currently responding with timeouts.
> 
> Interesting, I wonder if we have a contact here for GRNet.  In any case, 
> I'll see if I can contact them about.
> 
> FWIW, my AS112 node is back online, and may help with timeouts.  Testing 
> appreciated.  I'm coming in from behind AS path 6509 2884 and you can 
> give this a shot:
> 
> dig @prisoner.iana.org hostname.as112.net txt +short +norec
> 
> This might come back with:
> 
> "Federal GigaPOP" "Ottawa, Canada"
> "See http://as112.net/ for more information."
> 
> Provided we're 'closer' to you than others.
> 
> wfms
> 
> P.S. I have asked AS6509 to peer direct with them instead of the route 
> servers.
> 
> 

