From wfms at dns-oarc.net  Thu Mar  9 01:19:04 2017
From: wfms at dns-oarc.net (William F Sotomayor)
Date: Thu, 9 Mar 2017 01:19:04 +0000 (UTC)
Subject: [as112-ops] DITL 2017 dates
Message-ID: <alpine.DEB.2.20.1703090019140.29700@ix1.dns-oarc.net>


All,

Last month we announced we will be holding another DITL collection. 
As in previous years we are looking to solicit captures primarily from the 
root operators, but this need not be restricted to just them:  Any TLD 
operator including AS112 operators are encouraged to participate.  Also, 
those who agreed to contribute DITL data as part of their DNS-OARC 
membership agreements are warmly expected.

For testing your DITL upload capabilities (and we thank you for your
contribution), the test dates are (in settings.sh format):

START_T='2017-03-21 11:00:00'
STOP_T='2017-03-23 13:00:00'

Please feel free to use that as a test window or to test any time prior to
that, but the more who can participate during that test date, the better
as we'll be able to stress-test the upload servers and the whole 
eco-system.

--> The actual event itself will be:  April 11 to 13 inclusive, 2017. <--

Your settings.sh file should look like this:

START_T='2017-04-11 11:00:00'
STOP_T='2017-04-13 13:00:00'

(All times UTC)

As usual, remember to:

- Refresh your memories about what DITL is about:

           https://www.dns-oarc.net/oarc/data/ditl

- Ensure your patched NTP/clock sync software is functioning on your
   participating servers;

- To have a look at the latest 'ditl-' capture software suite located
   here:

           https://dnscap.dns-oarc.net/

    For those who like to live on the edge, there is also a Github version
    of dnscap at:

         https://github.com/verisign/dnscap

- And familiarise yourselves with the upload process which hasn't changed
   over the course of the years:

           https://www.dns-oarc.net/ditl/2011/

For those who would like to test and eventually use the Canadian-based 
upload server, you'll need to adjust your pcap-submit-to-oarc.sh file like 
so:

 	REMOTE=oarc-${OARC_MEMBER}@capture-e.ditl.dns-oarc.net

Note that if you do chose to participate, it's a good idea to join the
DITL mailing list where questions and discussions for the event are best
held:

          https://lists.dns-oarc.net/mailman/listinfo/ditl

Those of you who would like to do test uploads one-on-one with DNS-OARC, 
please contact admin at dns-oarc.net.

(Those of you who are members may also access the 'ditl' conference room
on the DNS-OARC jabber server.)

For those of you who have the HPN-SSH version of OpenSSH, you may elect to
have your SSH clients connect using that feature.  If you wish to test 
this feature the capture servers are enabled for it.  The servers will try 
to optimise the connection to have your transfers sped-up, subject to 
network, system and stack tuning.  For more information on how to do this, 
please refer to ESNet's Host Tuning web page for your particular 
operating system:

          https://fasterdata.es.net/host-tuning/

For details on HPN-SSH and patches, see:

          http://www.psc.edu/index.php/hpn-ssh

An example invocation used @ DNS-OARC is:

          '/usr/local/bin/ssh -caes128'

When passed to rsync.  Those who do not wish to use HPN-SSH clients will
remain unaffected and uploads will proceed as normal.

Thank you,

William

From as112-ops at trex.fi  Mon Mar 13 11:52:27 2017
From: as112-ops at trex.fi (Aleksi Suhonen)
Date: Mon, 13 Mar 2017 13:52:27 +0200
Subject: [as112-ops] Yahoo Peering Invite at Phoenix IX
In-Reply-To: <201703101736.v2AHZxgV032389@mrout1.yahoo.com>
References: <201703101736.v2AHZxgV032389@mrout1.yahoo.com>
Message-ID: <1dae474c-f1f6-053c-adc3-99b2d5d2d93e@trex.fi>

Hello,

On 03/10/2017 07:35 PM, peering-requests at yahoo-inc.com wrote:
> Dear Peer
> 
> Yahoo!, AS10310 has recently joined 'Phoenix IX', and we would like to peer with you.
> By peering with Yahoo, you will be able to get Tumblr, Flickr, Yahoo Sports and many other
> Yahoo services directly.

AS112 is an anycast service that is operated by dozens of different
organizations around the globe. Your peering automaton has picked the
contact address for the node in Tampere, Finland.

More info on AS112: https://www.as112.net/

I don't know who operates the node at 'Phoenix IX', so I've Cc'ed this
email to the global mailing list of AS112 operators. I hope someone from
Phoenix will get back to you.

> Our IP addresses are : 206.41.105.36, 2001:504:3b::36, 206.41.105.56, 2001:504:3b::56
> Md5 : not required
> 
> If you are ready to proceed, please simply setup your peering session and then contact us
> by replying to this email, including your ASN's peeringdb link in your response
> as this will allow us to build the sessions more efficiently.
> 
> We will then enable your session on our end and contact you confirming the session is up.
> If you want to peer with Yahoo in additional locations, please visit http://as10310.peeringdb.com
> and let us know what other locations you want to establish peering.
> 
> Follow above process and configure your end where we have common points of presence.
> Further details on Yahoo peering can be found at http://peering.yahoo.com
> 
> Thank you for peering!
> 
> 
> Yahoo! Global Interconnection Team
> http://peering.yahoo.com :: peering at yahoo.com :: as10310
> 

BTW, we'd love to peer with you in Finland. :-)

Best Regards,

-- 
	+358 44 9756548 / http://www.trex.fi/
	Aleksi Suhonen / TREX Regional Exchanges Oy

	You say "potato", I say "closest-exit."

From yahoo at service-now.com  Mon Mar 13 11:55:07 2017
From: yahoo at service-now.com (Yahoo! Help Central)
Date: Mon, 13 Mar 2017 04:55:07 -0700 (PDT)
Subject: [as112-ops] You are on the watchlist for ticket PTKT0619793
Message-ID: <15897970.107150.1489406107522.JavaMail.p16030@app129100.sjc4.service-now.com>

Hello,

You have received this message because you have been added to the watch list for this request: PTKT0619793 - Re: Yahoo Peering Invite at Phoenix IX

The description of the request is: Hello,

On 03/10/2017 07:35 PM, peering-requests at yahoo-inc.com wrote:
> Dear Peer
> 
> Yahoo!, AS10310 has recently joined 'Phoenix IX', and we would like to peer with you.
> By peering with Yahoo, you will be able to get Tumblr, Flickr, Yahoo Sports and many other
> Yahoo services directly.

AS112 is an anycast service that is operated by dozens of different
organizations around the globe. Your peering automaton has picked the
contact address for the node in Tampere, Finland.

More info on AS112: https://www.as112.net/

I don't know who operates the node at 'Phoenix IX', so I've Cc'ed this
email to the global mailing list of AS112 operators. I hope someone from
Phoenix will get back to you.

> Our IP addresses are : 206.41.105.36, 2001:504:3b::36, 206.41.105.56, 2001:504:3b::56
> Md5 : not required
> 
> If you are ready to proceed, please simply setup your peering session and then contact us
> by replying to this email, including your ASN's peeringdb link in your response
> as this will allow us to build the sessions more efficiently.
> 
> We will then enable your session on our end and contact you confirming the session is up.
> If you want to peer with Yahoo in additional locations, please visit http://as10310.peeringdb.com
> and let us know what other locations you want to establish peering.
> 
> Follow above process and configure your end where we have common points of presence.
> Further details on Yahoo peering can be found at http://peering.yahoo.com
> 
> Thank you for peering!
> 
> 
> Yahoo! Global Interconnection Team
> http://peering.yahoo.com :: peering at yahoo.com :: as10310
> 

BTW, we'd love to peer with you in Finland. :-)

Best Regards,

-- 
 +358 44 9756548 / http://www.trex.fi/
 Aleksi Suhonen / TREX Regional Exchanges Oy

 You say "potato", I say "closest-exit."

Thank you,

Yahoo Peering Team

Ref:MSG34996455
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dns-oarc.net/mailman/private/as112-ops/attachments/20170313/aa12b3b2/attachment.html>

From nick at inex.ie  Mon Mar 13 12:10:16 2017
From: nick at inex.ie (Nick Hilliard)
Date: Mon, 13 Mar 2017 12:10:16 +0000
Subject: [as112-ops] Yahoo Peering Invite at Phoenix IX
In-Reply-To: <1dae474c-f1f6-053c-adc3-99b2d5d2d93e@trex.fi>
References: <201703101736.v2AHZxgV032389@mrout1.yahoo.com>
 <1dae474c-f1f6-053c-adc3-99b2d5d2d93e@trex.fi>
Message-ID: <58C68C28.1080503@inex.ie>

Aleksi Suhonen wrote:
> AS112 is an anycast service that is operated by dozens of different
> organizations around the globe. Your peering automaton has picked the
> contact address for the node in Tampere, Finland.

Yahoo! aren't the only organisation with a provisioning system which
can't cope with AS112.  INEX regularly gets emails from other
organisations with presences at multiple IXPs  :-D

Nick

From as112-ops at trex.fi  Mon Mar 13 12:19:35 2017
From: as112-ops at trex.fi (Aleksi Suhonen)
Date: Mon, 13 Mar 2017 14:19:35 +0200
Subject: [as112-ops] Yahoo Peering Invite at Phoenix IX
In-Reply-To: <58C68C28.1080503@inex.ie>
References: <201703101736.v2AHZxgV032389@mrout1.yahoo.com>
 <1dae474c-f1f6-053c-adc3-99b2d5d2d93e@trex.fi> <58C68C28.1080503@inex.ie>
Message-ID: <af214da8-34f6-d428-14e9-8d18c2e24060@trex.fi>

[Removed yahoo from this thread]

On 03/13/2017 02:10 PM, Nick Hilliard wrote:
> Aleksi Suhonen wrote:
>> AS112 is an anycast service that is operated by dozens of different
>> organizations around the globe. Your peering automaton has picked the
>> contact address for the node in Tampere, Finland.
> 
> Yahoo! aren't the only organisation with a provisioning system which
> can't cope with AS112.  INEX regularly gets emails from other
> organisations with presences at multiple IXPs  :-D

This could be attributed to a shortcoming in the peeringdb data model:
it would be nice to be able to designate different peering contacts for
different places. I'm sure there are other ASNs as well, that have
regional peering coordinators. I think Google is one such example?

The challenge of course is to find a way to accommodate different
granularities of regions (per IXP, per Continent, per Country, ...) and
I don't think it makes sense to try to fix peeringdb to support this.

Perhaps we should instead consider submitting this mailing list as the
contact for as112.peeringdb.com?

-- 
	+358 44 9756548 / http://www.trex.fi/
	Aleksi Suhonen / TREX Regional Exchanges Oy

	You say "potato", I say "closest-exit."

From chris at in-berlin.de  Mon Mar 13 19:47:51 2017
From: chris at in-berlin.de (Christian Seitz)
Date: Mon, 13 Mar 2017 20:47:51 +0100
Subject: [as112-ops] Yahoo Peering Invite at Phoenix IX
In-Reply-To: <af214da8-34f6-d428-14e9-8d18c2e24060@trex.fi>
References: <201703101736.v2AHZxgV032389@mrout1.yahoo.com>
 <1dae474c-f1f6-053c-adc3-99b2d5d2d93e@trex.fi> <58C68C28.1080503@inex.ie>
 <af214da8-34f6-d428-14e9-8d18c2e24060@trex.fi>
Message-ID: <69f10230-9532-cf4c-8502-f4b844c2210b@in-berlin.de>

Hello Aleksi,

Am 13.03.2017 um 13:19 schrieb Aleksi Suhonen:
> [Removed yahoo from this thread]
> 
> On 03/13/2017 02:10 PM, Nick Hilliard wrote:
>> Aleksi Suhonen wrote:
>>> AS112 is an anycast service that is operated by dozens of different
>>> organizations around the globe. Your peering automaton has picked the
>>> contact address for the node in Tampere, Finland.
>>
>> Yahoo! aren't the only organisation with a provisioning system which
>> can't cope with AS112.  INEX regularly gets emails from other
>> organisations with presences at multiple IXPs  :-D
> 
> This could be attributed to a shortcoming in the peeringdb data model:
> it would be nice to be able to designate different peering contacts for
> different places. I'm sure there are other ASNs as well, that have
> regional peering coordinators. I think Google is one such example?
> 
> The challenge of course is to find a way to accommodate different
> granularities of regions (per IXP, per Continent, per Country, ...) and
> I don't think it makes sense to try to fix peeringdb to support this.
> 
> Perhaps we should instead consider submitting this mailing list as the
> contact for as112.peeringdb.com?

I could change this in PeeringDB if the members of this list give their OK. I
thought direct contact emails for the nodes would be better in PeeringDB, but
this leads to a problem in case of AS112.

Regards, Chris
-- 
Individual Network Berlin e.V. : support at in-berlin.de : vorstand at in-berlin.de
Tel +49-30-45494343 ::: Fax +49-30-45494344 ::: Web https://www.in-berlin.de/
IN-Berlin e.V. : Christian Seitz (1. Vors.) : Lehrter Str. 53 :: 10557 Berlin
Amtsgericht Charlottenburg 95 - VR 15669 Nz ::::::: USt.Ident-Nr. DE188894648

From clement at cavadore.net  Mon Mar 13 19:57:50 2017
From: clement at cavadore.net (Clement Cavadore)
Date: Mon, 13 Mar 2017 20:57:50 +0100
Subject: [as112-ops] Yahoo Peering Invite at Phoenix IX
In-Reply-To: <69f10230-9532-cf4c-8502-f4b844c2210b@in-berlin.de>
References: <201703101736.v2AHZxgV032389@mrout1.yahoo.com>
 <1dae474c-f1f6-053c-adc3-99b2d5d2d93e@trex.fi> <58C68C28.1080503@inex.ie>
 <af214da8-34f6-d428-14e9-8d18c2e24060@trex.fi>
 <69f10230-9532-cf4c-8502-f4b844c2210b@in-berlin.de>
Message-ID: <1489435070.2901.10.camel@puisard.hivane.net>

Hello Christian,

On Mon, 2017-03-13 at 20:47 +0100, Christian Seitz wrote:
> > Perhaps we should instead consider submitting this mailing list as the
> > contact for as112.peeringdb.com?
> 
> I could change this in PeeringDB if the members of this list give their OK. I
> thought direct contact emails for the nodes would be better in PeeringDB, but
> this leads to a problem in case of AS112.

I am not sure that this could be easily doable: Is this mailing list
posting open to non subscribed members ?

In my case, I added to my main ASN page (34019) the AS112 peering
addresses of the anycast node I run on https://as34019.peeringdb.com
but by experience, people do not really understand.


Isn't it possible for peeringDB to have a special case for
https://as112.peeringdb.com with an explanation about how special AS112
is, and to have a per-ixp contact ? This is almost impossible to have a
complete accurate list of IXP-connected instances, but that would still
be helpful.

-- 
Cl?ment Cavadore


From keith at dns-oarc.net  Mon Mar 13 20:09:51 2017
From: keith at dns-oarc.net (Keith Mitchell)
Date: Mon, 13 Mar 2017 16:09:51 -0400
Subject: [as112-ops] Yahoo Peering Invite at Phoenix IX
In-Reply-To: <1489435070.2901.10.camel@puisard.hivane.net>
References: <201703101736.v2AHZxgV032389@mrout1.yahoo.com>
 <1dae474c-f1f6-053c-adc3-99b2d5d2d93e@trex.fi> <58C68C28.1080503@inex.ie>
 <af214da8-34f6-d428-14e9-8d18c2e24060@trex.fi>
 <69f10230-9532-cf4c-8502-f4b844c2210b@in-berlin.de>
 <1489435070.2901.10.camel@puisard.hivane.net>
Message-ID: <58C6FC8F.8000700@dns-oarc.net>

On 03/13/2017 03:57 PM, Clement Cavadore wrote:

>>> Perhaps we should instead consider submitting this mailing list
>>> as the contact for as112.peeringdb.com?
>> 
>> I could change this in PeeringDB if the members of this list give
>> their OK. I thought direct contact emails for the nodes would be
>> better in PeeringDB, but this leads to a problem in case of AS112.
> 
> I am not sure that this could be easily doable: Is this mailing list 
> posting open to non subscribed members ?

Us OARC folks are moderating this list, so can approve any non-member
postings to be forwarded to the list if this is the way people want to go.

Keith


From grizz at 20c.com  Thu Mar 16 05:42:07 2017
From: grizz at 20c.com (Matt Griswold)
Date: Thu, 16 Mar 2017 05:42:07 +0000
Subject: [as112-ops] Yahoo Peering Invite at Phoenix IX
In-Reply-To: <af214da8-34f6-d428-14e9-8d18c2e24060@trex.fi>
References: <201703101736.v2AHZxgV032389@mrout1.yahoo.com>
 <1dae474c-f1f6-053c-adc3-99b2d5d2d93e@trex.fi>
 <58C68C28.1080503@inex.ie>
 <af214da8-34f6-d428-14e9-8d18c2e24060@trex.fi>
Message-ID: <20170316054207.1ae998d9@x0r>

* Aleksi Suhonen <as112-ops at trex.fi> [170313 14:19 +0200]:
> This could be attributed to a shortcoming in the peeringdb data model:
> it would be nice to be able to designate different peering contacts
> for different places. I'm sure there are other ASNs as well, that
> have regional peering coordinators. I think Google is one such
> example?
> 
> The challenge of course is to find a way to accommodate different
> granularities of regions (per IXP, per Continent, per Country, ...)
> and I don't think it makes sense to try to fix peeringdb to support
> this.

That's what we decided at PeeringDB as well, at least for the time
being.

* Clement Cavadore <clement at cavadore.net> [170313 20:57 +0100]:
> I am not sure that this could be easily doable: Is this mailing list
> posting open to non subscribed members ?
> 
> In my case, I added to my main ASN page (34019) the AS112 peering
> addresses of the anycast node I run on https://as34019.peeringdb.com
> but by experience, people do not really understand.
> 
> Isn't it possible for peeringDB to have a special case for
> https://as112.peeringdb.com with an explanation about how special
> AS112 is, and to have a per-ixp contact ? This is almost impossible
> to have a complete accurate list of IXP-connected instances, but that
> would still be helpful.

We ended up with a semi-solution of listing each IX that offers as112
under the Public Exchange Points at https://as112.peeringdb.com which
is a method most of the bigger networks handle correctly. I agree that
putting a better explanation in the notes section would be a good
thing, however that's still not going to stop automated emails.

From as112-ops at trex.fi  Sun Mar 19 20:44:39 2017
From: as112-ops at trex.fi (Aleksi Suhonen)
Date: Sun, 19 Mar 2017 22:44:39 +0200
Subject: [as112-ops] Yahoo Peering Invite at Phoenix IX
In-Reply-To: <58C6FC8F.8000700@dns-oarc.net>
References: <201703101736.v2AHZxgV032389@mrout1.yahoo.com>
 <1dae474c-f1f6-053c-adc3-99b2d5d2d93e@trex.fi> <58C68C28.1080503@inex.ie>
 <af214da8-34f6-d428-14e9-8d18c2e24060@trex.fi>
 <69f10230-9532-cf4c-8502-f4b844c2210b@in-berlin.de>
 <1489435070.2901.10.camel@puisard.hivane.net> <58C6FC8F.8000700@dns-oarc.net>
Message-ID: <cc29bf70-a230-fbac-48b3-d9797411482d@trex.fi>

Hi,
>>>> Perhaps we should instead consider submitting this mailing list
>>>> as the contact for as112.peeringdb.com?

>> I am not sure that this could be easily doable: Is this mailing list 
>> posting open to non subscribed members ?

> Us OARC folks are moderating this list, so can approve any non-member
> postings to be forwarded to the list if this is the way people want to go.

FWIW, We just received a peering request from the self-same Yahoo Inc
for Equinix Paris and couldn't find that listed at
https://www.as112.net/ops-listing.html either.

-- 
	+358 44 9756548 / http://www.trex.fi/
	Aleksi Suhonen / TREX Regional Exchanges Oy

	You say "potato", I say "closest-exit."

From clement at cavadore.net  Sun Mar 19 22:12:42 2017
From: clement at cavadore.net (Clement Cavadore)
Date: Sun, 19 Mar 2017 23:12:42 +0100
Subject: [as112-ops] Yahoo Peering Invite at Phoenix IX
In-Reply-To: <cc29bf70-a230-fbac-48b3-d9797411482d@trex.fi>
References: <201703101736.v2AHZxgV032389@mrout1.yahoo.com>
 <1dae474c-f1f6-053c-adc3-99b2d5d2d93e@trex.fi> <58C68C28.1080503@inex.ie>
 <af214da8-34f6-d428-14e9-8d18c2e24060@trex.fi>
 <69f10230-9532-cf4c-8502-f4b844c2210b@in-berlin.de>
 <1489435070.2901.10.camel@puisard.hivane.net>
 <58C6FC8F.8000700@dns-oarc.net>
 <cc29bf70-a230-fbac-48b3-d9797411482d@trex.fi>
Message-ID: <1489961562.32377.4.camel@puisard.hivane.net>

On Sun, 2017-03-19 at 22:44 +0200, Aleksi Suhonen wrote:
> FWIW, We just received a peering request from the self-same Yahoo Inc
> for Equinix Paris and couldn't find that listed at
> https://www.as112.net/ops-listing.html either.

We received it too, and we are responsible for it (Hivane), so thanks
for the followup :-)

For the ops page, maybe an update may be interesting: Hivane's node has
three IXP peering IPs in Paris area (The v4 global unicast listed on the
page is still valid, and the v6 is: 2001:67c:1740:8000::112)

FranceIX: 	37.49.236.37 	/ 2001:7f8:54::37 
Equinix-Paris: 	195.42.144.146	/ 2001:7f8:43::112:1
Sfinx: 		194.68.129.166	/ 2001:7f8:4e:2::166

Regards,

-- 
Cl?ment Cavadore



