IIJ demonstrating emergency information for broadband and smart TVs

[Sean Donelan]

Internet Initiative Japan (IIJ) and T-NET Japan are demonstrating a hybrid 
integration of emergency alerts for broadcasting and broadband smart TVs 
at this week's National Association of Broadcasters convention.  A 
consortium of Korean broadcasters and manufacturers is also demonstrating 
UHD. In addition to the gorgeous video, the Korean UHD consortium has a 
very nice emergency alert demostration.


Korea and Japan seem to be the leaders.

The U.S. smart assistant companies (Amazon and Google) have very 
large booths on the NAB show floor, but their products don't have 
emergency alerts.

RE: Amazon AS16509 peering... how long to wait?

[Erik Sundberg]

Chase them down at the next Nanog… I had to do that for two large content 
providers.

From: NANOG  On Behalf Of Mike Hammett
Sent: Monday, April 8, 2019 8:02 AM
To: John Von Essen 
Cc: nanog@nanog.org
Subject: Re: Amazon AS16509 peering... how long to wait?

I submitted requests for multiple networks over the course of a year. One got 
acknowledged and had a few week wait from when the session came up to 
routes\traffic passing. The others have been ignored.


-
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com

Midwest-IX
http://www.midwest-ix.com


From: "John Von Essen" mailto:j...@essenz.com>>
To: nanog@nanog.org
Sent: Sunday, April 7, 2019 4:41:22 PM
Subject: Amazon AS16509 peering... how long to wait?

I applied for peering, received an email, setup the BGP session, waited
about a month. Then 3 weeks ago my BGP session with Amazom came up, but
with zero routes. I assume I am in some kind of test/waiting period, but
after three weeks, I thought I would be getting routes by now. Emails to
the peeringdb POC have not returned anything. Anyone here from AS16509,
can this be bumped? We are AS17185, and peering is on DE-CIX NYC.


Thanks

John




CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or 
previous e-mail messages attached to it may contain confidential information 
that is legally privileged. If you are not the intended recipient, or a person 
responsible for delivering it to the intended recipient, you are hereby 
notified that any disclosure, copying, distribution or use of any of the 
information contained in or attached to this transmission is STRICTLY 
PROHIBITED. If you have received this transmission in error please notify the 
sender immediately by replying to this e-mail. You must destroy the original 
transmission and its attachments without reading or saving in any manner. Thank 
you.

Spoofer Report for NANOG for Mar 2019

[CAIDA Spoofer Project]

In response to feedback from operational security communities,
CAIDA's source address validation measurement project
(https://spoofer.caida.org) is automatically generating monthly
reports of ASes originating prefixes in BGP for systems from which
we received packets with a spoofed source address.
We are publishing these reports to network and security operations
lists in order to ensure this information reaches operational
contacts in these ASes.

This report summarises tests conducted within usa, can.

Inferred improvements during Mar 2019:
   ASN Name   Fixed-By
  2828 XO-AS152019-03-06
 33523 ROWANUNIVERSITY2019-03-25
  5050 PSC-EXT2019-03-26

Further information for the inferred remediation is available at:
https://spoofer.caida.org/remedy.php

Source Address Validation issues inferred during Mar 2019:
   ASN Name   First-Spoofed Last-Spoofed
   577 BACOM 2016-03-09   2019-03-22
  7029 WINDSTREAM2016-06-21   2019-03-29
   209 CENTURYLINK-US-LEGACY-QWEST   2016-08-16   2019-03-26
  6128 CABLE-NET-1   2016-09-03   2019-03-30
 18530 ISOMEDIA-12016-09-27   2019-03-26
 20412 CLARITY-TELECOM   2016-09-30   2019-03-29
  6181 FUSE-NET  2016-10-10   2019-03-29
 25787 ROWE-NETWORKS 2016-10-21   2019-03-28
   174 COGENT-1742016-10-21   2019-03-22
 11537 ABILENE   2016-10-24   2019-03-04
 31857 PRIORITY-TERABIT  2016-10-25   2019-03-29
 30341 SCTA-ASN  2016-10-31   2019-03-25
 32440 LONI  2016-11-03   2019-03-26
 12083 WOW-INTERNET  2016-11-09   2019-03-31
  1403 EBOX  2016-11-12   2019-03-08
 13427 SOFTCOM-INTERNET-COMMUNICATION2016-11-14   2019-03-26
  3549 LVLT-3549 2016-11-16   2019-03-07
 21832 KELLINCOM-1   2017-02-03   2019-03-31
 18451 LESNET2017-02-22   2019-03-07
 53597 HOYOS-CONSULTING-LLC  2017-03-24   2019-03-09
 23314 ORLANDOTELCO  2017-04-14   2019-03-09
 19624 SERVERROOM2017-06-02   2019-03-25
   701 UUNET 2017-06-14   2019-03-09
  6461 ZAYO-6461 2017-06-21   2019-03-06
 63296 AMARILLO-WIRELESS 2017-09-01   2019-03-27
  7233 YAHOO-US  2017-09-07   2019-03-05
 33523 ROWANUNIVERSITY   2017-10-29   2019-03-25
   546 PARSONS-PGS-1 2017-11-20   2019-03-25
 1 AKAMAI2018-02-14   2019-03-26
  8100 ASN-QUADRANET-GLOBAL  2018-04-06   2019-03-07
  4201 ORST  2018-04-19   2019-03-27
 12028 MMINTERNET2018-06-14   2019-03-26
   225 VIRGINIA  2018-06-18   2019-03-26
 40911 L2NC  2018-08-31   2019-03-29
 33452 RW2018-09-19   2019-03-26
 20448 VPNTRANET-LLC 2018-09-20   2019-03-26
 11215 LOGIXCOMM 2018-09-20   2019-03-11
 11996 LOBOIS2018-09-24   2019-03-26
 13825 TROYCABLE-NET 2018-11-21   2019-03-26
 32329 MONKEYBRAINS  2018-11-28   2019-03-22
  4943 NOL   2019-03-04   2019-03-12
 20278 NEXEON2019-03-05   2019-03-05
395565 MIEMX 2019-03-08   2019-03-08
 19531 NODESDIRECT   2019-03-14   2019-03-28
 44685 ShatelNet 2019-03-23   2019-03-23
 11297 LIPSCOMB  2019-03-29   2019-03-29

Further information for these tests where we received spoofed
packets is available at:
https://spoofer.caida.org/recent_tests.php?country_include=usa,can&no_block=1

Please send any feedback or suggestions to spoofer-i...@caida.org

RE: NANOG Digest, Vol 135, Issue 8 [EXTERNAL MAIL]

[DurgaPrasad - DatasoftComnet via NANOG]

 here.

We've received configuration details in Mar 12 and we've completed the
configuration on the same day.

Then we didn't hear any news from them.

On Mon, Apr 8, 2019 at 6:37 AM Ross Tajvar  wrote:

> From what I've heard, their peering department is really behind on
> processing new peer turn-ups.
>
> On Sun, Apr 7, 2019, 6:16 PM Mehmet Akcin  wrote:
>
>> I will connect you to right people offlist
>>
>> I am surprised its taking that long
>>
>> On Sun, Apr 7, 2019 at 16:41 John Von Essen  wrote:
>>
>>> I applied for peering, received an email, setup the BGP session, waited
>>> about a month. Then 3 weeks ago my BGP session with Amazom came up, but
>>> with zero routes. I assume I am in some kind of test/waiting period, but
>>> after three weeks, I thought I would be getting routes by now. Emails to
>>> the peeringdb POC have not returned anything. Anyone here from AS16509,
>>> can this be bumped? We are AS17185, and peering is on DE-CIX NYC.
>>>
>>>
>>> Thanks
>>>
>>> John
>>>
>>> --
>> Mehmet
>> +1-424-298-1903
>>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mailman.nanog.org/pipermail/nanog/attachments/20190408/5e7d30f5/attachment-0001.html>

--

Message: 5
Date: Mon, 8 Apr 2019 10:40:07 +1000
From: Kieran Murphy 
To: Ross Tajvar 
Cc: Mehmet Akcin ,  "North American Network
Operators' Group" 
Subject: Re: Amazon AS16509 peering... how long to wait?
Message-ID:

Content-Type: text/plain; charset="utf-8"

Yeah, it takes a while.

My peering request turned 1 year old on Friday.
There was cake.

On Mon, 8 Apr 2019 at 08:36, Ross Tajvar  wrote:

> From what I've heard, their peering department is really behind on
> processing new peer turn-ups.
>
> On Sun, Apr 7, 2019, 6:16 PM Mehmet Akcin  wrote:
>
>> I will connect you to right people offlist
>>
>> I am surprised its taking that long
>>
>> On Sun, Apr 7, 2019 at 16:41 John Von Essen  wrote:
>>
>>> I applied for peering, received an email, setup the BGP session, waited
>>> about a month. Then 3 weeks ago my BGP session with Amazom came up, but
>>> with zero routes. I assume I am in some kind of test/waiting period, but
>>> after three weeks, I thought I would be getting routes by now. Emails to
>>> the peeringdb POC have not returned anything. Anyone here from AS16509,
>>> can this be bumped? We are AS17185, and peering is on DE-CIX NYC.
>>>
>>>
>>> Thanks
>>>
>>> John
>>>
>>> --
>> Mehmet
>> +1-424-298-1903
>>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mailman.nanog.org/pipermail/nanog/attachments/20190408/188d7a80/attachment-0001.html>

--

Message: 6
Date: Sun, 7 Apr 2019 21:01:26 -0700
From: Bill Blackford 
To: Kieran Murphy 
Cc: Ross Tajvar , North American Network Operators'
Group 
Subject: Re: Amazon AS16509 peering... how long to wait?
Message-ID: <7ca9348b-0a17-4cff-9302-e13c31f64...@gmail.com>
Content-Type: text/plain; charset="utf-8"

😳🤣

Sent from my iPhone

> On Apr 7, 2019, at 17:40, Kieran Murphy  wrote:
>
> Yeah, it takes a while.
>
> My peering request turned 1 year old on Friday.
> There was cake.
>
>> On Mon, 8 Apr 2019 at 08:36, Ross Tajvar  wrote:
>> From what I've heard, their peering department is really behind on 
>> processing new peer turn-ups.
>>
>>> On Sun, Apr 7, 2019, 6:16 PM Mehmet Akcin  wrote:
>>> I will connect you to right people offlist
>>>
>>> I am surprised its taking that long
>>>
>>>> On Sun, Apr 7, 2019 at 16:41 John Von Essen  wrote:
>>>> I applied for peering, received an email, setup the BGP session, waited
>>>> about a month. Then 3 weeks ago my BGP session with Amazom came up, but
>>>> with zero routes. I assume I am in some kind of test/waiting period, but
>>>> after three weeks, I thought I would be getting routes by now. Emails to
>>>> the peeringdb POC have not returned anything. Anyone here from AS16509,
>>>> can this be bumped? We are AS17185, and peering is on DE-CIX NYC.
>>>>
>>>>
>>>> Thanks
>>>>
>>>> John
>>>>
>>> --
>>> Mehmet
>>> +1-424-298-1903
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mailman.nanog.org/pipermail/nanog/attachments/20190407/c875a280/attachment-0001.html>

End of NANOG Digest, Vol 135, Issue 8
*


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Re: SFP supplier in Europe?

[Måns Nilsson]

Subject: SFP supplier in Europe? Date: Thu, Apr 04, 2019 at 10:09:15PM +0200 
Quoting nanog-...@mail.com (nanog-...@mail.com):
> Hello NANOG,
> 
> Could somebody recommend an SFP supplier in Europe with a warehouse in the EU 
> and fast shipping? I need to pick up some 80km Bidi SFPs and I'd prefer to 
> use a supplier has and will keep stock locally.

With the caveats discussed in the thread taken into consideration,
I'd pitch in that both FS and FlexOptix have proven useful to me.
Flex got me a very specific coding (Siemens SDH gear compatible) in
no time, and FS are -- for stocked items -- hard to beat on price and
shipping time. Both being inside EU means zero hassle with customs
which is important. (Poor Brits, what have they done to themselves?)

-- 
Måns Nilsson primary/secondary/besserwisser/machina
MN-1334-RIPE   SA0XLR+46 705 989668
Are we on STRIKE yet?


signature.asc
Description: PGP signature

Re: Amazon AS16509 peering... how long to wait?

[Mike Hammett]

I submitted requests for multiple networks over the course of a year. One got 
acknowledged and had a few week wait from when the session came up to 
routes\traffic passing. The others have been ignored. 




- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 

Midwest-IX 
http://www.midwest-ix.com 

- Original Message -

From: "John Von Essen"  
To: nanog@nanog.org 
Sent: Sunday, April 7, 2019 4:41:22 PM 
Subject: Amazon AS16509 peering... how long to wait? 

I applied for peering, received an email, setup the BGP session, waited 
about a month. Then 3 weeks ago my BGP session with Amazom came up, but 
with zero routes. I assume I am in some kind of test/waiting period, but 
after three weeks, I thought I would be getting routes by now. Emails to 
the peeringdb POC have not returned anything. Anyone here from AS16509, 
can this be bumped? We are AS17185, and peering is on DE-CIX NYC. 


Thanks 

John