From sfulton at torix.ca  Tue Feb  6 16:41:31 2018
From: sfulton at torix.ca (Stephen Fulton)
Date: Tue, 6 Feb 2018 11:41:31 -0500
Subject: [as112-ops] New AS112 node (sort of)
Message-ID: <2e254e22-0f27-dad9-e0ab-70cdd5193f6e@torix.ca>

Hi all,

The Toronto Internet Exchange has re-implemented its' AS112 under new IP
addressing, mainly to address problems with running a node on an IX LAN
prefix which is not announced globally.? Details are below:

Toronto Internet Exchange
Toronto, CA
206.108.0.42
2001:504:1A:1:ABBA:15:DEAD:42
Transit AS: 393424

Stats will be set up in the coming week or so.

-- 
Stephen Fulton
Toronto Internet Exchange, Operations Group
http://torix.ca


From jabley at hopcount.ca  Tue Feb  6 17:39:07 2018
From: jabley at hopcount.ca (Joe Abley)
Date: Tue, 6 Feb 2018 12:39:07 -0500
Subject: [as112-ops] New AS112 node (sort of)
In-Reply-To: <2e254e22-0f27-dad9-e0ab-70cdd5193f6e@torix.ca>
References: <2e254e22-0f27-dad9-e0ab-70cdd5193f6e@torix.ca>
Message-ID: <A5143166-A913-4ACC-BE28-9A83A44ABD77@hopcount.ca>

Hi Stephen,

On 6 Feb 2018, at 11:41, Stephen Fulton <sfulton at torix.ca> wrote:

> The Toronto Internet Exchange has re-implemented its' AS112 under new IP
> addressing, mainly to address problems with running a node on an IX LAN
> prefix which is not announced globally.  Details are below:
> 
> Toronto Internet Exchange
> Toronto, CA
> 206.108.0.42
> 2001:504:1A:1:ABBA:15:DEAD:42
> Transit AS: 393424

I don't see any of the 112 nameservers in Toronto right now, for what that's worth, from EGATE or TekSavvy. Quite possibly they both just have weird exit policies or some over-enthusiastic filters, but I thought I'd mention it in case it's useful.

More info on AS112 as viewed from 5645 (actually, from the mac mini in my basement at home) below.

I get all the right answers from 206.108.0.42 and 2001:504:1A:1:ABBA:15:DEAD:42, which is funny but disco's coming back man, you mark my words.


Joe


[marlinspike:~]% cat as112.sh 
#!/bin/sh

for ns in prisoner.iana.org blackhole.as112.arpa
do
  for af in 4 6
  do
    echo "======= ${ns} over IPv${af}"
    for query in "hostname.as112.net txt" "hostname.as112.arpa txt" \
      "hostname.bind ch txt" "id.server ch txt"
    do
      echo "--- ${query}"
      dig -${af} @${ns} ${query} +short
    done
    echo ""
    echo "--- traceroute ${ns} over IPv${af} from AS5645"
    mtr --report --report-cycles 1 -${af} ${ns}
    echo ""
  done
done

[marlinspike:~]% ./as112.sh 
======= prisoner.iana.org over IPv4
--- hostname.as112.net txt
"Unicast IP: 192.0.2.4"
"Widgets, Pty Ltd KK GmbH LLC Inc"
"See http://as112.net/ for more information."
"Anytown, Anycountry"
"See http://widgetsptyltdkkgmbhllcinc.com/ for information on Widgets"
--- hostname.as112.arpa txt
--- hostname.bind ch txt
"rdns01.bsn05"
--- id.server ch txt

--- traceroute prisoner.iana.org over IPv4 from AS5645
Start: 2018-02-06T12:28:51-0500
HOST: marlinspike.hopcount.ca     Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 3.vlan.r1.calod1.shl.io    0.0%     1    0.5   0.5   0.5   0.5   0.0
  2.|-- 67.231.220.26              0.0%     1   13.4  13.4  13.4  13.4   0.0
  3.|-- 104-195-128-74.cpe.teksav  0.0%     1   12.1  12.1  12.1  12.1   0.0
  4.|-- 104-195-128-217.cpe.teksa  0.0%     1   14.3  14.3  14.3  14.3   0.0
  5.|-- ae1-0-bdr01-tor.teksavvy.  0.0%     1   13.8  13.8  13.8  13.8   0.0
  6.|-- xe-2-0-2-2230-bdr01-mtl.t  0.0%     1   21.3  21.3  21.3  21.3   0.0
  7.|-- ae2-10-bdr01-nyc.teksavvy  0.0%     1   27.7  27.7  27.7  27.7   0.0
  8.|-- decix-ny-px.jfk01.twdx.ne  0.0%     1   28.2  28.2  28.2  28.2   0.0
  9.|-- bbr03-et-0-0-0.bos01.twdx  0.0%     1  131.4 131.4 131.4 131.4   0.0
 10.|-- dcr03-xe-0-0-1.bsn01.twdx  0.0%     1   61.5  61.5  61.5  61.5   0.0
 11.|-- csw01-irb-194.bsn05.twdx.  0.0%     1   35.5  35.5  35.5  35.5   0.0
 12.|-- prisoner.iana.org          0.0%     1   33.4  33.4  33.4  33.4   0.0

======= prisoner.iana.org over IPv6
--- hostname.as112.net txt
"Hivane Networks"
"Paris, FR"
"Unicast IP: 193.17.192.194"
"See http://as112.net/ for more information."
"See http://noc.hivane.net/cgi-bin/dsc-grapher.pl for local information."
"See http://icanhascheezburger.com for EVEN more information."
--- hostname.as112.arpa txt
"Hivane Networks"
"Paris, FR"
"Unicast IP: 193.17.192.194"
"See http://as112.net/ for more information."
"See http://noc.hivane.net/cgi-bin/dsc-grapher.pl for local information."
"See http://icanhascheezburger.com for EVEN more information."
--- hostname.bind ch txt
"hostname.as112.net - Paris Hivane node"
--- id.server ch txt
"hostname.as112.net - Paris Hivane node"

--- traceroute prisoner.iana.org over IPv6 from AS5645
Start: 2018-02-06T12:28:58-0500
HOST: marlinspike.hopcount.ca     Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
  2.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
  3.|-- ae0-3021-agg01-tor2.teksa  0.0%     1   19.8  19.8  19.8  19.8   0.0
  4.|-- ae1-0-bdr01-tor.teksavvy.  0.0%     1   18.3  18.3  18.3  18.3   0.0
  5.|-- 10gigabitethernet9-9.core  0.0%     1   18.9  18.9  18.9  18.9   0.0
  6.|-- 100ge14-2.core1.nyc4.he.n  0.0%     1   27.6  27.6  27.6  27.6   0.0
  7.|-- 100ge4-1.core1.par2.he.ne  0.0%     1   99.7  99.7  99.7  99.7   0.0
  8.|-- prisoner.iana.org          0.0%     1   99.8  99.8  99.8  99.8   0.0

======= blackhole.as112.arpa over IPv4
--- hostname.as112.net txt
"AS112 node of IN-Berlin e.V."
"See http://as112.in-berlin.de/ for local information."
"Unicast IP: 217.197.83.145, 2001:67c:1400:2060::112"
"See http://as112.net/ for more information."
--- hostname.as112.arpa txt
"AS112 node of IN-Berlin e.V."
"See http://as112.net/ for more information."
"See http://as112.in-berlin.de/ for local information."
"Unicast IP: 217.197.83.145, 2001:67c:1400:2060::112"
--- hostname.bind ch txt
"as112"
--- id.server ch txt

--- traceroute blackhole.as112.arpa over IPv4 from AS5645
Start: 2018-02-06T12:29:04-0500
HOST: marlinspike.hopcount.ca     Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
  2.|-- 67.231.220.26              0.0%     1   14.2  14.2  14.2  14.2   0.0
  3.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
  4.|-- 104-195-128-73.cpe.teksav  0.0%     1   13.6  13.6  13.6  13.6   0.0
  5.|-- ae4-0-bdr01-tor.teksavvy.  0.0%     1   15.8  15.8  15.8  15.8   0.0
  6.|-- xe-2-0-2-2230-bdr01-mtl.t  0.0%     1   22.8  22.8  22.8  22.8   0.0
  7.|-- ae2-10-bdr01-nyc.teksavvy  0.0%     1   26.9  26.9  26.9  26.9   0.0
  8.|-- de-cix.nyc.retn.net        0.0%     1   29.8  29.8  29.8  29.8   0.0
  9.|-- ae8-3.rt.sb.ber.de.retn.n  0.0%     1  115.1 115.1 115.1 115.1   0.0
 10.|-- 192.31.196.1               0.0%     1  118.7 118.7 118.7 118.7   0.0

======= blackhole.as112.arpa over IPv6
--- hostname.as112.net txt
"Hivane Networks"
"Paris, FR"
"Unicast IP: 193.17.192.194"
"See http://as112.net/ for more information."
"See http://noc.hivane.net/cgi-bin/dsc-grapher.pl for local information."
"See http://icanhascheezburger.com for EVEN more information."
--- hostname.as112.arpa txt
"Hivane Networks"
"Paris, FR"
"Unicast IP: 193.17.192.194"
"See http://as112.net/ for more information."
"See http://noc.hivane.net/cgi-bin/dsc-grapher.pl for local information."
"See http://icanhascheezburger.com for EVEN more information."
--- hostname.bind ch txt
"hostname.as112.net - Paris Hivane node"
--- id.server ch txt
"hostname.as112.net - Paris Hivane node"

--- traceroute blackhole.as112.arpa over IPv6 from AS5645
Start: 2018-02-06T12:29:11-0500
HOST: marlinspike.hopcount.ca     Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 2607:f2c0:101:3:4e96:14ff  0.0%     1    1.1   1.1   1.1   1.1   0.0
  2.|-- 2607:f2c0:101:300::1:1     0.0%     1   17.6  17.6  17.6  17.6   0.0
  3.|-- ae0-3021-agg01-tor2.teksa  0.0%     1   15.9  15.9  15.9  15.9   0.0
  4.|-- ae1-0-bdr01-tor.teksavvy.  0.0%     1   20.1  20.1  20.1  20.1   0.0
  5.|-- 10gigabitethernet9-9.core  0.0%     1   29.8  29.8  29.8  29.8   0.0
  6.|-- 100ge14-2.core1.nyc4.he.n  0.0%     1   29.2  29.2  29.2  29.2   0.0
  7.|-- 100ge4-1.core1.par2.he.ne  0.0%     1  482.1 482.1 482.1 482.1   0.0
  8.|-- 2001:4:112::1              0.0%     1  107.8 107.8 107.8 107.8   0.0

[marlinspike:~]% 



From nick at inex.ie  Tue Feb  6 17:44:23 2018
From: nick at inex.ie (Nick Hilliard)
Date: Tue, 06 Feb 2018 17:44:23 +0000
Subject: [as112-ops] New AS112 node (sort of)
In-Reply-To: <A5143166-A913-4ACC-BE28-9A83A44ABD77@hopcount.ca>
References: <2e254e22-0f27-dad9-e0ab-70cdd5193f6e@torix.ca>
 <A5143166-A913-4ACC-BE28-9A83A44ABD77@hopcount.ca>
Message-ID: <5A79E977.3070804@inex.ie>

Joe Abley wrote:
> I get all the right answers from 206.108.0.42 and
> 2001:504:1A:1:ABBA:15:DEAD:42, which is funny but disco's coming back
> man, you mark my words.

2001:504:1A:1:ABBA:15:DEAD:42 is alive.

Nick

From sfulton at torix.ca  Wed Feb  7 03:06:56 2018
From: sfulton at torix.ca (Stephen Fulton)
Date: Tue, 6 Feb 2018 22:06:56 -0500
Subject: [as112-ops] New AS112 node (sort of)
In-Reply-To: <A5143166-A913-4ACC-BE28-9A83A44ABD77@hopcount.ca>
References: <2e254e22-0f27-dad9-e0ab-70cdd5193f6e@torix.ca>
 <A5143166-A913-4ACC-BE28-9A83A44ABD77@hopcount.ca>
Message-ID: <334a5cd8-7b66-ab23-edf2-c2246579d319@torix.ca>

Hi Joe,

Currently the AS112 node is announced only to the TorIX route-servers,
which ~ 80% of TorIX's peers use.? TekSavvy does not, so in order to
reach the AS112 node, they would have to peer with the TorIX services
peer directly.? As for eGate, they do peer with the route-servers but
may very well be preferring another AS112 for whatever routing policy
reason, like due to having the same BGP local preference for prefixes
received by the route-servers as their transits.?

As for disco, Nistor has strong feelings about that. :)

-- 
Stephen Fulton
Toronto Internet Exchange, Operations Group
http://torix.ca

On 2018-02-06 12:39 PM, Joe Abley wrote:
> Hi Stephen,
>
> On 6 Feb 2018, at 11:41, Stephen Fulton <sfulton at torix.ca> wrote:
>
>> The Toronto Internet Exchange has re-implemented its' AS112 under new IP
>> addressing, mainly to address problems with running a node on an IX LAN
>> prefix which is not announced globally.  Details are below:
>>
>> Toronto Internet Exchange
>> Toronto, CA
>> 206.108.0.42
>> 2001:504:1A:1:ABBA:15:DEAD:42
>> Transit AS: 393424
> I don't see any of the 112 nameservers in Toronto right now, for what that's worth, from EGATE or TekSavvy. Quite possibly they both just have weird exit policies or some over-enthusiastic filters, but I thought I'd mention it in case it's useful.
>
> More info on AS112 as viewed from 5645 (actually, from the mac mini in my basement at home) below.
>
> I get all the right answers from 206.108.0.42 and 2001:504:1A:1:ABBA:15:DEAD:42, which is funny but disco's coming back man, you mark my words.
>
>
> Joe
>
>
> [marlinspike:~]% cat as112.sh 
> #!/bin/sh
>
> for ns in prisoner.iana.org blackhole.as112.arpa
> do
>   for af in 4 6
>   do
>     echo "======= ${ns} over IPv${af}"
>     for query in "hostname.as112.net txt" "hostname.as112.arpa txt" \
>       "hostname.bind ch txt" "id.server ch txt"
>     do
>       echo "--- ${query}"
>       dig -${af} @${ns} ${query} +short
>     done
>     echo ""
>     echo "--- traceroute ${ns} over IPv${af} from AS5645"
>     mtr --report --report-cycles 1 -${af} ${ns}
>     echo ""
>   done
> done
>
> [marlinspike:~]% ./as112.sh 
> ======= prisoner.iana.org over IPv4
> --- hostname.as112.net txt
> "Unicast IP: 192.0.2.4"
> "Widgets, Pty Ltd KK GmbH LLC Inc"
> "See http://as112.net/ for more information."
> "Anytown, Anycountry"
> "See http://widgetsptyltdkkgmbhllcinc.com/ for information on Widgets"
> --- hostname.as112.arpa txt
> --- hostname.bind ch txt
> "rdns01.bsn05"
> --- id.server ch txt
>
> --- traceroute prisoner.iana.org over IPv4 from AS5645
> Start: 2018-02-06T12:28:51-0500
> HOST: marlinspike.hopcount.ca     Loss%   Snt   Last   Avg  Best  Wrst StDev
>   1.|-- 3.vlan.r1.calod1.shl.io    0.0%     1    0.5   0.5   0.5   0.5   0.0
>   2.|-- 67.231.220.26              0.0%     1   13.4  13.4  13.4  13.4   0.0
>   3.|-- 104-195-128-74.cpe.teksav  0.0%     1   12.1  12.1  12.1  12.1   0.0
>   4.|-- 104-195-128-217.cpe.teksa  0.0%     1   14.3  14.3  14.3  14.3   0.0
>   5.|-- ae1-0-bdr01-tor.teksavvy.  0.0%     1   13.8  13.8  13.8  13.8   0.0
>   6.|-- xe-2-0-2-2230-bdr01-mtl.t  0.0%     1   21.3  21.3  21.3  21.3   0.0
>   7.|-- ae2-10-bdr01-nyc.teksavvy  0.0%     1   27.7  27.7  27.7  27.7   0.0
>   8.|-- decix-ny-px.jfk01.twdx.ne  0.0%     1   28.2  28.2  28.2  28.2   0.0
>   9.|-- bbr03-et-0-0-0.bos01.twdx  0.0%     1  131.4 131.4 131.4 131.4   0.0
>  10.|-- dcr03-xe-0-0-1.bsn01.twdx  0.0%     1   61.5  61.5  61.5  61.5   0.0
>  11.|-- csw01-irb-194.bsn05.twdx.  0.0%     1   35.5  35.5  35.5  35.5   0.0
>  12.|-- prisoner.iana.org          0.0%     1   33.4  33.4  33.4  33.4   0.0
>
> ======= prisoner.iana.org over IPv6
> --- hostname.as112.net txt
> "Hivane Networks"
> "Paris, FR"
> "Unicast IP: 193.17.192.194"
> "See http://as112.net/ for more information."
> "See http://noc.hivane.net/cgi-bin/dsc-grapher.pl for local information."
> "See http://icanhascheezburger.com for EVEN more information."
> --- hostname.as112.arpa txt
> "Hivane Networks"
> "Paris, FR"
> "Unicast IP: 193.17.192.194"
> "See http://as112.net/ for more information."
> "See http://noc.hivane.net/cgi-bin/dsc-grapher.pl for local information."
> "See http://icanhascheezburger.com for EVEN more information."
> --- hostname.bind ch txt
> "hostname.as112.net - Paris Hivane node"
> --- id.server ch txt
> "hostname.as112.net - Paris Hivane node"
>
> --- traceroute prisoner.iana.org over IPv6 from AS5645
> Start: 2018-02-06T12:28:58-0500
> HOST: marlinspike.hopcount.ca     Loss%   Snt   Last   Avg  Best  Wrst StDev
>   1.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
>   2.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
>   3.|-- ae0-3021-agg01-tor2.teksa  0.0%     1   19.8  19.8  19.8  19.8   0.0
>   4.|-- ae1-0-bdr01-tor.teksavvy.  0.0%     1   18.3  18.3  18.3  18.3   0.0
>   5.|-- 10gigabitethernet9-9.core  0.0%     1   18.9  18.9  18.9  18.9   0.0
>   6.|-- 100ge14-2.core1.nyc4.he.n  0.0%     1   27.6  27.6  27.6  27.6   0.0
>   7.|-- 100ge4-1.core1.par2.he.ne  0.0%     1   99.7  99.7  99.7  99.7   0.0
>   8.|-- prisoner.iana.org          0.0%     1   99.8  99.8  99.8  99.8   0.0
>
> ======= blackhole.as112.arpa over IPv4
> --- hostname.as112.net txt
> "AS112 node of IN-Berlin e.V."
> "See http://as112.in-berlin.de/ for local information."
> "Unicast IP: 217.197.83.145, 2001:67c:1400:2060::112"
> "See http://as112.net/ for more information."
> --- hostname.as112.arpa txt
> "AS112 node of IN-Berlin e.V."
> "See http://as112.net/ for more information."
> "See http://as112.in-berlin.de/ for local information."
> "Unicast IP: 217.197.83.145, 2001:67c:1400:2060::112"
> --- hostname.bind ch txt
> "as112"
> --- id.server ch txt
>
> --- traceroute blackhole.as112.arpa over IPv4 from AS5645
> Start: 2018-02-06T12:29:04-0500
> HOST: marlinspike.hopcount.ca     Loss%   Snt   Last   Avg  Best  Wrst StDev
>   1.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
>   2.|-- 67.231.220.26              0.0%     1   14.2  14.2  14.2  14.2   0.0
>   3.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
>   4.|-- 104-195-128-73.cpe.teksav  0.0%     1   13.6  13.6  13.6  13.6   0.0
>   5.|-- ae4-0-bdr01-tor.teksavvy.  0.0%     1   15.8  15.8  15.8  15.8   0.0
>   6.|-- xe-2-0-2-2230-bdr01-mtl.t  0.0%     1   22.8  22.8  22.8  22.8   0.0
>   7.|-- ae2-10-bdr01-nyc.teksavvy  0.0%     1   26.9  26.9  26.9  26.9   0.0
>   8.|-- de-cix.nyc.retn.net        0.0%     1   29.8  29.8  29.8  29.8   0.0
>   9.|-- ae8-3.rt.sb.ber.de.retn.n  0.0%     1  115.1 115.1 115.1 115.1   0.0
>  10.|-- 192.31.196.1               0.0%     1  118.7 118.7 118.7 118.7   0.0
>
> ======= blackhole.as112.arpa over IPv6
> --- hostname.as112.net txt
> "Hivane Networks"
> "Paris, FR"
> "Unicast IP: 193.17.192.194"
> "See http://as112.net/ for more information."
> "See http://noc.hivane.net/cgi-bin/dsc-grapher.pl for local information."
> "See http://icanhascheezburger.com for EVEN more information."
> --- hostname.as112.arpa txt
> "Hivane Networks"
> "Paris, FR"
> "Unicast IP: 193.17.192.194"
> "See http://as112.net/ for more information."
> "See http://noc.hivane.net/cgi-bin/dsc-grapher.pl for local information."
> "See http://icanhascheezburger.com for EVEN more information."
> --- hostname.bind ch txt
> "hostname.as112.net - Paris Hivane node"
> --- id.server ch txt
> "hostname.as112.net - Paris Hivane node"
>
> --- traceroute blackhole.as112.arpa over IPv6 from AS5645
> Start: 2018-02-06T12:29:11-0500
> HOST: marlinspike.hopcount.ca     Loss%   Snt   Last   Avg  Best  Wrst StDev
>   1.|-- 2607:f2c0:101:3:4e96:14ff  0.0%     1    1.1   1.1   1.1   1.1   0.0
>   2.|-- 2607:f2c0:101:300::1:1     0.0%     1   17.6  17.6  17.6  17.6   0.0
>   3.|-- ae0-3021-agg01-tor2.teksa  0.0%     1   15.9  15.9  15.9  15.9   0.0
>   4.|-- ae1-0-bdr01-tor.teksavvy.  0.0%     1   20.1  20.1  20.1  20.1   0.0
>   5.|-- 10gigabitethernet9-9.core  0.0%     1   29.8  29.8  29.8  29.8   0.0
>   6.|-- 100ge14-2.core1.nyc4.he.n  0.0%     1   29.2  29.2  29.2  29.2   0.0
>   7.|-- 100ge4-1.core1.par2.he.ne  0.0%     1  482.1 482.1 482.1 482.1   0.0
>   8.|-- 2001:4:112::1              0.0%     1  107.8 107.8 107.8 107.8   0.0
>
> [marlinspike:~]% 
>


From sfulton at torix.ca  Wed Feb  7 05:09:29 2018
From: sfulton at torix.ca (Stephen Fulton)
Date: Wed, 7 Feb 2018 00:09:29 -0500
Subject: [as112-ops] New AS112 node (sort of)
In-Reply-To: <334a5cd8-7b66-ab23-edf2-c2246579d319@torix.ca>
References: <2e254e22-0f27-dad9-e0ab-70cdd5193f6e@torix.ca>
 <A5143166-A913-4ACC-BE28-9A83A44ABD77@hopcount.ca>
 <334a5cd8-7b66-ab23-edf2-c2246579d319@torix.ca>
Message-ID: <6c5e3664-8ec6-bb3b-0e0f-7c3c989f13ab@torix.ca>

A follow-up question for folks:

When announcing AS112 to your transits, have their required LOA's?? Have
"their" transits?? What have you found is sufficient to all parties?

I ask because I have a dual role, one at TorIX and $dayjob at a TorIX
peer which donates transit to TorIX, and I'd like to announce the TorIX
AS112 node to my $dayjob transits as well.

Thanks,

-- 
Stephen Fulton
Toronto Internet Exchange, Operations Group
http://torix.ca

On 2018-02-06 10:06 PM, Stephen Fulton wrote:
> Hi Joe,
>
> Currently the AS112 node is announced only to the TorIX route-servers,
> which ~ 80% of TorIX's peers use.? TekSavvy does not, so in order to
> reach the AS112 node, they would have to peer with the TorIX services
> peer directly.? As for eGate, they do peer with the route-servers but
> may very well be preferring another AS112 for whatever routing policy
> reason, like due to having the same BGP local preference for prefixes
> received by the route-servers as their transits.?
>
> As for disco, Nistor has strong feelings about that. :)
>


From jabley at hopcount.ca  Wed Feb  7 05:19:38 2018
From: jabley at hopcount.ca (Joe Abley)
Date: Tue, 6 Feb 2018 21:19:38 -0800
Subject: [as112-ops] New AS112 node (sort of)
In-Reply-To: <6c5e3664-8ec6-bb3b-0e0f-7c3c989f13ab@torix.ca>
References: <2e254e22-0f27-dad9-e0ab-70cdd5193f6e@torix.ca>
 <A5143166-A913-4ACC-BE28-9A83A44ABD77@hopcount.ca>
 <334a5cd8-7b66-ab23-edf2-c2246579d319@torix.ca>
 <6c5e3664-8ec6-bb3b-0e0f-7c3c989f13ab@torix.ca>
Message-ID: <CAJhMdTPZLDrmAry1ts3zPTbty6tTr3u5h-bgKgV50cDWC1ZsLQ@mail.gmail.com>

I think the whois-accessible metadata for the nets concerned points to
DNS-OARC, and I'm guessing they could probably post a general-purpose
LOA on as112.net if someone asked them nicely.

I seem to recall, years ago, there was some talk of writing up a LOA
as an RFC so that people could just point transit providers at that.
Perhaps we should have done that in an appendix of RFC7534. Probably
your average transit provider is going to be happier with a
conventional-looking scan of a letter with a signature, though, I
guess.

Back when I did these kinds of things at ISC and Afilias I do remember
being asked for a LOA but when I said "no that's silly" they stopped
asking. That was eleventy years ago though so things might have
changed.

> On Feb 7, 2018, at 00:09, Stephen Fulton <sfulton at torix.ca> wrote:
>
> A follow-up question for folks:
>
> When announcing AS112 to your transits, have their required LOA's?  Have
> "their" transits?  What have you found is sufficient to all parties?
>
> I ask because I have a dual role, one at TorIX and $dayjob at a TorIX
> peer which donates transit to TorIX, and I'd like to announce the TorIX
> AS112 node to my $dayjob transits as well.
>
> Thanks,
>
> --
> Stephen Fulton
> Toronto Internet Exchange, Operations Group
> http://torix.ca
>
>> On 2018-02-06 10:06 PM, Stephen Fulton wrote:
>> Hi Joe,
>>
>> Currently the AS112 node is announced only to the TorIX route-servers,
>> which ~ 80% of TorIX's peers use.  TekSavvy does not, so in order to
>> reach the AS112 node, they would have to peer with the TorIX services
>> peer directly.  As for eGate, they do peer with the route-servers but
>> may very well be preferring another AS112 for whatever routing policy
>> reason, like due to having the same BGP local preference for prefixes
>> received by the route-servers as their transits.
>>
>> As for disco, Nistor has strong feelings about that. :)
>>
>
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops

From mike at mikej.net.nz  Wed Feb  7 20:12:36 2018
From: mike at mikej.net.nz (Mike Jager)
Date: Thu, 08 Feb 2018 09:12:36 +1300
Subject: [as112-ops] New AS112 node (sort of)
In-Reply-To: <6c5e3664-8ec6-bb3b-0e0f-7c3c989f13ab@torix.ca>
References: <2e254e22-0f27-dad9-e0ab-70cdd5193f6e@torix.ca>
 <A5143166-A913-4ACC-BE28-9A83A44ABD77@hopcount.ca>
 <334a5cd8-7b66-ab23-edf2-c2246579d319@torix.ca>
 <6c5e3664-8ec6-bb3b-0e0f-7c3c989f13ab@torix.ca>
Message-ID: <5621B9F9-6D10-444C-A46E-AF5400424D19@mikej.net.nz>

On 7 Feb 2018, at 18:09, Stephen Fulton wrote:

> When announcing AS112 to your transits, have their required LOA's?? 
> Have
> "their" transits?? What have you found is sufficient to all parties?

I only had one say "Hey there, that doesn't look like your address 
space." I said "Indeed it is not. See RFC7534/7535 and as112.net." That 
seemed to satisfy them, but formal LOAs aren't really a thing in these 
parts.

Cheers
-Mike

From sfulton at torix.ca  Wed Feb  7 20:14:57 2018
From: sfulton at torix.ca (Stephen Fulton)
Date: Wed, 7 Feb 2018 15:14:57 -0500
Subject: [as112-ops] New AS112 node (sort of)
In-Reply-To: <5621B9F9-6D10-444C-A46E-AF5400424D19@mikej.net.nz>
References: <2e254e22-0f27-dad9-e0ab-70cdd5193f6e@torix.ca>
 <A5143166-A913-4ACC-BE28-9A83A44ABD77@hopcount.ca>
 <334a5cd8-7b66-ab23-edf2-c2246579d319@torix.ca>
 <6c5e3664-8ec6-bb3b-0e0f-7c3c989f13ab@torix.ca>
 <5621B9F9-6D10-444C-A46E-AF5400424D19@mikej.net.nz>
Message-ID: <08a13104-57ff-a10d-7b6e-7fecc239235b@torix.ca>

Thanks.? I put together an LOA under my TorIX hat and referenced the
RFC's.? Once of our transit's upstreams has accepted it and the other's
having balked so far, so it doesn't seem to be a big deal.? If I run
into problems, I'll document those in this thread for posterity.

Cheers,

-- 
Stephen Fulton
Toronto Internet Exchange, Operations Group
http://torix.ca

On 2018-02-07 3:12 PM, Mike Jager wrote:
> On 7 Feb 2018, at 18:09, Stephen Fulton wrote:
>
>> When announcing AS112 to your transits, have their required LOA's?? Have
>> "their" transits?? What have you found is sufficient to all parties?
>
> I only had one say "Hey there, that doesn't look like your address
> space." I said "Indeed it is not. See RFC7534/7535 and as112.net."
> That seemed to satisfy them, but formal LOAs aren't really a thing in
> these parts.
>
> Cheers
> -Mike


